| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)heterodb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FP16 Support? |
| Date: | 2017-11-14 01:33:30 |
| Message-ID: | CAEepm=1+QX7MSzr_6w35zFNbNkqhz5y49yRhJ_1mV2sX1jCwtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 14, 2017 at 1:11 PM, Kohei KaiGai <kaigai(at)heterodb(dot)com> wrote:
> Any opinions?
The only reason I can think of for having it in core is that you might
want to use standard SQL notation FLOAT(10) to refer to it. Right now
our parser converts that to float4 but it could map precisions up to
10 to float2. The need for such special treatment is one of my
arguments for considering SQL:2016 DECFLOAT(n) in core PostgreSQL.
But this case is different: FLOAT(10) already works, it just maps to a
type with a larger significand, as permitted by the standard. So why
not just do these short floats as an extension type?
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-11-14 01:48:52 | Re: [HACKERS] ginInsertCleanup called from vacuum could still miss tuples to be deleted |
| Previous Message | Andres Freund | 2017-11-14 01:32:30 | Re: FP16 Support? |