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

From: Christoph Berg <myon(at)debian(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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>
Subject: Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Date: 2025-09-11 12:28:06
Message-ID: aMLAVqeO5MuNcf0V@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Andres Freund
> Hm, that could just be a "harmless" race. Does it still happen if you apply
> the attached patch in addition?

> diff --git i/src/backend/utils/activity/pgstat_database.c w/src/backend/utils/activity/pgstat_database.c

Debian is still carrying that patch around. Did we ever get to any
conclusion on that issue?

https://salsa.debian.org/postgresql/postgresql/-/blob/18/debian/patches/pgstat-report-conflicts-immediately.patch?ref_type=heads

Christoph

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2025-09-11 12:43:35 Re: Making type Datum be 8 bytes everywhere
Previous Message Kirill Reshke 2025-09-11 12:07:29 Re: ALTER DATABASE RESET with unexistent guc doesn't report an error