Re: Major Version Upgrade failure due to orphan roles entries in catalog - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Major Version Upgrade failure due to orphan roles entries in catalog
Date
Msg-id CA+TgmobDbNWvc=p8H6ky6voGtzrQJRvwF44x8HGm+nVdqzbeTw@mail.gmail.com
Whole thread Raw
In response to Re: Major Version Upgrade failure due to orphan roles entries in catalog  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Feb 13, 2025 at 12:07 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The code the attached patch is touching is from commit 6566133c5.
> I'm not going to blame the bug on that commit, because before that
> we had dependencies on *zero* of the three roles; at least it added
> one on the grantor.  But I'm wondering whether Robert thought about
> the other two roles and explicitly rejected making dependencies
> for them, and if so why.

For some reason, I came to the conclusion that it wasn't needed.
Apparently, that was incorrect.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-bugs by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
Next
From: Dean Rasheed
Date:
Subject: Re: BUG #18830: ExecInitMerge Segfault on MERGE