Re: pg_avd

I think it's a question of, is this solution one that we want to keep
for a while, or do we want a different implementation of AVD, perhaps
something built into the backend that could take advantage of the FSM
also.

I would like to see it in bin, but thats just me :-) I would prefer
contrib over gborg.

What do people think of using pg_ctl to start and stop the AVD? Perhaps
an new "with AVD" option when starting the postmaster.

There are missing features still, but I will continue to work on this
and fill in the gaps if people think it's worth it.

On Mon, 2003-02-17 at 22:52, Christopher Kings-Lynne wrote:
> I think this is an important feature, especially for newbies, etc. I vote
> for /bin. That way it will grow and improve and it will soon become a power
> user feature.
>
> Chris
>
> ----- Original Message -----
> From: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
> To: "Matthew T. O'Connor" <matthew(at)zeut(dot)net>
> Cc: "Patches" <pgsql-patches(at)postgresql(dot)org>
> Sent: Tuesday, February 18, 2003 11:25 AM
> Subject: Re: [PATCHES] pg_avd
>
>
> >
> > This looks very good. It is something I have been hoping to have for
> > 7.4. It does what I think everyone wanted, that is, uses the stats
> > collector to determine what tables to vacuum.
> >
> > Just a few comments:
> >
> > The copyright line in the text should probably be removed.
> > pg_avd seems pretty cryptic. Perhaps pg_autovacuum.
> > I like the fact it is a client app.
> >
> > Now, where do we put it? /bin, /contrib, gborg?