Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PostgreSQL Replication, Second Edition

You're reading from   PostgreSQL Replication, Second Edition Leverage the power of PostgreSQL replication to make your databases more robust, secure, scalable, and fast

Arrow left icon
Product type Paperback
Published in Jul 2015
Publisher
ISBN-13 9781783550609
Length 322 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (17) Chapters Close

Preface 1. Understanding the Concepts of Replication FREE CHAPTER 2. Understanding the PostgreSQL Transaction Log 3. Understanding Point-in-time Recovery 4. Setting Up Asynchronous Replication 5. Setting Up Synchronous Replication 6. Monitoring Your Setup 7. Understanding Linux High Availability 8. Working with PgBouncer 9. Working with pgpool 10. Configuring Slony 11. Using SkyTools 12. Working with Postgres-XC 13. Scaling with PL/Proxy 14. Scaling with BDR 15. Working with Walbouncer Index

Performing failovers

Once you have learned how to replicate tables and add them to sets, it is time to learn about failover. Basically, we can distinguish between two types of failovers:

  • Planned failovers
  • Unplanned failovers and crashes

In this section, you will learn about both scenarios.

Planned failovers

Having planned failovers might be more of a luxury scenario. In some cases, you will not be so lucky and you will have to rely on automatic failovers or face unplanned outages.

Basically, a planned failover can be seen as moving a set of tables to some other node. Once that node is in charge of those tables, you can handle things accordingly.

In our example, we want to move all tables from node 1 to node 2. In addition to this, we want to drop the first node. Here is the code required:

#!/bin/sh

MASTERDB=db1
SLAVEDB=db2
HOST1=localhost
HOST2=localhost
DBUSER=hs

slonik<<_EOF_
cluster name = first_cluster;

node 1 admin conninfo = 'dbname=$MASTERDB host=$HOST1 user=$DBUSER';...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime