Re: \timing interval

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: \timing interval
Date: 2016-07-09 18:17:30
Message-ID: CAFj8pRB0G4bZM_DW9Ery+4zd1BzeOqidihVOO2zw1BpoL01vbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2016-07-09 18:59 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > On 7/7/16 5:52 PM, Corey Huinker wrote:
> >> Wouldn't it be great if we had a way of printing timing in more human
> >> friendly formats?
>
> > Something like what you are proposing might as well be the default and
> > only format.
>
> NAK --- if you're trying to do arithmetic on the numbers, converting
> them to hh:mm:ss notation isn't the best first step. I think a separate
> setting somewhere to select the format would be good. Please *don't*
> do "\timing interval" as that confuses the on/off state with the
> formatting selection. Maybe a \pset option?
>
>
\pset is good idea

> Also, might I suggest that leading zeroes in such a format are not
> helpful? That is, I'd want to see "1:02.345" not "00:01:02.345".
>

the value without units and without leading zeroes is not clear

Regards

Pavel

>
> regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-07-09 19:09:36 Re: \timing interval
Previous Message Greg Stark 2016-07-09 17:27:16 Re: \timing interval