Re: [PG19] pg_upgrade --check passes, then the upgrade fails

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ilmari(at)ilmari(dot)org
Subject: Re: [PG19] pg_upgrade --check passes, then the upgrade fails
Date: 2026-11-08 01:19:34
Message-ID: CAGRkXqTY1nBbebrJ3QTZnWavWjsiqCpw=1YdG7Mo5im4ZORiEA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Masahiko,

Thanks for digging into the older cases.

I started a thread for master in [1]. It tries each stored setting
on the new cluster. That covers both of your examples and Adesh's
GRANT SET case.

[1]
https://postgr.es/m/CAGRkXqRzM-68S9OhtLsTscZ_hhpHhy=ArWCdmp5GxRxo+UBmig@mail.gmail.com

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2026-11-08 01:20:35 Re: First draft of PG 19 release notes
Previous Message shihao zhong 2026-11-08 01:10:24 pg_upgrade --check: catch stored settings the new cluster rejects