Re: Vacuum

From: Ariunbold Gerelt-Od <gereltod(at)kikakuya(dot)com>
To: PGSQL <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Vacuum
Date: 2001-10-09 07:45:47
Message-ID: 3BC2AB2B.5030005@kikakuya.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)eclectic-world(dot)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(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
> .
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Steve Frampton 2001-10-09 08:01:28 [REPOST] Remote database questions (NFS shared access, RServ)
Previous Message Dmitry Chernikov 2001-10-08 16:53:46 pg_dump 7.1.2 objects dump order