Horton

Re: Inconsistency of timezones in postgresql

Chris BSomething <xpusostomos@gmail.com>

View thread
From: Chris BSomething <xpusostomos@gmail.com>
To: Aleksander Alekseev <aleksander@timescale.com>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2024-07-31T13:06:20Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. doc: add example of sign mismatch with POSIX/ISO-8601 time zones

"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@timescale.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
>