Re: [BUGS] segfault in pg 8.4, CurrentResourceOwner == NULL while processing SIGTERM

2010-03-19 Thread Tom Lane
Dennis Koegel writes: > [ crash when a SQL function is killed by SIGTERM ] Frankly, I would expect this to fail with even higher probability in 8.1. We didn't even pretend that SIGTERM'ing individual backends was a safe thing to do in 8.1. You ought to rethink your connection management methodo

Re: [BUGS] segfault in pg 8.4, CurrentResourceOwner == NULL while processing SIGTERM

2010-03-19 Thread Craig Ringer
On 19/03/2010 8:34 PM, Dennis Koegel wrote: We automatically SIGTERM long running queries (bad situation, of course, but necessary under certain load conditions here). This has been the case for 8.1 as well and worked fine ever since. Even with 8.4 it works fine most of the time. I'm not sayin

[BUGS] segfault in pg 8.4, CurrentResourceOwner == NULL while processing SIGTERM

2010-03-19 Thread Dennis Koegel
Hi, a week ago, we have migrated our production setup -- three amd64 machines on RHEL4 running only postgres and slony -- from pg 8.1 to pg 8.4. Since 8.4, we encounter rare crashes (between two and ten times per day for the whole setup) of single backend server processes, loosely related to very