Re: Column information

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Igor Korot <ikorot01(at)gmail(dot)com>
Cc: Alban Hertroys <haramrae(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Column information
Date: 2017-05-04 14:06:35
Message-ID: 55e98eff-5677-30e7-63b2-03c584211dc7@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 05/04/2017 07:00 AM, Tom Lane wrote:
> Igor Korot <ikorot01(at)gmail(dot)com> writes:
>> Yes, so for the Radix 2 only 0 and 1 should be used, right?
>> And so the value should be 100000 and not 32.
>
> No, certainly not. The radix column says what the units of measurement
> are, not that the values in the precision column aren't decimal. So radix
> 2 indicates that precision 32 means "32 bits", not "32 decimal digits".

Alright now I am confused:

https://www.postgresql.org/docs/9.6/static/infoschema-columns.html

"numeric_precision cardinal_number

If data_type identifies a numeric type, this column contains the
(declared or implicit) precision of the type for this column. The
precision indicates the number of significant digits. It can be
expressed in decimal (base 10) or binary (base 2) terms, as specified in
the column numeric_precision_radix. For all other data types, this
column is null.

"
>
> regards, tom lane
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-05-04 14:29:43 Re: Column information
Previous Message Adrian Klaver 2017-05-04 14:03:53 Re: Column information