X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 97CAA566D2 for ; Fri, 11 Mar 2005 16:40:27 +0000 (GMT) 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 91962-03 for ; Fri, 11 Mar 2005 16:40:16 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4F3BD565AC for ; Fri, 11 Mar 2005 16:40:15 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2BGeCbu003234; Fri, 11 Mar 2005 11:40:12 -0500 (EST) To: "Milen A. Radev" Cc: Michael Fuhr , pgsql-admin@postgresql.org Subject: Re: Too frequent warnings for wraparound failure In-reply-to: <42316D98.9030507@securax.org> References: <42301107.6010901@securax.org> <20050310155734.GA86004@winnie.fuhr.org> <423079B3.8050601@securax.org> <15917.1110474897@sss.pgh.pa.us> <42316D98.9030507@securax.org> Comments: In-reply-to "Milen A. Radev" message dated "Fri, 11 Mar 2005 12:06:16 +0200" Date: Fri, 11 Mar 2005 11:40:11 -0500 Message-ID: <3233.1110559211@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/181 X-Sequence-Number: 16679 "Milen A. Radev" writes: > Tom Lane wrote: >> So you managed to execute about 6000 transactions in those two seconds. >> Doing what? > Well that could be the problem - I'm 99.99% positive we do not execute > so many transactions - may be 30-40 thousand per day and that's only for > one relatively busy DB. The example database ("xxx1") you've chosen is > not used at all. As most of the other databases in that cluster. It doesn't matter --- all the age counts are going up at exactly the same rate. Somewhere you've got a client that's issuing dummy transaction starts at an insane rate. Some attention to "top" output on the server might help identify it ;-) regards, tom lane