From: | dalgoda(at)ix(dot)netcom(dot)com (Mike Castle) |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: vacuuming and freed disk space |
Date: | 2003-04-29 23:48:15 |
Message-ID: | vif3ox1if.ln2@thune.mrc-home.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In article <20030429143356(dot)C5EFD3F04(at)guthrie(dot)charm(dot)net>,
john <jimmer(at)guthrie(dot)charm(dot)net> wrote:
>i am looking at our database table maintenance. we are running a "space
>watch" task that looks at available disk space and removes old records
>when/if a certain threshold is passed.
I'm wondering: why?
If you just regularly expired old information anyway, PG will reuse the
data, so you should end up with a steady state. If really paranoid you can
monitor various PG stats, I believe, and use that to dry when to
delete/vacuum. But your current approach seemed a little odd to me (a bit
too non-deterministic is my gut feeling).
mrc
--
Mike Castle dalgoda(at)ix(dot)netcom(dot)com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2003-04-30 04:04:32 | knowing last modification / last access times of tables.. |
Previous Message | john | 2003-04-29 23:37:08 | vacuuming and freed disk space |