FAQ

FAQ

How do I recover from timeline X of the primary does not match recovery target timeline Y on the slave?

There are plenty of posts about this on the PostgreSQL mailing list, and the only way to recover from this is to resync the slave with the master. Luckily that's pretty easy now with our system up and running. All you need to do on the slave is to run: pg_ha.sh init-slave

Will this work with Django?

Unfortunately we had to disable the load-balancing (set 'load_balance_mode = false') on our production deployment of Django. Turns out the delay between the master and slave was significante enough to cause havoc with session keys. Maybe there's a workaround for this, but I'm yet to find it. In theory the solution would be to force time-sensitive queries, like the session table, to be read from the master.