Does Monitor can handle formations of different PG versions #1071
-
|
Hello, I plan to use pg_auto_failover in my company to manage a postgresql infrastructure of a set of 2 node master/slave "clusters" (i.e Formations). Each Formation may be of a different PG version We have 4 large servers which will carry all the instances in order to distribute the load. pg_auto_failover seems to meet our needs well. It is specified in the documentation that the Monitor can manage several Formations, but is it capable of managing Formation of different versions ? (e.g. Formations pg16-name1, pg16-name2, pg17-name1, etc.) Does the monitor installed on a PG.Vxx know how to manage PG training of a higher (or lower) version? Thank you in advance for your feedback |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @PatrickBzh ; thanks for opening that discussion. There is no hard dependency between the Postgres version where the monitor is deployed and the Postgres version of the nodes being monitored. This means you can deploy a mixed system like you envision without restriction in terms of Postgres versions in different formations and at the monitor level. Usual pg_auto_failover version matching applies, of course. If you have some time to consider it, I would happily review a PR that improves the documentation on that point. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dimitri, Many thanks for your reply. |
Beta Was this translation helpful? Give feedback.
Hi @PatrickBzh ; thanks for opening that discussion. There is no hard dependency between the Postgres version where the monitor is deployed and the Postgres version of the nodes being monitored. This means you can deploy a mixed system like you envision without restriction in terms of Postgres versions in different formations and at the monitor level. Usual pg_auto_failover version matching applies, of course.
If you have some time to consider it, I would happily review a PR that improves the documentation on that point.