Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Christoph Berg <myon@debian.org>
Cc: Noah Misch <noah@leadboat.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Andres Freund <andres@anarazel.de>
Date: 2023-08-05T01:42:33Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix instability in 031_recovery_conflict.pl.
- 0174c2d213f6 17.0 landed
-
Fix recovery conflict SIGUSR1 handling.
- 0da096d78e1e 17.0 landed
-
Disable 031_recovery_conflict.pl in 15 and 16.
- e13de4913913 15.5 landed
- 8d1cf9674a25 16.0 landed
On Sat, Aug 5, 2023 at 12:43 AM Christoph Berg <myon@debian.org> wrote: > I managed to reproduce it on the shell by running the test in a loop a > few times. The failure looks like this: It's great that you can reproduce this semi-reliably! I've rebased the patch, hoping you can try it out. https://www.postgresql.org/message-id/CA%2BhUKGJDcyW8Hbq3UyG-5-5Y7WqqOTjrXbFTMxxmhiofFraE-Q%40mail.gmail.com