aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2023-02-22 15:24:09 +0100
committerTomas Vondra <tomas.vondra@postgresql.org>2023-02-22 16:09:30 +0100
commit4df581fa0f4b663141901d87817f77ec695c6d22 (patch)
treedd457555ddb020d0cc0b4c7f540d7244efd4f30c /src/backend/executor/nodeModifyTable.c
parent906356cf6128ac6e35bcb07f7fd5361eb76c4999 (diff)
downloadpostgresql-4df581fa0f4b663141901d87817f77ec695c6d22.tar.gz
postgresql-4df581fa0f4b663141901d87817f77ec695c6d22.zip
Fix snapshot handling in logicalmsg_decode
Whe decoding a transactional logical message, logicalmsg_decode called SnapBuildGetOrBuildSnapshot. But we may not have a consistent snapshot yet at that point. We don't actually need the snapshot in this case (during replay we'll have the snapshot from the transaction), so in practice this is harmless. But in assert-enabled build this crashes. Fixed by requesting the snapshot only in non-transactional case, where we are guaranteed to have SNAPBUILD_CONSISTENT. Backpatch to 11. The issue exists since 9.6. Backpatch-through: 11 Reviewed-by: Andres Freund Discussion: https://postgr.es/m/84d60912-6eab-9b84-5de3-41765a5449e8@enterprisedb.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions