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

From: Noah Misch <noah(at)leadboat(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas
Date: 2022-11-30 15:01:36
Message-ID: 20221130150136.GA287291@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Nov 30, 2022 at 08:39:23AM -0500, Robert Haas wrote:
> On Wed, Nov 30, 2022 at 2:07 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > In general, the documentation should prefer simpler decision trees.
>
> True, but I found the current text confusing, which is also something
> to consider.

Could remove the paragraph about v14. Could have that paragraph say
explicitly that the REVOKE is a no-op. Would either of those be an
improvement?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2022-11-30 15:44:12 Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas
Previous Message Robert Haas 2022-11-30 13:39:23 Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas

Browse pgsql-hackers by date

  From Date Subject
Next Message Xing Guo 2022-11-30 15:02:35 pg_regress/pg_isolation_regress: Fix possible nullptr dereference.
Previous Message Alexander Pyhalov 2022-11-30 14:30:45 Re: Partial aggregates pushdown