| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [BUG?] SET TIME ZONE doesn't work with abbreviations |
| Date: | 2021-09-07 13:57:41 |
| Message-ID: | CAKFQuwaC8_0aFo2XCe3-i6OP_Unio+9p_ek+54HCoSta7=zpZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday, September 7, 2021, Aleksander Alekseev <aleksander(at)timescale(dot)com>
wrote:
> Hi hackers,
>
> I noticed that `SET TIME ZONE` / `SET timezone TO` don't work with
> abbreviations:
>
> Is it a bug or this behavior is intentional (something to do with SQL
> standard, perhaps)?
>
>
Well, given that the limitation is documented I’d have to say it is
intentional:
You cannot set the configuration parameters TimeZone
<https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE>
or log_timezone
<https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-TIMEZONE>
to
a time zone abbreviation, but you can use abbreviations in date/time input
values and with the AT TIME ZONE operator.
https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-07 14:00:09 | Re: [BUG?] SET TIME ZONE doesn't work with abbreviations |
| Previous Message | Bharath Rupireddy | 2021-09-07 13:48:53 | Re: Use "superuser" instead of "super user" in code comments |