Make StandbyAcquireAccessExclusiveLock() more resilent with OOMs In StandbyReleaseXidEntryLocks, a failure in acquiring a lock with LockAcquire() due to an out-of-memory problem would lead to an inconsistency with the lock state cached in the startup process, impacting the list of RecoveryLockXidEntrys. The code is updated here so as the cached state is updated once the lock is acquired.
This problem is unlikely going to happen in practice. Even if it were to show up, it would translate to a LOG message for non-assert builds (assertion failure otherwise), so no backpatch is done. This commit is in the same spirit as 29fb598b9cad, with a problem emulated by injecting random failures for allocations. Reported-by: Alexander Lakhin <[email protected]> Author: Matthias van de Meent <[email protected]> Discussion: https://postgr.es/m/[email protected] Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b85f9c00fb8822eb2142c347ce529f651dbef178 Modified Files -------------- src/backend/storage/ipc/standby.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
