Invalid transaction counters may be reported in firebird.log during the sweep [CORE3978] #4311
Assignees
Comments
Modified by: @dyemanovreporter: Dmitry Yemanov [ dimitr ] => Pavel Zotov [ tabloid ] |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.3 [ 10461 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested Test Details: AFAIR, this issue was created after run test with very intensive workload (100-200 attachments) for checking index corruption during several hours. It's impossible to repeat such test on regular basis. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @pavel-zotov
Is related to CORE2668
Log output example:
reservdb Sun Nov 11 02:26:56 2012
Sweep is started by SYSDBA
Database "idx_test"
OIT 855585, OAT 855586, OST 855586, Next 46909633725807
reservdb Sun Nov 11 02:29:00 2012
Sweep is finished
Database "idx_test"
OIT 855585, OAT 855586, OST 855586, Next 943545
Commits: 4192553 ef51f56
====== Test Details ======
AFAIR, this issue was created after run test with very intensive workload (100-200 attachments) for checking index corruption during several hours. It's impossible to repeat such test on regular basis.
The text was updated successfully, but these errors were encountered: