Re: Is PostgreSQL an easy choice for a large CMS?

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tony Lausin <tonylausin(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Is PostgreSQL an easy choice for a large CMS?
Date: 2006-05-04 19:50:06
Message-ID: 20060504195005.GW97354@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Apr 30, 2006 at 12:32:53PM -0700, Tony Lausin wrote:
> >[ rotfl... ] MySQL will fall over under any heavy concurrent-write
> >scenario. It's conceivable that PG won't do what you need either,
> >but if not I'm afraid you're going to be forced into Oracle or one
> >of the other serious-money DBs.
> >
> > regards, tom lane
>
> Hi Tom,
>
> That's a scary idea - being forced into Oracle or Sybase. Isn't
> Slashdot.org still running strongly off of MySQL?

/. is also essentially read-only, or fairly close to it. The only sites
I'm aware of that have gotten MySQL to scale in a more write-heavy
environment are only able to do so by hand-crafting a clustering
solution of some kind, so that not everything is in the same server.
Livejournal is an example of this.

Why would a CMS have that high an update rate anyway? I'd think it would
only be somewhere between 10% and 25% DML...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-04 19:58:54 Re: Is PostgreSQL an easy choice for a large CMS?
Previous Message Jim C. Nasby 2006-05-04 19:42:29 Re: how can i view deleted records?