Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #2996: to_char( timestamp, 'DD-Mon-YYYY HH24:MI:SS.MS' ) reports .1000 ms - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2996: to_char( timestamp, 'DD-Mon-YYYY HH24:MI:SS.MS' ) reports .1000 ms
Date
Msg-id 19218.1171439650@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2996: to_char( timestamp, 'DD-Mon-YYYY HH24:MI:SS.MS' ) reports .1000 ms  ("Anthony Taylor" <tony@tg-embedded.com>)
List pgsql-bugs
Tree view 
"Anthony Taylor" <tony@tg-embedded.com> writes:
> When using the "to_char" function to output timestamps, some timestamps
> report .1000 milliseconds.

Confirmed here: using your test case, successive timestamps look like

 14-Feb-2007 02:44:04.998
 14-Feb-2007 02:44:04.998
 14-Feb-2007 02:44:04.998
 14-Feb-2007 02:44:04.998
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.999
 14-Feb-2007 02:44:04.1000
 14-Feb-2007 02:44:04.1000
 14-Feb-2007 02:44:04.1000
 14-Feb-2007 02:44:05.000
 14-Feb-2007 02:44:05.000
 14-Feb-2007 02:44:05.000
 14-Feb-2007 02:44:05.001
 14-Feb-2007 02:44:05.001
 14-Feb-2007 02:44:05.001
 14-Feb-2007 02:44:05.001
 14-Feb-2007 02:44:05.001

Not having looked at the code, my bet is that this occurs only without
--enable-integer-timestamps; is your installation compiled with that?

It would be interesting to check what happens at an hour or day
boundary; I suspect the roundoff problem may extend to higher units.
We've seen related bugs before :-(

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3002: PQexecParams only supports some commands; needs improved error reporting, documenting or fixing
Next
From: Magnus Hagander
Date:
Subject: Re: BUG #2993: The program "postgres" is needed by initdb but was not found ...