From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ellen Cyran <ellen@urban.csuohio.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: After how many updates should a vacuum be performed?
Date: Wed, 13 Sep 2006 13:27:21 -0400
Message-ID: <13915.1158168441@sss.pgh.pa.us> (raw)
In-Reply-To: <45083BCE.9070109@urban.csuohio.edu>
References: <45082C83.5040206@urban.csuohio.edu>
<12738.1158164349@sss.pgh.pa.us>
<45083274.902@urban.csuohio.edu>
<13301.1158166441@sss.pgh.pa.us>
<45083BCE.9070109@urban.csuohio.edu>
Ellen Cyran <ellen@urban.csuohio.edu> writes:
>> Hm, that should be OK. What do you have maintenance_work_mem set to?
> It's set at the default 16384.
That should be plenty for getting rid of a million or so tuples. I'm
wondering if you are seeing some weird locking effect. Is the VACUUM
constantly busy with I/O or does it sit and wait at points? Do you have
other queries actively accessing the table during the VACUUM?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ellen@urban.csuohio.edu
Subject: Re: After how many updates should a vacuum be performed?
In-Reply-To: <13915.1158168441@sss.pgh.pa.us>
References: <45082C83.5040206@urban.csuohio.edu> <12738.1158164349@sss.pgh.pa.us> <45083274.902@urban.csuohio.edu> <13301.1158166441@sss.pgh.pa.us> <45083BCE.9070109@urban.csuohio.edu> <13915.1158168441@sss.pgh.pa.us>
* 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