Re: Correct comment wording in extension.c

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: li carol <carol(dot)li2025(at)outlook(dot)com>, albert tan <alterttan1223(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Correct comment wording in extension.c
Date: 2026-01-13 05:40:57
Message-ID: CANWCAZaqNd3Lc8YumUE05A-ybxB4dUCXT7dOP7Fr-+drBrR5kA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 11, 2026 at 11:58 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> v4-0001 looks good to me.

When I say I'm going to commit "unless/barring", no response is
necessary unless there is a problem.

> I just went through extension.c and got a few more comment improvements. I put them in v5-0002, please take a look.

- * for them therefore uses about O(N^2) time when there are N versions of
+ * for them therefore uses O(N^2) time when there are N versions of

- /* store the OID of the namespace to-be-changed */
+ /* store the OID of the namespace to be changed */

Please read these responses to you from last week:

https://www.postgresql.org/message-id/1909358.1767854695%40sss.pgh.pa.us
https://www.postgresql.org/message-id/7k27ut6kugt2mizo5cy5wplbbrz4ccbkxvsc2iqu5yde344iya%40dxktdjw6uvi2

I've pushed v4.

--
John Naylor
Amazon Web Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2026-01-13 05:46:57 Re: Optimize LISTEN/NOTIFY
Previous Message shveta malik 2026-01-13 05:34:06 Re: [Patch] add new parameter to pg_replication_origin_session_setup