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-select.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>SELECT</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="SECURITY LABEL"
HREF="sql-security-label.html"><LINK
REL="NEXT"
TITLE="SELECT INTO"
HREF="sql-selectinto.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="SECURITY LABEL"
HREF="sql-security-label.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="SELECT INTO"
HREF="sql-selectinto.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SQL-SELECT"
></A
>SELECT</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN77583"
></A
><H2
>Name</H2
>SELECT, TABLE, WITH&nbsp;--&nbsp;retrieve rows from a table or view</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN77595"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
>[ WITH [ RECURSIVE ] <TT
CLASS="REPLACEABLE"
>with_query</TT
> [, ...] ]
SELECT [ ALL | DISTINCT [ ON ( <TT
CLASS="REPLACEABLE"
>expression</TT
> [, ...] ) ] ]
 * | <TT
CLASS="REPLACEABLE"
>expression</TT
> [ [ AS ] <TT
CLASS="REPLACEABLE"
>output_name</TT
> ] [, ...]
 [ FROM <TT
CLASS="REPLACEABLE"
>from_item</TT
> [, ...] ]
 [ WHERE <TT
CLASS="REPLACEABLE"
>condition</TT
> ]
 [ GROUP BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [, ...] ]
 [ HAVING <TT
CLASS="REPLACEABLE"
>condition</TT
> [, ...] ]
 [ WINDOW <TT
CLASS="REPLACEABLE"
>window_name</TT
> AS ( <TT
CLASS="REPLACEABLE"
>window_definition</TT
> ) [, ...] ]
 [ { UNION | INTERSECT | EXCEPT } [ ALL | DISTINCT ] <TT
CLASS="REPLACEABLE"
>select</TT
> ]
 [ ORDER BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [ ASC | DESC | USING <TT
CLASS="REPLACEABLE"
>operator</TT
> ] [ NULLS { FIRST | LAST } ] [, ...] ]
 [ LIMIT { <TT
CLASS="REPLACEABLE"
>count</TT
> | ALL } ]
 [ OFFSET <TT
CLASS="REPLACEABLE"
>start</TT
> [ ROW | ROWS ] ]
 [ FETCH { FIRST | NEXT } [ <TT
CLASS="REPLACEABLE"
>count</TT
> ] { ROW | ROWS } ONLY ]
 [ FOR { UPDATE | SHARE } [ OF <TT
CLASS="REPLACEABLE"
>table_name</TT
> [, ...] ] [ NOWAIT ] [...] ]

where <TT
CLASS="REPLACEABLE"
>from_item</TT
> can be one of:

[ ONLY ] <TT
CLASS="REPLACEABLE"
>table_name</TT
> [ * ] [ [ AS ] <TT
CLASS="REPLACEABLE"
>alias</TT
> [ ( <TT
CLASS="REPLACEABLE"
>column_alias</TT
> [, ...] ) ] ]
 ( <TT
CLASS="REPLACEABLE"
>select</TT
> ) [ AS ] <TT
CLASS="REPLACEABLE"
>alias</TT
> [ ( <TT
CLASS="REPLACEABLE"
>column_alias</TT
> [, ...] ) ]
 <TT
CLASS="REPLACEABLE"
>with_query_name</TT
> [ [ AS ] <TT
CLASS="REPLACEABLE"
>alias</TT
> [ ( <TT
CLASS="REPLACEABLE"
>column_alias</TT
> [, ...] ) ] ]
 <TT
CLASS="REPLACEABLE"
>function_name</TT
> ( [ <TT
CLASS="REPLACEABLE"
>argument</TT
> [, ...] ] ) [ AS ] <TT
CLASS="REPLACEABLE"
>alias</TT
> [ ( <TT
CLASS="REPLACEABLE"
>column_alias</TT
> [, ...] | <TT
CLASS="REPLACEABLE"
>column_definition</TT
> [, ...] ) ]
 <TT
CLASS="REPLACEABLE"
>function_name</TT
> ( [ <TT
CLASS="REPLACEABLE"
>argument</TT
> [, ...] ] ) AS ( <TT
CLASS="REPLACEABLE"
>column_definition</TT
> [, ...] )
 <TT
CLASS="REPLACEABLE"
>from_item</TT
> [ NATURAL ] <TT
CLASS="REPLACEABLE"
>join_type</TT
> <TT
CLASS="REPLACEABLE"
>from_item</TT
> [ ON <TT
CLASS="REPLACEABLE"
>join_condition</TT
> | USING ( <TT
CLASS="REPLACEABLE"
>join_column</TT
> [, ...] ) ]

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

<TT
CLASS="REPLACEABLE"
>with_query_name</TT
> [ ( <TT
CLASS="REPLACEABLE"
>column_name</TT
> [, ...] ) ] AS ( <TT
CLASS="REPLACEABLE"
>select</TT
> | <TT
CLASS="REPLACEABLE"
>values</TT
> | <TT
CLASS="REPLACEABLE"
>insert</TT
> | <TT
CLASS="REPLACEABLE"
>update</TT
> | <TT
CLASS="REPLACEABLE"
>delete</TT
> )

TABLE [ ONLY ] <TT
CLASS="REPLACEABLE"
>table_name</TT
> [ * ]</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN77648"
></A
><H2
>Description</H2
> <TT
CLASS="COMMAND"
>SELECT</TT
> retrieves rows from zero or more tables.
 The general processing of <TT
CLASS="COMMAND"
>SELECT</TT
> is as follows:

<OL
TYPE="1"
><LI
> All queries in the <TT
CLASS="LITERAL"
>WITH</TT
> list are computed.
 These effectively serve as temporary tables that can be referenced
 in the <TT
CLASS="LITERAL"
>FROM</TT
> list. A <TT
CLASS="LITERAL"
>WITH</TT
> query
 that is referenced more than once in <TT
CLASS="LITERAL"
>FROM</TT
> is
 computed only once.
 (See <A
HREF="sql-select.html#SQL-WITH"
>WITH Clause</A
> below.)
 </LI
><LI
> All elements in the <TT
CLASS="LITERAL"
>FROM</TT
> list are computed.
 (Each element in the <TT
CLASS="LITERAL"
>FROM</TT
> list is a real or
 virtual table.) If more than one element is specified in the
 <TT
CLASS="LITERAL"
>FROM</TT
> list, they are cross-joined together.
 (See <A
HREF="sql-select.html#SQL-FROM"
>FROM Clause</A
> below.)
 </LI
><LI
> If the <TT
CLASS="LITERAL"
>WHERE</TT
> clause is specified, all rows
 that do not satisfy the condition are eliminated from the
 output. (See <A
HREF="sql-select.html#SQL-WHERE"
>WHERE Clause</A
> below.)
 </LI
><LI
> If the <TT
CLASS="LITERAL"
>GROUP BY</TT
> clause is specified, the
 output is combined into groups of rows that match on one or more
 values. If the <TT
CLASS="LITERAL"
>HAVING</TT
> clause is present, it
 eliminates groups that do not satisfy the given condition. (See
 <A
HREF="sql-select.html#SQL-GROUPBY"
>GROUP BY Clause</A
> and
 <A
HREF="sql-select.html#SQL-HAVING"
>HAVING Clause</A
> below.)
 </LI
><LI
> The actual output rows are computed using the
 <TT
CLASS="COMMAND"
>SELECT</TT
> output expressions for each selected
 row or row group. (See
 <A
HREF="sql-select.html#SQL-SELECT-LIST"
>SELECT List</A
>
 below.)
 </LI
><LI
><TT
CLASS="LITERAL"
>SELECT DISTINCT</TT
> eliminates duplicate rows from the
 result. <TT
CLASS="LITERAL"
>SELECT DISTINCT ON</TT
> eliminates rows that
 match on all the specified expressions. <TT
CLASS="LITERAL"
>SELECT ALL</TT
>
 (the default) will return all candidate rows, including
 duplicates. (See <A
HREF="sql-select.html#SQL-DISTINCT"
>DISTINCT Clause</A
> below.)
 </LI
><LI
> Using the operators <TT
CLASS="LITERAL"
>UNION</TT
>,
 <TT
CLASS="LITERAL"
>INTERSECT</TT
>, and <TT
CLASS="LITERAL"
>EXCEPT</TT
>, the
 output of more than one <TT
CLASS="COMMAND"
>SELECT</TT
> statement can
 be combined to form a single result set. The
 <TT
CLASS="LITERAL"
>UNION</TT
> operator returns all rows that are in
 one or both of the result sets. The
 <TT
CLASS="LITERAL"
>INTERSECT</TT
> operator returns all rows that are
 strictly in both result sets. The <TT
CLASS="LITERAL"
>EXCEPT</TT
>
 operator returns the rows that are in the first result set but
 not in the second. In all three cases, duplicate rows are
 eliminated unless <TT
CLASS="LITERAL"
>ALL</TT
> is specified. The noise
 word <TT
CLASS="LITERAL"
>DISTINCT</TT
> can be added to explicitly specify
 eliminating duplicate rows. Notice that <TT
CLASS="LITERAL"
>DISTINCT</TT
> is
 the default behavior here, even though <TT
CLASS="LITERAL"
>ALL</TT
> is
 the default for <TT
CLASS="COMMAND"
>SELECT</TT
> itself. (See
 <A
HREF="sql-select.html#SQL-UNION"
>UNION Clause</A
>, <A
HREF="sql-select.html#SQL-INTERSECT"
>INTERSECT Clause</A
>, and
 <A
HREF="sql-select.html#SQL-EXCEPT"
>EXCEPT Clause</A
> below.)
 </LI
><LI
> If the <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause is specified, the
 returned rows are sorted in the specified order. If
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> is not given, the rows are returned
 in whatever order the system finds fastest to produce. (See
 <A
HREF="sql-select.html#SQL-ORDERBY"
>ORDER BY Clause</A
> below.)
 </LI
