| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zhan Li <zhanli89(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Ideas of "printing out" the alternative paths |
| Date: | 2013-11-14 19:27:15 |
| Message-ID: | 19982.1384457235@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zhan Li <zhanli89(at)gmail(dot)com> writes:
> Thank you for your reply Tom. Then a) what are exactly stored in the
> pathlist of top level rel? Paths worth considering? b) I have been
> struggling to come up with a way to print the Path struct. If I can print a
> path the way like "A hash join (B nested loop join C)", that would be
> great. You mentioned people have printed "something" about each path, can
> you please give me a hint of what's that and how to achieve that?
I don't think anyone's tried anything much smarter than
src/backend/nodes/outfuncs.c, or there's some more limited stuff at the
bottom of src/backend/optimizer/path/allpaths.c. Reassembling into
something more human-readable than that would probably take some work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2013-11-14 19:54:04 | Re: additional json functionality |
| Previous Message | Merlin Moncure | 2013-11-14 19:17:22 | Re: additional json functionality |