diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-11 18:11:29 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-11 18:11:29 -0400 |
| commit | d1e9079295e9e6fcab8f2ad9c69dd1be8e876d47 (patch) | |
| tree | 537cf49a55082e8615c11ee2736d492257305af5 /src/include/executor/nodeModifyTable.h | |
| parent | 0408e1ed599b06d9bca2927a50a4be52c9e74bb9 (diff) | |
| download | postgresql-d1e9079295e9e6fcab8f2ad9c69dd1be8e876d47.tar.gz postgresql-d1e9079295e9e6fcab8f2ad9c69dd1be8e876d47.zip | |
Ignore nextOid when replaying an ONLINE checkpoint.
The nextOid value is from the start of the checkpoint and may well be stale
compared to values from more recent XLOG_NEXTOID records. Previously, we
adopted it anyway, allowing the OID counter to go backwards during a crash.
While this should be harmless, it contributed to the severity of the bug
fixed in commit 0408e1ed5, by allowing duplicate TOAST OIDs to be assigned
immediately following a crash. Without this error, that issue would only
have arisen when TOAST objects just younger than a multiple of 2^32 OIDs
were deleted and then not vacuumed in time to avoid a conflict.
Pavan Deolasee
Discussion: https://postgr.es/m/CABOikdOgWT2hHkYG3Wwo2cyZJq2zfs1FH0FgX-=h4OLosXHf9w@mail.gmail.com
Diffstat (limited to 'src/include/executor/nodeModifyTable.h')
0 files changed, 0 insertions, 0 deletions