Re: BUG #7534: walreceiver takes long time to detect n/w breakdown - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Date
Msg-id 007601cda563$21bde1d0$6539a570$@kapila@huawei.com
Whole thread Raw
In response to Re: BUG #7534: walreceiver takes long time to detect n/w breakdown  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
> On Monday, October 08, 2012 7:38 PM Robert Haas wrote:
> On Thu, Oct 4, 2012 at 6:12 AM, Amit kapila <amit.kapila@huawei.com>
> wrote:
> > 1. One new configuration parameter wal_receiver_timeout is added to
> detect timeout at receiver task.
> > 2. Existing parameter replication_timeout is renamed to
> wal_sender_timeout.
> 
> -1 from me on a backward compatibility break here.  I don't know what
> else to call the new GUC (replication_server_timeout?) but I'm not
> excited about breaking existing conf files, nor do I particularly like
> the proposed new names.

How about following:
1. replication_client_timeout -- shouldn't it be client as new configuration
is for wal receiver
2. replication_standby_timeout

If we introduce a new parameter for wal receiver, wouldn't
replication_timeout be confusing for user?

With Regards,
Amit Kapila.




pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Next
From: Nikolay
Date:
Subject: Re: BUG #7578: Not able to drop user if S/he has permission on tablespace