Skip site navigation (1) Skip section navigation (2)

Re: pg_avd

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_avd
Date: 2003-02-18 03:52:38
Message-ID: 066101c2d701$2dc74b50$6500a8c0@fhp.internal (view raw or flat)
Thread:
Lists: pgsql-patches
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?
>
> --------------------------------------------------------------------------
-
>
> Matthew T. O'Connor wrote:
> > Here is the code for the auto vacuum daemon I'm working on.
> >
> > I know some type of auto vacuum is highly desired by the project, I just
> > don't know if this implementation of auto vacuum is desired as it's not
> > built into the backend, rather it's a client app.
> >
> > Attached is tar.gz with all the files, expand it into the src/bin
> > directory in the source tree and apply the Makefile.diff patch to
> > src/bin/Makefile and then pg_avd will be built as an executable and
> > installed in the bin directory along with psql and others.
> >
> > I have done some benchmarking (I posted some of it to hackers several
> > weeks back) it always helps with file sizes, but doesn't always help
> > performance since it might kick off a vacuum in the middle of your
> > transaction.  However it does prevent postgres from performing badly due
> > to excessive file size and distorted statistics.
> >
> > Please try it out and give me feedback.  Included in the tar is a README
> > that describes what I have done, and how to use pg_avd.
> >
> > Matthew
> >
>
> Content-Description:
>
> [ Attachment, skipping... ]
>
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> > message can get through to the mailing list cleanly
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania
19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>


In response to

  • Re: pg_avd at 2003-02-18 03:25:31 from Bruce Momjian

Responses

  • Re: pg_avd at 2003-02-18 05:34:32 from Matthew T. O'Connor

pgsql-patches by date

Next:From: Bruce MomjianDate: 2003-02-18 04:57:58
Subject: Re: [HACKERS] psql and readline
Previous:From: Bruce MomjianDate: 2003-02-18 03:25:31
Subject: Re: pg_avd

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group