Chapter 8. Data Types
Table of Contents
- 8.1. Numeric Types
- 8.2. Monetary Types
- 8.3. Character Types
- 8.4. Binary Data Types
- 8.3. Character Types
- 8.5. Date/Time Types
- 8.6. Boolean Type
- 8.7. Enumerated Types
- 8.8. Geometric Types
- 8.9. Network Address Types
- 8.10. Bit String Types
- 8.11. Text Search Types
- 8.12. UUID Type
- 8.13. XML Type
- 8.14. JSON Types
- 8.15. Arrays
- 8.16. Composite Types
- 8.17. Range Types
- 8.17.1. Built-in Range and Multirange Types
- 8.17.2. Examples
- 8.17.3. Inclusive and Exclusive Bounds
- 8.17.4. Infinite (Unbounded) Ranges
- 8.17.5. Range Input/Output
- 8.17.6. Constructing Ranges and Multiranges
- 8.17.7. Discrete Range Types
- 8.17.8. Defining New Range Types
- 8.17.9. Indexing
- 8.17.10. Constraints on Ranges
- 8.17.2. Examples
- 8.17.1. Built-in Range and Multirange Types
- 8.18. Domain Types
- 8.19. Object Identifier Types
- 8.20.
pg_lsnType- 8.21. Pseudo-Types
- 8.19. Object Identifier Types
Postgres Pro has a rich set of native data types available to users. Users can add new types to Postgres Pro using the CREATE TYPE command.
Table 8.1 shows all the built-in general-purpose data types. Most of the alternative names listed in the “Aliases” column are the names used internally by Postgres Pro for historical reasons. In addition, some internally used or deprecated types are available, but are not listed here.
Table 8.1. Data Types
| Name | Aliases | Description |
|---|---|---|
bigint | int8 | signed eight-byte integer |
bigserial | serial8 | autoincrementing eight-byte integer |
bit [ ( | fixed-length bit string | |
bit varying [ ( | varbit [ ( | variable-length bit string |
boolean | bool | logical Boolean (true/false) |
box | rectangular box on a plane | |
bytea | binary data (“byte array”) | |
character [ ( | char [ ( | fixed-length character string |
character varying [ ( | varchar [ ( | variable-length character string |
cidr | IPv4 or IPv6 network address | |
circle | circle on a plane | |
date | calendar date (year, month, day) | |
double precision | float8 | double precision floating-point number (8 bytes) |
inet | IPv4 or IPv6 host address | |
integer | int, int4 | signed four-byte integer |
interval [ | time span | |
json | textual JSON data | |
jsonb | binary JSON data, decomposed | |
line | infinite line on a plane | |
lseg | line segment on a plane | |
macaddr | MAC (Media Access Control) address | |
macaddr8 | MAC (Media Access Control) address (EUI-64 format) | |
money | currency amount | |
numeric [ ( | decimal [ ( | exact numeric of selectable precision |
path | geometric path on a plane | |
pg_lsn | Postgres Pro Log Sequence Number | |
pg_snapshot | user-level transaction ID snapshot | |
point | geometric point on a plane | |
polygon | closed geometric path on a plane | |
real | float4 | single precision floating-point number (4 bytes) |
smallint | int2 | signed two-byte integer |
smallserial | serial2 | autoincrementing two-byte integer |
serial | serial4 | autoincrementing four-byte integer |
text | variable-length character string | |
time [ ( | time of day (no time zone) | |
time [ ( | timetz | time of day, including time zone |
timestamp [ ( | date and time (no time zone) | |
timestamp [ ( | timestamptz | date and time, including time zone |
tsquery | text search query | |
tsvector | text search document | |
txid_snapshot | user-level transaction ID snapshot (deprecated; see pg_snapshot) | |
uuid | universally unique identifier | |
xml | XML data |
Compatibility
The following types (or spellings thereof) are specified by SQL: bigint, bit, bit varying, boolean, char, character varying, character, varchar, date, double precision, integer, interval, numeric, decimal, real, smallint, time (with or without time zone), timestamp (with or without time zone), xml.
Each data type has an external representation determined by its input and output functions. Many of the built-in types have obvious external formats. However, several types are either unique to Postgres Pro, such as geometric paths, or have several possible formats, such as the date and time types. Some of the input and output functions are not invertible, i.e., the result of an output function might lose accuracy when compared to the original input.