From 768eaf14163fb89d4c2b395cbf4a5eb016d0c0b3 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 1 May 2005 15:54:46 +0000
Subject: [PATCH] Mention the actual stored size of NUMERIC values, per David
 Fetter.

---
 doc/src/sgml/datatype.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 5ca2ab2f61..06183ec9e7 100644
--- 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>