Re: Avoid leaking system path from pg_available_extensions - Mailing list pgsql-hackers

From Matheus Alcantara
Subject Re: Avoid leaking system path from pg_available_extensions
Date
Msg-id 87c8f8ac-614b-4679-afc7-f591b76c8ff7@gmail.com
Whole thread
In response to Re: Avoid leaking system path from pg_available_extensions  (Jim Jones <jim.jones@uni-muenster.de>)
Responses Re: Avoid leaking system path from pg_available_extensions
List pgsql-hackers
On 22/05/26 04:25, Jim Jones wrote:
> On 21/05/2026 17:12, Matheus Alcantara wrote:
>> I've reproduced the issue and the fix looks correct to me.
> 
> same here, +1
> 

Thank you for also testing.

> I was wondering if creating a constant for it would be, stylistically
> speaking, a cleaner solution. For instance:
> 
> #define EXTENSION_SYSTEM_MACRO  "$system"
> 
> I realize that it's used only inside get_extension_control_directories()
> but since it is even mentioned in the docs, I guess it wouldn't be a bad
> idea.
> 

I'm not against it but I don't think that it's necessary since as you 
mention, only get_extension_control_directories() use.

--
Matheus Alcantara
EDB: https://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Prevent setting NO INHERIT on partitioned not-null constraints
Next
From: Tom Lane
Date:
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?