pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@libertyrms.info>
To: shridhar_daithankar@persistent.co.in
Cc: pgsql-performance@postgresql.org, "Matthew T. O'Connor" <matthew@zeut.net>
Subject: Re: Some vacuum & tuning help
Date: Tue, 05 Aug 2003 10:29:26 -0400
Message-ID: <60el00jhyx.fsf@dev6.int.libertyrms.info> (raw)

Shridhar Daithankar wrote: 
> I agree, specifying per table thresholds would be good in autovacuum.. 
 
Which begs the question of what the future direction is for pg_autovacuum.

There would be some merit to having pg_autovacuum throw in some tables
in which to store persistent information, and at that point, it would
make sense to add some flags to support the respective notions that:

 -> Some tables should _never_ be touched;

 -> Some tables might get "reset" to indicate that they should be
    considered as having been recently vacuumed, or perhaps that they
    badly need vacuuming;

 -> As you suggest, per-table thresholds;

 -> pg_autovacuum would know when tables were last vacuumed by
    it...

 -> You could record vacuum times to tell pg_autovacuum that you
    vacuumed something "behind its back."

 -> If the system queued up proposed vacuums by having a "queue"
    table, you could request that pg_autovacuum do a vacuum on a
    particular table at the next opportunity.

All well and interesting stuff that could be worth implementing.

But the usual talk has been about ultimately integrating the
functionality into the backend, making it fairly futile to enhance
pg_autovacuum terribly much.

Unfortunately, the "integrate into the backend" thing has long seemed
"just around the corner."  I think we should either:
 a) Decide to enhance pg_autovacuum, or
 b) Not.

In view of how long the "better answers" seem to be taking to emerge,
I think it makes sense to add functionality to pg_autovacuum.
-- 
output = reverse("ofni.smrytrebil" "@" "enworbbc")
<http://dev6.int.libertyrms.com/;
Christopher Browne
(416) 646 3304 x124 (land)



view thread (26+ messages)  latest in thread

Message-ID: <60el00jhyx.fsf@dev6.int.libertyrms.info>
Permalink:  ../60el00jhyx.fsf@dev6.int.libertyrms.info/
Also on:    postgresql.org/message-id/60el00jhyx.fsf@dev6.int.libertyrms.info

 · 

reply

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: cbbrowne@libertyrms.info, shridhar_daithankar@persistent.co.in, matthew@zeut.net
  Subject: Re: Some vacuum & tuning help
  In-Reply-To: <60el00jhyx.fsf@dev6.int.libertyrms.info>
  References: <60el00jhyx.fsf@dev6.int.libertyrms.info>

* 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