Re: pg_upgrade stores an invalid datminmxid/relminmxid when the old cluster's newest multixact is 0xFFFFFFFF

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: pg_upgrade stores an invalid datminmxid/relminmxid when the old cluster's newest multixact is 0xFFFFFFFF
Date: 2026-10-17 08:11:54
Message-ID: CAN4CZFNkzb6oaMHOs9=5J=bcQz8rQFphys6bH0PqdNbaDYmu3Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

I agree that this seems to be another corner case, but about the commit message:

> servers before v19 skip 0 only when the next multixid is assigned.

It doesn't seem to be 19 specific to me?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2026-10-17 08:34:53 Re: Assert failure in standard_join_search()
Previous Message Manu 2026-10-17 07:45:01 pg_upgrade stores an invalid datminmxid/relminmxid when the old cluster's newest multixact is 0xFFFFFFFF