hi gabor, On Mon, Aug 06, 2007 at 11:02:08AM +0200, Gábor Farkas wrote: > > hi, > > how do/did you approach/solve the "what happens if the database (server) > dies?" problem? > > what kind of replication/failover solutions do you use? > (i'm primarily interested in postgres..) > > i'm not talking about database-replication solutions for performance > reasons (scaling etc..). > > i already collected some approaches that might be worth investigating > (pgpool,slony,heartbeat,drbd for example), and would like to know if > there are also some other solutions/approaches..
we have fairly good expirience (in terms of reliability) with slony2 for 1->1 replication. it's not for the faint of heart as there's some trigger-magic and rough edges involved but seemed like the most tested solution at the time. > or, if someone has some experience that he's willing to share, i'd be > glad to listen to "what worked" and "what did not work". among the ones you mentioned i would personally prefer pgpool-ii over most anything else, simply because it seems the least complex and the inherent drawbacks (i.e. serial columns and in-db magic [pl/sql] should be avoided) don't bother me. unfortunately it still doesn't seem to be available to the unwashed masses and pgpool-i feels way too hacky for my taste. hth, moe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
