Re: Unresponsive vacuum process

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unresponsive vacuum process
Date: 2004-05-20 03:39:48
Message-ID: 200405192139.48175.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday May 19 2004 5:49, Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > I have a 7.2.1 backend running VACUUM which appears to be blocking all
> > other processes. I have issued SIGTERM and SIGINT directly to that
> > backend and also killed the client process, but the VACUUM continues
> > chewing up CPU and blocking others.
>
> Hmph. AFAICS 7.2 does contain CHECK_FOR_INTERRUPT calls within all the
> major VACUUM loops, so it should respond to SIGINT in a reasonably
> timely fashion. I'd think it was blocked on someone else's lock if it
> weren't that you say it's still consuming CPU. Can you attach to the
> troublesome backend with gdb and get a stack trace to show where it is?

Had to kill it, couldn't wait. Looks like we'll punt this one and just
upgrade the cluster, but if not, I'll try to capture. Thanks.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message wespvp 2004-05-20 04:24:25 Re: Unresponsive vacuum process
Previous Message Vikram 2004-05-20 02:41:29 Unable to run testlibpq.c program