Garbage collection in GTT is unnecessary delayed by active transactions in
another attachments
----------------------------------------------------------------------------------------------
Key: CORE-3536
URL: http://tracker.firebirdsql.org/browse/CORE-3536
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Affects Versions: 2.1.4, 2.5.0, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Vlad Khorsun
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
