| From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
|---|---|
| To: | Tobias Brox <tobias(at)nordicbet(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Querying 19million records very slowly |
| Date: | 2005-06-22 08:55:35 |
| Message-ID: | 8B2836FF-F335-49A4-8131-8EF2D02100F9@myrealbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Jun 22, 2005, at 5:39 PM, Tobias Brox wrote:
> (btw, does postgresql really handles timezones? '+02' is quite
> different
> from 'CET', which will be obvious sometime in the late autoumn...)
Yes, it does. It doesn't (currently) record the time zone name, but
rather only the offset from UTC. If a time zone name (rather than UTC
offset) is given, it is converted to the UTC offset *at that
timestamptz* when it is stored. For time zones that take into account
DST, their UTC offset changes during the year, and PostgreSQL records
the equivalent UTC offset for the appropriate timestamptz values.
There has been discussion in the past on storing the time zone name
with the timestamptz as well, though no one has implemented this yet.
Michael Glaesemann
grzm myrealbox com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya Damle | 2005-06-22 09:03:29 | LIKE search with ending % not optimized in v8 |
| Previous Message | Tobias Brox | 2005-06-22 08:39:21 | Re: Querying 19million records very slowly |