From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: EXPLAIN ANALYZE formatting |
Date: | 2017-01-28 16:58:04 |
Message-ID: | 7935.1485622684@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2017-01-28 17:09 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Seems like that would make a difference in only a tiny minority of
>> situations. In a deeply nested plan you'll have trouble no matter
>> what, and it's not uncommon that the node name line isn't the widest
>> thing anyway.
> It is related to presentation where you have to use large type - and where
> usually don't present complex nested plans, or you present only fragments.
Sure, but then you're whacking around the text anyway while you put it
into your slides. I doubt anyone would have trouble understanding your
slides if you break up the lines like that, whether or not it's exactly
what you'd get out of EXPLAIN itself.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-01-28 17:14:26 | Re: proposal: EXPLAIN ANALYZE formatting |
Previous Message | Ashutosh Sharma | 2017-01-28 16:55:58 | Re: pageinspect: Hash index support |