Force Reconnect of streaming replication

From: Hannes Erven <hannes(at)erven(dot)at>
To: pgsql-general(at)postgresql(dot)org
Subject: Force Reconnect of streaming replication
Date: 2018-11-28 16:21:02
Message-ID: BF64066C-BA98-4526-B3E7-2B1F971FF2C6@erven.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

consider a PG10 master center, streaming via internet to another site. The receiving site has a fast primary uplink and much slower backup link.

When the primary link goes down, all traffic is routed through the backup connection. The streaming replication's connection drops and is automatically re-establish over the backup link.

But when the primary link comes up again, the replication will still use the already established connection via the slow backup link.

If I kill the wal_sender process on the master, the slave will immediately reconnect over the "best" available link.
But is this really the best way to force PG to re-connect the replication?

I guess I could as well kill the wal-receiving process on the slave but still I'm hesitating to put something like "killall pg_walsender" in a cronjob...

Is there a better way?

Thanks for your opinions,
best regards

-hannes

Browse pgsql-general by date

  From Date Subject
Next Message PegoraroF10 2018-11-28 19:55:17 Primary Key index with Include
Previous Message Andreas Kretschmer 2018-11-28 15:35:35 Re: 2018-11-28 10:40:01,906 9672 CRITICAL ? odoo.service.server: Failed to initialize database `abc`