Re: Inconsistent 'at time zone' conversion

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Inconsistent 'at time zone' conversion
Дата
Msg-id CAKFQuwa-VxQdeXK=KOQSTdk9QMwo6dDOoRH3Cv97mc9V-5=H9Q@mail.gmail.com
обсуждение исходный текст
Ответ на Inconsistent 'at time zone' conversion  (Umut TEKİN <umuttechin@gmail.com>)
Список pgsql-bugs
Дерево обсуждения
On Sun, Feb 19, 2023 at 4:10 PM Umut TEKİN <umuttechin@gmail.com> wrote:
I think I found a bug about time zones.

Nope, the observed behavior is documented.

1. select now();
2023-02-19 21:52:12.537849+00

2. select now()::timestamp with time zone  at time zone 'America/Denver';
2023-02-19 14:52:12.5383

3. select now()::timestamp with time zone at time zone 'UTC-7';
2023-02-20 04:52:12.538804

In America/Denver, UTC-7 is using as time zone that is why 1st and 2nd queries confirm each other, but 3rd query completely disapproves first two queries. Instead of '2023-02-19 14:52:12.538804', it shows '2023-02-20 04:52:12.538804'.

Unfortunately the actual +/- direction convention in use here is not the one you are expecting.  It is defined to be the reverse of what you've said, and so you get the observed behavior.

David J.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17795: Erroneous parsing of floating-poing components in DecodeISO8601Interval()
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Inconsistent 'at time zone' conversion