On Mon, May 29, 2017 at 3:58 PM, Ludovic Vaugeois-Pepin
wrote:
> < 2017-05-29 22:42:17.026 CEST > DEBUG: switched WAL source from
> archive to stream after failure
> ... (15 seconds later) ...
> < 2017-05-29 22:42:32.042 CEST > DEBUG: switched WAL source from
> stream to archive after failure
L
On Tue, May 30, 2017 at 12:20 AM, Michael Paquier
wrote:
> On Sun, May 28, 2017 at 9:41 AM, Ludovic Vaugeois-Pepin
> wrote:
>> On Sun, May 28, 2017 at 9:49 AM, Ludovic Vaugeois-Pepin
>> wrote:
>>> It really is set at 3s on all servers (master and standbies) earlier in the
>>> "deployment" proce
On Sun, May 28, 2017 at 9:41 AM, Ludovic Vaugeois-Pepin
wrote:
> On Sun, May 28, 2017 at 9:49 AM, Ludovic Vaugeois-Pepin
> wrote:
>> It really is set at 3s on all servers (master and standbies) earlier in the
>> "deployment" process at the same time "listen_addresses", "hot_standby", and
>> oth
On Sun, May 28, 2017 at 9:49 AM, Ludovic Vaugeois-Pepin
wrote:
>
>
> On Sun, May 28, 2017 at 6:54 AM, Michael Paquier
> wrote:
>>
>> On Sat, May 27, 2017 at 2:40 PM, Ludovic Vaugeois-Pepin
>> wrote:
>> > Say, with 9.6.2, a hot_standby fails to connect to a replication slot:
>> > FATAL: co
On Sun, May 28, 2017 at 6:54 AM, Michael Paquier
wrote:
> On Sat, May 27, 2017 at 2:40 PM, Ludovic Vaugeois-Pepin
> 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 ex
On Sat, May 27, 2017 at 2:40 PM, Ludovic Vaugeois-Pepin
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:
Hi,
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 ti