On Tue, 19 Aug 2025 at 10:32, Thomas Munro <thomas.mu...@gmail.com> wrote: >
> I don't know if there are other ways that LWLockReleaseAll() can lead > to persistent corruption that won't be corrected by crash recovery, > but this one is probably new since the following commit, explaining > the failure to reproduce on v17: > > commit bc22dc0e0ddc2dcb6043a732415019cc6b6bf683 > Author: Alexander Korotkov <akorot...@postgresql.org> > Date: Wed Apr 2 12:44:24 2025 +0300 > > Get rid of WALBufMappingLock > > Any idea involving deferring the handling of PM death from here > doesn't seem right: you'd keep waiting for the CV, but the backend > that would wake you might have exited. I revert this commit (these were conflicts but i resolved them) and added assert for crit sections in WaitEventSetWait. make check passes (without v2-0001 it fails) -- Best regards, Kirill Reshke
v2-0001-Revert-Get-rid-of-WALBufMappingLock.patch
Description: Binary data
v2-0002-Add-assertion-for-WaitEventSetWait-in-crit-sectio.patch
Description: Binary data
