| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | "Sofer, Yuval" <Yuval_Sofer(at)bmc(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Postgres 9.2.8 crash sporadically on Windows |
| Date: | 2014-04-07 15:39:01 |
| Message-ID: | 19447.1396885141@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-04-07 11:15:32 -0400, Tom Lane wrote:
>> The "exit code 0" bit reminds me of this:
>>
>> http://www.postgresql.org/message-id/21027.1393546453@sss.pgh.pa.us
>>
>> Is there another exit report for the same PID just above the quoted log
>> extract? Because if there isn't, the postmaster shouldn't be thinking
>> that status 0 represents a crash.
> Wouldn't a pl or library doing a exit(0); cause exactly that, because it
> will still be in PM_CHILD_ASSIGNED?
Oh, hm, that's a possibility, if the OP is using any untrusted PLs.
As you say, we lack sufficient context.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Souheila Hechaichi | 2014-04-07 16:03:42 | Postgres resources not released after call PQclear |
| Previous Message | Tom Lane | 2014-04-07 15:25:31 | Re: BUG #9896: Bug in FULL OUTER JOIN |