From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Ludovic Vaugeois-Pepin <ludovicvp(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: wal_retrieve_retry_interval |
Date: | 2017-05-28 04:54:10 |
Message-ID: | CAB7nPqSYL=w8Lmtntdj5uxgUFW_Y10KduHrrHS+bERS-YvyYmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, May 27, 2017 at 2:40 PM, Ludovic Vaugeois-Pepin
<ludovicvp(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ludovic Vaugeois-Pepin | 2017-05-28 08:07:05 | Fwd: wal_retrieve_retry_interval |
Previous Message | doganmeh | 2017-05-27 22:29:41 | Re: COPY: row is too big |