Skip site navigation (1)
Skip section navigation (2)
While looking at a database I inheritted I noticed the database has tables with integers used to store epoch.
Peripheral Links
Header And Logo
|
Site Navigation
Using Epoch to save timestamps in 4 bytes?
- From: Francisco Reyes <lists(at)stringsutils(dot)com>
- To: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
- Subject: Using Epoch to save timestamps in 4 bytes?
- Date: Thu, 08 May 2008 23:57:47 -0400
- Message-id: <cone(dot)1210305467(dot)346740(dot)51351(dot)1000(at)zoraida(dot)natserv(dot)net>
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.
- Follow-Ups:
- Re: Using Epoch to save timestamps in 4 bytes?
- From: Bruce Momjian
- Re: Using Epoch to save timestamps in 4 bytes?
- Prev by Date: Re: Fragments in tsearch2 headline
- Next by Date: Re: Using Epoch to save timestamps in 4 bytes?
- Previous by thread: Re: Fragments in tsearch2 headline
- Next by thread: Re: Using Epoch to save timestamps in 4 bytes?
- Indexes: