From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Be more clear what names can be used for tables with "CREATE TABLE"? |
Date: | 2021-11-01 16:04:16 |
Message-ID: | 1139298.1635782656@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Sat, 2021-10-30 at 11:08 +0000, Daniel Westermann (DWE) wrote:
>> in the documentation for CREATE TABLE we have this sentence:
>> "The name of the table must be distinct from the name of any other table, sequence, index, view, or foreign table in the same schema."
>> At least materialized views are missing:
> Technically speaking, it is "objects stored in pg_class".
We use "relation" for that concept in the code, and I believe that
that terminology is also used in the manual. I'm inclined to propose
"The name of the table must be distinct from the name of any other
relation (table, sequence, index, view, materialized view, or foreign
table) in the same schema."
I think the existing wording might be that way because somebody
figured that "view" could subsume "materialized view". Which
isn't an unreasonable position, but we haven't done it like that
consistently.
I don't think we need to be similarly exhaustive about enumerating
the kinds of types that there are.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2021-11-02 07:22:31 | initdb: nothing about template0 |
Previous Message | PG Doc comments form | 2021-11-01 13:23:01 | Empty values of pg_stats_ext when table is empty |