Re: BUG #14026: Problem to convert number to real

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: carlos_penteado(at)yahoo(dot)com(dot)br
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14026: Problem to convert number to real
Date: 2016-03-17 23:25:29
Message-ID: 16337.1458257129@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

carlos_penteado(at)yahoo(dot)com(dot)br writes:
> SELECT 109048.96::float, 0.96::float
> RETURNS
> 109048.96;0.96
> but
> SELECT 109048.96::real, 0.96::real
> RETURNS
> 109049;0.96

"float" means float8, while "real" means float4. Per
http://www.postgresql.org/docs/9.5/static/datatype-numeric.html#DATATYPE-FLOAT

PostgreSQL also supports the SQL-standard notations float and float(p)
for specifying inexact numeric types. Here, p specifies the minimum
acceptable precision in binary digits. PostgreSQL accepts float(1) to
float(24) as selecting the real type, while float(25) to float(53)
select double precision. Values of p outside the allowed range draw an
error. float with no precision specified is taken to mean double
precision.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2016-03-17 23:26:44 Re: Help
Previous Message Joe Conway 2016-03-17 23:23:12 Re: BUG #14024: problem in Creating pivot table