Re: [BUGS] BUG #1927: incorrect timestamp returned

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I have gone through the code and identified all the places that need
> JROUND, basically places where we do complex calculations that include
> fsec (fractional seconds). This only affects timestamp=double backends,
> not timestamp=int64.

I'm not sure I like this approach. What you've essentially done is to
remove any possibility of getting more than six digits of fractional
precision out of a "double" timestamp --- and impose nontrivial
calculation overhead to make sure that double doesn't have any extra
precision.

I think it'd probably be better to just fix the rounding during display.

regards, tom lane