diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-01-05 12:17:10 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-01-05 12:17:10 -0300 |
| commit | df9f682c7bf81674b6ae3900fd0146f35df0ae2e (patch) | |
| tree | acabb26e8db5019573f44fac8bafe40eebfd83fb /src/backend/executor/nodeModifyTable.c | |
| parent | 054e8c6cdb7f4261869e49d3ed7705cca475182e (diff) | |
| download | postgresql-df9f682c7bf81674b6ae3900fd0146f35df0ae2e.tar.gz postgresql-df9f682c7bf81674b6ae3900fd0146f35df0ae2e.zip | |
Fix failure to delete spill files of aborted transactions
Logical decoding's reorderbuffer.c may spill transaction files to disk
when transactions are large. These are supposed to be removed when they
become "too old" by xid; but file removal requires the boundary LSNs of
the transaction to be known. The final_lsn is only set when we see the
commit or abort record for the transaction, but nothing sets the value
for transactions that crash, so the removal code misbehaves -- in
assertion-enabled builds, it crashes by a failed assertion.
To fix, modify the final_lsn of transactions that don't have a value
set, to the LSN of the very latest change in the transaction. This
causes the spilled files to be removed appropriately.
Author: Atsushi Torikoshi
Reviewed-by: Kyotaro HORIGUCHI, Craig Ringer, Masahiko Sawada
Discussion: https://postgr.es/m/54e4e488-186b-a056-6628-50628e4e4ebc@lab.ntt.co.jp
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions