Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • PostgreSQL Replication, Second Edition
  • Toc
  • feedback
PostgreSQL Replication, Second Edition

PostgreSQL Replication, Second Edition

By : Hans-Jürgen Schönig
4.5 (4)
close
PostgreSQL Replication, Second Edition

PostgreSQL Replication, Second Edition

4.5 (4)
By: Hans-Jürgen Schönig

Overview of this book

This book is ideal for PostgreSQL administrators who want to set up and understand replication. By the end of the book, you will be able to make your databases more robust and secure by getting to grips with PostgreSQL replication.
Table of Contents (17 chapters)
close
16
Index

Common maintenance tasks


Let's now take a look at some common maintenance tasks.

Performing maintenance on a single node

Pacemaker has a built-in notion of bringing a node down for maintenance. This is called standby mode. This mode is also used for enforced failover.

You can activate it like this:

pcs cluster standby db1

If this command is issued on the master, it causes Pacemaker to try to gracefully shut down PostgreSQL. If the shutdown takes more than 110 seconds, a forced kill of PostgreSQL is tried. If this fails, the node is rebooted. Then Pacemaker moves the master IP over to the other node and promotes the chosen PostgreSQL slave to the master role. It is recommended that you issue a CHECKPOINT command on the master prior to doing this step in order to minimize downtime.

For slave nodes, this directive only stops PostgreSQL.

Then wait for the failover to complete:

crm_mon

At this point, your maintenance tasks can be performed.

Tip

Important! Remember to remove /pgsql/run/PGSQL.lock after...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete