Re: VACUUM Question - Mailing list pgsql-general

From Matthew T. O'Connor
Subject Re: VACUUM Question
Date
Msg-id 5071.71.40.140.99.1138304142.squirrel@mail.tocr.com
Whole thread Raw
In response to VACUUM Question  ("Oisin Glynn" <me@oisinglynn.com>)
Responses Re: VACUUM Question  (Michael Fuhr <mike@fuhr.org>)
List pgsql-general
If you really are just inserting, and never updating or deleting, then you
will never need to vacuum the table, rather you will just need to ANALYSE
the table.  If you use autovacuum that is exactly what it will do.

As for Reindex, I'm not entirely sure, I don't think you would benefit
from reindex because you aren't updating or deleting.  Can anyone comment
on this?  Is is possibile that a table with lots of inserts resulting in
lots of page splits etc could ever benifit form REINDEX?

Matt


> We have 2 tables we expect to grow by up to 50,000 rows per day each
> depending on the customer.  In normal operation we will most likely never
> update or delete from these tables as they are for historical reporting.
> (Eventually we may but a limit on the amount of data and delete older than
> X months or such)
> We intend to create a number of indexes based upon the reporting search
> criteria.
>
> What would the best setup be for VACUUM, ANALYSE, REINDEX.  Alot of the
> infor refers to data hanging around from deletes and updates which in
> normal course we will not do on these tables?
>
>
> Oisin
>


pgsql-general by date:

Previous
From: "Andrus"
Date:
Subject: Re: How to implement nested transactions
Next
From: Bob Pawley
Date:
Subject: Re: Arrays