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

From: "Tony Lausin" <tonylausin(at)gmail(dot)com>
To: "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>
Cc: "Philip Hallstrom" <postgresql(at)philip(dot)pjkh(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Is PostgreSQL an easy choice for a large CMS?
Date: 2006-05-01 19:08:37
Message-ID: 296cdcaf0605011208g63208033if9f43779d8d84e6b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> And from reading that page, one can see that InnoDB tables are still
> considered to be kind of the "red headed step child" of table handlers
> by the mysql crew. Sad, because it's the only table handler they have
> than can truly handle any real concurrency of reads and writes mixed
> together (it's a true MVCC modeled table handler).

I was just reading something about InnoDB. I've largely ignored it
myself, but basically MySQL is developing their own in-house engine
because InnoDB is now owned by Oracle. And I think there's been
problems with MySQL suddenly going from InnoDB to myISAM kinda out of
the blue. So much for transactions, right? :)

Anthony

In response to

Browse pgsql-general by date

  From Date Subject
Next Message EbGrooveCb 2006-05-01 20:16:15 Using the REPLACE command to replace all vowels
Previous Message Wes 2006-05-01 18:45:35 Re: Leading substrings - alternatives with 8.1.3?