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

Re: replace plugins directory with GUC

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: replace plugins directory with GUC
Date: 2012-10-11 09:19:34
Message-ID: m2y5jd5psp.fsf@2ndQuadrant.fr (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> 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 include directory in postgresql.conf). But
> actually, you can't, because there's no way to append to a setting, you can
> only override. That's an obvious missing feature in the include mechanism.
> Even ignoring the plugins directory, it would be nice to be able to append
> libraries to shared_preload_libraries.

I think we need a += operator in the configuration file, complementing
the = we have now, and defined so that when the setting is not yet
defined it's a bare =.

And I think this plugins thing needs to be revisited, yes.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


In response to

pgsql-hackers by date

Next:From: Sébastien LardièreDate: 2012-10-11 09:22:05
Subject: Re: Truncate if exists
Previous:From: Etsuro FujitaDate: 2012-10-11 09:10:58
Subject: Re: FDW for PostgreSQL

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