Date: Fri, 23 Feb 2007 16:34:57 -0600
From: "Jim C. Nasby" <jim@nasby.net>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long checkpoint_timeout
Message-ID: <20070223223456.GB11743@nasby.net>
References: <1172254469.10824.243.camel@dogma.v10.wvs>
	<20070223200215.GA11743@nasby.net>
	<1172262188.10824.248.camel@dogma.v10.wvs>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1172262188.10824.248.camel@dogma.v10.wvs>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Fri, Feb 23, 2007 at 12:23:08PM -0800, Jeff Davis wrote:
> On Fri, 2007-02-23 at 14:02 -0600, Jim C. Nasby wrote:
> > > say that checkpoints cause extra disk I/O. Is there a good way to
> > > measure how much extra I/O (and WAL volume) is caused by the
> > > checkpoints? Also, it would be good to know how much total I/O is caused
> > > by a checkpoint so that I know if bgwriter is doing it's job.
> > 
> > There's a patch someone just came up with that provides additional debug
> > info about both bgwriter operation and checkpoints. I know it will at
> > least tell you how much was written out by a checkpoint.
> 
> Excellent, that would answer a lot of my questions. I did some brief
> searching and nothing turned up. Do you have a link to the discussion or
> the patch?

http://archives.postgresql.org/pgsql-hackers/2007-02/msg01083.php
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)