X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 417895337B for ; Mon, 16 May 2005 01:39:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 01479-09 for ; Mon, 16 May 2005 04:39:15 +0000 (GMT) Received: from mr2.surnet.cl (smtp2.surnet.cl [216.155.73.163]) by svr1.postgresql.org (Postfix) with ESMTP id B16E653323 for ; Mon, 16 May 2005 01:39:14 -0300 (ADT) Received: from smtp2.surnet.cl (216.155.73.169) by mr2.surnet.cl (7.0.031.3) id 4259ADFA007A66DE; Mon, 16 May 2005 00:39:49 -0400 Received: from smtp1.surnet.cl (smtp1.surnet.cl []) by mr2.surnet.cl ([216.155.73.169]); Mon, 16 May 2005 04:39:48 +0000 Received: from cluster.surnet.cl (216.155.73.164) by smtp1.surnet.cl (7.0.031.3) id 42587C6E00648D5B; Mon, 16 May 2005 00:38:44 -0400 Received: from localhost (200.85.219.173) by cluster.surnet.cl (7.0.024) id 4276578F001DF245; Mon, 16 May 2005 00:39:13 -0400 Received: by localhost (Postfix, from userid 1000) id 8C0FEC32DDE; Mon, 16 May 2005 00:39:20 -0400 (CLT) Date: Mon, 16 May 2005 00:39:20 -0400 From: Alvaro Herrera To: David Parker Cc: pgsql-performance@postgresql.org Subject: Re: checkpoint segments Message-ID: <20050516043920.GA9292@surnet.cl> References: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.233 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, FORGED_RCVD_HELO, RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_NJABL_PROXY X-Spam-Level: *** X-Archive-Number: 200505/299 X-Sequence-Number: 12463 On Sun, May 15, 2005 at 08:22:13PM -0400, David Parker wrote: > In the database log at that time there was a "recycling transaction log" > message which seems to correspond to the time when the clients were > paused, though I don't have it concretely correlated. Maybe what you need is make the bgwriter more aggressive, so that I/O is more evenly spread between checkpoint intervals -- that way, at checkpoint there's less work to do. > I've seen these messages in the log before, and am aware of the need to > increase checkpoint_segments, but I wasn't aware that recycling a > transaction log could be that damaging to performance. There may have > been some local hiccup in this case, but I'm wondering if recycling is > known to be a big hit in general, and if I should strive to tune so that > it never happens (if that's possible)? Well, recycling is actually a *good* thing -- it saves you from having to remove WAL segment files and allocate new files for the new logs. So what you really want doesn't have anything to do with the recycling itself, but rather with the simultaneous checkpoint that's going on at the same time. -- Alvaro Herrera () Licensee shall have no right to use the Licensed Software for productive or commercial use. (Licencia de StarOffice 6.0 beta)