diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-11-14 10:11:10 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-11-14 10:11:10 +0530 |
| commit | 20c22333630111718bc97ce9a19b392f23e3c525 (patch) | |
| tree | d701e3669f469521c38e43ae0065aeb77ac7d4c8 /src/backend/access/gist/gistutil.c | |
| parent | 58a45bb1d82b90e33a45b646717bf6a035256ded (diff) | |
| download | postgresql-20c22333630111718bc97ce9a19b392f23e3c525.tar.gz postgresql-20c22333630111718bc97ce9a19b392f23e3c525.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/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions