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

From Peter Eisentraut
Subject Re: doc pg_constraint.convalidated column description need update
Date
Msg-id 673e9806-1849-40c8-9a70-8a3bded3dc81@eisentraut.org
Whole thread Raw
In response to Re: doc pg_constraint.convalidated column description need update  (Robert Treat <rob@xzilla.net>)
List pgsql-hackers
On 09.06.25 16:32, Robert Treat wrote:
> On Mon, Jun 9, 2025 at 12:00 AM jian he <jian.universality@gmail.com> wrote:
>>
>> On Thu, Jun 5, 2025 at 4:47 AM Robert Treat <rob@xzilla.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
> 
> Thanks for taking a look, and yes, I believe you are correct.

committed




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Logrep launcher race conditions leading to slow tests
Next
From: Amit Kapila
Date:
Subject: Re: Conflict detection for update_deleted in logical replication