Giudice, Salvatore wrote:

I have had MySQL databases running in excess of 2 terrabytes handling up
to 700,000 inserts/hour on an 8 cpu machine. Try doing that with
PostgreSQL.


If you are just running SER or Asterisk, etc - you simply do not need
the increased feature set or the need to optimize postgreSQL.

As for the "production recommendation" you refer to, I would
respectufully disagree. If you are an enterprise comapny looking to
deploy an open-source DB, you will pick the one that has an established
support company to contract with. So, 'NO': postgreSQL is not
recommended for production environments. MYSQL AB provides enterprise
class support. PostgreSQL support consists of contracting with mom and
pop support shops, mailing lists, and irc. That simply will not be
acceptable for the enterprise user.

In the end, pick whichever one works for you with the least problems.
Maybe postgreSQL is easier for your people to support. Green pill or
blue pill, it's your choice...


-----Original Message-----
From: Mohit Muthanna [mailto:[EMAIL PROTECTED] Sent: Thursday, March 10, 2005 8:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] OT: Best DB


On Thu, 10 Mar 2005 19:14:36 -0500, Giudice, Salvatore
<[EMAIL PROTECTED]> wrote:


I vote for MySQL. PostgreSQL is fine, but MySQL handles much better
under extreme load. MySQL is also usually touted as being generally



I'd have to (respectfully) disagree with that... MySQL just cannot handle high load or large datasets... it's inherent design does not allow it to scale too well...

I lost countless hours trying to optimize disk / filesystem
distribution, SQL queries, kernel parameters etc. etc. to get MySQL to
_not crawl_. After many failed attempts, I switched to Postgres and
haven't looked back.

I personally believe there is a "right tool for the right job". MySQL
works great for small datasets and (relatively) lighter load. Infact,
it shines there. But don't expect it to perform as your database grows
in orders of magnitude.

Postgres is certainly a database that is "recommended" (IMHO) for
production environments. If you're a VoIP provider, and are trying to
provide a near "carrier-grade" service, postgres shines.

Moht.




Maybe I miss read, but doesn't the licensing of the newer releases of MySQL require companies to purchase a license? This would mean that while it is open source, it is not "free as in beer". This does not mean it is not a good DB, just that there may be more that just the costs of a support contract involved. This is why most distros still ship the last version before the license change. As for support, check out http://techdocs.postgresql.org/companies.php.


For terrabytes, you can ask on the PostgreSQL mailing lists and get numerous responses from people running DBs in the terrabyte range. I'm sure the MySQL lists have simular stories.


<rant>
The DB mailing lists are full of "to-from" and "success-failure" stories. Both camps post stories saying "we're #1!".


Personally, I go with what meets (and ideally exceeds) a projects needs. If after evaluating a projects needs there is not a clear winner, try the possibilities and determine for you self what works.

Asking "what database is best" is like asking "which Linux distro is the best". There is no clear answer and generally the only result is a massive thread with no clear answer.
</rant>


Just my $0.02CDN.

David Filion









David


_______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to