Re: [pgsql-hackers-win32] Weird new time zone

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Oliver Jowett" <oliver(at)opencloud(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [pgsql-hackers-win32] Weird new time zone
Date: 2004-07-22 11:15:27
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184D164@m0114.s-mxs.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > DEBUG: TZ "Antarctica/McMurdo" scores 2534: at -442152000
> 1955-12-28 12:00:00 std versus 1955-12-29 00:00:00 std
> > DEBUG: TZ "Antarctica/South_Pole" scores 2534: at
> -442152000 1955-12-28 12:00:00 std versus 1955-12-29 00:00:00 std
> > DEBUG: TZ "Pacific/Auckland" gets max score 2600
> > DEBUG: TZ "NZ" gets max score 2600
>
> and it picks Pacific/Auckland.
>
> Also I'm a bit nervous about that hardcoded 2004 start date for the scan
> in pgtz.c -- that will presumably break if the timezone data files are
> updated for post-2004 changes without a corresponding change to the scan

Yes, how about scanning forward iff it is still a breakeven ?

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Jowett 2004-07-22 11:32:16 Re: [JDBC] V3 protocol + DECLARE problems
Previous Message Oliver Jowett 2004-07-22 10:58:27 Re: [pgsql-hackers-win32] Weird new time zone