On Fri, Nov 4, 2011 at 10:58 PM, Samba wrote:
> although both master(with replication_timeout) and slave (with tcp timeout
> option in primary_conninfo parameter) closes the connection in quick time
> (based on tcp idle connection timeout), as of now they do not log such
> information. It would
Thanks Fuji for that I hint...
I searched around on the internet for that trick and it looks like we can
make the Standby close its connection to the master much earlier than it
otherwise would;it is good for me now.
But still there seems to be two problem areas that can be improved over
time...
On Thu, Nov 3, 2011 at 12:25 AM, Samba wrote:
> The postgres manual explains the "replication_timeout" to be used to
>
> "Terminate replication connections that are inactive longer than the
> specified number of milliseconds. This is useful for the primary server to
> detect a standby crash or net
Hi all,
The postgres manual explains the "replication_timeout" to be used to
"Terminate replication connections that are inactive longer than the
specified number of milliseconds. This is useful for the primary server to
detect a standby crash or network outage"
Is there a similar configuration
