Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Begin and end of physical backup in the same transaction could crash engine [CORE5707] #5973

Closed
firebird-issue-importer opened this issue Jan 14, 2018 · 4 comments

Comments

@firebird-issue-importer

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 14, 2018

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 21, 2018

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.3 [ 10810 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 22, 2018

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment