| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 00:43:22 |
| Message-ID: | 20090504004322.GA8098@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Up to now we've always just dismissed the above possibility as
> "superusers should know better", but I think there's a reasonable case
> to be made that this is an obvious failure mode and we should put a bit
> more effort into being robust against it. With more and more external
> code being routinely run in the backend, who wants to swear that there
> is no "exit(1)" in the guts of libperl or libxml or whatever?
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-04 01:11:58 | Re: windows doesn't notice backend death |
| Previous Message | Tom Lane | 2009-05-03 23:17:09 | Re: pg_resetxlog bug? |