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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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: 2025-03-04 15:17:07
Message-ID: CA+TgmobDbNWvc=p8H6ky6voGtzrQJRvwF44x8HGm+nVdqzbeTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 13, 2025 at 12:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2025-03-04 18:56:34 Re: BUG #18830: ExecInitMerge Segfault on MERGE
Previous Message Bertrand Drouvot 2025-03-04 15:05:00 Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string