X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 851085280C for ; Sat, 30 Jul 2005 18:59:46 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64919-02 for ; Sat, 30 Jul 2005 21:59:41 +0000 (GMT) Received: from mail.travelamericas.com (unknown [206.130.134.147]) by svr1.postgresql.org (Postfix) with SMTP id A510152AB4 for ; Sat, 30 Jul 2005 18:59:29 -0300 (ADT) Received: (qmail 4203 invoked from network); 30 Jul 2005 21:59:32 -0000 Received: from unknown (HELO ?10.0.0.253?) (10.0.0.253) by verkiel.travelamericas.com with SMTP; 30 Jul 2005 21:59:32 -0000 Message-ID: <42EBF842.5090306@travelamericas.com> Date: Sat, 30 Jul 2005 14:59:30 -0700 From: Chris Travers User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: N/A Cc: Chris Travers , pgsql-admin@postgresql.org Subject: Re: Question on placing database on a network attached storage References: <01a201c59541$59648560$6401a8c0@irene> <42EBE690.2040100@metatrontech.com> <01c901c5954d$869ec660$6401a8c0@irene> In-Reply-To: <01c901c5954d$869ec660$6401a8c0@irene> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.037 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200507/260 X-Sequence-Number: 18316 N/A wrote: >Chris, > >The NAS is a Network Appliance 920c. I understand that an individual file >while be "intact" during a snap, (not sure I believe it, but that's what I'm >told). > Depending on the way that data is journalled, this may be a possibility (istr XFS is able to do this). > The NAS may be able to monitor the state of an individual file and >not "snap" it if it is on an "open" state or has a pending write, or some >such, but as the NAS has no knowledge of groups of files that need to exist >in a known state, (it deals on the file level), it cannot guarantee a >consistent state across a group of files. > That is a serious concern. Every table in PostgreSQL consists of at least one physical file. Transactions may touch several of these files. While it is not impossible to solve this problem (as I mentioned, I think XFS has this capability), it is hardly trivial or something you would normally expect. Also I wonder what the impact of several Postmasters trying to access data over NFS would be. Best Wishes, Chris Travers