From: Tom Lane <tgl@sss.pgh.pa.us>
To: buck@dbrhino.com
cc: pgsql-docs@postgresql.org
Subject: Re: Document PUBLIC grants on PUBLIC schema
In-reply-to: <20170930141856.28561.80812@wrigleys.postgresql.org>
References: <20170930141856.28561.80812@wrigleys.postgresql.org>
Comments: In-reply-to buck@dbrhino.com
	message dated "Sat, 30 Sep 2017 14:18:56 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12402.1507043533.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 03 Oct 2017 11:12:13 -0400
Message-ID: <12403.1507043533@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

buck@dbrhino.com writes:
> The GRANT documentation, regarding the PUBLIC role, says:

> &gt; No privileges are granted to PUBLIC by default on tables, columns, s=
chemas
> or tablespaces.

> But the PUBLIC role does receive USAGE and CREATE privileges on the PUBLIC
> schema, correct? I think the documentation should point this out.

The GRANT page is meant to explain what happens when you create new
objects.  It does not attempt to explain the privileges attached to every
predefined object, and that seems like a rather impractical thing to do
there.  We tend to document nondefault privileges for built-in objects
where those objects are described.  In the case of the public schema,
it's described here:

https://www.postgresql.org/docs/current/static/ddl-schemas.html#DDL-SCHEMAS=
-PUBLIC

but since privileges for schemas haven't been mentioned at that point,
the issue is taken up a little further down:

https://www.postgresql.org/docs/current/static/ddl-schemas.html#DDL-SCHEMAS=
-PRIV

			regards, tom lane


--=20
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs