|
453 | 453 | The type <type>integer</type> is the common choice, as it offers
|
454 | 454 | the best balance between range, storage size, and performance.
|
455 | 455 | 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. |
468 | 458 | </para>
|
469 | 459 |
|
470 | 460 | <para>
|
|