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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas
Date: 2021-12-17 19:57:08
Message-ID: 1375351.1639771028@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Noah Misch <noah(at)leadboat(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2021-12-17 21:22:41 pgsql: Fix the public schema's permissions in a separate test script.
Previous Message Noah Misch 2021-12-17 19:47:20 Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-12-17 20:04:19 Re: make tuplestore helper function
Previous Message Tom Lane 2021-12-17 19:53:46 Re: WIP: WAL prefetch (another approach)