From: | phil(at)Stimpy(dot)netroedge(dot)com |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Re: Bug in date_part() |
Date: | 2001-01-18 18:13:54 |
Message-ID: | 20010118101354.H30590@Stimpy.netroedge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Ah, I think I understand the trouble now. It's good it's fixed for
the next release. And, as predicted, I'm running in a DST zone
(/etc/localtime -> ../usr/share/zoneinfo/US/Pacific)
Thanks for the quick diagnosis!
Phil
On Wed, Jan 17, 2001 at 09:07:34PM -0500, Tom Lane wrote:
> Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> >> Query to reproduce the bug (7.0.3):
> >> edge=# select date_part('dow','4/1/2001'::date)::int4;
> >> ----------
> >> 6
>
> > I'm not seeing this on my 7.0.2 RPM installation, or on my from-cvs
> > current sources (dow for April 1 comes up as zero, as you would expect).
>
> I get the right answer from current sources, and the wrong one on 7.0.2.
> It's ye olde date-to-timestamp-off-an-hour-at-DST-boundary problem.
> Are you not running in a USA timezone?
>
> regards, tom lane
--
Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR
phil(at)netroedge(dot)com -- http://www.netroedge.com/~phil
PGP F16: 01 D2 FD 01 B5 46 F4 F0 3A 8B 9D 7E 14 7F FB 7A
From | Date | Subject | |
---|---|---|---|
Next Message | Bert de Jong | 2001-01-18 21:15:44 | minor fault report |
Previous Message | Thomas Lockhart | 2001-01-18 03:43:15 | Re: Bug in date_part() |