From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | bangh <banghe(at)baileylink(dot)net> |
Cc: | "Leong, Fushan" <fushan(dot)leong(at)SonoSite(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Vaccum |
Date: | 2001-11-29 18:39:41 |
Message-ID: | 20011129103838.Y44666-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, 29 Nov 2001, bangh wrote:
> HI,
>
> This is not necessary true, but you might feel understandable.
>
> To delete records, just seems as the records are marked as voided. Space is not
> collected. To run vaccum might do this kind space garbage collection.
>
> To run vacummdb really save the space, but it works at only some extent. e.g.
> index still goes quickly, it goes bigger and bigger, one day it eats all your
> space you have, behaves as gets a virus. In this case, my solution is to use
> pg_dump the original one, create new one and restory, this reaaly save your
> space, but you cannot do this as frequently as you do "vacuum". It costs much
> more CPU time to do it if your database is huge.
I think REINDEX or just DROP INDEX/CREATE INDEX should do the same thing
without requiring the dump/restore.
From | Date | Subject | |
---|---|---|---|
Next Message | Leong, Fushan | 2001-11-29 19:00:22 | Re: Vaccum |
Previous Message | Tom Lane | 2001-11-29 18:32:51 | Re: Bad Date field |