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 0E2DC9FA226 for ; Thu, 18 May 2006 01:45:32 -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 89643-10 for ; Thu, 18 May 2006 01:45:26 -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 13F379FA218 for ; Thu, 18 May 2006 01:45:25 -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 k4I4jBcG008270; Thu, 18 May 2006 00:45:11 -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> Comments: In-reply-to Jeff Frost message dated "Wed, 17 May 2006 21:39:40 -0700" Date: Thu, 18 May 2006 00:45:11 -0400 Message-ID: <8269.1147927511@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/249 X-Sequence-Number: 21781 Jeff Frost writes: > I seem to get alot of these: > May 17 21:34:04 discord postgres[20573]: [5-1] WARNING: could not rename file > "pg_xlog/archive_status/000000010000000000000001.ready" to > May 17 21:34:04 discord postgres[20573]: [5-2] > "pg_xlog/archive_status/000000010000000000000001.done": No such file or > directory That seems odd ... > Currently I'm using pgbench to generate WAL rollover, do you guys have any > other handy testing tools for this sort of job or is this the best tool? pgbench seems like an OK load for this, although it doesn't start/end any new connections while running. I *think* that that's not critical --- my guess is that your observation of new connections hanging is just because each new connection has to run one startup transaction, and transactions in general are at risk of hanging --- but that could be wrong. Also, you could increase the rate of WAL generation by decreasing the checkpoint segments/timeout parameters, if you need to. regards, tom lane