><LI
> If the <TT
CLASS="LITERAL"
>LIMIT</TT
> (or <TT
CLASS="LITERAL"
>FETCH FIRST</TT
>) or <TT
CLASS="LITERAL"
>OFFSET</TT
>
 clause is specified, the <TT
CLASS="COMMAND"
>SELECT</TT
> statement
 only returns a subset of the result rows. (See <A
HREF="sql-select.html#SQL-LIMIT"
>LIMIT Clause</A
> below.)
 </LI
><LI
> If <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 is specified, the
 <TT
CLASS="COMMAND"
>SELECT</TT
> statement locks the selected rows
 against concurrent updates. (See <A
HREF="sql-select.html#SQL-FOR-UPDATE-SHARE"
>FOR UPDATE/FOR SHARE Clause</A
> below.)
 </LI
></OL
>
 You must have <TT
CLASS="LITERAL"
>SELECT</TT
> privilege on each column used
 in a <TT
CLASS="COMMAND"
>SELECT</TT
> command. The use of <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>
 or <TT
CLASS="LITERAL"
>FOR SHARE</TT
> requires
 <TT
CLASS="LITERAL"
>UPDATE</TT
> privilege as well (for at least one column
 of each table so selected).
 </DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN77728"
></A
><H2
>Parameters</H2
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-WITH"
></A
><H3
><TT
CLASS="LITERAL"
>WITH</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>WITH</TT
> clause allows you to specify one or more
 subqueries that can be referenced by name in the primary query.
 The subqueries effectively act as temporary tables or views
 for the duration of the primary query.
 Each subquery can be a <TT
CLASS="COMMAND"
>SELECT</TT
>, <TT
CLASS="COMMAND"
>VALUES</TT
>,
 <TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
> or
 <TT
CLASS="COMMAND"
>DELETE</TT
> statement.
 When writing a data-modifying statement (<TT
CLASS="COMMAND"
>INSERT</TT
>,
 <TT
CLASS="COMMAND"
>UPDATE</TT
> or <TT
CLASS="COMMAND"
>DELETE</TT
>) in
 <TT
CLASS="LITERAL"
>WITH</TT
>, it is usual to include a <TT
CLASS="LITERAL"
>RETURNING</TT
> clause.
 It is the output of <TT
CLASS="LITERAL"
>RETURNING</TT
>, not the underlying
 table that the statement modifies, that forms the temporary table that is
 read by the primary query. If <TT
CLASS="LITERAL"
>RETURNING</TT
> is omitted, the
 statement is still executed, but it produces no output so it cannot be
 referenced as a table by the primary query.
 A name (without schema qualification) must be specified for each
 <TT
CLASS="LITERAL"
>WITH</TT
> query. Optionally, a list of column names
 can be specified; if this is omitted,
 the column names are inferred from the subquery.
 If <TT
CLASS="LITERAL"
>RECURSIVE</TT
> is specified, it allows a
 <TT
CLASS="COMMAND"
>SELECT</TT
> subquery to reference itself by name. Such a
 subquery must have the form
<PRE
CLASS="SYNOPSIS"
><TT
CLASS="REPLACEABLE"
>non_recursive_term</TT
> UNION [ ALL | DISTINCT ] <TT
CLASS="REPLACEABLE"
>recursive_term</TT
></PRE
>
 where the recursive self-reference must appear on the right-hand
 side of the <TT
CLASS="LITERAL"
>UNION</TT
>. Only one recursive self-reference
 is permitted per query. Recursive data-modifying statements are not
 supported, but you can use the results of a recursive
 <TT
CLASS="COMMAND"
>SELECT</TT
> query in
 a data-modifying statement. See <A
HREF="queries-with.html"
>Section 7.8</A
> for
 an example.
 Another effect of <TT
CLASS="LITERAL"
>RECURSIVE</TT
> is that
 <TT
CLASS="LITERAL"
>WITH</TT
> queries need not be ordered: a query
 can reference another one that is later in the list. (However,
 circular references, or mutual recursion, are not implemented.)
 Without <TT
CLASS="LITERAL"
>RECURSIVE</TT
>, <TT
CLASS="LITERAL"
>WITH</TT
> queries
 can only reference sibling <TT
CLASS="LITERAL"
>WITH</TT
> queries
 that are earlier in the <TT
CLASS="LITERAL"
>WITH</TT
> list.
 A key property of <TT
CLASS="LITERAL"
>WITH</TT
> queries is that they
 are evaluated only once per execution of the primary query,
 even if the primary query refers to them more than once.
 In particular, data-modifying statements are guaranteed to be
 executed once and only once, regardless of whether the primary query
 reads all or any of their output.
 The primary query and the <TT
CLASS="LITERAL"
>WITH</TT
> queries are all
 (notionally) executed at the same time. This implies that the effects of
 a data-modifying statement in <TT
CLASS="LITERAL"
>WITH</TT
> cannot be seen from
 other parts of the query, other than by reading its <TT
CLASS="LITERAL"
>RETURNING</TT
>
 output. If two such data-modifying statements attempt to modify the same
 row, the results are unspecified.
 See <A
HREF="queries-with.html"
>Section 7.8</A
> for additional information.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-FROM"
></A
><H3
><TT
CLASS="LITERAL"
>FROM</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>FROM</TT
> clause specifies one or more source
 tables for the <TT
CLASS="COMMAND"
>SELECT</TT
>. If multiple sources are
 specified, the result is the Cartesian product (cross join) of all
 the sources. But usually qualification conditions
 are added to restrict the returned rows to a small subset of the
 Cartesian product.
 The <TT
CLASS="LITERAL"
>FROM</TT
> clause can contain the following
 elements:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="REPLACEABLE"
>table_name</TT
></DT
><DD
> The name (optionally schema-qualified) of an existing table or view.
 If <TT
CLASS="LITERAL"
>ONLY</TT
> is specified before the table name, only that
 table is scanned. If <TT
CLASS="LITERAL"
>ONLY</TT
> is not specified, the table
 and all its descendant tables (if any) are scanned. Optionally,
 <TT
CLASS="LITERAL"
>*</TT
> can be specified after the table name to explicitly
 indicate that descendant tables are included.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>alias</TT
></DT
><DD
> A substitute name for the <TT
CLASS="LITERAL"
>FROM</TT
> item containing the
 alias. An alias is used for brevity or to eliminate ambiguity
 for self-joins (where the same table is scanned multiple
 times). When an alias is provided, it completely hides the
 actual name of the table or function; for example given
 <TT
CLASS="LITERAL"
>FROM foo AS f</TT
>, the remainder of the
 <TT
CLASS="COMMAND"
>SELECT</TT
> must refer to this <TT
CLASS="LITERAL"
>FROM</TT
>
 item as <TT
CLASS="LITERAL"
>f</TT
> not <TT
CLASS="LITERAL"
>foo</TT
>. If an alias is
 written, a column alias list can also be written to provide
 substitute names for one or more columns of the table.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>select</TT
></DT
><DD
> A sub-<TT
CLASS="COMMAND"
>SELECT</TT
> can appear in the
 <TT
CLASS="LITERAL"
>FROM</TT
> clause. This acts as though its
 output were created as a temporary table for the duration of
 this single <TT
CLASS="COMMAND"
>SELECT</TT
> command. Note that the
 sub-<TT
CLASS="COMMAND"
>SELECT</TT
> must be surrounded by
 parentheses, and an alias must be
 provided for it. A
 <A
HREF="sql-values.html"
>VALUES</A
> command
 can also be used here.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>with_query_name</TT
></DT
><DD
> A <TT
CLASS="LITERAL"
>WITH</TT
> query is referenced by writing its name,
 just as though the query's name were a table name. (In fact,
 the <TT
CLASS="LITERAL"
>WITH</TT
> query hides any real table of the same name
 for the purposes of the primary query. If necessary, you can
 refer to a real table of the same name by schema-qualifying
 the table's name.)
 An alias can be provided in the same way as for a table.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>function_name</TT
></DT
><DD
> Function calls can appear in the <TT
CLASS="LITERAL"
>FROM</TT
>
 clause. (This is especially useful for functions that return
 result sets, but any function can be used.) This acts as
 though its output were created as a temporary table for the
 duration of this single <TT
CLASS="COMMAND"
>SELECT</TT
> command. An
 alias can also be used. If an alias is written, a column alias
 list can also be written to provide substitute names for one
 or more attributes of the function's composite return type. If
 the function has been defined as returning the <TT
CLASS="TYPE"
>record</TT
>
 data type, then an alias or the key word <TT
CLASS="LITERAL"
>AS</TT
> must
 be present, followed by a column definition list in the form
 <TT
CLASS="LITERAL"
>( <TT
CLASS="REPLACEABLE"
>column_name</TT
> <TT
CLASS="REPLACEABLE"
>data_type</TT
> [, ... ]
 )</TT
>. The column definition list must match the actual
 number and types of columns returned by the function.
 </DD
><DT
><TT
CLASS="REPLACEABLE"
>join_type</TT
></DT
><DD
> One of
 <UL
><LI
><TT
CLASS="LITERAL"
>[ INNER ] JOIN</TT
></LI
><LI
><TT
CLASS="LITERAL"
>LEFT [ OUTER ] JOIN</TT
></LI
><LI
><TT
CLASS="LITERAL"
>RIGHT [ OUTER ] JOIN</TT
></LI
><LI
><TT
CLASS="LITERAL"
>FULL [ OUTER ] JOIN</TT
></LI
><LI
><TT
CLASS="LITERAL"
>CROSS JOIN</TT
></LI
></UL
>

For the <TT
CLASS="LITERAL"
>INNER</TT
> and <TT
CLASS="LITERAL"
>OUTER</TT
> join types, a
 join condition must be specified, namely exactly one of
 <TT
CLASS="LITERAL"
>NATURAL</TT
>, <TT
CLASS="LITERAL"
>ON <TT
CLASS="REPLACEABLE"
>join_condition</TT
></TT
>, or
 <TT
