mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-01 12:11:23 +02:00
Mention the actual stored size of NUMERIC values, per David Fetter.
This commit is contained in:
parent
628c0893fd
commit
768eaf1416
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.156 2005/03/13 09:36:30 neilc Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.157 2005/05/01 15:54:46 tgl Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<chapter id="datatype">
|
<chapter id="datatype">
|
||||||
@ -505,7 +505,9 @@ NUMERIC
|
|||||||
trailing zeroes. Thus, the declared precision and scale of a column
|
trailing zeroes. Thus, the declared precision and scale of a column
|
||||||
are maximums, not fixed allocations. (In this sense the <type>numeric</>
|
are maximums, not fixed allocations. (In this sense the <type>numeric</>
|
||||||
type is more akin to <type>varchar(<replaceable>n</>)</type>
|
type is more akin to <type>varchar(<replaceable>n</>)</type>
|
||||||
than to <type>char(<replaceable>n</>)</type>.)
|
than to <type>char(<replaceable>n</>)</type>.) The actual storage
|
||||||
|
requirement is two bytes for each group of four decimal digits,
|
||||||
|
plus eight bytes overhead.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
Reference in New Issue
Block a user