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

Re: pg_avd

From: "Magnus Naeslund(f)" <mag(at)fbab(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Peter Eisentraut" <peter_e(at)gmx(dot)net>,"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>,"Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_avd
Date: 2003-02-19 23:32:33
Message-ID: 048a01c2d86f$2daf0710$f80c0a0a@mnd (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Maybe i can provide a datapoint on this matter.
I've been using pgavd from over at gborg (Shridhar Daithankar's (i
think?) code) in production for some months now. I love it.
I was some hazzle to get it up, but once installed everything is smooth
and nice.

The vacuum + analyze seems to affect my system in an only postive way:

1) Everything seems snappier.
2) Weekly vacuum full is faster now.
3) The updates on a table with counters is updated faster nowadays.
4) pgavd is totally automatic, so just install it and run it.

Well i just wanted to say that i don't care if it's an external/client
process, it makes a huge differance to us lazy sob's that always forgets
to vacuum all the time.
It's even better that it's using pgstats to determine when to run
vacuum, so after big inserts it gets vacuumed promptly.


In response to

  • Re: pg_avd at 2003-02-19 21:37:50 from Bruce Momjian

pgsql-patches by date

Next:From: Bruce MomjianDate: 2003-02-19 23:47:01
Subject: Re: Object (Domain) locking
Previous:From: mlwDate: 2003-02-19 23:27:47
Subject: Re: The last configuration file patch (I hope!) This one

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