From: Ariunbold Gerelt-Od <gereltod@kikakuya.com>
To: PGSQL <pgsql-admin@postgresql.org>
Subject: Re: Vacuum
Date: Tue, 09 Oct 2001 16:45:47 +0900
Message-ID: <3BC2AB2B.5030005@kikakuya.com> (raw)
References: <000901c15006$cdd37de0$1b6b5ba5@tamu.edu>
<1433.1002557034@sss.pgh.pa.us>
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
>
> .
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gereltod@kikakuya.com
Subject: Re: Vacuum
In-Reply-To: <3BC2AB2B.5030005@kikakuya.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox