From: | Chris BSomething <xpusostomos(at)gmail(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Inconsistency of timezones in postgresql |
Date: | 2024-07-31 13:06:20 |
Message-ID: | CADrHaBE9EykgvqWQnm0wV7eZdzXjS0G+YZNpZxqpqEXXduwQdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"The function timezone(zone, timestamp) is equivalent to the SQL-conforming
construct timestamp AT TIME ZONE zone."
https://www.postgresql.org/docs/17/functions-datetime.html#FUNCTIONS-DATETIME-ZONECONVERT
Documentation seems to think it is.
On Wed, 31 Jul 2024 at 20:52, Aleksander Alekseev <aleksander(at)timescale(dot)com>
wrote:
> Hi,
>
> > I don't think merely thinking of a new function name is good enough
> because "AT TIME ZONE" I believe is an SQL standard. Now I don't have the
> SQL standard because I don't want to shell out the crazy money they want
> for it [...]
>
> From what I can tell AT TIME ZONE syntax is not a part of the SQL
> standard. The standard describes only implicit casts between TIMESTAMP
> WITH TIMEZONE and TIMESTAMP WITHOUT TIMEZONE.
>
> --
> Best regards,
> Aleksander Alekseev
>
From | Date | Subject | |
---|---|---|---|
Next Message | Junwang Zhao | 2024-07-31 13:17:38 | Re: BUG #18560: Inconsistent Behavior of PostgreSQL 'LIKE' Operator |
Previous Message | Sandeep Thakkar | 2024-07-31 13:00:07 | Re: [EXTERNAL] Re: BUG #18528: Installer displays error when installing |