Re: Using Epoch to save timestamps in 4 bytes?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Francisco Reyes" <lists(at)stringsutils(dot)com>, "PostgreSQL general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Using Epoch to save timestamps in 4 bytes?
Date: 2008-05-09 14:02:59
Message-ID: 13234.1210341779@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> There is nothing wrong with storing int4 epoch in your tables to save a
> little space if that suits your application.

... Just make sure you're safely away from the scene of the crime
before 2038 ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-05-09 14:18:37 Re: reproducible database crash with simple sql command on postgres 8.3.1
Previous Message Magnus Hagander 2008-05-09 13:55:16 Re: statistics collector process is thrashing my cpu