Na}{

Path: ~//opt/alt/postgresql11/usr/share/doc/alt-postgresql11-9.2.24/html/

File Content: sql-createtable.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>CREATE TABLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.2.24 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="SQL Commands"
HREF="sql-commands.html"><LINK
REL="PREVIOUS"
TITLE="CREATE SERVER"
HREF="sql-createserver.html"><LINK
REL="NEXT"
TITLE="CREATE TABLE AS"
HREF="sql-createtableas.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2017-11-06T22:43:11"></HEAD
><BODY
CLASS="REFENTRY"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.2.24 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="CREATE SERVER"
HREF="sql-createserver.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="CREATE TABLE AS"
HREF="sql-createtableas.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SQL-CREATETABLE"
></A
>CREATE TABLE</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN70513"
></A
><H2
>Name</H2
>CREATE TABLE&nbsp;--&nbsp;define a new table</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN70518"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
>CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <TT
CLASS="REPLACEABLE"
>table_name</TT
> ( [
 { <TT
CLASS="REPLACEABLE"
>column_name</TT
> <TT
CLASS="REPLACEABLE"
>data_type</TT
> [ COLLATE <TT
CLASS="REPLACEABLE"
>collation</TT
> ] [ <TT
CLASS="REPLACEABLE"
>column_constraint</TT
> [ ... ] ]
 | <TT
CLASS="REPLACEABLE"
>table_constraint</TT
>
 | LIKE <TT
CLASS="REPLACEABLE"
>source_table</TT
> [ <TT
CLASS="REPLACEABLE"
>like_option</TT
> ... ] }
 [, ... ]
] )
[ INHERITS ( <TT
CLASS="REPLACEABLE"
>parent_table</TT
> [, ... ] ) ]
[ WITH ( <TT
CLASS="REPLACEABLE"
>storage_parameter</TT
> [= <TT
CLASS="REPLACEABLE"
>value</TT
>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
[ TABLESPACE <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
> ]

CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <TT
CLASS="REPLACEABLE"
>table_name</TT
>
 OF <TT
CLASS="REPLACEABLE"
>type_name</TT
> [ (
 { <TT
CLASS="REPLACEABLE"
>column_name</TT
> WITH OPTIONS [ <TT
CLASS="REPLACEABLE"
>column_constraint</TT
> [ ... ] ]
 | <TT
CLASS="REPLACEABLE"
>table_constraint</TT
> }
 [, ... ]
) ]
[ WITH ( <TT
CLASS="REPLACEABLE"
>storage_parameter</TT
> [= <TT
CLASS="REPLACEABLE"
>value</TT
>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ]
[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
[ TABLESPACE <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
> ]

where <TT
CLASS="REPLACEABLE"
>column_constraint</TT
> is:

[ CONSTRAINT <TT
CLASS="REPLACEABLE"
>constraint_name</TT
> ]
{ NOT NULL |
 NULL |
 CHECK ( <TT
CLASS="REPLACEABLE"
>expression</TT
> ) [ NO INHERIT ] |
 DEFAULT <TT
CLASS="REPLACEABLE"
>default_expr</TT
> |
 UNIQUE <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> |
 PRIMARY KEY <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> |
 REFERENCES <TT
CLASS="REPLACEABLE"
>reftable</TT
> [ ( <TT
CLASS="REPLACEABLE"
>refcolumn</TT
> ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
 [ ON DELETE <TT
CLASS="REPLACEABLE"
>action</TT
> ] [ ON UPDATE <TT
CLASS="REPLACEABLE"
>action</TT
> ] }
[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]

and <TT
CLASS="REPLACEABLE"
>table_constraint</TT
> is:

[ CONSTRAINT <TT
CLASS="REPLACEABLE"
>constraint_name</TT
> ]
{ CHECK ( <TT
CLASS="REPLACEABLE"
>expression</TT
> ) [ NO INHERIT ] |
 UNIQUE ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] ) <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> |
 PRIMARY KEY ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] ) <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> |
 EXCLUDE [ USING <TT
CLASS="REPLACEABLE"
>index_method</TT
> ] ( <TT
CLASS="REPLACEABLE"
>exclude_element</TT
> WITH <TT
CLASS="REPLACEABLE"
>operator</TT
> [, ... ] ) <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> [ WHERE ( <TT
CLASS="REPLACEABLE"
>predicate</TT
> ) ] |
 FOREIGN KEY ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] ) REFERENCES <TT
CLASS="REPLACEABLE"
>reftable</TT
> [ ( <TT
CLASS="REPLACEABLE"
>refcolumn</TT
> [, ... ] ) ]
 [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE <TT
CLASS="REPLACEABLE"
>action</TT
> ] [ ON UPDATE <TT
CLASS="REPLACEABLE"
>action</TT
> ] }
[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]

and <TT
CLASS="REPLACEABLE"
>like_option</TT
> is:

{ INCLUDING | EXCLUDING } { DEFAULTS | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | ALL }

<TT
CLASS="REPLACEABLE"
>index_parameters</TT
> in <TT
CLASS="LITERAL"
>UNIQUE</TT
>, <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
>, and <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraints are:

[ WITH ( <TT
CLASS="REPLACEABLE"
>storage_parameter</TT
> [= <TT
CLASS="REPLACEABLE"
>value</TT
>] [, ... ] ) ]
[ USING INDEX TABLESPACE <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
> ]

<TT
CLASS="REPLACEABLE"
>exclude_element</TT
> in an <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraint is:

{ <TT
CLASS="REPLACEABLE"
>column_name</TT
> | ( <TT
CLASS="REPLACEABLE"
>expression</TT
> ) } [ <TT
CLASS="REPLACEABLE"
>opclass</TT
> ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ]</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATETABLE-DESCRIPTION"
></A
><H2
>Description</H2
> <TT
CLASS="COMMAND"
>CREATE TABLE</TT
> will create a new, initially empty table
 in the current database. The table will be owned by the user issuing the
 command.
 If a schema name is given (for example, <TT
CLASS="LITERAL"
>CREATE TABLE
 myschema.mytable ...</TT
>) then the table is created in the specified
 schema. Otherwise it is created in the current schema. Temporary
 tables exist in a special schema, so a schema name cannot be given
 when creating a temporary table. The name of the table must be
 distinct from the name of any other table, sequence, index, view,
 or foreign table in the same schema.
 <TT
CLASS="COMMAND"
>CREATE TABLE</TT
> also automatically creates a data
 type that represents the composite type corresponding
 to one row of the table. Therefore, tables cannot have the same
 name as any existing data type in the same schema.
 The optional constraint clauses specify constraints (tests) that
 new or updated rows must satisfy for an insert or update operation
 to succeed. A constraint is an SQL object that helps define the
 set of valid values in the table in various ways.
 There are two ways to define constraints: table constraints and
 column constraints. A column constraint is defined as part of a
 column definition. A table constraint definition is not tied to a
 particular column, and it can encompass more than one column.
 Every column constraint can also be written as a table constraint;
 a column constraint is only a notational convenience for use when the
 constraint only affects one column.
 To be able to create a table, you must have <TT
CLASS="LITERAL"
>USAGE</TT
>
 privilege on all column types or the type in the <TT
CLASS="LITERAL"
>OF</TT
>
 clause, respectively.
 </DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN70598"
></A
><H2
>Parameters</H2
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>TEMPORARY</TT
> or <TT
CLASS="LITERAL"
>TEMP</TT
></DT
><DD
> If specified, the table is created as a temporary table.
 Temporary tables are automatically dropped at the end of a
 session, or optionally at the end of the current transaction
 (see <TT
CLASS="LITERAL"
>ON COMMIT</TT
> below). Existing permanent
 tables with the same name are not visible to the current session
 while the temporary table exists, unless they are referenced
 with schema-qualified names. Any indexes created on a temporary
 table are automatically temporary as well.
 The <A
HREF="routine-vacuuming.html#AUTOVACUUM"
>autovacuum daemon</A
> cannot
 access and therefore cannot vacuum or analyze temporary tables.
 For this reason, appropriate vacuum and analyze operations should be
 performed via session SQL commands. For example, if a temporary
 table is going to be used in complex queries, it is wise to run
 <TT
CLASS="COMMAND"
>ANALYZE</TT
> on the temporary table after it is populated.
 Optionally, <TT
CLASS="LITERAL"
>GLOBAL</TT
> or <TT
CLASS="LITERAL"
>LOCAL</TT
>
 can be written before <TT
CLASS="LITERAL"
>TEMPORARY</TT
> or <TT
CLASS="LITERAL"
>TEMP</TT
>.
 This presently makes no difference in PostgreSQL
 and is deprecated; see
 <A
HREF="sql-createtable.html#SQL-CREATETABLE-COMPATIBILITY"
>Compatibility</A
>.
 </DD
><DT
><TT
CLASS="LITERAL"
>UNLOGGED</TT
></DT
><DD
> If specified, the table is created as an unlogged table. Data written
 to unlogged tables is not written to the write-ahead log (see <A
HREF="wal.html"
>Chapter 29</A
>), which makes them considerably faster than ordinary
 tables. However, they are not crash-safe: an unlogged table is
 automatically truncated after a crash or unclean shutdown. The contents
 of an unlogged table are also not replicated to standby servers.
 Any indexes created on an unlogged table are automatically unlogged as
 well; however, unlogged <A
HREF="gist.html"
>GiST indexes</A
> are
 currently not supported and cannot be created on an unlogged table.
 </DD
><DT
><TT
CLASS="LITERAL"
>IF NOT EXISTS</TT
></DT
><DD
> Do not throw an error if a relation with the same name already exists.
 A notice is issued in this case. Note that there is no guarantee that
 the existing relation is anything like the one that would have been
 created.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>table_name</TT
></DT
><DD
> The name (optionally schema-qualified) of the table to be created.
 </DD
><DT
><TT
CLASS="LITERAL"
>OF <TT
CLASS="REPLACEABLE"
>type_name</TT
></TT
></DT
><DD
> Creates a typed table, which takes its
 structure from the specified composite type (name optionally
 schema-qualified). A typed table is tied to its type; for
 example the table will be dropped if the type is dropped
 (with <TT
CLASS="LITERAL"
>DROP TYPE ... CASCADE</TT
>).
 When a typed table is created, then the data types of the
 columns are determined by the underlying composite type and are
 not specified by the <TT
CLASS="LITERAL"
>CREATE TABLE</TT
> command.
 But the <TT
CLASS="LITERAL"
>CREATE TABLE</TT
> command can add defaults
 and constraints to the table and can specify storage parameters.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>column_name</TT
></DT
><DD
> The name of a column to be created in the new table.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>data_type</TT
></DT
><DD
> The data type of the column. This can include array
 specifiers. For more information on the data types supported by
 PostgreSQL, refer to <A
HREF="datatype.html"
>Chapter 8</A
>.
 </DD
><DT
><TT
CLASS="LITERAL"
>COLLATE <TT
CLASS="REPLACEABLE"
>collation</TT
></TT
></DT
><DD
> The <TT
CLASS="LITERAL"
>COLLATE</TT
> clause assigns a collation to
 the column (which must be of a collatable data type).
 If not specified, the column data type's default collation is used.
 </DD
><DT
><TT
CLASS="LITERAL"
>INHERITS ( <TT
CLASS="REPLACEABLE"
>parent_table</TT
> [, ... ] )</TT
></DT
><DD
> The optional <TT
CLASS="LITERAL"
>INHERITS</TT
> clause specifies a list of
 tables from which the new table automatically inherits all
 columns.
 Use of <TT
CLASS="LITERAL"
>INHERITS</TT
> creates a persistent relationship
 between the new child table and its parent table(s). Schema
 modifications to the parent(s) normally propagate to children
 as well, and by default the data of the child table is included in
 scans of the parent(s).
 If the same column name exists in more than one parent
 table, an error is reported unless the data types of the columns
 match in each of the parent tables. If there is no conflict,
 then the duplicate columns are merged to form a single column in
 the new table. If the column name list of the new table
 contains a column name that is also inherited, the data type must
 likewise match the inherited column(s), and the column
 definitions are merged into one. If the
 new table explicitly specifies a default value for the column,
 this default overrides any defaults from inherited declarations
 of the column. Otherwise, any parents that specify default
 values for the column must all specify the same default, or an
 error will be reported.
 <TT
CLASS="LITERAL"
>CHECK</TT
> constraints are merged in essentially the same way as
 columns: if multiple parent tables and/or the new table definition
 contain identically-named <TT
CLASS="LITERAL"
>CHECK</TT
> constraints, these
 constraints must all have the same check expression, or an error will be
 reported. Constraints having the same name and expression will
 be merged into one copy. A constraint marked <TT
CLASS="LITERAL"
>NO INHERIT</TT
> in a
 parent will not be considered. Notice that an unnamed <TT
CLASS="LITERAL"
>CHECK</TT
>
 constraint in the new table will never be merged, since a unique name
 will always be chosen for it.
 Column <TT
CLASS="LITERAL"
>STORAGE</TT
> settings are also copied from parent tables.
 </DD
><DT
><TT
CLASS="LITERAL"
>LIKE <TT
CLASS="REPLACEABLE"
>source_table</TT
> [ <TT
CLASS="REPLACEABLE"
>like_option</TT
> ... ]</TT
></DT
><DD
> The <TT
CLASS="LITERAL"
>LIKE</TT
> clause specifies a table from which
 the new table automatically copies all column names, their data types,
 and their not-null constraints.
 Unlike <TT
CLASS="LITERAL"
>INHERITS</TT
>, the new table and original table
 are completely decoupled after creation is complete. Changes to the
 original table will not be applied to the new table, and it is not
 possible to include data of the new table in scans of the original
 table.
 Default expressions for the copied column definitions will be copied
 only if <TT
CLASS="LITERAL"
>INCLUDING DEFAULTS</TT
> is specified. The
 default behavior is to exclude default expressions, resulting in the
 copied columns in the new table having null defaults.
 Note that copying defaults that call database-modification functions,
 such as <CODE
CLASS="FUNCTION"
>nextval</CODE
>, may create a functional linkage between
 the original and new tables.
 Not-null constraints are always copied to the new table.
 <TT
CLASS="LITERAL"
>CHECK</TT
> constraints will be copied only if
 <TT
CLASS="LITERAL"
>INCLUDING CONSTRAINTS</TT
> is specified.
 No distinction is made between column constraints and table
 constraints.
 Indexes, <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
>, <TT
CLASS="LITERAL"
>UNIQUE</TT
>,
 and <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraints on the original table will be
 created on the new table only if <TT
CLASS="LITERAL"
>INCLUDING INDEXES</TT
>
 is specified. Names for the new indexes and constraints are
 chosen according to the default rules, regardless of how the originals
 were named. (This behavior avoids possible duplicate-name failures for
 the new indexes.)
 <TT
CLASS="LITERAL"
>STORAGE</TT
> settings for the copied column definitions will be
 copied only if <TT
CLASS="LITERAL"
>INCLUDING STORAGE</TT
> is specified. The
 default behavior is to exclude <TT
CLASS="LITERAL"
>STORAGE</TT
> settings, resulting
 in the copied columns in the new table having type-specific default
 settings. For more on <TT
CLASS="LITERAL"
>STORAGE</TT
> settings, see
 <A
HREF="storage-toast.html"
>Section 56.2</A
>.
 Comments for the copied columns, constraints, and indexes
 will be copied only if <TT
CLASS="LITERAL"
>INCLUDING COMMENTS</TT
>
 is specified. The default behavior is to exclude comments, resulting in
 the copied columns and constraints in the new table having no comments.
 <TT
CLASS="LITERAL"
>INCLUDING ALL</TT
> is an abbreviated form of
 <TT
CLASS="LITERAL"
>INCLUDING DEFAULTS INCLUDING CONSTRAINTS INCLUDING INDEXES INCLUDING STORAGE INCLUDING COMMENTS</TT
>.
 Note that unlike <TT
CLASS="LITERAL"
>INHERITS</TT
>, columns and
 constraints copied by <TT
CLASS="LITERAL"
>LIKE</TT
> are not merged with similarly
 named columns and constraints.
 If the same name is specified explicitly or in another
 <TT
CLASS="LITERAL"
>LIKE</TT
> clause, an error is signaled.
 The <TT
CLASS="LITERAL"
>LIKE</TT
> clause can also be used to copy column
 definitions from views, foreign tables, or composite types.
 Inapplicable options (e.g., <TT
CLASS="LITERAL"
>INCLUDING INDEXES</TT
> from
 a view) are ignored.
 </DD
><DT
><TT
CLASS="LITERAL"
>CONSTRAINT <TT
CLASS="REPLACEABLE"
>constraint_name</TT
></TT
></DT
><DD
> An optional name for a column or table constraint. If the
 constraint is violated, the constraint name is present in error messages,
 so constraint names like <TT
CLASS="LITERAL"
>col must be positive</TT
> can be used
 to communicate helpful constraint information to client applications.
 (Double-quotes are needed to specify constraint names that contain spaces.)
 If a constraint name is not specified, the system generates a name.
 </DD
><DT
><TT
CLASS="LITERAL"
>NOT NULL</TT
></DT
><DD
> The column is not allowed to contain null values.
 </DD
><DT
><TT
CLASS="LITERAL"
>NULL</TT
></DT
><DD
> The column is allowed to contain null values. This is the default.
 This clause is only provided for compatibility with
 non-standard SQL databases. Its use is discouraged in new
 applications.
 </DD
><DT
><TT
CLASS="LITERAL"
>CHECK ( <TT
CLASS="REPLACEABLE"
>expression</TT
> ) [ NO INHERIT ] </TT
></DT
><DD
> The <TT
CLASS="LITERAL"
>CHECK</TT
> clause specifies an expression producing a
 Boolean result which new or updated rows must satisfy for an
 insert or update operation to succeed. Expressions evaluating
 to TRUE or UNKNOWN succeed. Should any row of an insert or
 update operation produce a FALSE result an error exception is
 raised and the insert or update does not alter the database. A
 check constraint specified as a column constraint should
 reference that column's value only, while an expression
 appearing in a table constraint can reference multiple columns.
 Currently, <TT
CLASS="LITERAL"
>CHECK</TT
> expressions cannot contain
 subqueries nor refer to variables other than columns of the
 current row.
 A constraint marked with <TT
CLASS="LITERAL"
>NO INHERIT</TT
> will not propagate to
 child tables.
 </DD
><DT
><TT
CLASS="LITERAL"
>DEFAULT
 <TT
CLASS="REPLACEABLE"
>default_expr</TT
></TT
></DT
><DD
> The <TT
CLASS="LITERAL"
>DEFAULT</TT
> clause assigns a default data value for
 the column whose column definition it appears within. The value
 is any variable-free expression (subqueries and cross-references
 to other columns in the current table are not allowed). The
 data type of the default expression must match the data type of the
 column.
 The default expression will be used in any insert operation that
 does not specify a value for the column. If there is no default
 for a column, then the default is null.
 </DD
><DT
><TT
CLASS="LITERAL"
>UNIQUE</TT
> (column constraint) <TT
CLASS="LITERAL"
>UNIQUE ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] )</TT
> (table constraint)</DT
><DD
> The <TT
CLASS="LITERAL"
>UNIQUE</TT
> constraint specifies that a
 group of one or more columns of a table can contain
 only unique values. The behavior of the unique table constraint
 is the same as that for column constraints, with the additional
 capability to span multiple columns.
 For the purpose of a unique constraint, null values are not
 considered equal.
 Each unique table constraint must name a set of columns that is
 different from the set of columns named by any other unique or
 primary key constraint defined for the table. (Otherwise it
 would just be the same constraint listed twice.)
 </DD
><DT
><TT
CLASS="LITERAL"
>PRIMARY KEY</TT
> (column constraint) <TT
CLASS="LITERAL"
>PRIMARY KEY ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] )</TT
> (table constraint)</DT
><DD
> The <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
> constraint specifies that a column or
 columns of a table can contain only unique (non-duplicate), nonnull
 values. Only one primary key can be specified for a table, whether as a
 column constraint or a table constraint.
 The primary key constraint should name a set of columns that is
 different from the set of columns named by any unique
 constraint defined for the same table. (Otherwise, the unique
 constraint is redundant and will be discarded.)
 <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
