| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Matthew Woodcraft <matthew(at)woodcraft(dot)me(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-16 18:34:59 |
| Message-ID: | 20241116183459.93.nmisch@google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Nov 16, 2024 at 10:45:46AM -0500, Tom Lane wrote:
> Matthew Woodcraft <matthew(at)woodcraft(dot)me(dot)uk> writes:
> > I noticed one other change with the 14.14 point release, which I think
> > is likely to be related.
> > Previously a command like this would work to select a role immediately after
> > login:
> > psql "options='-crole=foo'"
> > With 14.14 as far as I can tell it has no effect.
>
> Yeah, same issue.
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.
| Attachment | Content-Type | Size |
|---|---|---|
| test-PGOPTIONS-role-v1.patch | text/plain | 9.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-11-16 20:11:11 | Re: Today's Postgres Releases break login roles |
| Previous Message | Tom Lane | 2024-11-16 16:02:58 | Re: BUG #18708: regex problem: (?:[^\d\D]){0} asserts with "lp->nouts == 0 && rp->nins == 0" |