This form sets the storage mode for a column. This controls whether this
- column is held inline or in a supplementary table, and whether the data
+ column is held inline or in a secondary
TOAST> table, and
+ whether the data
should be compressed or not. PLAIN must be used
for fixed-length values such as integer and is
inline, uncompressed. MAIN is for inline,
uncompressed data, and EXTENDED is for external,
compressed data. EXTENDED is the default for most
data types that support non-PLAIN storage.
- Use of EXTERNAL will
- make substring operations on text and bytea
- columns faster, at the penalty of increased storage space. Note that
+ Use of EXTERNAL will make substring operations on
+ very large text and bytea values run faster,
+ at the penalty of increased storage space. Note that
SET STORAGE> doesn't itself change anything in the table,
it just sets the strategy to be pursued during future table updates.
See for more information.
table is going to be used in complex queries, it is wise to run
ANALYZE> on the temporary table after it is populated.
-
+
Optionally, GLOBAL or LOCAL
can be written before TEMPORARY> or TEMP>.
for tables, and for indexes associated with a UNIQUE,
PRIMARY KEY, or EXCLUDE> constraint.
Storage parameters for
- indexes are documented in . The storage parameters currently
+ indexes are documented in .
+ The storage parameters currently
available for tables are listed below. For each parameter, unless noted,
- there is an additional, identically named parameter, prefixed with
- toast. which can be used to control the behavior of the
- supplementary storage table, if any; see .
- Note that the supplementary storage table inherits the
- autovacuum values from its parent table, if there are
+ there is an additional parameter with the same name prefixed with
+ toast., which can be used to control the behavior of the
+ table's secondary
TOAST> table, if any
+ (see for more information about TOAST).
+ Note that the TOAST table inherits the
+ autovacuum_* values from its parent table, if there are
no toast.autovacuum_* settings set.
original, which is more efficient than placing it on a different page.
For a table whose entries are never updated, complete packing is the
best choice, but in heavily updated tables smaller fillfactors are
- appropriate. This parameter cannot be set for the supplementary
- storage table.
+ appropriate. This parameter cannot be set for TOAST tables.