From: Noah Misch <noah@leadboat.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthew Woodcraft <matthew@woodcraft.me.uk>
Cc: pgsql-bugs@lists.postgresql.org, Etienne LAFARGE <etienne.lafarge@gmail.com>
Subject: Re: Today's Postgres Releases break login roles
Date: Sun, 24 Nov 2024 19:42:51 -0800
Message-ID: <20241125034251.28.nmisch@google.com> (raw)
In-Reply-To: <2903185.1731787871@sss.pgh.pa.us>
References: <CADOZwSb0UsEr4_UTFXC5k7=fyyK8uKXekucd+-uuGjJsGBfxgw@mail.gmail.com>
<87iksnsbhx.fsf@golux.woodcraft.me.uk>
<2742790.1731771946@sss.pgh.pa.us>
<20241116183459.93.nmisch@google.com>
<2903185.1731787871@sss.pgh.pa.us>
On Sat, Nov 16, 2024 at 03:11:11PM -0500, Tom Lane wrote:
> Noah Misch <noah@leadboat.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noah@leadboat.com, tgl@sss.pgh.pa.us, matthew@woodcraft.me.uk, etienne.lafarge@gmail.com
Subject: Re: Today's Postgres Releases break login roles
In-Reply-To: <20241125034251.28.nmisch@google.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox