-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
Attempt to use data in destroyed transaction pool #7446
Comments
Alex, do you plan to backport it into v3/v4? |
On 1/12/23 15:10, Dmitry Yemanov wrote:
Alex, do you plan to backport it into v3/v4?
Yes, certainly. But sooner of all it needs one more change to make code
cleaner.
I wanted to wait for Pavel to fix tests for master but looks like it can
take too long. Will have to use just comparison of failed list after
that change.
PS. This has nothing to do with a bug that was observed in HQBird for a
long time.
|
AlexPeshkoff
added a commit
that referenced
this issue
Jan 12, 2023
AlexPeshkoff
added a commit
that referenced
this issue
Jan 13, 2023
(cherry picked from commit 6c431cb)
AlexPeshkoff
added a commit
that referenced
this issue
Jan 13, 2023
…nsaction pool (cherry picked from commit 799a0a6)
AlexPeshkoff
added a commit
that referenced
this issue
Jan 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug was reported privately by firebird user. As a visible result there were core dump and an error in firebird.log:
Stack trace:
clearly shows that an error happens due to an attempt to cleanup (too late attempt - when processing disconnect in CS) savepoint stored in metadata cache. Put attention that savepoints are always created in transaction memory pool and keeping them after commit/rollback in metadata cache is bad idea.
The text was updated successfully, but these errors were encountered: