Re: Capturing EXPLAIN ANALYZE for a query without discarding the normal result set - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Capturing EXPLAIN ANALYZE for a query without discarding the normal result set
Date
Msg-id 27998.1389669260@sss.pgh.pa.us
Whole thread Raw
In response to Capturing EXPLAIN ANALYZE for a query without discarding the normal result set  (Dave Cole <davejohncole@gmail.com>)
Responses Re: Capturing EXPLAIN ANALYZE for a query without discarding the normal result set  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
Dave Cole <davejohncole@gmail.com> writes:
> It would be really cool if you could direct the EXPLAIN ANALYZE output to a
> temporary table so that the query being analyzed could execute normally.

What happens if the current transaction rolls back?

If you want noninvasive explain data, contrib/auto_explain offers
a solution right now.  The info goes to the postmaster log, which is
perhaps less convenient than a temp table for interactive use, but
it doesn't have the rollback problem --- and you can capture data
about queries issued by a live application, without hacking the app.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: Capturing EXPLAIN ANALYZE for a query without discarding the normal result set
Next
From: Florian Pflug
Date:
Subject: Re: Disallow arrays with non-standard lower bounds