From: Jeff Davis <pgsql@j-davis.com>
To: Jim C. Nasby <jim@nasby.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: long checkpoint_timeout
Date: Fri, 23 Feb 2007 12:23:08 -0800
Message-ID: <1172262188.10824.248.camel@dogma.v10.wvs> (raw)
In-Reply-To: <20070223200215.GA11743@nasby.net>
References: <1172254469.10824.243.camel@dogma.v10.wvs>
<20070223200215.GA11743@nasby.net>
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?
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@j-davis.com, jim@nasby.net
Subject: Re: long checkpoint_timeout
In-Reply-To: <1172262188.10824.248.camel@dogma.v10.wvs>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox