Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch
От | Peter Eisentraut |
---|---|
Тема | Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch |
Дата | |
Msg-id | ee683994-8f7c-aded-be43-543e66e68b94@2ndquadrant.com обсуждение исходный текст |
Ответы |
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch
Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost whenextracting epoch Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch |
Список | pgsql-hackers |
On 2019-12-02 23:52, Thomas Munro wrote: >> I'm not an expert in floating point math but hopefully it means that no >> type change is required - double precision can handle it. > Me neither, but the SQL standard requires us to use an exact numeric > type, so it's wrong on that level by definition. I looked into this (changing the return types of date_part()/extract() from float8 to numeric). One problem (other than perhaps performance, tbd.) is that this would no longer allow processing infinite timestamps, since numeric does not support infinity. It could be argued that running extract() on infinite timestamps isn't very useful, but it's something to consider explicitly. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: