PostgreSQL versus MySQL (fwd)

Attachments:
Message as email (text/plain)

Author: Joel Dudley
Date:
Subject: PostgreSQL versus MySQL (fwd)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Boundary_(ID_e3NOKOHkKZWFYpJrn6nnOg)
Content-type: text/plain;    charset="iso-8859-1"

In my opinion the speed difference between PostgreSQL and MySQL is
negligible. Tim Perdue from SourceForge did a study a while back
demonstrating that the newer PostgreSQL was actually faster than MySQL in
some cases. Trigger and PL support in PGSQL is very nice and I have never
been let down by PostgreSQL. PostgreSQL is the foundational database for all
of my Genomics research projects. I am transparently bias on the subject
because I have been burned by MySQL a few times so take that into
consideration. A replication daemon for PostgreSQL is also coming along
nicely.

Joel Dudley
Faculty Research Associate
Arizona State University
Kumar Laboratory of Evolutionary Functional Genomics
http://lsweb.la.asu.edu/skumar/

-----Original Message-----
From: William Lindley [mailto:wlindley@wlindley.com]
Sent: Monday, June 24, 2002 9:13 PM
To: Phoenix Linux Users Group
Subject: Re: PostgreSQL versus MySQL (fwd)

In response to the earlier question, Scott Walters <phaedrus@illogics.org>
who is not on the PLUG list writes:

--------

PostgreSQL supports triggers, constraints, PL, subqueries, and serveral
other things.

MySQL supports replication, precompiled queries (huge speed up on resident
code), and is optimized for throughput in addition to speed.

Both of them are very fast, and out perform almost all commercial
databases, hands down.

I wouldn't sweat it too much either way unless you specificly need a
feature that only one or the other has. They are both excellent systems.

I'd use MySQL where speed was the biggist factor.

I'd use Postgres where complex reporting or building a large
("Enterprise") data warehouse was the concern.

-scott

________________________________________________
See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post
to the list quickly and you use Netscape to write mail.

PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

--Boundary_(ID_e3NOKOHkKZWFYpJrn6nnOg)
Content-type: text/html;    charset="iso-8859-1"
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: PostgreSQL versus MySQL (fwd)</TITLE>
</HEAD>
<BODY>

In my opinion the speed difference between PostgreSQL =
and MySQL is negligible. Tim Perdue from SourceForge did a study a =
while back demonstrating that the newer PostgreSQL was actually faster =
than MySQL in some cases. Trigger and PL support in PGSQL is very nice =
and I have never been let down by PostgreSQL. PostgreSQL is the =
foundational database for all of my Genomics research projects. I am =
transparently bias on the subject because I have been burned by MySQL a =
few times so take that into consideration. A replication daemon for =
PostgreSQL is also coming along nicely. 

Joel Dudley
 Faculty Research Associate
 Arizona State University
 Kumar Laboratory of Evolutionary Functional =
Genomics
 <A HREF=3D"http://lsweb.la.asu.edu/skumar/" =
TARGET=3D"_blank">http://lsweb.la.asu.edu/skumar/</A>

 

-----Original Message-----
 From: William Lindley [<A =
HREF=3D"mailto:wlindley@wlindley.com">mailto:wlindley@wlindley.com</A>]<=
/FONT>
 Sent: Monday, June 24, 2002 9:13 PM
 To: Phoenix Linux Users Group
 Subject: Re: PostgreSQL versus MySQL (fwd)

 

In response to the earlier question, Scott Walters =
<phaedrus@illogics.org>
 who is not on the PLUG list writes:


--------


PostgreSQL supports triggers, constraints, PL, =
subqueries, and serveral
 other things.


MySQL supports replication, precompiled queries (huge =
speed up on resident
 code), and is optimized for throughput in addition =
to speed.


Both of them are very fast, and out perform almost =
all commercial
 databases, hands down.


I wouldn't sweat it too much either way unless you =
specificly need a
 feature that only one or the other has. They are =
both excellent systems.


I'd use MySQL where speed was the biggist =
factor.


I'd use Postgres where complex reporting or building =
a large
 ("Enterprise") data warehouse was the =
concern.


-scott


________________________________________________
 See <A =
HREF=3D"http://PLUG.phoenix.az.us/navigator-mail.shtml" =
TARGET=3D"_blank">http://PLUG.phoenix.az.us/navigator-mail.shtml</A> if =
your mail doesn't post to the list quickly and you use Netscape to =
write mail.

PLUG-discuss mailing list  -  =
PLUG-discuss@lists.plug.phoenix.az.us
 <A =
HREF=3D"http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss" =
TARGET=3D"_blank">http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-=
discuss</A>


</BODY>
</HTML>=

--Boundary_(ID_e3NOKOHkKZWFYpJrn6nnOg)--

This message is part of the following thread:
	the complete thread tree sorted by date
	Lynn David Newton at
	Chris Cowan at