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-25 10:51:57 |
Message-ID: | 673e9806-1849-40c8-9a70-8a3bded3dc81@eisentraut.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09.06.25 16:32, Robert Treat wrote:
> On Mon, Jun 9, 2025 at 12:00 AM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>>
>> 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
>
> Thanks for taking a look, and yes, I believe you are correct.
committed
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2025-06-25 11:26:41 | Re: Conflict detection for update_deleted in logical replication |
Previous Message | Nazir Bilal Yavuz | 2025-06-25 10:45:59 | Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson |