pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Sun, 23 Jan 2005 00:46:51 -0500
Message-ID: <m33bws1yus.fsf@knuth.knuth.cbbrowne.com> (raw)
References: <200501201503.31241.herve@elma.fr>
	<41EFC722.2050401@familyhealth.com.au>
	<41EFC8B5.9040902@commandprompt.com>
	<200501201607.51659.herve@elma.fr>

In the last exciting episode, herve@elma.fr (Hervé Piedvache) wrote:
> Le Jeudi 20 Janvier 2005 16:05, Joshua D. Drake a écrit :
>> Christopher Kings-Lynne wrote:
>> >>> Or you could fork over  hundreds of thousands of dollars for Oracle's
>> >>> RAC.
>> >>
>> >> No please do not talk about this again ... I'm looking about a
>> >> PostgreSQL solution ... I know RAC ... and I'm not able to pay for a
>> >> RAC certify hardware configuration plus a RAC Licence.
>> >
>> > There is absolutely zero PostgreSQL solution...
>>
>> I just replied the same thing but then I was thinking. Couldn't he use
>> multiple databases
>> over multiple servers with dblink?
>>
>> It is not exactly how I would want to do it, but it would provide what
>> he needs I think???
>
> Yes seems to be the only solution ... but I'm a little disapointed about 
> this ... could you explain me why there is not this kind of 
> functionnality ... it seems to be a real need for big applications no ?

If this is what you actually need, well, it's something that lots of
people would sort of like to have, but it's really DIFFICULT to
implement it.

Partitioning data onto different servers appears like it ought to be a
good idea.  Unfortunately, getting _exactly_ the right semantics is
hard.  

If the data is all truly independent, then it's no big deal; just have
one server for one set of data, and another for the other.

But reality normally is that if you _think_ you need a cluster, that's
because some of the data needs to be _shared_, which means you need to
either:

 a) Have queries that run across two databases, or

 b) Replicate the shared data between the systems.

We're likely back to the need for replication.
-- 
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne; rate me
http://www3.sympatico.ca/cbbrowne/rdbms.html
"It is the user who should parameterize procedures, not their
creators." -- Alan Perlis



view thread (131+ messages)  latest in thread

Message-ID: <m33bws1yus.fsf@knuth.knuth.cbbrowne.com>
Permalink:  ../m33bws1yus.fsf@knuth.knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m33bws1yus.fsf@knuth.knuth.cbbrowne.com

 · 

reply

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: cbbrowne@acm.org
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <m33bws1yus.fsf@knuth.knuth.cbbrowne.com>

* 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