| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc pg_constraint.convalidated column description need update |
| Date: | 2025-06-04 13:37:15 |
| Message-ID: | 4591b2f3-d55b-453b-ae03-8ad46ac32882@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-06-04 13:43:15 | Re: ABI Compliance Checker GSoC Project |
| Previous Message | Fujii Masao | 2025-06-04 13:18:36 | Re: Speedup truncations of temporary relation forks |