回复: Correct comment wording in extension.c - Mailing list pgsql-hackers

From li carol
Subject 回复: Correct comment wording in extension.c
Date
Msg-id KL1PR01MB6662DF8D45EB58001065FB458182A@KL1PR01MB6662.apcprd01.prod.exchangelabs.com
Whole thread Raw
In response to Re: Correct comment wording in extension.c  (albert tan <alterttan1223@gmail.com>)
Responses Re: Correct comment wording in extension.c
List pgsql-hackers

>On Wed, Jan 7, 2026 at 1:13PM albert tan <alterttan1223@gmail.com> wrote:
>Hi Join,
>Thanks for pointing out extra issues. I have addressed them in v2.

 

Hi Albert, John,

 

In addition to the previous findings, I went through src/backend/commands/extension.c again and identified other spots that need adjustment for better clarity and grammar.

In the header for find_in_paths:

/*

* Work in a very similar way with find_in_path but it receives an already

* parsed List of paths to search the basename and it do not support macro

* replacement or custom error messages (for simplicity).

*

* By "already parsed List of paths" this function expected that paths already

* have all macros replaced.

*/

 

This should be corrected to:

"Works in a very similar way to find_in_path, but it receives an already parsed List of paths to search the basename, and it does not support macro replacement or custom error messages (for simplicity). By 'already parsed List of paths' this function expects that the paths already have all macros replaced."

 

I hope this helps in making the file more consistent.

 

Best regards,

Yuan Li(carol)

pgsql-hackers by date:

Previous
From: Yuefei Shi
Date:
Subject: Re: Pasword expiration warning
Next
From: Chao Li
Date:
Subject: Re: Refactor replication origin state reset helpers