Re: \timing interval - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: \timing interval
Date
Msg-id 87poqm5pty.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: \timing interval  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Responses Re: \timing interval  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
List pgsql-hackers
>>>>> "Gavin" == Gavin Flower <GavinFlower@archidevsys.co.nz> writes:
>> How about>> >> Time: 1234567.666 ms (20m 34.6s)
Gavin> I like that, but I think the human form should retain the 3Gavin> decimal places.

Scale it.

Time: 12.345 ms (0.012345s)

Time: 1234.567 ms (1.235s)

Time: 98765.432 ms (98.8s)

Time: 123456.789 ms (2m 3.5s)

Time: 12345678.666 ms (3h 24m 46s)
Gavin> In a few years, we may well have enormously multiprocessorGavin> computers with massive very fast permanent
'RAM'where theGavin> entire database is always in memory, so timing to the nearestGavin> microsecond could be useful.
 

But the original microsecond-resolution value is still right there, so I
don't see the issue.

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: \timing interval
Next
From: Gavin Flower
Date:
Subject: Re: \timing interval