Peter Eisentraut writes:
> preprepare has an SQL function as entry point, so you don't need to
> preload it.
Well the whole goal of that extension is to autoload itself entirely
server side at connection time. The function API had been made to cope
with 8.3 where it wasn't possible to get a snaps
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
Peter Eisentraut writes:
> local_preload_libraries allows unprivileged users to preload whitelisted
> libraries. session_preload_libraries allows superusers to preload any
> library. It's hard to see how to consolidate those, at least without
> adding another setting that whitelists the librarie
On Sun, 2013-07-07 at 22:50 +0200, Dimitri Fontaine wrote:
> Would it make sense to review the local_preload_libraries semantics
> instead? It looks like session_preload_libraries only adds
> flexibility,
> and that current usages of local_preload_libraries would be served as
> well by the new sett
Peter Eisentraut writes:
> This is like shared_preload_libraries except that it takes effect at
> backend start and can be changed without a full postmaster restart. It
> is like local_preload_libraries except that it is still only settable by
> a superuser. This can be a better way to load modu
On Fri, 2013-06-21 at 11:51 +0200, Dimitri Fontaine wrote:
> I found it strange that those two paras read differently for saying
> the
> same thing?
>
> > +preloaded at connection start. This parameter cannot be
> changed after
> > +the start of a particular session. If a specifi
> Number of new lines added not covered by tests: -107 (Wierd but, it seems
> to have reduced line coverage). But correct me if am not seeing the
> elephant in the room.
>
>
My apologies.
Number of new untested lines: 108
Robins
On 12 June 2013 22:12, Peter Eisentraut wrote:
> This is like shared_preload_libraries except that it takes effect at
> backend start and can be changed without a full postmaster restart. It
> is like local_preload_libraries except that it is still only settable by
> a superuser. This can be a
Hi,
Peter Eisentraut writes:
> This is like shared_preload_libraries except that it takes effect at
> backend start and can be changed without a full postmaster restart. It
> is like local_preload_libraries except that it is still only settable by
> a superuser. This can be a better way to load
This is like shared_preload_libraries except that it takes effect at
backend start and can be changed without a full postmaster restart. It
is like local_preload_libraries except that it is still only settable by
a superuser. This can be a better way to load modules such as
auto_explain.
Since t
10 matches
Mail list logo
