From: Peter Eisentraut <peter@eisentraut.org>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: jian he <jian.universality@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: create table explicitly mention that unique|primary key constraint will create an
Date: Wed, 31 Jan 2024 12:15:31 +0100
Message-ID: <1bcaae7c-a643-4e29-836a-974941941e91@eisentraut.org> (raw)
In-Reply-To: <CAKFQuwZDggN=qaKt3N5rTaiRuzsWhgvF53cCBe+Bm4vFiyt5fQ@mail.gmail.com>
References: <CACJufxFG682tYcP9aH_F-jrqq5End8MHZR77zcp1=DUrEsSu1Q@mail.gmail.com>
<24f01200b651ff87311ae0f46b99eaf91fc3ec43.camel@cybertec.at>
<f0f2ecbc-3237-4cf7-8fb3-b8eb2b039bf8@eisentraut.org>
<CAKFQuwZDggN=qaKt3N5rTaiRuzsWhgvF53cCBe+Bm4vFiyt5fQ@mail.gmail.com>
On 18.01.24 22:21, David G. Johnston wrote:
> I started looking at this specific item and immediately got the idea to
> actually document in user-facing (i.e., not system catalogs) what these
> object categories are in which object types share the schema namespace.
> The "Other Object Types" section already in the DDL chapter seems to
> provide a near-perfect place to put this (not sure I like the word
> "other" there being my only complaint). The attached patch replaces
> Laurenz's v1, leaving the create_table changes as-is but presenting an
> alternative approach to introducing namespacing when we explain why
> schemas exist.
I think this proposal goes a bit too far into implementation-dependent
details. The namespace of tables and indexes is clearly important, but
for example, the subdivision of types into range types and multi-range
types is really low-level and not usually practically relevant. And you
don't mention array types, probably because they are not mentioned in
typtype, but they are also relevant for the namespace of types. There
are multiple ways to slice all this, but it's not clear why we need to
lay this all out in the introductory documentation.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter@eisentraut.org, david.g.johnston@gmail.com, laurenz.albe@cybertec.at, jian.universality@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: create table explicitly mention that unique|primary key constraint will create an
In-Reply-To: <1bcaae7c-a643-4e29-836a-974941941e91@eisentraut.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox