From: | Christopher Weimann <cweimann(at)k12hq(dot)com> |
---|---|
To: | Vincent Stoessel <vincent(at)xaymaca(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: MySQL vs. PostgreSQL |
Date: | 2002-07-25 23:02:33 |
Message-ID: | 20020725190232.A109@mail.k12us.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jul 25, 2002 at 04:01:26PM -0400, Vincent Stoessel wrote:
> >
> > In my personal experiance PostgreSQL runs circles around MySQL.
> > Specifically MySQL makes lousy choices about which indexes to
> > use and requires me to give it hints. PostgreSQL just works.
> >
>
> I use both databases depending on the project requirements. But
> I find that mysql is more willing to use your indexes than
> postgres is.
My experience differs greatly from yours here.
> I also like that fact that I can tell mysql to use
> specific indexes if I feel like it.
I haven't needed to do this on PostgreSQL ( but it would be nice )
but I have needed to on MySQL because of its bad index choices.
> Plus the ability to add ,delete
> and modify the name and type of any field , table or database is a
> fat fingered admin's dream.
>
Yes, that is something I miss on the sites where I use PostgreSQL.
( yes I use MySQL as well )
> I love postgres, but sometimes the mysql
> bashing goes way out hand on the list.
> No war please.
>
I would hardly call what I said bashing. I would call it the
facts in my experience with both products.
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Luc Lachance | 2002-07-25 23:40:32 | Re: select distinct error ? |
Previous Message | Doug McNaught | 2002-07-25 22:31:23 | Re: regression test |