Easily reading debug_print_plan

Hi all

I'm spending a lot of time staring at parse and plan trees at the
moment, and I'm finding reading them rather cumbersome.

For those of you who do this a lot, do you use any sort of tooling to
help you out? Just being able to collapse and expand subtrees would be a
lifesaver.

If it's a hassle for others too, how would you feel about using json as
an output format in future releases? It'd be pretty simple to retrofit
by the looks, though updating the regression tests would be a PITA. My
main concern would be effects on back-patching.

If the conensus opinion on that is "hell no" or if it's a much bigger
job than I thought I'll just write a converter that ingests node trees
and spits out json I can view using existing tools.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services