| 1 |
src/timezone/tznames/README |
| 2 |
|
| 3 |
tznames |
| 4 |
======= |
| 5 |
|
| 6 |
This directory contains files with timezone sets for PostgreSQL. The problem |
| 7 |
is that time zone abbreviations are not unique throughout the world and you |
| 8 |
might find out that a time zone abbreviation in the `Default' set collides |
| 9 |
with the one you wanted to use. This can be fixed by selecting a timezone |
| 10 |
set that defines the abbreviation the way you want it. There might already |
| 11 |
be a file here that serves your needs. If not, you can create your own. |
| 12 |
|
| 13 |
In order to use one of these files, you need to set |
| 14 |
|
| 15 |
timezone_abbreviations = 'xyz' |
| 16 |
|
| 17 |
in any of the usual ways for setting a parameter, where xyz is the filename |
| 18 |
that contains the desired time zone abbreviations. |
| 19 |
|
| 20 |
If you do not find an appropriate set of abbreviations for your geographic |
| 21 |
location supplied here, please report this to <[email protected]>. |
| 22 |
Your set of time zone abbreviations can then be included in future releases. |
| 23 |
For the time being you can always add your own set. |
| 24 |
|
| 25 |
Typically a custom abbreviation set is made by including the `Default' set |
| 26 |
and then adding or overriding abbreviations as necessary. For examples, |
| 27 |
see the `Australia' and `India' files. |
| 28 |
|
| 29 |
The files named Africa.txt, etc, are not intended to be used directly as |
| 30 |
time zone abbreviation files. They contain reference definitions of time zone |
| 31 |
abbreviations that can be copied into a custom abbreviation file as needed. |
| 32 |
These files contain most of the time zone abbreviations that were shown |
| 33 |
in the IANA timezone database circa 2010. |
| 34 |
|
| 35 |
However, it turns out that many of these abbreviations had simply been |
| 36 |
invented by the IANA timezone group, and do not have currency in real-world |
| 37 |
use. The IANA group have changed their policy about that, and now prefer to |
| 38 |
use numeric UTC offsets whenever there's not an abbreviation with known |
| 39 |
real-world popularity. A lot of these abbreviations therefore no longer |
| 40 |
appear in the IANA data, and so are marked "obsolete" in these data files. |