Re: BUG #9374: some timzone abbver is missing from pg_timezone_abbrevs that are in pg_timezone_names - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #9374: some timzone abbver is missing from pg_timezone_abbrevs that are in pg_timezone_names
Date
Msg-id 28086.1393639024@sss.pgh.pa.us
Whole thread Raw
In response to BUG #9374: some timzone abbver is missing from pg_timezone_abbrevs that are in pg_timezone_names  (mark.a.sloan@gmail.com)
Responses Re: BUG #9374: some timzone abbver is missing from pg_timezone_abbrevs that are in pg_timezone_names
List pgsql-bugs
mark.a.sloan@gmail.com writes:
> postgres=# SELECT * FROM pg_timezone_names   where abbrev = 'WIB' ;
>          name         | abbrev | utc_offset | is_dst
> ----------------------+--------+------------+--------
>  posix/Asia/Pontianak | WIB    | 07:00:00   | f
>  posix/Asia/Jakarta   | WIB    | 07:00:00   | f
>  Asia/Pontianak       | WIB    | 07:00:00   | f
>  Asia/Jakarta         | WIB    | 07:00:00   | f
> (4 rows)

> postgres=# SELECT * FROM pg_timezone_abbrevs  where abbrev = 'WIB' ;
>  abbrev | utc_offset | is_dst
> --------+------------+--------
> (0 rows)

This is not a bug.  pg_timezone_abbrevs only lists abbreviations that are
listed in the file selected by the timezone_abbreviations parameter.
The default file doesn't contain WIB.  You can if you like add it,
or maybe better make up a custom abbreviations file tuned to your
particular needs.

While we haven't got a hard and fast policy about which timezone
abbreviations to list in the default set, there are good reasons not to
list uncommonly used ones: the more abbreviations are in the file, the
greater chance of accepting typos as valid input.  And we're definitely
going to be cautious about including abbreviations that mean different
things in different parts of the world, which is an issue for several of
the "missing" ones you listed.

            regards, tom lane

pgsql-bugs by date:

Previous
From: rajkumarmca1488@gmail.com
Date:
Subject: BUG #9384: Restore Database using psql utility fails
Next
From: no-email@example.com
Date:
Subject: BUG #9398: DELETE refering to a materialized view produces "cannot lock rows in materialized view" error