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 77B439FA15C for ; Mon, 15 May 2006 18:39:26 -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 75780-08-2 for ; Mon, 15 May 2006 18:39:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id E9EBA9FA2C8 for ; Mon, 15 May 2006 18:39:18 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Mon, 15 May 2006 21:39:16 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 15 May 2006 16:39:16 -0500 Subject: Re: does wal archiving block the current client connection? From: Scott Marlowe To: Jeff Frost Cc: Simon Riggs , pgsql-admin@postgresql.org In-Reply-To: References: <1147728181.5074.73.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1147729156.9755.154.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 15 May 2006 16:39:16 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/203 X-Sequence-Number: 21735 On Mon, 2006-05-15 at 16:29, Jeff Frost wrote: > On Mon, 15 May 2006, Simon Riggs wrote: > > > On Mon, 2006-05-15 at 09:28 -0700, Jeff Frost wrote: > >> I've run into a problem with a PITR setup at a client. The problem is that > >> whenever the CIFS NAS device that we're mounting at /mnt/pgbackup has > >> problems > > > > What kind of problems? > > It becomes unwritable for whatever reason CIFS shares become unwritable. It's > a windows 2003 NAS device and a reboot solves the problem, but it leaves no > event logs on the windows side of things, so difficult to determine the root > cause. I don't think you need logs to figure out that the problem is that it's a Windows based NAS device. :) Seriously, we had BSD based NAS devices one place I worked, and the company making them switched to Win2k3 and after we had one or two do exactly what you're talking about, we just started building our own based on RedHat or BSD. Same hardware (we just formatted the drives on one of the ones that came with w2k3) and we never had another moment's problem with them. In other news... Does the archiver actually connect to the database?