Hi Amit, Thank you for your consideration.
My project not allows to use 9.2 or 9.3. In 9.3, it sounds replication_timeout is replaced by wal_sender_timeout. So if it is solved in 9.3 i think there is a way to terminate it. I hope it is fixed in 9.1 soon Regards, 2013/04/10 18:33、Amit Kapila <amit.kap...@huawei.com> のメッセージ: >> Sent: Wednesday, April 10, 2013 1:49 PM Dang Minh Huong wrote: >> To: Amit Kapila >> Subject: Re: [BUGS] replication_timeout not effective > On Wednesday, April 10, 2013 1:49 PM >> 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. > > I have also tried those, but they didn't work that's why I have proposed > this feature in 9.3 > > Please send mail on community list, others can also help you if they have > any idea for avoiding such problems. > >> 2013/04/10 14:05、Amit Kapila <amit.kap...@huawei.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. > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
