Re: Underscores in numeric literals - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: Underscores in numeric literals
Date
Msg-id CAEZATCWXrmkX+WzZ02AGDOk++zxD6RKoC0u_4uLSt+8OXDSCRg@mail.gmail.com
Whole thread Raw
In response to Re: Underscores in numeric literals  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Thu, 2 Feb 2023 at 22:40, Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 31.01.23 17:09, Dean Rasheed wrote:
> > On Tue, 31 Jan 2023 at 15:28, Peter Eisentraut
> > <peter.eisentraut@enterprisedb.com> wrote:
> >>
> >> Did you have any thoughts about what to do with the float types?  I
> >> guess we could handle those in a separate patch?
> >>
> >
> > I was assuming that we'd do nothing for float types, because anything
> > we did would necessarily impact their performance.
>
> Yeah, as long as we are using strtof() and strtod() we should just leave
> it alone.  If we have break that open and hand-code something, we can
> reconsider it.
>
> So I think you could go ahead with committing your patch and we can
> consider this topic done for now.
>

Done.

Regards,
Dean



pgsql-hackers by date:

Previous
From: "jacktby@gmail.com"
Date:
Subject: How to implement read operations for my own access method?
Next
From: Andres Freund
Date:
Subject: Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE