From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Ruprecht <chrup999@yahoo.com>
Cc: p-admin <pgsql-admin@postgresql.org>
Subject: Re: Vacuum
Date: Mon, 16 Jul 2001 18:59:57 -0400
Message-ID: <21618.995324397@sss.pgh.pa.us> (raw)
In-Reply-To: <00b001c10e2d$420007e0$5dd26383@corp.compucom.com>
References: <00b001c10e2d$420007e0$5dd26383@corp.compucom.com>
"Chris Ruprecht" <chrup999@yahoo.com> writes:
> Can somebody explain to me what this vacuum is doing with all these
> files?
Just wasting space, I'm afraid. You may want to apply the patch at
http://www.ca.postgresql.org/mhonarc/pgsql-patches/2001-06/msg00061.html
However, if the database consists of several small tables and not one
huge one, I'm not sure why VACUUM's WAL log might grow so long. The
log should be truncatable after each table is vacuumed, even without
the patch.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, chrup999@yahoo.com
Subject: Re: Vacuum
In-Reply-To: <21618.995324397@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