So while hacking away at the PLs-as-extension changes I ran across an unforeseen complication. plperl and plpython use the same C function entry points for both their trusted and untrusted variants. This is problematic for making them into extensions, since we need the two language variants to be different extensions (else you could not install just one of them) and the extensions can't both own the same handler function.
I can imagine that someplace down the road we might want to allow multiple extensions to own the same SQL object; I know that RPMs can share ownership of files, for comparison. But today is not that day. The only easy fix I can see at the moment is to arbitrarily create two pg_proc entries --- they can both point at the same C function, but there need to be two of 'em. Anyone have a different answer? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers