On 1/15/13 7:04 AM, Peter Eisentraut wrote:
>> It would seem to be much more in the spirit of things to simply list
>> > the
>> > allowed plugins in a GUC variable, like
>> >
>> > some_clever_name_here = $libdir/this, $libdir/that
> Here is a patch, with some_clever_name = user_loadable_libraries
2013/1/15 Peter Eisentraut :
> On Tue, 2012-10-09 at 20:45 -0400, Peter Eisentraut wrote:
>> About that plugins directory ($libdir/plugins) ... I don't think we
>> ever
>> really got that to work sensibly. I don't remember the original
>> design
>> discussion, but I have seen a number of explanati
Peter Eisentraut writes:
> Here is a patch, with some_clever_name = user_loadable_libraries.
Shouldn't user_loadable_libraries be PGC_SUSET? PGC_SIGHUP is typically
used when the same setting must apply in all active sessions, but it's
not clear why such a restriction must be made for this.
On Tue, 2012-10-09 at 20:45 -0400, Peter Eisentraut wrote:
> About that plugins directory ($libdir/plugins) ... I don't think we
> ever
> really got that to work sensibly. I don't remember the original
> design
> discussion, but I have seen a number of explanations offered over the
> years. It's
Heikki Linnakangas writes:
> Now that we support include-directories in postgresql.conf, you could put a
> "mylib.conf" file in the include directory that contains the above line, if
> you want to enable/disable a module just by moving things around in the
> filesystem (after configuring an includ
On 10.10.2012 03:45, Peter Eisentraut wrote:
About that plugins directory ($libdir/plugins) ... I don't think we ever
really got that to work sensibly. I don't remember the original design
discussion, but I have seen a number of explanations offered over the
years. It's not clear who decides wh
