X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A17E8D934B for ; Fri, 23 Sep 2005 16:57:47 -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 62966-10 for ; Fri, 23 Sep 2005 19:57:43 +0000 (GMT) Received: from mail.travelamericas.com (unknown [206.130.134.147]) by svr1.postgresql.org (Postfix) with SMTP id 7118CD937D for ; Fri, 23 Sep 2005 16:57:42 -0300 (ADT) Received: (qmail 29414 invoked from network); 23 Sep 2005 19:57:44 -0000 Received: from unknown (HELO ?10.0.0.253?) (10.0.0.253) by verkiel.travelamericas.com with SMTP; 23 Sep 2005 19:57:44 -0000 Message-ID: <43345E36.1020201@travelamericas.com> Date: Fri, 23 Sep 2005 12:57:42 -0700 From: Chris Travers User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Spiegelberg, Greg" , pgsql-admin@postgresql.org Subject: Re: postgresql cluster on SAN References: <82E74D266CB9B44390D3CCE44A781ED96B500D@POSTOFFICE.cranel.local> In-Reply-To: <82E74D266CB9B44390D3CCE44A781ED96B500D@POSTOFFICE.cranel.local> 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.051 required=5 tests=[AWL=0.001, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200509/276 X-Sequence-Number: 19013 Spiegelberg, Greg wrote: >This is possible. Below is a brief recipe. > >1. Use Veritas Storage Foundation HA with Cluster File System. >2. Have a volume with cfs available to 2 or more systems via SAN. >3. Install PostgreSQL and be sure PGDATA is on the cfs mount >4. Create a Storage Checkpoint of cfs mount (read-write virtual copy) >5. Bring up PostgreSQL on node1 >6. Mount storage checkpoint on node2 >7. Start PostgreSQL on node2 > >Drawbacks? Heck yes. There are many and you should understand the >nature of Veritas Storage Checkpoints before using. > Drawback #1-- only works read-only on all but one node. And I am not even sure what will happen when you start writing on that one node... > I have tested it >though in conjunction with dblink() and some other proprietary API's we >use for load balancing and the potential is there to manage many large >SELECT's. > > Ok, but what happens when you start doing inserts, updates, and deletes. Somehow I think that PostgreSQL's dependance on shmem and semaphores will cause corruption in your database as soon as you start writing to it on both nodes. And I don't know enough about PostgreSQL's internal structure to know if writing on only one node is safe. Best Wishes, Chris Travers Metatron Technology Consulting