Re: Fix bug in multixact Oldest*MXactId initialization and access

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, Sami Imseih <samimseih(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix bug in multixact Oldest*MXactId initialization and access
Date: 2026-03-03 18:47:57
Message-ID: 1108077.1772563677@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnaka(at)iki(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-03 18:50:46 Re: pg_dumpall --roles-only interact with other options
Previous Message Lukas Fittl 2026-03-03 18:22:42 Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?