Re: BUG #15434: NUMERIC without any precision or scale truncatesscale to 16 digits - Mailing list pgsql-bugs

From Andrey
Subject Re: BUG #15434: NUMERIC without any precision or scale truncatesscale to 16 digits
Date
Msg-id CAOYf6ecjuc7twZ6xTdb1Q2VxXVmb-SYhCrxvM3C+W=VpfKtnqQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15434: NUMERIC without any precision or scale truncates scale to 16 digits  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-bugs
вт, 16 окт. 2018 г. в 14:30, Andrew Gierth <andrew@tao11.riddles.org.uk>:
>>>>> "PG" == PG Bug reporting form <noreply@postgresql.org> writes:

 PG>  1800000000000000001::numeric / (10^18)::numeric truncated, --
 PG> truncates to 16 digits after decimal point

It has to truncate it _somewhere_, because otherwise 1::numeric / 3
would be infinitely long...

The choice that numeric division actually makes is to produce a result
with at least 16 significant figures, but also with at least as many
decimal places as the display scale of either of the inputs.

--
Andrew (irc:RhodiumToad)

It looks like precision does matters.
man: "...up to the implementation limit on precision".
Why we don't want to decrease scale, but we decrease precision without any problems?

Regards,
Andrey L

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15434: NUMERIC without any precision or scale truncates scale to 16 digits
Next
From: PG Bug reporting form
Date:
Subject: BUG #15435: Infinite-recursive SQL procedure can crash a databaseserver