From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
---|---|
To: | "'Dang Minh Huong'" <kakalot49(at)gmail(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: replication_timeout not effective |
Date: | 2013-04-10 05:05:14 |
Message-ID: | 003e01ce35a8$fced21a0$f6c764e0$@kapila@huawei.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dang Minh Huong | 2013-04-10 08:22:08 | Fwd: replication_timeout not effective |
Previous Message | Dang Minh Huong | 2013-04-10 04:04:52 | replication_timeout not effective |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-04-10 06:37:06 | Re: bgworker sigusr1 handler |
Previous Message | Rodrigo Barboza | 2013-04-10 04:59:25 | Re: Unrecognized type error (postgres 9.1.4) |