On Wed, Jun 3, 2009 at 11:54 PM, Andrew Dunstan <and...@dunslane.net> wrote: > > > Update: the problem is apparently occurring during the call to perl_parse() > in plperl_init_interp(). >
Not sure if you saw the previous thread on this, but here's a backtrace that gives some more detail: http://archives.postgresql.org/pgsql-bugs/2009-05/msg00198.php -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers