On 04/22/2011 12:06 PM, Tom Lane wrote:
You could possibly lobotomize plpgsql down to a small number of datatypes and operators that are known not to ever do anything more interesting than palloc() and elog(), but IMO the usefulness would be low and the fragility high. It'd be better to give the task to an interpreter that was never built to depend on a SQL environment in the first place. Thus my thought about perl etc.
It's not clear to me what the other interpreter would actually be doing. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
