On Tue, Jun 26, 2012 at 12:02 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Merlin Moncure <mmonc...@gmail.com> writes: >> I suspect (but haven't had time to prove and may not for several days >> -- unfortunately going on vacation momentarily) that this might be >> caused by pl/sh. > > Hm. The reported symptoms might be explainable if something had caused > multiple threads to become active within the backend process --- then > it would be plausible for it to try to do proc_exit cleanup twice. > Which would explain the first two errors, though I'm not sure how that > leads to failing to disown the process latch, as the third error > suggests must have happened. But I don't know enough about pl/sh to > know if it could cause threading activation. > >> In particular, we have a routine that was >> inadvertently applied to the database in with windows cr/lf instead of >> the normal linux newline. > > This doesn't seem real promising as an explanation ...
right -- just a suspicion. maybe the relevant point was that it immediately failed. operator invoking the busted routine (which I had to fix) and the crash were highly correlated, although it does not always crash. yesterday was very heavy load and today not so much. merlin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
