Re: BUG #18639: Unexpected behavior with SET ROLE and CREATE ROLE interaction - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18639: Unexpected behavior with SET ROLE and CREATE ROLE interaction
Date
Msg-id CAKFQuwZdixpP5uPbfYg69hS2N2re+vsdW+agVOK-d-BCREYW2g@mail.gmail.com
Whole thread Raw
In response to BUG #18639: Unexpected behavior with SET ROLE and CREATE ROLE interaction  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Friday, September 27, 2024, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18639
Logged by:          Luis Couto
Email address:      snaperling@gmail.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.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18641: Logical decoding of two-phase commit fails with TOASTed default values
Next
From: Craig Milhiser
Date:
Subject: Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker