From: Jan Peterson <jan.l.peterson@gmail.com>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: How long it takes to vacuum a big table
Date: Fri, 28 Oct 2005 10:48:51 -0600
Message-ID: <72e966b00510280948h15fd8d56qc3aaca7840f2348d@mail.gmail.com> (raw)
In-Reply-To: <1130512461.25950.20.camel@coppola.muc.ecircle.de>
References: <1130512461.25950.20.camel@coppola.muc.ecircle.de>
We've also experienced problems with VACUUM running for a long time.
A VACUUM on our pg_largeobject table, for example, can take over 24
hours to complete (pg_largeobject in our database has over 45million
rows). With our other tables, we've been able to partition them
(using inheritance) to keep any single table from getting "too large",
but we've been unable to do that with pg_largeobject. Currently,
we're experimenting with moving some of our bulk (large object) data
outside of the database and storing it in the filesystem directly.
I know that Hannu Krosing has developed some patches that allow
concurrent VACUUMs to run more effectively. Unfortunately, these
patches didn't get into 8.1 so far as I know. You can search the
performance mailing list for more information.
-jan-
--
Jan L. Peterson
<jan.l.peterson@gmail.com>
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: jan.l.peterson@gmail.com, nagy@ecircle-ag.com
Subject: Re: How long it takes to vacuum a big table
In-Reply-To: <72e966b00510280948h15fd8d56qc3aaca7840f2348d@mail.gmail.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