From: Luke Lonergan <llonergan@greenplum.com>
To: Tomeh, Husam <htomeh@firstam.com>
To: pgsql-performance@postgresql.org
Subject: Re: "Vacuum Full Analyze" taking so long
Date: Mon, 25 Jul 2005 15:48:39 -0700
Message-ID: <BF0ABA57.9EF6%llonergan@greenplum.com> (raw)
In-Reply-To: <C45835824D00A844BBD0F032D5CDED920116DC10@pisgana01sxch01.ana.firstamdata.com>
Vacuum full takes an exclusive lock on the tables it runs against, so if you
have anything else reading the table while you are trying to run it, the
vacuum full will wait, possibly forever until it can get the lock.
What does the system load look like while you are running this? What does
vmstat 1 show you? Is there load on the system other than the database?
Do you really need to run vacuum full instead of vacuum?
- Luke
On 7/25/05 2:30 PM, "Tomeh, Husam" <htomeh@firstam.com> wrote:
>
> I have an 8.02 postgresql database with about 180 GB in size, running on
> 2.6 RedHat kernel with 32 GB of RAM and 2 CPUs. I'm running the vacuum
> full analyze command, and has been running for at least two consecutive
> days with no other processes running (it's an offline loading server). I
> tweaked the maintenanace_mem to its max (2 GB) with work_mem of 8M. I
> have no issues with my checkpoints. I can still I/O activities against
> the physical files of the "property" table and its two indexes (primary
> key and r index). The property files are about 128GB and indexes are
> about 15 GB. I have run the same maintenance job on a different box
> (staging) with identical hardware config (except with 64 GB instead of
> 32) and took less than 12 hours. Any clue or tip is really
> appreciated.
>
> Also read a comment by Tom Lane, that terminating the process should be
> crash-safe if I had to.
>
> Thanks,
>
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: llonergan@greenplum.com, htomeh@firstam.com
Subject: Re: "Vacuum Full Analyze" taking so long
In-Reply-To: <BF0ABA57.9EF6%llonergan@greenplum.com>
* 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