On Tue, Jan 14, 2014 at 5:13 AM, Marti Raudsepp ma...@juffo.org wrote:
You can use the auto_explain contrib module
I just remembered that there's also the pg_stat_plans extension, which
is closer to what you asked:
https://github.com/2ndQuadrant/pg_stat_plans . This one you'll have to
build
On 1/13/14, 9:14 PM, Tom Lane wrote:
Dave Cole davejohnc...@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
I apologise for dropping this out of nowhere. I had an idea about EXPLAIN
ANALYZE that would be very useful for the system we are developing and
supporting.
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
On Tue, Jan 14, 2014 at 5:06 AM, Dave Cole davejohnc...@gmail.com wrote:
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.
You can use the auto_explain contrib module to log the query plans of
Dave Cole davejohnc...@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,
