Horton

Re: A failure in 031_recovery_conflict.pl on Debian/s390x

Christoph Berg <myon@debian.org>

View thread
From: Christoph Berg <myon@debian.org>
To: Thomas Munro <thomas.munro@gmail.com>
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-07T10:57:40Z
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 →

  1. Fix instability in 031_recovery_conflict.pl.

  2. Fix recovery conflict SIGUSR1 handling.

  3. Disable 031_recovery_conflict.pl in 15 and 16.

Attachments

Re: Thomas Munro
> Thanks for testing!  Would you mind trying v8 from that thread?  V7
> had a silly bug (I accidentally deleted a 'case' label while cleaning
> some stuff up, resulting in the above error...)

v8 worked better. It succeeded a few times (at least 12, my screen
scrollback didn't catch more) before erroring like this:

[10:21:58.410](0.151s) ok 15 - startup deadlock: logfile contains terminated connection due to recovery conflict
[10:21:58.463](0.053s) not ok 16 - startup deadlock: stats show conflict on standby
[10:21:58.463](0.000s)
[10:21:58.463](0.000s) #   Failed test 'startup deadlock: stats show conflict on standby'
#   at t/031_recovery_conflict.pl line 332.
[10:21:58.463](0.000s) #          got: '0'
#     expected: '1'

Christoph