From: Brad Nicholson <bnichols@ca.afilias.info>
To: Dan Harris <fbsd@drivefaster.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: vacuum full seems to hang on very small table
Date: Tue, 04 Apr 2006 11:07:51 -0400
Message-ID: <44328BC7.1070208@ca.afilias.info> (raw)
In-Reply-To: <443289E3.7020801@drivefaster.net>
References: <443289E3.7020801@drivefaster.net>
Dan Harris wrote:
> I have a table with 1 live row that I found has 115000 dead rows in it (
> from a testing run ). I'm trying to VACUUM FULL the table and it has
> run for over 18 hours without completion. Considering the hardware on
> this box and the fact that performance seems reasonable in all other
> aspects, I'm confused as to why this would happen. The database other
> than this table is quite large ( 70 gigs on disk ) and I would expect to
> take days to complete but I just did 'vacuum full table_stats'. That
> should only do that table, correct? I'm running 8.0.3.
VACUUM FULL requires an exclusive lock on the table that it's vacuuming.
Chances are something else has a lock on the table is blocking the
vacuum from obtaining the necessary lock. Check pg_locks for ungranted
locks, you'll probably find that the request from the vacuum is ungranted.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
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: bnichols@ca.afilias.info, fbsd@drivefaster.net
Subject: Re: vacuum full seems to hang on very small table
In-Reply-To: <44328BC7.1070208@ca.afilias.info>
* 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