X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A25E69FA293 for ; Thu, 18 May 2006 10:46:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 52441-02 for ; Thu, 18 May 2006 10:46:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 87A6A9F9C18 for ; Thu, 18 May 2006 10:46:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4IDjsbr013180; Thu, 18 May 2006 09:45:54 -0400 (EDT) To: Jeff Frost cc: Simon Riggs , pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: <1147728181.5074.73.camel@localhost.localdomain> <1147733193.5074.87.camel@localhost.localdomain> <1147781287.2646.32.camel@localhost.localdomain> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <7583.1147922685@sss.pgh.pa.us> <8269.1147927511@sss.pgh.pa.us> Comments: In-reply-to Jeff Frost message dated "Wed, 17 May 2006 23:09:07 -0700" Date: Thu, 18 May 2006 09:45:54 -0400 Message-ID: <13179.1147959954@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/261 X-Sequence-Number: 21793 Jeff Frost writes: > Hrmmm...my pgbench died with an integer out of range error: That's normal, if you run it long enough without re-creating the tables. It keeps adding small values to the balances, and eventually they overflow. (Possibly someone should fix it so that the deltas are uniformly distributed around zero, instead of being always positive.) regards, tom lane