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

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Dennis Koegel <dk(at)openit(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: segfault in pg 8.4, CurrentResourceOwner == NULL while processing SIGTERM
Date: 2010-03-19 13:59:35
Message-ID: 4BA38347.1070905@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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 saying the crash doesn't need fixing, _but_: why not use
statement_timeout instead?

Are you trying to get rid of idle backends, too, or backends that're
just transferring data to the client?

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Roberto Rivera Mardones 2010-03-19 15:29:07 BUG #5383: Problemas con GROUP BY
Previous Message Dennis Koegel 2010-03-19 12:34:45 segfault in pg 8.4, CurrentResourceOwner == NULL while processing SIGTERM