| From: | Juliann Meyer <Julie(dot)Meyer(at)noaa(dot)gov> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | vacuum questions |
| Date: | 2007-08-20 18:33:52 |
| Message-ID: | 46C9DE90.1030206@noaa.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Currently running v7.4.8 postgres on a RHE Linux 4.0 box. Will be
upgraded to postgres 8.2.x sometime this fall.
Several of the tables in the database that resides on this system have
lots of inserts and updates. Very little is deleted at this time, as
the database is intended for archiving.
Currently a cron job runs a vacuum analyze 3 times a day. Is there any
need to run a vacuum full every so often?
If so, how often should a vacuum full be done? And do all other
processes that "hit" the database need to shut off when a vacuum full is
done?
Also another office that has a similar setup has switched to running
pg_autovacuum instead of the vacuum analyze 3 times/day, are there any
advantages and/or disadvantages to this approach?
Thanks in advance for any information and guidance you can give,
Julie
| Attachment | Content-Type | Size |
|---|---|---|
| julie.meyer.vcf | text/x-vcard | 249 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erwin Brandstetter | 2007-08-20 18:38:10 | vacuumdb for a number of tables |
| Previous Message | Scott Marlowe | 2007-08-20 18:03:10 | Re: how to call sql code without function |