How it works...
The next primitive that we add to Pacemaker will need to use systemd to manage PostgreSQL. As we'd mentioned at the beginning of this chapter, this ensures Pacemaker receives expected LSB status codes when performing actions. Hence, when we call crm with the configure primitive parameters, we name the new primitive pg_service to remain consistent. We also use the systemd:postgresql@12-main resource agent, which targets our specific PostgreSQL instance.
One consequence of this is that our resource agent is not fully integrated into Pacemaker and has no configurable parameters. The only things we can change are the generic options (op) such as monitor intervals and start or stop timeouts. For this agent, we've set all of the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access