CLASS="LITERAL"
>USING (<TT
CLASS="REPLACEABLE"
>join_column</TT
> [, ...])</TT
>.
 See below for the meaning. For <TT
CLASS="LITERAL"
>CROSS JOIN</TT
>,
 none of these clauses can appear.
 A <TT
CLASS="LITERAL"
>JOIN</TT
> clause combines two
 <TT
CLASS="LITERAL"
>FROM</TT
> items. Use parentheses if necessary to
 determine the order of nesting. In the absence of parentheses,
 <TT
CLASS="LITERAL"
>JOIN</TT
>s nest left-to-right. In any case
 <TT
CLASS="LITERAL"
>JOIN</TT
> binds more tightly than the commas
 separating <TT
CLASS="LITERAL"
>FROM</TT
> items.
 <TT
CLASS="LITERAL"
>CROSS JOIN</TT
> and <TT
CLASS="LITERAL"
>INNER JOIN</TT
>
 produce a simple Cartesian product, the same result as you get from
 listing the two items at the top level of <TT
CLASS="LITERAL"
>FROM</TT
>,
 but restricted by the join condition (if any).
 <TT
CLASS="LITERAL"
>CROSS JOIN</TT
> is equivalent to <TT
CLASS="LITERAL"
>INNER JOIN ON
 (TRUE)</TT
>, that is, no rows are removed by qualification.
 These join types are just a notational convenience, since they
 do nothing you couldn't do with plain <TT
CLASS="LITERAL"
>FROM</TT
> and
 <TT
CLASS="LITERAL"
>WHERE</TT
>.
 <TT
CLASS="LITERAL"
>LEFT OUTER JOIN</TT
> returns all rows in the qualified
 Cartesian product (i.e., all combined rows that pass its join
 condition), plus one copy of each row in the left-hand table
 for which there was no right-hand row that passed the join
 condition. This left-hand row is extended to the full width
 of the joined table by inserting null values for the
 right-hand columns. Note that only the <TT
CLASS="LITERAL"
>JOIN</TT
>
 clause's own condition is considered while deciding which rows
 have matches. Outer conditions are applied afterwards.
 Conversely, <TT
CLASS="LITERAL"
>RIGHT OUTER JOIN</TT
> returns all the
 joined rows, plus one row for each unmatched right-hand row
 (extended with nulls on the left). This is just a notational
 convenience, since you could convert it to a <TT
CLASS="LITERAL"
>LEFT
 OUTER JOIN</TT
> by switching the left and right inputs.
 <TT
CLASS="LITERAL"
>FULL OUTER JOIN</TT
> returns all the joined rows, plus
 one row for each unmatched left-hand row (extended with nulls
 on the right), plus one row for each unmatched right-hand row
 (extended with nulls on the left).
 </DD
><DT
><TT
CLASS="LITERAL"
>ON <TT
CLASS="REPLACEABLE"
>join_condition</TT
></TT
></DT
><DD
><TT
CLASS="REPLACEABLE"
>join_condition</TT
> is
 an expression resulting in a value of type
 <TT
CLASS="TYPE"
>boolean</TT
> (similar to a <TT
CLASS="LITERAL"
>WHERE</TT
>
 clause) that specifies which rows in a join are considered to
 match.
 </DD
><DT
><TT
CLASS="LITERAL"
>USING ( <TT
CLASS="REPLACEABLE"
>join_column</TT
> [, ...] )</TT
></DT
><DD
> A clause of the form <TT
CLASS="LITERAL"
>USING ( a, b, ... )</TT
> is
 shorthand for <TT
CLASS="LITERAL"
>ON left_table.a = right_table.a AND
 left_table.b = right_table.b ...</TT
>. Also,
 <TT
CLASS="LITERAL"
>USING</TT
> implies that only one of each pair of
 equivalent columns will be included in the join output, not
 both.
 </DD
><DT
><TT
CLASS="LITERAL"
>NATURAL</TT
></DT
><DD
> <TT
CLASS="LITERAL"
>NATURAL</TT
> is shorthand for a
 <TT
CLASS="LITERAL"
>USING</TT
> list that mentions all columns in the two
 tables that have matching names. If there are no common
 column names, <TT
CLASS="LITERAL"
>NATURAL</TT
> is equivalent
 to <TT
CLASS="LITERAL"
>ON TRUE</TT
>.
 </DD
></DL
></DIV
>
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-WHERE"
></A
><H3
><TT
CLASS="LITERAL"
>WHERE</TT
> Clause</H3
> The optional <TT
CLASS="LITERAL"
>WHERE</TT
> clause has the general form
<PRE
CLASS="SYNOPSIS"
>WHERE <TT
CLASS="REPLACEABLE"
>condition</TT
></PRE
>
 where <TT
CLASS="REPLACEABLE"
>condition</TT
> is
 any expression that evaluates to a result of type
 <TT
CLASS="TYPE"
>boolean</TT
>. Any row that does not satisfy this
 condition will be eliminated from the output. A row satisfies the
 condition if it returns true when the actual row values are
 substituted for any variable references.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-GROUPBY"
></A
><H3
><TT
CLASS="LITERAL"
>GROUP BY</TT
> Clause</H3
> The optional <TT
CLASS="LITERAL"
>GROUP BY</TT
> clause has the general form
<PRE
CLASS="SYNOPSIS"
>GROUP BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [, ...]</PRE
>
 <TT
CLASS="LITERAL"
>GROUP BY</TT
> will condense into a single row all
 selected rows that share the same values for the grouped
 expressions. <TT
CLASS="REPLACEABLE"
>expression</TT
> can be an input column
 name, or the name or ordinal number of an output column
 (<TT
CLASS="COMMAND"
>SELECT</TT
> list item), or an arbitrary
 expression formed from input-column values. In case of ambiguity,
 a <TT
CLASS="LITERAL"
>GROUP BY</TT
> name will be interpreted as an
 input-column name rather than an output column name.
 Aggregate functions, if any are used, are computed across all rows
 making up each group, producing a separate value for each group
 (whereas without <TT
CLASS="LITERAL"
>GROUP BY</TT
>, an aggregate
 produces a single value computed across all the selected rows).
 When <TT
CLASS="LITERAL"
>GROUP BY</TT
> is present, it is not valid for
 the <TT
CLASS="COMMAND"
>SELECT</TT
> list expressions to refer to
 ungrouped columns except within aggregate functions or if the
 ungrouped column is functionally dependent on the grouped columns,
 since there would otherwise be more than one possible value to
 return for an ungrouped column. A functional dependency exists if
 the grouped columns (or a subset thereof) are the primary key of
 the table containing the ungrouped column.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-HAVING"
></A
><H3
><TT
CLASS="LITERAL"
>HAVING</TT
> Clause</H3
> The optional <TT
CLASS="LITERAL"
>HAVING</TT
> clause has the general form
<PRE
CLASS="SYNOPSIS"
>HAVING <TT
CLASS="REPLACEABLE"
>condition</TT
></PRE
>
 where <TT
CLASS="REPLACEABLE"
>condition</TT
> is
 the same as specified for the <TT
CLASS="LITERAL"
>WHERE</TT
> clause.
 <TT
CLASS="LITERAL"
>HAVING</TT
> eliminates group rows that do not
 satisfy the condition. <TT
CLASS="LITERAL"
>HAVING</TT
> is different
 from <TT
CLASS="LITERAL"
>WHERE</TT
>: <TT
CLASS="LITERAL"
>WHERE</TT
> filters
 individual rows before the application of <TT
CLASS="LITERAL"
>GROUP
 BY</TT
>, while <TT
CLASS="LITERAL"
>HAVING</TT
> filters group rows
 created by <TT
CLASS="LITERAL"
>GROUP BY</TT
>. Each column referenced in
 <TT
CLASS="REPLACEABLE"
>condition</TT
> must
 unambiguously reference a grouping column, unless the reference
 appears within an aggregate function.
 The presence of <TT
CLASS="LITERAL"
>HAVING</TT
> turns a query into a grouped
 query even if there is no <TT
CLASS="LITERAL"
>GROUP BY</TT
> clause. This is the
 same as what happens when the query contains aggregate functions but
 no <TT
CLASS="LITERAL"
>GROUP BY</TT
> clause. All the selected rows are considered to
 form a single group, and the <TT
CLASS="COMMAND"
>SELECT</TT
> list and
 <TT
CLASS="LITERAL"
>HAVING</TT
> clause can only reference table columns from
 within aggregate functions. Such a query will emit a single row if the
 <TT
CLASS="LITERAL"
>HAVING</TT
> condition is true, zero rows if it is not true.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-WINDOW"
></A
><H3
><TT
CLASS="LITERAL"
>WINDOW</TT
> Clause</H3
> The optional <TT
CLASS="LITERAL"
>WINDOW</TT
> clause has the general form
<PRE
CLASS="SYNOPSIS"
>WINDOW <TT
CLASS="REPLACEABLE"
>window_name</TT
> AS ( <TT
CLASS="REPLACEABLE"
>window_definition</TT
> ) [, ...]</PRE
>
 where <TT
CLASS="REPLACEABLE"
>window_name</TT
> is
 a name that can be referenced from <TT
CLASS="LITERAL"
>OVER</TT
> clauses or
 subsequent window definitions, and
 <TT
CLASS="REPLACEABLE"
>window_definition</TT
> is
<PRE
CLASS="SYNOPSIS"
>[ <TT
CLASS="REPLACEABLE"
>existing_window_name</TT
> ]
[ PARTITION BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [, ...] ]
[ ORDER BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [ ASC | DESC | USING <TT
CLASS="REPLACEABLE"
>operator</TT
> ] [ NULLS { FIRST | LAST } ] [, ...] ]
[ <TT
CLASS="REPLACEABLE"
>frame_clause</TT
> ]</PRE
>
 If an <TT
CLASS="REPLACEABLE"
>existing_window_name</TT
>
 is specified it must refer to an earlier entry in the <TT
