2006-07-25 05:51:23 +02:00
|
|
|
|
#
|
|
|
|
|
# NOTE:
|
|
|
|
|
# This file is NOT loaded by the PostgreSQL database. It just serves as
|
|
|
|
|
# a template for timezones you could need. See the `Date/Time Support'
|
|
|
|
|
# appendix in the PostgreSQL documentation for more information.
|
|
|
|
|
#
|
2010-09-20 22:08:53 +02:00
|
|
|
|
# src/timezone/tznames/Europe.txt
|
2006-07-25 15:49:21 +02:00
|
|
|
|
#
|
2006-07-25 05:51:23 +02:00
|
|
|
|
|
2014-11-17 18:08:02 +01:00
|
|
|
|
# CONFLICT! BST is not unique
|
|
|
|
|
# Other timezones:
|
|
|
|
|
# - BST: Bougainville Standard Time (Papua New Guinea)
|
2006-07-25 05:51:23 +02:00
|
|
|
|
BST 3600 D # British Summer Time
|
|
|
|
|
# (Europe/London)
|
|
|
|
|
CEST 7200 D # Central Europe Summer Time
|
|
|
|
|
# (Africa/Ceuta)
|
|
|
|
|
# (Europe/Amsterdam)
|
|
|
|
|
# (Europe/Andorra)
|
|
|
|
|
# (Europe/Belgrade)
|
|
|
|
|
# (Europe/Berlin)
|
|
|
|
|
# (Europe/Brussels)
|
|
|
|
|
# (Europe/Budapest)
|
|
|
|
|
# (Europe/Copenhagen)
|
|
|
|
|
# (Europe/Gibraltar)
|
|
|
|
|
# (Europe/Luxembourg)
|
|
|
|
|
# (Europe/Madrid)
|
|
|
|
|
# (Europe/Malta)
|
|
|
|
|
# (Europe/Monaco)
|
|
|
|
|
# (Europe/Oslo)
|
|
|
|
|
# (Europe/Paris)
|
|
|
|
|
# (Europe/Prague)
|
|
|
|
|
# (Europe/Rome)
|
|
|
|
|
# (Europe/Stockholm)
|
|
|
|
|
# (Europe/Tirane)
|
|
|
|
|
# (Europe/Vaduz)
|
|
|
|
|
# (Europe/Vienna)
|
|
|
|
|
# (Europe/Warsaw)
|
|
|
|
|
# (Europe/Zurich)
|
|
|
|
|
CET 3600 # Central Europe Time
|
|
|
|
|
# (Africa/Algiers)
|
|
|
|
|
# (Africa/Ceuta)
|
|
|
|
|
# (Europe/Amsterdam)
|
|
|
|
|
# (Europe/Andorra)
|
|
|
|
|
# (Europe/Belgrade)
|
|
|
|
|
# (Europe/Berlin)
|
|
|
|
|
# (Europe/Brussels)
|
|
|
|
|
# (Europe/Budapest)
|
|
|
|
|
# (Europe/Copenhagen)
|
|
|
|
|
# (Europe/Gibraltar)
|
|
|
|
|
# (Europe/Luxembourg)
|
|
|
|
|
# (Europe/Madrid)
|
|
|
|
|
# (Europe/Malta)
|
|
|
|
|
# (Europe/Monaco)
|
|
|
|
|
# (Europe/Oslo)
|
|
|
|
|
# (Europe/Paris)
|
|
|
|
|
# (Europe/Prague)
|
|
|
|
|
# (Europe/Rome)
|
|
|
|
|
# (Europe/Stockholm)
|
|
|
|
|
# (Europe/Tirane)
|
|
|
|
|
# (Europe/Vaduz)
|
|
|
|
|
# (Europe/Vienna)
|
|
|
|
|
# (Europe/Warsaw)
|
|
|
|
|
# (Europe/Zurich)
|
|
|
|
|
CETDST 7200 D # Central Europe Summer Time
|
|
|
|
|
# (Africa/Ceuta)
|
|
|
|
|
# (Europe/Amsterdam)
|
|
|
|
|
# (Europe/Andorra)
|
|
|
|
|
# (Europe/Belgrade)
|
|
|
|
|
# (Europe/Berlin)
|
|
|
|
|
# (Europe/Brussels)
|
|
|
|
|
# (Europe/Budapest)
|
|
|
|
|
# (Europe/Copenhagen)
|
|
|
|
|
# (Europe/Gibraltar)
|
|
|
|
|
# (Europe/Luxembourg)
|
|
|
|
|
# (Europe/Madrid)
|
|
|
|
|
# (Europe/Malta)
|
|
|
|
|
# (Europe/Monaco)
|
|
|
|
|
# (Europe/Oslo)
|
|
|
|
|
# (Europe/Paris)
|
|
|
|
|
# (Europe/Prague)
|
|
|
|
|
# (Europe/Rome)
|
|
|
|
|
# (Europe/Stockholm)
|
|
|
|
|
# (Europe/Tirane)
|
|
|
|
|
# (Europe/Vaduz)
|
|
|
|
|
# (Europe/Vienna)
|
|
|
|
|
# (Europe/Warsaw)
|
|
|
|
|
# (Europe/Zurich)
|
|
|
|
|
EEST 10800 D # East-Egypt Summertime
|
|
|
|
|
# Eastern Europe Summer Time
|
|
|
|
|
# (Africa/Cairo)
|
|
|
|
|
# (Asia/Amman)
|
|
|
|
|
# (Asia/Beirut)
|
|
|
|
|
# (Asia/Damascus)
|
|
|
|
|
# (Asia/Gaza)
|
|
|
|
|
# (Asia/Nicosia)
|
|
|
|
|
# (Europe/Athens)
|
|
|
|
|
# (Europe/Bucharest)
|
|
|
|
|
# (Europe/Chisinau)
|
|
|
|
|
# (Europe/Helsinki)
|
|
|
|
|
# (Europe/Istanbul)
|
|
|
|
|
# (Europe/Kaliningrad)
|
|
|
|
|
# (Europe/Kiev)
|
|
|
|
|
# (Europe/Minsk)
|
|
|
|
|
# (Europe/Riga)
|
|
|
|
|
# (Europe/Simferopol)
|
|
|
|
|
# (Europe/Sofia)
|
|
|
|
|
# (Europe/Tallinn)
|
|
|
|
|
# (Europe/Uzhgorod)
|
|
|
|
|
# (Europe/Vilnius)
|
|
|
|
|
# (Europe/Zaporozhye)
|
|
|
|
|
EET 7200 # East-Egypt Time
|
|
|
|
|
# Eastern Europe Time
|
|
|
|
|
# (Africa/Cairo)
|
|
|
|
|
# (Africa/Tripoli)
|
|
|
|
|
# (Asia/Amman)
|
|
|
|
|
# (Asia/Beirut)
|
|
|
|
|
# (Asia/Damascus)
|
|
|
|
|
# (Asia/Gaza)
|
|
|
|
|
# (Asia/Nicosia)
|
|
|
|
|
# (Europe/Athens)
|
|
|
|
|
# (Europe/Bucharest)
|
|
|
|
|
# (Europe/Chisinau)
|
|
|
|
|
# (Europe/Helsinki)
|
|
|
|
|
# (Europe/Istanbul)
|
|
|
|
|
# (Europe/Kaliningrad)
|
|
|
|
|
# (Europe/Kiev)
|
|
|
|
|
# (Europe/Minsk)
|
|
|
|
|
# (Europe/Riga)
|
|
|
|
|
# (Europe/Simferopol)
|
|
|
|
|
# (Europe/Sofia)
|
|
|
|
|
# (Europe/Tallinn)
|
|
|
|
|
# (Europe/Uzhgorod)
|
|
|
|
|
# (Europe/Vilnius)
|
|
|
|
|
# (Europe/Zaporozhye)
|
|
|
|
|
EETDST 10800 D # East-Egypt Summertime
|
|
|
|
|
# Eastern Europe Summer Time
|
|
|
|
|
# (Africa/Cairo)
|
|
|
|
|
# (Asia/Amman)
|
|
|
|
|
# (Asia/Beirut)
|
|
|
|
|
# (Asia/Damascus)
|
|
|
|
|
# (Asia/Gaza)
|
|
|
|
|
# (Asia/Nicosia)
|
|
|
|
|
# (Europe/Athens)
|
|
|
|
|
# (Europe/Bucharest)
|
|
|
|
|
# (Europe/Chisinau)
|
|
|
|
|
# (Europe/Helsinki)
|
|
|
|
|
# (Europe/Istanbul)
|
|
|
|
|
# (Europe/Kaliningrad)
|
|
|
|
|
# (Europe/Kiev)
|
|
|
|
|
# (Europe/Minsk)
|
|
|
|
|
# (Europe/Riga)
|
|
|
|
|
# (Europe/Simferopol)
|
|
|
|
|
# (Europe/Sofia)
|
|
|
|
|
# (Europe/Tallinn)
|
|
|
|
|
# (Europe/Uzhgorod)
|
|
|
|
|
# (Europe/Vilnius)
|
|
|
|
|
# (Europe/Zaporozhye)
|
2014-11-17 18:08:02 +01:00
|
|
|
|
FET 10800 # Further-eastern European Time (obsolete)
|
2013-01-14 20:45:40 +01:00
|
|
|
|
# (Europe/Kaliningrad)
|
|
|
|
|
# (Europe/Minsk)
|
2006-07-25 05:51:23 +02:00
|
|
|
|
GMT 0 # Greenwich Mean Time
|
|
|
|
|
# (Africa/Abidjan)
|
|
|
|
|
# (Africa/Bamako)
|
|
|
|
|
# (Africa/Banjul)
|
|
|
|
|
# (Africa/Bissau)
|
|
|
|
|
# (Africa/Conakry)
|
|
|
|
|
# (Africa/Dakar)
|
|
|
|
|
# (Africa/Lome)
|
|
|
|
|
# (Africa/Monrovia)
|
|
|
|
|
# (Africa/Nouakchott)
|
|
|
|
|
# (Africa/Ouagadougou)
|
|
|
|
|
# (Africa/Sao_Tome)
|
|
|
|
|
# (America/Danmarkshavn)
|
|
|
|
|
# (Atlantic/Reykjavik)
|
|
|
|
|
# (Atlantic/St_Helena)
|
|
|
|
|
# (Etc/GMT)
|
|
|
|
|
# (Europe/Dublin)
|
|
|
|
|
# (Europe/London)
|
|
|
|
|
# CONFLICT! IST is not unique
|
|
|
|
|
# Other timezones:
|
|
|
|
|
# - IST: Indian Standard Time (Asia)
|
|
|
|
|
# - IST: Israel Standard Time (Asia)
|
|
|
|
|
IST 3600 D # Irish Summer Time
|
|
|
|
|
# (Europe/Dublin)
|
|
|
|
|
MEST 7200 D # Middle Europe Summer Time (not in zic)
|
|
|
|
|
MET 3600 # Middle Europe Time (not in zic)
|
|
|
|
|
METDST 7200 D # Middle Europe Summer Time (not in zic)
|
|
|
|
|
MEZ 3600 # Mitteleurop<6F>ische Zeit (German) (not in zic)
|
Update time zone abbreviation lists for changes missed since 2006.
Most (all?) of Russia has moved to what's effectively year-round daylight
savings time, so that the "standard" zone names now mean an hour later
than they used to. Update that, notably changing MSK as per recent
complaint from Sergey Konoplev, but also CHOT, GET, IRKT, KGT, KRAT,
MAGT, NOVT, OMST, VLAT, YAKT, YEKT. The corresponding DST abbreviations
are presumably now obsolete, but I left them in place with their old
definitions, just to reduce any possible breakage from this change.
Also add VOLT (Europe/Volgograd), which for some reason we never had
before, as well as MIST (Antarctica/Macquarie), and fix obsolete
definitions of MAWT, TKT, and WST.
2013-03-24 00:16:36 +01:00
|
|
|
|
MSD 14400 D # Moscow Daylight Time (obsolete)
|
Support timezone abbreviations that sometimes change.
Up to now, PG has assumed that any given timezone abbreviation (such as
"EDT") represents a constant GMT offset in the usage of any particular
region; we had a way to configure what that offset was, but not for it
to be changeable over time. But, as with most things horological, this
view of the world is too simplistic: there are numerous regions that have
at one time or another switched to a different GMT offset but kept using
the same timezone abbreviation. Almost the entire Russian Federation did
that a few years ago, and later this month they're going to do it again.
And there are similar examples all over the world.
To cope with this, invent the notion of a "dynamic timezone abbreviation",
which is one that is referenced to a particular underlying timezone
(as defined in the IANA timezone database) and means whatever it currently
means in that zone. For zones that use or have used daylight-savings time,
the standard and DST abbreviations continue to have the property that you
can specify standard or DST time and get that time offset whether or not
DST was theoretically in effect at the time. However, the abbreviations
mean what they meant at the time in question (or most recently before that
time) rather than being absolutely fixed.
The standard abbreviation-list files have been changed to use this behavior
for abbreviations that have actually varied in meaning since 1970. The
old simple-numeric definitions are kept for abbreviations that have not
changed, since they are a bit faster to resolve.
While this is clearly a new feature, it seems necessary to back-patch it
into all active branches, because otherwise use of Russian zone
abbreviations is going to become even more problematic than it already was.
This change supersedes the changes in commit 513d06ded et al to modify the
fixed meanings of the Russian abbreviations; since we've not shipped that
yet, this will avoid an undesirably incompatible (not to mention incorrect)
change in behavior for timestamps between 2011 and 2014.
This patch makes some cosmetic changes in ecpglib to keep its usage of
datetime lookup tables as similar as possible to the backend code, but
doesn't do anything about the increasingly obsolete set of timezone
abbreviation definitions that are hard-wired into ecpglib. Whatever we
do about that will likely not be appropriate material for back-patching.
Also, a potential free() of a garbage pointer after an out-of-memory
failure in ecpglib has been fixed.
This patch also fixes pre-existing bugs in DetermineTimeZoneOffset() that
caused it to produce unexpected results near a timezone transition, if
both the "before" and "after" states are marked as standard time. We'd
only ever thought about or tested transitions between standard and DST
time, but that's not what's happening when a zone simply redefines their
base GMT offset.
In passing, update the SGML documentation to refer to the Olson/zoneinfo/
zic timezone database as the "IANA" database, since it's now being
maintained under the auspices of IANA.
2014-10-16 21:22:10 +02:00
|
|
|
|
MSK Europe/Moscow # Moscow Time
|
2006-07-25 05:51:23 +02:00
|
|
|
|
# (Europe/Moscow)
|
Support timezone abbreviations that sometimes change.
Up to now, PG has assumed that any given timezone abbreviation (such as
"EDT") represents a constant GMT offset in the usage of any particular
region; we had a way to configure what that offset was, but not for it
to be changeable over time. But, as with most things horological, this
view of the world is too simplistic: there are numerous regions that have
at one time or another switched to a different GMT offset but kept using
the same timezone abbreviation. Almost the entire Russian Federation did
that a few years ago, and later this month they're going to do it again.
And there are similar examples all over the world.
To cope with this, invent the notion of a "dynamic timezone abbreviation",
which is one that is referenced to a particular underlying timezone
(as defined in the IANA timezone database) and means whatever it currently
means in that zone. For zones that use or have used daylight-savings time,
the standard and DST abbreviations continue to have the property that you
can specify standard or DST time and get that time offset whether or not
DST was theoretically in effect at the time. However, the abbreviations
mean what they meant at the time in question (or most recently before that
time) rather than being absolutely fixed.
The standard abbreviation-list files have been changed to use this behavior
for abbreviations that have actually varied in meaning since 1970. The
old simple-numeric definitions are kept for abbreviations that have not
changed, since they are a bit faster to resolve.
While this is clearly a new feature, it seems necessary to back-patch it
into all active branches, because otherwise use of Russian zone
abbreviations is going to become even more problematic than it already was.
This change supersedes the changes in commit 513d06ded et al to modify the
fixed meanings of the Russian abbreviations; since we've not shipped that
yet, this will avoid an undesirably incompatible (not to mention incorrect)
change in behavior for timestamps between 2011 and 2014.
This patch makes some cosmetic changes in ecpglib to keep its usage of
datetime lookup tables as similar as possible to the backend code, but
doesn't do anything about the increasingly obsolete set of timezone
abbreviation definitions that are hard-wired into ecpglib. Whatever we
do about that will likely not be appropriate material for back-patching.
Also, a potential free() of a garbage pointer after an out-of-memory
failure in ecpglib has been fixed.
This patch also fixes pre-existing bugs in DetermineTimeZoneOffset() that
caused it to produce unexpected results near a timezone transition, if
both the "before" and "after" states are marked as standard time. We'd
only ever thought about or tested transitions between standard and DST
time, but that's not what's happening when a zone simply redefines their
base GMT offset.
In passing, update the SGML documentation to refer to the Olson/zoneinfo/
zic timezone database as the "IANA" database, since it's now being
maintained under the auspices of IANA.
2014-10-16 21:22:10 +02:00
|
|
|
|
# (Europe/Volgograd)
|
|
|
|
|
SAMST Europe/Samara # Samara Summer Time (obsolete)
|
|
|
|
|
SAMT Europe/Samara # Samara Time
|
2006-07-25 05:51:23 +02:00
|
|
|
|
# (Europe/Samara)
|
Support timezone abbreviations that sometimes change.
Up to now, PG has assumed that any given timezone abbreviation (such as
"EDT") represents a constant GMT offset in the usage of any particular
region; we had a way to configure what that offset was, but not for it
to be changeable over time. But, as with most things horological, this
view of the world is too simplistic: there are numerous regions that have
at one time or another switched to a different GMT offset but kept using
the same timezone abbreviation. Almost the entire Russian Federation did
that a few years ago, and later this month they're going to do it again.
And there are similar examples all over the world.
To cope with this, invent the notion of a "dynamic timezone abbreviation",
which is one that is referenced to a particular underlying timezone
(as defined in the IANA timezone database) and means whatever it currently
means in that zone. For zones that use or have used daylight-savings time,
the standard and DST abbreviations continue to have the property that you
can specify standard or DST time and get that time offset whether or not
DST was theoretically in effect at the time. However, the abbreviations
mean what they meant at the time in question (or most recently before that
time) rather than being absolutely fixed.
The standard abbreviation-list files have been changed to use this behavior
for abbreviations that have actually varied in meaning since 1970. The
old simple-numeric definitions are kept for abbreviations that have not
changed, since they are a bit faster to resolve.
While this is clearly a new feature, it seems necessary to back-patch it
into all active branches, because otherwise use of Russian zone
abbreviations is going to become even more problematic than it already was.
This change supersedes the changes in commit 513d06ded et al to modify the
fixed meanings of the Russian abbreviations; since we've not shipped that
yet, this will avoid an undesirably incompatible (not to mention incorrect)
change in behavior for timestamps between 2011 and 2014.
This patch makes some cosmetic changes in ecpglib to keep its usage of
datetime lookup tables as similar as possible to the backend code, but
doesn't do anything about the increasingly obsolete set of timezone
abbreviation definitions that are hard-wired into ecpglib. Whatever we
do about that will likely not be appropriate material for back-patching.
Also, a potential free() of a garbage pointer after an out-of-memory
failure in ecpglib has been fixed.
This patch also fixes pre-existing bugs in DetermineTimeZoneOffset() that
caused it to produce unexpected results near a timezone transition, if
both the "before" and "after" states are marked as standard time. We'd
only ever thought about or tested transitions between standard and DST
time, but that's not what's happening when a zone simply redefines their
base GMT offset.
In passing, update the SGML documentation to refer to the Olson/zoneinfo/
zic timezone database as the "IANA" database, since it's now being
maintained under the auspices of IANA.
2014-10-16 21:22:10 +02:00
|
|
|
|
VOLT Europe/Volgograd # Volgograd Time (obsolete)
|
2006-07-25 05:51:23 +02:00
|
|
|
|
WEST 3600 D # Western Europe Summer Time
|
2009-09-06 17:25:23 +02:00
|
|
|
|
# (Africa/Casablanca)
|
2006-07-25 05:51:23 +02:00
|
|
|
|
# (Atlantic/Canary)
|
|
|
|
|
# (Atlantic/Faeroe)
|
|
|
|
|
# (Atlantic/Madeira)
|
|
|
|
|
# (Europe/Lisbon)
|
|
|
|
|
WET 0 # Western Europe Time
|
|
|
|
|
# (Africa/Casablanca)
|
|
|
|
|
# (Africa/El_Aaiun)
|
|
|
|
|
# (Atlantic/Canary)
|
|
|
|
|
# (Atlantic/Faeroe)
|
|
|
|
|
# (Atlantic/Madeira)
|
|
|
|
|
# (Europe/Lisbon)
|
|
|
|
|
WETDST 3600 D # Western Europe Summer Time
|
|
|
|
|
# (Atlantic/Canary)
|
|
|
|
|
# (Atlantic/Faeroe)
|
|
|
|
|
# (Atlantic/Madeira)
|
|
|
|
|
# (Europe/Lisbon)
|