Re: Using Epoch to save timestamps in 4 bytes? - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Using Epoch to save timestamps in 4 bytes?
Date
Msg-id dcc563d10805090015s10523e0dq5f274635e7419303@mail.gmail.com
Whole thread Raw
In response to Re: Using Epoch to save timestamps in 4 bytes?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Using Epoch to save timestamps in 4 bytes?
List pgsql-general
On Thu, May 8, 2008 at 10:00 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
>  Our timestamp has a much larger range than a 4-byte time_t, docs say:
>
>         <entry>4713 BC</entry>
>         <entry>294276 AD</entry>

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.  :)

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Using Epoch to save timestamps in 4 bytes?
Next
From: "Scott Marlowe"
Date:
Subject: Re: auto-vacuum questions