From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark M. Huber <MHuber@VMdirect.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum Issues
Date: Mon, 22 Mar 2004 11:39:36 -0500
Message-ID: <1589.1079973576@sss.pgh.pa.us> (raw)
In-Reply-To: <C82819B1AE6E934A91FE8481153EB422A9E37E@mail.co.vmdirect.com>
References: <C82819B1AE6E934A91FE8481153EB422A9E37E@mail.co.vmdirect.com>
"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
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: tgl@sss.pgh.pa.us, MHuber@VMdirect.com
Subject: Re: Vacuum Issues
In-Reply-To: <1589.1079973576@sss.pgh.pa.us>
* 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