| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, 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 18:22:56 |
| Message-ID: | E7D2495C-BB4B-4BDE-A07B-82C44F0C0F6C@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-12-02 18:24:18 | Re: [GENERAL] pg_upgrade ?deficiency |
| Previous Message | Andres Freund | 2013-12-02 18:19:10 | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |