Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Tom Lane
Peter Eisentraut writes: > What I liked about it is that it makes it a bit easier to compare the > estimate and actual for each node. Hmm, you'd have to make some effort to line up those fields, if you wanted that to be a thing. regards, tom lane -- Sent via pgsql-hack

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Peter Eisentraut
On 1/28/17 3:24 PM, Gavin Flower wrote: > How about have a GUC to control the formatting of how it is displayed? > > Could also include maximum line width (default 'infinite'), and word > wrapping rules, ... You can already configure that in psql. You can also use the yaml format if you want to

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Gavin Flower
On 29/01/17 05:31, Pavel Stehule wrote: 2017-01-28 17:09 GMT+01:00 Tom Lane >: Pavel Stehule mailto:pavel.steh...@gmail.com>> writes: > Now EXPLAIN ANALYZE produce too wide rows for usage in presentations > What do you think about possibility to impleme

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Pavel Stehule
2017-01-28 17:58 GMT+01:00 Tom Lane : > Pavel Stehule writes: > > 2017-01-28 17:09 GMT+01:00 Tom Lane : > >> 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 na

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Tom Lane
Pavel Stehule writes: > 2017-01-28 17:09 GMT+01:00 Tom Lane : >> 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 i

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Pavel Stehule
2017-01-28 17:09 GMT+01:00 Tom Lane : > Pavel Stehule 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: >

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Tom Lane
Pavel Stehule 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)

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Pavel Stehule
2017-01-28 16:22 GMT+01:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 1/28/17 2:36 AM, Pavel Stehule wrote: > > Now EXPLAIN ANALYZE produce too wide rows for usage in presentations > > > > What do you think about possibility to implement >>optional<< > > alternative formatting. > >

Re: [HACKERS] proposal: EXPLAIN ANALYZE formatting

2017-01-28 Thread Peter Eisentraut
On 1/28/17 2:36 AM, Pavel Stehule wrote: > 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 (estimatio