Is there some sort of time delay involved with VACUUM that I should be aware
of? I ran a VACUUM FULL on the table that I had run the test on this morning
and sure enough, it shrunk down to zero size (there were no rows in the
table) but then I reran the test and then ran VACUUM FULL and it DID NOT
shrink the file on disk ...
Is there some sort of cache or something that's never getting timed out (the
out of control 500 meg table file i made mention of, gets dumped and
repopulated every 2 minutes ... is there something that's never getting
removed from a LRU cache?)
Here's my VACUUM command ...
> -----Original Message-----
> From: Andrew Sullivan [mailto:andrew@libertyrms.com]On Behalf Of Andrew
> Sullivan
> Sent: Monday, April 08, 2002 2:55 PM
> To: David Esposito
> Subject: Re: [GENERAL] vacuuming not working?
>
>
> On Mon, Apr 08, 2002 at 01:40:48PM -0400, David Esposito wrote:
> > Me again,
> >
> > I have a problem with VACUUM. I searched the list and don't seem to see
> > anyone else reporting this behavior so I'm wondering if i'm
> doing something
> > wrong
> >
> > Summary: Vacuuming does not seem to mark the space as
> "available for reuse"
> > as the documentation says.
>
> You haven't read the documentation carefully enough, or else you're
> reading old docs.
>
> > Platform: Postgres 7.2.1 on RedHat 7.0
> ^
> > The problem is that the file on disk is over 500 megs! and it
> appears to be
> > growing pretty much without bound ... I do a VACUUM every night (not a
> > VACUUM FULL, just a straight VACUUM)
> ^^^^^^^^^^^
>
> Only the VACUUM FULL makes the disk space available for reuse (by
> other programs; postgres will be able to reuse some of the space with
> lazy VACUUM).
>
> A
>
> --
> ----
> Andrew Sullivan 87 Mowat Avenue
> Liberty RMS Toronto, Ontario Canada
> <andrew@libertyrms.info> M6K 3E3
> +1 416 646 3304 x110
>