Re: New horology failure - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: New horology failure
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34BABC@algol.sollentuna.se
Whole thread Raw
In response to New horology failure  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: New horology failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: New horology failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>I get this since Tom's commit.
>
>>--- ./results/horology.out      Sun May 23 11:39:49 2004
>>***************
>>*** 1787,1796 ****
>>!      | Sat Sep 22 18:19:20 2001 PDT | @ 34 years
>        | Fri Sep 22 18:19:20 1967 PDT
>>[...]
>>--- 1787,1796 ----
>>!      | Sat Sep 22 18:19:20 2001 PDT | @ 34 years
>        | Fri Sep 22 18:19:20 1967 PST
>>[...]
>
>I got the same with snapshot-20040521 yesterday [i.e. 2004-05-22]
>afternoon when I ran make check.  But only once.  make installcheck
>passed all tests, and the failure didn't reappear when I tried make
>check again.
>
>I just got the failure again with make check after having configured
>with a new install directory.  My guess is that horology needs some
>datafile from the install location.

Not only a file, but the entire directory "<pginstall>/share/timezone",
with subdirs.

Without it, it will parse "PST8PDT" using the default DST rules. If it
finds the file (named PST8PDT in that directory), it will use the
correct DST rules.

//Magnus


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Optimizer bug??
Next
From: "Ismail Kizir"
Date:
Subject: Re: Optimizer bug??