On Wed, Jan 26, 2011 at 8:24 PM, Mark <dvlhntr(at)gmail(dot)com> wrote:
> getting a break down in streaming rep. my current work around is to restart
> the PG instance on the ROHS. doesn't seem to affect the master any. doesn't
> require a re-rsync of the base to get replication going again. has happened
> with 9.0.2 twice now in a month.
> 2011-01-26 08:35:42 MST :: (postgres(at)10(dot)80(dot)2(dot)89) LOG: could not receive
> from client: Connection reset by peer
> 2011-01-26 08:35:42 MST :: (postgres(at)10(dot)80(dot)2(dot)89) LOG: unexpected EOF on
> standby connection
> this was all I have in the master's log with the level set to debug 1, I
> have reset it to debug 5 and will just wait till it dies again and hopefully
> get a better idea of what is going on. nothing is being logged to the
Maybe a break in network connectivity is leading the master to think
that the slave is dead, while the slave still thinks it's connected.
You might need to adjust the TCP keepalive parameters the slave uses
to connect to the master.
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Robert Haas||Date: 2011-01-28 13:49:33|
|Subject: Re: A bug to report|
|Previous:||From: Heikki Linnakangas||Date: 2011-01-28 09:15:07|
|Subject: Re: 回复:Re: 回复:Re: [BUGS] BUG #5853: when the walsender cannot exit when reboot slave computer|