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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: David Steele <david(at)pgmasters(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Petr Fedorov <petr(dot)fedorov(at)phystech(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch
Date: 2021-04-06 05:48:21
Message-ID: 7594008a-5f47-ae29-3122-42d13228fd9e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 01.04.21 20:49, Peter Eisentraut wrote:
> also done
>
> I also figured out a way to combine the float8 and numeric
> implementations so that there is not so much duplication.  Added tests
> to cover all the edge and overflow cases.
>
> I think this is solid now.
>
> The extract(julian from timestamp) is still a bit in the slow mode, but
> as I previously stated, it's not documented and gives the wrong result,
> so it's not clear whether it should be fixed and what it should do.  I
> think I'll register that part as an open item in any case, to see what
> we should do about that.

committed and done

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message chenyanfei 2021-04-06 09:30:05 Do we need to add parameter to libpq to set the TCP_SYNCNT parameter
Previous Message Tom Lane 2021-04-04 00:45:36 Re: BUG #16952: PG admin errors out when connecting via ssh because it can't get pg_settings

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-04-06 05:52:47 Re: Replication slot stats misgivings
Previous Message Rohit Bhogate 2021-04-06 05:39:13 Reference Leak with type