Subject Re: [Firebird-Architect] FW: Recomputing index statistics and stored procedures
Author Ann W. Harrison
Martijn Tonies wrote:
> How is classic currently handling metadata changes, any changes?
Table changes are handled through a table existence lock that must be
held exclusively to change the table. Getting that exclusive lock
requires signaling all other holders, who mark their copy of the table
as needing to be refreshed.

Index changes are handled through locks on the index root page for the

Foreign key changes, up to now, require exclusive access to the database
to avoid exactly the problems with classic.

There's nothing inherently wrong with classic, and it will be our
salvation as we move into clusters, but it does require a bit more care.