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: Francisco Reyes <lists(at)stringsutils(dot)com>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Using Epoch to save timestamps in 4 bytes?
- Date: Sat, 10 May 2008 20:47:11 -0400
- Message-id: <cone(dot)1210466831(dot)824341(dot)64807(dot)1000(at)zoraida(dot)natserv(dot)net>
Bruce Momjian writes:
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>
Given that all of our dates will fall within what we can store in 4bytes, what would be the easiest way to use epoch as a timestamp?
Create a couple of functions so our developers can use a date representation like '20080508 12:40:00' and have the functions tranlate strings to epoch and back?
- Follow-Ups:
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Tom Lane
- Re: Using Epoch to save timestamps in 4 bytes?
- References:
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Bruce Momjian
- Re: Using Epoch to save timestamps in 4 bytes?
- Prev by Date: ORDER BY FIELD feature
- Next by Date: Re: Using Epoch to save timestamps in 4 bytes?
- 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: