Message-ID: <429360FB.1040106@commandprompt.com>
Date: Tue, 24 May 2005 10:14:35 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324)
MIME-Version: 1.0
To: Amit V Shah <ashah@tagaudit.com>
Cc: "'pgsql-performance@postgresql.org'" <pgsql-performance@postgresql.org>
Subject: Re: Need help to decide Mysql vs Postgres
References: <0C072E7CC947D511AC9600A0CC7341200256CF03@xeon400.tagaudit.com>
In-Reply-To: <0C072E7CC947D511AC9600A0CC7341200256CF03@xeon400.tagaudit.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> 
> I am not trying to start a mysql vs postgres war so please dont
> misunderstand me .... I tried to look around for mysql vs postgres articles,
> but most of them said mysql is better in speed. However those articles were
> very old so I dont know about recent stage. Please comment !!!

It is my experience that MySQL is faster under smaller load scenarios. 
Say 5 - 10 connections only doing simple SELECTS. E.g; a dymanic website.

It is also my experience that PostgreSQL is faster and more stable under
consistent and heavy load. I have customers you regularly are using up 
to 500 connections.

Note that alot of this depends on how your database is designed. Foreign 
keys slow things down.

I think it would be important for you to look at your overall goal of 
migration. MySQL is really not a bad product "IF" you are willing to 
work within its limitations.

PostgreSQL is a real RDMS, it is like Oracle or DB2 and comes with a 
comparable feature set. Only you can decide if that is what you need.

Sincerely,

Joshua D. Drake
Command Prompt, Inc.


-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/