| From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:10:23 |
| Message-ID: | CAMsr+YEA3Vk5zZZOTf7WmwDJnmrV4OcFV185jGw9=E=bHgQL8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Wagner | 2016-09-08 11:24:20 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Craig Ringer | 2016-09-08 11:04:27 | Re: High-CPU consumption on information_schema (only) query |