Table 5-4. Character Types
| Type name |
Description |
| character(n),
char(n) |
fixed-length, blank padded |
| character varying(n), varchar(n) |
variable-length with limit |
| text |
variable unlimited length |
Table
5-4 shows the general-purpose character types available in PostgreSQL.
SQL defines two primary character types: character(n) and character varying(n), where n is a
positive integer. Both of these types can store strings up to n
characters in length. An attempt to store a longer string into a column of these types will
result in an error, unless the excess characters are all spaces, in which case the string will
be truncated to the maximum length. (This somewhat bizarre exception is required by the SQL standard.) If the string to be stored is shorter than the declared
length, values of type character will be space-padded; values of type character varying will simply store the shorter string.
Note: If one explicitly casts a value to character(n) or character varying(n), then an overlength value will be truncated to n characters without raising an error. (This too is
required by the SQL standard.)
Note: Prior to PostgreSQL 7.2, strings that
were too long were always truncated without raising an error, in either explicit or
implicit casting contexts.
The notations char(n) and varchar(n) are aliases for character(n) and character
varying(n), respectively. character
without length specifier is equivalent to character(1); if character varying is used without length specifier, the type accepts strings
of any size. The latter is a PostgreSQL extension.
In addition, PostgreSQL supports the more general text type, which stores strings of any length. Unlike character
varying, text does not require an explicit declared upper limit on
the size of the string. Although the type text is not in the SQL standard, many other RDBMS packages have it as well.
The storage requirement for data of these types is 4 bytes plus the actual string, and in
case of character plus the padding. Long strings are compressed by the
system automatically, so the physical requirement on disk may be less. Long values are also
stored in background tables so they don't interfere with rapid access to the shorter column
values. In any case, the longest possible character string that can be stored is about 1 GB.
(The maximum value that will be allowed for n in the data
type declaration is less than that. It wouldn't be very useful to change this because with
multibyte character encodings the number of characters and bytes can be quite different
anyway. If you desire to store long strings with no specific upper limit, use text
or character varying without a length specifier, rather than making up
an arbitrary length limit.)
Tip: There are no performance differences between these three types, apart from
the increased storage size when using the blank-padded type.
Refer to Section
1.1.2.1 for information about the syntax of string literals, and to Chapter 6 for information
about available operators and functions.
Example 5-1. Using the character types
CREATE TABLE test1 (a character(4));
INSERT INTO test1 VALUES ('ok');
SELECT a, char_length(a) FROM test1; -- (1)
a | char_length
------+-------------
ok | 4
CREATE TABLE test2 (b varchar(5));
INSERT INTO test2 VALUES ('ok');
INSERT INTO test2 VALUES ('good ');
INSERT INTO test2 VALUES ('too long');
ERROR: value too long for type character varying(5)
INSERT INTO test2 VALUES ('too long'::varchar(5)); -- explicit truncation
SELECT b, char_length(b) FROM test2;
b | char_length
-------+-------------
ok | 2
good | 5
too l | 5
There are two other fixed-length character types in PostgreSQL,
shown in Table
5-5. The name type exists only
for storage of internal catalog names and is not intended for use by the general user. Its
length is currently defined as 64 bytes (63 usable characters plus terminator) but should be
referenced using the constant NAMEDATALEN. The length is set at
compile time (and is therefore adjustable for special uses); the default maximum length may
change in a future release. The type "char" (note the quotes)
is different from char(1) in that it only uses one byte of storage. It
is internally used in the system catalogs as a poor-man's enumeration type.
Table 5-5. Specialty Character Types
| Type Name |
Storage |
Description |
| "char" |
1 byte |
single character internal type |
| name |
64 bytes |
sixty-three character internal type |
|