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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Date: 2023-08-05 01:42:33
Message-ID: CA+hUKGK0w54NiAcGCVb-MJTz_FhUjEo553-tM0zctUtA6b2tpg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 5, 2023 at 12:43 AM Christoph Berg <myon(at)debian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-08-05 02:53:09 Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?
Previous Message Thomas Munro 2023-08-05 01:39:24 Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?