| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: server crash with "process 22821 releasing ProcSignal slot 32, but it contains 0" |
| Date: | 2012-08-14 00:09:52 |
| Message-ID: | 1344902992.8485.8.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | exclusion | 2012-08-14 10:13:15 | BUG #7493: Postmaster messages are unreadable in a Windows console |
| Previous Message | Greg Stark | 2012-08-13 23:02:34 | Re: Possible Bug in 9.2beta3 |