> enforces the same data constraints as
 a combination of <TT
CLASS="LITERAL"
>UNIQUE</TT
> and <TT
CLASS="LITERAL"
>NOT NULL</TT
>, but
 identifying a set of columns as the primary key also provides metadata
 about the design of the schema, since a primary key implies that other
 tables can rely on this set of columns as a unique identifier for rows.
 </DD
><DT
><A
NAME="SQL-CREATETABLE-EXCLUDE"
></A
><TT
CLASS="LITERAL"
>EXCLUDE [ USING <TT
CLASS="REPLACEABLE"
>index_method</TT
> ] ( <TT
CLASS="REPLACEABLE"
>exclude_element</TT
> WITH <TT
CLASS="REPLACEABLE"
>operator</TT
> [, ... ] ) <TT
CLASS="REPLACEABLE"
>index_parameters</TT
> [ WHERE ( <TT
CLASS="REPLACEABLE"
>predicate</TT
> ) ]</TT
></DT
><DD
> The <TT
CLASS="LITERAL"
>EXCLUDE</TT
> clause defines an exclusion
 constraint, which guarantees that if
 any two rows are compared on the specified column(s) or
 expression(s) using the specified operator(s), not all of these
 comparisons will return <TT
CLASS="LITERAL"
>TRUE</TT
>. If all of the
 specified operators test for equality, this is equivalent to a
 <TT
CLASS="LITERAL"
>UNIQUE</TT
> constraint, although an ordinary unique constraint
 will be faster. However, exclusion constraints can specify
 constraints that are more general than simple equality.
 For example, you can specify a constraint that
 no two rows in the table contain overlapping circles
 (see <A
HREF="datatype-geometric.html"
>Section 8.8</A
>) by using the
 <TT
CLASS="LITERAL"
>&amp;&amp;</TT
> operator.
 Exclusion constraints are implemented using
 an index, so each specified operator must be associated with an
 appropriate operator class
 (see <A
HREF="indexes-opclass.html"
>Section 11.9</A
>) for the index access
 method <TT
CLASS="REPLACEABLE"
>index_method</TT
>.
 The operators are required to be commutative.
 Each <TT
CLASS="REPLACEABLE"
>exclude_element</TT
>
 can optionally specify an operator class and/or ordering options;
 these are described fully under
 <A
HREF="sql-createindex.html"
>CREATE INDEX</A
>.
 The access method must support <TT
CLASS="LITERAL"
>amgettuple</TT
> (see <A
HREF="indexam.html"
>Chapter 52</A
>); at present this means <ACRONYM
CLASS="ACRONYM"
>GIN</ACRONYM
>
 cannot be used. Although it's allowed, there is little point in using
 B-tree or hash indexes with an exclusion constraint, because this
 does nothing that an ordinary unique constraint doesn't do better.
 So in practice the access method will always be <ACRONYM
CLASS="ACRONYM"
>GiST</ACRONYM
> or
 <ACRONYM
CLASS="ACRONYM"
>SP-GiST</ACRONYM
>.
 The <TT
CLASS="REPLACEABLE"
>predicate</TT
> allows you to specify an
 exclusion constraint on a subset of the table; internally this creates a
 partial index. Note that parentheses are required around the predicate.
 </DD
><DT
><TT
CLASS="LITERAL"
>REFERENCES <TT
CLASS="REPLACEABLE"
>reftable</TT
> [ ( <TT
CLASS="REPLACEABLE"
>refcolumn</TT
> ) ] [ MATCH <TT
CLASS="REPLACEABLE"
>matchtype</TT
> ] [ ON DELETE <TT
CLASS="REPLACEABLE"
>action</TT
> ] [ ON UPDATE <TT
CLASS="REPLACEABLE"
>action</TT
> ]</TT
> (column constraint) <TT
CLASS="LITERAL"
>FOREIGN KEY ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ... ] )
 REFERENCES <TT
CLASS="REPLACEABLE"
>reftable</TT
> [ ( <TT
CLASS="REPLACEABLE"
>refcolumn</TT
> [, ... ] ) ]
 [ MATCH <TT
CLASS="REPLACEABLE"
>matchtype</TT
> ]
 [ ON DELETE <TT
CLASS="REPLACEABLE"
>action</TT
> ]
 [ ON UPDATE <TT
CLASS="REPLACEABLE"
>action</TT
> ]</TT
>
 (table constraint)</DT
><DD
> These clauses specify a foreign key constraint, which requires
 that a group of one or more columns of the new table must only
 contain values that match values in the referenced
 column(s) of some row of the referenced table. If <TT
CLASS="REPLACEABLE"
>refcolumn</TT
> is omitted, the
 primary key of the <TT
CLASS="REPLACEABLE"
>reftable</TT
>
 is used. The referenced columns must be the columns of a non-deferrable
 unique or primary key constraint in the referenced table. Note that
 foreign key constraints cannot be defined between temporary tables and
 permanent tables.
 A value inserted into the referencing column(s) is matched against the
 values of the referenced table and referenced columns using the
 given match type. There are three match types: <TT
CLASS="LITERAL"
>MATCH
 FULL</TT
>, <TT
CLASS="LITERAL"
>MATCH PARTIAL</TT
>, and <TT
CLASS="LITERAL"
>MATCH
 SIMPLE</TT
>, which is also the default. <TT
CLASS="LITERAL"
>MATCH
 FULL</TT
> will not allow one column of a multicolumn foreign key
 to be null unless all foreign key columns are null.
 <TT
CLASS="LITERAL"
>MATCH SIMPLE</TT
> allows some foreign key columns
 to be null while other parts of the foreign key are not
 null. <TT
CLASS="LITERAL"
>MATCH PARTIAL</TT
> is not yet implemented.
 In addition, when the data in the referenced columns is changed,
 certain actions are performed on the data in this table's
 columns. The <TT
CLASS="LITERAL"
>ON DELETE</TT
> clause specifies the
 action to perform when a referenced row in the referenced table is
 being deleted. Likewise, the <TT
CLASS="LITERAL"
>ON UPDATE</TT
>
 clause specifies the action to perform when a referenced column
 in the referenced table is being updated to a new value. If the
 row is updated, but the referenced column is not actually
 changed, no action is done. Referential actions other than the
 <TT
CLASS="LITERAL"
>NO ACTION</TT
> check cannot be deferred, even if
 the constraint is declared deferrable. There are the following possible
 actions for each clause:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>NO ACTION</TT
></DT
><DD
> Produce an error indicating that the deletion or update
 would create a foreign key constraint violation.
 If the constraint is deferred, this
 error will be produced at constraint check time if there still
 exist any referencing rows. This is the default action.
 </DD
><DT
><TT
CLASS="LITERAL"
>RESTRICT</TT
></DT
><DD
> Produce an error indicating that the deletion or update
 would create a foreign key constraint violation.
 This is the same as <TT
CLASS="LITERAL"
>NO ACTION</TT
> except that
 the check is not deferrable.
 </DD
><DT
><TT
CLASS="LITERAL"
>CASCADE</TT
></DT
><DD
> Delete any rows referencing the deleted row, or update the
 value of the referencing column to the new value of the
 referenced column, respectively.
 </DD
><DT
><TT
CLASS="LITERAL"
>SET NULL</TT
></DT
><DD
> Set the referencing column(s) to null.
 </DD
><DT
><TT
CLASS="LITERAL"
>SET DEFAULT</TT
></DT
><DD
> Set the referencing column(s) to their default values.
 </DD
></DL
></DIV
>
 If the referenced column(s) are changed frequently, it might be wise to
 add an index to the foreign key column so that referential actions
 associated with the foreign key column can be performed more
 efficiently.
 </DD
><DT
><TT
CLASS="LITERAL"
>DEFERRABLE</TT
> <TT
CLASS="LITERAL"
>NOT DEFERRABLE</TT
></DT
><DD
> This controls whether the constraint can be deferred. A
 constraint that is not deferrable will be checked immediately
 after every command. Checking of constraints that are
 deferrable can be postponed until the end of the transaction
 (using the <A
HREF="sql-set-constraints.html"
>SET CONSTRAINTS</A
> command).
 <TT
CLASS="LITERAL"
>NOT DEFERRABLE</TT
> is the default.
 Currently, only <TT
CLASS="LITERAL"
>UNIQUE</TT
>, <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
>,
 <TT
CLASS="LITERAL"
>EXCLUDE</TT
>, and
 <TT
CLASS="LITERAL"
>REFERENCES</TT
> (foreign key) constraints accept this
 clause. <TT
CLASS="LITERAL"
>NOT NULL</TT
> and <TT
CLASS="LITERAL"
>CHECK</TT
> constraints are not
 deferrable.
 </DD
><DT
><TT
CLASS="LITERAL"
>INITIALLY IMMEDIATE</TT
> <TT
CLASS="LITERAL"
>INITIALLY DEFERRED</TT
></DT
><DD
> If a constraint is deferrable, this clause specifies the default
 time to check the constraint. If the constraint is
 <TT
CLASS="LITERAL"
>INITIALLY IMMEDIATE</TT
>, it is checked after each
 statement. This is the default. If the constraint is
 <TT
CLASS="LITERAL"
>INITIALLY DEFERRED</TT
>, it is checked only at the
 end of the transaction. The constraint check time can be
 altered with the <A
HREF="sql-set-constraints.html"
>SET CONSTRAINTS</A
> command.
 </DD
><DT
><TT
CLASS="LITERAL"
>WITH ( <TT
CLASS="REPLACEABLE"
>storage_parameter</TT
> [= <TT
CLASS="REPLACEABLE"
>value</TT
>] [, ... ] )</TT
></DT
><DD
> This clause specifies optional storage parameters for a table or index;
 see <A
HREF="sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS"
>Storage Parameters</A
> for more
 information. The <TT
CLASS="LITERAL"
>WITH</TT
> clause for a
 table can also include <TT
CLASS="LITERAL"
>OIDS=TRUE</TT
> (or just <TT
CLASS="LITERAL"
>OIDS</TT
>)
 to specify that rows of the new table
 should have OIDs (object identifiers) assigned to them, or
 <TT
CLASS="LITERAL"
>OIDS=FALSE</TT
> to specify that the rows should not have OIDs.
 If <TT
CLASS="LITERAL"
>OIDS</TT
> is not specified, the default setting depends upon
 the <A
HREF="runtime-config-compatible.html#GUC-DEFAULT-WITH-OIDS"
>default_with_oids</A
> configuration parameter.
 (If the new table inherits from any tables that have OIDs, then
 <TT
CLASS="LITERAL"
>OIDS=TRUE</TT
> is forced even if the command says
 <TT
CLASS="LITERAL"
>OIDS=FALSE</TT
>.)
 If <TT
CLASS="LITERAL"
>OIDS=FALSE</TT
> is specified or implied, the new
 table does not store OIDs and no OID will be assigned for a row inserted
 into it. This is generally considered worthwhile, since it
 will reduce OID consumption and thereby postpone the wraparound
 of the 32-bit OID counter. Once the counter wraps around, OIDs
 can no longer be assumed to be unique, which makes them
 considerably less useful. In addition, excluding OIDs from a
 table reduces the space required to store the table on disk by
 4 bytes per row (on most machines), slightly improving performance.
 To remove OIDs from a table after it has been created, use <A
HREF="sql-altertable.html"
>ALTER TABLE</A
>.
 </DD
><DT
><TT
CLASS="LITERAL"
>WITH OIDS</TT
> <TT
CLASS="LITERAL"
>WITHOUT OIDS</TT
></DT
><DD
> These are obsolescent syntaxes equivalent to <TT
CLASS="LITERAL"
>WITH (OIDS)</TT
>
 and <TT
CLASS="LITERAL"
>WITH (OIDS=FALSE)</TT
>, respectively. If you wish to give
 both an <TT
CLASS="LITERAL"
>OIDS</TT
> setting and storage parameters, you must use
 the <TT
CLASS="LITERAL"
>WITH ( ... )</TT
> syntax; see above.
 </DD
><DT
><TT
CLASS="LITERAL"
>ON COMMIT</TT
></DT
><DD
> The behavior of temporary tables at the end of a transaction
 block can be controlled using <TT
CLASS="LITERAL"
>ON COMMIT</TT
>.
 The three options are:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>PRESERVE ROWS</TT
></DT
><DD
> No special action is taken at the ends of transactions.
 This is the default behavior.
 </DD
><DT
><TT
CLASS="LITERAL"
>DELETE ROWS</TT
></DT
><DD
> All rows in the temporary table will be deleted at the end
 of each transaction block. Essentially, an automatic <A
HREF="sql-truncate.html"
>TRUNCATE</A
> is done
 at each commit.
 </DD
><DT
><TT
CLASS="LITERAL"
>DROP</TT
></DT
><DD
> The temporary table will be dropped at the end of the current
 transaction block.
 </DD
></DL
></DIV
></DD
><DT
><TT
CLASS="LITERAL"
>TABLESPACE <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
></TT
></DT
><DD
> The <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
> is the name
 of the tablespace in which the new table is to be created.
 If not specified,
 <A
HREF="runtime-config-client.html#GUC-DEFAULT-TABLESPACE"
>default_tablespace</A
> is consulted, or
 <A
HREF="runtime-config-client.html#GUC-TEMP-TABLESPACES"
>temp_tablespaces</A
> if the table is temporary.
 </DD
><DT
><TT
CLASS="LITERAL"
>USING INDEX TABLESPACE <TT
CLASS="REPLACEABLE"
>tablespace_name</TT
></TT
></DT
><DD
> This clause allows selection of the tablespace in which the index
 associated with a <TT
CLASS="LITERAL"
>UNIQUE</TT
>, <TT
CLASS="LITERAL"
>PRIMARY
 KEY</TT
>, or <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraint will be created.
 If not specified,
 <A
HREF="runtime-config-client.html#GUC-DEFAULT-TABLESPACE"
>default_tablespace</A
> is consulted, or
 <A
HREF="runtime-config-client.html#GUC-TEMP-TABLESPACES"
>temp_tablespaces</A
> if the table is temporary.
 </DD
></DL
></DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-CREATETABLE-STORAGE-PARAMETERS"
></A
><H3
>Storage Parameters</H3
> The <TT
CLASS="LITERAL"
>WITH</TT
> clause can specify storage parameters
 for tables, and for indexes associated with a <TT
CLASS="LITERAL"
>UNIQUE</TT
>,
 <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
>, or <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraint.
 Storage parameters for
 indexes are documented in <A
HREF="sql-createindex.html"
>CREATE INDEX</A
>.
 The storage parameters currently
 available for tables are listed below. For each parameter, unless noted,
 there is an additional parameter with the same name prefixed with
 <TT
CLASS="LITERAL"
>toast.</TT
>, which can be used to control the behavior of the
 table's secondary <ACRONYM
CLASS="ACRONYM"
>TOAST</ACRONYM
> table, if any
 (see <A
HREF="storage-toast.html"
>Section 56.2</A
> for more information about TOAST).
 Note that the TOAST table inherits the
 <TT
CLASS="LITERAL"
>autovacuum_*</TT
> values from its parent table, if there are
 no <TT
CLASS="LITERAL"
>toast.autovacuum_*</TT
> settings set.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>fillfactor</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> The fillfactor for a table is a percentage between 10 and 100.
 100 (complete packing) is the default. When a smaller fillfactor
 is specified, <TT
CLASS="COMMAND"
>INSERT</TT
> operations pack table pages only
 to the indicated percentage; the remaining space on each page is
 reserved for updating rows on that page. This gives <TT
CLASS="COMMAND"
>UPDATE</TT
>
 a chance to place the updated copy of a row on the same page as the
 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 TOAST tables.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_enabled</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_enabled</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
> Enables or disables the autovacuum daemon on a particular table.
 If true, the autovacuum daemon will initiate a <TT
CLASS="COMMAND"
>VACUUM</TT
> operation
 on a particular table when the number of updated or deleted tuples exceeds
 <TT
CLASS="LITERAL"
>autovacuum_vacuum_threshold</TT
> plus
 <TT
CLASS="LITERAL"
>autovacuum_vacuum_scale_factor</TT
> times the number of live tuples
 currently estimated to be in the relation.
 Similarly, it will initiate an <TT
CLASS="COMMAND"
>ANALYZE</TT
> operation when the
 number of inserted, updated or deleted tuples exceeds
 <TT
CLASS="LITERAL"
>autovacuum_analyze_threshold</TT
> plus
 <TT
CLASS="LITERAL"
>autovacuum_analyze_scale_factor</TT
> times the number of live tuples
 currently estimated to be in the relation.
 If false, this table will not be autovacuumed, except to prevent
 transaction Id wraparound. See <A
HREF="routine-vacuuming.html#VACUUM-FOR-WRAPAROUND"
>Section 23.1.5</A
> for
 more about wraparound prevention.
 Observe that this variable inherits its value from the <A
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM"
>autovacuum</A
> setting.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_vacuum_threshold</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_vacuum_threshold</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Minimum number of updated or deleted tuples before initiate a
 <TT
CLASS="COMMAND"
>VACUUM</TT
> operation on a particular table.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_vacuum_scale_factor</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_vacuum_scale_factor</TT
> (<TT
CLASS="TYPE"
>float4</TT
>)</DT
><DD
> Multiplier for <TT
CLASS="STRUCTFIELD"
>reltuples</TT
> to add to
 <TT
CLASS="LITERAL"
>autovacuum_vacuum_threshold</TT
>.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_analyze_threshold</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Minimum number of inserted, updated, or deleted tuples before initiate an
 <TT
CLASS="COMMAND"
>ANALYZE</TT
> operation on a particular table.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_analyze_scale_factor</TT
> (<TT
CLASS="TYPE"
>float4</TT
>)</DT
><DD
> Multiplier for <TT
CLASS="STRUCTFIELD"
>reltuples</TT
> to add to
 <TT
CLASS="LITERAL"
>autovacuum_analyze_threshold</TT
>.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_vacuum_cost_delay</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_vacuum_cost_delay</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Custom <A
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DELAY"
>autovacuum_vacuum_cost_delay</A
> parameter.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_vacuum_cost_limit</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_vacuum_cost_limit</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Custom <A
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-LIMIT"
>autovacuum_vacuum_cost_limit</A
> parameter.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_freeze_min_age</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_freeze_min_age</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Custom <A
HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE"
>vacuum_freeze_min_age</A
> parameter. Note that
 autovacuum will ignore attempts to set a per-table
 <TT
CLASS="LITERAL"
>autovacuum_freeze_min_age</TT
> larger than the half system-wide
 <A
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE"
>autovacuum_freeze_max_age</A
> setting.
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_freeze_max_age</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_freeze_max_age</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Custom <A
HREF="runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE"
>autovacuum_freeze_max_age</A
> parameter. Note that
 autovacuum will ignore attempts to set a per-table
 <TT
CLASS="LITERAL"
>autovacuum_freeze_max_age</TT
> larger than the system-wide setting
 (it can only be set smaller).
 </DD
><DT
><TT
CLASS="LITERAL"
>autovacuum_freeze_table_age</TT
>, <TT
CLASS="LITERAL"
>toast.autovacuum_freeze_table_age</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
> Custom <A
HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE"
>vacuum_freeze_table_age</A
> parameter.
 </DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATETABLE-NOTES"
></A
><H2
>Notes</H2
> Using OIDs in new applications is not recommended: where
 possible, using a <TT
CLASS="LITERAL"
>SERIAL</TT
> or other sequence
 generator as the table's primary key is preferred. However, if
 your application does make use of OIDs to identify specific
 rows of a table, it is recommended to create a unique constraint
 on the <TT
CLASS="STRUCTFIELD"
>oid</TT
> column of that table, to ensure that
 OIDs in the table will indeed uniquely identify rows even after
 counter wraparound. Avoid assuming that OIDs are unique across
 tables; if you need a database-wide unique identifier, use the
 combination of <TT
CLASS="STRUCTFIELD"
>tableoid</TT
> and row OID for the
 purpose.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: The use of <TT
CLASS="LITERAL"
>OIDS=FALSE</TT
> is not recommended
 for tables with no primary key, since without either an OID or a
 unique data key, it is difficult to identify specific rows.
 </BLOCKQUOTE
></DIV
> PostgreSQL automatically creates an
 index for each unique constraint and primary key constraint to
 enforce uniqueness. Thus, it is not necessary to create an
 index explicitly for primary key columns. (See <A
HREF="sql-createindex.html"
>CREATE INDEX</A
> for more information.)
 Unique constraints and primary keys are not inherited in the
 current implementation. This makes the combination of
 inheritance and unique constraints rather dysfunctional.
 A table cannot have more than 1600 columns. (In practice, the
 effective limit is usually lower because of tuple-length constraints.)
 </DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATETABLE-EXAMPLES"
></A
><H2
>Examples</H2
> Create table <TT
CLASS="STRUCTNAME"
>films</TT
> and table
 <TT
CLASS="STRUCTNAME"
>distributors</TT
>:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE films (
 code char(5) CONSTRAINT firstkey PRIMARY KEY,
 title varchar(40) NOT NULL,
 did integer NOT NULL,
 date_prod date,
 kind varchar(10),
 len interval hour to minute
);

CREATE TABLE distributors (
 did integer PRIMARY KEY DEFAULT nextval('serial'),
 name varchar(40) NOT NULL CHECK (name &lt;&gt; '')
);</PRE
>
 Create a table with a 2-dimensional array:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE array_int (
 vector int[][]
);</PRE
>
 Define a unique table constraint for the table
 <TT
CLASS="LITERAL"
>films</TT
>. Unique table constraints can be defined
 on one or more columns of the table:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer CHECK (did &gt; 100),
 name varchar(40)
);</PRE
>
 Define a check table constraint:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer,
 name varchar(40)
 CONSTRAINT con1 CHECK (did &gt; 100 AND name &lt;&gt; '')
);</PRE
>
 Define a primary key table constraint for the table
 <TT
CLASS="STRUCTNAME"
>films</TT
>:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE films (
 code char(5),
 title varchar(40),
 did integer,
 date_prod date,
 kind varchar(10),
 len interval hour to minute,
 CONSTRAINT code_title PRIMARY KEY(code,title)
);</PRE
>
 Define a primary key constraint for table
 <TT
CLASS="STRUCTNAME"
>distributors</TT
>. The following two examples are
 equivalent, the first using the table constraint syntax, the second
 the column constraint syntax:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer,
 name varchar(40),
 PRIMARY KEY(did)
);

CREATE TABLE distributors (
 did integer PRIMARY KEY,
 name varchar(40)
);</PRE
>
 Assign a literal constant default value for the column
 <TT
CLASS="LITERAL"
>name</TT
>, arrange for the default value of column
 <TT
CLASS="LITERAL"
>did</TT
> to be generated by selecting the next value
 of a sequence object, and make the default value of
 <TT
CLASS="LITERAL"
>modtime</TT
> be the time at which the row is
 inserted:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 name varchar(40) DEFAULT 'Luso Films',
 did integer DEFAULT nextval('distributors_serial'),
 modtime timestamp DEFAULT current_timestamp
);</PRE
>
 Define two <TT
CLASS="LITERAL"
>NOT NULL</TT
> column constraints on the table
 <CODE
CLASS="CLASSNAME"
>distributors</CODE
>, one of which is explicitly
 given a name:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer CONSTRAINT no_null NOT NULL,
 name varchar(40) NOT NULL
);</PRE
>
 Define a unique constraint for the <TT
CLASS="LITERAL"
>name</TT
> column:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer,
 name varchar(40) UNIQUE
);</PRE
>

The same, specified as a table constraint:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer,
 name varchar(40),
 UNIQUE(name)
);</PRE
>
 Create the same table, specifying 70% fill factor for both the table
 and its unique index:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE distributors (
 did integer,
 name varchar(40),
 UNIQUE(name) WITH (fillfactor=70)
)
WITH (fillfactor=70);</PRE
>
 Create table <TT
CLASS="STRUCTNAME"
>circles</TT
> with an exclusion
 constraint that prevents any two circles from overlapping:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE circles (
 c circle,
 EXCLUDE USING gist (c WITH &amp;&amp;)
);</PRE
>
 Create table <TT
CLASS="STRUCTNAME"
>cinemas</TT
> in tablespace <TT
CLASS="STRUCTNAME"
>diskvol1</TT
>:

<PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE cinemas (
 id serial,
 name text,
 location text
) TABLESPACE diskvol1;</PRE
>
 Create a composite type and a typed table:
<PRE
CLASS="PROGRAMLISTING"
>CREATE TYPE employee_type AS (name text, salary numeric);

CREATE TABLE employees OF employee_type (
 PRIMARY KEY (name),
 salary WITH OPTIONS DEFAULT 1000
);</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATETABLE-COMPATIBILITY"
></A
><H2
>Compatibility</H2
> The <TT
CLASS="COMMAND"
>CREATE TABLE</TT
> command conforms to the
 <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> standard, with exceptions listed below.
 <DIV
CLASS="REFSECT2"
><A
NAME="AEN71148"
></A
><H3
>Temporary Tables</H3
> Although the syntax of <TT
CLASS="LITERAL"
>CREATE TEMPORARY TABLE</TT
>
 resembles that of the SQL standard, the effect is not the same. In the
 standard,
 temporary tables are defined just once and automatically exist (starting
 with empty contents) in every session that needs them.
 PostgreSQL instead
 requires each session to issue its own <TT
CLASS="LITERAL"
>CREATE TEMPORARY
 TABLE</TT
> command for each temporary table to be used. This allows
 different sessions to use the same temporary table name for different
 purposes, whereas the standard's approach constrains all instances of a
 given temporary table name to have the same table structure.
 The standard's definition of the behavior of temporary tables is
 widely ignored. PostgreSQL's behavior
 on this point is similar to that of several other SQL databases.
 The SQL standard also distinguishes between global and local temporary
 tables, where a local temporary table has a separate set of contents for
 each SQL module within each session, though its definition is still shared
 across sessions. Since PostgreSQL does not
 support SQL modules, this distinction is not relevant in
 PostgreSQL.
 For compatibility's sake, PostgreSQL will
 accept the <TT
CLASS="LITERAL"
>GLOBAL</TT
> and <TT
CLASS="LITERAL"
>LOCAL</TT
> keywords
 in a temporary table declaration, but they currently have no effect.
 Use of these keywords is discouraged, since future versions of
 PostgreSQL might adopt a more
 standard-compliant interpretation of their meaning.
 The <TT
CLASS="LITERAL"
>ON COMMIT</TT
> clause for temporary tables
 also resembles the SQL standard, but has some differences.
 If the <TT
CLASS="LITERAL"
>ON COMMIT</TT
> clause is omitted, SQL specifies that the
 default behavior is <TT
CLASS="LITERAL"
>ON COMMIT DELETE ROWS</TT
>. However, the
 default behavior in PostgreSQL is
 <TT
CLASS="LITERAL"
>ON COMMIT PRESERVE ROWS</TT
>. The <TT
CLASS="LITERAL"
>ON COMMIT
 DROP</TT
> option does not exist in SQL.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71171"
></A
><H3
>Non-deferred Uniqueness Constraints</H3
> When a <TT
CLASS="LITERAL"
>UNIQUE</TT
> or <TT
CLASS="LITERAL"
>PRIMARY KEY</TT
> constraint is
 not deferrable, PostgreSQL checks for
 uniqueness immediately whenever a row is inserted or modified.
 The SQL standard says that uniqueness should be enforced only at
 the end of the statement; this makes a difference when, for example,
 a single command updates multiple key values. To obtain
 standard-compliant behavior, declare the constraint as
 <TT
CLASS="LITERAL"
>DEFERRABLE</TT
> but not deferred (i.e., <TT
CLASS="LITERAL"
>INITIALLY
 IMMEDIATE</TT
>). Be aware that this can be significantly slower than
 immediate uniqueness checking.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71179"
></A
><H3
>Column Check Constraints</H3
> The SQL standard says that <TT
CLASS="LITERAL"
>CHECK</TT
> column constraints
 can only refer to the column they apply to; only <TT
CLASS="LITERAL"
>CHECK</TT
>
 table constraints can refer to multiple columns.
 PostgreSQL does not enforce this
 restriction; it treats column and table check constraints alike.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71185"
></A
><H3
><TT
CLASS="LITERAL"
>EXCLUDE</TT
> Constraint</H3
> The <TT
CLASS="LITERAL"
>EXCLUDE</TT
> constraint type is a
 PostgreSQL extension.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71191"
></A
><H3
><TT
CLASS="LITERAL"
>NULL</TT
> "Constraint"</H3
> The <TT
CLASS="LITERAL"
>NULL</TT
> "constraint" (actually a
 non-constraint) is a PostgreSQL
 extension to the SQL standard that is included for compatibility with some
 other database systems (and for symmetry with the <TT
CLASS="LITERAL"
>NOT
 NULL</TT
> constraint). Since it is the default for any
 column, its presence is simply noise.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71200"
></A
><H3
>Inheritance</H3
> Multiple inheritance via the <TT
CLASS="LITERAL"
>INHERITS</TT
> clause is
 a PostgreSQL language extension.
 SQL:1999 and later define single inheritance using a
 different syntax and different semantics. SQL:1999-style
 inheritance is not yet supported by
 PostgreSQL.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71206"
></A
><H3
>Zero-column Tables</H3
> PostgreSQL allows a table of no columns
 to be created (for example, <TT
CLASS="LITERAL"
>CREATE TABLE foo();</TT
>). This
 is an extension from the SQL standard, which does not allow zero-column
 tables. Zero-column tables are not in themselves very useful, but
 disallowing them creates odd special cases for <TT
CLASS="COMMAND"
>ALTER TABLE
 DROP COLUMN</TT
>, so it seems cleaner to ignore this spec restriction.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71212"
></A
><H3
><TT
CLASS="LITERAL"
>LIKE</TT
> Clause</H3
> While a <TT
CLASS="LITERAL"
>LIKE</TT
> clause exists in the SQL standard, many of the
 options that PostgreSQL accepts for it are not
 in the standard, and some of the standard's options are not implemented
 by PostgreSQL.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71219"
></A
><H3
><TT
CLASS="LITERAL"
>WITH</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>WITH</TT
> clause is a PostgreSQL
 extension; neither storage parameters nor OIDs are in the standard.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71225"
></A
><H3
>Tablespaces</H3
> The PostgreSQL concept of tablespaces is not
 part of the standard. Hence, the clauses <TT
CLASS="LITERAL"
>TABLESPACE</TT
>
 and <TT
CLASS="LITERAL"
>USING INDEX TABLESPACE</TT
> are extensions.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN71231"
></A
><H3
>Typed Tables</H3
> Typed tables implement a subset of the SQL standard. According to
 the standard, a typed table has columns corresponding to the
 underlying composite type as well as one other column that is
 the "self-referencing column". PostgreSQL does not
 support these self-referencing columns explicitly, but the same
 effect can be had using the OID feature.
 </DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN71235"
></A
><H2
>See Also</H2
><A
HREF="sql-altertable.html"
>ALTER TABLE</A
>, <A
HREF="sql-droptable.html"
>DROP TABLE</A
>, <A
HREF="sql-createtablespace.html"
>CREATE TABLESPACE</A
>, <A
HREF="sql-createtype.html"
>CREATE TYPE</A
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-createserver.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-createtableas.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CREATE SERVER</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>CREATE TABLE AS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

FILE FOLDER

Name	Size	Permission
LEGALNOTICE.html	2681 bytes	0644
acronyms.html	16284 bytes	0644
admin.html	12564 bytes	0644
adminpack.html	7889 bytes	0644
app-clusterdb.html	10602 bytes	0644
app-createdb.html	12856 bytes	0644
app-createlang.html	9907 bytes	0644
app-createuser.html	15640 bytes	0644
app-dropdb.html	9642 bytes	0644
app-droplang.html	9638 bytes	0644
app-dropuser.html	9596 bytes	0644
app-ecpg.html	8718 bytes	0644
app-initdb.html	15405 bytes	0644
app-pg-ctl.html	22459 bytes	0644
app-pg-dumpall.html	20706 bytes	0644
app-pgbasebackup.html	19833 bytes	0644
app-pgconfig.html	11093 bytes	0644
app-pgcontroldata.html	3979 bytes	0644
app-pgdump.html	43964 bytes	0644
app-pgreceivexlog.html	11057 bytes	0644
app-pgresetxlog.html	11566 bytes	0644
app-pgrestore.html	30269 bytes	0644
app-postgres.html	31828 bytes	0644
app-postmaster.html	3005 bytes	0644
app-psql.html	138871 bytes	0644
app-reindexdb.html	11281 bytes	0644
app-vacuumdb.html	12616 bytes	0644
appendixes.html	26329 bytes	0644
applevel-consistency.html	10315 bytes	0644
archive-recovery-settings.html	7338 bytes	0644
arrays.html	28079 bytes	0644
auth-delay.html	3780 bytes	0644
auth-methods.html	36202 bytes	0644
auth-pg-hba-conf.html	29759 bytes	0644
auth-username-maps.html	8597 bytes	0644
auto-explain.html	9887 bytes	0644
backup-dump.html	15927 bytes	0644
backup-file.html	7996 bytes	0644
backup.html	4485 bytes	0644
biblio.html	11549 bytes	0644
bki-commands.html	9646 bytes	0644
bki-example.html	3049 bytes	0644
bki-format.html	3463 bytes	0644
bki-structure.html	4320 bytes	0644
bki.html	4330 bytes	0644
bookindex.html	243165 bytes	0644
btree-gin.html	4600 bytes	0644
btree-gist.html	6884 bytes	0644
bug-reporting.html	18646 bytes	0644
catalog-pg-aggregate.html	5502 bytes	0644
catalog-pg-am.html	10547 bytes	0644
catalog-pg-amop.html	7593 bytes	0644
catalog-pg-amproc.html	4885 bytes	0644
catalog-pg-attrdef.html	4364 bytes	0644
catalog-pg-attribute.html	10287 bytes	0644
catalog-pg-auth-members.html	4255 bytes	0644
catalog-pg-authid.html	6815 bytes	0644
catalog-pg-cast.html	6955 bytes	0644
catalog-pg-class.html	12661 bytes	0644
catalog-pg-collation.html	5897 bytes	0644
catalog-pg-constraint.html	11579 bytes	0644
catalog-pg-conversion.html	4430 bytes	0644
catalog-pg-database.html	7027 bytes	0644
catalog-pg-db-role-setting.html	4068 bytes	0644
catalog-pg-default-acl.html	5267 bytes	0644
catalog-pg-depend.html	8635 bytes	0644
catalog-pg-description.html	4478 bytes	0644
catalog-pg-enum.html	4716 bytes	0644
catalog-pg-extension.html	5282 bytes	0644
catalog-pg-foreign-data-wrapper.html	4945 bytes	0644
catalog-pg-foreign-server.html	4688 bytes	0644
catalog-pg-foreign-table.html	4036 bytes	0644
catalog-pg-index.html	8868 bytes	0644
catalog-pg-inherits.html	3888 bytes	0644
catalog-pg-language.html	5952 bytes	0644
catalog-pg-largeobject-metadata.html	3630 bytes	0644
catalog-pg-largeobject.html	5154 bytes	0644
catalog-pg-namespace.html	3751 bytes	0644
catalog-pg-opclass.html	5863 bytes	0644
catalog-pg-operator.html	6645 bytes	0644
catalog-pg-opfamily.html	4811 bytes	0644
catalog-pg-pltemplate.html	5364 bytes	0644
catalog-pg-proc.html	13403 bytes	0644
catalog-pg-range.html	5182 bytes	0644
catalog-pg-rewrite.html	5391 bytes	0644
catalog-pg-seclabel.html	4515 bytes	0644
catalog-pg-shdepend.html	7043 bytes	0644
catalog-pg-shdescription.html	4247 bytes	0644
catalog-pg-shseclabel.html	4404 bytes	0644
catalog-pg-statistic.html	9538 bytes	0644
catalog-pg-tablespace.html	4158 bytes	0644
catalog-pg-trigger.html	8287 bytes	0644
catalog-pg-ts-config-map.html	4193 bytes	0644
catalog-pg-ts-config.html	4481 bytes	0644
catalog-pg-ts-dict.html	4716 bytes	0644
catalog-pg-ts-parser.html	5082 bytes	0644
catalog-pg-ts-template.html	4258 bytes	0644
catalog-pg-type.html	19905 bytes	0644
catalog-pg-user-mapping.html	3847 bytes	0644
catalogs-overview.html	10431 bytes	0644
catalogs.html	10387 bytes	0644
charset.html	4162 bytes	0644
chkpass.html	4391 bytes	0644
citext.html	11148 bytes	0644
client-authentication-problems.html	4224 bytes	0644
client-authentication.html	5914 bytes	0644
client-interfaces.html	13717 bytes	0644
collation.html	14222 bytes	0644
config-setting.html	11146 bytes	0644
connect-estab.html	4315 bytes	0644
continuous-archiving.html	49830 bytes	0644
contrib-dblink-build-sql-delete.html	5451 bytes	0644
contrib-dblink-build-sql-insert.html	6052 bytes	0644
contrib-dblink-build-sql-update.html	6281 bytes	0644
contrib-dblink-cancel-query.html	3820 bytes	0644
contrib-dblink-close.html	4650 bytes	0644
contrib-dblink-connect-u.html	4482 bytes	0644
contrib-dblink-connect.html	7325 bytes	0644
contrib-dblink-disconnect.html	3718 bytes	0644
contrib-dblink-error-message.html	3508 bytes	0644
contrib-dblink-exec.html	5466 bytes	0644
contrib-dblink-fetch.html	5979 bytes	0644
contrib-dblink-function.html	8630 bytes	0644
contrib-dblink-get-connections.html	3206 bytes	0644
contrib-dblink-get-notify.html	4168 bytes	0644
contrib-dblink-get-pkey.html	4498 bytes	0644
contrib-dblink-get-result.html	6959 bytes	0644
contrib-dblink-is-busy.html	3490 bytes	0644
contrib-dblink-open.html	5464 bytes	0644
contrib-dblink-send-query.html	4170 bytes	0644
contrib-prog-client.html	3434 bytes	0644
contrib-prog-server.html	3837 bytes	0644
contrib-prog.html	3320 bytes	0644
contrib-spi.html	11236 bytes	0644
contrib.html	8904 bytes	0644
creating-cluster.html	12465 bytes	0644
cube.html	15941 bytes	0644
database-roles.html	6092 bytes	0644
datatype-binary.html	12893 bytes	0644
datatype-bit.html	5096 bytes	0644
datatype-boolean.html	5267 bytes	0644
datatype-character.html	11893 bytes	0644
datatype-datetime.html	50763 bytes	0644
datatype-enum.html	6433 bytes	0644
datatype-geometric.html	12503 bytes	0644
datatype-json.html	3439 bytes	0644
datatype-money.html	5482 bytes	0644
datatype-net-types.html	10423 bytes	0644
datatype-numeric.html	22353 bytes	0644
datatype-oid.html	9686 bytes	0644
datatype-pseudo.html	7285 bytes	0644
datatype-textsearch.html	10033 bytes	0644
datatype-uuid.html	4560 bytes	0644
datatype-xml.html	11334 bytes	0644
datatype.html	16609 bytes	0644
datetime-appendix.html	3525 bytes	0644
datetime-config-files.html	8980 bytes	0644
datetime-input-rules.html	6763 bytes	0644
datetime-keywords.html	5096 bytes	0644
datetime-units-history.html	7634 bytes	0644
dblink.html	5322 bytes	0644
ddl-alter.html	10498 bytes	0644
ddl-basics.html	7816 bytes	0644
ddl-constraints.html	22790 bytes	0644
ddl-default.html	4540 bytes	0644
ddl-depend.html	6498 bytes	0644
ddl-foreign-data.html	4485 bytes	0644
ddl-inherit.html	15308 bytes	0644
ddl-others.html	3080 bytes	0644
ddl-partitioning.html	27763 bytes	0644
ddl-priv.html	6066 bytes	0644
ddl-schemas.html	18046 bytes	0644
ddl-system-columns.html	8049 bytes	0644
ddl.html	6382 bytes	0644
dict-int.html	4793 bytes	0644
dict-xsyn.html	6481 bytes	0644
different-replication-solutions.html	14793 bytes	0644
disk-full.html	3517 bytes	0644
disk-usage.html	5661 bytes	0644
diskusage.html	2668 bytes	0644
dml-delete.html	3565 bytes	0644
dml-insert.html	5801 bytes	0644
dml-returning.html	5104 bytes	0644
dml-update.html	5556 bytes	0644
dml.html	2944 bytes	0644
docguide-authoring.html	6757 bytes	0644
docguide-build.html	15280 bytes	0644
docguide-docbook.html	3853 bytes	0644
docguide-style.html	7429 bytes	0644
docguide-toolsets.html	20683 bytes	0644
docguide.html	3624 bytes	0644
dummy-seclabel.html	4358 bytes	0644
dynamic-trace.html	27234 bytes	0644
earthdistance.html	8806 bytes	0644
ecpg-commands.html	9527 bytes	0644
ecpg-concept.html	4979 bytes	0644
ecpg-connect.html	10826 bytes	0644
ecpg-cpp.html	9624 bytes	0644
ecpg-descriptors.html	34909 bytes	0644
ecpg-develop.html	7964 bytes	0644
ecpg-dynamic.html	6515 bytes	0644
ecpg-errors.html	25737 bytes	0644
ecpg-informix-compat.html	52760 bytes	0644
ecpg-library.html	5798 bytes	0644
ecpg-lo.html	5527 bytes	0644
ecpg-pgtypes.html	54457 bytes	0644
ecpg-preproc.html	8985 bytes	0644
ecpg-process.html	5386 bytes	0644
ecpg-sql-allocate-descriptor.html	3983 bytes	0644
ecpg-sql-commands.html	4698 bytes	0644
ecpg-sql-connect.html	9375 bytes	0644
ecpg-sql-deallocate-descriptor.html	3773 bytes	0644
ecpg-sql-declare.html	5397 bytes	0644
ecpg-sql-describe.html	4595 bytes	0644
ecpg-sql-disconnect.html	4733 bytes	0644
ecpg-sql-execute-immediate.html	3877 bytes	0644
ecpg-sql-get-descriptor.html	7709 bytes	0644
ecpg-sql-open.html	4642 bytes	0644
ecpg-sql-prepare.html	4177 bytes	0644
ecpg-sql-set-autocommit.html	3333 bytes	0644
ecpg-sql-set-connection.html	3929 bytes	0644
ecpg-sql-set-descriptor.html	5505 bytes	0644
ecpg-sql-type.html	5026 bytes	0644
ecpg-sql-var.html	3539 bytes	0644
ecpg-sql-whenever.html	4686 bytes	0644
ecpg-variables.html	40283 bytes	0644
ecpg.html	10344 bytes	0644
encryption-options.html	7495 bytes	0644
errcodes-appendix.html	36965 bytes	0644
error-message-reporting.html	14124 bytes	0644
error-style-guide.html	16769 bytes	0644
event-log-registration.html	4188 bytes	0644
executor.html	6612 bytes	0644
explicit-joins.html	11019 bytes	0644
explicit-locking.html	25073 bytes	0644
extend-extensions.html	32430 bytes	0644
extend-how.html	4552 bytes	0644
extend-pgxs.html	11761 bytes	0644
extend-type-system.html	10111 bytes	0644
extend.html	9982 bytes	0644
external-admin-tools.html	2722 bytes	0644
external-extensions.html	3263 bytes	0644
external-interfaces.html	5513 bytes	0644
external-pl.html	4670 bytes	0644
external-projects.html	3004 bytes	0644
fdw-callbacks.html	12905 bytes	0644
fdw-functions.html	4496 bytes	0644
fdw-helpers.html	5988 bytes	0644
fdw-planning.html	9845 bytes	0644
fdwhandler.html	3990 bytes	0644
features-sql-standard.html	39105 bytes	0644
features.html	7566 bytes	0644
file-fdw.html	7709 bytes	0644
functions-admin.html	50395 bytes	0644
functions-aggregate.html	21814 bytes	0644
functions-array.html	13521 bytes	0644
functions-binarystring.html	12588 bytes	0644
functions-bitstring.html	6786 bytes	0644
functions-comparison.html	10638 bytes	0644
functions-comparisons.html	13531 bytes	0644
functions-conditional.html	11007 bytes	0644
functions-datetime.html	48303 bytes	0644
functions-enum.html	5491 bytes	0644
functions-formatting.html	35401 bytes	0644
functions-geometry.html	20347 bytes	0644
functions-info.html	58658 bytes	0644
functions-json.html	3814 bytes	0644
functions-logical.html	4665 bytes	0644
functions-matching.html	75728 bytes	0644
functions-math.html	20401 bytes	0644
functions-net.html	13502 bytes	0644
functions-range.html	10857 bytes	0644
functions-sequence.html	12925 bytes	0644
functions-srf.html	8840 bytes	0644
functions-string.html	59052 bytes	0644
functions-subquery.html	16381 bytes	0644
functions-textsearch.html	20488 bytes	0644
functions-trigger.html	4548 bytes	0644
functions-window.html	12085 bytes	0644
functions-xml.html	32169 bytes	0644
functions.html	9939 bytes	0644
fuzzystrmatch.html	8061 bytes	0644
geqo-biblio.html	3459 bytes	0644
geqo-intro.html	4415 bytes	0644
geqo-intro2.html	5627 bytes	0644
geqo-pg-intro.html	8785 bytes	0644
geqo.html	3616 bytes	0644
gin-examples.html	3322 bytes	0644
gin-extensibility.html	14402 bytes	0644
gin-implementation.html	6564 bytes	0644
gin-intro.html	4662 bytes	0644
gin-limit.html	2817 bytes	0644
gin-tips.html	5713 bytes	0644
gin.html	2929 bytes	0644
gist-examples.html	3752 bytes	0644
gist-extensibility.html	24354 bytes	0644
gist-implementation.html	4101 bytes	0644
gist-intro.html	3616 bytes	0644
gist.html	2679 bytes	0644
git.html	4564 bytes	0644
high-availability.html	7698 bytes	0644
history.html	11918 bytes	0644
hot-standby.html	36045 bytes	0644
hstore.html	22629 bytes	0644
index-catalog.html	7996 bytes	0644
index-cost-estimation.html	9991 bytes	0644
index-functions.html	19114 bytes	0644
index-locking.html	8049 bytes	0644
index-scanning.html	10707 bytes	0644
index-unique-checks.html	9192 bytes	0644
index.html	8071 bytes	0644
indexam.html	5247 bytes	0644
indexes-bitmap-scans.html	6580 bytes	0644
indexes-collations.html	3640 bytes	0644
indexes-examine.html	7161 bytes	0644
indexes-expressional.html	4813 bytes	0644
indexes-intro.html	6313 bytes	0644
indexes-multicolumn.html	6298 bytes	0644
indexes-opclass.html	7336 bytes	0644
indexes-ordering.html	6480 bytes	0644
indexes-partial.html	11812 bytes	0644
indexes-types.html	10233 bytes	0644
indexes-unique.html	4002 bytes	0644
indexes.html	3619 bytes	0644
information-schema.html	11177 bytes	0644
infoschema-administrable-role-authorizations.html	3751 bytes	0644
infoschema-applicable-roles.html	3970 bytes	0644
infoschema-attributes.html	12807 bytes	0644
infoschema-character-sets.html	7050 bytes	0644
infoschema-check-constraint-routine-usage.html	4349 bytes	0644
infoschema-check-constraints.html	3876 bytes	0644
infoschema-collation-character-set-applicab.html	4425 bytes	0644
infoschema-collations.html	3885 bytes	0644
infoschema-column-domain-usage.html	4322 bytes	0644
infoschema-column-options.html	4109 bytes	0644
infoschema-column-privileges.html	5029 bytes	0644
infoschema-column-udt-usage.html	4583 bytes	0644
infoschema-columns.html	17625 bytes	0644
infoschema-constraint-column-usage.html	4873 bytes	0644
infoschema-constraint-table-usage.html	4774 bytes	0644
infoschema-data-type-privileges.html	5089 bytes	0644
infoschema-datatypes.html	4229 bytes	0644
infoschema-domain-constraints.html	4664 bytes	0644
infoschema-domain-udt-usage.html	4171 bytes	0644
infoschema-domains.html	11367 bytes	0644
infoschema-element-types.html	11374 bytes	0644
infoschema-enabled-roles.html	3780 bytes	0644
infoschema-foreign-data-wrapper-options.html	3910 bytes	0644
infoschema-foreign-data-wrappers.html	4227 bytes	0644
infoschema-foreign-server-options.html	3853 bytes	0644
infoschema-foreign-servers.html	4571 bytes	0644
infoschema-foreign-table-options.html	3974 bytes	0644
infoschema-foreign-tables.html	4072 bytes	0644
infoschema-information-schema-catalog-name.html	3357 bytes	0644
infoschema-key-column-usage.html	5185 bytes	0644
infoschema-parameters.html	10799 bytes	0644
infoschema-referential-constraints.html	5664 bytes	0644
infoschema-role-column-grants.html	5017 bytes	0644
infoschema-role-routine-grants.html	5360 bytes	0644
infoschema-role-table-grants.html	5427 bytes	0644
infoschema-role-udt-grants.html	4781 bytes	0644
infoschema-role-usage-grants.html	5010 bytes	0644
infoschema-routine-privileges.html	5032 bytes	0644
infoschema-routines.html	23052 bytes	0644
infoschema-schema.html	3180 bytes	0644
infoschema-schemata.html	4248 bytes	0644
infoschema-sequences.html	6111 bytes	0644
infoschema-sql-features.html	4708 bytes	0644
infoschema-sql-implementation-info.html	4503 bytes	0644
infoschema-sql-languages.html	5094 bytes	0644
infoschema-sql-packages.html	4178 bytes	0644
infoschema-sql-parts.html	4080 bytes	0644
infoschema-sql-sizing-profiles.html	4177 bytes	0644
infoschema-sql-sizing.html	4101 bytes	0644
infoschema-table-constraints.html	4914 bytes	0644
infoschema-table-privileges.html	5097 bytes	0644
infoschema-tables.html	5957 bytes	0644
infoschema-triggered-update-columns.html	4554 bytes	0644
infoschema-triggers.html	9447 bytes	0644
infoschema-udt-privileges.html	4509 bytes	0644
infoschema-usage-privileges.html	5512 bytes	0644
infoschema-user-defined-types.html	9753 bytes	0644
infoschema-user-mapping-options.html	4449 bytes	0644
infoschema-user-mappings.html	3833 bytes	0644
infoschema-view-column-usage.html	4728 bytes	0644
infoschema-view-routine-usage.html	4368 bytes	0644
infoschema-view-table-usage.html	4389 bytes	0644
infoschema-views.html	5529 bytes	0644
install-getsource.html	3574 bytes	0644
install-post.html	8076 bytes	0644
install-procedure.html	46527 bytes	0644
install-requirements.html	14481 bytes	0644
install-short.html	2870 bytes	0644
install-windows-full.html	19274 bytes	0644
install-windows-libpq.html	6283 bytes	0644
install-windows.html	6620 bytes	0644
installation-platform-notes.html	39380 bytes	0644
installation.html	4160 bytes	0644
intagg.html	6254 bytes	0644
intarray.html	13757 bytes	0644
internals.html	15638 bytes	0644
intro-whatis.html	4011 bytes	0644
isn.html	13356 bytes	0644
kernel-resources.html	37822 bytes	0644
largeobjects.html	4675 bytes	0644
libpq-async.html	21020 bytes	0644
libpq-build.html	6369 bytes	0644
libpq-cancel.html	6777 bytes	0644
libpq-connect.html	51248 bytes	0644
libpq-control.html	6280 bytes	0644
libpq-copy.html	22442 bytes	0644
libpq-envars.html	9820 bytes	0644
libpq-events.html	23093 bytes	0644
libpq-example.html	16024 bytes	0644
libpq-exec.html	64877 bytes	0644
libpq-fastpath.html	6124 bytes	0644
libpq-ldap.html	5506 bytes	0644
libpq-misc.html	13815 bytes	0644
libpq-notice-processing.html	6284 bytes	0644
libpq-notify.html	6715 bytes	0644
libpq-pgpass.html	4861 bytes	0644
libpq-pgservice.html	3905 bytes	0644
libpq-single-row-mode.html	6353 bytes	0644
libpq-ssl.html	19972 bytes	0644
libpq-status.html	17695 bytes	0644
libpq-threading.html	5544 bytes	0644
libpq.html	7918 bytes	0644
lo-examplesect.html	8696 bytes	0644
lo-funcs.html	4640 bytes	0644
lo-implementation.html	3353 bytes	0644
lo-interfaces.html	15155 bytes	0644
lo-intro.html	3206 bytes	0644
lo.html	6627 bytes	0644
locale.html	13691 bytes	0644
locking-indexes.html	4350 bytes	0644
log-shipping-alternative.html	11057 bytes	0644
logfile-maintenance.html	7143 bytes	0644
ltree.html	27295 bytes	0644
maintenance.html	5538 bytes	0644
manage-ag-config.html	3746 bytes	0644
manage-ag-createdb.html	6310 bytes	0644
manage-ag-dropdb.html	3605 bytes	0644
manage-ag-overview.html	5144 bytes	0644
manage-ag-tablespaces.html	9250 bytes	0644
manage-ag-templatedbs.html	8162 bytes	0644
managing-databases.html	3273 bytes	0644
monitoring-locks.html	3673 bytes	0644
monitoring-ps.html	6782 bytes	0644
monitoring-stats.html	58063 bytes	0644
monitoring.html	4458 bytes	0644
multibyte.html	31965 bytes	0644
mvcc-caveats.html	4077 bytes	0644
mvcc-intro.html	4552 bytes	0644
mvcc.html	4302 bytes	0644
nls-programmer.html	10078 bytes	0644
nls-translator.html	14522 bytes	0644
nls.html	3134 bytes	0644
non-durability.html	4484 bytes	0644
notation.html	4415 bytes	0644
oid2name.html	11962 bytes	0644
overview.html	4093 bytes	0644
pageinspect.html	8117 bytes	0644
parser-stage.html	8117 bytes	0644
passwordcheck.html	4788 bytes	0644
performance-tips.html	4501 bytes	0644
perm-functions.html	3338 bytes	0644
pgarchivecleanup.html	8999 bytes	0644
pgbench.html	30833 bytes	0644
pgbuffercache.html	7715 bytes	0644
pgcrypto.html	38804 bytes	0644
pgfreespacemap.html	5230 bytes	0644
pgrowlocks.html	6078 bytes	0644
pgstandby.html	15204 bytes	0644
pgstatstatements.html	16068 bytes	0644
pgstattuple.html	9449 bytes	0644
pgtestfsync.html	5254 bytes	0644
pgtesttiming.html	12476 bytes	0644
pgtrgm.html	12333 bytes	0644
pgupgrade.html	24737 bytes	0644
planner-optimizer.html	9396 bytes	0644
planner-stats-details.html	3276 bytes	0644
planner-stats-security.html	5556 bytes	0644
planner-stats.html	9058 bytes	0644
plhandler.html	13748 bytes	0644
plperl-builtins.html	18276 bytes	0644
plperl-data.html	2878 bytes	0644
plperl-funcs.html	13369 bytes	0644
plperl-global.html	5067 bytes	0644
plperl-triggers.html	6446 bytes	0644
plperl-trusted.html	6712 bytes	0644
plperl-under-the-hood.html	8991 bytes	0644
plperl.html	4930 bytes	0644
plpgsql-control-structures.html	46183 bytes	0644
plpgsql-cursors.html	25586 bytes	0644
plpgsql-declarations.html	21746 bytes	0644
plpgsql-development-tips.html	9511 bytes	0644
plpgsql-errors-and-messages.html	10094 bytes	0644
plpgsql-expressions.html	4662 bytes	0644
plpgsql-implementation.html	18043 bytes	0644
plpgsql-overview.html	9032 bytes	0644
plpgsql-porting.html	27094 bytes	0644
plpgsql-statements.html	32221 bytes	0644
plpgsql-structure.html	8329 bytes	0644
plpgsql-trigger.html	22322 bytes	0644
plpgsql.html	6965 bytes	0644
plpython-data.html	14648 bytes	0644
plpython-database.html	15413 bytes	0644
plpython-do.html	2771 bytes	0644
plpython-envar.html	3885 bytes	0644
plpython-funcs.html	5478 bytes	0644
plpython-python23.html	7207 bytes	0644
plpython-sharing.html	3032 bytes	0644
plpython-subtransaction.html	7888 bytes	0644
plpython-trigger.html	5069 bytes	0644
plpython-util.html	5104 bytes	0644
plpython.html	6067 bytes	0644
pltcl-data.html	2906 bytes	0644
pltcl-dbaccess.html	13902 bytes	0644
pltcl-functions.html	6177 bytes	0644
pltcl-global.html	5066 bytes	0644
pltcl-overview.html	5288 bytes	0644
pltcl-procnames.html	3222 bytes	0644
pltcl-trigger.html	9452 bytes	0644
pltcl-unknown.html	5075 bytes	0644
pltcl.html	3400 bytes	0644
populate.html	17114 bytes	0644
postgres-user.html	3314 bytes	0644
preface.html	5070 bytes	0644
preventing-server-spoofing.html	4604 bytes	0644
protocol-changes.html	6650 bytes	0644
protocol-error-fields.html	6131 bytes	0644
protocol-flow.html	46202 bytes	0644
protocol-message-formats.html	40844 bytes	0644
protocol-message-types.html	4933 bytes	0644
protocol-overview.html	9670 bytes	0644
protocol-replication.html	14666 bytes	0644
protocol.html	5652 bytes	0644
queries-limit.html	5335 bytes	0644
queries-order.html	7369 bytes	0644
queries-overview.html	5068 bytes	0644
queries-select-lists.html	9308 bytes	0644
queries-table-expressions.html	39874 bytes	0644
queries-union.html	5114 bytes	0644
queries-values.html	4930 bytes	0644
queries-with.html	20880 bytes	0644
queries.html	4418 bytes	0644
query-path.html	5470 bytes	0644
querytree.html	11136 bytes	0644
rangetypes.html	22735 bytes	0644
recovery-config.html	3550 bytes	0644
recovery-target-settings.html	7762 bytes	0644
reference-client.html	6102 bytes	0644
reference-server.html	3964 bytes	0644
reference.html	23162 bytes	0644
regress-coverage.html	3325 bytes	0644
regress-evaluation.html	12487 bytes	0644
regress-run.html	13710 bytes	0644
regress-variant.html	7177 bytes	0644
regress.html	4277 bytes	0644
release-0-01.html	2555 bytes	0644
release-0-02.html	4292 bytes	0644
release-0-03.html	7798 bytes	0644
release-1-0.html	4229 bytes	0644
release-1-01.html	9346 bytes	0644
release-1-02.html	6489 bytes	0644
release-1-09.html	2525 bytes	0644
release-6-0.html	7920 bytes	0644
release-6-1-1.html	3719 bytes	0644
release-6-1.html	9025 bytes	0644
release-6-2-1.html	4405 bytes	0644
release-6-2.html	8883 bytes	0644
release-6-3-1.html	4444 bytes	0644
release-6-3-2.html	4157 bytes	0644
release-6-3.html	16311 bytes	0644
release-6-4-1.html	4061 bytes	0644
release-6-4-2.html	2908 bytes	0644
release-6-4.html	14732 bytes	0644
release-6-5-1.html	3842 bytes	0644
release-6-5-2.html	4102 bytes	0644
release-6-5-3.html	3053 bytes	0644
release-6-5.html	17387 bytes	0644
release-7-0-1.html	3920 bytes	0644
release-7-0-2.html	2887 bytes	0644
release-7-0-3.html	4656 bytes	0644
release-7-0.html	23104 bytes	0644
release-7-1-1.html	3262 bytes	0644
release-7-1-2.html	2975 bytes	0644
release-7-1-3.html	3139 bytes	0644
release-7-1.html	13017 bytes	0644
release-7-2-1.html	4011 bytes	0644
release-7-2-2.html	3793 bytes	0644
release-7-2-3.html	3364 bytes	0644
release-7-2-4.html	3587 bytes	0644
release-7-2-5.html	3746 bytes	0644
release-7-2-6.html	3624 bytes	0644
release-7-2-7.html	3726 bytes	0644
release-7-2-8.html	3948 bytes	0644
release-7-2.html	27098 bytes	0644
release-7-3-1.html	4168 bytes	0644
release-7-3-10.html	7493 bytes	0644
release-7-3-11.html	4111 bytes	0644
release-7-3-12.html	3527 bytes	0644
release-7-3-13.html	4618 bytes	0644
release-7-3-14.html	3931 bytes	0644
release-7-3-15.html	6315 bytes	0644
release-7-3-16.html	3424 bytes	0644
release-7-3-17.html	3550 bytes	0644
release-7-3-18.html	3647 bytes	0644
release-7-3-19.html	3686 bytes	0644
release-7-3-2.html	5205 bytes	0644
release-7-3-20.html	3524 bytes	0644
release-7-3-21.html	6216 bytes	0644
release-7-3-3.html	10290 bytes	0644
release-7-3-4.html	3502 bytes	0644
release-7-3-5.html	4493 bytes	0644
release-7-3-6.html	4428 bytes	0644
release-7-3-7.html	3352 bytes	0644
release-7-3-8.html	3571 bytes	0644
release-7-3-9.html	4079 bytes	0644
release-7-3.html	33053 bytes	0644
release-7-4-1.html	7116 bytes	0644
release-7-4-10.html	3806 bytes	0644
release-7-4-11.html	4857 bytes	0644
release-7-4-12.html	4221 bytes	0644
release-7-4-13.html	6961 bytes	0644
release-7-4-14.html	3673 bytes	0644
release-7-4-15.html	4270 bytes	0644
release-7-4-16.html	3972 bytes	0644
release-7-4-17.html	4013 bytes	0644
release-7-4-18.html	3927 bytes	0644
release-7-4-19.html	7242 bytes	0644
release-7-4-2.html	8260 bytes	0644
release-7-4-20.html	6605 bytes	0644
release-7-4-21.html	3922 bytes	0644
release-7-4-22.html	4071 bytes	0644
release-7-4-23.html	4423 bytes	0644
release-7-4-24.html	4289 bytes	0644
release-7-4-25.html	4506 bytes	0644
release-7-4-26.html	5455 bytes	0644
release-7-4-27.html	5164 bytes	0644
release-7-4-28.html	5629 bytes	0644
release-7-4-29.html	6960 bytes	0644
release-7-4-3.html	4615 bytes	0644
release-7-4-30.html	6211 bytes	0644
release-7-4-4.html	4085 bytes	0644
release-7-4-5.html	3194 bytes	0644
release-7-4-6.html	4731 bytes	0644
release-7-4-7.html	4274 bytes	0644
release-7-4-8.html	10156 bytes	0644
release-7-4-9.html	5118 bytes	0644
release-7-4.html	57378 bytes	0644
release-8-0-1.html	4744 bytes	0644
release-8-0-10.html	4751 bytes	0644
release-8-0-11.html	3969 bytes	0644
release-8-0-12.html	3134 bytes	0644
release-8-0-13.html	4118 bytes	0644
release-8-0-14.html	4518 bytes	0644
release-8-0-15.html	9101 bytes	0644
release-8-0-16.html	8946 bytes	0644
release-8-0-17.html	3920 bytes	0644
release-8-0-18.html	5579 bytes	0644
release-8-0-19.html	4976 bytes	0644
release-8-0-2.html	9566 bytes	0644
release-8-0-20.html	4312 bytes	0644
release-8-0-21.html	4504 bytes	0644
release-8-0-22.html	6440 bytes	0644
release-8-0-23.html	6023 bytes	0644
release-8-0-24.html	7002 bytes	0644
release-8-0-25.html	7427 bytes	0644
release-8-0-26.html	8026 bytes	0644
release-8-0-3.html	7425 bytes	0644
release-8-0-4.html	6680 bytes	0644
release-8-0-5.html	4816 bytes	0644
release-8-0-6.html	5694 bytes	0644
release-8-0-7.html	5909 bytes	0644
release-8-0-8.html	7225 bytes	0644
release-8-0-9.html	4306 bytes	0644
release-8-0.html	66818 bytes	0644
release-8-1-1.html	5459 bytes	0644
release-8-1-10.html	4781 bytes	0644
release-8-1-11.html	9946 bytes	0644
release-8-1-12.html	9341 bytes	0644
release-8-1-13.html	4292 bytes	0644
release-8-1-14.html	6901 bytes	0644
release-8-1-15.html	6274 bytes	0644
release-8-1-16.html	5278 bytes	0644
release-8-1-17.html	6035 bytes	0644
release-8-1-18.html	6442 bytes	0644
release-8-1-19.html	6612 bytes	0644
release-8-1-2.html	6335 bytes	0644
release-8-1-20.html	7298 bytes	0644
release-8-1-21.html	7213 bytes	0644
release-8-1-22.html	8324 bytes	0644
release-8-1-23.html	7933 bytes	0644
release-8-1-3.html	7026 bytes	0644
release-8-1-4.html	8873 bytes	0644
release-8-1-5.html	5479 bytes	0644
release-8-1-6.html	5337 bytes	0644
release-8-1-7.html	4558 bytes	0644
release-8-1-8.html	3116 bytes	0644
release-8-1-9.html	4388 bytes	0644
release-8-1.html	62113 bytes	0644
release-8-2-1.html	5065 bytes	0644
release-8-2-10.html	8180 bytes	0644
release-8-2-11.html	7147 bytes	0644
release-8-2-12.html	6748 bytes	0644
release-8-2-13.html	7348 bytes	0644
release-8-2-14.html	7876 bytes	0644
release-8-2-15.html	8155 bytes	0644
release-8-2-16.html	9293 bytes	0644
release-8-2-17.html	8214 bytes	0644
release-8-2-18.html	10277 bytes	0644
release-8-2-19.html	8589 bytes	0644
release-8-2-2.html	5802 bytes	0644
release-8-2-20.html	6244 bytes	0644
release-8-2-21.html	5593 bytes	0644
release-8-2-22.html	9617 bytes	0644
release-8-2-23.html	9559 bytes	0644
release-8-2-3.html	3095 bytes	0644
release-8-2-4.html	5428 bytes	0644
release-8-2-5.html	5995 bytes	0644
release-8-2-6.html	10551 bytes	0644
release-8-2-7.html	9311 bytes	0644
release-8-2-8.html	7521 bytes	0644
release-8-2-9.html	4281 bytes	0644
release-8-2.html	69398 bytes	0644
release-8-3-1.html	10585 bytes	0644
release-8-3-10.html	10725 bytes	0644
release-8-3-11.html	8963 bytes	0644
release-8-3-12.html	12119 bytes	0644
release-8-3-13.html	9506 bytes	0644
release-8-3-14.html	6242 bytes	0644
release-8-3-15.html	6381 bytes	0644
release-8-3-16.html	11015 bytes	0644
release-8-3-17.html	10590 bytes	0644
release-8-3-18.html	11265 bytes	0644
release-8-3-19.html	8466 bytes	0644
release-8-3-2.html	12203 bytes	0644
release-8-3-20.html	9251 bytes	0644
release-8-3-21.html	5034 bytes	0644
release-8-3-22.html	10585 bytes	0644
release-8-3-23.html	6284 bytes	0644
release-8-3-3.html	4275 bytes	0644
release-8-3-4.html	11273 bytes	0644
release-8-3-5.html	8689 bytes	0644
release-8-3-6.html	9197 bytes	0644
release-8-3-7.html	9729 bytes	0644
release-8-3-8.html	9260 bytes	0644
release-8-3-9.html	10206 bytes	0644
release-8-3.html	69773 bytes	0644
release-8-4-1.html	9563 bytes	0644
release-8-4-10.html	11932 bytes	0644
release-8-4-11.html	13787 bytes	0644
release-8-4-12.html	9987 bytes	0644
release-8-4-13.html	9714 bytes	0644
release-8-4-14.html	5117 bytes	0644
release-8-4-15.html	10626 bytes	0644
release-8-4-16.html	7329 bytes	0644
release-8-4-17.html	9572 bytes	0644
release-8-4-18.html	7048 bytes	0644
release-8-4-19.html	7780 bytes	0644
release-8-4-2.html	15697 bytes	0644
release-8-4-20.html	16258 bytes	0644
release-8-4-21.html	5450 bytes	0644
release-8-4-22.html	11306 bytes	0644
release-8-4-3.html	13928 bytes	0644
release-8-4-4.html	10736 bytes	0644
release-8-4-5.html	15933 bytes	0644
release-8-4-6.html	10430 bytes	0644
release-8-4-7.html	6220 bytes	0644
release-8-4-8.html	8850 bytes	0644
release-8-4-9.html	14528 bytes	0644
release-8-4.html	87976 bytes	0644
release-9-0-1.html	5946 bytes	0644
release-9-0-10.html	5693 bytes	0644
release-9-0-11.html	12666 bytes	0644
release-9-0-12.html	8824 bytes	0644
release-9-0-13.html	11671 bytes	0644
release-9-0-14.html	8759 bytes	0644
release-9-0-15.html	9147 bytes	0644
release-9-0-16.html	17408 bytes	0644
release-9-0-17.html	6335 bytes	0644
release-9-0-18.html	11879 bytes	0644
release-9-0-19.html	26610 bytes	0644
release-9-0-2.html	13636 bytes	0644
release-9-0-20.html	15836 bytes	0644
release-9-0-21.html	5166 bytes	0644
release-9-0-22.html	4321 bytes	0644
release-9-0-23.html	16158 bytes	0644
release-9-0-3.html	7256 bytes	0644
release-9-0-4.html	11345 bytes	0644
release-9-0-5.html	17915 bytes	0644
release-9-0-6.html	13426 bytes	0644
release-9-0-7.html	18091 bytes	0644
release-9-0-8.html	10993 bytes	0644
release-9-0-9.html	11743 bytes	0644
release-9-0.html	96127 bytes	0644
release-9-1-1.html	3670 bytes	0644
release-9-1-10.html	10352 bytes	0644
release-9-1-11.html	9584 bytes	0644
release-9-1-12.html	18554 bytes	0644
release-9-1-13.html	6685 bytes	0644
release-9-1-14.html	13036 bytes	0644
release-9-1-15.html	28969 bytes	0644
release-9-1-16.html	19119 bytes	0644
release-9-1-17.html	4947 bytes	0644
release-9-1-18.html	4102 bytes	0644
release-9-1-19.html	17617 bytes	0644
release-9-1-2.html	21571 bytes	0644
release-9-1-20.html	17541 bytes	0644
release-9-1-21.html	7601 bytes	0644
release-9-1-22.html	7258 bytes	0644
release-9-1-23.html	12653 bytes	0644
release-9-1-24.html	8731 bytes	0644
release-9-1-3.html	21153 bytes	0644
release-9-1-4.html	16018 bytes	0644
release-9-1-5.html	14042 bytes	0644
release-9-1-6.html	9521 bytes	0644
release-9-1-7.html	14941 bytes	0644
release-9-1-8.html	10154 bytes	0644
release-9-1-9.html	12679 bytes	0644
release-9-1.html	78963 bytes	0644
release-9-2-1.html	7111 bytes	0644
release-9-2-10.html	32368 bytes	0644
release-9-2-11.html	20298 bytes	0644
release-9-2-12.html	5130 bytes	0644
release-9-2-13.html	4102 bytes	0644
release-9-2-14.html	18386 bytes	0644
release-9-2-15.html	18605 bytes	0644
release-9-2-16.html	7598 bytes	0644
release-9-2-17.html	8195 bytes	0644
release-9-2-18.html	12718 bytes	0644
release-9-2-19.html	10514 bytes	0644
release-9-2-2.html	23001 bytes	0644
release-9-2-20.html	13332 bytes	0644
release-9-2-21.html	14198 bytes	0644
release-9-2-22.html	15865 bytes	0644
release-9-2-23.html	8126 bytes	0644
release-9-2-24.html	7877 bytes	0644
release-9-2-3.html	13373 bytes	0644
release-9-2-4.html	14800 bytes	0644
release-9-2-5.html	12005 bytes	0644
release-9-2-6.html	11684 bytes	0644
release-9-2-7.html	20022 bytes	0644
release-9-2-8.html	7375 bytes	0644
release-9-2-9.html	15615 bytes	0644
release-9-2.html	79519 bytes	0644
release.html	22882 bytes	0644
resources.html	4226 bytes	0644
role-attributes.html	7855 bytes	0644
role-membership.html	8390 bytes	0644
role-removal.html	5303 bytes	0644
routine-reindex.html	3628 bytes	0644
routine-vacuuming.html	38023 bytes	0644
row-estimation-examples.html	20767 bytes	0644
rowtypes.html	23412 bytes	0644
rule-system.html	4117 bytes	0644
rules-privileges.html	11663 bytes	0644
rules-status.html	4512 bytes	0644
rules-triggers.html	9476 bytes	0644
rules-update.html	32615 bytes	0644
rules-views.html	26888 bytes	0644
rules.html	4948 bytes	0644
runtime-config-autovacuum.html	10974 bytes	0644
runtime-config-client.html	32815 bytes	0644
runtime-config-compatible.html	14827 bytes	0644
runtime-config-connection.html	23478 bytes	0644
runtime-config-custom.html	3548 bytes	0644
runtime-config-developer.html	14070 bytes	0644
runtime-config-error-handling.html	3570 bytes	0644
runtime-config-file-locations.html	6977 bytes	0644
runtime-config-locks.html	7634 bytes	0644
runtime-config-logging.html	45446 bytes	0644
runtime-config-preset.html	8710 bytes	0644
runtime-config-query.html	24950 bytes	0644
runtime-config-replication.html	18294 bytes	0644
runtime-config-resource.html	27901 bytes	0644
runtime-config-short.html	6683 bytes	0644
runtime-config-statistics.html	8616 bytes	0644
runtime-config-wal.html	27093 bytes	0644
runtime-config.html	8249 bytes	0644
runtime.html	5241 bytes	0644
seg.html	15470 bytes	0644
sepgsql.html	30829 bytes	0644
server-programming.html	9618 bytes	0644
server-shutdown.html	6469 bytes	0644
server-start.html	14217 bytes	0644
source-format.html	5133 bytes	0644
source.html	4071 bytes	0644
sourcerepo.html	3411 bytes	0644
spgist-examples.html	2703 bytes	0644
spgist-extensibility.html	31282 bytes	0644
spgist-implementation.html	8098 bytes	0644
spgist-intro.html	4323 bytes	0644
spgist.html	2966 bytes	0644
spi-examples.html	6217 bytes	0644
spi-interface-support.html	3770 bytes	0644
spi-interface.html	5998 bytes	0644
spi-memory.html	7089 bytes	0644
spi-realloc.html	3627 bytes	0644
spi-spi-connect.html	4052 bytes	0644
spi-spi-copytuple.html	3453 bytes	0644
spi-spi-cursor-close.html	3336 bytes	0644
spi-spi-cursor-fetch.html	4110 bytes	0644
spi-spi-cursor-find.html	3464 bytes	0644
spi-spi-cursor-move.html	3890 bytes	0644
spi-spi-cursor-open-with-args.html	6178 bytes	0644
spi-spi-cursor-open-with-paramlist.html	5035 bytes	0644
spi-spi-cursor-open.html	5732 bytes	0644
spi-spi-exec.html	3591 bytes	0644
spi-spi-execp.html	4866 bytes	0644
spi-spi-execute-plan-with-paramlist.html	4893 bytes	0644
spi-spi-execute-plan.html	5901 bytes	0644
spi-spi-execute-with-args.html	6221 bytes	0644
spi-spi-execute.html	12598 bytes	0644
spi-spi-finish.html	3655 bytes	0644
spi-spi-fname.html	3767 bytes	0644
spi-spi-fnumber.html	3936 bytes	0644
spi-spi-freeplan.html	3505 bytes	0644
spi-spi-freetuple.html	3277 bytes	0644
spi-spi-freetupletable.html	3628 bytes	0644
spi-spi-getargcount.html	3698 bytes	0644
spi-spi-getargtypeid.html	4141 bytes	0644
spi-spi-getbinval.html	4287 bytes	0644
spi-spi-getnspname.html	3467 bytes	0644
spi-spi-getrelname.html	3351 bytes	0644
spi-spi-gettype.html	3714 bytes	0644
spi-spi-gettypeid.html	3718 bytes	0644
spi-spi-getvalue.html	4166 bytes	0644
spi-spi-is-cursor-plan.html	4560 bytes	0644
spi-spi-keepplan.html	3884 bytes	0644
spi-spi-modifytuple.html	5631 bytes	0644
spi-spi-palloc.html	3157 bytes	0644
spi-spi-pfree.html	3275 bytes	0644
spi-spi-pop.html	2743 bytes	0644
spi-spi-prepare-cursor.html	5055 bytes	0644
spi-spi-prepare-params.html	4412 bytes	0644
spi-spi-prepare.html	7661 bytes	0644
spi-spi-push.html	3737 bytes	0644
spi-spi-returntuple.html	4097 bytes	0644
spi-spi-saveplan.html	4576 bytes	0644
spi-spi-scroll-cursor-fetch.html	4809 bytes	0644
spi-spi-scroll-cursor-move.html	4899 bytes	0644
spi-visibility.html	4152 bytes	0644
spi.html	10843 bytes	0644
sql-abort.html	4177 bytes	0644
sql-alteraggregate.html	6111 bytes	0644
sql-altercollation.html	5084 bytes	0644
sql-alterconversion.html	5170 bytes	0644
sql-alterdatabase.html	8778 bytes	0644
sql-alterdefaultprivileges.html	9407 bytes	0644
sql-alterdomain.html	11113 bytes	0644
sql-alterextension.html	11745 bytes	0644
sql-alterforeigndatawrapper.html	7378 bytes	0644
sql-alterforeigntable.html	12707 bytes	0644
sql-alterfunction.html	12845 bytes	0644
sql-altergroup.html	5239 bytes	0644
sql-alterindex.html	7655 bytes	0644
sql-alterlanguage.html	4022 bytes	0644
sql-alterlargeobject.html	3730 bytes	0644
sql-alteropclass.html	5114 bytes	0644
sql-alteroperator.html	5435 bytes	0644
sql-alteropfamily.html	13564 bytes	0644
sql-alterrole.html	13028 bytes	0644
sql-alterschema.html	4314 bytes	0644
sql-altersequence.html	13031 bytes	0644
sql-alterserver.html	5928 bytes	0644
sql-altertable.html	43543 bytes	0644
sql-altertablespace.html	5866 bytes	0644
sql-altertrigger.html	4647 bytes	0644
sql-altertsconfig.html	8126 bytes	0644
sql-altertsdictionary.html	6539 bytes	0644
sql-altertsparser.html	4257 bytes	0644
sql-altertstemplate.html	4223 bytes	0644
sql-altertype.html	11193 bytes	0644
sql-alteruser.html	4720 bytes	0644
sql-alterusermapping.html	5714 bytes	0644
sql-alterview.html	6969 bytes	0644
sql-analyze.html	10674 bytes	0644
sql-begin.html	6695 bytes	0644
sql-checkpoint.html	3758 bytes	0644
sql-close.html	4984 bytes	0644
sql-cluster.html	9404 bytes	0644
sql-commands.html	18810 bytes	0644
sql-comment.html	13799 bytes	0644
sql-commit-prepared.html	4516 bytes	0644
sql-commit.html	3992 bytes	0644
sql-copy.html	37443 bytes	0644
sql-createaggregate.html	13829 bytes	0644
sql-createcast.html	19632 bytes	0644
sql-createcollation.html	6739 bytes	0644
sql-createconversion.html	6538 bytes	0644
sql-createdatabase.html	12133 bytes	0644
sql-createdomain.html	8544 bytes	0644
sql-createextension.html	9083 bytes	0644
sql-createforeigndatawrapper.html	8059 bytes	0644
sql-createforeigntable.html	7718 bytes	0644
sql-createfunction.html	31076 bytes	0644
sql-creategroup.html	4012 bytes	0644
sql-createindex.html	25934 bytes	0644
sql-createlanguage.html	14888 bytes	0644
sql-createopclass.html	12676 bytes	0644
sql-createoperator.html	10688 bytes	0644
sql-createopfamily.html	5626 bytes	0644
sql-createrole.html	19325 bytes	0644
sql-createrule.html	12656 bytes	0644
sql-createschema.html	8319 bytes	0644
sql-createsequence.html	13862 bytes	0644
sql-createserver.html	6251 bytes	0644
sql-createtable.html	59172 bytes	0644
sql-createtableas.html	12772 bytes	0644
sql-createtablespace.html	6104 bytes	0644
sql-createtrigger.html	23175 bytes	0644
sql-createtsconfig.html	5352 bytes	0644
sql-createtsdictionary.html	5533 bytes	0644
sql-createtsparser.html	5947 bytes	0644
sql-createtstemplate.html	5437 bytes	0644
sql-createtype.html	39460 bytes	0644
sql-createuser.html	4524 bytes	0644
sql-createusermapping.html	5503 bytes	0644
sql-createview.html	10556 bytes	0644
sql-deallocate.html	3785 bytes	0644
sql-declare.html	15400 bytes	0644
sql-delete.html	11777 bytes	0644
sql-discard.html	4309 bytes	0644
sql-do.html	5204 bytes	0644
sql-drop-owned.html	5058 bytes	0644
sql-dropaggregate.html	4561 bytes	0644
sql-dropcast.html	4344 bytes	0644
sql-dropcollation.html	4409 bytes	0644
sql-dropconversion.html	4437 bytes	0644
sql-dropdatabase.html	4344 bytes	0644
sql-dropdomain.html	4257 bytes	0644
sql-dropextension.html	4785 bytes	0644
sql-dropforeigndatawrapper.html	4526 bytes	0644
sql-dropforeigntable.html	4560 bytes	0644
sql-dropfunction.html	5838 bytes	0644
sql-dropgroup.html	3047 bytes	0644
sql-dropindex.html	5182 bytes	0644
sql-droplanguage.html	4841 bytes	0644
sql-dropopclass.html	5678 bytes	0644
sql-dropoperator.html	5222 bytes	0644
sql-dropopfamily.html	5279 bytes	0644
sql-droprole.html	5158 bytes	0644
sql-droprule.html	4151 bytes	0644
sql-dropschema.html	4529 bytes	0644
sql-dropsequence.html	4367 bytes	0644
sql-dropserver.html	4265 bytes	0644
sql-droptable.html	5028 bytes	0644
sql-droptablespace.html	4585 bytes	0644
sql-droptrigger.html	4711 bytes	0644
sql-droptsconfig.html	4772 bytes	0644
sql-droptsdictionary.html	4689 bytes	0644
sql-droptsparser.html	4595 bytes	0644
sql-droptstemplate.html	4567 bytes	0644
sql-droptype.html	4463 bytes	0644
sql-dropuser.html	3181 bytes	0644
sql-dropusermapping.html	4679 bytes	0644
sql-dropview.html	4262 bytes	0644
sql-end.html	4157 bytes	0644
sql-execute.html	5073 bytes	0644
sql-explain.html	17094 bytes	0644
sql-expressions.html	47801 bytes	0644
sql-fetch.html	14251 bytes	0644
sql-grant.html	29245 bytes	0644
sql-insert.html	12860 bytes	0644
sql-keywords-appendix.html	106534 bytes	0644
sql-listen.html	5903 bytes	0644
sql-load.html	4207 bytes	0644
sql-lock.html	11869 bytes	0644
sql-move.html	4984 bytes	0644
sql-notify.html	10948 bytes	0644
sql-prepare-transaction.html	8640 bytes	0644
sql-prepare.html	9181 bytes	0644
sql-reassign-owned.html	5344 bytes	0644
sql-reindex.html	11103 bytes	0644
sql-release-savepoint.html	5005 bytes	0644
sql-reset.html	4993 bytes	0644
sql-revoke.html	14879 bytes	0644
sql-rollback-prepared.html	4627 bytes	0644
sql-rollback-to.html	6401 bytes	0644
sql-rollback.html	3996 bytes	0644
sql-savepoint.html	5605 bytes	0644
sql-security-label.html	8879 bytes	0644
sql-select.html	79544 bytes	0644
sql-selectinto.html	7634 bytes	0644
sql-set-constraints.html	7068 bytes	0644
sql-set-role.html	6915 bytes	0644
sql-set-session-authorization.html	6062 bytes	0644
sql-set-transaction.html	12696 bytes	0644
sql-set.html	12057 bytes	0644
sql-show.html	6851 bytes	0644
sql-start-transaction.html	4983 bytes	0644
sql-syntax-calling-funcs.html	8080 bytes	0644
sql-syntax-lexical.html	43370 bytes	0644
sql-syntax.html	5430 bytes	0644
sql-truncate.html	9364 bytes	0644
sql-unlisten.html	4923 bytes	0644
sql-update.html	15669 bytes	0644
sql-vacuum.html	10669 bytes	0644
sql-values.html	10640 bytes	0644
sql.html	13569 bytes	0644
ssh-tunnels.html	6263 bytes	0644
ssl-tcp.html	13477 bytes	0644
sslinfo.html	7594 bytes	0644
standby-settings.html	5427 bytes	0644
storage-file-layout.html	12936 bytes	0644
storage-fsm.html	3821 bytes	0644
storage-init.html	2760 bytes	0644
storage-page-layout.html	13891 bytes	0644
storage-toast.html	11478 bytes	0644
storage-vm.html	3540 bytes	0644
storage.html	2952 bytes	0644
stylesheet.css	1538 bytes	0644
supported-platforms.html	5042 bytes	0644
tablefunc.html	32193 bytes	0644
tcn.html	4974 bytes	0644
test-parser.html	4530 bytes	0644
textsearch-configuration.html	6257 bytes	0644
textsearch-controls.html	26966 bytes	0644
textsearch-debugging.html	17227 bytes	0644
textsearch-dictionaries.html	31261 bytes	0644
textsearch-features.html	21310 bytes	0644
textsearch-indexes.html	7387 bytes	0644
textsearch-intro.html	18453 bytes	0644
textsearch-limitations.html	3859 bytes	0644
textsearch-migration.html	5034 bytes	0644
textsearch-parsers.html	9210 bytes	0644
textsearch-psql.html	9345 bytes	0644
textsearch-tables.html	9750 bytes	0644
textsearch.html	5878 bytes	0644
transaction-iso.html	27240 bytes	0644
trigger-datachanges.html	5072 bytes	0644
trigger-definition.html	15507 bytes	0644
trigger-example.html	7749 bytes	0644
trigger-interface.html	10719 bytes	0644
triggers.html	3798 bytes	0644
tsearch2.html	9950 bytes	0644
tutorial-accessdb.html	7040 bytes	0644
tutorial-advanced-intro.html	3341 bytes	0644
tutorial-advanced.html	2856 bytes	0644
tutorial-agg.html	7594 bytes	0644
tutorial-arch.html	4852 bytes	0644
tutorial-concepts.html	3839 bytes	0644
tutorial-conclusion.html	2849 bytes	0644
tutorial-createdb.html	9200 bytes	0644
tutorial-delete.html	3517 bytes	0644
tutorial-fk.html	4422 bytes	0644
tutorial-inheritance.html	6137 bytes	0644
tutorial-install.html	4522 bytes	0644
tutorial-join.html	9685 bytes	0644
tutorial-populate.html	4839 bytes	0644
tutorial-select.html	8033 bytes	0644
tutorial-sql-intro.html	4904 bytes	0644
tutorial-sql.html	3060 bytes	0644
tutorial-start.html	2629 bytes	0644
tutorial-table.html	5704 bytes	0644
tutorial-transactions.html	9948 bytes	0644
tutorial-update.html	3159 bytes	0644
tutorial-views.html	3375 bytes	0644
tutorial-window.html	12481 bytes	0644
tutorial.html	5209 bytes	0644
typeconv-func.html	12170 bytes	0644
typeconv-oper.html	14907 bytes	0644
typeconv-overview.html	8301 bytes	0644
typeconv-query.html	5450 bytes	0644
typeconv-union-case.html	6612 bytes	0644
typeconv.html	3721 bytes	0644
unaccent.html	6742 bytes	0644
unsupported-features-sql-standard.html	35115 bytes	0644
upgrading.html	12795 bytes	0644
user-manag.html	3983 bytes	0644
using-explain.html	41824 bytes	0644
uuid-ossp.html	7228 bytes	0644
vacuumlo.html	7548 bytes	0644
view-pg-available-extension-versions.html	4642 bytes	0644
view-pg-available-extensions.html	3944 bytes	0644
view-pg-cursors.html	5669 bytes	0644
view-pg-group.html	3897 bytes	0644
view-pg-indexes.html	4155 bytes	0644
view-pg-locks.html	14444 bytes	0644
view-pg-prepared-statements.html	5060 bytes	0644
view-pg-prepared-xacts.html	4912 bytes	0644
view-pg-roles.html	6073 bytes	0644
view-pg-rules.html	3999 bytes	0644
view-pg-seclabels.html	5123 bytes	0644
view-pg-settings.html	10600 bytes	0644
view-pg-shadow.html	5381 bytes	0644
view-pg-stats.html	8887 bytes	0644
view-pg-tables.html	4836 bytes	0644
view-pg-timezone-abbrevs.html	3860 bytes	0644
view-pg-timezone-names.html	4177 bytes	0644
view-pg-user-mappings.html	5165 bytes	0644
view-pg-user.html	4517 bytes	0644
view-pg-views.html	3853 bytes	0644
views-overview.html	6542 bytes	0644
wal-async-commit.html	9016 bytes	0644
wal-configuration.html	14960 bytes	0644
wal-internals.html	6151 bytes	0644
wal-intro.html	5534 bytes	0644
wal-reliability.html	11479 bytes	0644
wal.html	2928 bytes	0644
warm-standby-failover.html	6102 bytes	0644
warm-standby.html	34646 bytes	0644
xaggr.html	9902 bytes	0644
xfunc-c.html	78520 bytes	0644
xfunc-internal.html	4004 bytes	0644
xfunc-overload.html	5911 bytes	0644
xfunc-pl.html	2991 bytes	0644
xfunc-sql.html	38027 bytes	0644
xfunc-volatility.html	9839 bytes	0644
xfunc.html	4518 bytes	0644
xindex.html	44593 bytes	0644
xml2.html	16900 bytes	0644
xoper-optimization.html	23144 bytes	0644
xoper.html	4835 bytes	0644
xplang-install.html	11127 bytes	0644
xplang.html	4235 bytes	0644
xtypes.html	12114 bytes	0644