Subject: Re: Be more clear what names can be used for tables with "CREATE
 TABLE"?
To: pgsql-docs@lists.postgresql.org
References: 
 <ZR0P278MB0920D0946509233459AF0DEFD2889@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM>
From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
Message-ID: <998c5708-95f9-d58f-4480-5890b56138f7@purtz.de>
Date: Sat, 30 Oct 2021 17:27:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: 
 <ZR0P278MB0920D0946509233459AF0DEFD2889@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM>
Content-Type: multipart/alternative;
 boundary="------------4F9133AE6D21B5D535857D43"
Content-Language: en-US
Archived-At: 
 <https://www.postgresql.org/message-id/998c5708-95f9-d58f-4480-5890b56138f7%40purtz.de>
Precedence: bulk

This is a multi-part message in MIME format.
--------------4F9133AE6D21B5D535857D43
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

a) Don't forget: constraint, function, procedure, trigger.

b) The hint applies to each of such objects: CREATE 
[TABLE|VIEW|FUNCTION|...]. To avoid such redundancy we could extend and 
clarify the definition of 'SQL object / local object / global object' 
within the glossary and refer to it.

c) In general we have 3 levels (namespaces) where object names are 
unique across the same or different types.

  * cluster-level: database name, tablespace, replication origin,
    subscription for logical replication, role, ...?
  * database-level: schema, extension, collation, data type cast, ...?
  * schema-level: table, index, view, materialized view, foreign table,
    sequence, constraint, function, procedure, trigger, operator, ...?

--

Jürgen Purtz


--------------4F9133AE6D21B5D535857D43
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>a) Don't forget: constraint, function, procedure, trigger.</p>
    <p>b) The hint applies to each of such objects: CREATE
      [TABLE|VIEW|FUNCTION|...]. To avoid such redundancy we could
      extend and clarify the definition of 'SQL object / local object /
      global object' within the glossary and refer to it.</p>
    <p>c) In general we have 3 levels (namespaces) where object names
      are unique across the same or different types. <br>
    </p>
    <ul>
      <li>cluster-level: database name, tablespace, replication origin,
        subscription for logical replication, role, ...?<br>
      </li>
      <li>database-level: schema, extension, collation, data type cast,
        ...?<br>
      </li>
      <li>schema-level: table, index, view, materialized view, foreign
        table, sequence, constraint, function, procedure, trigger,
        operator, ...?</li>
    </ul>
    <p>--<br>
      <br>
      Jürgen Purtz <br>
      <br>
    </p>
  </body>
</html>

--------------4F9133AE6D21B5D535857D43--