Message-ID: <3BC2AB2B.5030005@kikakuya.com>
Date: Tue, 09 Oct 2001 16:45:47 +0900
From: Ariunbold Gerelt-Od <gereltod@kikakuya.com>
Organization: Kikakuya.Ltd
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:0.9.2) Gecko/20010726 Netscape6/6.1
MIME-Version: 1.0
To: PGSQL <pgsql-admin@postgresql.org>
Subject: Re: Vacuum
References: <000901c15006$cdd37de0$1b6b5ba5@tamu.edu>
	<1433.1002557034@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

Tom,
Is there any way to check whether there is open transaction with a lock
on stucking table while vacuuming and terminate vacuum?
Tom Lane wrote:

> "Summer S. Wilson" <collectonian@eclectic-world.com> writes:
> 
>>I'm running PostgreSQL 7.1 with Slackware 8 on a dual processor Dell server.
>>I have a database with 17 tables.  I started VacuumDB with the analyze
>>option on Friday around 3pm...when I came in this morning at 8 it was still
>>not done.  From the verbose info, it seems to be "stuck" on one table,
>>whowrote which is the second largest table (2546 records).
>>
> 
> Is it consuming CPU time, or just sitting?  (ps or top would tell you)
> If it's just sitting, I'd bet that there is some other connected backend
> that's holding an open transaction with a lock on that table.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 
> .
> 
>