Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hüseyin Demir <huseyin.d3r@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
Greg Sabino Mullane <htamfids@gmail.com>,
pgsql-bugs@lists.postgresql.org
Date: 2026-06-25T13:53:25Z
Lists: pgsql-bugs
=?UTF-8?Q?H=C3=BCseyin_Demir?= <huseyin.d3r@gmail.com> writes: >> An alternative answer is to back-patch the putid() fix and teach >> dumputils.c to consider the server minor version when deciding whether >> to reject unquoted all-numeric roles. We don't typically make pg_dump >> pay attention to minor versions, but it would provide a pathway for >> users to deal with this problem: if you've got dangling grants then >> update the old server before dumping. > It will require an almost mandatory minor-version update prior to the > upgrade, which adds extra friction and a more complex upgrade story > for our users since both sides need to be updated. Only if you actually have dangling ACL references, which I think is the case for a vanishingly small set of users --- otherwise we'd have heard more complaints and been motivated to fix this long ago. Let's not optimize for the broken case. regards, tom lane