| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | cnliou(at)so-net(dot)net(dot)tw, "" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: TIMEZONE not working? |
| Date: | 2003-11-26 10:16:33 |
| Message-ID: | 200311261016.33530.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday 26 November 2003 09:02, cnliou wrote:
> [QUOTE]
> Note: When timestamp values are stored as double precision
> floating-point numbers (currently the default), the
> effective limit of precision may be less than 6. timestamp
> values are stored as seconds since 2000-01-01, and
> microsecond precision is achieved for dates within a few
> years of 2000-01-01, but the precision degrades for dates
> further away.
> [/QUOTE]
>
> Does this mean double timestamp, the default storage type,
> allows dates starting from 2000-1-1? I just inserted and
> selected the value '1999-1-1' without problem.
No, it means that if you have a timestamp such as
2003-11-26 10:15:27.842204+00
then the .842204 part (microseconds) gets less accurate the further away the
dates get.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Hampl | 2003-11-26 10:52:35 | Re: indexing with lower(...) -> queries are not optimised very well - Please Help |
| Previous Message | Michael Meskes | 2003-11-26 09:51:42 | Re: Embedded Vacuum Still Not Working... |