Re: Hot Standy introduced problem with query cancel behavior - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Hot Standy introduced problem with query cancel behavior
Date
Msg-id 201001121943.59270.andres@anarazel.de
Whole thread Raw
In response to Re: Hot Standy introduced problem with query cancel behavior  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standy introduced problem with query cancel behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Hot Standy introduced problem with query cancel behavior  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Tuesday 12 January 2010 09:40:03 Simon Riggs wrote:
> On Tue, 2010-01-12 at 06:30 +0100, Andres Freund wrote:
> > Currently the patch does not yet do anything to avoid letting the
> > protocol out of sync. What do you think about adding a flag for error
> > codes not to communicate with the client (Similarly to COMERROR)?
> > 
> > So that one could do an elog(ERROR & ERROR_NO_SEND_CLIENT, .. or such?
> Seems fairly important piece.
Do you aggree on the approach then? Do you want to do it? 

Andres


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Streaming replication and non-blocking I/O
Next
From: Greg Smith
Date:
Subject: Re: Clearing global statistics