Re: MySQL vs PostgreSQL. - Mailing list pgsql-hackers

From Shridhar Daithankar
Subject Re: MySQL vs PostgreSQL.
Date
Msg-id 3DA721A7.12077.A0A79DE@localhost
Whole thread Raw
In response to MySQL vs PostgreSQL.  (Antti Haapala <antti.haapala@iki.fi>)
List pgsql-hackers
On 11 Oct 2002 at 16:20, Antti Haapala wrote:

> Check out:
>   http://www.mysql.com/doc/en/MySQL-PostgreSQL_features.html

Well, I guess there are many threads on this. You can dig around archives..
> > Upgrading MySQL Server is painless. When you are upgrading MySQL Server,
> > you don't need to dump/restore your data, as you have to do with most
> > PostgreSQL upgrades.
> 
> Ok... this is true, but not so hard - yesterday I installed 7.3b2 onto my
> linux box.

Well, that remains as a point. Imagine a 100GB database on a 150GB disk array. 
How do you dump and reload? In place conversion of data is an absolute 
necessary feature and it's already on TODO.

> Of course PostgreSQL isn't yet as fast as it could be. ;)

Check few posts I have made in last three weeks. You will find that postgresql 
is fast enough to surpass mysql in what are considered as mysql strongholds. Of 
course it's not a handy win but for sure, postgresql is not slow.

And for vacuum thing, I have written a autovacuum daemon that can automatically 
vacuum databases depending upon their activity. Check it at 
gborg.postgresql.org. (I can't imagine this as an advertisement of myself but 
looks like the one)

Let thread be rested. Postgresql certaily needs some maketing hand but refuting 
claims in that article is not the best way to start it. I guess most hackers 
would agree with this..


ByeShridhar

--
Cat, n.:    Lapwarmer with built-in buzzer.



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: MySQL vs PostgreSQL.
Next
From: "Shridhar Daithankar"
Date:
Subject: Re: Peer to peer replication of Postgresql databases