Re: fixes for date_part micro/millisecond precision

> > I have been thinking of implementing timestamp (and other related types)
> > as 8 byte integers, which are not slow on some platforms. doubles are
> > fast on most platforms nowadays.
> OTOH, 8 byte integers fail to exist at all on some other platforms.

Sure. It would be selectable at configure/build time. Failing to support
int64 would mean you don't get the integer alternative for timestamp
either.

> > The tradeoff will be repeatability vs
> > range, since we will not get the quasi-infinite range we have now when
> > using a fixed decimal type.
> If we didn't mind increasing the storage requirement, we could do
> "float8 for the integral seconds, plus an int4 for the nanoseconds",
> which would work perfectly out to about 2^52 seconds either way from the
> epoch, and continue to work with reduced accuracy until the heat death
> of the universe. But this would be 12 bytes, plus 4 bytes alignment
> padding on some platforms, which might be excessive just to guarantee
> nanosecond precision out to the next geological era.

Yes. Mixing the float with the int seems to invite math troubles though
(as does the struct solution of using two ints, since roundoff and
carryover might be troublesome).

Just a thought for now, but the int8 alternative may be pretty easy to
do.

- Thomas