diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-11-14 10:01:14 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-11-14 10:01:14 +0530 |
| commit | 4dccccb37e0b87bc3f941ea2c7f0b9e51661bc79 (patch) | |
| tree | 49fe061d3af083c35beb63e57034907cb734a8e5 /src/backend/access/heap/heapam_handler.c | |
| parent | 7dd39e9e80288f2f4ef2990c4f074010973b56cb (diff) | |
| download | postgresql-4dccccb37e0b87bc3f941ea2c7f0b9e51661bc79.tar.gz postgresql-4dccccb37e0b87bc3f941ea2c7f0b9e51661bc79.zip | |
Fix cleanup lock acquisition in SPLIT_ALLOCATE_PAGE replay.
During XLOG_HASH_SPLIT_ALLOCATE_PAGE replay, we were checking for a
cleanup lock on the new bucket page after acquiring an exclusive lock on
it and raising a PANIC error on failure. However, it is quite possible
that checkpointer can acquire the pin on the same page before acquiring a
lock on it, and then the replay will lead to an error. So instead, directly
acquire the cleanup lock on the new bucket page during
XLOG_HASH_SPLIT_ALLOCATE_PAGE replay operation.
Reported-by: Andres Freund
Author: Robert Haas
Reviewed-By: Amit Kapila, Andres Freund, Vignesh C
Backpatch-through: 11
Discussion: https://postgr.es/m/20220810022617.fvjkjiauaykwrbse@awork3.anarazel.de
Diffstat (limited to 'src/backend/access/heap/heapam_handler.c')
0 files changed, 0 insertions, 0 deletions