Skip site navigation (1) Skip section navigation (2)

Re: replace plugins directory with GUC

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: replace plugins directory with GUC
Date: 2013-01-15 12:04:52
Message-ID: 1358251492.401.5.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
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 not clear who decides what to put in there (plugin
> author,
> packager, DBA?), how to put it there (move it, copy it, symlink it? --
> no support in pgxs), and based on what criteria.
> 
> 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.

There are obviously some conflict/transition issues with using
user_loadable_libraries vs the plugins directory.  I have tried to
explain the mechanisms in the documentation, but there are other choices
possible in some situations.


Attachment: pg-user-loadable-libraries.patch
Description: text/x-patch (8.1 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2013-01-15 12:53:21
Subject: Re: pg_ctl idempotent option
Previous:From: Andres FreundDate: 2013-01-15 11:36:25
Subject: Re: [PATCH] Compile without warning with gcc's -Wtype-limits, -Wempty-body

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group