From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Vratislav_Morkus(at)lmc(dot)cz |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL vs. MySQL |
Date: | 2005-08-01 17:08:13 |
Message-ID: | 20050801170813.GD60019@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 01, 2005 at 06:44:50PM +0200, Vratislav_Morkus(at)lmc(dot)cz wrote:
> Hi all,
> I am sorry for a stupid easy question, but I'am PostgreSQL novice.
> Our development team has encountered problem with trying to install and
> maintain cluster (pgcluster) on our production database. So they have
> decided to switch the entire solution to MySql database.
> a) have you got any good/bad experience with administering and running
> cluster on PostrgeSQL DB?
> b) would u switch PostgreSQL to MySql (7.4 --> 4.1) and why?
For pgcluster help, your best bet is to hit either their mailling list
or their forums. http://pgfoundry.org/projects/pgcluster/ has more info.
As for MySQL, http://sql-info.de/mysql/gotchas.html has about 100
different reasons why you don't want to use MySQL. Some favorites:
Feb. 31st is a valid date
Data will be silently truncated if it overflows
1/0 = NULL
count(*) is an approximation
easy to configure in such a way that it's not ACID
...
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2005-08-01 17:19:19 | Re: New MySQL to PostgreSQL Migration Guide |
Previous Message | Jim C. Nasby | 2005-08-01 17:01:03 | Re: New MySQL to PostgreSQL Migration Guide |