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

Physical backup doesn't delete the delta file if the db is dropped before stopping such physical backup [CORE2749] #3144

Open
firebird-automations opened this issue Nov 12, 2009 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Claudio Valderrama C. (robocop)

F:\fb3dev\fbbuild\firebird30\temp\Win32\Debug\firebird\bin>isql
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'flags.db';
SQL> alter database begin backup;
SQL> drop database;
SQL> shell dir;
...
13-11-2009 08:29 12.288 FLAGS.DB.delta
SQL>

The db was deleted but the delta wasn't. Either dropping a db with a physical backup in progress is not allowed or the delta is obliterated, too.

@firebird-automations
Copy link
Collaborator Author

Commented by: Claudio Valderrama C. (robocop)

It's more correct to assign the bug to ENGINE itself.

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

Component: Engine [ 10000 ]

Component: NBACKUP [ 10007 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @romansimakov

I think we should drop delta file as well. If we need not database having delta does not make sense. Right?

@firebird-automations
Copy link
Collaborator Author

Commented by: Claudio Valderrama C. (robocop)

There are two options and I don't know what's better:
- When dropping the db, the delta file is deleted as well even if a physical backup is in progress; no warning to the user.
- The db can't be dropped unless the physical backup is stopped.

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