From: Tom Lane <tgl@sss.pgh.pa.us>
To: Petr Fedorov <petr.fedorov@phystech.edu>
cc: pgsql-bugs@postgresql.org
Subject: Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when
 extracting epoch
In-reply-to: <42b73d2d-da12-ba9f-570a-420e0cce19d9@phystech.edu>
References: <42b73d2d-da12-ba9f-570a-420e0cce19d9@phystech.edu>
Comments: In-reply-to Petr Fedorov <petr.fedorov@phystech.edu>
	message dated "Sat, 30 Nov 2019 12:28:18 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17990.1575127261.1@sss.pgh.pa.us>
Date: Sat, 30 Nov 2019 10:21:01 -0500
Message-ID: <17991.1575127261@sss.pgh.pa.us>
Precedence: bulk

Petr Fedorov <petr.fedorov@phystech.edu> 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