New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Barman mode, fix primary_conninfo creation #232
Comments
gciolli
added a commit
to gcedb/repmgr
that referenced
this issue
Aug 18, 2016
After introducing Barman mode, it is no longer true that STANDBY CLONE can derive primary_conninfo from the connection to the master. Now we ask Barman how to connect to a valid cluster node, and then we fetch the conninfo for the current master from repmgr metadata.
Fixed in 4028594. |
ibarwick
pushed a commit
that referenced
this issue
Sep 5, 2016
After introducing Barman mode, it is no longer true that STANDBY CLONE can derive primary_conninfo from the connection to the master. Now we ask Barman how to connect to a valid cluster node, and then we fetch the conninfo for the current master from repmgr metadata.
Fixes added, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Barman mode, STANDBY CLONE cannot assume the existence of a libpq connection to the current primary node; therefore it must create primary_conninfo by other means.
The text was updated successfully, but these errors were encountered: