| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: long checkpoint_timeout |
| Date: | 2007-02-23 20:23:08 |
| Message-ID: | 1172262188.10824.248.camel@dogma.v10.wvs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2007-02-23 21:30:56 | Re: which Xeon processors don't have the context switching problem |
| Previous Message | Jim C. Nasby | 2007-02-23 20:02:15 | Re: long checkpoint_timeout |