Horton
Menu

Re: Dumping an Extension's Script

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnakangas@vmware.com>, Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2012-12-05T20:43:56Z
Lists: pgsql-hackers 
Andres Freund escribió:
> On 2012-12-05 21:16:52 +0100, Dimitri Fontaine wrote:

> > Now if we can't fix the executable files situation, what about making
> > the C coded extensions not require an executable anymore? I'm thinking
> > about studying what it would take exactly to write a PL/C where the
> > PostgreSQL backend would basically compile the embedded C code at CREATE
> > FUNCTION time and store bytecode or binary in the probin column.

> Imo thats not a sensible thing to pursue.

+1.  Certainly a pg_dump patch's thread is not the place to propose it.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services