From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: timestamp skew during 7.4 -> 8.2 upgrade |
Date: | 2007-08-10 20:59:52 |
Message-ID: | 13855.1186779592@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> writes:
> On Fri, Aug 10, 2007 at 10:11:29AM +0200, Louis-David Mitterrand wrote:
>> So if I understand correctly, a timestamp_tz is ...
> ... stored as UTC in the backend
> ... sent to clients shifted by whatever timezone was
> requested by the client by one of several mechanisms:
> - "set timezone to ..." used by the client
> - "select ... at time zone ..." used by the client
> - the server timezone if neither of the above is used
The other point to be clear on is that the "shifting" is done according
to whatever timezone rule files the server currently has. Since
politicians keep changing daylight-savings rules, the same UTC date/time
might be displayed differently after an update of the relevant rule
file.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Ortíz | 2007-08-10 21:03:48 | Re: SQL question: checking all required items |
Previous Message | Scott Marlowe | 2007-08-10 20:42:45 | Re: SQL question: checking all required items |