head	1.9;
access;
symbols
	REL9_0_0:1.9
	REL9_1_ALPHA1:1.9
	REL9_0_RC1:1.9
	REL9_0_BETA4:1.9
	REL9_0_STABLE:1.9.0.2
	REL9_0_BETA3:1.9
	REL9_0_BETA2:1.9
	REL8_0_25:1.4
	REL8_1_21:1.4
	REL8_2_17:1.5
	REL8_3_11:1.5
	REL8_4_4:1.7.2.1
	REL9_0_BETA1:1.9
	REL9_0_ALPHA5_BRANCH:1.8.0.2
	REL9_0_ALPHA5:1.8
	REL8_0_24:1.4
	REL8_1_20:1.4
	REL8_2_16:1.5
	REL8_3_10:1.5
	REL8_4_3:1.7.2.1
	REL9_0_ALPHA4:1.7
	REL9_0_ALPHA4_BRANCH:1.7.0.10
	REL8_5_ALPHA3:1.7
	REL8_5_ALPHA3_BRANCH:1.7.0.8
	REL8_0_23:1.4
	REL8_1_19:1.4
	REL8_2_15:1.5
	REL8_3_9:1.5
	REL8_4_2:1.7
	REL8_5_ALPHA2:1.7
	REL8_5_ALPHA2_BRANCH:1.7.0.6
	REL8_0_22:1.4
	REL8_1_18:1.4
	REL8_2_14:1.5
	REL8_3_8:1.5
	REL8_4_1:1.7
	REL8_5_ALPHA1:1.7
	REL8_5_ALPHA1_BRANCH:1.7.0.4
	REL8_4_STABLE:1.7.0.2
	REL8_4_0:1.7
	REL8_4_RC2:1.7
	REL8_4_RC1:1.7
	REL8_4_BETA2:1.7
	REL8_4_BETA1:1.7
	REL8_0_21:1.4
	REL8_1_17:1.4
	REL8_2_13:1.5
	REL8_3_7:1.5
	REL8_0_20:1.4
	REL8_1_16:1.4
	REL8_2_12:1.5
	REL8_3_6:1.5
	REL8_0_19:1.4
	REL8_1_15:1.4
	REL8_2_11:1.5
	REL8_3_5:1.5
	REL8_0_18:1.4
	REL8_1_14:1.4
	REL8_2_10:1.5
	REL8_3_4:1.5
	REL8_0_17:1.4
	REL8_1_13:1.4
	REL8_2_9:1.5
	REL8_3_3:1.5
	REL8_0_16:1.4
	REL8_1_12:1.4
	REL8_2_8:1.5
	REL8_3_2:1.5
	REL8_2_7:1.5
	REL8_3_1:1.5
	REL8_3_STABLE:1.5.0.4
	REL8_3_0:1.5
	REL8_3_RC2:1.5
	REL8_0_15:1.4
	REL8_1_11:1.4
	REL8_2_6:1.5
	REL8_3_RC1:1.5
	REL8_3_BETA4:1.5
	REL8_3_BETA3:1.5
	REL8_3_BETA2:1.5
	REL8_3_BETA1:1.5
	REL8_0_14:1.4
	REL8_1_10:1.4
	REL8_2_5:1.5
	REL8_0_13:1.4
	REL8_1_9:1.4
	REL8_2_4:1.5
	REL8_0_12:1.4
	REL8_1_8:1.4
	REL8_2_3:1.5
	REL8_0_11:1.4
	REL8_1_7:1.4
	REL8_2_2:1.5
	REL8_0_10:1.4
	REL8_1_6:1.4
	REL8_2_1:1.5
	REL8_2_STABLE:1.5.0.2
	REL8_2_0:1.5
	REL8_2_RC1:1.5
	REL8_2_BETA3:1.5
	REL8_2_BETA2:1.5
	REL8_1_5:1.4
	REL8_0_9:1.4
	REL8_2_BETA1:1.5
	REL8_0_8:1.4
	REL8_1_4:1.4
	REL8_0_7:1.4
	REL8_1_3:1.4
	REL8_0_6:1.4
	REL8_1_2:1.4
	REL8_0_5:1.4
	REL8_1_1:1.4
	REL8_1_STABLE:1.4.0.6
	REL8_1_0:1.4
	REL8_1_0RC1:1.4
	REL8_1_0BETA4:1.4
	REL8_1_0BETA3:1.4
	REL8_0_4:1.4
	REL8_1_0BETA2:1.4
	REL8_1_0BETA1:1.4
	REL8_0_3:1.4
	REL8_0_2:1.4
	REL8_0_1:1.4
	REL8_0_STABLE:1.4.0.4
	REL8_0_0:1.4.0.2
	REL8_0_0RC5:1.4
	REL8_0_0RC4:1.4
	REL8_0_0RC3:1.4
	REL8_0_0RC2:1.4
	REL8_0_0RC1:1.4
	REL8_0_0BETA5:1.4
	REL8_0_0BETA4:1.4
	REL8_0_0BETA3:1.3
	REL8_0_0BETA2:1.3
	REL8_0_0BETA1:1.3;
locks; strict;
comment	@# @;


1.9
date	2010.04.15.11.00.45;	author mha;	state Exp;
branches;
next	1.8;

1.8
date	2010.03.11.18.43.24;	author tgl;	state Exp;
branches;
next	1.7;

1.7
date	2008.03.21.13.23.29;	author momjian;	state Exp;
branches
	1.7.2.1;
next	1.6;

1.6
date	2008.02.16.21.16.04;	author tgl;	state Exp;
branches;
next	1.5;

1.5
date	2006.07.25.03.51.22;	author tgl;	state Exp;
branches;
next	1.4;

