guys... this is turning into a religious debate. I think the question has been answered.
both are excellent choices. and in the hands of an expert can be made to shine. On 08/07/2006, at 8:18 AM, Geert Vanderkelen wrote: > > Don Arbow wrote: >> On Jul 7, 2006, at 3:35 AM, Kenneth Gonsalves wrote: >>> another thing, your have to be careful about postgresql is that data >>> recovery tools for a borked db for postgres are rare to the point of >>> non-existence, whereas there are lots of them for mysql >> >> >> Perhaps MySQL borks its databases much more frequently, requiring >> said tools. I have much more experience with Postgres than MySQL and >> have never needed any tools other than those provided with the >> install and never have had Postgres corrupt a database. > > Well.. Since corruptions comes mostly from failing hardware, you > better have > more tools to make backups, than just one or even none. > If you don't have tools to make backups correctly, you better don't > use this > particular DBMS at all. :) > > If using MySQL with Django, or any tool, some quick check list for > backups: > - binary log on (point in time recovery) > - replication going > - regular backups using mysqldump or LVM snapshotting > - backup the my.cnf and mysql database > - and make sure the backups are actually usable!!! > > If you are hosting your project, make sure the hosting company has > at least > some replication going and daily backups in place. Never trust your or > others hardware.. > > Cheers, > > Geert > > -- > Geert Vanderkelen > http://some-abstract-type.com > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
