On 7/8/13 4:37 AM, Dimitri Fontaine wrote: >> I don't know of any actual legitimate uses of local_preload_libraries. >> I recall that the plpgsql debugger was meant to use it, but doesn't >> anymore. So it's hard to judge what to do about this, without any >> actual use cases. > > Well there's my preprepare thing at > > https://github.com/dimitri/preprepare
preprepare has an SQL function as entry point, so you don't need to preload it. > I don't think that the whitelisting is actually used in a way to allow > for non superusers to load modules in the field, because the only way to > do that with local_preload_libraries that I know of is to edit the > postgresql.conf file and reload. > > alter role dim set local_preload_libraries = 'auto_explain'; > ERROR: 55P02: parameter "local_preload_libraries" cannot be set after > connection start I think the idea was to use PGOPTIONS to load it, controlled by the client side. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
