2012/10/11 Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>:
> Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
>> I've wanted to allow writing i/o functions in non-C languages for a long
>> time as well, but never got around to do anything about it. Custom datatypes
>> are really powerful, but as soon as you have to write C code, that raises
>> the bar significantly. I/O functions written in, say, PL/pgSQL would be an
>> order of magnitude slower than ones written in C, but for many applications
>> it would be OK.
> Do you want a crazy idea now? Yes, I do mean Yet Another One.
> I'm thinking about what it would take to have a new PL/C language where
> the backend would actually compile and link/load the C code at CREATE
> FUNCTION time, using dynamic code generation techniques.
> That would allow writing functions in C and not have to ship a binary
> executable file on the system, which would solve a bunch of problems.
> With that tool and this use case, you could simply ship inline your C
> coded IO functions in the middle of the PL/pythonu extension, using the
> exact same mechanisms.
> In the more general view of our offerings, that would fix C coded
> extensions for Hot Standby, for one thing.
long time I am thinking about it. I would to use our embedded C - but
replace libpq by SPI. Other idea - compile PL/pgSQL to C - and ...
> Dimitri Fontaine
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-hackers by date
|Next:||From: Andres Freund||Date: 2012-10-11 11:42:29|
|Subject: Re: [RFC][PATCH] wal decoding, attempt #2 - Design Documents (really attached)|
|Previous:||From: Noah Misch||Date: 2012-10-11 11:17:48|
|Subject: Re: September 2012 commitfest|