From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Shay Rojansky <roji(at)roji(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Missing docs on AT TIME ZONE precedence? |
Date: | 2023-11-26 14:27:34 |
Message-ID: | ZWNV1pjBepdBwJK7@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Nov 26, 2023 at 11:13:39AM +0100, Shay Rojansky wrote:
> Greeting hackers,
>
> In the operator precedence table[1] table, AT TIME ZONE isn't explicitly listed
> out; that means it's to be interpreted in the "any other operator category".
>
> However, it seems that the precedence of AT TIME ZONE is actually higher than
> that of the addition operator:
>
> -- Fails with "function pg_catalog.timezone(unknown, interval) does not exist
> SELECT now() + INTERVAL '14 days' AT TIME ZONE 'UTC';
>
> -- Works:
> SELECT (now() + INTERVAL '14 days') AT TIME ZONE 'UTC';
>
> Note that missing parentheses for this were discussed in the context
> of pg_catalog.pg_get_viewdef[2].
>
> Is there a missing line in the operator precedence table in the docs?
I think the big question is whether AT TIME ZONE is significant enough
to list there because there are many other clauses we could potentially
add there.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Anton A. Melnikov | 2023-11-26 14:47:49 | Should timezone be inherited from template database? |
Previous Message | Shay Rojansky | 2023-11-26 10:13:39 | Missing docs on AT TIME ZONE precedence? |