Re: Today's Postgres Releases break login roles

From: Noah Misch <noah(at)leadboat(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Matthew Woodcraft <matthew(at)woodcraft(dot)me(dot)uk>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Etienne LAFARGE <etienne(dot)lafarge(at)gmail(dot)com>
Subject: Re: Today's Postgres Releases break login roles
Date: 2024-11-25 03:42:51
Message-ID: 20241125034251.28.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Nov 16, 2024 at 03:11:11PM -0500, Tom Lane wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
> > Agreed. I cut some corners by not directly testing that or ALTER DATABASE, so
> > here are some more tests. The output is the same on master @ now, on master @
> > 2024-11-10 (before the regression), and on v12. It reproduces the trouble on
> > master @ 2024-11-12. That's sufficient confirmation for the moment, so I'll
> > hold this until the releases wrap and make it master-only.
>
> If you only intend to apply it to master, there's no need to wait.

True, the delay wasn't obligatory. I pushed it today, for whatever reason.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Aya Iwata (Fujitsu) 2024-11-25 05:54:50 RE: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
Previous Message Tom Lane 2024-11-25 01:27:13 Re: Detection of hadware feature => please do not use signal