PostgreSQL 12 High Availability Cookbook - Third Edition

How to do it...

We will assume that the 10.0.30.150 IP address exists as a predefined target for our PostgreSQL cluster. Users and applications will connect to it instead of the actual addresses of pg1 or pg2.

Perform these steps on any Pacemaker node as the root user:

1. Add an IP address primitive to Pacemaker with crm:

crm configure primitive pg_vip ocf:heartbeat:IPaddr2 \
    params ip="10.0.30.150" \
           iflabel="pgvip" \
    op monitor interval="5"

2. Try to view the IP allocation on pg1 and pg2:

ip addr | grep -A1 :pgvip

3. Clean up any errors that might have accumulated with crm:

crm resource cleanup pg_vip

4. Display the status of our new IP address with crm:

crm resource status