| Subject | What can go wrong with indexes after migration from 2.5.1 to 2.5.2 ? |
|---|---|
| Author | hjcats59 |
| Post date | 2012-12-12T18:25:16Z |
Hello,
In the Firebird 2.5.2 release notes it is strongly advised to migrate databases using gbak backup/restore. or `If this is impracticable, at least rebuild all compound indices in the databases being migrated.'
What's the reason for this advise, what can go wrong when indexes are not rebuilt?
Is it because of http://tracker.firebirdsql.org/browse/CORE-3675
And if so would it be enough to rebuild indexes with these characteristics:
- Compound
- Unique
- At least one character column where nulls are allowed
Henk Cats
Syntess Software
In the Firebird 2.5.2 release notes it is strongly advised to migrate databases using gbak backup/restore. or `If this is impracticable, at least rebuild all compound indices in the databases being migrated.'
What's the reason for this advise, what can go wrong when indexes are not rebuilt?
Is it because of http://tracker.firebirdsql.org/browse/CORE-3675
And if so would it be enough to rebuild indexes with these characteristics:
- Compound
- Unique
- At least one character column where nulls are allowed
Henk Cats
Syntess Software