|Subject||Re: [firebird-support] High CPU use after restore|
Thursday, October 29, 2015, 9:55:20 PM, you wrote:
The comment about "at least rebuild indexes" does that mean that I can expect this to work or do I risk that I still need to backup/restore?
A restore will rebuild all of the indexes. However, the indexes affected by the v.2.5.1 bug are those that are compound, i.e., multi-column, so they are the only ones you need to rebuild. A backup/restore will not be required.
If you have multi-column primary, foreign or unique key constraints, note that ALTER INDEX <index-name> INACTIVE will not work on a constraint index; but ALTER INDEX <index-name> ACTIVE will rebuild those anyway.
Do I need to say, do this job whilst you have exclusive access as an administrator of the database or as the owner of the affected tables.