| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Gerdan Santos <gerdan(at)gmail(dot)com> |
| Subject: | Re: \timing interval |
| Date: | 2016-09-08 11:42:47 |
| Message-ID: | CAFj8pRChHS0hnCw-Yq1+oL93Eq+JgEn4CLM0SBQ58wruEriOpQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-09-08 13:10 GMT+02:00 Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>:
> On 4 Sep. 2016 3:36 am, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >
>
> > After further thought I concluded that not providing any labeling of
> > days is a bad idea.
>
> Yeah. I think labeling days is definitely good. I'm glad you changed that.
>
> Personally I'd like to trim milliseconds when dealing with minute+ long
> runs and seconds from hour+ runs too, since it's all there in the ms output
> and the units output is for human readability. I see the value of retaining
> full precision too, though, and don't feel strongly about it.
>
It should be hard to read without units. I know so now it is maybe late,
but the current output is not too readable for me. I miss units - 10s,
1m20.5s, 1h 30m 5s
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Borodin | 2016-09-08 11:51:43 | Re: GiST penalty functions [PoC] |
| Previous Message | Tom Lane | 2016-09-08 11:37:39 | Re: GiST penalty functions [PoC] |