4 ms·
Just standard replication on 2 other nodes. We don’t have huge constant loads. Over-provisioned on massive bare metal so we can take a lot. Also daily pg_base
by eric4smith 4y ago
Just standard replication on 2 other nodes.
We don’t have huge constant loads. Over-provisioned on massive bare metal so we can take a lot.
Also daily pg_basebackup which does not eat too many resources. Standard pg_dump is impossible.
About to also add log shipping when I upgrade. We don’t do super critical things like banking or anything like that. But I do want to move to the point where at worse we only lose a few minutes of data.
Now we can lose up to 24 hours if all the replicas die at once.
- MuffinFlavored 4y agoSo that's 3 nodes total, one permanently master and the other two permanently read-only slaves? Is there any kind of "automatic rollover" if the master goes down where one of the slaves automatically promotes itself?
- eric4smith 4y agoNot necessary. As I said, we are not at all a critical service. If we are down an hour, it's not a big deal (like 95% of the rest of the inter-webs). We are not banksters. If it goes down, we get a page, and we can have it switched by hand in a few minutes. I guess if our service was super-critical, I would do that, but since it's not, the three of us that work as developers and sys-admins can deal with it very quickly.