We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently PG replicas are potentially a bit behind the master, so there could be data loss in the event of a failover
The text was updated successfully, but these errors were encountered:
As part of the simple version of you might want to include application_name in primary_conninfo in recovery.conf:
application_name
primary_conninfo
recovery.conf
primary_conninfo = 'application_name= '{{cfg.replication.application_name}} user={{cfg.replication.name}} password={{cfg.replication.password}} host={{svc.leader.sys.ip}} port={{cfg.port}} sslmode=prefer sslcompression=1'
Even if you don't use it to start with, it allows grouping of standbys if you would like (sync group, async group etc....)
Sorry, something went wrong.
Added application_name 1d2d8a1
No branches or pull requests
Currently PG replicas are potentially a bit behind the master, so there could be data loss in the event of a failover
The text was updated successfully, but these errors were encountered: