Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Fri, 09 May 2008 10:02:59 -0400
- Message-id: <13234(dot)1210341779(at)sss(dot)pgh(dot)pa(dot)us>
"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
- References:
- Using Epoch to save timestamps in 4 bytes?
- From: Francisco Reyes
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Bruce Momjian
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Scott Marlowe
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Merlin Moncure
- Using Epoch to save timestamps in 4 bytes?
- Prev by Date: Re: statistics collector process is thrashing my cpu
- Next by Date: Re: reproducible database crash with simple sql command on postgres 8.3.1
- Previous by thread: Re: Using Epoch to save timestamps in 4 bytes?
- Next by thread: Re: Using Epoch to save timestamps in 4 bytes?
- Indexes: