Re: [BUGS] replication_timeout not effective - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: [BUGS] replication_timeout not effective
Date
Msg-id CAM103DuLWwRPXXfpn-6HzXnGOfOuA04gQoRt8EW28m8bpy8Crg@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] replication_timeout not effective  (Dang Minh Huong <kakalot49@gmail.com>)
Responses Re: [BUGS] replication_timeout not effective  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Hello,

On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong <kakalot49@gmail.com> 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 way to terminate it.
> I hope it is fixed in 9.1 soon

Hmm. He said that,

> But in my environment the sender process is hang up (in several tens of minunites) if i turn off  (by power off)
StandbyPC while *pg_basebackup* is excuting.
 

Does basebackup run only on 'replication connection' ?
As far as I saw base backup uses 'base backup' connection in addition
to 'streaming' connection. The former seems not under the control of
wal_sender_timeout or replication_timeout and easily blocked at
send(2) after sudden cut out of the network connection underneath.
Although the latter indeed is terminated by them.

Blocking in send(2) might could occur for async-rep connection but not
likely for sync-rep since it does not fill the buffers of libpq and
socket easilly.

I suppose he says about this.

This seems to occur as of the latest 9.3dev.

regards,
--
Kyotaro Horiguchi



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Inconsistent DB data in Streaming Replication
Next
From: Andres Freund
Date:
Subject: Re: [BUGS] replication_timeout not effective