Re: Using Epoch to save timestamps in 4 bytes?

Francisco Reyes wrote:
> While looking at a database I inheritted I noticed the database has
tables 
> with integers used to store epoch.
> 
> I noticed that timestamp is 8 bytes and was wondering how come timestamp
is 
> 8 bytes and not 4. Is it to be able to sup****t precission beyond a
second?
> 
> I am looking at tens of millions of rows, which is why my predecessor
may 
> have used integer to store epoch to save space.    

Our timestamp has a much larger range than a 4-byte time_t, docs say:

        <entry>4713 BC</entry>
        <entry>294276 AD</entry>

-- 
  Bruce Momjian  <bruce@[EMAIL PROTECTED]
>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

-- 
Sent via pgsql-general mailing list (pgsql-general@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general