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

From Robert Haas
Subject Re: Ryu floating point output patch
Date
Msg-id CA+Tgmoap3=8htn7y+6xLwHdWHxUWugBeC-qYjDMJMeg7cU2B9g@mail.gmail.com
Whole thread Raw
In response to Re: Ryu floating point output patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Ryu floating point output patch  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
On Thu, Jan 10, 2019 at 11:10 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2019-01-10 23:02:01 -0500, Chapman Flack wrote:
> >> Does the project have an established view on non-ASCII names in
> >> sources or docs?
> >> AFAICS [1], the name of the algorithm may be Ryū.
>
> > I think it'd be a really bad idea to start having non-ascii
> > filenames, and I quite doubt that I'm alone in that.
>
> Non-ASCII filenames seem right out.  I thought the question was
> about whether we even want to have non-ASCII characters within
> source code (my view: avoid if possible) or in docs (we do,
> but it's better if you can make it into html entities).

+1 to all that.

I don't have an opinion on the code that is part of this patch, but
the benchmark results are impressive.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remove all "INTERFACE ROUTINES" style comments
Next
From: Peter Eisentraut
Date:
Subject: Re: Unified logging system for command-line programs