| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tender Wang <tndrwang(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: not null constraints, again |
| Date: | 2025-04-16 19:55:09 |
| Message-ID: | 2057835.1744833309@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Here's another version where I do skip searching for children twice, and
> rewrote the comments.
v2 LGTM, with two small nits:
1. Grammar feels shaky here:
+ * normal case where we're asked to recurse, this routine ensures that the
+ * not-null constraints either exist already, or queues a requirement for them
+ * to be created by phase 2.
The "either" seems to apply to "ensures" versus "queues", but it's in
the wrong place for that. Maybe something like
+ * normal case where we're asked to recurse, this routine checks if the
+ * not-null constraints exist already, and if not queues a requirement for
+ * them to be created by phase 2.
2. Stupider compilers are likely to whine about the "children"
variable possibly being used uninitialized. Suggest initializing
it to NIL.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2025-04-16 21:24:09 | Re: Built-in Raft replication |
| Previous Message | Konstantin Osipov | 2025-04-16 19:35:34 | Re: Built-in Raft replication |