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 15:22:03
Message-ID: 1009073.1772551323@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:
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-03-03 15:31:06 Re: [BUG?] estimate_hash_bucket_stats uses wrong ndistinct for avgfreq
Previous Message Heikki Linnakangas 2026-03-03 15:11:05 Re: Fix bug in multixact Oldest*MXactId initialization and access