3 ms·
Floating point timestamps - the only item which affects my work is also one of the few in this wiki page with no description. These were removed with no breakin
by qume 9y ago
Floating point timestamps - the only item which affects my work is also one of the few in this wiki page with no description. These were removed with no breaking compatibility.
For anyone else using them, I just did a bit of reading [1] and it looks like they are inferior to default 8 byte timestamps. FP timestamps have microsecond precision around the year 2000, but it drops off as it moves away from there.
I was using them to be the same as some GPS timing code, but it seems this isn't needed or desirable.
[1] https://www.postgresql.org/docs/9.0/static/datatype-datetime.html#DATATYPE-DATETIME-TABLE https://www.postgresql.org/docs/9.0/static/datatype-datetime...
- chowells 9y agoYeah.. You should never use floating point when your use case wants uniform precision across the full range. That's the opposite of what floating point gives you.