database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-31 17:02:12 +03:00
Code Activity

Doc: be more precise about conflicts between relation names.

Browse Source 
Use verbiage like "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." in the reference pages for all
those object types.  The main change here is to mention materialized
views explicitly; although a couple of these pages failed to say
anything at all about name conflicts.

Per suggestion from Daniel Westermann.

Discussion: https://postgr.es/m/ZR0P278MB0920D0946509233459AF0DEFD2889@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM
This commit is contained in:
Tom Lane
2021-11-02 12:12:02 -04:00
parent 65c6cab136
commit af8c580e5c
6 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/create_view.sgml
View File

@@ -52,8 +52,8 @@ CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] [ RECURSIVE ] VIEW <replaceable class
schema. Otherwise it is created in the current schema. Temporary
views exist in a special schema, so a schema name cannot be given
when creating a temporary view. The name of the view must be
distinct from the name of any other view, table, sequence, index or foreign table
in the same schema.
distinct from the name of any other relation (table, sequence, index, view,
materialized view, or foreign table) in the same schema.
</para>
</refsect1>