pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: shridhar_daithankar@persistent.co.in
Cc: Christopher Browne <cbbrowne@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Some vacuum & tuning help
Date: Tue, 5 Aug 2003 11:45:04 -0400
Message-ID: <004901c35b68$8a9d8010$c202a8c0@hplaptop> (raw)
References: <60el00jhyx.fsf@dev6.int.libertyrms.info>
	<000b01c35b63$22d748d0$c202a8c0@hplaptop>
	<22888.1060097705@sss.pgh.pa.us>

From: "Tom Lane" <tgl@sss.pgh.pa.us>
> "Matthew T. O'Connor" <matthew@zeut.net> writes:
> > I chose to leave pg_autovacuum simple and not add too many features
because
> > the core team has said that it needs to be integrated into the backend
> > before it can be considered a core tool.
>
> I think actually it makes plenty of sense to enhance pg_autovacuum while
> it's still contrib stuff.  My guess is it'll be much less painful to
> whack it around in minor or major ways while it's standalone code.
> Once it's integrated in the backend, making significant changes will be
> harder and more ticklish.  So, now is precisely the time to be
> experimenting to find out what works well and what features are needed.

Fair point, my only concern is that a backend integrated pg_autovacuum would
be radically different from the current libpq based client application.
When integrated into the backend you have access to a lot of information
that you don't have access to as a client.  I know one goal I have for the
backend version is to be based on the FSM and not require the stats
collector since it has a measurable negative effect on performance.

But in the more general sense of learning what features people want
(exclusion lists, per table defaults etc) I agree the current version is a
sufficient testing ground.




view thread (26+ messages)  latest in thread

Message-ID: <004901c35b68$8a9d8010$c202a8c0@hplaptop>
Permalink:  ../004901c35b68$8a9d8010$c202a8c0@hplaptop/
Also on:    postgresql.org/message-id/004901c35b68$8a9d8010$c202a8c0@hplaptop

 · 

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: matthew@zeut.net, tgl@sss.pgh.pa.us, shridhar_daithankar@persistent.co.in, cbbrowne@libertyrms.info
  Subject: Re: Some vacuum & tuning help
  In-Reply-To: <004901c35b68$8a9d8010$c202a8c0@hplaptop>
  References: <60el00jhyx.fsf@dev6.int.libertyrms.info> <000b01c35b63$22d748d0$c202a8c0@hplaptop> <22888.1060097705@sss.pgh.pa.us> <004901c35b68$8a9d8010$c202a8c0@hplaptop>

* 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