Re: Avoid leaking system path from pg_available_extensions
Jim Jones <jim.jones@uni-muenster.de>
From: Jim Jones <jim.jones@uni-muenster.de>
To: Matheus Alcantara <matheusssilv97@gmail.com>,
Chao Li <li.evan.chao@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>
Date: 2026-05-22T07:25:54Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid leaking system path from pg_available_extensions
- db5ed03217b9 19 (unreleased) landed
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