Re: FN-FORUM: Recruitment Software - php/mysql or perl - Why MySQL? Why not Postgre SQL?

date posted 31st January 2007 14:33

I think that's the problem. MySQL is fast, BUT if you start turning on
all the stuff you would expect a database to do, then it just becomes
another DB.

MySQL feels like it is playing catch-up with Postgre, but doesn't have
the maturity.

I've been evaluating both for a server configuration and am landing
squarely in the Postgre camp.

I've heard some nightmare restore stories for MySQL, but this is where
people go for speed speed speed rather than actually writing good
caching /sql etc, and rely on getting the fastest db.

You don't seem to get that with Postgre.

*shrug*

Ben Moxon wrote:
> It's one of those things I sort of know but haven't really acted on.
>
> My recollection of when I was first making this decision was that
> because it was more of a "fast filesystem" and less of a real
> database, MySQL was a good choice for simple web stuff, whereas
> Postgres was better for "real" database applications where one wanted
> transactions and whathaveyou.
>
> I'm guessing that as MySQL has sprouted features there isn't really
> much between them now performance-wise - although features designed-in
> to Postgres from the start presumably give it an advantage there - but
> MySQL is more ubiquitous and a familliar choice, particularly for web
> developers.
>
> Is that a fair assessment? What would be the most compelling reasons
> for switching away from MySQL?
>
> thanks,
>
> -ben
>
>