X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 8840FD1D361
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Mon, 22 Mar 2004 16:39:27 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 82127-09
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Mon, 22 Mar 2004 12:39:36 -0400 (AST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by svr1.postgresql.org (Postfix) with ESMTP id E042ED1D315
	for <pgsql-admin@postgresql.org>; Mon, 22 Mar 2004 12:39:25 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2MGda0q001590;
	Mon, 22 Mar 2004 11:39:36 -0500 (EST)
To: "Mark M. Huber" <MHuber@VMdirect.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum Issues 
In-reply-to: <C82819B1AE6E934A91FE8481153EB422A9E37E@mail.co.vmdirect.com> 
References: <C82819B1AE6E934A91FE8481153EB422A9E37E@mail.co.vmdirect.com>
Comments: In-reply-to "Mark M. Huber" <MHuber@VMdirect.com>
	message dated "Fri, 19 Mar 2004 09:46:09 -0800"
Date: Mon, 22 Mar 2004 11:39:36 -0500
Message-ID: <1589.1079973576@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200403/286
X-Sequence-Number: 12855

"Mark M. Huber" <MHuber@VMdirect.com> writes:
> I was did a normal vacuum and then I did a full which hung on a table,

Sounds to me like some other transaction is holding a lock on that
table.

In recent releases you can look in the pg_locks system view to see
who's got the lock.

			regards, tom lane