Re: postgresql clustering

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: Tino Wildenhain <tino(at)wildenhain(dot)de>
Cc: Daniel Duvall <the(dot)liberal(dot)media(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgresql clustering
Date: 2005-09-29 14:43:04
Message-ID: 36e682920509290743h29849321je0052b30ad0bcee4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/29/05, Tino Wildenhain <tino(at)wildenhain(dot)de> wrote:
>
> Well, I dont know why many people believe parallel execution
> automatically means high performance. Actually most of the time
> the performance is much worser this way.
> If your dataset remains statically and you do only read-only
> requets, you get higher performance thru load-balancing.
> If howewer you do some changes to the data, the change has to
> be propagated to all nodes - which in fact costs performance.
> This highly depends on the link speed between the nodes.

I think you should clarify that the type of clustering you're discussing is
the, "shared-nothing" model which is most prevalent in open-source
databases. Shared-disk and shared-memory clustered systems do not have the
"propagation" issue but do have others (distributed lock manager, etc).
Don't make blind statements. If you want more information about "real-world"
clustering, read the research for DB2 (Mainframe) and Oracle RAC.

--
Respectfully,

Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
http://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2005-09-29 15:05:47 Re: PCTFree Results
Previous Message Bruce Momjian 2005-09-29 14:40:51 Re: Added documentation about caching, reliability