From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Yeb Havinga <yebhavinga(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: explain.c: why trace PlanState and Plan trees separately? |
Date: | 2010-07-13 18:14:25 |
Message-ID: | 3875.1279044865@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yeb Havinga <yebhavinga(at)gmail(dot)com> writes:
> Will the new referenced expression printing also be used when printing
> subplans?
> If yes, I do not have to submit the latest version of a patch I made for
> subplan argument printing (discussed earlier in this thread
> http://archives.postgresql.org/pgsql-hackers/2010-02/msg01602.php)
Oh, I had forgotten that patch was still in progress. I think it's
unnecessary given what I'm fooling with. The attached patch needs
some more testing, but what I get with it is for example
regression=# explain (verbose) select (select oid from pg_class a where
regression(# a.oid = b.relfilenode) from pg_class b;
QUERY PLAN
--------------------------------------------------------------------------------------------------------
Seq Scan on pg_catalog.pg_class b (cost=0.00..5556.81 rows=669 width=4)
Output: (SubPlan 1)
SubPlan 1
-> Index Scan using pg_class_oid_index on pg_catalog.pg_class a (cost=0.00..8.27 rows=1 width=4)
Output: a.oid
Index Cond: (a.oid = b.relfilenode)
(6 rows)
(this is the first example in the above-referenced thread).
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
explain-params-1.patch | text/x-patch | 57.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-07-13 18:25:31 | Per-column collation, proof of concept |
Previous Message | Thom Brown | 2010-07-13 16:25:53 | Re: ERROR: argument to pg_get_expr() must come from system catalogs |