| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: extension_control_path: ignore empty elements and deduplicate directories |
| Date: | 2026-11-16 16:26:22 |
| Message-ID: | 5glsbkcw3ermvhljzwurzyuw4zvtswbwsmvevud2e7tmxwuyny@iexdkglx6no6 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2026-11-16 13:20:41 -0300, Matheus Alcantara wrote:
> On Mon Nov 16, 2026 at 12:10 PM -03, Andres Freund wrote:
> > I don't like silently ignoring user mistakes. Either we should make it an
> > error or accept it. Which user would be served by silently reinterpreting
> > what they might have meant?
> >
>
> The idea on v6 is that it just discard empty path elements. It doesn't
> mean that the path element will be reinterpreted. So if an user set
> extension_control_path = '$system:' just $system will be used.
>
> We already ignore paths that does not exists, so the idea was to follow
> the same behavior.
I don't think that's the same. A non-existing extension dir could make sense,
e.g. to allow installing extensions from container overlays. And it's not
ignoring the users intent to ignore it, since there obviously aren't
extensions in there. What's the argument for ignoring empty path elements
instead of erroring out?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2026-11-16 16:40:50 | Re: extension_control_path: ignore empty elements and deduplicate directories |
| Previous Message | shihao zhong | 2026-11-16 16:21:28 | Re: Incremental Sort crash on a rescan that becomes bounded |