On 10/07/16 08:00, Andrew Gierth wrote:
"Tom" == Tom Lane <t...@sss.pgh.pa.us> writes:
  > Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes:
  >> I'm not quite sure what you mean by wanting to do arithmetic on the
  >> numbers.  My phrasing of the problem is that after a long query, you
  >> might get output like this:
  >> Time: 1234567.666 ms
  >> which is pretty useless.

  Tom> What I mean by that is that not infrequently, I'll run the same
  Tom> query several times and then want to average the results.  That's
  Tom> easy with awk or similar scripts as long as the numbers are in
  Tom> straight decimal.

  Tom> I don't mind if we provide a way to print in Babylonian-inspired
  Tom> notation(s) as well, but I'm going to be seriously annoyed if
  Tom> that's the only way to get the output.

How about

Time: 1234567.666 ms (20m 34.6s)


I like that, but I think the human form should retain the 3 decimal places.

In a few years, we may well have enormously multiprocessor computers with massive very fast permanent 'RAM' where the entire database is always in memory, so timing to the nearest microsecond could be useful. Obviously microsecond precision would be silly now, and would probably never warrant being the default (I'd be happy to be proved wrong here!), but it might be worthwhile putting in as an option - while people are looking at the relevant areas of the code.

Am inspired by the man page for 'ls': [...] The SIZE argument is an integer and optional unit (example: 10K is 10*1024). Units are K,M,G,T,P,E,Z,Y (powers of 1024) [...]" Obviously learnt from the lessons of "640KB should be enough for everyone" stupidity!


Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to