On Sat, Sep 24, 2016 at 7:52 AM, <pszegheo@itnnetworks.com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14337
> Logged by: Pavol Szegheo
> Email address: pszegheo@itnnetworks.com
> PostgreSQL version: 9.5.4
> Operating system: Windows 10
> Description:
>
> "HDT" time zone is not recognized by PostreSQL 9.5
>
> Neither are the more modern HADT and HAST time zones recognized by PostreSQL
> 9.5
>
> So, the only Hawaiian timezone recognized by PostreSQL 9.5 is HST, thus the
> following would run fine:
> SELECT TIMESTAMP '2013-08-13 00:00:00' AT TIME ZONE 'HST';
>
> While all these would fail:
>
> SELECT TIMESTAMP '2013-08-13 00:00:00' AT TIME ZONE 'HDT';
>
> SELECT TIMESTAMP '2013-08-13 00:00:00' AT TIME ZONE 'HADT';
>
> SELECT TIMESTAMP '2013-08-13 00:00:00' AT TIME ZONE 'HAST';
>
> e.g.:
> SELECT TIMESTAMP '2013-08-13 00:00:00' AT TIME ZONE 'HDT';
> /*
> Example output:
> ERROR: time zone "HDT" not recognized
> ********** Error **********
>
> ERROR: time zone "HDT" not recognized
> SQL state: 22023
> */
Hawaii doesn't do daylight savings.
BTW Most people would advise you to use 'Pacific/Honolulu' instead.
--
Thomas Munro
http://www.enterprisedb.com
