Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f6GN0Pa75718
	for <pgsql-admin@postgresql.org>; Mon, 16 Jul 2001 19:00:25 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f6GMxvX21621;
	Mon, 16 Jul 2001 18:59:57 -0400 (EDT)
To: "Chris Ruprecht" <chrup999@yahoo.com>
cc: "p-admin" <pgsql-admin@postgresql.org>
Subject: Re: Vacuum 
In-reply-to: <00b001c10e2d$420007e0$5dd26383@corp.compucom.com> 
References: <00b001c10e2d$420007e0$5dd26383@corp.compucom.com>
Comments: In-reply-to "Chris Ruprecht" <chrup999@yahoo.com>
	message dated "Mon, 16 Jul 2001 14:26:48 -0500"
Date: Mon, 16 Jul 2001 18:59:57 -0400
Message-ID: <21618.995324397@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200107/77
X-Sequence-Number: 1835

"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