Skip site navigation (1) Skip section navigation (2)

Re: Timing overhead and Linux clock sources

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timing overhead and Linux clock sources
Date: 2012-08-28 16:59:38
Message-ID: 20120828165938.GF16116@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Aug 28, 2012 at 10:43:07AM -0400, Robert Haas wrote:
> On Mon, Aug 27, 2012 at 11:13 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> > After staring at all the examples I generated again, I think Bruce is right
> > that the newer format he's suggesting is better.
> 
> OK by me, then.  If you're happy, I'm happy.

OK, applied.  The general rule I followed here is that if a report has a
fixed start value and a variable stop value, the start value should be
reported first.  When comparing runs, any missing (ending) rows are seen
visually as empty (at the end of the output but blank).  This isn't a
common case, so this issue doesn't come up often.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-08-28 17:06:42
Subject: Re: MySQL search query is not executing in Postgres DB
Previous:From: Bruce MomjianDate: 2012-08-28 16:55:08
Subject: Re: psql: tab-completion fails SET var=

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group