database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-29 13:56:47 +03:00
Code

Remove old documentation warnings about the use of bigint.

Browse Source
This commit is contained in:
Bruce Momjian 2012-08-30 13:13:35 -04:00
parent c8ba697a4b
commit 48a9c7823e
1 changed files with 2 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/datatype.sgml
View File

@ -453,18 +453,8 @@
The type <type>integer</type> is the common choice, as it offers The type <type>integer</type> is the common choice, as it offers
the best balance between range, storage size, and performance. the best balance between range, storage size, and performance.
The <type>smallint</type> type is generally only used if disk The <type>smallint</type> type is generally only used if disk
space is at a premium. The <type>bigint</type> type should only space is at a premium. The <type>bigint</type> type is designed to be
be used if the range of the <type>integer</type> type is insufficient, used when 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.)
</para> </para>
<para> <para>