Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 77DC79FC25D for ; Fri, 23 Feb 2007 16:23:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 98251-02 for ; Fri, 23 Feb 2007 16:23:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from servata.com (ip-216-152-249-241.servata.com [216.152.249.241]) by postgresql.org (Postfix) with ESMTP id 0A7B59FC16E for ; Fri, 23 Feb 2007 16:23:24 -0400 (AST) Received: from [209.162.219.253] (helo=dogma.v10.wvs) by servata.com with esmtpa (Exim 4.50) id 1HKgwc-0005wg-GN; Fri, 23 Feb 2007 12:23:06 -0800 Subject: Re: long checkpoint_timeout From: Jeff Davis To: "Jim C. Nasby" Cc: pgsql-performance@postgresql.org In-Reply-To: <20070223200215.GA11743@nasby.net> References: <1172254469.10824.243.camel@dogma.v10.wvs> <20070223200215.GA11743@nasby.net> Content-Type: text/plain Date: Fri, 23 Feb 2007 12:23:08 -0800 Message-Id: <1172262188.10824.248.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.177 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200702/259 X-Sequence-Number: 23313 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