Re: Easily reading debug_print_plan
От | Craig Ringer |
---|---|
Тема | Re: Easily reading debug_print_plan |
Дата | |
Msg-id | 528C72E5.5040804@2ndquadrant.com обсуждение исходный текст |
Ответ на | Easily reading debug_print_plan (Craig Ringer <craig@2ndquadrant.com>) |
Список | 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
В списке pgsql-hackers по дате отправления: