Re: [GENERAL] wal_retrieve_retry_interval

On Sat, May 27, 2017 at 2:40 PM, Ludovic Vaugeois-Pepin
<ludovicvp@gmail.com> wrote:
> Say, with 9.6.2,  a hot_standby fails to connect to a replication slot:
>     FATAL:  could not start WAL streaming: ERROR:  replication slot "test3"
> does not exist
> or
>     FATAL:  could not connect to the primary server: FATAL:  the database
> system is starting up
>
> Is there a way to reduce the time it takes until the next attempt? I
> assumed, wrongly I think, that this would be wal_retrieve_retry_interval,
> but it seems that it won't make a difference. I tried setting it to 3s, but
> it seems to take 15s still. Here are two log samples:

Could you double-check your configuration? If I set
wal_retrieve_retry_interval to 1s on a standby, I am able to see a
connection attempt from a WAL receiver happening with this interval of
time in the case of repetitive failures.
--
Michael