Re: PG9.1.2 -- 3 day old orphaned/non-responsive query -- pg_(cancel)(terminate)_backend has no effect

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Reid Thompson <Reid(dot)Thompson(at)ateb(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PG9.1.2 -- 3 day old orphaned/non-responsive query -- pg_(cancel)(terminate)_backend has no effect
Date: 2012-01-14 17:31:44
Message-ID: CAK3UJREtFA8t7mCQwujoVu0vrB-Cd=dxsq-rSqYdDq=j=CoxAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jan 13, 2012 at 12:02 PM, Reid Thompson <Reid(dot)Thompson(at)ateb(dot)com> wrote:

> The select query has been apparently orphaned by it's originating
> terminal or script or application.  pg_/cancel/terminate/_backend both
> return t, but the query does not cancel/terminate.   sigterm via the OS
> has no effect either.

You're sure you're killing the right backend (looks like the process
ID should be 32697, from what you posted)? What does strace tell you
the backend is doing?

> I'm not sure whether the vacuum is active, and just slow, or if it's
> spinning, or...?  I've taken no action toward the vacuum process.

Above you talk about the "select query has been apparently orphaned".
Are you trying to kill off the vacuum or the SELECT query?

Josh

In response to

Browse pgsql-general by date

  From Date Subject
Next Message plasmasoftware net 2012-01-15 03:22:31 how to make select for multiunit
Previous Message Tomas Vondra 2012-01-13 21:49:37 Re: indexes no longer used after shutdown during reindexing