Re: pgsql: Add new GUC createrole_self_grant. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgsql: Add new GUC createrole_self_grant.
Date
Msg-id CA+Tgmoauqd1cHQjsNEoxL5O-kEO4iC9dAPyCudSvmNqPJGmy9g@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add new GUC createrole_self_grant.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: pgsql: Add new GUC createrole_self_grant.  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Wed, Jan 11, 2023 at 7:53 PM David G. Johnston
<david.g.johnston@gmail.com> wrote:
> Justed wanted to chime in and say Robert has eloquently put into words much of what I have been thinking here, and
thatI concur that guiding the DBA to use care with the power they have been provided is a sane position to take.
 
>
> +1, and thank you.

Thanks!

Here's a patch. In it I make three changes, only one of which is
directly relevant to the topic at hand:

1. Add a sentence to the documentation on writing SECURITY FUNCTIONS
safely concerning createrole_self_grant.
2. Add a sentence to the documentation on SECURITY DEFINER referring
to the section about writing such functions safely.
3. Remove a note discussing the fact that pre-8.3 versions did not
have SET clauses for functions.

I can separate this into multiple patches if desired. And of course
you, Tom, or others may have suggestions on which of these changes
should be included at all or how to word them better.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: Improving btree performance through specializing by key shape, take 2
Next
From: Xing Guo
Date:
Subject: PL/Python: Fix return in the middle of PG_TRY() block.