From: | Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Oscar Calderon <ocalderon(at)solucionesaplicativas(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL isn't enough scalable as Oracle or DB2 |
Date: | 2014-04-21 20:53:54 |
Message-ID: | 53558562.5090106@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>> http://reshmaparveen.blogspot.com/2009/12/postgresql-system-architecture.html
>>
>> I was reading the Scalability section, where it mentions this:
>>
>> Even though the query receiving thread is alone it still offers better or
>> equal scalability to MySQL. In terms of multi-computer scalability,
>> PostgreSQL does not scale at all.
> This statement was wrong in 2009 and it's still wrong today. We were
> using slony well before 2009 with read slaves to handle massive read
> loads. While muti-master setups are still pretty new in the PostgreSQL
> universe, there are some seups like Bucardo. Of course this paper
> doesn't mention whether or not they're referring to shared storage or
> separate storage, and what kind of loads would be expected. RedHat
> Cluster server can provide failover etc. There are several different
> options that pre-date this article.
>
> The fact that it then goes on the sing the praises of MySQL clusters
> as reliable and stable makes me question the whole article.
>
>
And, the page mentioned above seems to be copied verbatim (and without
attribution) from a 2004 paper here:
http:// www.benjaminarai.com/downloads/whitepapers/postgresql.doc
-- Korry
From | Date | Subject | |
---|---|---|---|
Next Message | Oscar Calderon | 2014-04-21 22:39:19 | Re: PostgreSQL isn't enough scalable as Oracle or DB2 |
Previous Message | Scott Marlowe | 2014-04-21 19:23:43 | Re: PostgreSQL isn't enough scalable as Oracle or DB2 |