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 AD6029FA294 for ; Thu, 18 May 2006 00:25:09 -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 83909-01 for ; Thu, 18 May 2006 00:25:00 -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 6D2EF9F9CEE for ; Thu, 18 May 2006 00:25:00 -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 k4I3OjSG007584; Wed, 17 May 2006 23:24:47 -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> Comments: In-reply-to Jeff Frost message dated "Wed, 17 May 2006 09:11:51 -0700" Date: Wed, 17 May 2006 23:24:45 -0400 Message-ID: <7583.1147922685@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/246 X-Sequence-Number: 21778 Jeff Frost writes: > Was the 3,000 transactions per minute helpful? What other evidence should I > be looking for? Did you try generating a test case using a long sleep() as a replacement for the archive_command script? If there is a PG bug here it shouldn't be that hard to expose it in a simple test case. I'm up to my armpits in other stuff and don't have time to try it myself... regards, tom lane