| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Query Plan Columns |
| Date: | 2010-11-09 08:19:23 |
| Message-ID: | 1DBCA69A-5440-4232-B8FF-D5D457D4495A@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 9, 2010, at 12:12 AM, Dimitri Fontaine wrote:
> WITH plan AS (
> EXPLAIN (format table) SELECT * FROM bar
> )
> INSERT INTO plan_audit
> SELECT * FROM plan
> WHERE actual_total_time > 12 * interval '100 ms';
Yeah, that would be nice, but my current implementation has a row for each node, and a single explain can have many nodes. With this, you'd only get the top-level node (and not even that, as you didn't do EXPLAIN ANALYZE, so actual_total_time would be blank!).
But I do like the idea…
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2010-11-09 09:11:59 | Re: CLUSTER can change t_len |
| Previous Message | Dimitri Fontaine | 2010-11-09 08:12:06 | Re: Query Plan Columns |