Re: Using Epoch to save timestamps in 4 bytes?

On Thu, May 8, 2008 at 10:00 PM, Bruce Momjian  wrote:
>
>  Our timestamp has a much larger range than a 4-byte time_t, docs say:
>
>         4713 BC
>         294276 AD

Which is normally great.  Doesn't it have greater precision in the
modern era or something like that?

If you compile for integer dates do they have the same range?

Also, that range is fine, unless you're tracking geological timeframes.  :)