Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

PostgreSQL Repmgr Upgradation And information about repmgr tools

What is repmgr?

repmgr is an open source package which greatly simplifies the process of setting up and managing replication using streaming replication within a cluster of PostgreSQL servers. Taking advantage of features introduced since PostgreSQL 9.3, repmgr builds on PostgreSQL's core functionality to provide a smooth, user-friendly way of working with the complexities of replication and failover management in high-availability environments.
repmgr consists of two core tools:
  1. repmgr command line interface, which provides functionality for adminstering replication such as cloning standby servers.
  2. repmgrd, a background daemon which monitors nodes in a replication cluster and provides automatic failover support.
The latest repmgr major version, 3.1, leverages improvements included with PostgreSQL 9.5 to provide support for switchover, a common administrative task where the roles of primary and standby server are swapped in a controlled manner to facilitate software and hardware maintenance.


Upgrading from repmgr 3.1.1 or 3.1

repmgr 3.1.2 can simply be installed in placed of the existing repmgr 3.1.1 or repmgr 3.1 version. It should be installed first, either from your operating system's packaging system or from source, then perform following tasks:
  • Run the provided repmgr database upgrade script, repmgr3.1.1_repmgr3.1.2.sql. This makes a small modification to the repl_nodes table's foreign key definition.
  • If repmgrd is running, stop and restart the service to ensure it is running with the current repmgr version.


Upgrading from repmgr 3.0

repmgr 3.1.2 is a drop-in replacement for an existing repmgr 3.0 installation. It should be installed first, either from your operating system's packaging system or from source, then following tasks performed:
  • Run the provided repmgr database upgrade script, sql/repmgr3.0_repmgr3.1.sql. This introduces one new convenience view, repl_show_nodes, but otherwise no changes have been made to repmgr's metadata schema.
  • Run the provided repmgr database upgrade script, repmgr3.1.1_repmgr3.1.2.sql. This makes a small modification to the repl_nodes table's foreign key definition.
  • If repmgrd is running, stop and restart the service to ensure it is running with the current repmgr version.


Upgrading from repmgr 2.0

repmgr 3.1.2 can replace an existing repmgr 2.0 installation. It should be installed first, either from your operating system's packaging system or from source, then following tasks performed:
  • If repmgrd is running, stop the service.
  • Run the provided repmgr database upgrade script, sql/repmgr2_repmgr3.sql, which is required to expand the repl_nodes table.
  • Run the provided repmgr database upgrade script, sql/repmgr3.0_repmgr3.1.sql. This introduces one new convenience view, repl_show_nodes.
  • Run the provided repmgr database upgrade script, repmgr3.1.1_repmgr3.1.2.sql. This makes a small modification to the repl_nodes table's foreign key definition.
  • Restart repmgrd if required.


Changes in release 3.1.2

When running on a witness server, repmgrd will now continuously update the witness server's copy of the master's repl_nodes table. This ensures any changes to the repmgr replication cluster configuration are available to the witness server as soon as possible.
Minor corrections and improvements have been made to documentation and log messages. Additionally this version of repmgr can be compiled against the current PostgreSQL 9.6 development source tree.

Comments

Popular posts from this blog

PostgreSQL pgBadger

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated ORA-01262: Stat failed on a file destination directory Linux-x86_64 Error: 2: No such file or directory

PostgreSQL Pgbadger Installation On Linux

PostgreSQL Database startup / shutdown /restart