In article <20030429143356.C5EFD3F04@guthrie.charm.net>,
john <jimmer@guthrie.charm.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@ix.netcom.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
