I wrote:
> Aleksander Alekseev <aleksander@timescale.com> writes:
>> 1. Should this behavior be documented in the 9.9.4. AT TIME ZONE
>> section or maybe it's documented elsewhere and I just missed it?
> https://www.postgresql.org/docs/current/datetime-invalid-input.html
... and reading that again, I realize that I screwed up the
fall-back example :-(. 2:30 is not ambiguous; I should have
demonstrated the behavior for, say, 1:30. Will fix.
regards, tom lane