CLASS="LITERAL"
>WINDOW</TT
>
 list; the new window copies its partitioning clause from that entry,
 as well as its ordering clause if any. In this case the new window cannot
 specify its own <TT
CLASS="LITERAL"
>PARTITION BY</TT
> clause, and it can specify
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> only if the copied window does not have one.
 The new window always uses its own frame clause; the copied window
 must not specify a frame clause.
 The elements of the <TT
CLASS="LITERAL"
>PARTITION BY</TT
> list are interpreted in
 much the same fashion as elements of a
 <A
HREF="sql-select.html#SQL-GROUPBY"
>GROUP BY Clause</A
>, except that
 they are always simple expressions and never the name or number of an
 output column.
 Another difference is that these expressions can contain aggregate
 function calls, which are not allowed in a regular <TT
CLASS="LITERAL"
>GROUP BY</TT
>
 clause. They are allowed here because windowing occurs after grouping
 and aggregation.
 Similarly, the elements of the <TT
CLASS="LITERAL"
>ORDER BY</TT
> list are interpreted
 in much the same fashion as elements of an
 <A
HREF="sql-select.html#SQL-ORDERBY"
>ORDER BY Clause</A
>, except that
 the expressions are always taken as simple expressions and never the name
 or number of an output column.
 The optional <TT
CLASS="REPLACEABLE"
>frame_clause</TT
> defines
 the window frame for window functions that depend on the
 frame (not all do). The window frame is a set of related rows for
 each row of the query (called the current row).
 The <TT
CLASS="REPLACEABLE"
>frame_clause</TT
> can be one of

<PRE
CLASS="SYNOPSIS"
>{ RANGE | ROWS } <TT
CLASS="REPLACEABLE"
>frame_start</TT
>
{ RANGE | ROWS } BETWEEN <TT
CLASS="REPLACEABLE"
>frame_start</TT
> AND <TT
CLASS="REPLACEABLE"
>frame_end</TT
></PRE
>

where <TT
CLASS="REPLACEABLE"
>frame_start</TT
> and <TT
CLASS="REPLACEABLE"
>frame_end</TT
> can be
 one of

<PRE
CLASS="SYNOPSIS"
>UNBOUNDED PRECEDING
<TT
CLASS="REPLACEABLE"
>value</TT
> PRECEDING
CURRENT ROW
<TT
CLASS="REPLACEABLE"
>value</TT
> FOLLOWING
UNBOUNDED FOLLOWING</PRE
>

If <TT
CLASS="REPLACEABLE"
>frame_end</TT
> is omitted it defaults to <TT
CLASS="LITERAL"
>CURRENT
 ROW</TT
>. Restrictions are that
 <TT
CLASS="REPLACEABLE"
>frame_start</TT
> cannot be <TT
CLASS="LITERAL"
>UNBOUNDED FOLLOWING</TT
>,
 <TT
CLASS="REPLACEABLE"
>frame_end</TT
> cannot be <TT
CLASS="LITERAL"
>UNBOUNDED PRECEDING</TT
>,
 and the <TT
CLASS="REPLACEABLE"
>frame_end</TT
> choice cannot appear earlier in the
 above list than the <TT
CLASS="REPLACEABLE"
>frame_start</TT
> choice &mdash; for example
 <TT
CLASS="LITERAL"
>RANGE BETWEEN CURRENT ROW AND <TT
CLASS="REPLACEABLE"
>value</TT
>
 PRECEDING</TT
> is not allowed.
 The default framing option is <TT
CLASS="LITERAL"
>RANGE UNBOUNDED PRECEDING</TT
>,
 which is the same as <TT
CLASS="LITERAL"
>RANGE BETWEEN UNBOUNDED PRECEDING AND
 CURRENT ROW</TT
>; it sets the frame to be all rows from the partition start
 up through the current row's last peer in the <TT
CLASS="LITERAL"
>ORDER BY</TT
>
 ordering (which means all rows if there is no <TT
CLASS="LITERAL"
>ORDER BY</TT
>).
 In general, <TT
CLASS="LITERAL"
>UNBOUNDED PRECEDING</TT
> means that the frame
 starts with the first row of the partition, and similarly
 <TT
CLASS="LITERAL"
>UNBOUNDED FOLLOWING</TT
> means that the frame ends with the last
 row of the partition (regardless of <TT
CLASS="LITERAL"
>RANGE</TT
> or <TT
CLASS="LITERAL"
>ROWS</TT
>
 mode). In <TT
CLASS="LITERAL"
>ROWS</TT
> mode, <TT
CLASS="LITERAL"
>CURRENT ROW</TT
>
 means that the frame starts or ends with the current row; but in
 <TT
CLASS="LITERAL"
>RANGE</TT
> mode it means that the frame starts or ends with
 the current row's first or last peer in the <TT
CLASS="LITERAL"
>ORDER BY</TT
> ordering.
 The <TT
CLASS="REPLACEABLE"
>value</TT
> <TT
CLASS="LITERAL"
>PRECEDING</TT
> and
 <TT
CLASS="REPLACEABLE"
>value</TT
> <TT
CLASS="LITERAL"
>FOLLOWING</TT
> cases are currently only
 allowed in <TT
CLASS="LITERAL"
>ROWS</TT
> mode. They indicate that the frame starts
 or ends with the row that many rows before or after the current row.
 <TT
CLASS="REPLACEABLE"
>value</TT
> must be an integer expression not
 containing any variables, aggregate functions, or window functions.
 The value must not be null or negative; but it can be zero, which
 selects the current row itself.
 Beware that the <TT
CLASS="LITERAL"
>ROWS</TT
> options can produce unpredictable
 results if the <TT
CLASS="LITERAL"
>ORDER BY</TT
> ordering does not order the rows
 uniquely. The <TT
CLASS="LITERAL"
>RANGE</TT
> options are designed to ensure that
 rows that are peers in the <TT
CLASS="LITERAL"
>ORDER BY</TT
> ordering are treated
 alike; any two peer rows will be both in or both not in the frame.
 The purpose of a <TT
CLASS="LITERAL"
>WINDOW</TT
> clause is to specify the
 behavior of window functions appearing in the query's
 <A
HREF="sql-select.html#SQL-SELECT-LIST"
>SELECT List</A
> or
 <A
HREF="sql-select.html#SQL-ORDERBY"
>ORDER BY Clause</A
>. These functions
 can reference the <TT
CLASS="LITERAL"
>WINDOW</TT
> clause entries by name
 in their <TT
CLASS="LITERAL"
>OVER</TT
> clauses. A <TT
CLASS="LITERAL"
>WINDOW</TT
> clause
 entry does not have to be referenced anywhere, however; if it is not
 used in the query it is simply ignored. It is possible to use window
 functions without any <TT
CLASS="LITERAL"
>WINDOW</TT
> clause at all, since
 a window function call can specify its window definition directly in
 its <TT
CLASS="LITERAL"
>OVER</TT
> clause. However, the <TT
CLASS="LITERAL"
>WINDOW</TT
>
 clause saves typing when the same window definition is needed for more
 than one window function.
 Window functions are described in detail in
 <A
HREF="tutorial-window.html"
>Section 3.5</A
>,
 <A
HREF="sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS"
>Section 4.2.8</A
>, and
 <A
HREF="queries-table-expressions.html#QUERIES-WINDOW"
>Section 7.2.4</A
>.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-SELECT-LIST"
></A
><H3
><TT
CLASS="COMMAND"
>SELECT</TT
> List</H3
> The <TT
CLASS="COMMAND"
>SELECT</TT
> list (between the key words
 <TT
CLASS="LITERAL"
>SELECT</TT
> and <TT
CLASS="LITERAL"
>FROM</TT
>) specifies expressions
 that form the output rows of the <TT
CLASS="COMMAND"
>SELECT</TT
>
 statement. The expressions can (and usually do) refer to columns
 computed in the <TT
CLASS="LITERAL"
>FROM</TT
> clause.
 Just as in a table, every output column of a <TT
CLASS="COMMAND"
>SELECT</TT
>
 has a name. In a simple <TT
CLASS="COMMAND"
>SELECT</TT
> this name is just
 used to label the column for display, but when the <TT
CLASS="COMMAND"
>SELECT</TT
>
 is a sub-query of a larger query, the name is seen by the larger query
 as the column name of the virtual table produced by the sub-query.
 To specify the name to use for an output column, write
 <TT
CLASS="LITERAL"
>AS</TT
> <TT
CLASS="REPLACEABLE"
>output_name</TT
>
 after the column's expression. (You can omit <TT
CLASS="LITERAL"
>AS</TT
>,
 but only if the desired output name does not match any
 PostgreSQL keyword (see <A
HREF="sql-keywords-appendix.html"
>Appendix C</A
>). For protection against possible
 future keyword additions, it is recommended that you always either
 write <TT
CLASS="LITERAL"
>AS</TT
> or double-quote the output name.)
 If you do not specify a column name, a name is chosen automatically
 by PostgreSQL. If the column's expression
 is a simple column reference then the chosen name is the same as that
 column's name. In more complex cases a function or type name may be
 used, or the system may fall back on a generated name such as
 <TT
CLASS="LITERAL"
>?column?</TT
>.
 An output column's name can be used to refer to the column's value in
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> and <TT
CLASS="LITERAL"
>GROUP BY</TT
> clauses, but not in the
 <TT
CLASS="LITERAL"
>WHERE</TT
> or <TT
CLASS="LITERAL"
>HAVING</TT
> clauses; there you must write
 out the expression instead.
 Instead of an expression, <TT
CLASS="LITERAL"
>*</TT
> can be written in
 the output list as a shorthand for all the columns of the selected
 rows. Also, you can write <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
>table_name</TT
>.*</TT
> as a
 shorthand for the columns coming from just that table. In these
 cases it is not possible to specify new names with <TT
CLASS="LITERAL"
>AS</TT
>;
 the output column names will be the same as the table columns' names.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-DISTINCT"
></A
><H3
><TT
CLASS="LITERAL"
>DISTINCT</TT
> Clause</H3
> If <TT
CLASS="LITERAL"
>SELECT DISTINCT</TT
> is specified, all duplicate rows are
 removed from the result set (one row is kept from each group of
 duplicates). <TT
CLASS="LITERAL"
>SELECT ALL</TT
> specifies the opposite: all rows are
 kept; that is the default.
 <TT
CLASS="LITERAL"
>SELECT DISTINCT ON ( <TT
CLASS="REPLACEABLE"
>expression</TT
> [, ...] )</TT
>
 keeps only the first row of each set of rows where the given
 expressions evaluate to equal. The <TT
CLASS="LITERAL"
>DISTINCT ON</TT
>
 expressions are interpreted using the same rules as for
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> (see above). Note that the "first
 row" of each set is unpredictable unless <TT
CLASS="LITERAL"
>ORDER
 BY</TT
> is used to ensure that the desired row appears first. For
 example:
<PRE
CLASS="PROGRAMLISTING"
>SELECT DISTINCT ON (location) location, time, report
 FROM weather_reports
 ORDER BY location, time DESC;</PRE
>
 retrieves the most recent weather report for each location. But
 if we had not used <TT
CLASS="LITERAL"
>ORDER BY</TT
> to force descending order
 of time values for each location, we'd have gotten a report from
 an unpredictable time for each location.
 The <TT
CLASS="LITERAL"
>DISTINCT ON</TT
> expression(s) must match the leftmost
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> expression(s). The <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause
 will normally contain additional expression(s) that determine the
 desired precedence of rows within each <TT
CLASS="LITERAL"
>DISTINCT ON</TT
> group.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-UNION"
></A
><H3
><TT
CLASS="LITERAL"
>UNION</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>UNION</TT
> clause has this general form:
<PRE
CLASS="SYNOPSIS"
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> UNION [ ALL | DISTINCT ] <TT
CLASS="REPLACEABLE"
>select_statement</TT
></PRE
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> is
 any <TT
CLASS="COMMAND"
>SELECT</TT
> statement without an <TT
CLASS="LITERAL"
>ORDER
 BY</TT
>, <TT
CLASS="LITERAL"
>LIMIT</TT
>, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>, or
 <TT
CLASS="LITERAL"
>FOR SHARE</TT
> clause.
 (<TT
CLASS="LITERAL"
>ORDER BY</TT
> and <TT
CLASS="LITERAL"
>LIMIT</TT
> can be attached to a
 subexpression if it is enclosed in parentheses. Without
 parentheses, these clauses will be taken to apply to the result of
 the <TT
CLASS="LITERAL"
>UNION</TT
>, not to its right-hand input
 expression.)
 The <TT
CLASS="LITERAL"
>UNION</TT
> operator computes the set union of
 the rows returned by the involved <TT
CLASS="COMMAND"
>SELECT</TT
>
 statements. A row is in the set union of two result sets if it
 appears in at least one of the result sets. The two
 <TT
CLASS="COMMAND"
>SELECT</TT
> statements that represent the direct
 operands of the <TT
CLASS="LITERAL"
>UNION</TT
> must produce the same
 number of columns, and corresponding columns must be of compatible
 data types.
 The result of <TT
CLASS="LITERAL"
>UNION</TT
> does not contain any duplicate
 rows unless the <TT
CLASS="LITERAL"
>ALL</TT
> option is specified.
 <TT
CLASS="LITERAL"
>ALL</TT
> prevents elimination of duplicates. (Therefore,
 <TT
CLASS="LITERAL"
>UNION ALL</TT
> is usually significantly quicker than
 <TT
CLASS="LITERAL"
>UNION</TT
>; use <TT
CLASS="LITERAL"
>ALL</TT
> when you can.)
 <TT
CLASS="LITERAL"
>DISTINCT</TT
> can be written to explicitly specify the
 default behavior of eliminating duplicate rows.
 Multiple <TT
CLASS="LITERAL"
>UNION</TT
> operators in the same
 <TT
CLASS="COMMAND"
>SELECT</TT
> statement are evaluated left to right,
 unless otherwise indicated by parentheses.
 Currently, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
> cannot be
 specified either for a <TT
CLASS="LITERAL"
>UNION</TT
> result or for any input of a
 <TT
CLASS="LITERAL"
>UNION</TT
>.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-INTERSECT"
></A
><H3
><TT
CLASS="LITERAL"
>INTERSECT</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>INTERSECT</TT
> clause has this general form:
<PRE
CLASS="SYNOPSIS"
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> INTERSECT [ ALL | DISTINCT ] <TT
CLASS="REPLACEABLE"
>select_statement</TT
></PRE
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> is
 any <TT
CLASS="COMMAND"
>SELECT</TT
> statement without an <TT
CLASS="LITERAL"
>ORDER
 BY</TT
>, <TT
CLASS="LITERAL"
>LIMIT</TT
>, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>, or
 <TT
CLASS="LITERAL"
>FOR SHARE</TT
> clause.
 The <TT
CLASS="LITERAL"
>INTERSECT</TT
> operator computes the set
 intersection of the rows returned by the involved
 <TT
CLASS="COMMAND"
>SELECT</TT
> statements. A row is in the
 intersection of two result sets if it appears in both result sets.
 The result of <TT
CLASS="LITERAL"
>INTERSECT</TT
> does not contain any
 duplicate rows unless the <TT
CLASS="LITERAL"
>ALL</TT
> option is specified.
 With <TT
CLASS="LITERAL"
>ALL</TT
>, a row that has <TT
CLASS="REPLACEABLE"
>m</TT
> duplicates in the
 left table and <TT
CLASS="REPLACEABLE"
>n</TT
> duplicates in the right table will appear
 min(<TT
CLASS="REPLACEABLE"
>m</TT
>,<TT
CLASS="REPLACEABLE"
>n</TT
>) times in the result set.
 <TT
CLASS="LITERAL"
>DISTINCT</TT
> can be written to explicitly specify the
 default behavior of eliminating duplicate rows.
 Multiple <TT
CLASS="LITERAL"
>INTERSECT</TT
> operators in the same
 <TT
CLASS="COMMAND"
>SELECT</TT
> statement are evaluated left to right,
 unless parentheses dictate otherwise.
 <TT
CLASS="LITERAL"
>INTERSECT</TT
> binds more tightly than
 <TT
CLASS="LITERAL"
>UNION</TT
>. That is, <TT
CLASS="LITERAL"
>A UNION B INTERSECT
 C</TT
> will be read as <TT
CLASS="LITERAL"
>A UNION (B INTERSECT
 C)</TT
>.
 Currently, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
> cannot be
 specified either for an <TT
CLASS="LITERAL"
>INTERSECT</TT
> result or for any input of
 an <TT
CLASS="LITERAL"
>INTERSECT</TT
>.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-EXCEPT"
></A
><H3
><TT
CLASS="LITERAL"
>EXCEPT</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>EXCEPT</TT
> clause has this general form:
<PRE
CLASS="SYNOPSIS"
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> EXCEPT [ ALL | DISTINCT ] <TT
CLASS="REPLACEABLE"
>select_statement</TT
></PRE
><TT
CLASS="REPLACEABLE"
>select_statement</TT
> is
 any <TT
CLASS="COMMAND"
>SELECT</TT
> statement without an <TT
CLASS="LITERAL"
>ORDER
 BY</TT
>, <TT
CLASS="LITERAL"
>LIMIT</TT
>, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>, or
 <TT
CLASS="LITERAL"
>FOR SHARE</TT
> clause.
 The <TT
CLASS="LITERAL"
>EXCEPT</TT
> operator computes the set of rows
 that are in the result of the left <TT
CLASS="COMMAND"
>SELECT</TT
>
 statement but not in the result of the right one.
 The result of <TT
CLASS="LITERAL"
>EXCEPT</TT
> does not contain any
 duplicate rows unless the <TT
CLASS="LITERAL"
>ALL</TT
> option is specified.
 With <TT
CLASS="LITERAL"
>ALL</TT
>, a row that has <TT
CLASS="REPLACEABLE"
>m</TT
> duplicates in the
 left table and <TT
CLASS="REPLACEABLE"
>n</TT
> duplicates in the right table will appear
 max(<TT
CLASS="REPLACEABLE"
>m</TT
>-<TT
CLASS="REPLACEABLE"
>n</TT
>,0) times in the result set.
 <TT
CLASS="LITERAL"
>DISTINCT</TT
> can be written to explicitly specify the
 default behavior of eliminating duplicate rows.
 Multiple <TT
CLASS="LITERAL"
>EXCEPT</TT
> operators in the same
 <TT
CLASS="COMMAND"
>SELECT</TT
> statement are evaluated left to right,
 unless parentheses dictate otherwise. <TT
CLASS="LITERAL"
>EXCEPT</TT
> binds at
 the same level as <TT
CLASS="LITERAL"
>UNION</TT
>.
 Currently, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
> cannot be
 specified either for an <TT
CLASS="LITERAL"
>EXCEPT</TT
> result or for any input of
 an <TT
CLASS="LITERAL"
>EXCEPT</TT
>.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-ORDERBY"
></A
><H3
><TT
CLASS="LITERAL"
>ORDER BY</TT
> Clause</H3
> The optional <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause has this general form:
<PRE
CLASS="SYNOPSIS"
>ORDER BY <TT
CLASS="REPLACEABLE"
>expression</TT
> [ ASC | DESC | USING <TT
CLASS="REPLACEABLE"
>operator</TT
> ] [ NULLS { FIRST | LAST } ] [, ...]</PRE
>
 The <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause causes the result rows to
 be sorted according to the specified expression(s). If two rows are
 equal according to the leftmost expression, they are compared
 according to the next expression and so on. If they are equal
 according to all specified expressions, they are returned in
 an implementation-dependent order.
 Each <TT
CLASS="REPLACEABLE"
>expression</TT
> can be the
 name or ordinal number of an output column
 (<TT
CLASS="COMMAND"
>SELECT</TT
> list item), or it can be an arbitrary
 expression formed from input-column values.
 The ordinal number refers to the ordinal (left-to-right) position
 of the output column. This feature makes it possible to define an
 ordering on the basis of a column that does not have a unique
 name. This is never absolutely necessary because it is always
 possible to assign a name to an output column using the
 <TT
CLASS="LITERAL"
>AS</TT
> clause.
 It is also possible to use arbitrary expressions in the
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause, including columns that do not
 appear in the <TT
CLASS="COMMAND"
>SELECT</TT
> output list. Thus the
 following statement is valid:
<PRE
CLASS="PROGRAMLISTING"
>SELECT name FROM distributors ORDER BY code;</PRE
>
 A limitation of this feature is that an <TT
CLASS="LITERAL"
>ORDER BY</TT
>
 clause applying to the result of a <TT
CLASS="LITERAL"
>UNION</TT
>,
 <TT
CLASS="LITERAL"
>INTERSECT</TT
>, or <TT
CLASS="LITERAL"
>EXCEPT</TT
> clause can only
 specify an output column name or number, not an expression.
 If an <TT
CLASS="LITERAL"
>ORDER BY</TT
> expression is a simple name that
 matches both an output column name and an input column name,
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> will interpret it as the output column name.
 This is the opposite of the choice that <TT
CLASS="LITERAL"
>GROUP BY</TT
> will
 make in the same situation. This inconsistency is made to be
 compatible with the SQL standard.
 Optionally one can add the key word <TT
CLASS="LITERAL"
>ASC</TT
> (ascending) or
 <TT
CLASS="LITERAL"
>DESC</TT
> (descending) after any expression in the
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause. If not specified, <TT
CLASS="LITERAL"
>ASC</TT
> is
 assumed by default. Alternatively, a specific ordering operator
 name can be specified in the <TT
CLASS="LITERAL"
>USING</TT
> clause.
 An ordering operator must be a less-than or greater-than
 member of some B-tree operator family.
 <TT
CLASS="LITERAL"
>ASC</TT
> is usually equivalent to <TT
CLASS="LITERAL"
>USING &lt;</TT
> and
 <TT
CLASS="LITERAL"
>DESC</TT
> is usually equivalent to <TT
CLASS="LITERAL"
>USING &gt;</TT
>.
 (But the creator of a user-defined data type can define exactly what the
 default sort ordering is, and it might correspond to operators with other
 names.)
 If <TT
CLASS="LITERAL"
>NULLS LAST</TT
> is specified, null values sort after all
 non-null values; if <TT
CLASS="LITERAL"
>NULLS FIRST</TT
> is specified, null values
 sort before all non-null values. If neither is specified, the default
 behavior is <TT
CLASS="LITERAL"
>NULLS LAST</TT
> when <TT
CLASS="LITERAL"
>ASC</TT
> is specified
 or implied, and <TT
CLASS="LITERAL"
>NULLS FIRST</TT
> when <TT
CLASS="LITERAL"
>DESC</TT
> is specified
 (thus, the default is to act as though nulls are larger than non-nulls).
 When <TT
CLASS="LITERAL"
>USING</TT
> is specified, the default nulls ordering depends
 on whether the operator is a less-than or greater-than operator.
 Note that ordering options apply only to the expression they follow;
 for example <TT
CLASS="LITERAL"
>ORDER BY x, y DESC</TT
> does not mean
 the same thing as <TT
CLASS="LITERAL"
>ORDER BY x DESC, y DESC</TT
>.
 Character-string data is sorted according to the collation that applies
 to the column being sorted. That can be overridden at need by including
 a <TT
CLASS="LITERAL"
>COLLATE</TT
> clause in the
 <TT
CLASS="REPLACEABLE"
>expression</TT
>, for example
 <TT
CLASS="LITERAL"
>ORDER BY mycolumn COLLATE "en_US"</TT
>.
 For more information see <A
HREF="sql-expressions.html#SQL-SYNTAX-COLLATE-EXPRS"
>Section 4.2.10</A
> and
 <A
HREF="collation.html"
>Section 22.2</A
>.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-LIMIT"
></A
><H3
><TT
CLASS="LITERAL"
>LIMIT</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>LIMIT</TT
> clause consists of two independent
 sub-clauses:
<PRE
CLASS="SYNOPSIS"
>LIMIT { <TT
CLASS="REPLACEABLE"
>count</TT
> | ALL }
OFFSET <TT
CLASS="REPLACEABLE"
>start</TT
></PRE
>
 <TT
CLASS="REPLACEABLE"
>count</TT
> specifies the
 maximum number of rows to return, while <TT
CLASS="REPLACEABLE"
>start</TT
> specifies the number of rows
 to skip before starting to return rows. When both are specified,
 <TT
CLASS="REPLACEABLE"
>start</TT
> rows are skipped
 before starting to count the <TT
CLASS="REPLACEABLE"
>count</TT
> rows to be returned.
 If the <TT
CLASS="REPLACEABLE"
>count</TT
> expression
 evaluates to NULL, it is treated as <TT
CLASS="LITERAL"
>LIMIT ALL</TT
>, i.e., no
 limit. If <TT
CLASS="REPLACEABLE"
>start</TT
> evaluates
 to NULL, it is treated the same as <TT
CLASS="LITERAL"
>OFFSET 0</TT
>.
 SQL:2008 introduced a different syntax to achieve the same result,
 which PostgreSQL also supports. It is:
<PRE
CLASS="SYNOPSIS"
>OFFSET <TT
CLASS="REPLACEABLE"
>start</TT
> { ROW | ROWS }
FETCH { FIRST | NEXT } [ <TT
CLASS="REPLACEABLE"
>count</TT
> ] { ROW | ROWS } ONLY</PRE
>
 In this syntax, to write anything except a simple integer constant for
 <TT
CLASS="REPLACEABLE"
>start</TT
> or <TT
CLASS="REPLACEABLE"
>count</TT
>, you must write parentheses
 around it.
 If <TT
CLASS="REPLACEABLE"
>count</TT
> is
 omitted in a <TT
CLASS="LITERAL"
>FETCH</TT
> clause, it defaults to 1.
 <TT
CLASS="LITERAL"
>ROW</TT
>
 and <TT
CLASS="LITERAL"
>ROWS</TT
> as well as <TT
CLASS="LITERAL"
>FIRST</TT
>
 and <TT
CLASS="LITERAL"
>NEXT</TT
> are noise words that don't influence
 the effects of these clauses.
 According to the standard, the <TT
CLASS="LITERAL"
>OFFSET</TT
> clause must come
 before the <TT
CLASS="LITERAL"
>FETCH</TT
> clause if both are present; but
 PostgreSQL is laxer and allows either order.
 When using <TT
CLASS="LITERAL"
>LIMIT</TT
>, it is a good idea to use an
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause that constrains the result rows into a
 unique order. Otherwise you will get an unpredictable subset of
 the query's rows &mdash; you might be asking for the tenth through
 twentieth rows, but tenth through twentieth in what ordering? You
 don't know what ordering unless you specify <TT
CLASS="LITERAL"
>ORDER BY</TT
>.
 The query planner takes <TT
CLASS="LITERAL"
>LIMIT</TT
> into account when
 generating a query plan, so you are very likely to get different
 plans (yielding different row orders) depending on what you use
 for <TT
CLASS="LITERAL"
>LIMIT</TT
> and <TT
CLASS="LITERAL"
>OFFSET</TT
>. Thus, using
 different <TT
CLASS="LITERAL"
>LIMIT</TT
>/<TT
CLASS="LITERAL"
>OFFSET</TT
> values to select
 different subsets of a query result will give
 inconsistent results unless you enforce a predictable
 result ordering with <TT
CLASS="LITERAL"
>ORDER BY</TT
>. This is not a bug; it
 is an inherent consequence of the fact that SQL does not promise
 to deliver the results of a query in any particular order unless
 <TT
CLASS="LITERAL"
>ORDER BY</TT
> is used to constrain the order.
 It is even possible for repeated executions of the same <TT
CLASS="LITERAL"
>LIMIT</TT
>
 query to return different subsets of the rows of a table, if there
 is not an <TT
CLASS="LITERAL"
>ORDER BY</TT
> to enforce selection of a deterministic
 subset. Again, this is not a bug; determinism of the results is
 simply not guaranteed in such a case.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-FOR-UPDATE-SHARE"
></A
><H3
><TT
CLASS="LITERAL"
>FOR UPDATE</TT
>/<TT
CLASS="LITERAL"
>FOR SHARE</TT
> Clause</H3
> The <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> clause has this form:
<PRE
CLASS="SYNOPSIS"
>FOR UPDATE [ OF <TT
CLASS="REPLACEABLE"
>table_name</TT
> [, ...] ] [ NOWAIT ]</PRE
>
 The closely related <TT
CLASS="LITERAL"
>FOR SHARE</TT
> clause has this form:
<PRE
CLASS="SYNOPSIS"
>FOR SHARE [ OF <TT
CLASS="REPLACEABLE"
>table_name</TT
> [, ...] ] [ NOWAIT ]</PRE
>
 <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> causes the rows retrieved by the
 <TT
CLASS="COMMAND"
>SELECT</TT
> statement to be locked as though for
 update. This prevents them from being modified or deleted by
 other transactions until the current transaction ends. That is,
 other transactions that attempt <TT
CLASS="COMMAND"
>UPDATE</TT
>,
 <TT
CLASS="COMMAND"
>DELETE</TT
>, or <TT
CLASS="COMMAND"
>SELECT FOR UPDATE</TT
>
 of these rows will be blocked until the current transaction ends.
 Also, if an <TT
CLASS="COMMAND"
>UPDATE</TT
>, <TT
CLASS="COMMAND"
>DELETE</TT
>,
 or <TT
CLASS="COMMAND"
>SELECT FOR UPDATE</TT
> from another transaction
 has already locked a selected row or rows, <TT
CLASS="COMMAND"
>SELECT FOR
 UPDATE</TT
> will wait for the other transaction to complete,
 and will then lock and return the updated row (or no row, if the
 row was deleted). Within a <TT
CLASS="LITERAL"
>REPEATABLE READ</TT
> or <TT
CLASS="LITERAL"
>SERIALIZABLE</TT
> transaction,
 however, an error will be thrown if a row to be locked has changed
 since the transaction started. For further discussion see <A
HREF="mvcc.html"
>Chapter 13</A
>.
 <TT
CLASS="LITERAL"
>FOR SHARE</TT
> behaves similarly, except that it
 acquires a shared rather than exclusive lock on each retrieved
 row. A shared lock blocks other transactions from performing
 <TT
CLASS="COMMAND"
>UPDATE</TT
>, <TT
CLASS="COMMAND"
>DELETE</TT
>, or <TT
CLASS="COMMAND"
>SELECT
 FOR UPDATE</TT
> on these rows, but it does not prevent them
 from performing <TT
CLASS="COMMAND"
>SELECT FOR SHARE</TT
>.
 To prevent the operation from waiting for other transactions to commit,
 use the <TT
CLASS="LITERAL"
>NOWAIT</TT
> option. With <TT
CLASS="LITERAL"
>NOWAIT</TT
>, the statement
 reports an error, rather than waiting, if a selected row
 cannot be locked immediately. Note that <TT
CLASS="LITERAL"
>NOWAIT</TT
> applies only
 to the row-level lock(s) &mdash; the required <TT
CLASS="LITERAL"
>ROW SHARE</TT
>
 table-level lock is still taken in the ordinary way (see
 <A
HREF="mvcc.html"
>Chapter 13</A
>). You can use
 <A
HREF="sql-lock.html"
>LOCK</A
>
 with the <TT
CLASS="LITERAL"
>NOWAIT</TT
> option first,
 if you need to acquire the table-level lock without waiting.
 If specific tables are named in <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>
 or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>,
 then only rows coming from those tables are locked; any other
 tables used in the <TT
CLASS="COMMAND"
>SELECT</TT
> are simply read as
 usual. A <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 clause without a table list affects all tables used in the statement.
 If <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
> is
 applied to a view or sub-query, it affects all tables used in
 the view or sub-query.
 However, <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>/<TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 do not apply to <TT
CLASS="LITERAL"
>WITH</TT
> queries referenced by the primary query.
 If you want row locking to occur within a <TT
CLASS="LITERAL"
>WITH</TT
> query, specify
 <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
> within the
 <TT
CLASS="LITERAL"
>WITH</TT
> query.
 Multiple <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 clauses can be written if it is necessary to specify different locking
 behavior for different tables. If the same table is mentioned (or
 implicitly affected) by both <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and
 <TT
CLASS="LITERAL"
>FOR SHARE</TT
> clauses, then it is processed as
 <TT
CLASS="LITERAL"
>FOR UPDATE</TT
>. Similarly, a table is processed
 as <TT
CLASS="LITERAL"
>NOWAIT</TT
> if that is specified in any of the clauses
 affecting it.
 <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
> cannot be
 used in contexts where returned rows cannot be clearly identified with
 individual table rows; for example they cannot be used with aggregation.
 When <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 appears at the top level of a <TT
CLASS="COMMAND"
>SELECT</TT
> query, the rows that
 are locked are exactly those that are returned by the query; in the
 case of a join query, the rows locked are those that contribute to
 returned join rows. In addition, rows that satisfied the query
 conditions as of the query snapshot will be locked, although they
 will not be returned if they were updated after the snapshot
 and no longer satisfy the query conditions. If a
 <TT
CLASS="LITERAL"
>LIMIT</TT
> is used, locking stops
 once enough rows have been returned to satisfy the limit (but note that
 rows skipped over by <TT
CLASS="LITERAL"
>OFFSET</TT
> will get locked). Similarly,
 if <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 is used in a cursor's query, only rows actually fetched or stepped past
 by the cursor will be locked.
 When <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> or <TT
CLASS="LITERAL"
>FOR SHARE</TT
>
 appears in a sub-<TT
CLASS="COMMAND"
>SELECT</TT
>, the rows locked are those
 returned to the outer query by the sub-query. This might involve
 fewer rows than inspection of the sub-query alone would suggest,
 since conditions from the outer query might be used to optimize
 execution of the sub-query. For example,
<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM (SELECT * FROM mytable FOR UPDATE) ss WHERE col1 = 5;</PRE
>
 will lock only rows having <TT
CLASS="LITERAL"
>col1 = 5</TT
>, even though that
 condition is not textually within the sub-query.
 <DIV
CLASS="CAUTION"
><TABLE
CLASS="CAUTION"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
>Caution</TD
></TR
><TR
><TD
ALIGN="LEFT"
> Avoid locking a row and then modifying it within a later savepoint or
 PL/pgSQL exception block. A subsequent
 rollback would cause the lock to be lost. For example:
<PRE
CLASS="PROGRAMLISTING"
>BEGIN;
SELECT * FROM mytable WHERE key = 1 FOR UPDATE;
SAVEPOINT s;
UPDATE mytable SET ... WHERE key = 1;
ROLLBACK TO s;</PRE
>
 After the <TT
CLASS="COMMAND"
>ROLLBACK</TT
>, the row is effectively unlocked, rather
 than returned to its pre-savepoint state of being locked but not modified.
 This hazard occurs if a row locked in the current transaction is updated
 or deleted, or if a shared lock is upgraded to exclusive: in all these
 cases, the former lock state is forgotten. If the transaction is then
 rolled back to a state between the original locking command and the
 subsequent change, the row will appear not to be locked at all. This is
 an implementation deficiency which will be addressed in a future release
 of PostgreSQL.
 </TD
></TR
></TABLE
></DIV
><DIV
CLASS="CAUTION"
><TABLE
CLASS="CAUTION"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
>Caution</TD
></TR
><TR
><TD
ALIGN="LEFT"
> It is possible for a <TT
CLASS="COMMAND"
>SELECT</TT
> command running at the <TT
CLASS="LITERAL"
>READ
 COMMITTED</TT
> transaction isolation level and using <TT
CLASS="LITERAL"
>ORDER
 BY</TT
> and <TT
CLASS="LITERAL"
>FOR UPDATE/SHARE</TT
> to return rows out of
 order. This is because <TT
CLASS="LITERAL"
>ORDER BY</TT
> is applied first.
 The command sorts the result, but might then block trying to obtain a lock
 on one or more of the rows. Once the <TT
CLASS="LITERAL"
>SELECT</TT
> unblocks, some
 of the ordering column values might have been modified, leading to those
 rows appearing to be out of order (though they are in order in terms
 of the original column values). This can be worked around at need by
 placing the <TT
CLASS="LITERAL"
>FOR UPDATE/SHARE</TT
> clause in a sub-query,
 for example
<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM (SELECT * FROM mytable FOR UPDATE) ss ORDER BY column1;</PRE
>
 Note that this will result in locking all rows of <TT
CLASS="STRUCTNAME"
>mytable</TT
>,
 whereas <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> at the top level would lock only the
 actually returned rows. This can make for a significant performance
 difference, particularly if the <TT
CLASS="LITERAL"
>ORDER BY</TT
> is combined with
 <TT
CLASS="LITERAL"
>LIMIT</TT
> or other restrictions. So this technique is recommended
 only if concurrent updates of the ordering columns are expected and a
 strictly sorted result is required.
 At the <TT
CLASS="LITERAL"
>REPEATABLE READ</TT
> or <TT
CLASS="LITERAL"
>SERIALIZABLE</TT
>
 transaction isolation level this would cause a serialization failure (with
 a <TT
CLASS="LITERAL"
>SQLSTATE</TT
> of <TT
CLASS="LITERAL"
>'40001'</TT
>), so there is
 no possibility of receiving rows out of order under these isolation levels.
 </TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="REFSECT2"
><A
NAME="SQL-TABLE"
></A
><H3
><TT
CLASS="LITERAL"
>TABLE</TT
> Command</H3
> The command
<PRE
CLASS="PROGRAMLISTING"
>TABLE <TT
CLASS="REPLACEABLE"
>name</TT
></PRE
>
 is completely equivalent to
<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM <TT
CLASS="REPLACEABLE"
>name</TT
></PRE
>
 It can be used as a top-level command or as a space-saving syntax
 variant in parts of complex queries.
 </DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN78429"
></A
><H2
>Examples</H2
> To join the table <TT
CLASS="LITERAL"
>films</TT
> with the table
 <TT
CLASS="LITERAL"
>distributors</TT
>:

<PRE
CLASS="PROGRAMLISTING"
>SELECT f.title, f.did, d.name, f.date_prod, f.kind
 FROM distributors d, films f
 WHERE f.did = d.did

<PRE
CLASS="PROGRAMLISTING"
>SELECT kind, sum(len) AS total FROM films GROUP BY kind;

<PRE
CLASS="PROGRAMLISTING"
>SELECT kind, sum(len) AS total
 FROM films
 GROUP BY kind
 HAVING sum(len) &lt; interval '5 hours';

kind | total
----------+-------
 Comedy | 02:58
 Romantic | 04:38</PRE
>
 The following two examples are identical ways of sorting the individual
 results according to the contents of the second column
 (<TT
CLASS="LITERAL"
>name</TT
>):

<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM distributors ORDER BY name;
SELECT * FROM distributors ORDER BY 2;

SELECT distributors.name
    FROM distributors
    WHERE distributors.name LIKE 'W%'
UNION
SELECT actors.name
    FROM actors
    WHERE actors.name LIKE 'W%';

name
----------------
 Walt Disney
 Walter Matthau
 Warner Bros.
 Warren Beatty
 Westward
 Woody Allen</PRE
>
 This example shows how to use a function in the <TT
CLASS="LITERAL"
>FROM</TT
>
 clause, both with and without a column definition list:

<PRE
CLASS="PROGRAMLISTING"
>CREATE FUNCTION distributors(int) RETURNS SETOF distributors AS $$
 SELECT * FROM distributors WHERE did = $1;
$$ LANGUAGE SQL;

SELECT * FROM distributors(111);
 did |    name
-----+-------------
 111 | Walt Disney

CREATE FUNCTION distributors_2(int) RETURNS SETOF record AS $$
    SELECT * FROM distributors WHERE did = $1;
$$ LANGUAGE SQL;

SELECT * FROM distributors_2(111) AS (f1 int, f2 text);
 f1 | f2
-----+-------------
 111 | Walt Disney</PRE
>
 This example shows how to use a simple <TT
CLASS="LITERAL"
>WITH</TT
> clause:

<PRE
CLASS="PROGRAMLISTING"
>WITH t AS (
 SELECT random() as x FROM generate_series(1, 3)
 )
SELECT * FROM t
UNION ALL
SELECT * FROM t

x 
--------------------
 0.534150459803641
 0.520092216785997
 0.0735620250925422
 0.534150459803641
 0.520092216785997
 0.0735620250925422</PRE
>

Notice that the <TT
CLASS="LITERAL"
>WITH</TT
> query was evaluated only once,
 so that we got two sets of the same three random values.
 This example uses <TT
CLASS="LITERAL"
>WITH RECURSIVE</TT
> to find all
 subordinates (direct or indirect) of the employee Mary, and their
 level of indirectness, from a table that shows only direct
 subordinates:

<PRE
CLASS="PROGRAMLISTING"
>WITH RECURSIVE employee_recursive(distance, employee_name, manager_name) AS (
 SELECT 1, employee_name, manager_name
 FROM employee
 WHERE manager_name = 'Mary'
 UNION ALL
 SELECT er.distance + 1, e.employee_name, e.manager_name
 FROM employee_recursive er, employee e
 WHERE er.employee_name = e.manager_name
 )
SELECT distance, employee_name FROM employee_recursive;</PRE
>

Notice the typical form of recursive queries:
 an initial condition, followed by <TT
CLASS="LITERAL"
>UNION</TT
>,
 followed by the recursive part of the query. Be sure that the
 recursive part of the query will eventually return no tuples, or
 else the query will loop indefinitely. (See <A
HREF="queries-with.html"
>Section 7.8</A
>
 for more examples.)
 </DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN78463"
></A
><H2
>Compatibility</H2
> Of course, the <TT
CLASS="COMMAND"
>SELECT</TT
> statement is compatible
 with the SQL standard. But there are some extensions and some
 missing features.
 <DIV
CLASS="REFSECT2"
><A
NAME="AEN78467"
></A
><H3
>Omitted <TT
CLASS="LITERAL"
>FROM</TT
> Clauses</H3
> PostgreSQL allows one to omit the
 <TT
CLASS="LITERAL"
>FROM</TT
> clause. It has a straightforward use to
 compute the results of simple expressions:
<PRE
CLASS="PROGRAMLISTING"
>SELECT 2+2;

?column?
----------
 4</PRE
>
 Some other <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> databases cannot do this except
 by introducing a dummy one-row table from which to do the
 <TT
CLASS="COMMAND"
>SELECT</TT
>.
 Note that if a <TT
CLASS="LITERAL"
>FROM</TT
> clause is not specified,
 the query cannot reference any database tables. For example, the
 following query is invalid:
<PRE
CLASS="PROGRAMLISTING"
>SELECT distributors.* WHERE distributors.name = 'Westward';</PRE
>PostgreSQL releases prior to
 8.1 would accept queries of this form, and add an implicit entry
 to the query's <TT
CLASS="LITERAL"
>FROM</TT
> clause for each table
 referenced by the query. This is no longer allowed.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78481"
></A
><H3
>Omitting the <TT
CLASS="LITERAL"
>AS</TT
> Key Word</H3
> In the SQL standard, the optional key word <TT
CLASS="LITERAL"
>AS</TT
> can be
 omitted before an output column name whenever the new column name
 is a valid column name (that is, not the same as any reserved
 keyword). PostgreSQL is slightly more
 restrictive: <TT
CLASS="LITERAL"
>AS</TT
> is required if the new column name
 matches any keyword at all, reserved or not. Recommended practice is
 to use <TT
CLASS="LITERAL"
>AS</TT
> or double-quote output column names, to prevent
 any possible conflict against future keyword additions.
 In <TT
CLASS="LITERAL"
>FROM</TT
> items, both the standard and
 PostgreSQL allow <TT
CLASS="LITERAL"
>AS</TT
> to
 be omitted before an alias that is an unreserved keyword. But
 this is impractical for output column names, because of syntactic
 ambiguities.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78493"
></A
><H3
><TT
CLASS="LITERAL"
>ONLY</TT
> and Inheritance</H3
> The SQL standard requires parentheses around the table name when
 writing <TT
CLASS="LITERAL"
>ONLY</TT
>, for example <TT
CLASS="LITERAL"
>SELECT * FROM ONLY
 (tab1), ONLY (tab2) WHERE ...</TT
>. PostgreSQL
 considers these parentheses to be optional.
 PostgreSQL allows a trailing <TT
CLASS="LITERAL"
>*</TT
> to be written to
 explicitly specify the non-<TT
CLASS="LITERAL"
>ONLY</TT
> behavior of including
 child tables. The standard does not allow this.
 (These points apply equally to all SQL commands supporting the
 <TT
CLASS="LITERAL"
>ONLY</TT
> option.)
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78506"
></A
><H3
>Namespace Available to <TT
CLASS="LITERAL"
>GROUP BY</TT
> and <TT
CLASS="LITERAL"
>ORDER BY</TT
></H3
> In the SQL-92 standard, an <TT
CLASS="LITERAL"
>ORDER BY</TT
> clause can
 only use output column names or numbers, while a <TT
CLASS="LITERAL"
>GROUP
 BY</TT
> clause can only use expressions based on input column
 names. PostgreSQL extends each of
 these clauses to allow the other choice as well (but it uses the
 standard's interpretation if there is ambiguity).
 PostgreSQL also allows both clauses to
 specify arbitrary expressions. Note that names appearing in an
 expression will always be taken as input-column names, not as
 output-column names.
 SQL:1999 and later use a slightly different definition which is not
 entirely upward compatible with SQL-92.
 In most cases, however, PostgreSQL
 will interpret an <TT
CLASS="LITERAL"
>ORDER BY</TT
> or <TT
CLASS="LITERAL"
>GROUP
 BY</TT
> expression the same way SQL:1999 does.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78519"
></A
><H3
>Functional Dependencies</H3
> PostgreSQL recognizes functional dependency
 (allowing columns to be omitted from <TT
CLASS="LITERAL"
>GROUP BY</TT
>) only when
 a table's primary key is included in the <TT
CLASS="LITERAL"
>GROUP BY</TT
> list.
 The SQL standard specifies additional conditions that should be
 recognized.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78525"
></A
><H3
><TT
CLASS="LITERAL"
>WINDOW</TT
> Clause Restrictions</H3
> The SQL standard provides additional options for the window
 <TT
CLASS="REPLACEABLE"
>frame_clause</TT
>.
 PostgreSQL currently supports only the
 options listed above.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78531"
></A
><H3
><TT
CLASS="LITERAL"
>LIMIT</TT
> and <TT
CLASS="LITERAL"
>OFFSET</TT
></H3
> The clauses <TT
CLASS="LITERAL"
>LIMIT</TT
> and <TT
CLASS="LITERAL"
>OFFSET</TT
>
 are PostgreSQL-specific syntax, also
 used by MySQL. The SQL:2008 standard
 has introduced the clauses <TT
CLASS="LITERAL"
>OFFSET ... FETCH {FIRST|NEXT}
 ...</TT
> for the same functionality, as shown above
 in <A
HREF="sql-select.html#SQL-LIMIT"
>LIMIT Clause</A
>. This
 syntax is also used by IBM DB2.
 (Applications written for Oracle
 frequently use a workaround involving the automatically
 generated <TT
CLASS="LITERAL"
>rownum</TT
> column, which is not available in
 PostgreSQL, to implement the effects of these clauses.)
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78545"
></A
><H3
><TT
CLASS="LITERAL"
>FOR UPDATE</TT
> and <TT
CLASS="LITERAL"
>FOR SHARE</TT
></H3
> Although <TT
CLASS="LITERAL"
>FOR UPDATE</TT
> appears in the SQL standard, the
 standard allows it only as an option of <TT
CLASS="COMMAND"
>DECLARE CURSOR</TT
>.
 PostgreSQL allows it in any <TT
CLASS="COMMAND"
>SELECT</TT
>
 query as well as in sub-<TT
CLASS="COMMAND"
>SELECT</TT
>s, but this is an extension.
 The <TT
CLASS="LITERAL"
>FOR SHARE</TT
> variant, and the <TT
CLASS="LITERAL"
>NOWAIT</TT
> option,
 do not appear in the standard.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78557"
></A
><H3
>Data-Modifying Statements in <TT
CLASS="LITERAL"
>WITH</TT
></H3
> PostgreSQL allows <TT
CLASS="COMMAND"
>INSERT</TT
>,
 <TT
CLASS="COMMAND"
>UPDATE</TT
>, and <TT
CLASS="COMMAND"
>DELETE</TT
> to be used as <TT
CLASS="LITERAL"
>WITH</TT
>
 queries. This is not found in the SQL standard.
 </DIV
><DIV
CLASS="REFSECT2"
><A
NAME="AEN78566"
></A
><H3
>Nonstandard Clauses</H3
> The clause <TT
CLASS="LITERAL"
>DISTINCT ON</TT
> is not defined in the
 SQL standard.
 </DIV
></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-security-label.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-selectinto.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SECURITY LABEL</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"
>SELECT INTO</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

${this.title}

Code Editor : sql-select.html