Comments on: postgres and mysql comparison paper

By: thebigdog

thebigdog — Mon, 11 Aug 2008 16:21:02 +0000

here are some other features that i enjoy with pgsql: stored procedures, table inheritance and postgis is killer. I have used postgresql to build a killer image map system similar to google earth. postgresql is where it is at.

By: robbat2

robbat2 — Wed, 06 Aug 2008 19:16:37 +0000

We use both at my work. MySQL for the old stuff, postgres for the new, with a very slow migration between the two.

Also of interest for you pgpool2 (compare to NDB).

By: John McFarlane

John McFarlane — Wed, 06 Aug 2008 17:38:52 +0000

I also think this is a great idea, especially if you can manage to avoid the FUD trap. It’s surprisingly easy to wind up sounding that way - even when you have no intentions of doing so :/

I think table inheritance, tsearch2, and point in time recovery are really nice features.

Best of luck

By: eggyknap

eggyknap — Wed, 06 Aug 2008 17:18:52 +0000

Several reasons, in no particular order:
1) Sane licensing. PostgreSQL is free, period. Should you want to mod MySQL, for instance, for commercial reasons, in some instances it can get sticky.

2) Better support for complex SQL (where “complex” == “anything but really simple SQL”)

3) *MUCH* better support for stored procedures, including procedures written in languages your developers are likely to understand (Perl, Python, PHP, Java, even (shameless plug) LOLCODE).

4) You don’t even have the option of screwing yourself with ISAM tables

This is what comes to mind right off…

By: Rich

Rich — Wed, 06 Aug 2008 16:39:19 +0000

You’ve looked here, I hope?

http://archives.postgresql.org/pgsql-jobs/

By: goozbach

goozbach — Wed, 06 Aug 2008 16:08:12 +0000

I think this is a good idea.

I really wish I could get us moved off of MySQL to PostgreSQL here at $DAYJOB.