Re: glob support in extension_control_path/dynamic_library_path?

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: zsolt(dot)parragi(at)percona(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: glob support in extension_control_path/dynamic_library_path?
Date: 2026-06-25 05:15:09
Message-ID: 20260625.141509.1210296325675941839.horikyota.ntt@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

At Wed, 24 Jun 2026 14:19:33 -0700, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote in
> Security seems to be an interesting question for this.
>
> The current patch simply takes a wildcard, and evaluates it every time
> it is needed. Is that the correct approach? The advantage is that when
> a new directory matching the pattern appears, it is automatically
> detected... but that's also the disadvantage.

I understand the motivation, but I'm also a bit worried about allowing
glob patterns in paths searched for extension files.

Just a thought, but another approach would be to allow symlinks to
extension installation directories either in the existing extension
file search directories or in a separate directory added to the search
path. That would likely require PostgreSQL to recognize a somewhat
different extension file layout than it currently assumes, though.

Regards,

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-06-25 05:15:47 Re: Fix unsafe coding in ResourceOwnerReleaseAll()
Previous Message vignesh C 2026-06-25 05:04:44 Re: Proposal: Conflict log history table for Logical Replication