Generally speaking, MySQL is ideal for small-to-mid range sites, although it will support larger loads.
Postgresql is where you'll end up going for performance when you approach larger sites. It can compete with Oracle in situations MySQL cannot. This is off the top of my head, so I don't have any numbers or anything, but thats what I've come to understand. On Wed, Jun 18, 2008 at 1:44 PM, Sebastian Bauer <[EMAIL PROTECTED]> wrote: > i was using mysql for about 5y but now postgresql is better for me because > of exclusive locks and full transactions support > > xhenxhe pisze: > > Thanks for the info. So I guess I can just stick with MySQL since I > know it well... unless at some future date I find a compelling reason > to swtich to PostgreSQL > > On Jun 18, 10:31 am, Tim Chase <[EMAIL PROTECTED]> wrote: > > > This may be a loaded question, but I was reading a blog post > that postgresql is the preferred database for Django. Is this > true? If so, why? > > > I think the "preference" comes from "that's what we happen to be > using, so we may be be better equipped to answer questions you > might have" as there seems to be a recommendation in the 0.96 docs > > http://www.djangoproject.com/documentation/0.96/install/ > > but that preference has been removed in the current docs > > http://www.djangoproject.com/documentation/install/ > > I can't speak for the authors of the documentation, but I've > found that PostgreSQL is generally more complete when it comes to > standards compliance, though I must say that MySQL has been > rapidly closing that gap. It used to be that MySQL lacked Views, > stored procedures, and my biggest pet-peeve, sub-selects (there > may have been some additional features I'm missing in this list). > Postgres also has greater support for GIS info if that's > important to you. > > MySQL did have native full-text and replication features before > Postgres (which had them as add-on modules, but not natively). > > Postgres has taken a path of "get it correct & complete, then > optimize" while MySQL seems to have taken the path of "get it > fast and then fill in the missing features". > > The last shoot-out I saw, MySQL performed better under light to > modest load (especially with read-only queries), but started > choking at higher sustained load, while Postgres was a tiny bit > slower at low to medium volumes but just kept on truckin' at > higher sustained load. And Postgres is no slouch in the speed > department anyways. > > These days, I find them fairly equal in functionality -- MySQL > has added support for most of the missing elements, and Postgres > has added support for full-text and native replication. Speed is > also pretty comparable these days. I personally find MySQL a > little easier to administer but that's my own experience. > > Additionally, you're often more likely to find MySQL on most > hosting company servers. But if you're building your own server, > then you can install whatever you like. > > -tim > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
