| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| 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: | 2025-02-21 16:31:09 |
| Message-ID: | 3137106.1740155469@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Thanks for the explanation. That might be worth a comment.
The adjacent comment already says
/*
* Advance command counter so we can see new record; else tests in
* AddRoleMems may fail.
*/
so I didn't see anything to add there. Maybe "We can skip this in
cases where we will not call AddRoleMems"? Or maybe the better answer
is to conclude that the whole idea of not calling
CommandCounterIncrement unconditionally is too fragile and not worth
expending brain cells on, and just rip out the if-test.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-02-21 21:39:40 | Re: Major Version Upgrade failure due to orphan roles entries in catalog |
| Previous Message | Laurenz Albe | 2025-02-21 16:23:24 | Re: Major Version Upgrade failure due to orphan roles entries in catalog |