1.4
date	2004.10.24.15.01.54;	author tgl;	state Exp;
branches;
next	1.3;

1.3
date	2004.05.21.05.08.06;	author tgl;	state Exp;
branches;
next	1.2;

1.2
date	2004.04.30.04.14.06;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2004.04.30.04.09.23;	author momjian;	state Exp;
branches;
next	;

1.7.2.1
date	2010.03.11.18.43.32;	author tgl;	state Exp;
branches;
next	;


desc
@@


1.9
log
@Add script to enumerate the timezones in the Windows registry and compare
it with the list we have in pgtz.c, showing any differences.
@
text
@$PostgreSQL: pgsql/src/timezone/README,v 1.8 2010/03/11 18:43:24 tgl Exp $

Timezone
========

This is a PostgreSQL adapted version of the timezone library from:

	ftp://elsie.nci.nih.gov/pub/tzcode*.tar.gz

The code is currently synced with release 2010c.  There are many cosmetic
(and not so cosmetic) differences from the original tzcode library, but
diffs in the upstream version should usually be propagated to our version.

The data files under data/ are an exact copy of the latest data set from:

	ftp://elsie.nci.nih.gov/pub/tzdata*.tar.gz

Since time zone rules change frequently in some parts of the world,
we should endeavor to update the data files before each PostgreSQL
release.

At each update, we should check if time zone offsets have changed.
Just search for the current or previous year and see what has changed.
Sometimes a country changes its time zone offsets, for example Georgia
in 2004.  Just grepping in the zic database files for 2004 is enough to
spot such a change.  Then the files under tznames/ should be updated.

When there has been a new release of Windows (probably including Service
Packs), the list of matching timezones need to be updated. Run the
script in src/tools/win32tzlist.pl on a Windows machine running this new
release and apply any new timezones that it detects. Never remove any
mappings in case they are removed in Windows, since we still need to
match properly on the old version.
@


1.8
log
@Sync timezone code with tzcode 2010c from the Olson group.  This fixes some
corner cases that come up in certain timezones (apparently, only those with
lots and lots of distinct TZ transition rules, as far as I can gather from
a quick scan of their archives).  Per suggestion from Jeevan Chalke.

Back-patch to 8.4.  Possibly we need to push this into earlier releases
as well, but I'm hesitant to update them to the 64-bit tzcode without
more thought and testing.
@
text
@d1 1
a1 1
$PostgreSQL: pgsql/src/timezone/README,v 1.7 2008/03/21 13:23:29 momjian Exp $
d27 7
@


1.7
log
@More README src cleanups.
@
text
@d1 1
a1 1
$PostgreSQL: pgsql/src/backend/access/gin/README,v 1.5 2008/03/20 17:55:14 momjian Exp $
d10 1
a10 1
The code is currently synced with release 2007k.  There are many cosmetic
@


1.7.2.1
log
@Sync timezone code with tzcode 2010c from the Olson group.  This fixes some
corner cases that come up in certain timezones (apparently, only those with
lots and lots of distinct TZ transition rules, as far as I can gather from
a quick scan of their archives).  Per suggestion from Jeevan Chalke.

Back-patch to 8.4.  Possibly we need to push this into earlier releases
as well, but I'm hesitant to update them to the 64-bit tzcode without
more thought and testing.
@
text
@d1 1
a1 1
$PostgreSQL: pgsql/src/timezone/README,v 1.7 2008/03/21 13:23:29 momjian Exp $
d10 1
a10 1
The code is currently synced with release 2010c.  There are many cosmetic
@


1.6
log
@Update timezone code to track the upstream changes since 2003.  In particular
this adds support for 64-bit tzdata files, which is needed to support DST
calculations beyond 2038.  Add a regression test case to give some minimal
confidence that that really works.

Heikki Linnakangas
@
text
@d1 5
@


1.5
log
@Remove hard-wired lists of timezone abbreviations in favor of providing
configuration files that can be altered by a DBA.  The australian_timezones
GUC setting disappears, replaced by a timezone_abbreviations setting (set this
to 'Australia' to get the effect of australian_timezones).  The list of zone
names defined by default has undergone a bit of cleanup, too.  Documentation
still needs some work --- in particular, should we fix Table B-4, or just get
rid of it?  Joachim Wieland, with some editorializing by moi.
@
text
@d1 1
a1 2
This is a PostgreSQL adapted version of the timezone library
from:
d5 5
a9 2
The data files under data/ are an exact copy of the latest data set
from
@


1.4
log
@Update RELEASE_CHANGES to mention updating the timezone database as
a routine part of release prep.
@
text
@d14 6
@


1.3
log
@Integrate src/timezone library for all platforms.  There is more we can
and should do now that we control our own destiny for timezone handling,
but this commit gets the bulk of the picayune diffs in place.
Magnus Hagander and Tom Lane.
@
text
@d4 1
a4 1
	ftp://elsie.nci.nih.gov/pub/tz*.tar.gz
d6 8
@


1.2
log
@Minor adjustments to enable public-domain timezone library to be called
from our code.
@
text
@a5 12
The interface is used when USE_PGTZ is defined at the top level. This
will cause the following functions to be redefined:
  localtime		pg_localtime
  gmtime		pg_gmtime
  asctime		pg_asctime
  ctime			pg_ctime
  difftime		pg_difftime
  mktime		pg_mktime
  tzset			pg_tzset

and the TIMEZONE_GLOBAL define in c.h is redefined to pg_timezone.

@


1.1
log
@Add Olson's public domain timezone library to src/timezone.
@
text
@a2 1
ftp://elsie.nci.nih.gov/pub/tz*.tar.gz
d4 1
@

