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

Re: Interval output bug in HAVE_INT64_TIMESTAMP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Interval output bug in HAVE_INT64_TIMESTAMP
Date: 2008-10-02 13:50:22
Message-ID: 27156.1222955422@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> writes:
> Seems to me there's a bug in HEAD (and probably old branches
> as well) when compiled with HAVE_INT64_TIMESTAMP.  As shown below
> It sometimes shows things like "-6.-70 secs" where 8.3
> showed "-6.70 secs".

> I think the attached one-liner patch fixes this, as well as
> another roundoff regression between HEAD and 8.3.

Yeah, bug all the way back --- applied.

I don't much like the forced rounding to two digits here, but changing
that doesn't seem like material for back-patching.  Are you going to
fix that up while working on your other patches?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-10-02 13:57:56
Subject: Re: Block-level CRC checks
Previous:From: Heikki LinnakangasDate: 2008-10-02 13:50:07
Subject: Re: Block-level CRC checks

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