| From: | Philip Edelbrock <phil(at)studiogeologie(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Vacuuming |
| Date: | 2012-02-23 00:08:01 |
| Message-ID: | 67590CDC-CEB2-4A5A-AC7A-B7B1C18B4637@studiogeologie.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
We're having a problem with database maintenance. If we do a full vacuum, it takes down the app until it completes (which is a bit to be expected as a full vacuum locked the app out of the database). However, if we don't do a periodic full vacuum, our drive gets filled up.
The question is, is there a way to keep availability of the app 100% yet keep the database maintained without the drive filling up? Or is it just the nature of the beast that a full vacuum needs to be done periodically?
BTW- This is PostgreSQL 8.1.23 as part of RHEL 5.6.
Thanks, any tips on good practices for cron scripts doing Postgres maintenance would be great!
Phil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Dicaire | 2012-02-23 00:20:41 | Re: Vacuuming |
| Previous Message | Kevin Grittner | 2012-02-22 20:53:23 | Re: WAL files containing old and unmodified data? |