Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)
Date
Msg-id 12726.1149869915@sss.pgh.pa.us
Whole thread Raw
In response to Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)  ("Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
"Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at> writes:
>> This bothers me a bit, because in 
>> fact the effects if any of the tested query would have been 
>> rolled back.  Not sure we have any choice though.  If we 
>> expose the error then we'll have problems with clients not 
>> showing the EXPLAIN results.

> I think we should leave it in top level, throw the error and fix the
> clients.
> As I understood, the idea was, that it only does that if you 
> press ^C or query timeout. In this case current clients would also
> not show the plan.

Not if the clients are implemented per protocol spec.  A client cannot
assume that sending QueryCancel will make the current query fail.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: That EXPLAIN ANALYZE patch still needs work
Next
From: Tom Lane
Date:
Subject: Re: patch postgresql for AMD64 (Opteron)