Re: Major Version Upgrade failure due to orphan roles entries in catalog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Virender Singla <virender(dot)cse(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Aniket Jha <aniketkumarj(at)gmail(dot)com>
Subject: Re: Major Version Upgrade failure due to orphan roles entries in catalog
Date: 2026-02-27 21:22:25
Message-ID: 1103272.1772227345@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> I'd be content to use those wordings (except I think our style
> guide wants detail to be punctuated like a sentence). I'll wait
> a day or so to see if anyone has a better idea, though.

When I looked at the code more closely, I realized that it already
doesn't dump grantors when dumping from pre-v16. I'm inclined to
think that is an overreaction to the possible unreliability of the
data (and from your comment upthread you might agree). But given
the lack of complaints about it, let's leave that as-is for now.
The immediate problem is that the code is allowing a null grantor to
suppress the GRANT altogether, *even if it's not going to use the
grantor*. Clearly that's silly. But if we're not going to use
the grantor, let's skip trying to fetch it, which means we also
don't need the info-level variant of the message.

So I end with the attached draft patch.

regards, tom lane

#text/x-diff; name="v1-clean-up-dumpRoleMembership.patch" [v1-clean-up-dumpRoleMembership.patch] /home/tgl/pgsql/v1-clean-up-dumpRoleMembership.patch

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-02-27 21:28:51 Re: Major Version Upgrade failure due to orphan roles entries in catalog
Previous Message Tom Lane 2026-02-27 18:08:36 Re: pg_get_viewdef() produces non-round-trippable SQL for views with USING join on mismatched integer types