| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: make ALTER DOMAIN VALIDATE CONSTRAINT no-op when constraint is validated |
| Date: | 2025-10-10 14:42:42 |
| Message-ID: | CACJufxFCzKNqJGwYFHoXskiGnO-uP7E7kiMn6yeZReJ16dG3mw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 21, 2025 at 2:49 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> hi.
>
> Looking at AlterDomainValidateConstraint, it seems currently, ALTER
> DOMAIN VALIDATE
> CONSTRAINT will re-validate a VALID constraint, which
> would just waste cycles.
> Ideally, this operation should be a no-op.
>
> The attached patch addresses this by making ALTER DOMAIN VALIDATE CONSTRAINT a
> no-op in such cases.
>
> ALTER TABLE VALIDATE CONSTRAINT is already a no-op when the constraint is VALID.
hi.
simple rebase.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-make-ALTER-DOMAIN-VALIDATE-CONSTRAINT-no-op-when-constraint-is-va.patch | text/x-patch | 3.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-10-10 15:22:46 | [PATCH] Remove make_temptable_name_n() |
| Previous Message | ls7777 | 2025-10-10 14:19:58 | Re: Patch for migration of the pg_commit_ts directory |