Re: Avoid leaking system path from pg_available_extensions

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Avoid leaking system path from pg_available_extensions
Date: 2026-05-22 07:25:54
Message-ID: cf40d36e-e45a-41c2-aea1-7834bcb62da9@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21/05/2026 17:12, Matheus Alcantara wrote:
> I've reproduced the issue and the fix looks correct to me.

same here, +1

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.

Thanks!

Best, Jim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2026-05-22 08:10:41 Re: Prevent setting NO INHERIT on partitioned not-null constraints
Previous Message Chao Li 2026-05-22 07:02:48 Fix pg_get_multixact_stats() members_size calculation