From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Recovering a database in danger of transaction wrap-around
Date: Fri, 25 Jan 2008 20:23:42 +0100
Message-ID: <20080125192342.GA15475@easy2.in-chemnitz.de> (raw)
In-Reply-To: <3757.1201288206@sss.pgh.pa.us>
References: <OF9BE59CFF.E7484997-ON852573DB.006729F4-852573DB.0067D0FC@us.ibm.com>
<3757.1201288206@sss.pgh.pa.us>
On Fri, Jan 25, 2008 at 02:10:06PM -0500, Tom Lane wrote:
> > I used lsof to monitor which files the backend was actually working on. It
> > took two of the four days for it to vacuum a single table with 43
> > one-gigabyte extents. I have one table with over 300 extents. I'm looking
> > at a vacuum process which can ultimately take weeks (if not months) to
> > complete.
>
> Yipes. You are just using plain VACUUM, right, not VACUUM FULL?
> Have you checked that vacuum_cost_delay isn't enabled?
pg_dump/pg_restore may be a lot faster here - we're in an emergency
situation anyway and after that, the whole DB will be clean again, all
indices rebuilt nicely, no bloat in the tables.
Tino.
--
www.craniosacralzentrum.de
www.spiritualdesign-chemnitz.de
Tino Schwarze * Lortzingstraße 21 * 09119 Chemnitz
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: postgresql@tisc.de
Subject: Re: Recovering a database in danger of transaction wrap-around
In-Reply-To: <20080125192342.GA15475@easy2.in-chemnitz.de>
* 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