On Feb 18, 2010, at 10:09 AM, Tim Bunce wrote: > It took a depressingly large number of intense hours to work out what > was going on and then more to try to work out a relatively clean solution. > > The underlying problem is in perl and Safe but sadly there's no > reasonable way to fix Safe such that PostgreSQL would work without > changes.
Hrm. I don't have this bug with Safe 3.19, FWIW. Best, David -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
