Both databases work well for what they are intended to do. Either database will have good basic performance, however PostgreSQL has had more advanced features and stability in the past some of which MySQL has worked on gaining.
Last I heard there was still issues with complex operations and table locking with MySQL (I don't use MySQL anymore). If you use persistent connections PostgreSQL performance will equal, be greater than or slighly less than MySQL performance (depending on what you are doing). There are also other database choices available for example Firebird (open source version of Interbase), and many others. Asking what is the best database generally is an answer that can't easily be answered, especially on mailing lists without causing enthusiastic believers of a database to become over stimulated. You should take into consideration what databases are available to you, are you using your own server so you have (near) total control, are you using shared hosting so are limited by what your hosting provider supplies? Additionally consider the ability for the database to scale, ease of management, support, and documentation quality. Both PostgreSQL and MySQL have excellent online help communities and both have excellent documentation. With that said, for my purposes I prefer PostgreSQL, I like the performance and the stability I have seen from PostgreSQL, I develop intranet applications that need to do complex reporting while providing data entry services at the same time. Weigh everyones opinions, also consider deploying both and doing some of your own testing to see which will work best for you, it takes a while but it will give you more concrete information. Jason > Youy are unlikely to egt balanced asvice on this in the MySQL or > Postgress lists -after all those people have already made thier decision. > > I haven't used Postgress much - but basically... > > > Mysql - available on loads of hosting packages, very large user base. > > PostgreSQL - better adherance to ANSII standards, resulting in more > portable code. > Implements VIEWS, subselects and foriegn keys. > > Mysql is faster (as long as you don't need the missing features) > It is better established, and things like subselects are being worked > on, foriegn keys are already partially implemented. > > The docs for both projects have sections on camparing to the other (I > think they both cheat a bit and compare thier newest version to a > slighlty older version of the other project) > > Sean > > > Rick Emery wrote: > > You accidentally published this to the wrong email list. I assume you meant to >send this > > to the MySQL email list. > > > > ----- Original Message ----- > > From: "Miro Kralovic" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, December 23, 2002 9:10 AM > > Subject: [PHP] MySQL vs PostgreSQL > > > > > > > >>Hi, > >> > >>I'm just deciding which DB to use for my projects and I'm not clear with one > >>thing... When considering a database for web, is MySQL good enough? I read > >>it only supports table locking, which is not very satisfying in such a > >>multiuser environment as the internet.. > >> > >>Based on your experience, what are pros and cons of MySQL and why most of > >>you prefer to use MySQL to PostgreSQL, which is aparently more powerful.. > >> > >>Thanks for your opinions.. > >>Miro.. > >> > >> > >> > >>-- > >>PHP General Mailing List (http://www.php.net/) > >>To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > > > > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
