Re: A failure in 031_recovery_conflict.pl on Debian/s390x - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Date
Msg-id CA+hUKGKYNHmL_DhmVRiidHv6YLAL8jViifwwn2ABY__Y3BCphg@mail.gmail.com
Whole thread Raw
In response to Re: A failure in 031_recovery_conflict.pl on Debian/s390x  (Christoph Berg <myon@debian.org>)
Responses Re: A failure in 031_recovery_conflict.pl on Debian/s390x
List pgsql-hackers
Thanks.  I realised that it's easy enough to test that theory about
cleanup locks by hacking ConditionalLockBufferForCleanup() to return
false randomly.  Then the test occasionally fails as described.  Seems
like we'll need to fix that test, but it's not evidence of a server
bug, and my signal handler refactoring patch is in the clear.  Thanks
for testing it!



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: CREATE FUNCTION ... SEARCH { DEFAULT | SYSTEM | SESSION }
Next
From: Amit Kapila
Date:
Subject: Re: Adding a LogicalRepWorker type field