Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Alvaro Herrera
Craig Ringer escribió: > On 11/20/2013 04:22 PM, Antonin Houska wrote: > > vim editor. The '%' shortcut can be used to jump between opening and > > closing brackets and thus skip smaller or bigger parts of the output. > > IMO, this output is primarily for hackers (as opposed to application > > deve

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Craig Ringer
On 11/20/2013 10:36 PM, Tom Lane wrote: > Craig Ringer writes: >> I'm spending a lot of time staring at parse and plan trees at the >> moment, and I'm finding reading them rather cumbersome. > > Is there a particular reason you're doing that rather than looking at > EXPLAIN output? Only the latt

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Robert Haas
On Wed, Nov 20, 2013 at 9:36 AM, Tom Lane wrote: > We could in principle change to a different text representation for > stored rules. Compactness would be an issue if it were materially > bigger than the existing formatting, but offhand it seems like JSON > is morally equivalent to what we do no

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Tom Lane
Craig Ringer writes: > I'm spending a lot of time staring at parse and plan trees at the > moment, and I'm finding reading them rather cumbersome. Is there a particular reason you're doing that rather than looking at EXPLAIN output? Only the latter is meant to be at all user-friendly. > For tho

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Dimitri Fontaine
Craig Ringer writes: > That's what I'm currently doing, I just wanted something that makes it > quicker and easier. Jumping around the tree is good, but easy > collapse/expand would be much better. As I'm using psql under an Emacs M-x shell buffer, I wanted to experiment with your problem here, s

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Craig Ringer
On 11/20/2013 04:22 PM, Antonin Houska wrote: > vim editor. The '%' shortcut can be used to jump between opening and > closing brackets and thus skip smaller or bigger parts of the output. > IMO, this output is primarily for hackers (as opposed to application > developers or users) and hacker shoul

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Craig Ringer
On 11/20/2013 04:12 PM, Craig Ringer wrote: > 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 collaps

Re: [HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Antonin Houska
On 11/20/2013 09:12 AM, Craig Ringer wrote: > 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? vim editor. The '%' short

[HACKERS] Easily reading debug_print_plan

2013-11-20 Thread Craig Ringer
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 has