You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a single asynchronous replica set up for my master db. It runs great out of the box with the REPLICATION_XXX env vars!
I'm trying to enable synchronous_standby_names so that we don't get inconsistent reads. Adding EXTRA_CONF="synchronous_standby_names = '*'\n" as an env var (or via the /settings/extra.conf file) causes the master to just hang on the log entry 'Creating superuser xxx' and it never accepts connections.
Has anyone successfully set up synchronous replication and if so, how?
The text was updated successfully, but these errors were encountered:
I tried this one and got a slightly different error. The master takes very long to start and when it eventually does the replicant is not able to ping master. But reading from https://www.crunchydata.com/blog/synchronous-replication-in-postgresql it specifies that you need to reload the configs using pg_ctl or sql. I am not sure what causes this
Version: 12
I have a single asynchronous replica set up for my master db. It runs great out of the box with the REPLICATION_XXX env vars!
I'm trying to enable synchronous_standby_names so that we don't get inconsistent reads. Adding EXTRA_CONF="synchronous_standby_names = '*'\n" as an env var (or via the /settings/extra.conf file) causes the master to just hang on the log entry 'Creating superuser xxx' and it never accepts connections.
Has anyone successfully set up synchronous replication and if so, how?
The text was updated successfully, but these errors were encountered: