Search Postgresql Archives

Re: postgre vs MySQL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 11, 2008 at 3:31 PM, Dann Corbit <DCorbit@xxxxxxxxx> wrote:
> > -----Original Message-----
>  > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-
>  > owner@xxxxxxxxxxxxxx] On Behalf Of rrahul
>  > Sent: Tuesday, March 11, 2008 6:48 AM
>  > To: pgsql-general@xxxxxxxxxxxxxx
>  > Subject:  postgre vs MySQL
>  >
>  >
>  > Hi,
>  >
>  > I am a database professional but have never used Postgre. My client
>  was
>  > exploring the posiblity of using Postgre instead of Mysql and wnated
>  to
>  > know
>  > the comments from the community.
>  > I waned you people you post your views on the following comparision
>  points
>  > 1] Performance

If you use InnoDB tables, and you should, then MySQL is actually
slower than PostgreSQL in most cases, and it gets worse the more load
you have and the more complex your DB is.

>  > 2] Scalablity

I've run databases with millions of rows with no problem on a multiway
system with 24 disks, and the performance was stellar.

>  > 3] community support

I have never found a mailing so willing and able to help than the
PostgreSQL mailing list.  The folks here are the experts, and they
never turn a problem away that I have seen.  They are insightful and
highly helpful.  I only wish other products especially commercial ones
could rival this level of committment by the developers, give this
sort of support.

>  > 4] Speed

Like I said, as long as you don't try something stupid, PostgreSQL has
been very quick on all the projects I've used.  Unless you make an
index that wont fit in RAM, and any database will dog on that.  (you
might get a shock with count(*) but that's because postgresql cares
about getting the answer right, not guessing).

>  > 5] ease of use

They have excellent drivers for Python, Perl, Java, C, stored
procedures can be written in just about any popular language, and the
help screens in the command line app are very good.

>  > 6] robustness

In ten years of using PostgreSQL I've never seen it crash,  Our entire
enterprise ran off PostgreSQL at our last company, and it was rock
solid, never skipping a beat.

>  >
>  > Any major clients of the two.
>  > You can add you own points too.
>
>  Consider the license differences for commercial use:
>
>  http://www.postgresql.org/docs/8.3/interactive/LEGALNOTICE.html
>
>  http://www.mysql.com/about/legal/licensing/
>

Like he said, PostgreSQL is really the only good choice for an open
source database that free.  I don't understand why people use MySQL at
all to be honest.

>
>
>  --
>  Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
>  To make changes to your subscription:
>  http://www.postgresql.org/mailpref/pgsql-general
>

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux