Search Postgresql Archives

Re: Using Epoch to save timestamps in 4 bytes?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 support 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@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux