Re: Docs: Create table description for constraints markup fix and label tweaks - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Docs: Create table description for constraints markup fix and label tweaks
Date
Msg-id CAKFQuwYda2RwHdzwbz3FcMs_2kaKn7skpuPzAd15h5DH1LfzQg@mail.gmail.com
Whole thread Raw
In response to Docs: Create table description for constraints markup fix and label tweaks  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Fri, Apr 3, 2026 at 10:18 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
Responding to a recent report on -general [1] I found a markup bug in the primary key description under create table.  0001 fixes this.

The complaint itself was about using "column constraint" as a descriptive label in a syntax area when "column constraint" is an actual defined syntax label.  0002 adds the word "variant" to the six places "(table/column constraint)" is used in this manner.



The more you look (not having production dark mode in the core build is a bit annoying)...v2 attached after re-reading the original thread and looking around a bit more.

Unique had the same sgml markup error as primary key.

 
David J.

P.S. Reviewing this we are inconsistent as to where we use "optional" markup versus just literal [ ].  Even among these three locations there are variances - and simply literals used for optional meaning brackets.

Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Changing the state of data checksums in a running cluster
Next
From: "David G. Johnston"
Date:
Subject: Docs: Distinguish table and index storage parameters in CREATE TABLE