X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 231553A48E6 for ; Thu, 20 Jan 2005 19:13:27 +0000 (GMT) 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 62393-03 for ; Thu, 20 Jan 2005 19:13:22 +0000 (GMT) Received: from noao.edu (astronomyinspanish.org [140.252.1.54]) by svr1.postgresql.org (Postfix) with ESMTP id 23E073A48F6 for ; Thu, 20 Jan 2005 19:13:22 +0000 (GMT) X-TFF-CGPSA-Version: 1.4f1 X-TFF-CGPSA-Filter: Scanned Received: from [140.252.14.8] (HELO weaver.tuc.noao.edu) by noao.edu (CommuniGate Pro SMTP 4.2.8) with ESMTP-TLS id 16158049; Thu, 20 Jan 2005 12:13:20 -0700 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by weaver.tuc.noao.edu (8.12.8/8.12.8) with ESMTP id j0KJDH32023133; Thu, 20 Jan 2005 12:13:18 -0700 Message-ID: <41F002CD.3040900@noao.edu> Date: Thu, 20 Jan 2005 12:13:17 -0700 From: Steve Wampler User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mitch Pirtle Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering References: <200501201503.31241.herve@elma.fr> <200501201542.06645.herve@elma.fr> <41EFC569.6030800@familyhealth.com.au> <200501200933.42951.darcy@wavefire.com> <330532b6050120104246597d2a@mail.gmail.com> In-Reply-To: <330532b6050120104246597d2a@mail.gmail.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-noao.edu-MailScanner-Information: Please contact the ISP for more information X-noao.edu-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.033 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/336 X-Sequence-Number: 10026 Mitch Pirtle wrote: > Which brings up another question: why not just cluster at the hardware > layer? Get an external fiberchannel array, and cluster a bunch of dual > Opterons, all sharing that storage. In that sense you would be getting > one big PostgreSQL 'image' running across all of the servers. This isn't as easy as it sounds. Simply sharing the array among hosts with a 'standard' file system won't work because of cache inconsistencies. So, you need to put a shareable filesystem (such as GFS or Lustre) on it. But that's not enough, because you're going to be running separate postgresql backends on the different hosts, and there are definitely consistency issues with trying to do that. So far as I know (right, experts?) postgresql isn't designed with providing distributed consistency in mind (isn't shared memory used for consistency, which restricts all the backends to a single host?). -- Steve Wampler -- swampler@noao.edu The gods that smiled on your birth are now laughing out loud.