Re: server crash with "process 22821 releasing ProcSignal slot 32, but it contains 0" - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: server crash with "process 22821 releasing ProcSignal slot 32, but it contains 0"
Date
Msg-id 1344902992.8485.8.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: server crash with "process 22821 releasing ProcSignal slot 32, but it contains 0"  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-bugs
On Thu, 2012-08-09 at 16:26 -0500, Merlin Moncure wrote:
> Follow up on this.  It is pl/sh and it is a newline issue: one of the
> developers is using a tool (I think pgadmin?) that is sticking \r
> characters at the end of every line which is throwing off pl/sh's
> shebang parsing.  The issuing query gets an error along the lines of
> 'could not exec' and the server goes belly up if there is significant
> concurrent load when that's issued.  This is an out of date pl/sh, so
> I'm going to upgrade it and try and reproduce. If I still can, I'll
> supply a test case.

I had received an independent report of this cr/lf issue and fixed it
now.  But that doesn't explain why the server would crash.

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: Possible Bug in 9.2beta3
Next
From: exclusion@gmail.com
Date:
Subject: BUG #7493: Postmaster messages are unreadable in a Windows console