Hacker News Reader

Nice, definitely something that is a pain for mirroring in SQL Server, though if you have a good runbook its just time consuming and boring.

View on HN

? MSSQL mirroring failover is very easy and painless( arguably one of best compared to other rdbms), just make sure not to do automatic failover as that can cause false failover with spotty network between nodes and witness.

Sorry about that, I was referencing failing back over to the primary after failing over to the secondary. Specifically from the post:

- Cool. And how do I fail back to the old master?

- Umm, well, you have to take a new base backup from the new master, and re-build the node from scratch..

The post is about Postgres, you were referring to MSSQL mirroring, which can fail back from primary to secondary and back to primary almost seamlessly, depending on type of failure and log catchup.

Postgres has been a pain as described in the article.......

Reply on news.ycombinator.com