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

From Christopher Kings-Lynne
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 446D205C.9060306@calorieking.com
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: [OT] MySQL is bad, but THIS bad?
List pgsql-hackers
> 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
partitioningbefore us...
 

...don't underestimate their development speed.



pgsql-hackers by date:

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