Re: Streaming replication and unfit messages - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Streaming replication and unfit messages
Date
Msg-id 201002180923.20434.andres@anarazel.de
Whole thread Raw
In response to Streaming replication and unfit messages  (Fujii Masao <masao.fujii@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Streaming replication on win32, still broken
Next
From: Richard Huxton
Date:
Subject: Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl