pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Yura Sokolov <y.sokolov@postgrespro.ru>
Cc: Sami Imseih <samimseih@gmail.com>
Cc: Chao Li <li.evan.chao@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
Subject: Re: Fix bug in multixact Oldest*MXactId initialization and access
Date: Tue, 03 Mar 2026 13:47:57 -0500
Message-ID: <1108077.1772563677@sss.pgh.pa.us> (raw)
In-Reply-To: <824fe90a-9954-4964-a177-bc8789f06d13@iki.fi>
References: <7acc94b0-ea82-4657-b1b0-77842cb7a60c@postgrespro.ru>
	<bf2951b4-687b-4bd3-a072-46deb463f177@postgrespro.ru>
	<CAA5RZ0t8iGnqO3JcAZP1VEjCspcnZtQ0GFFVGLNLAsFqfHqRsw@mail.gmail.com>
	<ebeb0db1-0eb2-4439-a6c8-1d96b60b25ad@postgrespro.ru>
	<CAA5RZ0s+rr=DVkFnMwupgnCAvPjJkjQ3jr5=7X_=Sb5Mr02-Mg@mail.gmail.com>
	<3d7a2207-0e61-4d95-bc00-e5248956a32b@postgrespro.ru>
	<366b6f95-613d-4ef8-82e4-bb2fd06d9c4d@iki.fi>
	<CAA5RZ0vXCMHEsPg7wFXmBOEPgWB8NvGKWx9cZsz7F99mFU+xLw@mail.gmail.com>
	<231cd950-73e9-4db5-a516-c5216af7b93a@iki.fi>
	<944d7897-3ec3-47bb-9e93-b99f2ef3124a@postgrespro.ru>
	<CAA5RZ0umyHiQNwr1m6FVF0WPCP3QAFAzdF=mQ+_u-vknhOBYWw@mail.gmail.com>
	<A0249625-0EF4-4068-854F-0592139DFBC1@gmail.com>
	<c585168a-210a-4728-8e5e-8e9384126ccd@iki.fi>
	<CAA5RZ0s3wL+4RJRRtJVK1VxEgAmYrj7ftfSuAJHJ+oDfTabQbg@mail.gmail.com>
	<120550bf-ca50-4a07-91b1-a88f1434ee8b@postgrespro.ru>
	<e7c8a4ef-458a-4e7! 2-be09-51c65ab446d5@iki.fi>
	<1009073.1772551323@sss.pgh.pa.us>
	<824fe90a-9954-4964-a177-bc8789f06d13@! iki.fi>

Heikki Linnakangas <hlinnaka@iki.fi> writes:
> On 03/03/2026 17:22, Tom Lane wrote:
>> 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.

Personally I'd put the exit test after the file's header comment,
but that's just a quibble.  LGTM otherwise.

			regards, tom lane





view thread (31+ messages)  latest in thread

Message-ID: <1108077.1772563677@sss.pgh.pa.us>
Permalink:  ../1108077.1772563677@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1108077.1772563677@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, hlinnaka@iki.fi, y.sokolov@postgrespro.ru, samimseih@gmail.com, li.evan.chao@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Fix bug in multixact Oldest*MXactId initialization and access
  In-Reply-To: <1108077.1772563677@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox