Re: [PATCH] Allow bare library names for non-superuser LOAD

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: cca5507 <cca5507(at)qq(dot)com>, solai v <solai(dot)cdac(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Allow bare library names for non-superuser LOAD
Date: 2026-09-09 10:01:26
Message-ID: fbf5df8b-2c09-4153-bcad-c7682686d632@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/09/2026 10:04, cca5507 wrote:
> I think we just need to avoid doing something like this: different libraries
> with the same name.

As a general rule I totally agree with you. I just wonder if it should
be possible in the first place. My point is that we could be trading
server guarantee for admin discipline.

> The behavior of "local_preload_libraries" also like this. So I think it's
> ok if we document the auto expand of "$libdir/plugins/" clearly.

Fair enough.

Thanks!

Best, Jim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeevan Chalke 2026-09-09 10:09:04 Use-after-free of a shared Path in add_path()/add_partial_path()
Previous Message Nazir Bilal Yavuz 2026-09-09 10:00:46 Re: Speed up COPY FROM text/CSV parsing using SIMD