From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Easily reading debug_print_plan |
Date: | 2013-11-20 08:29:25 |
Message-ID: | 528C72E5.5040804@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 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.
Inevitably, as soon as I post I realise why it's "hell no".
The same representation is used for storing rules. So it can't be
changed for BC reasons and compactness/performance.
I'll just post-process.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2013-11-20 08:31:50 | Re: Easily reading debug_print_plan |
Previous Message | Antonin Houska | 2013-11-20 08:22:34 | Re: Easily reading debug_print_plan |