Return-Path: pg_adm@postgres.berkeley.edu 
Delivery-Date: Tue, 02 Feb 93 08:58:41 PST
Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02275; Tue, 2 Feb 93 08:41:48 -0800
Date: Tue, 2 Feb 93 08:41:48 -0800
Message-Id: <9302021641.AA02275@postgres.Berkeley.EDU>
From: klein@imasun.lbl.gov (Gregory Klein)
Apparently-To: postgres-dist@postgres

klein@imasun.lbl.gov (Gregory Klein)
Subject: vacuum cleaner Subject: vacuum cleaner
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu

Well this post didn't make it last time, so here's another try.
Any comments???

----- Begin Included Message -----

>From pg_adm@postgres.Berkeley.EDU Thu Jan 21 18:44:04 1993
Date: Tue, 19 Jan 93 11:32:54 -0800
From: klein@imasun.lbl.gov (Gregory Klein)
Subject: vacuum cleaner
To: postgres@postgres.Berkeley.EDU
Sender: pg_adm@postgres.Berkeley.EDU
Cc: klein@imasun.lbl.gov
Content-Length: 389

Could someone explain how the Postgres vacuum cleaner is supposed to
work.  I see no change in the file size in
/usr/postgres/data/base/[dbname]/[recordname] after a do a large number
of deletes and then run vacuum.  Is there no way to reduce this file
size?  I am afraid that if I have an extremely dynamic database, my
disk will fill up rather quickly.

Thanks for any help,

Greg Klein


----- End Included Message -----