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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-02 13:57:56 Re: Block-level CRC checks
Previous Message Heikki Linnakangas 2008-10-02 13:50:07 Re: Block-level CRC checks