| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Adding qualification conditions to EXPLAIN output |
| Date: | 2002-03-12 16:23:09 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA488787B@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Index Scan using foo_f1_key on foo (cost=0.00..17.08 rows=1 width=12)
> indxqual: (f1 = 11)
> qual: (f3 = 44)
Wow, that looks really nice.
The field headers could probably be more verbose, like:
Index Scan using foo_f1_key on foo (cost=0.00..17.08 rows=1 width=12)
Index Filter: (f1 = 11)
Filter: (f3 = 44)
and for btree ranges:
Lower Index Filter:
Upper Index Filter:
> Question for the group: does this seem valuable enough to put into the
> standard EXPLAIN output, or should it be a special option? I can
Imho make it standard for EXPLAIN. Simply too useful to not show it :-)
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2002-03-12 16:24:10 | Re: Zlib vulnerability heads-up. |
| Previous Message | Lamar Owen | 2002-03-12 16:05:24 | Zlib vulnerability heads-up. |