Re: Add A Glossary

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Jürgen Purtz <juergen(at)purtz(dot)de>
Cc: Roger Harkavy <rogerharkavy(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Add A Glossary
Date: 2020-03-19 02:34:25
Message-ID: CADkLM=fwtE-TCU7sRnvaE74z12kOp_A+CdUwMr7aZt39pXbh6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Fri, Mar 13, 2020 at 12:18 AM Jürgen Purtz <juergen(at)purtz(dot)de> wrote:

>
> The statement that names of schema objects are unique isn't *strictly* true,
> just *mostly* true. Take the case of a unique constraints.
>
> Concerning CONSTRAINTS you are right. Constraints seems to be an exception:
>
> - Their name belongs to a schema, but are not necessarily unique
> within this context:
> https://www.postgresql.org/docs/current/catalog-pg-constraint.html.
> - There is a UNIQUE index within the system catalog pg_constraints: "pg_constraint_conrelid_contypid_conname_index"
> UNIQUE, btree (conrelid, contypid, conname), which expresses that
> names are unique within the context of a table/constraint-type.
> Nevertheless tests have shown that some stronger restrictions exists across
> table-boarders (,which seems to be implemented in CREATE statements - or as
> a consequence of your mentioned correlation between constraint and index ?).
>
> I hope that there are no more such exception to the global rule 'object
> names in a schema are unique':
> https://www.postgresql.org/docs/current/sql-createschema.html
>
> This facts must be mentioned as a short note in glossary and in more
> detail in the later patch about the architecture.
>
>
> I did what I could to address the near uniqueness, as well as incorporate
your earlier edits into this new, squashed patch attached.

Attachment Content-Type Size
0001-add-glossary-page-with-revisions.patch text/x-patch 49.4 KB

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2020-03-19 15:57:04 "Cannot" vs "could not"
Previous Message Bruce Momjian 2020-03-19 00:37:58 Re: Better documentation for row_number() combined with set returning functions

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-03-19 02:38:29 Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side
Previous Message Amit Langote 2020-03-19 02:32:37 Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side