| From: | Rick Dicaire <kritek(at)gmail(dot)com> |
|---|---|
| To: | Philip Edelbrock <phil(at)studiogeologie(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Vacuuming |
| Date: | 2012-02-23 00:20:41 |
| Message-ID: | CA+Cc--eD5kMeaT_P4wizehpPnnn56StRJVYCQi9t4Su6V1++Lg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Feb 22, 2012 at 7:08 PM, Philip Edelbrock
<phil(at)studiogeologie(dot)com> wrote:
> 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?
Short answer, no.
Are you doing ANY vacuuming on this database?
> 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!
I have a client using this same version, and they use a number of
scripts in cron to vacuum various tables
that get modified at a high rate. Based on the clients needs, they're
vacuuming every ten minutes.
Note they're not doing VACUUM FULL.
Your mileage may vary, and you'll need to determine what best fits your needs.
Moving to postgres 9 would help alleviate some of your performance and
maintenance issues.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Fehrle | 2012-02-23 00:38:38 | Re: WAL files containing old and unmodified data? |
| Previous Message | Philip Edelbrock | 2012-02-23 00:08:01 | Vacuuming |