Re: doc pg_constraint.convalidated column description need update
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Robert Treat <rob@xzilla.net>, jian he <jian.universality@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-06-04T13:37:15Z
Lists: pgsql-hackers
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.
Commits
-
doc: Some copy-editing around constraint validation and enforcement
- 62a47aea1d8d 18.0 landed
-
doc: Update description of pg_constraint.convalidated
- 30c15987d9b7 18.0 landed