PostgreSQL 12 High Availability Cookbook - Third Edition

How it works...

For the first time in this chapter, we are not configuring a primitive, but a group. Unlike primitives, which describe each resource we want to manage, a group tells Pacemaker how. In this case, any resource listed in the group must share a few new attributes:

• Resources must reside on the same node.
• Resources must be started in the specified order.
• Resources must be stopped by reversing the specified order.

We named the group PGServer, and now we can address every member as a cohesive unit using that name. The resource order mirrors the order in which we defined the primitives, which is the logical order necessary to start (and stop) a PostgreSQL server.

When PGServer is started, Pacemaker will activate LVM, followed by ...