Re: Today's Postgres Releases break login roles

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

Thank you so much for acknowledging & fixing this so promptly Noah & Tom
!!!

Have a great week both.

Best regards,

-Étienne

On Sat, Nov 16, 2024 at 9:11 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-11-20 15:10:51 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Previous Message PG Bug reporting form 2024-11-20 12:33:41 BUG #18717: ALTER ROLE SET ROLE functionality is broken