| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: windows doesn't notice backend death |
| Date: | 2009-05-04 01:11:58 |
| Message-ID: | 6678.1241399518@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-04 01:30:20 | Re: unchecked out of memory in postmaster.c |
| Previous Message | Alvaro Herrera | 2009-05-04 00:43:22 | Re: windows doesn't notice backend death |