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

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, 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 17:08:44
Message-ID: CAA5RZ0vMxZkR=GgzOm6nrjS59ss-TSR+v2f_BUnEzpWi+38-Ug@mail.gmail.com
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?

You are correct. concurrent sessions not needed. v2 LGTM.

Thanks!

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-03-03 17:09:08 Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Previous Message Matheus Alcantara 2026-03-03 17:01:43 Re: Show expression of virtual columns in error messages