Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit48a9c78

Browse files
committed
Remove old documentation warnings about the use of bigint.
1 parentc8ba697 commit48a9c78

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

‎doc/src/sgml/datatype.sgml

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -453,18 +453,8 @@
453453
The type <type>integer</type> is the common choice, as it offers
454454
the best balance between range, storage size, and performance.
455455
The <type>smallint</type> type is generally only used if disk
456-
space is at a premium. The <type>bigint</type> type should only
457-
be used if the range of the <type>integer</type> type is insufficient,
458-
because the latter is definitely faster.
459-
</para>
460-
461-
<para>
462-
On very minimal operating systems the <type>bigint</type> type
463-
might not function correctly, because it relies on compiler support
464-
for eight-byte integers. On such machines, <type>bigint</type>
465-
acts the same as <type>integer</type>, but still takes up eight
466-
bytes of storage. (We are not aware of any modern
467-
platform where this is the case.)
456+
space is at a premium. The <type>bigint</type> type is designed to be
457+
used when the range of the <type>integer</type> type is insufficient.
468458
</para>
469459

470460
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp