"Anthony Taylor" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
