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

From Bruce Momjian
Subject Re: Using Epoch to save timestamps in 4 bytes?
Date
Msg-id 200805090400.m4940pY21053@momjian.us
Whole thread Raw
In response to Using Epoch to save timestamps in 4 bytes?  (Francisco Reyes <lists@stringsutils.com>)
Responses Re: Using Epoch to save timestamps in 4 bytes?  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

pgsql-general by date:

Previous
From: Francisco Reyes
Date:
Subject: Using Epoch to save timestamps in 4 bytes?
Next
From: "Scott Marlowe"
Date:
Subject: Re: Using Epoch to save timestamps in 4 bytes?