Re: Active connections are terminated because of small wal_sender_timeout

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: AYahorau(at)ibagroup(dot)eu, pgsql-general(at)postgresql(dot)org
Subject: Re: Active connections are terminated because of small wal_sender_timeout
Date: 2019-07-08 07:45:23
Message-ID: 20190708074523.GE2709@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 05, 2019 at 10:03:16AM -0400, Tom Lane wrote:
> AYahorau(at)ibagroup(dot)eu writes:
>> Do you have any thoughts regarding this issue?
>
> I do not think anybody thinks this is a bug. Setting wal_sender_timeout
> too small is a configuration mistake.

Yeah. I don't see any bug here. Please note that it can be also a
problem to set up a too high value in some configuration setups. The
lack of flexibility in this area is why wal_sender_timeout has been
switch to be user-settable in v12. In short you can configure it in
the connection string to enforce a custom value per standby.
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Morris de Oryx 2019-07-08 07:48:30 Incremental aggregate/rollup strategy advice
Previous Message Tom Lane 2019-07-08 01:26:44 Re: Measuring the Query Optimizer Effect: Turning off the QO?