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
The crazy (but allowed) statement ALTER DATABASE BEGIN BACKUP END BACKUP could crash the engine on commit.
It happens also if ALTER DATABASE BEGIN BACKUP and ALTER DATABASE END BACKUP is issued in the same transaction.
The crash happens if database was not in physical backup (state == normal) due to access to not initialized allocation table.
I going to fix the crash and to disable such ambiguous statements as shown above.
Submitted by: @hvlad
The crazy (but allowed) statement ALTER DATABASE BEGIN BACKUP END BACKUP could crash the engine on commit.
It happens also if ALTER DATABASE BEGIN BACKUP and ALTER DATABASE END BACKUP is issued in the same transaction.
The crash happens if database was not in physical backup (state == normal) due to access to not initialized allocation table.
I going to fix the crash and to disable such ambiguous statements as shown above.
Commits: 2a53615 df109c3 45a4ecb b217175
The text was updated successfully, but these errors were encountered: