2013/04/10 23:44、Andres Freund のメッセージ:
> On 2013-04-10 23:37:44 +0900, Dang Minh Huong wrote:
>> Thanks all,
>>
>> (2013/04/10 22:55), Andres Freund wrote:
>>> On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
>>>> Hello,
>>>>
Thanks all,
(2013/04/10 22:55), Andres Freund wrote:
On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
Hello,
On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong wrote:
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
のメッセージ:
>> 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
のメッセージ:
>
>> 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
>>> replicatio
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)
