Re: Timezone matching script (win32) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Timezone matching script (win32)
Date
Msg-id 7220.1271181339@sss.pgh.pa.us
Whole thread Raw
In response to Re: Timezone matching script (win32)  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Timezone matching script (win32)  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Timezone matching script (win32)  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Magnus Hagander wrote:
>> This script should probably live in CVS, and be run when Microsoft
>> releases new timezone data. Where should I put it - src/timezone or
>> somewhere in src/tools? (it does read pgtz.c in the current directory,
>> but it doesn't actually edit the file - just outputs on stdout a list
>> of changes to be made to the file manually)

> I think it should live in src/tools and be mentioned in
> src/tools/RELEASE_CHANGES

+1 for src/tools/, but the documentation note should probably be in
src/timezone/README.  This task isn't especially coupled to release
times (at least not *our* release times).  And it's definitely not
likely to happen at the times anyone would be consulting
RELEASE_CHANGES, because none of the release leadup work gets done
on Windows machines.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Timezone matching script (win32)
Next
From: Heikki Linnakangas
Date:
Subject: Re: testing HS/SR - 1 vs 2 performance