Mention the actual stored size of NUMERIC values, per David Fetter.

[postgresql] / doc / src / sgml / datatype.sgml

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 5ca2ab2f61bbad47d225dd92b016f8a27704daf5..06183ec9e76802696bbc98bc156ad19ddc01799a 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -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">
@@ -505,7 +505,9 @@ NUMERIC
      trailing zeroes.  Thus, the declared precision and scale of a column
      are maximums, not fixed allocations.  (In this sense the <type>numeric</>
      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>