Fwd: replication_timeout not effective

From: Dang Minh Huong <kakalot49(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Fwd: replication_timeout not effective
Date: 2013-04-10 08:22:08
Message-ID: 9ACA1D14-16B1-496B-9F51-45A0D4B4E67D@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Hi,
>
> Thank you for your soon reply.
>
> I'm trying to set the network timeout related parameters to terminate it.
>
> # i've tried to set postgresql.conf's tcp_keepalives_* but not success.
>
> Regards,
>
> 2013/04/10 14:05、Amit Kapila <amit(dot)kapila(at)huawei(dot)com> のメッセージ:
>
>> On Wednesday, April 10, 2013 9:35 AM Dang Minh Huong wrote:
>>> Hi,
>>
>>> I'm wondering if this is a bug of PostgreSQL.
>>
>>> PostgreSQL's show that replication_timeout parameter can "Terminate replication connections that are inactive longer than the specified number of milliseconds". But in my environment the sender process > is hang up (in several tens of minunites) if i turn off (by power off) Standby PC while pg_basebackup is excuting.
>>
>>> Is this correct?
>>
>>> As my debug, sender process is terminated when recieve SIGPIPE process but it come too slow (about 30minutes after standby PC was down).
>>
>> For such scenario's, new parameter wal_sender_timeout has been introduced in 9.3. Refer below:
>> http://www.postgresql.org/docs/devel/static/runtime-config-replication.html#RUNTIME-CONFIG-REPLICATION-SENDER
>>
>> I am not sure how to get rid of this problem in 9.1.9
>>
>> With Regards,
>> Amit Kapila.
>>

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2013-04-10 09:33:59 Re: replication_timeout not effective
Previous Message Amit Kapila 2013-04-10 05:05:14 Re: replication_timeout not effective