Horton

Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-committers@lists.postgresql.org
Date: 2021-12-17T19:57:08Z
Lists: pgsql-hackers 
Noah Misch <noah@leadboat.com> writes:
> On Fri, Dec 17, 2021 at 01:41:00PM -0500, Tom Lane wrote:
>> If we're thinking of a generalized setup file, putting it after the
>> tablespace test feels pretty weird.  What was your motivation for
>> doing this at the end of tablespace.source rather than the start?

> I did it that way so a bit of the "make check" suite would exercise the
> standard user experience.  That's a minor concern, so putting the setup file
> before the tablespace file is fine.  Various contrib and TAP suites will still
> test the standard user experience.

Check.  I'll make it so in a little bit.

			regards, tom lane

Commits

  1. Doc: word-smith the discussion of secure schema usage patterns.

  2. Fix the public schema's permissions in a separate test script.

  3. Revoke PUBLIC CREATE from public schema, now owned by pg_database_owner.