Changing the DST setting for an invalid date-time is a bad move.
If you do not know the date-time (because it is not valid), then you
do not know whether it is the date at which the change should occur.
The date of the change is different in different timezones, and if the
date-time is incorrect,
I think it is less commonly used by new users. In my experience, the
INNER JOIN syntax is preferred by more experiences users.
On Sun, 7 Mar 2021 at 10:44, PG Doc comments form
wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs
I think there needs to be a careful analysis of the language and a formal
effort to stabilise it for the future.
In the context of, say, an Oracle T series, which is partitioned into
multiple domains (virtual machines) in it, each
of these has multiple CPUs, and can run an instance of the OS which
