Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Fix typo in code comment
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: <tencent_38B5875E2D440C8DA8C0C022ABD999F9C207@qq.com>
Date: Sun, 4 Jan 2026 17:24:12 +0800
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8566AA4A-54CA-4DD4-9CEA-5B6A22CED4D8@gmail.com>
References: <tencent_38B5875E2D440C8DA8C0C022ABD999F9C207@qq.com>
To: kelan <ke_lan1@qq.com>
Archived-At: <https://www.postgresql.org/message-id/8566AA4A-54CA-4DD4-9CEA-5B6A22CED4D8%40gmail.com>
Precedence: bulk


> On Dec 31, 2025, at 09:10, kelan <ke_lan1@qq.com> wrote:
>=20
> 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".
>=20
> --
> Best regards,
> Ke Lan
> Email:ke_lan1@qq.com
>=20
> <v1-0001-correct-typos-in-the-code-comments.patch>

Looking at the context, =E2=80=9Cor=E2=80=9D doesn=E2=80=99t make sense =
here. Both =E2=80=9Cthe=E2=80=9D and =E2=80=9Cour=E2=80=9D would work =
grammatically, and given the intent of the comment, =E2=80=9Cour=E2=80=9D =
seems the most likely original wording.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/