From: | Wolfgang Keller <wolfgang(dot)keller(dot)privat(at)gmx(dot)de> |
---|---|
To: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Precision of time types |
Date: | 2007-11-13 11:45:39 |
Message-ID: | 988223449A3F5A0D4A67CE35@[192.168.1.25] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hello,
and yet another clueless newbie question:
The precision of time types is specified as follows in the
documentation:
"For the time types, the allowed range of p is from 0 to 6 when
eight-byte integer storage is used, or from 0 to 10 when floating-point
storage is used."
When/how is the internal storage method determined?
Compile-time option?
Database-initialisation time option?
Other?
Unfortunately, the schema I am trying to implement using PostgreSQL
specifies 9 digits (nanosecond precision) for its custom datetime
column (don't ask me why, I'M just a poor mech eng).
So, do I need to use a numeric type for the seconds and define my own
composite datetime column or can I use a properly parameterized
built-in time type of PostgreSQL?
TIA,
Sincerely,
Wolfgang Keller
From | Date | Subject | |
---|---|---|---|
Next Message | gokul | 2007-11-13 16:52:34 | Re: postgresql 8.1.10-1PGDG (32 bit) installaion on RHEL 4 |
Previous Message | Wolfgang Keller | 2007-11-13 11:32:04 | Composite types for composite primary/foreign keys? |