Re: Ryu floating point output patch - Mailing list pgsql-hackers

From Donald Dong
Subject Re: Ryu floating point output patch
Date
Msg-id 9CA1C652-0629-469C-8E97-602DE9D33D19@csumb.edu
Whole thread Raw
In response to Re: Ryu floating point output patch  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Ryu floating point output patch  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
> On Jan 18, 2019, at 2:05 AM, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
>
> BTW, doing that in a thread about a commitfest patch confuses the
> commitfest app and cfbot (both of which think it's a new version of the
> patch under discussion), so best avoided.

Oops. Thank you. Noted.

I think the previous additional digits behavior still exist
in the latest patch. For example:

=# set extra_float_digits = 0;
SET
=# select float4in('1.123456789');
 float4in
----------
  1.12346
(1 row)

=# set extra_float_digits = 1;
SET
=# select float4in('1.123456789');
 float4in
-----------
 1.1234568
(1 row)

The extra_float_digits is increased by 1, but two digits are
added. Without the patch, it will render ' 1.123457' instead.

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables
Next
From: Tom Lane
Date:
Subject: Re: Thread-unsafe coding in ecpg