Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting
Date
Msg-id 6096.1485619776@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] proposal: EXPLAIN ANALYZE formatting  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> Now EXPLAIN ANALYZE produce too wide rows for usage in presentations

> What do you think about possibility to implement >>optional<< alternative
> formatting.
> Now:
>   node name (estimation) (actual)
> Alternative:
>   node name (estimation)
>                    (actual)

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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Removing link-time cross-module refs in contrib