mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-30 10:41:18 +02:00
312d51798f
and thereby in the pg_timezone_names view. Although we allow such zones to be used in certain limited contexts like AT TIME ZONE, we don't allow them in SET TIME ZONE, and bug #4528 shows that they're more likely to confuse users than do anything useful. So hide 'em. (Note that we don't even generate these zones when installing our own timezone database. But they are likely to be present when using a system-provided database.) |
||
---|---|---|
.. | ||
data | ||
tznames | ||
ialloc.c | ||
localtime.c | ||
Makefile | ||
pgtz.c | ||
pgtz.h | ||
private.h | ||
README | ||
scheck.c | ||
strftime.c | ||
tzfile.h | ||
zic.c |
$PostgreSQL: pgsql/src/timezone/README,v 1.7 2008/03/21 13:23:29 momjian 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 2007k. 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.