Re: Configurable location for extension .control files

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Charles <ollie(at)ocharles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Configurable location for extension .control files
Date: 2013-06-04 20:28:47
Message-ID: 20130604202847.GD2678@alap2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-06-04 16:24:07 -0400, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > I don't really care much about Oliver's usecase TBH, but I would very much
> > welcome making it easier for application developers to package part of
> > ther in-database application code as extensions without either requiring
> > a selfcompiled postgres with a custom extension dir or them having have
> > root access to the machine running postgres.
>
> Well, if you're installing an extension that includes C code, you're
> going to need root access anyway to install the shlib (at least on
> conservatively-configured machines). For pure-SQL extensions, Dimitri's
> been pushing a different approach that needn't involve the filesystem at
> all. We didn't get that finished in 9.3 but I think it's still on the
> agenda for 9.4.

Yea, I know of Dimitri's work ;). But I really would like this to work
for C extensions as well. For me personally its no problem at all that
this wouldn't work on conservatively configured machines. Heck, I
*don't* want it to work on production machines. But being able to
configure a dev machine to allow it would be very helpful.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-06-04 20:55:27 Re: pg_rewind, a tool for resynchronizing an old master after failover
Previous Message Oliver Charles 2013-06-04 20:24:43 Re: Configurable location for extension .control files