From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Pantelis Theodosiou <ypercube(at)gmail(dot)com> |
Cc: | hans(at)matfyz(dot)cz, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: missing schema_name |
Date: | 2021-03-10 19:42:21 |
Message-ID: | 20210310194221.GE16791@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Mar 1, 2021 at 03:29:02PM +0000, Pantelis Theodosiou wrote:
>
>
> On Mon, Mar 1, 2021 at 2:43 PM Pantelis Theodosiou <ypercube(at)gmail(dot)com> wrote:
>
>
>
> On Mon, Mar 1, 2021 at 1:42 PM PG Doc comments form <noreply(at)postgresql(dot)org
> > wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/sql-createschema.html
> Description:
>
> The second and forth syntax for CREATE SCHEMA is missing schema_name.
>
>
> Right. It looks like the 2nd and 4th lines should be removed. The 1st and
> 3rd cover the syntax cases, don't they?
>
>
> Oh, how silly of me. The command
> CREATE SCHEMA AUTHORIZATION role_specification
> creates a schema with same name as role_specification.
>
> It is explained a few lines later:
>
> schema_name
>
> The name of a schema to be created. If this is omitted, the user_name is
> used as the schema name.
So, I assume our docs don't need improvement here.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-03-11 00:49:45 | Re: Jumbled words |
Previous Message | David Steele | 2021-03-10 13:06:16 | Re: Change JOIN tutorial to focus more on explicit joins |