| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13636: psql numericlocale adds comma where it ought not |
| Date: | 2015-09-24 23:46:42 |
| Message-ID: | CAEepm=1nTC__rwR78OE5NRW_AK4XYU6RsQxwxRv7m16=C5mUsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 25, 2015 at 11:37 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> jeff(dot)janes(at)gmail(dot)com writes:
>> \pset numericlocale on
>> select 1000000::real;
>> float4
>> --------
>> 1e,+06
>> (1 row)
>
>> There should not be a comma added between e and +.
>
> Indeed. It looks like the author of format_numeric_locale() never
> heard of e-format output. There's some other pretty crummy code in
> there, but that's the core problem ...
Does this look reasonable?
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| numeric-locale-scientific.patch | application/octet-stream | 5.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | aaron | 2015-09-25 02:06:58 | BUG #13637: ~2 GB psql import fails with out of memory error on machine with 64 GB RAM |
| Previous Message | Tom Lane | 2015-09-24 23:37:20 | Re: BUG #13636: psql numericlocale adds comma where it ought not |