| From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | BST Time Zone Discrepancy |
| Date: | 2017-02-06 19:32:31 |
| Message-ID: | b489698f-0f92-0221-1ad7-fedd3c3ca4da@lucee.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I've been having some issues with using BST as a timezone, so I checked
the Postgres catalogs and found a discrepancy.
I expected it to be British Summer Time, which is a Daylight Saving Time
in England and has a 1-hour UTC offset.
In pg_timezone_abbrevs I see a 1-hr offset and is_dst set to true as I
expected:
intranet=> SELECT * FROM pg_timezone_abbrevs WHERE abbrev='BST';
abbrev | utc_offset | is_dst
--------+------------+--------
BST | 01:00:00 | t
(1 row)
But in pg_timezone_names I get an 11-hr offset with a completely
different time zone.
intranet=> SELECT * FROM pg_timezone_names WHERE abbrev='BST';
name | abbrev | utc_offset | is_dst
----------------------------+--------+------------+--------
Pacific/Bougainville | BST | 11:00:00 | f
posix/Pacific/Bougainville | BST | 11:00:00 | f
(2 rows)
Surely, they can not both be right, so I'm thinking that this is a bug?
Thank you,
--
Igal Sapir
Lucee Core Developer
Lucee.org <http://lucee.org/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-06 20:18:48 | Re: BST Time Zone Discrepancy |
| Previous Message | Rui Pacheco | 2017-02-06 17:21:56 | Logging broken messages |