mirror of
https://github.com/postgres/postgres.git
synced 2025-07-26 01:22:12 +03:00
Set ReorderBufferTXN->final_lsn more eagerly
... specifically, set it incrementally as each individual change is
spilled down to disk. This way, it is set correctly when the
transaction disappears without trace, ie. without leaving an XACT_ABORT
wal record. (This happens when the server crashes midway through a
transaction.)
Failing to have final_lsn prevents ReorderBufferRestoreCleanup() from
working, since it needs the final_lsn in order to know the endpoint of
its iteration through spilled files.
Commit df9f682c7b
already tried to fix the problem, but it didn't set
the final_lsn in all cases. Revert that, since it's no longer needed.
Author: Vignesh C
Reviewed-by: Amit Kapila, Dilip Kumar
Discussion: https://postgr.es/m/CALDaNm2CLk+K9JDwjYST0sPbGg5AQdvhUt0jbKyX_HdAE0jk3A@mail.gmail.com
This commit is contained in:
@ -207,9 +207,10 @@ typedef struct ReorderBufferTXN
|
||||
* * prepared transaction commit
|
||||
* * plain abort record
|
||||
* * prepared transaction abort
|
||||
* * error during decoding
|
||||
* * for a crashed transaction, the LSN of the last change, regardless of
|
||||
* what it was.
|
||||
*
|
||||
* This can also become set to earlier values than transaction end when
|
||||
* a transaction is spilled to disk; specifically it's set to the LSN of
|
||||
* the latest change written to disk so far.
|
||||
* ----
|
||||
*/
|
||||
XLogRecPtr final_lsn;
|
||||
|
Reference in New Issue
Block a user