Horton

Re: Inconsistency of timezones in postgresql

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Chris BSomething <xpusostomos@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Aleksander Alekseev <aleksander@timescale.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-07-31T17:42:09Z
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

On Wednesday, July 31, 2024, Chris BSomething <xpusostomos@gmail.com> wrote:

> Tom Lane said:
> "However, notice that the value following TIME ZONE is only allowed to
> be an interval by the spec (and this is still true in SQL:2021,
> the latest version I have handy).  Such an interval is interpreted per
> ISO (positive = east of Greenwich)."
>
> Erm, what do you mean by an interval? If you mean a number, then it’s
> broken, because "UTC+10" and "+10" do the same thing. But you seem to be
> saying there is indeed some syntax that is interpreted by ISO logic?
>

There is a named data type called “interval”.  He’s referring to that.
Neither of those text values is an interval.  ‘4 hours 30
minutes’::interval is a relevant example.

David J.