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. :)
For clarification, Don said that he _did_ have tools. He noted that _Postgres_ had never corrupted a database on him (while failing hardware might have). For my own part, I've used Postgres, and I find their backup/restore system to be fully functional. See their documentation for more information: http://www.postgresql.org/docs/8.1/interactive/backup.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
