postgres.git / summary / log / commit / refs

commit    48a9c7823e032fde54cb0658fbd488809a3fdc69
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Aug 30 17:13:35 2012 +0000

    Remove old documentation warnings about the use of bigint.


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

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 7f6e661adb3..71cf59e38b9 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -453,18 +453,8 @@
      The type <type>integer</type> is the common choice, as it offers
      the best balance between range, storage size, and performance.
      The <type>smallint</type> type is generally only used if disk
-     space is at a premium.  The <type>bigint</type> type should only
-     be used if the range of the <type>integer</type> type is insufficient,
-     because the latter is definitely faster.
-    </para>
-
-    <para>
-     On very minimal operating systems the <type>bigint</type> type
-     might not function correctly, because it relies on compiler support
-     for eight-byte integers.  On such machines, <type>bigint</type>
-     acts the same as <type>integer</type>, but still takes up eight
-     bytes of storage.  (We are not aware of any modern
-     platform where this is the case.)
+     space is at a premium.  The <type>bigint</type> type is designed to be
+     used when the range of the <type>integer</type> type is insufficient.
     </para>
 
     <para>


[parent: c8ba697a4bdb]