diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2023-02-22 15:24:09 +0100 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2023-02-22 16:48:30 +0100 |
| commit | 949ac32e12674d9c0bcd3d95ea5e56338a567a18 (patch) | |
| tree | 02ad3c19f516a4c5edacb2f233d78bb581705a02 /src/backend/executor | |
| parent | 576b25bfd0e9a1d5bbc54931e888135bc6da8a2f (diff) | |
| download | postgresql-949ac32e12674d9c0bcd3d95ea5e56338a567a18.tar.gz postgresql-949ac32e12674d9c0bcd3d95ea5e56338a567a18.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')
0 files changed, 0 insertions, 0 deletions