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 29824.1149793286@sss.pgh.pa.us
Whole thread Raw
In response to Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)  (Gregory Stark <gsstark@mit.edu>)
Responses Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN  ("A.M." <agentm@themactionfaction.com>)
Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Gregory Stark <gsstark@mit.edu> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> Would it be possible to make a whole new protocol message for EXPLAIN results?

I'm really unwilling to get into that.  For one thing, that would
absolutely positively break *all* use of EXPLAIN from un-fixed clients,
whether you were trying to stop early or not.

> The reason I'm suggesting that is because it might make it easier to implement
> the SIGINFO handler that sends incremental EXPLAIN results on demand that I
> was describing earlier.

Doesn't matter, because that's not happening ;-)  SIGINFO isn't
portable, and even if it were, a signal handler couldn't possibly
generate EXPLAIN output (remember those catalog accesses).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: ADD/DROP INHERITS
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] drop if exists remainder