Re: Is PostgreSQL an easy choice for a large CMS? - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: Is PostgreSQL an easy choice for a large CMS?
Date
Msg-id 20060504195005.GW97354@pervasive.com
Whole thread Raw
In response to Re: Is PostgreSQL an easy choice for a large CMS?  ("Tony Lausin" <tonylausin@gmail.com>)
Responses Re: Is PostgreSQL an easy choice for a large CMS?
Re: Is PostgreSQL an easy choice for a large CMS?
List 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@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: how can i view deleted records?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Is PostgreSQL an easy choice for a large CMS?