Fixes a typo in tablecmd
Chao Li <li.evan.chao@gmail.com>
From: Chao Li <li.evan.chao@gmail.com>
To: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-14T23:25:56Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix typo in tablecmds.c
- cd83ed9a91bb 19 (unreleased) landed
Attachments
- v1-0001-Fixes-a-typo-in-tablecmd.patch (application/octet-stream) patch v1-0001
Hi Hackers,
I noticed this while working on a patch with tablecmd:
```
/*
* If the table at either end of the constraint is partitioned, we need to
* recurse and handle every unvalidate constraint that is a child of this
* constraint.
*/
```
Here “unvalidate” looks abnormal to me but not an obvious spelling error.
Then I searched over the source tree, and found two similar occurrences:
Also in tablecmd.c
```
/* an unvalidated constraint is no good */
```
In pg_dump.c
```
/*
* An unvalidated constraint needs to be dumped separately, so
* that potentially-violating existing data is loaded before
* the constraint.
*/
```
Notice the difference: “unvalidate” vs “unvalidated”.
Then I recalled that Tom referred to the online dictionary
https://www.onelook.com for checking typo in discussion [1], and I checked
with the web site. It shows that “unvalidate” is not found; and
“unvalidated” has 3 matches and means “not confirmed as true yet”.
So, I believe “unvalidate” is a typo, a “d” should be appended.
[1] https://postgr.es/m/2118725.1762837193@sss.pgh.pa.us
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/