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

Garbage collection in GTT is unnecessary delayed by active transactions in another attachments [CORE3536] #3893

Closed
firebird-issue-importer opened this issue Jun 24, 2011 · 4 comments

Comments

@firebird-issue-importer

Submitted by: @hvlad

It is well known that OST defines garbage collection treshold for every record in database.
By its nature, GTT's data is local to one attachment. Again, by its nature, OST is global state.
While (global) OST could be stuck or slowly advanced, there is no need to look at it to detect
if given record verion in GTT is mature for garbage collection. Instead, attachment-local
counter could be maintained to define garbage collection treshold for GTT's records in given
attachement.

Commits: 08842c3 f2aaa12

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 24, 2011

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 24, 2011

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 23, 2013

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2016

Modified by: @pavel-zotov

QA Status: No test

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