| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extension Templates S03E11 |
| Date: | 2013-11-26 16:29:02 |
| Message-ID: | 8365.1385483342@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> So, to support uploading PGXN zip files directly within the backend, now
> the backend must be in a position to unpack the archive and build the
> extension, then it must know where the build artefacts are going to be
> found or it needs to `make install` in a known prefix and follow our
> current conventions to find the files.
As I've said multiple times before, this is an absolute nonstarter.
It's insane from a security standpoint, and it requires a whole lot
of infrastructure that wouldn't be there on a production box
(starting with the Postgres header files, but even a C compiler
wouldn't necessarily be there).
What you are looking for is a software distribution channel. A postgres
daemon isn't that and we shouldn't try to make it that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-26 16:29:50 | Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |
| Previous Message | Tom Lane | 2013-11-26 16:22:39 | Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |