Make GetSnapshotData() more resilient on out-of-memory errors
Michael Paquier <michael@paquier.xyz>
Make GetSnapshotData() more resilient on out-of-memory errors If the allocation of Snapshot->subxip fails, a follow-up call of GetSnapshotData() would see a partially-initialized snapshot, causing a NULL dereference on reentry when using "subxip" because only "xip" would be allocated. In the event of an out-of-memory error when allocating "subxip", "xip" is now reset before throwing an ERROR, so as Snapshots can be allocated and handled gracefully on retry. This problem is unlikely going to show up in practice, so no backpatch. Reported-by: Alexander Lakhin <exclusion@gmail.com> Author: Matthias van de Meent <boekewurm+postgres@gmail.com> Discussion: https://postgr.es/m/e77acaac-a1b3-40b3-99ee-5769b4e453e4@gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/storage/ipc/procarray.c | modified | +8 −0 |
Discussion
- Unexpected behavior after OOM errors 14 messages · 2026-06-17 → 2026-06-20