| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: EXPLAIN ANALYZE formatting |
| Date: | 2017-01-28 21:31:10 |
| Message-ID: | 6c9753fb-f57b-5bac-e921-97943834f4a7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 use less horizontal
space. (I have used that in presentations.)
What I liked about it is that it makes it a bit easier to compare the
estimate and actual for each node.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-28 21:40:15 | Re: proposal: EXPLAIN ANALYZE formatting |
| Previous Message | Gavin Flower | 2017-01-28 20:24:05 | Re: proposal: EXPLAIN ANALYZE formatting |