Alvaro Herrera <alvhe...@commandprompt.com> writes:
> FWIW there is (or there was, last time I looked) an exit(1) call in the
> guts of the PHP library that PL/php uses, which is triggered when the
> memory used goes over the configured memory limit. It was very easily
> triggered with some of the test functions we had on our regression
> tests, and the only solution was to kludge up the limit.
I don't think we'll be able to prevent PHP from doing that :-(. But
it now seems clear that we should try to make the database as a whole
recover with some degree of grace. I'll go work up a patch.
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
