Re: 回复:Re: [BUGS] BUG #5853: when the walsender cannot exit when reboot slave computer - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: 回复:Re: [BUGS] BUG #5853: when the walsender cannot exit when reboot slave computer
Date
Msg-id 4D419C5F.8050603@enterprisedb.com
Whole thread Raw
In response to BUG #5853: when the walsender cannot exit when reboot slave computer  ("lxzou" <zoulx1982@163.com>)
List pgsql-bugs
(Please keep the mailing list cc'd so that others can help)

On 27.01.2011 16:38, zoulx1982 wrote:
> There is no error or log, but when  i use  "ps -ef | grep postgres" to watch the process, i find walsender process
alreadyexists. 
> In my view, whether this process should exit, because the walreceiver have exit  (caused by computer restart).

If the client just goes away, like if the computer is reset, it can take
up to a few minutes for the operating system to declare the TCP
connection as dead. And you'll need to generate a little bit of WAL so
that the walsender has something it tries to send to the receiver,
otherwise it might take even longer. You can also look at "netstat"
output, to see if the OS thinks the connection is still established.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5852: Function date_trunc is not IMMUTABLE
Next
From: Peter Eisentraut
Date:
Subject: Re: Bug in italian help of "pg_dumpall"