From: Steve Wampler <swampler@noao.edu>
To: Mitch Pirtle <mitch.pirtle@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Thu, 20 Jan 2005 12:13:17 -0700
Message-ID: <41F002CD.3040900@noao.edu> (raw)
In-Reply-To: <330532b6050120104246597d2a@mail.gmail.com>
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swampler@noao.edu, mitch.pirtle@gmail.com
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <41F002CD.3040900@noao.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox