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
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e49e191815b6a7fc801e03cf798fb83d3b7f2501
Modified Files
--------------
src/backend/access/hash/hash_xlog.c | 5 ++---
src/backend/access/hash/hashpage.c | 10 +++++++---
2 files changed, 9 insertions(+), 6 deletions(-)
