From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nimesh Satam <nimesh.zedo@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Table not getting vaccumed.
Date: Sat, 30 Sep 2006 12:45:50 -0400
Message-ID: <13551.1159634750@sss.pgh.pa.us> (raw)
In-Reply-To: <965aa3ed0609300225v33a3a6d4s9b19568d75949cc3@mail.gmail.com>
References: <965aa3ed0609300225v33a3a6d4s9b19568d75949cc3@mail.gmail.com>
"Nimesh Satam" <nimesh.zedo@gmail.com> writes:
> I am trying to vaccum one of the table using the following command:
> VACUUM FULL ANALYZE VERBOSE table_name;
> But for some reason the table vaccuming is not going ahead.
VACUUM FULL requires exclusive lock on the table, so it's probably
waiting for some open transaction that has a reader's or writer's
lock on it. Look in pg_stat_activity and pg_locks to find out more.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, nimesh.zedo@gmail.com
Subject: Re: Table not getting vaccumed.
In-Reply-To: <13551.1159634750@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