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

gbak: ERROR: table id <number> is not defined [CORE5509] #5778

Open
firebird-automations opened this issue Mar 24, 2017 · 2 comments
Open

gbak: ERROR: table id <number> is not defined [CORE5509] #5778

firebird-automations opened this issue Mar 24, 2017 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Attila Molnár (e_pluribus_unum)

Hi!

I create/alter/drop tables in parallel and in high frequency (stress and concurrency test)
During this test I run gbak on the database, and I get some "table id <number> is not defined" errors from gbak.

I tought gbak runs in snapshot mode, so this should never happen. (or snapshot is just for data and not for metadata?)

Also sometimes the reported error is wrong, because the reported table id is existed before the gbak start, and still existed after the gbak finish and not dropped/altered druing the run and still get reported as not defined.

@EPluribusUnum
Copy link

We have this issue in 3.0.10 also.

@hvlad
Copy link
Member

hvlad commented Jun 6, 2023

Yes, gbak run backup in snapshot transaction, but engine see metadata despite of user transaction mode.
BTW, it is not recommended (since IB times) to run DDL in concurrent environment.
Do you have reproducible test case ?
No promise to fully fix it in current versions, but some improvements could be made, I hope.

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

No branches or pull requests

3 participants