Date: Fri, 15 Nov 2024 20:53:58 -0800
From: Noah Misch <noah@leadboat.com>
To: Etienne LAFARGE <etienne.lafarge@gmail.com>,
	Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Today's Postgres Releases break login roles
Message-ID: <20241116045358.1e.nmisch@google.com>
References: 
 <CADOZwSb0UsEr4_UTFXC5k7=fyyK8uKXekucd+-uuGjJsGBfxgw@mail.gmail.com>
 <2629829.1731714840@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2629829.1731714840@sss.pgh.pa.us>
User-Agent: Mutt/2.2.12 (2023-09-09)
Archived-At: 
 <https://www.postgresql.org/message-id/20241116045358.1e.nmisch%40google.com>
Precedence: bulk

On Fri, Nov 15, 2024 at 06:54:00PM -0500, Tom Lane wrote:
> Etienne LAFARGE <etienne.lafarge@gmail.com> writes:
> > Today, when upgrading from Postgres 15.8 to 15.9, we realized that the
> > login role set for a user (with ALTER USER my_user SET ROLE my_role) was
> > not automatically set upon login any more.
> 
> Right, that was not intended.  We'll fix it next week.

Per https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-november-21-2024-2958/
we're issuing releases next Thursday to fix this and fix a separate ABI break.
I've pushed postgr.es/c/7b88529 for $SUBJECT.  To maximize time-in-buildfarm,
I've pushed it without a public comment period.  I welcome post-commit review,
and I'm happy to amend the change if anyone finds something that would have
been cause for change during a standard opportunity for pre-commit review.
That said, given our wrap schedule, feedback after Saturday is less likely to
change next week's releases.  Such feedback could still affect the 2025-02
releases, of course.

I overlooked this consequence of the 2024-11-14 change.  I apologize.