On Sat, Nov 30, 2019 at 10:28 PM Petr Fedorov <petr(dot)fedorov(at)phystech(dot)edu> wrote:
> Obviously, it is due to the fact that extract epoch returns double
> precision which in turn has 15 decimal digits precision.
I guess this deviation from the SQL standard ("exact numeric") made
sense when PostgreSQL used double for timestamps, but would break a
lot of queries if we changed it.