| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, 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-12-02 20:17:16 |
| Message-ID: | 20131202201716.GM17272@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David,
* David E. Wheeler (david(at)justatheory(dot)com) wrote:
> On Dec 2, 2013, at 6:14 AM, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> wrote:
>
> > Whether you're targetting a file system template or a catalog template,
> > PGXN is not a complete solution, you still need to build the extension.
>
> This is true today, but only because PostgreSQL provides the infrastructure for building and installing extensions that entails `make && make install`. If Postgres provided some other method of building and installing extensions, you could start using it right away on PGXN. The *only* requirement for PGXN distributions, really, is a META.json file describing the extension.
Thanks, that's a pretty interesting point.. I like the idea that we
could provide a new make target which could build an 'inline extension'
(or what-have-you) which could then be distributed and used by users
either directly or with some client-side tool.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-12-02 20:17:30 | Re: Extension Templates S03E11 |
| Previous Message | Tom Lane | 2013-12-02 20:17:13 | Re: Trust intermediate CA for client certificates |