Vacuuming DVs with few/no updates?

From: Preston <unsane(at)idl(dot)com(dot)au>
To: pgsql-admin(at)postgresql(dot)org
Subject: Vacuuming DVs with few/no updates?
Date: 2003-02-05 21:33:28
Message-ID: 1044480808.3e418328aca17@mail.idl.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all,

Just wondering about how useful the vacuumdb functionality is for a database
that pretty much only ever gets inserts/selects.

I've got a database that is intended for next-to-no deletion of records, which
is where I see the vacuum facility mostly intended for. I.e., while there'll be
the occasional record edits, these edits will primarily be of the form of
adjusting integer records (and therefore shouldn't adjust any space requirements
for a row).

I'm thinking that with this database I'll configure vacuumdb to only run once a
month or so. But before I do that I want to make sure I'm not missing some other
important functionality that it does...

Cheers,

-Preston de Guise.

--
Oops.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris White 2003-02-05 22:33:13 Re: Duplicate indexes found in the postgres Database
Previous Message webmaster 2003-02-05 21:23:38 Cascade on update statement, not on table definition