| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| 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:24:07 |
| Message-ID: | 3904.1370377447@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Charles | 2013-06-04 20:24:43 | Re: Configurable location for extension .control files |
| Previous Message | Sean Chittenden | 2013-06-04 20:23:21 | Re: Improved error message for CREATE EXTENSION patch... |