Re: Timing overhead and Linux clock sources - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Timing overhead and Linux clock sources
Date
Msg-id 20120828165938.GF16116@momjian.us
Whole thread Raw
In response to Re: Timing overhead and Linux clock sources  (Robert Haas <robertmhaas@gmail.com>)
List 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@2ndquadrant.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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: psql: tab-completion fails SET var=
Next
From: Tom Lane
Date:
Subject: Re: MySQL search query is not executing in Postgres DB