On Mon, Oct 24, 2005 at 06:53:30PM -0600, Michael Fuhr wrote:
So in case anybody was going to check on that prior to the upcoming
8.1 release candidate, there is new timezone data available (2005n
vs. the current 2005m) but it appears to have only minor changes
for Kyrgyzstan and Uruguay. If
Michael Fuhr wrote:
I see that new timezone data is available at
ftp://elsie.nci.nih.gov/pub/
It looks like the only changes from PostgreSQL's current data involve
Kyrgyzstan and Uruguay. What's the policy on keeping the source
code up to date? Does the data change too often to bother
Bruce Momjian wrote:
Michael Fuhr wrote:
I see that new timezone data is available at
ftp://elsie.nci.nih.gov/pub/
It looks like the only changes from PostgreSQL's current data involve
Kyrgyzstan and Uruguay. What's the policy on keeping the source
code up to date? Does the data
On Mon, Oct 24, 2005 at 07:02:07PM -0400, Andrew Dunstan wrote:
There's nothing magical about the files, is there? A user should be able
to plug in a zic-compiled zone file from just about anywhere if they
really need it, without having to update postgres, or I have badly
misunderstood how
Michael Fuhr [EMAIL PROTECTED] writes:
* Update timezone data to match latest zic database (see src/timezone/README)
So in case anybody was going to check on that prior to the upcoming
8.1 release candidate, there is new timezone data available (2005n
vs. the current 2005m) but it appears to
I see that new timezone data is available at
ftp://elsie.nci.nih.gov/pub/
It looks like the only changes from PostgreSQL's current data involve
Kyrgyzstan and Uruguay. What's the policy on keeping the source
code up to date? Does the data change too often to bother except
just before a
