Re: [OT] MySQL is bad, but THIS bad? - Mailing list pgsql-hackers

From Mark Kirkwood
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 446D224B.8020909@paradise.net.nz
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  (Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>)
List pgsql-hackers
Christopher Kings-Lynne wrote:
>> And MySQL is much closer to being a competitor now than they were in
>> 4.1. And feature-wise they'll probably equal PostgreSQL in the next
>> release. Will the features be anywhere near as robust or well thought
>> out? No. But in a heck of a lot of companies that doesn't matter.
> 
> Don't forget that they got nested transactions and PITR both before us. 
>  They will also shortly have really nice partitioning before us...
> 
> ...don't underestimate their development speed.
> 

Second that. In addition they have (early) in-memory multi-node 
clustering and Jim Starkey is writing them a new transactional storage 
engine to replace the probably-soon-to-be-license-hampered Innodb...

Cheers

Mark


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: [OT] MySQL is bad, but THIS bad?
Next
From: Mark Dilger
Date:
Subject: Re: text_position worst case runtime