At 3:19 PM +0200 22/4/02, Maxim Maletsky \(PHPBeginner.com\) wrote: >PostgreSQL is the best choice on my opinion. mySQL might fail on a large >DB.
I'd love to see an example or detailed anecdote of MySQL failing on a large DB. I keep seeing comments saying MySQL is not robust, but in my experience it's nearly bulletproof. I have thrown some pretty large tasks at it, and even on my lowly server it has handled everything with great agility. The only times it has caused me problems are when: 1. a hard crash corrupted a table. Easily fixed once the problem was pinpointed. 2. a mysql_pconnect escaped into a live site and every apache process finished up holding open a connection to the database. This is nothing less than a DB misconfiguration -- the default timeout for pconnections is like 8 hours when 2 minutes would be more appropriate. ...R. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
