Re: Streaming replication and unfit messages
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@postgresql.org
Cc: Fujii Masao <masao.fujii@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Date: 2010-02-18T08:23:17Z
Lists: pgsql-hackers
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 connection could be made > > because the target machine actively refused it. > > Also the walsender wrongly tries to send the FATAL message to the standby > even though the connection has already been closed, and then gets the > following LOG message after the FATAL one. This FATAL message is suitable, > but output of the LOG message looks messy, too. We should use COMMERROR > instead of FATAL and then just call proc_exit() in order to prevent a > message from being sent? Or hope for my idle query cancellation prelim. patch to get applied so you can do ereport(FATAL | LOG_NO_CLIENT, ...) ;-) Andres