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 0FB139FA2BC; Tue, 23 May 2006 01:02:47 -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 89407-03; Tue, 23 May 2006 01:02:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- 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 5360B9F9CAA; Tue, 23 May 2006 01:02:35 -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 k4N42P9j017817; Tue, 23 May 2006 00:02:25 -0400 (EDT) To: Jeff Frost cc: Simon Riggs , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: <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> <1879.1148055449@sss.pgh.pa.us> <1941.1148055645@sss.pgh.pa.us> <1148056900.2646.687.camel@localhost.localdomain> <1148246910.2755.70.camel@localhost.localdomain> Comments: In-reply-to Jeff Frost message dated "Mon, 22 May 2006 20:59:30 -0700" Date: Tue, 23 May 2006 00:02:25 -0400 Message-ID: <17816.1148356945@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/302 X-Sequence-Number: 21834 Jeff Frost writes: > I tried both pulling the plug on the CIFS server and unsharing the CIFS share, > but pgbench continued completely unconcerned. I guess the failure mode of the > NAS device in the customer colo must be something different that I don't yet > know how to simulate. I suspect I'll have to wait till it happens again and > try to gather some more data before restarting the NAS device. Thanks for all > your suggestions guys! I'm still thinking that the simplest explanation is that $PGDATA/pg_clog/ is on the NAS device. Please double-check the file locations. regards, tom lane