From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Sayyid Ali Sajjad Rizavi <sasrizavi(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Allow round() function to accept float and double precision |
Date: | 2022-12-01 21:40:48 |
Message-ID: | CAKFQuwaK-nkgb6Dx5SauGvz9k++=dSXcE6MUyePeEy9+a+hk2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 1, 2022 at 2:21 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Fri, 2 Dec 2022 at 09:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >
> > David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > > I don't really agree that it will work fine in all cases though. If
> > > the numeric has more than 1000 digits left of the decimal point then
> > > the method won't work at all.
> >
> > But what we're talking about is starting from a float4 or float8
> > input, so it can't be more than ~308 digits.
>
> I may have misunderstood. I thought David J was proposing this as a
> useful method for rounding numeric too. Re-reading what he wrote, I no
> longer think he was.
>
>
I was not, my response was that what is being asked for is basically a cast
from float to numeric, and doing that via a "round()" function seems odd.
And we can handle the desired rounding aspect of that process already via
the existing numeric(1000, n) syntax.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-12-01 21:51:58 | Re: Questions regarding distinct operation implementation |
Previous Message | Nathan Bossart | 2022-12-01 21:40:26 | Re: O(n) tasks cause lengthy startups and checkpoints |