Re: [PG19] pg_upgrade from <= 18 loses the newest multixid if its members end at offset wraparound

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: [PG19] pg_upgrade from <= 18 loses the newest multixid if its members end at offset wraparound
Date: 2026-10-16 03:37:19
Message-ID: CAGRkXqT8V_RTQebEOZsF9q_FQf2A1URU5aG0M9t51=bopG5hXw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Zsolt,

This is rare and hard to hit. But 18 accepts this state, and the
damage only shows up after the upgrade.

Someone told me a story today. If you build a payroll app and it
breaks one time in x, would you ship it? That one time is someone
who does not get paid. A rare bug is still a real bug for whoever
hits it.

So I think it is worth fixing

The patch looks right to me

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-16 03:39:54 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Previous Message shihao zhong 2026-10-16 03:27:01 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client