| From: | Aravind Kumar <aravindc26(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: numeric data type upper limit. |
| Date: | 2016-08-14 14:27:23 |
| Message-ID: | CADhiBKZHoDgg6jzcoxNVtOkeu=fZrhd+edyM6Ut3tTW2x2x-Ag@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice |
On Sun, Aug 14, 2016 at 6:05 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Sunday, August 14, 2016, Aravind Kumar <aravindc26(at)gmail(dot)com> wrote:
>>
>> Hi,
>>
>> when I do
>>
>> select 1.0e+1001::numeric;
>>
>> I get
>>
>> invalid input syntax for type numeric: "1.0e+1001"
>>
>> But
>>
>> select 1.0e+1000::numeric;
>>
>> seems to be valid.
>>
>> Postgresql documentation tells me that numeric data type has an upper
>> limit of 131072 digits before decimal point.
>>
>> Am I missing something ?
>>
>
> Guessing here but I think numeric input requires single quotes around the
> value.
>
> David J.
Tried with single quotes doesn't seem to work. Possible bug ?
Aravind Chintalapalli
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Murphy | 2016-08-14 15:12:45 | Patch: initdb: "'" for QUOTE_PATH (non-windows) |
| Previous Message | David G. Johnston | 2016-08-14 12:35:07 | Re: numeric data type upper limit. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-14 17:28:41 | Re: numeric data type upper limit. |
| Previous Message | David G. Johnston | 2016-08-14 12:35:07 | Re: numeric data type upper limit. |