Restriction for the PostgreSQL WAL File Shipping Without Shared Storage

The pg_standby utility must be configured with a trigger file after a failover from the primary to the standby triggering a role conversion. An automatic failback cannot occur because the old primary is now out of synchronization. To invoke an actual copy, the PostgreSQL user needs to copy, customize, and execute the two example scripts :resilver-step1 and resilver-step2.

To minimize the data loss on a planned failover, you should switch the PostgreSQL transaction logs before you perform the failover. For information about switching transaction logs, see http://www.postgresql.org.

The PostgreSQL WAL file Shipping without shared storage configuration cannot be deployed with HA containers managed by the HA container agent.