Re: Inconsistency of timezones in postgresql
Aleksander Alekseev <aleksander@timescale.com>
From: Aleksander Alekseev <aleksander@timescale.com>
To: pgsql-bugs@lists.postgresql.org
Cc: Chris BSomething <xpusostomos@gmail.com>
Date: 2024-07-31T12:52:28Z
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 →
-
doc: add example of sign mismatch with POSIX/ISO-8601 time zones
- 06dc1ffd2409 18.0 landed
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