From: Josh Berkus <josh@agliodbs.com>
To: Patrick Hatcher <PHatcher@macys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum full 100 mins plus?
Date: Wed, 14 Jul 2004 17:13:13 -0700
Message-ID: <200407141713.13472.josh@agliodbs.com> (raw)
In-Reply-To: <OFE37D67EB.C42A1B3B-ON88256ED1.007C0430-88256ED1.007D08AB@fds.com>
References: <OFE37D67EB.C42A1B3B-ON88256ED1.007C0430-88256ED1.007D08AB@fds.com>
Patrick,
> Answered my own question. I gave up the vacuum full after 150 mins. I was
> able to export to a file, vacuum full the empty table, and reimport in less
> than 10 mins. I suspect the empty item pointers and the sheer number of
> removable rows was causing an issue.
Yeah. If you've a table that's not been vacuumed in a month, it's often
faster to clean it out and import it.
I've seen vacuums take up to 3 hours in really bad cases.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, PHatcher@macys.com
Subject: Re: vacuum full 100 mins plus?
In-Reply-To: <200407141713.13472.josh@agliodbs.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