![]() You will need three nodes to have a quorum to prevent a split brain scenario. Allocate at least 3 nodes (master/slave/slave or master/slave/witness).Make sure your PostgreSQL streaming replication is running.Think of re-configuring your load-balancing tools, like Pgpool-II to make sure read and write queries get assigned to the correct cluster nodes. It gives you a wealth of ‘hooks’, where you can call scripts to help you reconfigure you surrounding landscape to a switch of masters. The tool ensures access to the cluster of database clusters using a Virtual IP Address. It is based on PostgreSQL streaming replication, which allows you to create multiple slave clusters to your master cluster. Failover from a master node to a slave node (which will be promoted to new master).This way you have the chance to do maintenance on the (previously master) node. A graceful switch-over from a master database to a slave database (and back) with just one single command.Introducing EDB Failover Manager (or short: EFM). Making sure your database systems stay up during planned maintenance? Absolutely yes, no discussion about that!Įnsuring your systems stay up during a catastrophic failure of your master? Yes! We need to ensure 99.99999 availability. ![]() And why not? This extremely stable and performant database can compete with ease with almost all enterprise database installations out there today.Ĭompeting from a business perspective? Absolutely!! Using PostgreSQL in enterprise environments gets more and more popular.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |