Gecko [ finalhopeacademy.com ]

/ usr / share / doc / postgresql-9.2.24 / html / [ HOME SHELL ]

Name	Size	Permission
LEGALNOTICE.html	2.62 KB	-rw-r--r--
acronyms.html	15.9 KB	-rw-r--r--
admin.html	12.27 KB	-rw-r--r--
adminpack.html	7.7 KB	-rw-r--r--
app-clusterdb.html	10.35 KB	-rw-r--r--
app-createdb.html	12.55 KB	-rw-r--r--
app-createlang.html	9.67 KB	-rw-r--r--
app-createuser.html	15.27 KB	-rw-r--r--
app-dropdb.html	9.42 KB	-rw-r--r--
app-droplang.html	9.41 KB	-rw-r--r--
app-dropuser.html	9.37 KB	-rw-r--r--
app-ecpg.html	8.51 KB	-rw-r--r--
app-initdb.html	15.04 KB	-rw-r--r--
app-pg-ctl.html	21.93 KB	-rw-r--r--
app-pg-dumpall.html	20.22 KB	-rw-r--r--
app-pgbasebackup.html	19.37 KB	-rw-r--r--
app-pgconfig.html	10.83 KB	-rw-r--r--
app-pgcontroldata.html	3.89 KB	-rw-r--r--
app-pgdump.html	42.93 KB	-rw-r--r--
app-pgreceivexlog.html	10.8 KB	-rw-r--r--
app-pgresetxlog.html	11.29 KB	-rw-r--r--
app-pgrestore.html	29.56 KB	-rw-r--r--
app-postgres.html	31.08 KB	-rw-r--r--
app-postmaster.html	2.93 KB	-rw-r--r--
app-psql.html	135.62 KB	-rw-r--r--
app-reindexdb.html	11.02 KB	-rw-r--r--
app-vacuumdb.html	12.32 KB	-rw-r--r--
appendixes.html	25.71 KB	-rw-r--r--
applevel-consistency.html	10.07 KB	-rw-r--r--
archive-recovery-settings.html	7.17 KB	-rw-r--r--
arrays.html	27.42 KB	-rw-r--r--
auth-delay.html	3.69 KB	-rw-r--r--
auth-methods.html	35.35 KB	-rw-r--r--
auth-pg-hba-conf.html	29.06 KB	-rw-r--r--
auth-username-maps.html	8.4 KB	-rw-r--r--
auto-explain.html	9.66 KB	-rw-r--r--
backup-dump.html	15.55 KB	-rw-r--r--
backup-file.html	7.81 KB	-rw-r--r--
backup.html	4.38 KB	-rw-r--r--
biblio.html	11.28 KB	-rw-r--r--
bki-commands.html	9.42 KB	-rw-r--r--
bki-example.html	2.98 KB	-rw-r--r--
bki-format.html	3.38 KB	-rw-r--r--
bki-structure.html	4.22 KB	-rw-r--r--
bki.html	4.23 KB	-rw-r--r--
bookindex.html	237.47 KB	-rw-r--r--
btree-gin.html	4.49 KB	-rw-r--r--
btree-gist.html	6.72 KB	-rw-r--r--
bug-reporting.html	18.21 KB	-rw-r--r--
catalog-pg-aggregate.html	5.37 KB	-rw-r--r--
catalog-pg-am.html	10.3 KB	-rw-r--r--
catalog-pg-amop.html	7.42 KB	-rw-r--r--
catalog-pg-amproc.html	4.77 KB	-rw-r--r--
catalog-pg-attrdef.html	4.26 KB	-rw-r--r--
catalog-pg-attribute.html	10.05 KB	-rw-r--r--
catalog-pg-auth-members.html	4.16 KB	-rw-r--r--
catalog-pg-authid.html	6.66 KB	-rw-r--r--
catalog-pg-cast.html	6.79 KB	-rw-r--r--
catalog-pg-class.html	12.36 KB	-rw-r--r--
catalog-pg-collation.html	5.76 KB	-rw-r--r--
catalog-pg-constraint.html	11.31 KB	-rw-r--r--
catalog-pg-conversion.html	4.33 KB	-rw-r--r--
catalog-pg-database.html	6.86 KB	-rw-r--r--
catalog-pg-db-role-setting.htm...	3.97 KB	-rw-r--r--
catalog-pg-default-acl.html	5.14 KB	-rw-r--r--
catalog-pg-depend.html	8.43 KB	-rw-r--r--
catalog-pg-description.html	4.37 KB	-rw-r--r--
catalog-pg-enum.html	4.61 KB	-rw-r--r--
catalog-pg-extension.html	5.16 KB	-rw-r--r--
catalog-pg-foreign-data-wrappe...	4.83 KB	-rw-r--r--
catalog-pg-foreign-server.html	4.58 KB	-rw-r--r--
catalog-pg-foreign-table.html	3.94 KB	-rw-r--r--
catalog-pg-index.html	8.66 KB	-rw-r--r--
catalog-pg-inherits.html	3.8 KB	-rw-r--r--
catalog-pg-language.html	5.81 KB	-rw-r--r--
catalog-pg-largeobject-metadat...	3.54 KB	-rw-r--r--
catalog-pg-largeobject.html	5.03 KB	-rw-r--r--
catalog-pg-namespace.html	3.66 KB	-rw-r--r--
catalog-pg-opclass.html	5.73 KB	-rw-r--r--
catalog-pg-operator.html	6.49 KB	-rw-r--r--
catalog-pg-opfamily.html	4.7 KB	-rw-r--r--
catalog-pg-pltemplate.html	5.24 KB	-rw-r--r--
catalog-pg-proc.html	13.09 KB	-rw-r--r--
catalog-pg-range.html	5.06 KB	-rw-r--r--
catalog-pg-rewrite.html	5.26 KB	-rw-r--r--
catalog-pg-seclabel.html	4.41 KB	-rw-r--r--
catalog-pg-shdepend.html	6.88 KB	-rw-r--r--
catalog-pg-shdescription.html	4.15 KB	-rw-r--r--
catalog-pg-shseclabel.html	4.3 KB	-rw-r--r--
catalog-pg-statistic.html	9.31 KB	-rw-r--r--
catalog-pg-tablespace.html	4.06 KB	-rw-r--r--
catalog-pg-trigger.html	8.09 KB	-rw-r--r--
catalog-pg-ts-config-map.html	4.09 KB	-rw-r--r--
catalog-pg-ts-config.html	4.38 KB	-rw-r--r--
catalog-pg-ts-dict.html	4.61 KB	-rw-r--r--
catalog-pg-ts-parser.html	4.96 KB	-rw-r--r--
catalog-pg-ts-template.html	4.16 KB	-rw-r--r--
catalog-pg-type.html	19.44 KB	-rw-r--r--
catalog-pg-user-mapping.html	3.76 KB	-rw-r--r--
catalogs-overview.html	10.19 KB	-rw-r--r--
catalogs.html	10.14 KB	-rw-r--r--
charset.html	4.06 KB	-rw-r--r--
chkpass.html	4.29 KB	-rw-r--r--
citext.html	10.89 KB	-rw-r--r--
client-authentication-problems...	4.13 KB	-rw-r--r--
client-authentication.html	5.78 KB	-rw-r--r--
client-interfaces.html	13.4 KB	-rw-r--r--
collation.html	13.89 KB	-rw-r--r--
config-setting.html	10.88 KB	-rw-r--r--
connect-estab.html	4.21 KB	-rw-r--r--
continuous-archiving.html	48.66 KB	-rw-r--r--
contrib-dblink-build-sql-delet...	5.32 KB	-rw-r--r--
contrib-dblink-build-sql-inser...	5.91 KB	-rw-r--r--
contrib-dblink-build-sql-updat...	6.13 KB	-rw-r--r--
contrib-dblink-cancel-query.ht...	3.73 KB	-rw-r--r--
contrib-dblink-close.html	4.54 KB	-rw-r--r--
contrib-dblink-connect-u.html	4.38 KB	-rw-r--r--
contrib-dblink-connect.html	7.15 KB	-rw-r--r--
contrib-dblink-disconnect.html	3.63 KB	-rw-r--r--
contrib-dblink-error-message.h...	3.43 KB	-rw-r--r--
contrib-dblink-exec.html	5.34 KB	-rw-r--r--
contrib-dblink-fetch.html	5.84 KB	-rw-r--r--
contrib-dblink-function.html	8.43 KB	-rw-r--r--
contrib-dblink-get-connections...	3.13 KB	-rw-r--r--
contrib-dblink-get-notify.html	4.07 KB	-rw-r--r--
contrib-dblink-get-pkey.html	4.39 KB	-rw-r--r--
contrib-dblink-get-result.html	6.8 KB	-rw-r--r--
contrib-dblink-is-busy.html	3.41 KB	-rw-r--r--
contrib-dblink-open.html	5.34 KB	-rw-r--r--
contrib-dblink-send-query.html	4.07 KB	-rw-r--r--
contrib-prog-client.html	3.35 KB	-rw-r--r--
contrib-prog-server.html	3.75 KB	-rw-r--r--
contrib-prog.html	3.24 KB	-rw-r--r--
contrib-spi.html	10.97 KB	-rw-r--r--
contrib.html	8.7 KB	-rw-r--r--
creating-cluster.html	12.17 KB	-rw-r--r--
cube.html	15.57 KB	-rw-r--r--
database-roles.html	5.95 KB	-rw-r--r--
datatype-binary.html	12.59 KB	-rw-r--r--
datatype-bit.html	4.98 KB	-rw-r--r--
datatype-boolean.html	5.14 KB	-rw-r--r--
datatype-character.html	11.61 KB	-rw-r--r--
datatype-datetime.html	49.57 KB	-rw-r--r--
datatype-enum.html	6.28 KB	-rw-r--r--
datatype-geometric.html	12.21 KB	-rw-r--r--
datatype-json.html	3.36 KB	-rw-r--r--
datatype-money.html	5.35 KB	-rw-r--r--
datatype-net-types.html	10.18 KB	-rw-r--r--
datatype-numeric.html	21.83 KB	-rw-r--r--
datatype-oid.html	9.46 KB	-rw-r--r--
datatype-pseudo.html	7.11 KB	-rw-r--r--
datatype-textsearch.html	9.8 KB	-rw-r--r--
datatype-uuid.html	4.45 KB	-rw-r--r--
datatype-xml.html	11.07 KB	-rw-r--r--
datatype.html	16.22 KB	-rw-r--r--
datetime-appendix.html	3.44 KB	-rw-r--r--
datetime-config-files.html	8.77 KB	-rw-r--r--
datetime-input-rules.html	6.6 KB	-rw-r--r--
datetime-keywords.html	4.98 KB	-rw-r--r--
datetime-units-history.html	7.46 KB	-rw-r--r--
dblink.html	5.2 KB	-rw-r--r--
ddl-alter.html	10.25 KB	-rw-r--r--
ddl-basics.html	7.63 KB	-rw-r--r--
ddl-constraints.html	22.26 KB	-rw-r--r--
ddl-default.html	4.43 KB	-rw-r--r--
ddl-depend.html	6.35 KB	-rw-r--r--
ddl-foreign-data.html	4.38 KB	-rw-r--r--
ddl-inherit.html	14.95 KB	-rw-r--r--
ddl-others.html	3.01 KB	-rw-r--r--
ddl-partitioning.html	27.11 KB	-rw-r--r--
ddl-priv.html	5.92 KB	-rw-r--r--
ddl-schemas.html	17.62 KB	-rw-r--r--
ddl-system-columns.html	7.86 KB	-rw-r--r--
ddl.html	6.23 KB	-rw-r--r--
dict-int.html	4.68 KB	-rw-r--r--
dict-xsyn.html	6.33 KB	-rw-r--r--
different-replication-solution...	14.45 KB	-rw-r--r--
disk-full.html	3.43 KB	-rw-r--r--
disk-usage.html	5.53 KB	-rw-r--r--
diskusage.html	2.61 KB	-rw-r--r--
dml-delete.html	3.48 KB	-rw-r--r--
dml-insert.html	5.67 KB	-rw-r--r--
dml-returning.html	4.98 KB	-rw-r--r--
dml-update.html	5.43 KB	-rw-r--r--
dml.html	2.88 KB	-rw-r--r--
docguide-authoring.html	6.6 KB	-rw-r--r--
docguide-build.html	14.92 KB	-rw-r--r--
docguide-docbook.html	3.76 KB	-rw-r--r--
docguide-style.html	7.25 KB	-rw-r--r--
docguide-toolsets.html	20.2 KB	-rw-r--r--
docguide.html	3.54 KB	-rw-r--r--
dummy-seclabel.html	4.26 KB	-rw-r--r--
dynamic-trace.html	26.6 KB	-rw-r--r--
earthdistance.html	8.6 KB	-rw-r--r--
ecpg-commands.html	9.3 KB	-rw-r--r--
ecpg-concept.html	4.86 KB	-rw-r--r--
ecpg-connect.html	10.57 KB	-rw-r--r--
ecpg-cpp.html	9.4 KB	-rw-r--r--
ecpg-descriptors.html	34.09 KB	-rw-r--r--
ecpg-develop.html	7.78 KB	-rw-r--r--
ecpg-dynamic.html	6.36 KB	-rw-r--r--
ecpg-errors.html	25.13 KB	-rw-r--r--
ecpg-informix-compat.html	51.52 KB	-rw-r--r--
ecpg-library.html	5.66 KB	-rw-r--r--
ecpg-lo.html	5.4 KB	-rw-r--r--
ecpg-pgtypes.html	53.18 KB	-rw-r--r--
ecpg-preproc.html	8.77 KB	-rw-r--r--
ecpg-process.html	5.26 KB	-rw-r--r--
ecpg-sql-allocate-descriptor.h...	3.89 KB	-rw-r--r--
ecpg-sql-commands.html	4.59 KB	-rw-r--r--
ecpg-sql-connect.html	9.16 KB	-rw-r--r--
ecpg-sql-deallocate-descriptor...	3.68 KB	-rw-r--r--
ecpg-sql-declare.html	5.27 KB	-rw-r--r--
ecpg-sql-describe.html	4.49 KB	-rw-r--r--
ecpg-sql-disconnect.html	4.62 KB	-rw-r--r--
ecpg-sql-execute-immediate.htm...	3.79 KB	-rw-r--r--
ecpg-sql-get-descriptor.html	7.53 KB	-rw-r--r--
ecpg-sql-open.html	4.53 KB	-rw-r--r--
ecpg-sql-prepare.html	4.08 KB	-rw-r--r--
ecpg-sql-set-autocommit.html	3.25 KB	-rw-r--r--
ecpg-sql-set-connection.html	3.84 KB	-rw-r--r--
ecpg-sql-set-descriptor.html	5.38 KB	-rw-r--r--
ecpg-sql-type.html	4.91 KB	-rw-r--r--
ecpg-sql-var.html	3.46 KB	-rw-r--r--
ecpg-sql-whenever.html	4.58 KB	-rw-r--r--
ecpg-variables.html	39.34 KB	-rw-r--r--
ecpg.html	10.1 KB	-rw-r--r--
encryption-options.html	7.32 KB	-rw-r--r--
errcodes-appendix.html	36.1 KB	-rw-r--r--
error-message-reporting.html	13.79 KB	-rw-r--r--
error-style-guide.html	16.38 KB	-rw-r--r--
event-log-registration.html	4.09 KB	-rw-r--r--
executor.html	6.46 KB	-rw-r--r--
explicit-joins.html	10.76 KB	-rw-r--r--
explicit-locking.html	24.49 KB	-rw-r--r--
extend-extensions.html	31.67 KB	-rw-r--r--
extend-how.html	4.45 KB	-rw-r--r--
extend-pgxs.html	11.49 KB	-rw-r--r--
extend-type-system.html	9.87 KB	-rw-r--r--
extend.html	9.75 KB	-rw-r--r--
external-admin-tools.html	2.66 KB	-rw-r--r--
external-extensions.html	3.19 KB	-rw-r--r--
external-interfaces.html	5.38 KB	-rw-r--r--
external-pl.html	4.56 KB	-rw-r--r--
external-projects.html	2.93 KB	-rw-r--r--
fdw-callbacks.html	12.6 KB	-rw-r--r--
fdw-functions.html	4.39 KB	-rw-r--r--
fdw-helpers.html	5.85 KB	-rw-r--r--
fdw-planning.html	9.61 KB	-rw-r--r--
fdwhandler.html	3.9 KB	-rw-r--r--
features-sql-standard.html	38.19 KB	-rw-r--r--
features.html	7.39 KB	-rw-r--r--
file-fdw.html	7.53 KB	-rw-r--r--
functions-admin.html	49.21 KB	-rw-r--r--
functions-aggregate.html	21.3 KB	-rw-r--r--
functions-array.html	13.2 KB	-rw-r--r--
functions-binarystring.html	12.29 KB	-rw-r--r--
functions-bitstring.html	6.63 KB	-rw-r--r--
functions-comparison.html	10.39 KB	-rw-r--r--
functions-comparisons.html	13.21 KB	-rw-r--r--
functions-conditional.html	10.75 KB	-rw-r--r--
functions-datetime.html	47.17 KB	-rw-r--r--
functions-enum.html	5.36 KB	-rw-r--r--
functions-formatting.html	34.57 KB	-rw-r--r--
functions-geometry.html	19.87 KB	-rw-r--r--
functions-info.html	57.28 KB	-rw-r--r--
functions-json.html	3.72 KB	-rw-r--r--
functions-logical.html	4.56 KB	-rw-r--r--
functions-matching.html	73.95 KB	-rw-r--r--
functions-math.html	19.92 KB	-rw-r--r--
functions-net.html	13.19 KB	-rw-r--r--
functions-range.html	10.6 KB	-rw-r--r--
functions-sequence.html	12.62 KB	-rw-r--r--
functions-srf.html	8.63 KB	-rw-r--r--
functions-string.html	57.67 KB	-rw-r--r--
functions-subquery.html	16 KB	-rw-r--r--
functions-textsearch.html	20.01 KB	-rw-r--r--
functions-trigger.html	4.44 KB	-rw-r--r--
functions-window.html	11.8 KB	-rw-r--r--
functions-xml.html	31.42 KB	-rw-r--r--
functions.html	9.71 KB	-rw-r--r--
fuzzystrmatch.html	7.87 KB	-rw-r--r--
geqo-biblio.html	3.38 KB	-rw-r--r--
geqo-intro.html	4.31 KB	-rw-r--r--
geqo-intro2.html	5.5 KB	-rw-r--r--
geqo-pg-intro.html	8.58 KB	-rw-r--r--
geqo.html	3.53 KB	-rw-r--r--
gin-examples.html	3.24 KB	-rw-r--r--
gin-extensibility.html	14.06 KB	-rw-r--r--
gin-implementation.html	6.41 KB	-rw-r--r--
gin-intro.html	4.55 KB	-rw-r--r--
gin-limit.html	2.75 KB	-rw-r--r--
gin-tips.html	5.58 KB	-rw-r--r--
gin.html	2.86 KB	-rw-r--r--
gist-examples.html	3.66 KB	-rw-r--r--
gist-extensibility.html	23.78 KB	-rw-r--r--
gist-implementation.html	4 KB	-rw-r--r--
gist-intro.html	3.53 KB	-rw-r--r--
gist.html	2.62 KB	-rw-r--r--
git.html	4.46 KB	-rw-r--r--
high-availability.html	7.52 KB	-rw-r--r--
history.html	11.64 KB	-rw-r--r--
hot-standby.html	35.2 KB	-rw-r--r--
hstore.html	22.1 KB	-rw-r--r--
index-catalog.html	7.81 KB	-rw-r--r--
index-cost-estimation.html	9.76 KB	-rw-r--r--
index-functions.html	18.67 KB	-rw-r--r--
index-locking.html	7.86 KB	-rw-r--r--
index-scanning.html	10.46 KB	-rw-r--r--
index-unique-checks.html	8.98 KB	-rw-r--r--
index.html	7.88 KB	-rw-r--r--
indexam.html	5.12 KB	-rw-r--r--
indexes-bitmap-scans.html	6.43 KB	-rw-r--r--
indexes-collations.html	3.55 KB	-rw-r--r--
indexes-examine.html	6.99 KB	-rw-r--r--
indexes-expressional.html	4.7 KB	-rw-r--r--
indexes-intro.html	6.17 KB	-rw-r--r--
indexes-multicolumn.html	6.15 KB	-rw-r--r--
indexes-opclass.html	7.16 KB	-rw-r--r--
indexes-ordering.html	6.33 KB	-rw-r--r--
indexes-partial.html	11.54 KB	-rw-r--r--
indexes-types.html	9.99 KB	-rw-r--r--
indexes-unique.html	3.91 KB	-rw-r--r--
indexes.html	3.53 KB	-rw-r--r--
information-schema.html	10.92 KB	-rw-r--r--
infoschema-administrable-role-...	3.66 KB	-rw-r--r--
infoschema-applicable-roles.ht...	3.88 KB	-rw-r--r--
infoschema-attributes.html	12.51 KB	-rw-r--r--
infoschema-character-sets.html	6.88 KB	-rw-r--r--
infoschema-check-constraint-ro...	4.25 KB	-rw-r--r--
infoschema-check-constraints.h...	3.79 KB	-rw-r--r--
infoschema-collation-character...	4.32 KB	-rw-r--r--
infoschema-collations.html	3.79 KB	-rw-r--r--
infoschema-column-domain-usage...	4.22 KB	-rw-r--r--
infoschema-column-options.html	4.01 KB	-rw-r--r--
infoschema-column-privileges.h...	4.91 KB	-rw-r--r--
infoschema-column-udt-usage.ht...	4.48 KB	-rw-r--r--
infoschema-columns.html	17.21 KB	-rw-r--r--
infoschema-constraint-column-u...	4.76 KB	-rw-r--r--
infoschema-constraint-table-us...	4.66 KB	-rw-r--r--
infoschema-data-type-privilege...	4.97 KB	-rw-r--r--
infoschema-datatypes.html	4.13 KB	-rw-r--r--
infoschema-domain-constraints....	4.55 KB	-rw-r--r--
infoschema-domain-udt-usage.ht...	4.07 KB	-rw-r--r--
infoschema-domains.html	11.1 KB	-rw-r--r--
infoschema-element-types.html	11.11 KB	-rw-r--r--
infoschema-enabled-roles.html	3.69 KB	-rw-r--r--
infoschema-foreign-data-wrappe...	3.82 KB	-rw-r--r--
infoschema-foreign-data-wrappe...	4.13 KB	-rw-r--r--
infoschema-foreign-server-opti...	3.76 KB	-rw-r--r--
infoschema-foreign-servers.htm...	4.46 KB	-rw-r--r--
infoschema-foreign-table-optio...	3.88 KB	-rw-r--r--
infoschema-foreign-tables.html	3.98 KB	-rw-r--r--
infoschema-information-schema-...	3.28 KB	-rw-r--r--
infoschema-key-column-usage.ht...	5.06 KB	-rw-r--r--
infoschema-parameters.html	10.55 KB	-rw-r--r--
infoschema-referential-constra...	5.53 KB	-rw-r--r--
infoschema-role-column-grants....	4.9 KB	-rw-r--r--
infoschema-role-routine-grants...	5.23 KB	-rw-r--r--
infoschema-role-table-grants.h...	5.3 KB	-rw-r--r--
infoschema-role-udt-grants.htm...	4.67 KB	-rw-r--r--
infoschema-role-usage-grants.h...	4.89 KB	-rw-r--r--
infoschema-routine-privileges....	4.91 KB	-rw-r--r--
infoschema-routines.html	22.51 KB	-rw-r--r--
infoschema-schema.html	3.11 KB	-rw-r--r--
infoschema-schemata.html	4.15 KB	-rw-r--r--
infoschema-sequences.html	5.97 KB	-rw-r--r--
infoschema-sql-features.html	4.6 KB	-rw-r--r--
infoschema-sql-implementation-...	4.4 KB	-rw-r--r--
infoschema-sql-languages.html	4.97 KB	-rw-r--r--
infoschema-sql-packages.html	4.08 KB	-rw-r--r--
infoschema-sql-parts.html	3.98 KB	-rw-r--r--
infoschema-sql-sizing-profiles...	4.08 KB	-rw-r--r--
infoschema-sql-sizing.html	4 KB	-rw-r--r--
infoschema-table-constraints.h...	4.8 KB	-rw-r--r--
infoschema-table-privileges.ht...	4.98 KB	-rw-r--r--
infoschema-tables.html	5.82 KB	-rw-r--r--
infoschema-triggered-update-co...	4.45 KB	-rw-r--r--
infoschema-triggers.html	9.23 KB	-rw-r--r--
infoschema-udt-privileges.html	4.4 KB	-rw-r--r--
infoschema-usage-privileges.ht...	5.38 KB	-rw-r--r--
infoschema-user-defined-types....	9.52 KB	-rw-r--r--
infoschema-user-mapping-option...	4.34 KB	-rw-r--r--
infoschema-user-mappings.html	3.74 KB	-rw-r--r--
infoschema-view-column-usage.h...	4.62 KB	-rw-r--r--
infoschema-view-routine-usage....	4.27 KB	-rw-r--r--
infoschema-view-table-usage.ht...	4.29 KB	-rw-r--r--
infoschema-views.html	5.4 KB	-rw-r--r--
install-getsource.html	3.49 KB	-rw-r--r--
install-post.html	7.89 KB	-rw-r--r--
install-procedure.html	45.44 KB	-rw-r--r--
install-requirements.html	14.14 KB	-rw-r--r--
install-short.html	2.8 KB	-rw-r--r--
install-windows-full.html	18.82 KB	-rw-r--r--
install-windows-libpq.html	6.14 KB	-rw-r--r--
install-windows.html	6.46 KB	-rw-r--r--
installation-platform-notes.ht...	38.46 KB	-rw-r--r--
installation.html	4.06 KB	-rw-r--r--
intagg.html	6.11 KB	-rw-r--r--
intarray.html	13.43 KB	-rw-r--r--
internals.html	15.27 KB	-rw-r--r--
intro-whatis.html	3.92 KB	-rw-r--r--
isn.html	13.04 KB	-rw-r--r--
kernel-resources.html	36.94 KB	-rw-r--r--
largeobjects.html	4.57 KB	-rw-r--r--
libpq-async.html	20.53 KB	-rw-r--r--
libpq-build.html	6.22 KB	-rw-r--r--
libpq-cancel.html	6.62 KB	-rw-r--r--
libpq-connect.html	50.05 KB	-rw-r--r--
libpq-control.html	6.13 KB	-rw-r--r--
libpq-copy.html	21.92 KB	-rw-r--r--
libpq-envars.html	9.59 KB	-rw-r--r--
libpq-events.html	22.55 KB	-rw-r--r--
libpq-example.html	15.65 KB	-rw-r--r--
libpq-exec.html	63.36 KB	-rw-r--r--
libpq-fastpath.html	5.98 KB	-rw-r--r--
libpq-ldap.html	5.38 KB	-rw-r--r--
libpq-misc.html	13.49 KB	-rw-r--r--
libpq-notice-processing.html	6.14 KB	-rw-r--r--
libpq-notify.html	6.56 KB	-rw-r--r--
libpq-pgpass.html	4.75 KB	-rw-r--r--
libpq-pgservice.html	3.81 KB	-rw-r--r--
libpq-single-row-mode.html	6.2 KB	-rw-r--r--
libpq-ssl.html	19.5 KB	-rw-r--r--
libpq-status.html	17.28 KB	-rw-r--r--
libpq-threading.html	5.41 KB	-rw-r--r--
libpq.html	7.73 KB	-rw-r--r--
lo-examplesect.html	8.49 KB	-rw-r--r--
lo-funcs.html	4.53 KB	-rw-r--r--
lo-implementation.html	3.27 KB	-rw-r--r--
lo-interfaces.html	14.8 KB	-rw-r--r--
lo-intro.html	3.13 KB	-rw-r--r--
lo.html	6.47 KB	-rw-r--r--
locale.html	13.37 KB	-rw-r--r--
locking-indexes.html	4.25 KB	-rw-r--r--
log-shipping-alternative.html	10.8 KB	-rw-r--r--
logfile-maintenance.html	6.98 KB	-rw-r--r--
ltree.html	26.66 KB	-rw-r--r--
maintenance.html	5.41 KB	-rw-r--r--
manage-ag-config.html	3.66 KB	-rw-r--r--
manage-ag-createdb.html	6.16 KB	-rw-r--r--
manage-ag-dropdb.html	3.52 KB	-rw-r--r--
manage-ag-overview.html	5.02 KB	-rw-r--r--
manage-ag-tablespaces.html	9.03 KB	-rw-r--r--
manage-ag-templatedbs.html	7.97 KB	-rw-r--r--
managing-databases.html	3.2 KB	-rw-r--r--
monitoring-locks.html	3.59 KB	-rw-r--r--
monitoring-ps.html	6.62 KB	-rw-r--r--
monitoring-stats.html	56.7 KB	-rw-r--r--
monitoring.html	4.35 KB	-rw-r--r--
multibyte.html	31.22 KB	-rw-r--r--
mvcc-caveats.html	3.98 KB	-rw-r--r--
mvcc-intro.html	4.45 KB	-rw-r--r--
mvcc.html	4.2 KB	-rw-r--r--
nls-programmer.html	9.84 KB	-rw-r--r--
nls-translator.html	14.18 KB	-rw-r--r--
nls.html	3.06 KB	-rw-r--r--
non-durability.html	4.38 KB	-rw-r--r--
notation.html	4.31 KB	-rw-r--r--
oid2name.html	11.68 KB	-rw-r--r--
overview.html	4 KB	-rw-r--r--
pageinspect.html	7.93 KB	-rw-r--r--
parser-stage.html	7.93 KB	-rw-r--r--
passwordcheck.html	4.68 KB	-rw-r--r--
performance-tips.html	4.4 KB	-rw-r--r--
perm-functions.html	3.26 KB	-rw-r--r--
pgarchivecleanup.html	8.79 KB	-rw-r--r--
pgbench.html	30.11 KB	-rw-r--r--
pgbuffercache.html	7.53 KB	-rw-r--r--
pgcrypto.html	37.89 KB	-rw-r--r--
pgfreespacemap.html	5.11 KB	-rw-r--r--
pgrowlocks.html	5.94 KB	-rw-r--r--
pgstandby.html	14.85 KB	-rw-r--r--
pgstatstatements.html	15.69 KB	-rw-r--r--
pgstattuple.html	9.23 KB	-rw-r--r--
pgtestfsync.html	5.13 KB	-rw-r--r--
pgtesttiming.html	12.18 KB	-rw-r--r--
pgtrgm.html	12.04 KB	-rw-r--r--
pgupgrade.html	24.16 KB	-rw-r--r--
planner-optimizer.html	9.18 KB	-rw-r--r--
planner-stats-details.html	3.2 KB	-rw-r--r--
planner-stats-security.html	5.43 KB	-rw-r--r--
planner-stats.html	8.85 KB	-rw-r--r--
plhandler.html	13.43 KB	-rw-r--r--
plperl-builtins.html	17.85 KB	-rw-r--r--
plperl-data.html	2.81 KB	-rw-r--r--
plperl-funcs.html	13.06 KB	-rw-r--r--
plperl-global.html	4.95 KB	-rw-r--r--
plperl-triggers.html	6.29 KB	-rw-r--r--
plperl-trusted.html	6.55 KB	-rw-r--r--
plperl-under-the-hood.html	8.78 KB	-rw-r--r--
plperl.html	4.81 KB	-rw-r--r--
plpgsql-control-structures.htm...	45.1 KB	-rw-r--r--
plpgsql-cursors.html	24.99 KB	-rw-r--r--
plpgsql-declarations.html	21.24 KB	-rw-r--r--
plpgsql-development-tips.html	9.29 KB	-rw-r--r--
plpgsql-errors-and-messages.ht...	9.86 KB	-rw-r--r--
plpgsql-expressions.html	4.55 KB	-rw-r--r--
plpgsql-implementation.html	17.62 KB	-rw-r--r--
plpgsql-overview.html	8.82 KB	-rw-r--r--
plpgsql-porting.html	26.46 KB	-rw-r--r--
plpgsql-statements.html	31.47 KB	-rw-r--r--
plpgsql-structure.html	8.13 KB	-rw-r--r--
plpgsql-trigger.html	21.8 KB	-rw-r--r--
plpgsql.html	6.8 KB	-rw-r--r--
plpython-data.html	14.3 KB	-rw-r--r--
plpython-database.html	15.05 KB	-rw-r--r--
plpython-do.html	2.71 KB	-rw-r--r--
plpython-envar.html	3.79 KB	-rw-r--r--
plpython-funcs.html	5.35 KB	-rw-r--r--
plpython-python23.html	7.04 KB	-rw-r--r--
plpython-sharing.html	2.96 KB	-rw-r--r--
plpython-subtransaction.html	7.7 KB	-rw-r--r--
plpython-trigger.html	4.95 KB	-rw-r--r--
plpython-util.html	4.98 KB	-rw-r--r--
plpython.html	5.92 KB	-rw-r--r--
pltcl-data.html	2.84 KB	-rw-r--r--
pltcl-dbaccess.html	13.58 KB	-rw-r--r--
pltcl-functions.html	6.03 KB	-rw-r--r--
pltcl-global.html	4.95 KB	-rw-r--r--
pltcl-overview.html	5.16 KB	-rw-r--r--
pltcl-procnames.html	3.15 KB	-rw-r--r--
pltcl-trigger.html	9.23 KB	-rw-r--r--
pltcl-unknown.html	4.96 KB	-rw-r--r--
pltcl.html	3.32 KB	-rw-r--r--
populate.html	16.71 KB	-rw-r--r--
postgres-user.html	3.24 KB	-rw-r--r--
preface.html	4.95 KB	-rw-r--r--
preventing-server-spoofing.htm...	4.5 KB	-rw-r--r--
protocol-changes.html	6.49 KB	-rw-r--r--
protocol-error-fields.html	5.99 KB	-rw-r--r--
protocol-flow.html	45.12 KB	-rw-r--r--
protocol-message-formats.html	39.89 KB	-rw-r--r--
protocol-message-types.html	4.82 KB	-rw-r--r--
protocol-overview.html	9.44 KB	-rw-r--r--
protocol-replication.html	14.32 KB	-rw-r--r--
protocol.html	5.52 KB	-rw-r--r--
queries-limit.html	5.21 KB	-rw-r--r--
queries-order.html	7.2 KB	-rw-r--r--
queries-overview.html	4.95 KB	-rw-r--r--
queries-select-lists.html	9.09 KB	-rw-r--r--
queries-table-expressions.html	38.94 KB	-rw-r--r--
queries-union.html	4.99 KB	-rw-r--r--
queries-values.html	4.81 KB	-rw-r--r--
queries-with.html	20.39 KB	-rw-r--r--
queries.html	4.31 KB	-rw-r--r--
query-path.html	5.34 KB	-rw-r--r--
querytree.html	10.88 KB	-rw-r--r--
rangetypes.html	22.2 KB	-rw-r--r--
recovery-config.html	3.47 KB	-rw-r--r--
recovery-target-settings.html	7.58 KB	-rw-r--r--
reference-client.html	5.96 KB	-rw-r--r--
reference-server.html	3.87 KB	-rw-r--r--
reference.html	22.62 KB	-rw-r--r--
regress-coverage.html	3.25 KB	-rw-r--r--
regress-evaluation.html	12.19 KB	-rw-r--r--
regress-run.html	13.39 KB	-rw-r--r--
regress-variant.html	7.01 KB	-rw-r--r--
regress.html	4.18 KB	-rw-r--r--
release-0-01.html	2.5 KB	-rw-r--r--
release-0-02.html	4.19 KB	-rw-r--r--
release-0-03.html	7.62 KB	-rw-r--r--
release-1-0.html	4.13 KB	-rw-r--r--
release-1-01.html	9.13 KB	-rw-r--r--
release-1-02.html	6.34 KB	-rw-r--r--
release-1-09.html	2.47 KB	-rw-r--r--
release-6-0.html	7.73 KB	-rw-r--r--
release-6-1-1.html	3.63 KB	-rw-r--r--
release-6-1.html	8.81 KB	-rw-r--r--
release-6-2-1.html	4.3 KB	-rw-r--r--
release-6-2.html	8.67 KB	-rw-r--r--
release-6-3-1.html	4.34 KB	-rw-r--r--
release-6-3-2.html	4.06 KB	-rw-r--r--
release-6-3.html	15.93 KB	-rw-r--r--
release-6-4-1.html	3.97 KB	-rw-r--r--
release-6-4-2.html	2.84 KB	-rw-r--r--
release-6-4.html	14.39 KB	-rw-r--r--
release-6-5-1.html	3.75 KB	-rw-r--r--
release-6-5-2.html	4.01 KB	-rw-r--r--
release-6-5-3.html	2.98 KB	-rw-r--r--
release-6-5.html	16.98 KB	-rw-r--r--
release-7-0-1.html	3.83 KB	-rw-r--r--
release-7-0-2.html	2.82 KB	-rw-r--r--
release-7-0-3.html	4.55 KB	-rw-r--r--
release-7-0.html	22.56 KB	-rw-r--r--
release-7-1-1.html	3.19 KB	-rw-r--r--
release-7-1-2.html	2.91 KB	-rw-r--r--
release-7-1-3.html	3.07 KB	-rw-r--r--
release-7-1.html	12.71 KB	-rw-r--r--
release-7-2-1.html	3.92 KB	-rw-r--r--
release-7-2-2.html	3.7 KB	-rw-r--r--
release-7-2-3.html	3.29 KB	-rw-r--r--
release-7-2-4.html	3.5 KB	-rw-r--r--
release-7-2-5.html	3.66 KB	-rw-r--r--
release-7-2-6.html	3.54 KB	-rw-r--r--
release-7-2-7.html	3.64 KB	-rw-r--r--
release-7-2-8.html	3.86 KB	-rw-r--r--
release-7-2.html	26.46 KB	-rw-r--r--
release-7-3-1.html	4.07 KB	-rw-r--r--
release-7-3-10.html	7.32 KB	-rw-r--r--
release-7-3-11.html	4.01 KB	-rw-r--r--
release-7-3-12.html	3.44 KB	-rw-r--r--
release-7-3-13.html	4.51 KB	-rw-r--r--
release-7-3-14.html	3.84 KB	-rw-r--r--
release-7-3-15.html	6.17 KB	-rw-r--r--
release-7-3-16.html	3.34 KB	-rw-r--r--
release-7-3-17.html	3.47 KB	-rw-r--r--
release-7-3-18.html	3.56 KB	-rw-r--r--
release-7-3-19.html	3.6 KB	-rw-r--r--
release-7-3-2.html	5.08 KB	-rw-r--r--
release-7-3-20.html	3.44 KB	-rw-r--r--
release-7-3-21.html	6.07 KB	-rw-r--r--
release-7-3-3.html	10.05 KB	-rw-r--r--
release-7-3-4.html	3.42 KB	-rw-r--r--
release-7-3-5.html	4.39 KB	-rw-r--r--
release-7-3-6.html	4.32 KB	-rw-r--r--
release-7-3-7.html	3.27 KB	-rw-r--r--
release-7-3-8.html	3.49 KB	-rw-r--r--
release-7-3-9.html	3.98 KB	-rw-r--r--
release-7-3.html	32.28 KB	-rw-r--r--
release-7-4-1.html	6.95 KB	-rw-r--r--
release-7-4-10.html	3.72 KB	-rw-r--r--
release-7-4-11.html	4.74 KB	-rw-r--r--
release-7-4-12.html	4.12 KB	-rw-r--r--
release-7-4-13.html	6.8 KB	-rw-r--r--
release-7-4-14.html	3.59 KB	-rw-r--r--
release-7-4-15.html	4.17 KB	-rw-r--r--
release-7-4-16.html	3.88 KB	-rw-r--r--
release-7-4-17.html	3.92 KB	-rw-r--r--
release-7-4-18.html	3.83 KB	-rw-r--r--
release-7-4-19.html	7.07 KB	-rw-r--r--
release-7-4-2.html	8.07 KB	-rw-r--r--
release-7-4-20.html	6.45 KB	-rw-r--r--
release-7-4-21.html	3.83 KB	-rw-r--r--
release-7-4-22.html	3.98 KB	-rw-r--r--
release-7-4-23.html	4.32 KB	-rw-r--r--
release-7-4-24.html	4.19 KB	-rw-r--r--
release-7-4-25.html	4.4 KB	-rw-r--r--
release-7-4-26.html	5.33 KB	-rw-r--r--
release-7-4-27.html	5.04 KB	-rw-r--r--
release-7-4-28.html	5.5 KB	-rw-r--r--
release-7-4-29.html	6.8 KB	-rw-r--r--
release-7-4-3.html	4.51 KB	-rw-r--r--
release-7-4-30.html	6.07 KB	-rw-r--r--
release-7-4-4.html	3.99 KB	-rw-r--r--
release-7-4-5.html	3.12 KB	-rw-r--r--
release-7-4-6.html	4.62 KB	-rw-r--r--
release-7-4-7.html	4.17 KB	-rw-r--r--
release-7-4-8.html	9.92 KB	-rw-r--r--
release-7-4-9.html	5 KB	-rw-r--r--
release-7-4.html	56.03 KB	-rw-r--r--
release-8-0-1.html	4.63 KB	-rw-r--r--
release-8-0-10.html	4.64 KB	-rw-r--r--
release-8-0-11.html	3.88 KB	-rw-r--r--
release-8-0-12.html	3.06 KB	-rw-r--r--
release-8-0-13.html	4.02 KB	-rw-r--r--
release-8-0-14.html	4.41 KB	-rw-r--r--
release-8-0-15.html	8.89 KB	-rw-r--r--
release-8-0-16.html	8.74 KB	-rw-r--r--
release-8-0-17.html	3.83 KB	-rw-r--r--
release-8-0-18.html	5.45 KB	-rw-r--r--
release-8-0-19.html	4.86 KB	-rw-r--r--
release-8-0-2.html	9.34 KB	-rw-r--r--
release-8-0-20.html	4.21 KB	-rw-r--r--
release-8-0-21.html	4.4 KB	-rw-r--r--
release-8-0-22.html	6.29 KB	-rw-r--r--
release-8-0-23.html	5.88 KB	-rw-r--r--
release-8-0-24.html	6.84 KB	-rw-r--r--
release-8-0-25.html	7.25 KB	-rw-r--r--
release-8-0-26.html	7.84 KB	-rw-r--r--
release-8-0-3.html	7.25 KB	-rw-r--r--
release-8-0-4.html	6.52 KB	-rw-r--r--
release-8-0-5.html	4.7 KB	-rw-r--r--
release-8-0-6.html	5.56 KB	-rw-r--r--
release-8-0-7.html	5.77 KB	-rw-r--r--
release-8-0-8.html	7.06 KB	-rw-r--r--
release-8-0-9.html	4.21 KB	-rw-r--r--
release-8-0.html	65.25 KB	-rw-r--r--
release-8-1-1.html	5.33 KB	-rw-r--r--
release-8-1-10.html	4.67 KB	-rw-r--r--
release-8-1-11.html	9.71 KB	-rw-r--r--
release-8-1-12.html	9.12 KB	-rw-r--r--
release-8-1-13.html	4.19 KB	-rw-r--r--
release-8-1-14.html	6.74 KB	-rw-r--r--
release-8-1-15.html	6.13 KB	-rw-r--r--
release-8-1-16.html	5.15 KB	-rw-r--r--
release-8-1-17.html	5.89 KB	-rw-r--r--
release-8-1-18.html	6.29 KB	-rw-r--r--
release-8-1-19.html	6.46 KB	-rw-r--r--
release-8-1-2.html	6.19 KB	-rw-r--r--
release-8-1-20.html	7.13 KB	-rw-r--r--
release-8-1-21.html	7.04 KB	-rw-r--r--
release-8-1-22.html	8.13 KB	-rw-r--r--
release-8-1-23.html	7.75 KB	-rw-r--r--
release-8-1-3.html	6.86 KB	-rw-r--r--
release-8-1-4.html	8.67 KB	-rw-r--r--
release-8-1-5.html	5.35 KB	-rw-r--r--
release-8-1-6.html	5.21 KB	-rw-r--r--
release-8-1-7.html	4.45 KB	-rw-r--r--
release-8-1-8.html	3.04 KB	-rw-r--r--
release-8-1-9.html	4.29 KB	-rw-r--r--
release-8-1.html	60.66 KB	-rw-r--r--
release-8-2-1.html	4.95 KB	-rw-r--r--
release-8-2-10.html	7.99 KB	-rw-r--r--
release-8-2-11.html	6.98 KB	-rw-r--r--
release-8-2-12.html	6.59 KB	-rw-r--r--
release-8-2-13.html	7.18 KB	-rw-r--r--
release-8-2-14.html	7.69 KB	-rw-r--r--
release-8-2-15.html	7.96 KB	-rw-r--r--
release-8-2-16.html	9.08 KB	-rw-r--r--
release-8-2-17.html	8.02 KB	-rw-r--r--
release-8-2-18.html	10.04 KB	-rw-r--r--
release-8-2-19.html	8.39 KB	-rw-r--r--
release-8-2-2.html	5.67 KB	-rw-r--r--
release-8-2-20.html	6.1 KB	-rw-r--r--
release-8-2-21.html	5.46 KB	-rw-r--r--
release-8-2-22.html	9.39 KB	-rw-r--r--
release-8-2-23.html	9.33 KB	-rw-r--r--
release-8-2-3.html	3.02 KB	-rw-r--r--
release-8-2-4.html	5.3 KB	-rw-r--r--
release-8-2-5.html	5.85 KB	-rw-r--r--
release-8-2-6.html	10.3 KB	-rw-r--r--
release-8-2-7.html	9.09 KB	-rw-r--r--
release-8-2-8.html	7.34 KB	-rw-r--r--
release-8-2-9.html	4.18 KB	-rw-r--r--
release-8-2.html	67.77 KB	-rw-r--r--
release-8-3-1.html	10.34 KB	-rw-r--r--
release-8-3-10.html	10.47 KB	-rw-r--r--
release-8-3-11.html	8.75 KB	-rw-r--r--
release-8-3-12.html	11.83 KB	-rw-r--r--
release-8-3-13.html	9.28 KB	-rw-r--r--
release-8-3-14.html	6.1 KB	-rw-r--r--
release-8-3-15.html	6.23 KB	-rw-r--r--
release-8-3-16.html	10.76 KB	-rw-r--r--
release-8-3-17.html	10.34 KB	-rw-r--r--
release-8-3-18.html	11 KB	-rw-r--r--
release-8-3-19.html	8.27 KB	-rw-r--r--
release-8-3-2.html	11.92 KB	-rw-r--r--
release-8-3-20.html	9.03 KB	-rw-r--r--
release-8-3-21.html	4.92 KB	-rw-r--r--
release-8-3-22.html	10.34 KB	-rw-r--r--
release-8-3-23.html	6.14 KB	-rw-r--r--
release-8-3-3.html	4.17 KB	-rw-r--r--
release-8-3-4.html	11.01 KB	-rw-r--r--
release-8-3-5.html	8.49 KB	-rw-r--r--
release-8-3-6.html	8.98 KB	-rw-r--r--
release-8-3-7.html	9.5 KB	-rw-r--r--
release-8-3-8.html	9.04 KB	-rw-r--r--
release-8-3-9.html	9.97 KB	-rw-r--r--
release-8-3.html	68.14 KB	-rw-r--r--
release-8-4-1.html	9.34 KB	-rw-r--r--
release-8-4-10.html	11.65 KB	-rw-r--r--
release-8-4-11.html	13.46 KB	-rw-r--r--
release-8-4-12.html	9.75 KB	-rw-r--r--
release-8-4-13.html	9.49 KB	-rw-r--r--
release-8-4-14.html	5 KB	-rw-r--r--
release-8-4-15.html	10.38 KB	-rw-r--r--
release-8-4-16.html	7.16 KB	-rw-r--r--
release-8-4-17.html	9.35 KB	-rw-r--r--
release-8-4-18.html	6.88 KB	-rw-r--r--
release-8-4-19.html	7.6 KB	-rw-r--r--
release-8-4-2.html	15.33 KB	-rw-r--r--
release-8-4-20.html	15.88 KB	-rw-r--r--
release-8-4-21.html	5.32 KB	-rw-r--r--
release-8-4-22.html	11.04 KB	-rw-r--r--
release-8-4-3.html	13.6 KB	-rw-r--r--
release-8-4-4.html	10.48 KB	-rw-r--r--
release-8-4-5.html	15.56 KB	-rw-r--r--
release-8-4-6.html	10.19 KB	-rw-r--r--
release-8-4-7.html	6.07 KB	-rw-r--r--
release-8-4-8.html	8.64 KB	-rw-r--r--
release-8-4-9.html	14.19 KB	-rw-r--r--
release-8-4.html	85.91 KB	-rw-r--r--
release-9-0-1.html	5.81 KB	-rw-r--r--
release-9-0-10.html	5.56 KB	-rw-r--r--
release-9-0-11.html	12.37 KB	-rw-r--r--
release-9-0-12.html	8.62 KB	-rw-r--r--
release-9-0-13.html	11.4 KB	-rw-r--r--
release-9-0-14.html	8.55 KB	-rw-r--r--
release-9-0-15.html	8.93 KB	-rw-r--r--
release-9-0-16.html	17 KB	-rw-r--r--
release-9-0-17.html	6.19 KB	-rw-r--r--
release-9-0-18.html	11.6 KB	-rw-r--r--
release-9-0-19.html	25.99 KB	-rw-r--r--
release-9-0-2.html	13.32 KB	-rw-r--r--
release-9-0-20.html	15.46 KB	-rw-r--r--
release-9-0-21.html	5.04 KB	-rw-r--r--
release-9-0-22.html	4.22 KB	-rw-r--r--
release-9-0-23.html	15.78 KB	-rw-r--r--
release-9-0-3.html	7.09 KB	-rw-r--r--
release-9-0-4.html	11.08 KB	-rw-r--r--
release-9-0-5.html	17.5 KB	-rw-r--r--
release-9-0-6.html	13.11 KB	-rw-r--r--
release-9-0-7.html	17.67 KB	-rw-r--r--
release-9-0-8.html	10.74 KB	-rw-r--r--
release-9-0-9.html	11.47 KB	-rw-r--r--
release-9-0.html	93.87 KB	-rw-r--r--
release-9-1-1.html	3.58 KB	-rw-r--r--
release-9-1-10.html	10.11 KB	-rw-r--r--
release-9-1-11.html	9.36 KB	-rw-r--r--
release-9-1-12.html	18.12 KB	-rw-r--r--
release-9-1-13.html	6.53 KB	-rw-r--r--
release-9-1-14.html	12.73 KB	-rw-r--r--
release-9-1-15.html	28.29 KB	-rw-r--r--
release-9-1-16.html	18.67 KB	-rw-r--r--
release-9-1-17.html	4.83 KB	-rw-r--r--
release-9-1-18.html	4.01 KB	-rw-r--r--
release-9-1-19.html	17.2 KB	-rw-r--r--
release-9-1-2.html	21.07 KB	-rw-r--r--
release-9-1-20.html	17.13 KB	-rw-r--r--
release-9-1-21.html	7.42 KB	-rw-r--r--
release-9-1-22.html	7.09 KB	-rw-r--r--
release-9-1-23.html	12.36 KB	-rw-r--r--
release-9-1-24.html	8.53 KB	-rw-r--r--
release-9-1-3.html	20.66 KB	-rw-r--r--
release-9-1-4.html	15.64 KB	-rw-r--r--
release-9-1-5.html	13.71 KB	-rw-r--r--
release-9-1-6.html	9.3 KB	-rw-r--r--
release-9-1-7.html	14.59 KB	-rw-r--r--
release-9-1-8.html	9.92 KB	-rw-r--r--
release-9-1-9.html	12.38 KB	-rw-r--r--
release-9-1.html	77.11 KB	-rw-r--r--
release-9-2-1.html	6.94 KB	-rw-r--r--
release-9-2-10.html	31.61 KB	-rw-r--r--
release-9-2-11.html	19.82 KB	-rw-r--r--
release-9-2-12.html	5.01 KB	-rw-r--r--
release-9-2-13.html	4.01 KB	-rw-r--r--
release-9-2-14.html	17.96 KB	-rw-r--r--
release-9-2-15.html	18.17 KB	-rw-r--r--
release-9-2-16.html	7.42 KB	-rw-r--r--
release-9-2-17.html	8 KB	-rw-r--r--
release-9-2-18.html	12.42 KB	-rw-r--r--
release-9-2-19.html	10.27 KB	-rw-r--r--
release-9-2-2.html	22.46 KB	-rw-r--r--
release-9-2-20.html	13.02 KB	-rw-r--r--
release-9-2-21.html	13.87 KB	-rw-r--r--
release-9-2-22.html	15.49 KB	-rw-r--r--
release-9-2-23.html	7.94 KB	-rw-r--r--
release-9-2-24.html	7.69 KB	-rw-r--r--
release-9-2-3.html	13.06 KB	-rw-r--r--
release-9-2-4.html	14.45 KB	-rw-r--r--
release-9-2-5.html	11.72 KB	-rw-r--r--
release-9-2-6.html	11.41 KB	-rw-r--r--
release-9-2-7.html	19.55 KB	-rw-r--r--
release-9-2-8.html	7.2 KB	-rw-r--r--
release-9-2-9.html	15.25 KB	-rw-r--r--
release-9-2.html	77.66 KB	-rw-r--r--
release.html	22.35 KB	-rw-r--r--
resources.html	4.13 KB	-rw-r--r--
role-attributes.html	7.67 KB	-rw-r--r--
role-membership.html	8.19 KB	-rw-r--r--
role-removal.html	5.18 KB	-rw-r--r--
routine-reindex.html	3.54 KB	-rw-r--r--
routine-vacuuming.html	37.13 KB	-rw-r--r--
row-estimation-examples.html	20.28 KB	-rw-r--r--
rowtypes.html	22.86 KB	-rw-r--r--
rule-system.html	4.02 KB	-rw-r--r--
rules-privileges.html	11.39 KB	-rw-r--r--
rules-status.html	4.41 KB	-rw-r--r--
rules-triggers.html	9.25 KB	-rw-r--r--
rules-update.html	31.85 KB	-rw-r--r--
rules-views.html	26.26 KB	-rw-r--r--
rules.html	4.83 KB	-rw-r--r--
runtime-config-autovacuum.html	10.72 KB	-rw-r--r--
runtime-config-client.html	32.05 KB	-rw-r--r--
runtime-config-compatible.html	14.48 KB	-rw-r--r--
runtime-config-connection.html	22.93 KB	-rw-r--r--
runtime-config-custom.html	3.46 KB	-rw-r--r--
runtime-config-developer.html	13.74 KB	-rw-r--r--
runtime-config-error-handling....	3.49 KB	-rw-r--r--
runtime-config-file-locations....	6.81 KB	-rw-r--r--
runtime-config-locks.html	7.46 KB	-rw-r--r--
runtime-config-logging.html	44.38 KB	-rw-r--r--
runtime-config-preset.html	8.51 KB	-rw-r--r--
runtime-config-query.html	24.37 KB	-rw-r--r--
runtime-config-replication.htm...	17.87 KB	-rw-r--r--
runtime-config-resource.html	27.25 KB	-rw-r--r--
runtime-config-short.html	6.53 KB	-rw-r--r--
runtime-config-statistics.html	8.41 KB	-rw-r--r--
runtime-config-wal.html	26.46 KB	-rw-r--r--
runtime-config.html	8.06 KB	-rw-r--r--
runtime.html	5.12 KB	-rw-r--r--
seg.html	15.11 KB	-rw-r--r--
sepgsql.html	30.11 KB	-rw-r--r--
server-programming.html	9.39 KB	-rw-r--r--
server-shutdown.html	6.32 KB	-rw-r--r--
server-start.html	13.88 KB	-rw-r--r--
source-format.html	5.01 KB	-rw-r--r--
source.html	3.98 KB	-rw-r--r--
sourcerepo.html	3.33 KB	-rw-r--r--
spgist-examples.html	2.64 KB	-rw-r--r--
spgist-extensibility.html	30.55 KB	-rw-r--r--
spgist-implementation.html	7.91 KB	-rw-r--r--
spgist-intro.html	4.22 KB	-rw-r--r--
spgist.html	2.9 KB	-rw-r--r--
spi-examples.html	6.07 KB	-rw-r--r--
spi-interface-support.html	3.68 KB	-rw-r--r--
spi-interface.html	5.86 KB	-rw-r--r--
spi-memory.html	6.92 KB	-rw-r--r--
spi-realloc.html	3.54 KB	-rw-r--r--
spi-spi-connect.html	3.96 KB	-rw-r--r--
spi-spi-copytuple.html	3.37 KB	-rw-r--r--
spi-spi-cursor-close.html	3.26 KB	-rw-r--r--
spi-spi-cursor-fetch.html	4.01 KB	-rw-r--r--
spi-spi-cursor-find.html	3.38 KB	-rw-r--r--
spi-spi-cursor-move.html	3.8 KB	-rw-r--r--
spi-spi-cursor-open-with-args....	6.03 KB	-rw-r--r--
spi-spi-cursor-open-with-param...	4.92 KB	-rw-r--r--
spi-spi-cursor-open.html	5.6 KB	-rw-r--r--
spi-spi-exec.html	3.51 KB	-rw-r--r--
spi-spi-execp.html	4.75 KB	-rw-r--r--
spi-spi-execute-plan-with-para...	4.78 KB	-rw-r--r--
spi-spi-execute-plan.html	5.76 KB	-rw-r--r--
spi-spi-execute-with-args.html	6.08 KB	-rw-r--r--
spi-spi-execute.html	12.3 KB	-rw-r--r--
spi-spi-finish.html	3.57 KB	-rw-r--r--
spi-spi-fname.html	3.68 KB	-rw-r--r--
spi-spi-fnumber.html	3.84 KB	-rw-r--r--
spi-spi-freeplan.html	3.42 KB	-rw-r--r--
spi-spi-freetuple.html	3.2 KB	-rw-r--r--
spi-spi-freetupletable.html	3.54 KB	-rw-r--r--
spi-spi-getargcount.html	3.61 KB	-rw-r--r--
spi-spi-getargtypeid.html	4.04 KB	-rw-r--r--
spi-spi-getbinval.html	4.19 KB	-rw-r--r--
spi-spi-getnspname.html	3.39 KB	-rw-r--r--
spi-spi-getrelname.html	3.27 KB	-rw-r--r--
spi-spi-gettype.html	3.63 KB	-rw-r--r--
spi-spi-gettypeid.html	3.63 KB	-rw-r--r--
spi-spi-getvalue.html	4.07 KB	-rw-r--r--
spi-spi-is-cursor-plan.html	4.45 KB	-rw-r--r--
spi-spi-keepplan.html	3.79 KB	-rw-r--r--
spi-spi-modifytuple.html	5.5 KB	-rw-r--r--
spi-spi-palloc.html	3.08 KB	-rw-r--r--
spi-spi-pfree.html	3.2 KB	-rw-r--r--
spi-spi-pop.html	2.68 KB	-rw-r--r--
spi-spi-prepare-cursor.html	4.94 KB	-rw-r--r--
spi-spi-prepare-params.html	4.31 KB	-rw-r--r--
spi-spi-prepare.html	7.48 KB	-rw-r--r--
spi-spi-push.html	3.65 KB	-rw-r--r--
spi-spi-returntuple.html	4 KB	-rw-r--r--
spi-spi-saveplan.html	4.47 KB	-rw-r--r--
spi-spi-scroll-cursor-fetch.ht...	4.7 KB	-rw-r--r--
spi-spi-scroll-cursor-move.htm...	4.78 KB	-rw-r--r--
spi-visibility.html	4.05 KB	-rw-r--r--
spi.html	10.59 KB	-rw-r--r--
sql-abort.html	4.08 KB	-rw-r--r--
sql-alteraggregate.html	5.97 KB	-rw-r--r--
sql-altercollation.html	4.96 KB	-rw-r--r--
sql-alterconversion.html	5.05 KB	-rw-r--r--
sql-alterdatabase.html	8.57 KB	-rw-r--r--
sql-alterdefaultprivileges.htm...	9.19 KB	-rw-r--r--
sql-alterdomain.html	10.85 KB	-rw-r--r--
sql-alterextension.html	11.47 KB	-rw-r--r--
sql-alterforeigndatawrapper.ht...	7.21 KB	-rw-r--r--
sql-alterforeigntable.html	12.41 KB	-rw-r--r--
sql-alterfunction.html	12.54 KB	-rw-r--r--
sql-altergroup.html	5.12 KB	-rw-r--r--
sql-alterindex.html	7.48 KB	-rw-r--r--
sql-alterlanguage.html	3.93 KB	-rw-r--r--
sql-alterlargeobject.html	3.64 KB	-rw-r--r--
sql-alteropclass.html	4.99 KB	-rw-r--r--
sql-alteroperator.html	5.31 KB	-rw-r--r--
sql-alteropfamily.html	13.25 KB	-rw-r--r--
sql-alterrole.html	12.72 KB	-rw-r--r--
sql-alterschema.html	4.21 KB	-rw-r--r--
sql-altersequence.html	12.73 KB	-rw-r--r--
sql-alterserver.html	5.79 KB	-rw-r--r--
sql-altertable.html	42.52 KB	-rw-r--r--
sql-altertablespace.html	5.73 KB	-rw-r--r--
sql-altertrigger.html	4.54 KB	-rw-r--r--
sql-altertsconfig.html	7.94 KB	-rw-r--r--
sql-altertsdictionary.html	6.39 KB	-rw-r--r--
sql-altertsparser.html	4.16 KB	-rw-r--r--
sql-altertstemplate.html	4.12 KB	-rw-r--r--
sql-altertype.html	10.93 KB	-rw-r--r--
sql-alteruser.html	4.61 KB	-rw-r--r--
sql-alterusermapping.html	5.58 KB	-rw-r--r--
sql-alterview.html	6.81 KB	-rw-r--r--
sql-analyze.html	10.42 KB	-rw-r--r--
sql-begin.html	6.54 KB	-rw-r--r--
sql-checkpoint.html	3.67 KB	-rw-r--r--
sql-close.html	4.87 KB	-rw-r--r--
sql-cluster.html	9.18 KB	-rw-r--r--
sql-commands.html	18.37 KB	-rw-r--r--
sql-comment.html	13.48 KB	-rw-r--r--
sql-commit-prepared.html	4.41 KB	-rw-r--r--
sql-commit.html	3.9 KB	-rw-r--r--
sql-copy.html	36.57 KB	-rw-r--r--
sql-createaggregate.html	13.5 KB	-rw-r--r--
sql-createcast.html	19.17 KB	-rw-r--r--
sql-createcollation.html	6.58 KB	-rw-r--r--
sql-createconversion.html	6.38 KB	-rw-r--r--
sql-createdatabase.html	11.85 KB	-rw-r--r--
sql-createdomain.html	8.34 KB	-rw-r--r--
sql-createextension.html	8.87 KB	-rw-r--r--
sql-createforeigndatawrapper.h...	7.87 KB	-rw-r--r--
sql-createforeigntable.html	7.54 KB	-rw-r--r--
sql-createfunction.html	30.35 KB	-rw-r--r--
sql-creategroup.html	3.92 KB	-rw-r--r--
sql-createindex.html	25.33 KB	-rw-r--r--
sql-createlanguage.html	14.54 KB	-rw-r--r--
sql-createopclass.html	12.38 KB	-rw-r--r--
sql-createoperator.html	10.44 KB	-rw-r--r--
sql-createopfamily.html	5.49 KB	-rw-r--r--
sql-createrole.html	18.87 KB	-rw-r--r--
sql-createrule.html	12.36 KB	-rw-r--r--
sql-createschema.html	8.12 KB	-rw-r--r--
sql-createsequence.html	13.54 KB	-rw-r--r--
sql-createserver.html	6.1 KB	-rw-r--r--
sql-createtable.html	57.79 KB	-rw-r--r--
sql-createtableas.html	12.47 KB	-rw-r--r--
sql-createtablespace.html	5.96 KB	-rw-r--r--
sql-createtrigger.html	22.63 KB	-rw-r--r--
sql-createtsconfig.html	5.23 KB	-rw-r--r--
sql-createtsdictionary.html	5.4 KB	-rw-r--r--
sql-createtsparser.html	5.81 KB	-rw-r--r--
sql-createtstemplate.html	5.31 KB	-rw-r--r--
sql-createtype.html	38.54 KB	-rw-r--r--
sql-createuser.html	4.42 KB	-rw-r--r--
sql-createusermapping.html	5.37 KB	-rw-r--r--
sql-createview.html	10.31 KB	-rw-r--r--
sql-deallocate.html	3.7 KB	-rw-r--r--
sql-declare.html	15.04 KB	-rw-r--r--
sql-delete.html	11.5 KB	-rw-r--r--
sql-discard.html	4.21 KB	-rw-r--r--
sql-do.html	5.08 KB	-rw-r--r--
sql-drop-owned.html	4.94 KB	-rw-r--r--
sql-dropaggregate.html	4.45 KB	-rw-r--r--
sql-dropcast.html	4.24 KB	-rw-r--r--
sql-dropcollation.html	4.31 KB	-rw-r--r--
sql-dropconversion.html	4.33 KB	-rw-r--r--
sql-dropdatabase.html	4.24 KB	-rw-r--r--
sql-dropdomain.html	4.16 KB	-rw-r--r--
sql-dropextension.html	4.67 KB	-rw-r--r--
sql-dropforeigndatawrapper.htm...	4.42 KB	-rw-r--r--
sql-dropforeigntable.html	4.45 KB	-rw-r--r--
sql-dropfunction.html	5.7 KB	-rw-r--r--
sql-dropgroup.html	2.98 KB	-rw-r--r--
sql-dropindex.html	5.06 KB	-rw-r--r--
sql-droplanguage.html	4.73 KB	-rw-r--r--
sql-dropopclass.html	5.54 KB	-rw-r--r--
sql-dropoperator.html	5.1 KB	-rw-r--r--
sql-dropopfamily.html	5.16 KB	-rw-r--r--
sql-droprole.html	5.04 KB	-rw-r--r--
sql-droprule.html	4.05 KB	-rw-r--r--
sql-dropschema.html	4.42 KB	-rw-r--r--
sql-dropsequence.html	4.26 KB	-rw-r--r--
sql-dropserver.html	4.17 KB	-rw-r--r--
sql-droptable.html	4.91 KB	-rw-r--r--
sql-droptablespace.html	4.48 KB	-rw-r--r--
sql-droptrigger.html	4.6 KB	-rw-r--r--
sql-droptsconfig.html	4.66 KB	-rw-r--r--
sql-droptsdictionary.html	4.58 KB	-rw-r--r--
sql-droptsparser.html	4.49 KB	-rw-r--r--
sql-droptstemplate.html	4.46 KB	-rw-r--r--
sql-droptype.html	4.36 KB	-rw-r--r--
sql-dropuser.html	3.11 KB	-rw-r--r--
sql-dropusermapping.html	4.57 KB	-rw-r--r--
sql-dropview.html	4.16 KB	-rw-r--r--
sql-end.html	4.06 KB	-rw-r--r--
sql-execute.html	4.95 KB	-rw-r--r--
sql-explain.html	16.69 KB	-rw-r--r--
sql-expressions.html	46.68 KB	-rw-r--r--
sql-fetch.html	13.92 KB	-rw-r--r--
sql-grant.html	28.56 KB	-rw-r--r--
sql-insert.html	12.56 KB	-rw-r--r--
sql-keywords-appendix.html	104.04 KB	-rw-r--r--
sql-listen.html	5.76 KB	-rw-r--r--
sql-load.html	4.11 KB	-rw-r--r--
sql-lock.html	11.59 KB	-rw-r--r--
sql-move.html	4.87 KB	-rw-r--r--
sql-notify.html	10.69 KB	-rw-r--r--
sql-prepare-transaction.html	8.44 KB	-rw-r--r--
sql-prepare.html	8.97 KB	-rw-r--r--
sql-reassign-owned.html	5.22 KB	-rw-r--r--
sql-reindex.html	10.84 KB	-rw-r--r--
sql-release-savepoint.html	4.89 KB	-rw-r--r--
sql-reset.html	4.88 KB	-rw-r--r--
sql-revoke.html	14.53 KB	-rw-r--r--
sql-rollback-prepared.html	4.52 KB	-rw-r--r--
sql-rollback-to.html	6.25 KB	-rw-r--r--
sql-rollback.html	3.9 KB	-rw-r--r--
sql-savepoint.html	5.47 KB	-rw-r--r--
sql-security-label.html	8.67 KB	-rw-r--r--
sql-select.html	77.68 KB	-rw-r--r--
sql-selectinto.html	7.46 KB	-rw-r--r--
sql-set-constraints.html	6.9 KB	-rw-r--r--
sql-set-role.html	6.75 KB	-rw-r--r--
sql-set-session-authorization....	5.92 KB	-rw-r--r--
sql-set-transaction.html	12.4 KB	-rw-r--r--
sql-set.html	11.77 KB	-rw-r--r--
sql-show.html	6.69 KB	-rw-r--r--
sql-start-transaction.html	4.87 KB	-rw-r--r--
sql-syntax-calling-funcs.html	7.89 KB	-rw-r--r--
sql-syntax-lexical.html	42.35 KB	-rw-r--r--
sql-syntax.html	5.3 KB	-rw-r--r--
sql-truncate.html	9.14 KB	-rw-r--r--
sql-unlisten.html	4.81 KB	-rw-r--r--
sql-update.html	15.3 KB	-rw-r--r--
sql-vacuum.html	10.42 KB	-rw-r--r--
sql-values.html	10.39 KB	-rw-r--r--
sql.html	13.25 KB	-rw-r--r--
ssh-tunnels.html	6.12 KB	-rw-r--r--
ssl-tcp.html	13.16 KB	-rw-r--r--
sslinfo.html	7.42 KB	-rw-r--r--
standby-settings.html	5.3 KB	-rw-r--r--
storage-file-layout.html	12.63 KB	-rw-r--r--
storage-fsm.html	3.73 KB	-rw-r--r--
storage-init.html	2.7 KB	-rw-r--r--
storage-page-layout.html	13.57 KB	-rw-r--r--
storage-toast.html	11.21 KB	-rw-r--r--
storage-vm.html	3.46 KB	-rw-r--r--
storage.html	2.88 KB	-rw-r--r--
stylesheet.css	1.5 KB	-rw-r--r--
supported-platforms.html	4.92 KB	-rw-r--r--
tablefunc.html	31.44 KB	-rw-r--r--
tcn.html	4.86 KB	-rw-r--r--
test-parser.html	4.42 KB	-rw-r--r--
textsearch-configuration.html	6.11 KB	-rw-r--r--
textsearch-controls.html	26.33 KB	-rw-r--r--
textsearch-debugging.html	16.82 KB	-rw-r--r--
textsearch-dictionaries.html	30.53 KB	-rw-r--r--
textsearch-features.html	20.81 KB	-rw-r--r--
textsearch-indexes.html	7.21 KB	-rw-r--r--
textsearch-intro.html	18.02 KB	-rw-r--r--
textsearch-limitations.html	3.77 KB	-rw-r--r--
textsearch-migration.html	4.92 KB	-rw-r--r--
textsearch-parsers.html	8.99 KB	-rw-r--r--
textsearch-psql.html	9.13 KB	-rw-r--r--
textsearch-tables.html	9.52 KB	-rw-r--r--
textsearch.html	5.74 KB	-rw-r--r--
transaction-iso.html	26.6 KB	-rw-r--r--
trigger-datachanges.html	4.95 KB	-rw-r--r--
trigger-definition.html	15.14 KB	-rw-r--r--
trigger-example.html	7.57 KB	-rw-r--r--
trigger-interface.html	10.47 KB	-rw-r--r--
triggers.html	3.71 KB	-rw-r--r--
tsearch2.html	9.72 KB	-rw-r--r--
tutorial-accessdb.html	6.88 KB	-rw-r--r--
tutorial-advanced-intro.html	3.26 KB	-rw-r--r--
tutorial-advanced.html	2.79 KB	-rw-r--r--
tutorial-agg.html	7.42 KB	-rw-r--r--
tutorial-arch.html	4.74 KB	-rw-r--r--
tutorial-concepts.html	3.75 KB	-rw-r--r--
tutorial-conclusion.html	2.78 KB	-rw-r--r--
tutorial-createdb.html	8.98 KB	-rw-r--r--
tutorial-delete.html	3.43 KB	-rw-r--r--
tutorial-fk.html	4.32 KB	-rw-r--r--
tutorial-inheritance.html	5.99 KB	-rw-r--r--
tutorial-install.html	4.42 KB	-rw-r--r--
tutorial-join.html	9.46 KB	-rw-r--r--
tutorial-populate.html	4.73 KB	-rw-r--r--
tutorial-select.html	7.84 KB	-rw-r--r--
tutorial-sql-intro.html	4.79 KB	-rw-r--r--
tutorial-sql.html	2.99 KB	-rw-r--r--
tutorial-start.html	2.57 KB	-rw-r--r--
tutorial-table.html	5.57 KB	-rw-r--r--
tutorial-transactions.html	9.71 KB	-rw-r--r--
tutorial-update.html	3.08 KB	-rw-r--r--
tutorial-views.html	3.3 KB	-rw-r--r--
tutorial-window.html	12.19 KB	-rw-r--r--
tutorial.html	5.09 KB	-rw-r--r--
typeconv-func.html	11.88 KB	-rw-r--r--
typeconv-oper.html	14.56 KB	-rw-r--r--
typeconv-overview.html	8.11 KB	-rw-r--r--
typeconv-query.html	5.32 KB	-rw-r--r--
typeconv-union-case.html	6.46 KB	-rw-r--r--
typeconv.html	3.63 KB	-rw-r--r--
unaccent.html	6.58 KB	-rw-r--r--
unsupported-features-sql-stand...	34.29 KB	-rw-r--r--
upgrading.html	12.5 KB	-rw-r--r--
user-manag.html	3.89 KB	-rw-r--r--
using-explain.html	40.84 KB	-rw-r--r--
uuid-ossp.html	7.06 KB	-rw-r--r--
vacuumlo.html	7.37 KB	-rw-r--r--
view-pg-available-extension-ve...	4.53 KB	-rw-r--r--
view-pg-available-extensions.h...	3.85 KB	-rw-r--r--
view-pg-cursors.html	5.54 KB	-rw-r--r--
view-pg-group.html	3.81 KB	-rw-r--r--
view-pg-indexes.html	4.06 KB	-rw-r--r--
view-pg-locks.html	14.11 KB	-rw-r--r--
view-pg-prepared-statements.ht...	4.94 KB	-rw-r--r--
view-pg-prepared-xacts.html	4.8 KB	-rw-r--r--
view-pg-roles.html	5.93 KB	-rw-r--r--
view-pg-rules.html	3.91 KB	-rw-r--r--
view-pg-seclabels.html	5 KB	-rw-r--r--
view-pg-settings.html	10.35 KB	-rw-r--r--
view-pg-shadow.html	5.25 KB	-rw-r--r--
view-pg-stats.html	8.68 KB	-rw-r--r--
view-pg-tables.html	4.72 KB	-rw-r--r--
view-pg-timezone-abbrevs.html	3.77 KB	-rw-r--r--
view-pg-timezone-names.html	4.08 KB	-rw-r--r--
view-pg-user-mappings.html	5.04 KB	-rw-r--r--
view-pg-user.html	4.41 KB	-rw-r--r--
view-pg-views.html	3.76 KB	-rw-r--r--
views-overview.html	6.39 KB	-rw-r--r--
wal-async-commit.html	8.8 KB	-rw-r--r--
wal-configuration.html	14.61 KB	-rw-r--r--
wal-internals.html	6.01 KB	-rw-r--r--
wal-intro.html	5.4 KB	-rw-r--r--
wal-reliability.html	11.21 KB	-rw-r--r--
wal.html	2.86 KB	-rw-r--r--
warm-standby-failover.html	5.96 KB	-rw-r--r--
warm-standby.html	33.83 KB	-rw-r--r--
xaggr.html	9.67 KB	-rw-r--r--
xfunc-c.html	76.68 KB	-rw-r--r--
xfunc-internal.html	3.91 KB	-rw-r--r--
xfunc-overload.html	5.77 KB	-rw-r--r--
xfunc-pl.html	2.92 KB	-rw-r--r--
xfunc-sql.html	37.14 KB	-rw-r--r--
xfunc-volatility.html	9.61 KB	-rw-r--r--
xfunc.html	4.41 KB	-rw-r--r--
xindex.html	43.55 KB	-rw-r--r--
xml2.html	16.5 KB	-rw-r--r--
xoper-optimization.html	22.6 KB	-rw-r--r--
xoper.html	4.72 KB	-rw-r--r--
xplang-install.html	10.87 KB	-rw-r--r--
xplang.html	4.14 KB	-rw-r--r--
xtypes.html	11.83 KB	-rw-r--r--

Code Editor : 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
>

${this.title}

Code Editor : sql-createtable.html