Re: Inconsistency of timezones in postgresql - Mailing list pgsql-bugs

From Chris BSomething
Subject Re: Inconsistency of timezones in postgresql
Date
Msg-id CADrHaBEK_WbNV=d6i19uPyqjKzOpWRhhZup8QAN839KAsK7kqQ@mail.gmail.com
Whole thread Raw
In response to Re: Inconsistency of timezones in postgresql  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Inconsistency of timezones in postgresql
List pgsql-bugs

Well... I guess then at least we have...

AT TIME ZONE INTERVAL '8 hours'

or indeed...

AT TIME ZONE INTERVAL '+8h'

so at a bare minimum we need documentation that promotes that, and warns about UTC+-

I still think Z+- would be a few  lines of code that would be a cool fix that wouldn't hurt anyone, but anyway.

Chris


On Thu, 1 Aug 2024 at 01:42, David G. Johnston <david.g.johnston@gmail.com> wrote:
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.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Inconsistency of timezones in postgresql
Next
From: Tim Dysinger
Date:
Subject: Re: BUG #18561: postgresql16-devel rpm cannot be installed due to missing Perl-IPC-Run