Re: Fix bug in multixact Oldest*MXactId initialization and access - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Fix bug in multixact Oldest*MXactId initialization and access
Date
Msg-id 824fe90a-9954-4964-a177-bc8789f06d13@iki.fi
Whole thread Raw
In response to Re: Fix bug in multixact Oldest*MXactId initialization and access  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix bug in multixact Oldest*MXactId initialization and access
Re: Fix bug in multixact Oldest*MXactId initialization and access
List pgsql-hackers
On 03/03/2026 17:22, Tom Lane wrote:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
>> Ok, here's another version of Sami's repro. I realized that it doesn't
>> even need concurrent sessions, so I moved it to the main regression test
>> suite, into the 'prepared_xacts' test. Looks good?
> 
> Not directly relevant to the thing being tested here, but ...
> I wonder if we couldn't reduce future maintenance effort for
> prepared_xacts_1.out by modifying that test script to make an
> early exit if prepared transactions are disabled.

+1, I was just thinking the same.

Here's a patch to do that. I'll backpatch this to all supported 
versions, to make backpatching test changes less painful in the future.

- Heikki

Attachment

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: updates for handling optional argument in system functions
Next
From: "Matheus Alcantara"
Date:
Subject: Re: Show expression of virtual columns in error messages