| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | Rob Richardson <Rob(dot)Richardson(at)rad-con(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: A simpler time zone question |
| Date: | 2011-03-28 16:18:40 |
| Message-ID: | 20594.1301329120@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
> On 03/28/2011 08:57 AM, Tom Lane wrote:
>> Yes, I believe that's even documented somewhere. I think it will also
>> do that if the time is impossible (eg, 02:30 during a forward DST jump)
> I'd love a link to the documentation specifying that behavior. I've
> spent a while searching and have thus-far failed to locate it.
Hmm. The code is perfectly clear about it, see DetermineTimeZoneOffset:
/*
* It's an invalid or ambiguous time due to timezone transition. Prefer
* the standard-time interpretation.
*/
but right offhand I don't see any mention of ambiguous times in the
likely parts of the documentation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2011-03-28 16:21:38 | Re: Disk space usage analyzer? |
| Previous Message | Steve Crawford | 2011-03-28 16:12:47 | Re: A simpler time zone question |