| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Etienne LAFARGE <etienne(dot)lafarge(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Today's Postgres Releases break login roles |
| Date: | 2024-11-16 04:53:58 |
| Message-ID: | 20241116045358.1e.nmisch@google.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Nov 15, 2024 at 06:54:00PM -0500, Tom Lane wrote:
> Etienne LAFARGE <etienne(dot)lafarge(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-11-16 06:50:10 | BUG #18712: inet value ::2 handling goes not as expected |
| Previous Message | Danish Hajwane | 2024-11-16 04:29:47 | Re: Libpq library error when doing physical Replication |