Attached is trimmed randgen output. For clarity, I have removed all bad queries (impossible WHERE's, etc) and SELECT's (I doubt they contributed to this).
What I have tried to do is compare randgen queries to the SQL generated by transaction_reader when called against the server's transaction log.
From my analysis, it appears that a block of queries was somehow missed / ignored by the log as queries that came before and after this block are visible in the transaction_reader output.
I can provide assistance with running the randgen test if you are interested in duplicating things yourself that way. Otherwise, we can work on trying to produce a test-run'able test case.
Attached is trimmed randgen output. For clarity, I have removed all bad queries (impossible WHERE's, etc) and SELECT's (I doubt they contributed to this).
What I have tried to do is compare randgen queries to the SQL generated by transaction_reader when called against the server's transaction log.
From my analysis, it appears that a block of queries was somehow missed / ignored by the log as queries that came before and after this block are visible in the transaction_reader output.
I can provide assistance with running the randgen test if you are interested in duplicating things yourself that way. Otherwise, we can work on trying to produce a test-run'able test case.