From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Justin <justin(at)emproshunts(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: timestamps-accuracy |
Date: | 2008-05-09 09:16:13 |
Message-ID: | 20080509091613.GA15417@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 09, 2008 at 04:59:30AM -0400, Justin wrote:
> generail this don't hurt us but we have some needs with data coming from
> manufacturing testing applications that needs to keep the timestamps to
> .000,000,001 aka 1 nano second.
> what would be the easiest way to do this?
I would suggest storing it as epoch time (seconds since X) in a numeric
fields and create some helper functions to get data in and out in the
right format. Or a timestamp(0) column with an additional nano-second
column.
Depending on how often you use it it may be interesting to create a
specific type, but this may come close enough.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | josep porres | 2008-05-09 09:41:26 | Re: reproducible database crash with simple sql command on postgres 8.3.1 |
Previous Message | Justin | 2008-05-09 08:59:30 | timestamps-accuracy |