You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before the fix the order of events when attachment is established was :
- exclusive access to dbb is acquired
- attachment block is created
...
- crypt thread is started
- TRA_sweep is run, if necessary
- BackupManager::endBackup is called
- "ATTACH_DATABASE" event is fired
- ON CONNECT trigger is fired
- exclusive access to dbb is released and concurrent attachments to the same dbb is allowed
TRA_sweep is run while exclusive access to dbb is holds, therefore it blocks cuncurrent attach_database calls.
Note: if exception is raised then "FAILED ATTACH_DATABASE" event is fired
New order of events is:
- exclusive access to dbb is acquired
- attachment block is created
...
- exclusive access to dbb is released and concurrent attachments to the same dbb is allowed
- "ATTACH_DATABASE" event is fired
- BackupManager::endBackup is called
- TRA_sweep is run, if necessary
- crypt thread is started
- ON CONNECT trigger is fired
If exception is raised after "ATTACH_DATABASE" was fired, then "ERROR" and "DETACH_DATABASE" events will be fired.
Submitted by: @hvlad
Commits: 32c5d00 ffa909f FirebirdSQL/fbt-repository@3224666 FirebirdSQL/fbt-repository@dcec4f3
The text was updated successfully, but these errors were encountered: