On Thu, Jul 28, 2005 at 11:42:22AM +1000, Gavin Sherry wrote:
> On Wed, 27 Jul 2005, Alvaro Herrera wrote:
> * Change how we track the need to vacuum
> I don't really think the use of row level stats are the best
> indicator for a need to vacuum. I wonder if we could keep a
> counter for each segment (ie, every 1 GB file backing a heap or
> index) or file which indicates the number of blocks which have been
> dirtied since the last vacuum. The user would specify a threshold
> of X blocks and once we reached that we would invoke vacuum.
Interesting approach. I don't think it's too difficult to implement.
We just need a new stat message indicating that block N was dirtied
because of new or deleted tuples (hint bit changes need not apply)
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"I love the Postgres community. It's all about doing things _properly_. :-)"
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2005-07-28 02:55:50|
|Subject: Re: Some new list.c primitives |
|Previous:||From: Josh Berkus||Date: 2005-07-28 02:32:34|
|Subject: Re: [Testperf-general] dbt2 & opteron performance|