| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "snaperling(at)gmail(dot)com" <snaperling(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18639: Unexpected behavior with SET ROLE and CREATE ROLE interaction |
| Date: | 2024-09-28 13:43:21 |
| Message-ID: | CAKFQuwZdixpP5uPbfYg69hS2N2re+vsdW+agVOK-d-BCREYW2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, September 27, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18639
> Logged by: Luis Couto
> Email address: snaperling(at)gmail(dot)com
> PostgreSQL version: 16.4
> Operating system: Windows Any
> Description:
>
> I've observed an unexpected behavior when using SET ROLE in combination
> with
> CREATE ROLE in PostgreSQL. I'd like to confirm if this is intended behavior
> or if it's an undocumented side effect.
>
> Yes, this was part of making the usage of the create role attribute more
secure.
See related discussion here:
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2024-09-29 07:49:39 | Re: BUG #18634: Wrong varnullingrels with merge ... when not matched by source |
| Previous Message | PG Bug reporting form | 2024-09-28 11:00:01 | BUG #18641: Logical decoding of two-phase commit fails with TOASTed default values |