Re: Re: Bug in date_part()

Поиск
Список
Период
Сортировка
От phil@Stimpy.netroedge.com
Тема Re: Re: Bug in date_part()
Дата
Msg-id 20010118101354.H30590@Stimpy.netroedge.com
обсуждение исходный текст
Ответ на Re: Re: Bug in date_part()  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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@alumni.caltech.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@netroedge.com -- http://www.netroedge.com/~phil
 PGP F16: 01 D2 FD 01 B5 46 F4 F0  3A 8B 9D 7E 14 7F FB 7A

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Bert de Jong"
Дата:
Сообщение: minor fault report
Следующее
От: pgsql-bugs@postgresql.org
Дата:
Сообщение: ascii() picks up sign bit past CHAR value 127