From: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | explain inside begin; commit; |
Date: | 2008-08-18 20:01:19 |
Message-ID: | 20080818220119.54fd8e07@dawn.webthatworks.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
this:
begin;
explain select * from catalog_items limit 5;
commit;
return this:
-- Executing query:
begin;
explain select * from catalog_items limit 5;
commit;
Query result with 2 rows discarded.
Query returned successfully with no result in 58 ms.
I'm interested in explain inside a transaction because:
1) the query I'd like to explain depends on previous statements
2) it modify the DB and I'd like to keep a consistent state. If the
following queries fail I'd like to roll it back.
explain analyze doesn't make any difference in the output.
I didn't find anything in the log.
Any alternative approach?
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2008-08-18 20:08:49 | Re: explain inside begin; commit; |
Previous Message | Ivan Sergio Borgonovo | 2008-08-18 19:51:39 | Re: on cascade delete performances, transaction and set constraints deferred |