On Thursday 18 February 2010 06:17:06 Fujii Masao wrote:
[2460]: LOG: could not receive data from client: No connection could be
made because the target machine actively refused it. [2460]: FATAL:
invalid standby closing message type 4
[2460]: LOG: could not send data to client: No
Fujii Masao wrote:
Hi,
When the replication connection is closed unexpectedly, walsender might emit
the following unfit messages. IOW, the loss of the connection might be wrongly
regarded as an arrival of invalid message by the walsender. This looks messy.
We should get rid of that unfit
2010/2/18 Heikki Linnakangas heikki.linnakan...@enterprisedb.com:
Fujii Masao wrote:
Hi,
When the replication connection is closed unexpectedly, walsender might emit
the following unfit messages. IOW, the loss of the connection might be
wrongly
regarded as an arrival of invalid message by
Magnus Hagander wrote:
This cannot possibly be correct:
+ if (errno == EAGAIN || EWOULDBLOCK || errno == EINTR)
The middle argument is missing the errno== part.
Ahh, rats. Yeah it clearly is. Thanks.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
On Thu, Feb 18, 2010 at 7:05 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Magnus Hagander wrote:
This cannot possibly be correct:
+ if (errno == EAGAIN || EWOULDBLOCK || errno == EINTR)
The middle argument is missing the errno== part.
Ahh, rats.
Fujii Masao wrote:
* The received byte is stored in *c. Returns 1 if a byte was read, 0 if
! * if no data was available, or EOF if trouble.
Typo. 'if' is repeated.
+ ereport(COMMERROR,
+
Hi,
When the replication connection is closed unexpectedly, walsender might emit
the following unfit messages. IOW, the loss of the connection might be wrongly
regarded as an arrival of invalid message by the walsender. This looks messy.
We should get rid of that unfit FATAL message, emit a
