Re: doc pg_constraint.convalidated column description need update - Mailing list pgsql-hackers

From Robert Treat
Subject Re: doc pg_constraint.convalidated column description need update
Date
Msg-id CAJSLCQ1xjfT_SNvJtE6Yjh6kZQR=0Ps7veQg4sEuFaqrVJyDdQ@mail.gmail.com
Whole thread Raw
In response to Re: doc pg_constraint.convalidated column description need update  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Jun 4, 2025 at 9:37 AM Peter Eisentraut <peter@eisentraut.org> wrote:
> On 03.05.25 17:42, Robert Treat wrote:
> > I actually think this mix of VALID / ENFORCED is a little convoluted
> > for end users, but I don't think the system catalog documentation is
> > the best place to work that out, and I see we've also not added this
> > type of extra information to other columns in the table that have
> > similar restrictions, so I think removing it is the right move.
> >
> > As such, attached patch removes the above, and attempts some clean up
> > of the documentation in ALTER TABLE to better clarify the behavior
> > around valid/not valid, enforced/not enforced, and how it affects
> > different constraints, with some additional literal tag formatting
> > changes.
>
> I committed the catalog.sgml change.  I don't agree with some of the
> other changes, such as changing foreign key to >FOREIGN KEY< etc.  It
> was hard to tell if there were any other changes in there that could be
> considered separately from that.
>

I think some of those changes are worth a second stab, so here is an
updated patch which removes the ancillary tagging and corresponding
line wrappings and focuses just on the wording/grammer improvements;
hopefully it will be easier to make sense of.


Robert Treat
https://xzilla.net

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade: warn about roles with md5 passwords
Next
From: Alexander Korotkov
Date:
Subject: Re: postgres_fdw could deparse ArrayCoerceExpr