Re: now() vs 'epoch'::timestamp

Поиск
Список
Период
Сортировка
От James Cloos
Тема Re: now() vs 'epoch'::timestamp
Дата
Msg-id m38ueae8zc.fsf@carbon.jhcloos.org
обсуждение исходный текст
Ответ на Re: now() vs 'epoch'::timestamp  (Steve Crawford <scrawford@pinpointresearch.com>)
Ответы Re: now() vs 'epoch'::timestamp  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-general
>>>>> "SC" == Steve Crawford <scrawford@pinpointresearch.com> writes:

SC> Very convoluted calculation as others have noted. As to why it is
SC> "off", you are casting one part of the statement to an integer thus
SC> truncating the microseconds but are not doing the same on the other
SC> side of the calculation.

It wasn't the microsecond difference I asked about, it was the 6 hour difference.

The original, ancient code I used needed to return integer seconds.  And
it always gave answers consistant with date +%s.

What I haven't determined is why converting back is off by 21600 seconds.

-JimC
--
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6

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

Предыдущее
От: Taylor Brown
Дата:
Сообщение: Re: Why doesn't `RAISE EXCEPTION` provide error context?
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: now() vs 'epoch'::timestamp