On Mon, Sep 27, 2010 at 7:46 AM, fazool mein <fazoolmein@gmail.com> wrote: > I checked the code for the keepalive feature. It seems that the socket > options are only set on the primary's socket connection. The tcp connection > created on the secondary for walreceiver does not use the keepalive > parameters from the configuration.
You can use libpq keepalive parameters for walreceiver.