| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dana Burd <DBurd(at)cpr(dot)org> |
| Cc: | "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: to_char function has Daylight Savings Bug |
| Date: | 2003-05-15 17:26:13 |
| Message-ID: | 10391.1053019573@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dana Burd <DBurd(at)cpr(dot)org> writes:
> to_char(timestamp, 'SSSS') has a Daylight Savings bug. It includes the
> missing 2am hour in it's "seconds from midnight count" for DST begin day
> (4/6/2003), and does not include the extra hour for DST end day
> (10/26/2003).
It's not readily apparent to me that this is a bug. The SSSS value is
evidently being calculated as HH*3600+MM*60+SS, so it corresponds to the
nominal time of 3:00:00 AM. I think it would be rather surprising if
SSSS *didn't* correspond to HH:MM:SS.
However, to_char() is intended to slavishly imitate Oracle's to_char(),
warts and all. What does Oracle do with this situation?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Schmitz | 2003-05-16 19:46:24 | UPDATE has a bug to update tables with an index of 2 columns |
| Previous Message | Tom Lane | 2003-05-15 17:10:05 | Re: segfault in postmaster (pg 7.3.2 & FreeBSD) |