From: Rich Cullingford <rculling@sysd.com>
To: pgsql-performance@postgresql.org
Subject: pre-Vacuum statistics
Date: Thu, 10 Jul 2003 14:19:26 -0400
Message-ID: <3F0DAE2E.3020102@sysd.com> (raw)
Greetings,
All the recommendations I can locate concerning the use of (the various
flavors of) VACUUM suggest running it at regular intervals. Is there any
way, for a given table, to discover how many/what percentage of rows are
likely to be VACUUMable at a given point, so that some kind of
threshold-based VACUUM could be done by an application? We have several
tables that undergo bursty UPDATEs, where large numbers of transactions
occur "relatively" infrequently; and others where the UPDATEs occur at
regular intervals (a few seconds or so).
Thanks for any advice!
Regards,
Rich Cullingford
rculling@sysd.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: rculling@sysd.com
Subject: Re: pre-Vacuum statistics
In-Reply-To: <3F0DAE2E.3020102@sysd.com>
References: <3F0DAE2E.3020102@sysd.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox