Re: Where to load modules from?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Where to load modules from?
Date: 2013-09-19 17:54:41
Message-ID: CA+TgmoaP5AS6Jes+ZZtAew-Km0e3wJgWQJon9aYbevV7SzLWrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 18, 2013 at 12:53 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2013-09-18 08:46:08 -0400, Robert Haas wrote:
>> Here's another idea. At initdb time, create an empty directory called
>> called pg_you_can_load_stuff_from_here (pick a better name) inside
>> $PGDATA. Allow it to be replaced with a symlink. This would be
>> similar to what we do today with pg_xlog. In fact, you can imagine an
>> equivalent of initdb -X that does something precisely analogous. This
>> feels a bit more natural to me than a GUC.
>
> I think I'd prefer a GUC that allows specifying multiple directories
> that are searched in order to a single symlinked directory.

Why?

I ask because I have the opposite preference, based on the precedent of pg_xlog.

> Also, aren't "symlinks" an absolute PITA to manipulate by hand on
> windows?

Maybe so, but if that's an issue here it's a preexisting issue also.
I think we shouldn't burden this patch with fixing it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2013-09-19 18:09:58 Re: Not In Foreign Key Constraint
Previous Message Robert Haas 2013-09-19 17:51:54 Re: Dead code or buggy code?