Re: doc pg_constraint.convalidated column description need update

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Robert Treat <rob(at)xzilla(dot)net>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: doc pg_constraint.convalidated column description need update
Date: 2025-06-09 03:59:34
Message-ID: CACJufxGA4MvBSJV03uih6o728ATmUg8-9=1pJUnr6gAwKkTPFw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 5, 2025 at 4:47 AM Robert Treat <rob(at)xzilla(dot)net> wrote:
>
> 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.
>

hi.

<para>
- Scanning a large table to verify a new foreign key or check constraint
+ Scanning a large table to verify new foreign key, check, or not
null constraints
can take a long time, and other updates to the table are locked out
until the <command>ALTER TABLE ADD CONSTRAINT</command> command is
committed. The main purpose of the <literal>NOT VALID</literal>

here, it should be "not-null constraints"?
Other than that, it looks good to me

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2025-06-09 04:06:25 Re: pg_restore - cannot to restore blobs in dictionary format from older pg dumps
Previous Message Michael Paquier 2025-06-09 03:59:20 Replace some %llu remnants in the tree