Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch
Дата
Msg-id
17991.1575127261@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch Petr Fedorov <petr.fedorov@phystech.edu>
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch Tom Lane <tgl@sss.pgh.pa.us>
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch Thomas Munro <thomas.munro@gmail.com>
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch Tom Lane <tgl@sss.pgh.pa.us>
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch Petr Fedorov <petr.fedorov@phystech.edu>
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch Thomas Munro <thomas.munro@gmail.com>
Petr Fedorov  writes:
> select extract(epoch from '2001-09-09 01:46:40.000021'::timestamp)
> returns 1000000000.00002 - 1 microsecond is truncated.
> Obviously, it is due to the fact that extract epoch returns double
> precision which in turn has 15 decimal digits precision.

I can't get very excited about this.  However, it might be worth
noting that v12 and HEAD print "1000000000.000021" as expected,
thanks to the Ryu float output code.  You can get that from older
branches as well if you set extra_float_digits = 1.

By my arithmetic, IEEE float8 ought to be able to represent
microseconds accurately out to about 285 years either way from the
1970 epoch, so for practical purposes it'll be fine for a long time.

			regards, tom lane


В списке pgsql-bugs по дате отправления
От: Tomas Vondra
Дата:
От: Tom Lane
Дата:
FAQ