Skip site navigation (1) Skip section navigation (2)

Re: Timezone matching script (win32)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timezone matching script (win32)
Date: 2010-04-13 19:00:25
Message-ID: 20100413190025.GD2990@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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.

True, but if there's a www.microsoft.com URL that could be checked for
timezone updates, perhaps we don't need a Windows machine.  In any case,
perhaps whoever does the release work can *ask* someone else to provide
the Windows TZ patch.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-04-13 19:03:58
Subject: Re: a faster compression algorithm for pg_dump
Previous:From: Heikki LinnakangasDate: 2010-04-13 18:09:46
Subject: Re: testing HS/SR - 1 vs 2 performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group