| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | kelan <ke_lan1(at)qq(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix typo in code comment |
| Date: | 2026-01-04 09:24:12 |
| Message-ID: | 8566AA4A-54CA-4DD4-9CEA-5B6A22CED4D8@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Dec 31, 2025, at 09:10, kelan <ke_lan1(at)qq(dot)com> wrote:
>
> Hi hickers,
> I fixed a comment error in the `WaitForParallelWorkersToFinish` function. The original comment was "In that case, or latch should have been set as well...", where I think "or" is a typo and it should be "our".
>
> --
> Best regards,
> Ke Lan
> Email:ke_lan1(at)qq(dot)com
>
> <v1-0001-correct-typos-in-the-code-comments.patch>
Looking at the context, “or” doesn’t make sense here. Both “the” and “our” would work grammatically, and given the intent of the comment, “our” seems the most likely original wording.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-01-04 09:46:06 | Re: WIP - xmlvalidate implementation from TODO list |
| Previous Message | David Rowley | 2026-01-04 09:20:00 | Re: Small optimization set tuple block/tableOid once |