From e427e8e242a18e765647c1926bc76094ae14b08f Mon Sep 17 00:00:00 2001 From: Dave Page Date: Sat, 6 Jan 2007 21:07:12 +0000 Subject: [PATCH] Update docs for PostgreSQL 8.2.1 git-svn-id: svn://svn.pgadmin.org/branches/REL-1_6_0_PATCHES@5836 a7884b65-44f6-0310-8a51-81a127f17b15 --- docs/en_US/pg/admin.html | 42 +- docs/en_US/pg/app-clusterdb.html | 16 +- docs/en_US/pg/app-createdb.html | 14 +- docs/en_US/pg/app-createlang.html | 18 +- docs/en_US/pg/app-createuser.html | 16 +- docs/en_US/pg/app-dropdb.html | 16 +- docs/en_US/pg/app-droplang.html | 16 +- docs/en_US/pg/app-dropuser.html | 16 +- docs/en_US/pg/app-ecpg.html | 10 +- docs/en_US/pg/app-initdb.html | 10 +- docs/en_US/pg/app-ipcclean.html | 6 +- docs/en_US/pg/app-pg-ctl.html | 12 +- docs/en_US/pg/app-pg-dumpall.html | 12 +- docs/en_US/pg/app-pgconfig.html | 14 +- docs/en_US/pg/app-pgcontroldata.html | 6 +- docs/en_US/pg/app-pgdump.html | 10 +- docs/en_US/pg/app-pgresetxlog.html | 4 +- docs/en_US/pg/app-pgrestore.html | 10 +- docs/en_US/pg/app-postgres.html | 225 +- docs/en_US/pg/app-postmaster.html | 8 +- docs/en_US/pg/app-psql.html | 39 +- docs/en_US/pg/app-reindexdb.html | 18 +- docs/en_US/pg/app-vacuumdb.html | 18 +- docs/en_US/pg/appendixes.html | 591 +-- docs/en_US/pg/applevel-consistency.html | 2 +- docs/en_US/pg/arrays.html | 18 +- docs/en_US/pg/auth-methods.html | 20 +- docs/en_US/pg/backup-file.html | 2 +- docs/en_US/pg/backup.html | 4 +- docs/en_US/pg/biblio.html | 10 +- docs/en_US/pg/bki-commands.html | 2 +- docs/en_US/pg/bki-example.html | 2 +- docs/en_US/pg/bki-structure.html | 2 +- docs/en_US/pg/bki.html | 2 +- docs/en_US/pg/bug-reporting.html | 10 +- docs/en_US/pg/catalog-pg-aggregate.html | 6 +- docs/en_US/pg/catalog-pg-am.html | 6 +- docs/en_US/pg/catalog-pg-amop.html | 6 +- docs/en_US/pg/catalog-pg-amproc.html | 6 +- docs/en_US/pg/catalog-pg-attrdef.html | 6 +- docs/en_US/pg/catalog-pg-attribute.html | 6 +- docs/en_US/pg/catalog-pg-auth-members.html | 6 +- docs/en_US/pg/catalog-pg-authid.html | 6 +- docs/en_US/pg/catalog-pg-autovacuum.html | 6 +- docs/en_US/pg/catalog-pg-cast.html | 6 +- docs/en_US/pg/catalog-pg-class.html | 6 +- docs/en_US/pg/catalog-pg-constraint.html | 6 +- docs/en_US/pg/catalog-pg-conversion.html | 6 +- docs/en_US/pg/catalog-pg-database.html | 6 +- docs/en_US/pg/catalog-pg-depend.html | 6 +- docs/en_US/pg/catalog-pg-description.html | 6 +- docs/en_US/pg/catalog-pg-index.html | 6 +- docs/en_US/pg/catalog-pg-inherits.html | 6 +- docs/en_US/pg/catalog-pg-language.html | 6 +- docs/en_US/pg/catalog-pg-largeobject.html | 6 +- docs/en_US/pg/catalog-pg-listener.html | 6 +- docs/en_US/pg/catalog-pg-namespace.html | 6 +- docs/en_US/pg/catalog-pg-opclass.html | 6 +- docs/en_US/pg/catalog-pg-operator.html | 6 +- docs/en_US/pg/catalog-pg-pltemplate.html | 6 +- docs/en_US/pg/catalog-pg-proc.html | 6 +- docs/en_US/pg/catalog-pg-rewrite.html | 6 +- docs/en_US/pg/catalog-pg-shdepend.html | 6 +- docs/en_US/pg/catalog-pg-shdescription.html | 6 +- docs/en_US/pg/catalog-pg-statistic.html | 6 +- docs/en_US/pg/catalog-pg-tablespace.html | 6 +- docs/en_US/pg/catalog-pg-trigger.html | 6 +- docs/en_US/pg/catalog-pg-type.html | 6 +- docs/en_US/pg/catalogs.html | 2 +- docs/en_US/pg/charset.html | 32 +- .../pg/client-authentication-problems.html | 2 +- docs/en_US/pg/client-authentication.html | 8 +- docs/en_US/pg/client-interfaces.html | 68 +- docs/en_US/pg/connect-estab.html | 2 +- docs/en_US/pg/continuous-archiving.html | 6 +- docs/en_US/pg/creating-cluster.html | 12 +- docs/en_US/pg/cvs-tree.html | 2 +- docs/en_US/pg/cvs.html | 10 +- docs/en_US/pg/cvsup.html | 6 +- docs/en_US/pg/datatype-binary.html | 4 +- docs/en_US/pg/datatype-bit.html | 6 +- docs/en_US/pg/datatype-boolean.html | 4 +- docs/en_US/pg/datatype-character.html | 6 +- docs/en_US/pg/datatype-datetime.html | 28 +- docs/en_US/pg/datatype-geometric.html | 26 +- docs/en_US/pg/datatype-money.html | 2 +- docs/en_US/pg/datatype-net-types.html | 10 +- docs/en_US/pg/datatype-oid.html | 4 +- docs/en_US/pg/datatype-pseudo.html | 4 +- docs/en_US/pg/datatype-xml.html | 4 +- docs/en_US/pg/datatype.html | 48 +- docs/en_US/pg/datetime-appendix.html | 6 +- docs/en_US/pg/datetime-config-files.html | 4 +- docs/en_US/pg/datetime-keywords.html | 2 +- docs/en_US/pg/datetime-units-history.html | 2 +- docs/en_US/pg/ddl-alter.html | 36 +- docs/en_US/pg/ddl-constraints.html | 30 +- docs/en_US/pg/ddl-default.html | 6 +- docs/en_US/pg/ddl-depend.html | 4 +- docs/en_US/pg/ddl-inherit.html | 4 +- docs/en_US/pg/ddl-others.html | 2 +- docs/en_US/pg/ddl-partitioning.html | 6 +- docs/en_US/pg/ddl-priv.html | 4 +- docs/en_US/pg/ddl-schemas.html | 22 +- docs/en_US/pg/ddl-system-columns.html | 18 +- docs/en_US/pg/ddl.html | 32 +- docs/en_US/pg/disk-full.html | 2 +- docs/en_US/pg/diskusage.html | 4 +- docs/en_US/pg/dml-delete.html | 4 +- docs/en_US/pg/dml-update.html | 4 +- docs/en_US/pg/dml.html | 4 +- docs/en_US/pg/docguide-authoring.html | 6 +- docs/en_US/pg/docguide-build.html | 16 +- docs/en_US/pg/docguide-style.html | 4 +- docs/en_US/pg/docguide-toolsets.html | 18 +- docs/en_US/pg/docguide.html | 28 +- docs/en_US/pg/dynamic-trace.html | 37 +- docs/en_US/pg/ecpg-commands.html | 2 +- docs/en_US/pg/ecpg-connect.html | 2 +- docs/en_US/pg/ecpg-descriptors.html | 2 +- docs/en_US/pg/ecpg-develop.html | 2 +- docs/en_US/pg/ecpg-disconnect.html | 2 +- docs/en_US/pg/ecpg-dynamic.html | 2 +- docs/en_US/pg/ecpg-errors.html | 8 +- docs/en_US/pg/ecpg-informix-compat.html | 8 +- docs/en_US/pg/ecpg-library.html | 2 +- docs/en_US/pg/ecpg-pgtypes.html | 24 +- docs/en_US/pg/ecpg-preproc.html | 8 +- docs/en_US/pg/ecpg-process.html | 2 +- docs/en_US/pg/ecpg-set-connection.html | 2 +- docs/en_US/pg/ecpg-variables.html | 12 +- docs/en_US/pg/ecpg.html | 46 +- docs/en_US/pg/encryption-options.html | 4 +- docs/en_US/pg/errcodes-appendix.html | 6 +- docs/en_US/pg/error-message-reporting.html | 8 +- docs/en_US/pg/error-style-guide.html | 34 +- docs/en_US/pg/executor.html | 2 +- docs/en_US/pg/explicit-joins.html | 4 +- docs/en_US/pg/explicit-locking.html | 10 +- docs/en_US/pg/extend-type-system.html | 14 +- docs/en_US/pg/extend.html | 44 +- docs/en_US/pg/external-extensions.html | 4 +- docs/en_US/pg/external-pl.html | 4 +- docs/en_US/pg/external-projects.html | 4 +- docs/en_US/pg/features.html | 2 +- docs/en_US/pg/functions-admin.html | 30 +- docs/en_US/pg/functions-aggregate.html | 42 +- docs/en_US/pg/functions-array.html | 2 +- docs/en_US/pg/functions-binarystring.html | 20 +- docs/en_US/pg/functions-bitstring.html | 4 +- docs/en_US/pg/functions-comparison.html | 34 +- docs/en_US/pg/functions-comparisons.html | 12 +- docs/en_US/pg/functions-conditional.html | 18 +- docs/en_US/pg/functions-datetime.html | 18 +- docs/en_US/pg/functions-formatting.html | 4 +- docs/en_US/pg/functions-geometry.html | 4 +- docs/en_US/pg/functions-info.html | 22 +- docs/en_US/pg/functions-matching.html | 10 +- docs/en_US/pg/functions-math.html | 6 +- docs/en_US/pg/functions-net.html | 2 +- docs/en_US/pg/functions-sequence.html | 4 +- docs/en_US/pg/functions-srf.html | 4 +- docs/en_US/pg/functions-string.html | 16 +- docs/en_US/pg/functions-subquery.html | 18 +- docs/en_US/pg/functions.html | 46 +- docs/en_US/pg/geqo-biblio.html | 2 +- docs/en_US/pg/geqo-intro2.html | 2 +- docs/en_US/pg/geqo-pg-intro.html | 2 +- docs/en_US/pg/geqo.html | 2 +- docs/en_US/pg/gin-examples.html | 2 +- docs/en_US/pg/gin-extensibility.html | 2 +- docs/en_US/pg/gin-implementation.html | 2 +- docs/en_US/pg/gin-limit.html | 2 +- docs/en_US/pg/gin-tips.html | 2 +- docs/en_US/pg/gin.html | 4 +- docs/en_US/pg/gist-examples.html | 2 +- docs/en_US/pg/gist-extensibility.html | 2 +- docs/en_US/pg/gist-implementation.html | 2 +- docs/en_US/pg/gist-recovery.html | 2 +- docs/en_US/pg/gist.html | 4 +- docs/en_US/pg/high-availability.html | 4 +- docs/en_US/pg/history.html | 10 +- docs/en_US/pg/index-cost-estimation.html | 4 +- docs/en_US/pg/index-functions.html | 2 +- docs/en_US/pg/index-locking.html | 2 +- docs/en_US/pg/index-scanning.html | 2 +- docs/en_US/pg/index-unique-checks.html | 2 +- docs/en_US/pg/index.html | 1091 ++--- docs/en_US/pg/indexam.html | 2 +- docs/en_US/pg/indexes-bitmap-scans.html | 4 +- docs/en_US/pg/indexes-examine.html | 4 +- docs/en_US/pg/indexes-expressional.html | 4 +- docs/en_US/pg/indexes-multicolumn.html | 4 +- docs/en_US/pg/indexes-opclass.html | 4 +- docs/en_US/pg/indexes-partial.html | 4 +- docs/en_US/pg/indexes-types.html | 18 +- docs/en_US/pg/indexes-unique.html | 4 +- docs/en_US/pg/indexes.html | 4 +- docs/en_US/pg/information-schema.html | 4 +- ...ema-administrable-role-authorizations.html | 4 +- .../en_US/pg/infoschema-applicable-roles.html | 8 +- docs/en_US/pg/infoschema-attributes.html | 4 +- ...schema-check-constraint-routine-usage.html | 4 +- .../pg/infoschema-check-constraints.html | 4 +- .../pg/infoschema-column-domain-usage.html | 4 +- .../pg/infoschema-column-privileges.html | 4 +- .../en_US/pg/infoschema-column-udt-usage.html | 4 +- docs/en_US/pg/infoschema-columns.html | 4 +- .../infoschema-constraint-column-usage.html | 4 +- .../pg/infoschema-constraint-table-usage.html | 4 +- .../pg/infoschema-data-type-privileges.html | 4 +- docs/en_US/pg/infoschema-datatypes.html | 2 +- .../pg/infoschema-domain-constraints.html | 4 +- .../en_US/pg/infoschema-domain-udt-usage.html | 4 +- docs/en_US/pg/infoschema-domains.html | 4 +- docs/en_US/pg/infoschema-element-types.html | 4 +- docs/en_US/pg/infoschema-enabled-roles.html | 8 +- ...chema-information-schema-catalog-name.html | 4 +- .../en_US/pg/infoschema-key-column-usage.html | 4 +- docs/en_US/pg/infoschema-parameters.html | 4 +- .../infoschema-referential-constraints.html | 4 +- .../pg/infoschema-role-column-grants.html | 4 +- .../pg/infoschema-role-routine-grants.html | 4 +- .../pg/infoschema-role-table-grants.html | 4 +- .../pg/infoschema-role-usage-grants.html | 4 +- .../pg/infoschema-routine-privileges.html | 4 +- docs/en_US/pg/infoschema-routines.html | 4 +- docs/en_US/pg/infoschema-schemata.html | 4 +- docs/en_US/pg/infoschema-sequences.html | 4 +- docs/en_US/pg/infoschema-sql-features.html | 4 +- .../infoschema-sql-implementation-info.html | 4 +- docs/en_US/pg/infoschema-sql-languages.html | 4 +- docs/en_US/pg/infoschema-sql-packages.html | 4 +- docs/en_US/pg/infoschema-sql-parts.html | 4 +- .../pg/infoschema-sql-sizing-profiles.html | 4 +- docs/en_US/pg/infoschema-sql-sizing.html | 4 +- .../pg/infoschema-table-constraints.html | 4 +- .../en_US/pg/infoschema-table-privileges.html | 4 +- docs/en_US/pg/infoschema-tables.html | 4 +- docs/en_US/pg/infoschema-triggers.html | 4 +- .../en_US/pg/infoschema-usage-privileges.html | 4 +- .../pg/infoschema-view-column-usage.html | 4 +- .../pg/infoschema-view-routine-usage.html | 4 +- .../en_US/pg/infoschema-view-table-usage.html | 4 +- docs/en_US/pg/infoschema-views.html | 4 +- docs/en_US/pg/install-getsource.html | 12 +- docs/en_US/pg/install-post.html | 14 +- docs/en_US/pg/install-procedure.html | 26 +- docs/en_US/pg/install-requirements.html | 22 +- docs/en_US/pg/install-upgrading.html | 10 +- docs/en_US/pg/install-win32.html | 4 +- docs/en_US/pg/installation.html | 8 +- docs/en_US/pg/internals.html | 32 +- docs/en_US/pg/ix01.html | 186 +- docs/en_US/pg/kernel-resources.html | 10 +- docs/en_US/pg/largeobjects.html | 26 +- docs/en_US/pg/libpq-async.html | 28 +- docs/en_US/pg/libpq-build.html | 6 +- docs/en_US/pg/libpq-cancel.html | 14 +- docs/en_US/pg/libpq-control.html | 8 +- docs/en_US/pg/libpq-copy.html | 26 +- docs/en_US/pg/libpq-envars.html | 44 +- docs/en_US/pg/libpq-example.html | 2 +- docs/en_US/pg/libpq-exec.html | 84 +- docs/en_US/pg/libpq-fastpath.html | 6 +- docs/en_US/pg/libpq-ldap.html | 4 +- docs/en_US/pg/libpq-misc.html | 4 +- docs/en_US/pg/libpq-notice-processing.html | 8 +- docs/en_US/pg/libpq-notify.html | 6 +- docs/en_US/pg/libpq-pgpass.html | 4 +- docs/en_US/pg/libpq-pgservice.html | 4 +- docs/en_US/pg/libpq-ssl.html | 4 +- docs/en_US/pg/libpq-status.html | 44 +- docs/en_US/pg/libpq-threading.html | 6 +- docs/en_US/pg/libpq.html | 34 +- docs/en_US/pg/lo-examplesect.html | 2 +- docs/en_US/pg/lo-funcs.html | 12 +- docs/en_US/pg/lo-implementation.html | 2 +- docs/en_US/pg/lo-interfaces.html | 44 +- docs/en_US/pg/locking-indexes.html | 4 +- docs/en_US/pg/logfile-maintenance.html | 4 +- docs/en_US/pg/maintenance.html | 14 +- docs/en_US/pg/manage-ag-config.html | 2 +- docs/en_US/pg/manage-ag-createdb.html | 10 +- docs/en_US/pg/manage-ag-dropdb.html | 6 +- docs/en_US/pg/manage-ag-tablespaces.html | 6 +- docs/en_US/pg/manage-ag-templatedbs.html | 8 +- docs/en_US/pg/managing-databases.html | 6 +- docs/en_US/pg/migration.html | 6 +- docs/en_US/pg/monitoring-locks.html | 4 +- docs/en_US/pg/monitoring-stats.html | 4 +- docs/en_US/pg/monitoring.html | 8 +- docs/en_US/pg/multibyte.html | 10 +- docs/en_US/pg/mvcc.html | 6 +- docs/en_US/pg/nls-programmer.html | 4 +- docs/en_US/pg/nls.html | 18 +- docs/en_US/pg/notation.html | 2 +- docs/en_US/pg/overview.html | 8 +- docs/en_US/pg/parser-stage.html | 6 +- docs/en_US/pg/performance-tips.html | 10 +- docs/en_US/pg/perm-functions.html | 2 +- docs/en_US/pg/planner-optimizer.html | 4 +- docs/en_US/pg/planner-stats-details.html | 4 +- docs/en_US/pg/planner-stats.html | 8 +- docs/en_US/pg/plhandler.html | 4 +- docs/en_US/pg/plperl-data.html | 2 +- docs/en_US/pg/plperl-database.html | 4 +- docs/en_US/pg/plperl-global.html | 2 +- docs/en_US/pg/plperl-missing.html | 2 +- docs/en_US/pg/plperl-triggers.html | 2 +- docs/en_US/pg/plperl-trusted.html | 6 +- docs/en_US/pg/plperl.html | 6 +- docs/en_US/pg/plpgsql-control-structures.html | 36 +- docs/en_US/pg/plpgsql-cursors.html | 16 +- docs/en_US/pg/plpgsql-declarations.html | 2 +- docs/en_US/pg/plpgsql-development-tips.html | 2 +- .../en_US/pg/plpgsql-errors-and-messages.html | 4 +- docs/en_US/pg/plpgsql-expressions.html | 2 +- docs/en_US/pg/plpgsql-porting.html | 10 +- docs/en_US/pg/plpgsql-statements.html | 6 +- docs/en_US/pg/plpgsql-structure.html | 2 +- docs/en_US/pg/plpgsql-trigger.html | 4 +- docs/en_US/pg/plpgsql.html | 8 +- docs/en_US/pg/plpython-database.html | 6 +- docs/en_US/pg/plpython-trigger.html | 4 +- docs/en_US/pg/plpython.html | 8 +- docs/en_US/pg/pltcl-data.html | 2 +- docs/en_US/pg/pltcl-dbaccess.html | 4 +- docs/en_US/pg/pltcl-functions.html | 2 +- docs/en_US/pg/pltcl-global.html | 4 +- docs/en_US/pg/pltcl-procnames.html | 2 +- docs/en_US/pg/pltcl-trigger.html | 4 +- docs/en_US/pg/pltcl-unknown.html | 2 +- docs/en_US/pg/pltcl.html | 4 +- docs/en_US/pg/populate.html | 8 +- docs/en_US/pg/preface.html | 14 +- docs/en_US/pg/privileges.html | 4 +- docs/en_US/pg/protocol-changes.html | 2 +- docs/en_US/pg/protocol-error-fields.html | 2 +- docs/en_US/pg/protocol-flow.html | 14 +- docs/en_US/pg/protocol-message-formats.html | 2 +- docs/en_US/pg/protocol-message-types.html | 2 +- docs/en_US/pg/protocol.html | 14 +- docs/en_US/pg/queries-limit.html | 4 +- docs/en_US/pg/queries-order.html | 8 +- docs/en_US/pg/queries-select-lists.html | 12 +- docs/en_US/pg/queries-table-expressions.html | 24 +- docs/en_US/pg/queries-union.html | 4 +- docs/en_US/pg/queries-values.html | 4 +- docs/en_US/pg/queries.html | 4 +- docs/en_US/pg/reference-client.html | 4 +- docs/en_US/pg/reference-server.html | 4 +- docs/en_US/pg/reference.html | 6 +- docs/en_US/pg/regress-evaluation.html | 16 +- docs/en_US/pg/regress-variant.html | 2 +- docs/en_US/pg/regress.html | 18 +- docs/en_US/pg/release-0-01.html | 8 +- docs/en_US/pg/release-0-02.html | 12 +- docs/en_US/pg/release-0-03.html | 12 +- docs/en_US/pg/release-1-0.html | 12 +- docs/en_US/pg/release-1-01.html | 14 +- docs/en_US/pg/release-1-02.html | 16 +- docs/en_US/pg/release-1-09.html | 10 +- docs/en_US/pg/release-6-0.html | 16 +- docs/en_US/pg/release-6-1-1.html | 14 +- docs/en_US/pg/release-6-1.html | 14 +- docs/en_US/pg/release-6-2-1.html | 14 +- docs/en_US/pg/release-6-2.html | 16 +- docs/en_US/pg/release-6-3-1.html | 12 +- docs/en_US/pg/release-6-3-2.html | 12 +- docs/en_US/pg/release-6-3.html | 14 +- docs/en_US/pg/release-6-4-1.html | 14 +- docs/en_US/pg/release-6-4-2.html | 14 +- docs/en_US/pg/release-6-4.html | 14 +- docs/en_US/pg/release-6-5-1.html | 14 +- docs/en_US/pg/release-6-5-2.html | 14 +- docs/en_US/pg/release-6-5-3.html | 14 +- docs/en_US/pg/release-6-5.html | 16 +- docs/en_US/pg/release-7-0-1.html | 14 +- docs/en_US/pg/release-7-0-2.html | 14 +- docs/en_US/pg/release-7-0-3.html | 14 +- docs/en_US/pg/release-7-0.html | 14 +- docs/en_US/pg/release-7-1-1.html | 14 +- docs/en_US/pg/release-7-1-2.html | 14 +- docs/en_US/pg/release-7-1-3.html | 14 +- docs/en_US/pg/release-7-1.html | 14 +- docs/en_US/pg/release-7-2-1.html | 14 +- docs/en_US/pg/release-7-2-2.html | 14 +- docs/en_US/pg/release-7-2-3.html | 14 +- docs/en_US/pg/release-7-2-4.html | 14 +- docs/en_US/pg/release-7-2-5.html | 14 +- docs/en_US/pg/release-7-2-6.html | 14 +- docs/en_US/pg/release-7-2-7.html | 14 +- docs/en_US/pg/release-7-2-8.html | 14 +- docs/en_US/pg/release-7-2.html | 62 +- docs/en_US/pg/release-7-3-1.html | 14 +- docs/en_US/pg/release-7-3-10.html | 14 +- docs/en_US/pg/release-7-3-11.html | 14 +- docs/en_US/pg/release-7-3-12.html | 14 +- docs/en_US/pg/release-7-3-13.html | 14 +- docs/en_US/pg/release-7-3-14.html | 14 +- docs/en_US/pg/release-7-3-15.html | 14 +- docs/en_US/pg/release-7-3-16.html | 14 +- docs/en_US/pg/release-7-3-17.html | 54 + docs/en_US/pg/release-7-3-2.html | 14 +- docs/en_US/pg/release-7-3-3.html | 14 +- docs/en_US/pg/release-7-3-4.html | 14 +- docs/en_US/pg/release-7-3-5.html | 14 +- docs/en_US/pg/release-7-3-6.html | 14 +- docs/en_US/pg/release-7-3-7.html | 14 +- docs/en_US/pg/release-7-3-8.html | 14 +- docs/en_US/pg/release-7-3-9.html | 14 +- docs/en_US/pg/release-7-3.html | 48 +- docs/en_US/pg/release-7-4-1.html | 14 +- docs/en_US/pg/release-7-4-10.html | 14 +- docs/en_US/pg/release-7-4-11.html | 14 +- docs/en_US/pg/release-7-4-12.html | 14 +- docs/en_US/pg/release-7-4-13.html | 14 +- docs/en_US/pg/release-7-4-14.html | 14 +- docs/en_US/pg/release-7-4-15.html | 69 + docs/en_US/pg/release-7-4-2.html | 14 +- docs/en_US/pg/release-7-4-3.html | 14 +- docs/en_US/pg/release-7-4-4.html | 14 +- docs/en_US/pg/release-7-4-5.html | 14 +- docs/en_US/pg/release-7-4-6.html | 14 +- docs/en_US/pg/release-7-4-7.html | 14 +- docs/en_US/pg/release-7-4-8.html | 14 +- docs/en_US/pg/release-7-4-9.html | 14 +- docs/en_US/pg/release-7-4.html | 46 +- docs/en_US/pg/release-8-0-1.html | 14 +- docs/en_US/pg/release-8-0-10.html | 83 + docs/en_US/pg/release-8-0-2.html | 14 +- docs/en_US/pg/release-8-0-3.html | 16 +- docs/en_US/pg/release-8-0-4.html | 14 +- docs/en_US/pg/release-8-0-5.html | 14 +- docs/en_US/pg/release-8-0-6.html | 14 +- docs/en_US/pg/release-8-0-7.html | 14 +- docs/en_US/pg/release-8-0-8.html | 14 +- docs/en_US/pg/release-8-0-9.html | 14 +- docs/en_US/pg/release-8-0.html | 42 +- docs/en_US/pg/release-8-1-1.html | 14 +- docs/en_US/pg/release-8-1-2.html | 14 +- docs/en_US/pg/release-8-1-3.html | 14 +- docs/en_US/pg/release-8-1-4.html | 14 +- docs/en_US/pg/release-8-1-5.html | 14 +- docs/en_US/pg/release-8-1-6.html | 98 + docs/en_US/pg/release-8-1.html | 46 +- docs/en_US/pg/release-8-2.html | 1536 +++++++ docs/en_US/pg/release.html | 2119 ++------- docs/en_US/pg/resources.html | 4 +- docs/en_US/pg/role-attributes.html | 14 +- docs/en_US/pg/role-membership.html | 4 +- docs/en_US/pg/routine-reindex.html | 4 +- docs/en_US/pg/rowtypes.html | 16 +- docs/en_US/pg/rule-system.html | 2 +- docs/en_US/pg/rules-privileges.html | 4 +- docs/en_US/pg/rules-status.html | 2 +- docs/en_US/pg/rules-triggers.html | 4 +- docs/en_US/pg/rules-update.html | 10 +- docs/en_US/pg/rules-views.html | 38 +- docs/en_US/pg/rules.html | 12 +- docs/en_US/pg/runtime-config-autovacuum.html | 4 +- docs/en_US/pg/runtime-config-client.html | 2 +- docs/en_US/pg/runtime-config-compatible.html | 2 +- docs/en_US/pg/runtime-config-connection.html | 2 +- docs/en_US/pg/runtime-config-custom.html | 2 +- docs/en_US/pg/runtime-config-developer.html | 2 +- .../pg/runtime-config-file-locations.html | 2 +- docs/en_US/pg/runtime-config-locks.html | 2 +- docs/en_US/pg/runtime-config-logging.html | 8 +- docs/en_US/pg/runtime-config-preset.html | 2 +- docs/en_US/pg/runtime-config-query.html | 2 +- docs/en_US/pg/runtime-config-resource.html | 4 +- docs/en_US/pg/runtime-config-short.html | 2 +- docs/en_US/pg/runtime-config-statistics.html | 2 +- docs/en_US/pg/runtime-config-wal.html | 2 +- docs/en_US/pg/runtime-config.html | 10 +- docs/en_US/pg/runtime.html | 8 +- docs/en_US/pg/server-programming.html | 54 +- docs/en_US/pg/server-shutdown.html | 10 +- docs/en_US/pg/server-start.html | 18 +- docs/en_US/pg/source.html | 2 +- docs/en_US/pg/spi-examples.html | 2 +- docs/en_US/pg/spi-interface-support.html | 2 +- docs/en_US/pg/spi-memory.html | 4 +- docs/en_US/pg/spi-realloc.html | 10 +- docs/en_US/pg/spi-spi-connect.html | 8 +- docs/en_US/pg/spi-spi-copytuple.html | 10 +- docs/en_US/pg/spi-spi-cursor-close.html | 8 +- docs/en_US/pg/spi-spi-cursor-fetch.html | 10 +- docs/en_US/pg/spi-spi-cursor-find.html | 10 +- docs/en_US/pg/spi-spi-cursor-move.html | 8 +- docs/en_US/pg/spi-spi-cursor-open.html | 10 +- docs/en_US/pg/spi-spi-exec.html | 10 +- docs/en_US/pg/spi-spi-execp.html | 10 +- docs/en_US/pg/spi-spi-execute-plan.html | 12 +- docs/en_US/pg/spi-spi-execute.html | 12 +- docs/en_US/pg/spi-spi-finish.html | 8 +- docs/en_US/pg/spi-spi-fname.html | 10 +- docs/en_US/pg/spi-spi-fnumber.html | 10 +- docs/en_US/pg/spi-spi-freeplan.html | 10 +- docs/en_US/pg/spi-spi-freetuple.html | 8 +- docs/en_US/pg/spi-spi-freetupletable.html | 8 +- docs/en_US/pg/spi-spi-getargcount.html | 10 +- docs/en_US/pg/spi-spi-getargtypeid.html | 10 +- docs/en_US/pg/spi-spi-getbinval.html | 10 +- docs/en_US/pg/spi-spi-getnspname.html | 10 +- docs/en_US/pg/spi-spi-getrelname.html | 10 +- docs/en_US/pg/spi-spi-gettype.html | 10 +- docs/en_US/pg/spi-spi-gettypeid.html | 10 +- docs/en_US/pg/spi-spi-getvalue.html | 10 +- docs/en_US/pg/spi-spi-is-cursor-plan.html | 10 +- docs/en_US/pg/spi-spi-modifytuple.html | 10 +- docs/en_US/pg/spi-spi-palloc.html | 10 +- docs/en_US/pg/spi-spi-pfree.html | 8 +- docs/en_US/pg/spi-spi-pop.html | 6 +- docs/en_US/pg/spi-spi-prepare.html | 12 +- docs/en_US/pg/spi-spi-push.html | 6 +- docs/en_US/pg/spi-spi-returntuple.html | 10 +- docs/en_US/pg/spi-spi-saveplan.html | 12 +- docs/en_US/pg/spi-visibility.html | 2 +- docs/en_US/pg/spi.html | 4 +- docs/en_US/pg/sql-abort.html | 16 +- docs/en_US/pg/sql-alteraggregate.html | 14 +- docs/en_US/pg/sql-alterconversion.html | 14 +- docs/en_US/pg/sql-alterdatabase.html | 16 +- docs/en_US/pg/sql-alterdomain.html | 10 +- docs/en_US/pg/sql-alterfunction.html | 14 +- docs/en_US/pg/sql-altergroup.html | 14 +- docs/en_US/pg/sql-alterindex.html | 16 +- docs/en_US/pg/sql-alterlanguage.html | 12 +- docs/en_US/pg/sql-alteropclass.html | 12 +- docs/en_US/pg/sql-alteroperator.html | 14 +- docs/en_US/pg/sql-alterrole.html | 16 +- docs/en_US/pg/sql-alterschema.html | 12 +- docs/en_US/pg/sql-altersequence.html | 16 +- docs/en_US/pg/sql-altertable.html | 14 +- docs/en_US/pg/sql-altertablespace.html | 14 +- docs/en_US/pg/sql-altertrigger.html | 16 +- docs/en_US/pg/sql-altertype.html | 12 +- docs/en_US/pg/sql-alteruser.html | 10 +- docs/en_US/pg/sql-analyze.html | 14 +- docs/en_US/pg/sql-begin.html | 16 +- docs/en_US/pg/sql-checkpoint.html | 8 +- docs/en_US/pg/sql-close.html | 16 +- docs/en_US/pg/sql-cluster.html | 16 +- docs/en_US/pg/sql-commands.html | 4 +- docs/en_US/pg/sql-comment.html | 14 +- docs/en_US/pg/sql-commit-prepared.html | 12 +- docs/en_US/pg/sql-commit.html | 16 +- docs/en_US/pg/sql-copy.html | 30 +- docs/en_US/pg/sql-createaggregate.html | 14 +- docs/en_US/pg/sql-createcast.html | 6 +- docs/en_US/pg/sql-createconstraint.html | 10 +- docs/en_US/pg/sql-createconversion.html | 6 +- docs/en_US/pg/sql-createdatabase.html | 16 +- docs/en_US/pg/sql-createdomain.html | 10 +- docs/en_US/pg/sql-createfunction.html | 8 +- docs/en_US/pg/sql-creategroup.html | 10 +- docs/en_US/pg/sql-createindex.html | 18 +- docs/en_US/pg/sql-createlanguage.html | 6 +- docs/en_US/pg/sql-createopclass.html | 16 +- docs/en_US/pg/sql-createoperator.html | 16 +- docs/en_US/pg/sql-createrole.html | 16 +- docs/en_US/pg/sql-createrule.html | 12 +- docs/en_US/pg/sql-createschema.html | 16 +- docs/en_US/pg/sql-createsequence.html | 16 +- docs/en_US/pg/sql-createtable.html | 22 +- docs/en_US/pg/sql-createtableas.html | 16 +- docs/en_US/pg/sql-createtablespace.html | 16 +- docs/en_US/pg/sql-createtrigger.html | 10 +- docs/en_US/pg/sql-createtype.html | 16 +- docs/en_US/pg/sql-createuser.html | 10 +- docs/en_US/pg/sql-createview.html | 16 +- docs/en_US/pg/sql-deallocate.html | 12 +- docs/en_US/pg/sql-declare.html | 14 +- docs/en_US/pg/sql-delete.html | 16 +- docs/en_US/pg/sql-drop-owned.html | 14 +- docs/en_US/pg/sql-dropaggregate.html | 14 +- docs/en_US/pg/sql-dropcast.html | 8 +- docs/en_US/pg/sql-dropconversion.html | 8 +- docs/en_US/pg/sql-dropdatabase.html | 14 +- docs/en_US/pg/sql-dropdomain.html | 8 +- docs/en_US/pg/sql-dropfunction.html | 10 +- docs/en_US/pg/sql-dropgroup.html | 10 +- docs/en_US/pg/sql-dropindex.html | 14 +- docs/en_US/pg/sql-droplanguage.html | 14 +- docs/en_US/pg/sql-dropopclass.html | 14 +- docs/en_US/pg/sql-dropoperator.html | 14 +- docs/en_US/pg/sql-droprole.html | 16 +- docs/en_US/pg/sql-droprule.html | 14 +- docs/en_US/pg/sql-dropschema.html | 14 +- docs/en_US/pg/sql-dropsequence.html | 14 +- docs/en_US/pg/sql-droptable.html | 14 +- docs/en_US/pg/sql-droptablespace.html | 16 +- docs/en_US/pg/sql-droptrigger.html | 10 +- docs/en_US/pg/sql-droptype.html | 8 +- docs/en_US/pg/sql-dropuser.html | 10 +- docs/en_US/pg/sql-dropview.html | 14 +- docs/en_US/pg/sql-end.html | 16 +- docs/en_US/pg/sql-execute.html | 16 +- docs/en_US/pg/sql-explain.html | 16 +- docs/en_US/pg/sql-expressions.html | 42 +- docs/en_US/pg/sql-fetch.html | 18 +- docs/en_US/pg/sql-grant.html | 6 +- docs/en_US/pg/sql-insert.html | 14 +- docs/en_US/pg/sql-keywords-appendix.html | 6 +- docs/en_US/pg/sql-listen.html | 14 +- docs/en_US/pg/sql-load.html | 8 +- docs/en_US/pg/sql-lock.html | 14 +- docs/en_US/pg/sql-move.html | 14 +- docs/en_US/pg/sql-notify.html | 14 +- docs/en_US/pg/sql-prepare-transaction.html | 12 +- docs/en_US/pg/sql-prepare.html | 14 +- docs/en_US/pg/sql-reassign-owned.html | 14 +- docs/en_US/pg/sql-reindex.html | 17 +- docs/en_US/pg/sql-release-savepoint.html | 16 +- docs/en_US/pg/sql-reset.html | 12 +- docs/en_US/pg/sql-revoke.html | 6 +- docs/en_US/pg/sql-rollback-prepared.html | 12 +- docs/en_US/pg/sql-rollback-to.html | 16 +- docs/en_US/pg/sql-rollback.html | 16 +- docs/en_US/pg/sql-savepoint.html | 16 +- docs/en_US/pg/sql-select.html | 20 +- docs/en_US/pg/sql-selectinto.html | 16 +- docs/en_US/pg/sql-set-constraints.html | 10 +- docs/en_US/pg/sql-set-role.html | 14 +- .../pg/sql-set-session-authorization.html | 12 +- docs/en_US/pg/sql-set-transaction.html | 8 +- docs/en_US/pg/sql-set.html | 16 +- docs/en_US/pg/sql-show.html | 16 +- docs/en_US/pg/sql-start-transaction.html | 12 +- docs/en_US/pg/sql-syntax.html | 62 +- docs/en_US/pg/sql-truncate.html | 14 +- docs/en_US/pg/sql-unlisten.html | 16 +- docs/en_US/pg/sql-update.html | 16 +- docs/en_US/pg/sql-vacuum.html | 18 +- docs/en_US/pg/sql-values.html | 16 +- docs/en_US/pg/sql.html | 106 +- docs/en_US/pg/ssh-tunnels.html | 4 +- docs/en_US/pg/ssl-tcp.html | 4 +- docs/en_US/pg/storage-page-layout.html | 6 +- docs/en_US/pg/storage-toast.html | 4 +- docs/en_US/pg/storage.html | 2 +- docs/en_US/pg/supported-platforms.html | 2 +- docs/en_US/pg/transaction-iso.html | 22 +- docs/en_US/pg/trigger-datachanges.html | 2 +- docs/en_US/pg/trigger-example.html | 2 +- docs/en_US/pg/trigger-interface.html | 4 +- docs/en_US/pg/triggers.html | 6 +- docs/en_US/pg/tutorial-accessdb.html | 12 +- docs/en_US/pg/tutorial-advanced.html | 2 +- docs/en_US/pg/tutorial-agg.html | 18 +- docs/en_US/pg/tutorial-arch.html | 4 +- docs/en_US/pg/tutorial-concepts.html | 20 +- docs/en_US/pg/tutorial-conclusion.html | 2 +- docs/en_US/pg/tutorial-createdb.html | 8 +- docs/en_US/pg/tutorial-delete.html | 4 +- docs/en_US/pg/tutorial-fk.html | 4 +- docs/en_US/pg/tutorial-inheritance.html | 4 +- docs/en_US/pg/tutorial-join.html | 10 +- docs/en_US/pg/tutorial-populate.html | 6 +- docs/en_US/pg/tutorial-select.html | 20 +- docs/en_US/pg/tutorial-sql.html | 2 +- docs/en_US/pg/tutorial-start.html | 2 +- docs/en_US/pg/tutorial-table.html | 6 +- docs/en_US/pg/tutorial-transactions.html | 4 +- docs/en_US/pg/tutorial-update.html | 4 +- docs/en_US/pg/tutorial-views.html | 4 +- docs/en_US/pg/tutorial.html | 6 +- docs/en_US/pg/typeconv-func.html | 10 +- docs/en_US/pg/typeconv-oper.html | 12 +- docs/en_US/pg/typeconv-query.html | 6 +- docs/en_US/pg/typeconv-union-case.html | 12 +- docs/en_US/pg/typeconv.html | 6 +- .../pg/unsupported-features-sql-standard.html | 2 +- docs/en_US/pg/user-manag.html | 6 +- docs/en_US/pg/view-pg-cursors.html | 6 +- docs/en_US/pg/view-pg-group.html | 6 +- docs/en_US/pg/view-pg-indexes.html | 6 +- docs/en_US/pg/view-pg-locks.html | 6 +- .../en_US/pg/view-pg-prepared-statements.html | 6 +- docs/en_US/pg/view-pg-prepared-xacts.html | 6 +- docs/en_US/pg/view-pg-roles.html | 6 +- docs/en_US/pg/view-pg-rules.html | 6 +- docs/en_US/pg/view-pg-settings.html | 6 +- docs/en_US/pg/view-pg-shadow.html | 6 +- docs/en_US/pg/view-pg-stats.html | 6 +- docs/en_US/pg/view-pg-tables.html | 6 +- docs/en_US/pg/view-pg-timezone-abbrevs.html | 6 +- docs/en_US/pg/view-pg-timezone-names.html | 6 +- docs/en_US/pg/view-pg-user.html | 6 +- docs/en_US/pg/view-pg-views.html | 6 +- docs/en_US/pg/views-overview.html | 2 +- docs/en_US/pg/wal-configuration.html | 4 +- docs/en_US/pg/wal-internals.html | 4 +- docs/en_US/pg/wal-intro.html | 4 +- docs/en_US/pg/wal.html | 2 +- docs/en_US/pg/warm-standby.html | 6 +- docs/en_US/pg/xaggr.html | 4 +- docs/en_US/pg/xfunc-c.html | 42 +- docs/en_US/pg/xfunc-internal.html | 4 +- docs/en_US/pg/xfunc-overload.html | 4 +- docs/en_US/pg/xfunc-pl.html | 2 +- docs/en_US/pg/xfunc-sql.html | 18 +- docs/en_US/pg/xfunc-volatility.html | 4 +- docs/en_US/pg/xfunc.html | 4 +- docs/en_US/pg/xindex.html | 8 +- docs/en_US/pg/xoper-optimization.html | 16 +- docs/en_US/pg/xoper.html | 6 +- docs/en_US/pg/xplang.html | 6 +- docs/en_US/pg/xtypes.html | 14 +- docs/en_US/pgadmin3.hhc | 1008 ++-- docs/en_US/pgadmin3.hhk | 4064 ++++++++--------- docs/en_US/pgadmin3.hhp | 5 + 715 files changed, 9510 insertions(+), 9004 deletions(-) create mode 100644 docs/en_US/pg/release-7-3-17.html create mode 100644 docs/en_US/pg/release-7-4-15.html create mode 100644 docs/en_US/pg/release-8-0-10.html create mode 100644 docs/en_US/pg/release-8-1-6.html create mode 100644 docs/en_US/pg/release-8-2.html diff --git a/docs/en_US/pg/admin.html b/docs/en_US/pg/admin.html index 4b22799a5b..21411a678b 100644 --- a/docs/en_US/pg/admin.html +++ b/docs/en_US/pg/admin.html @@ -5,8 +5,8 @@ - - + + @@ -14,7 +14,7 @@

Part III. Server Administration

-
+

This part covers topics that are of interest to a PostgreSQL database administrator. This includes @@ -51,8 +51,8 @@

14.5. Installation Procedure
14.6. Post-Installation Setup
-
14.6.1. Shared Libraries
-
14.6.2. Environment Variables
+
14.6.1. Shared Libraries
+
14.6.2. Environment Variables
14.7. Supported Platforms
@@ -69,8 +69,8 @@
16.4. Managing Kernel Resources
16.4.1. Shared Memory and Semaphores
-
16.4.2. Resource Limits
-
16.4.3. Linux Memory Overcommit
+
16.4.2. Resource Limits
+
16.4.3. Linux Memory Overcommit
16.5. Shutting Down the Server
16.6. Encryption Options
@@ -173,16 +173,16 @@
21.1. Locale Support
-
21.1.1. Overview
-
21.1.2. Behavior
-
21.1.3. Problems
+
21.1.1. Overview
+
21.1.2. Behavior
+
21.1.3. Problems
21.2. Character Set Support
21.2.1. Supported Character Sets
-
21.2.2. Setting the Character Set
-
21.2.3. Automatic Character Set Conversion Between Server and Client
-
21.2.4. Further Reading
+
21.2.2. Setting the Character Set
+
21.2.3. Automatic Character Set Conversion Between Server and Client
+
21.2.4. Further Reading
22. Routine Database Maintenance Tasks
@@ -236,7 +236,7 @@
25.3. Viewing Locks
25.4. Dynamic Tracing
-
25.4.1. Compiling for Dynamic Trace
+
25.4.1. Compiling for Dynamic Tracing
25.4.2. Built-in Trace Points
25.4.3. Using Trace Points
25.4.4. Defining Trace Points
@@ -259,13 +259,13 @@
28.1. Running the Tests
28.2. Test Evaluation
-
28.2.1. Error message differences
-
28.2.2. Locale differences
-
28.2.3. Date and time differences
-
28.2.4. Floating-point differences
-
28.2.5. Row ordering differences
-
28.2.6. Insufficient stack depth
-
28.2.7. The “random” test
+
28.2.1. Error message differences
+
28.2.2. Locale differences
+
28.2.3. Date and time differences
+
28.2.4. Floating-point differences
+
28.2.5. Row ordering differences
+
28.2.6. Insufficient stack depth
+
28.2.7. The “random” test
28.3. Variant Comparison Files
diff --git a/docs/en_US/pg/app-clusterdb.html b/docs/en_US/pg/app-clusterdb.html index 6a7ac5d627..cc881561ca 100644 --- a/docs/en_US/pg/app-clusterdb.html +++ b/docs/en_US/pg/app-clusterdb.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

clusterdb — cluster a PostgreSQL database

-
+

Synopsis

clusterdb [connection-option...] [--table | -t table ] [dbname]
clusterdb [connection-option...] [[--all] | [-a]]

-

Description

+

Description

clusterdb is a utility for reclustering tables in a PostgreSQL database. It finds tables that have previously been clustered, and clusters them again on the same @@ -36,7 +36,7 @@

Synopsis

-

Options

+

Options

clusterdb accepts the following command-line arguments:

@@ -109,7 +109,7 @@

Synopsis

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -119,7 +119,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see CLUSTER and psql for discussions of potential problems and error messages. The database server must be running at the @@ -129,7 +129,7 @@

Synopsis

-

Examples

+

Examples

To cluster the database test: 

$ clusterdb test
@@ -144,7 +144,7 @@

Synopsis

-

See Also

+

See Also

CLUSTER, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-createdb.html b/docs/en_US/pg/app-createdb.html index 4128a7025c..c46ad117ea 100644 --- a/docs/en_US/pg/app-createdb.html +++ b/docs/en_US/pg/app-createdb.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

createdb — create a new PostgreSQL database

-
+

Synopsis

createdb [option...] [dbname] [description]

@@ -39,7 +39,7 @@

Synopsis

-

Options

+

Options

createdb accepts the following command-line arguments:

@@ -130,7 +130,7 @@

Synopsis

-

Environment

+

Environment

PGDATABASE

If set, the name of the database to create, unless overridden on @@ -146,7 +146,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see CREATE DATABASE and psql for discussions of potential problems and error messages. The database server must be running at the @@ -156,7 +156,7 @@

Synopsis

-

Examples

+

Examples

To create the database demo using the default database server:

@@ -178,7 +178,7 @@

Synopsis

-

See Also

+

See Also

dropdb, CREATE DATABASE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-createlang.html b/docs/en_US/pg/app-createlang.html index c5d1c5f382..7deaf29d30 100644 --- a/docs/en_US/pg/app-createlang.html +++ b/docs/en_US/pg/app-createlang.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

createlang — define a new PostgreSQL procedural language

-
+

Synopsis

createlang [connection-option...] langname [dbname]
createlang [connection-option...] [--list] | [-l] dbname

-

Description

+

Description

createlang is a utility for adding a new programming language to a PostgreSQL database. createlang is just a wrapper around the @@ -31,7 +31,7 @@

Synopsis

-

Options

+

Options

createlang accepts the following command-line arguments:

@@ -95,7 +95,7 @@

Synopsis

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -105,7 +105,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

Most error messages are self-explanatory. If not, run createlang with the --echo option and see under the respective SQL command @@ -113,12 +113,12 @@

Synopsis

-

Notes

+

Notes

Use droplang to remove a language.

-

Examples

+

Examples

To install the language pltcl into the database template1:

@@ -130,7 +130,7 @@

Synopsis

-

See Also

+

See Also

droplang, CREATE LANGUAGE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-createuser.html b/docs/en_US/pg/app-createuser.html index 642b2966a8..fb0ab8c179 100644 --- a/docs/en_US/pg/app-createuser.html +++ b/docs/en_US/pg/app-createuser.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

createuser — define a new PostgreSQL user account

-
+

Synopsis

createuser [option...] [username]

-

Description

+

Description

createuser creates a new PostgreSQL user (or more precisely, a role). Only superusers and users with CREATEROLE privilege can create @@ -42,7 +42,7 @@

Synopsis

-

Options

+

Options

createuser accepts the following command-line arguments:

@@ -192,7 +192,7 @@

Synopsis

-

Environment

+

Environment

PGHOST

PGPORT

PGUSER @@ -202,7 +202,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see CREATE ROLE and psql for discussions of potential problems and error messages. The database server must be running at the @@ -212,7 +212,7 @@

Synopsis

-

Examples

+

Examples

To create a user joe on the default database server:

@@ -249,7 +249,7 @@

Synopsis

-

See Also

+

See Also

dropuser, CREATE ROLE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-dropdb.html b/docs/en_US/pg/app-dropdb.html index fd72548d72..0f254b0759 100644 --- a/docs/en_US/pg/app-dropdb.html +++ b/docs/en_US/pg/app-dropdb.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

dropdb — remove a PostgreSQL database

-
+

Synopsis

dropdb [option...] dbname

-

Description

+

Description

dropdb destroys an existing PostgreSQL database. The user who executes this command must be a database @@ -35,7 +35,7 @@

Synopsis

-

Options

+

Options

dropdb accepts the following command-line arguments:

@@ -97,7 +97,7 @@

Synopsis

-

Environment

+

Environment

PGHOST

PGPORT

PGUSER @@ -107,7 +107,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see DROP DATABASE and psql for discussions of potential problems and error messages. The database server must be running at the @@ -117,7 +117,7 @@

Synopsis

-

Examples

+

Examples

To destroy the database demo on the default database server:

@@ -138,7 +138,7 @@

Synopsis

-

See Also

+

See Also

createdb, DROP DATABASE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-droplang.html b/docs/en_US/pg/app-droplang.html index 813c3ccfa9..7ebb9afb18 100644 --- a/docs/en_US/pg/app-droplang.html +++ b/docs/en_US/pg/app-droplang.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

droplang — remove a PostgreSQL procedural language

-
+

Synopsis

droplang [connection-option...] langname [dbname]
droplang [connection-option...] [--list] | [-l] dbname

@@ -39,7 +39,7 @@

Synopsis

-

Options

+

Options

droplang accepts the following command line arguments:

@@ -102,7 +102,7 @@

Synopsis

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -112,7 +112,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

Most error messages are self-explanatory. If not, run droplang with the --echo option and see under the respective SQL command @@ -120,12 +120,12 @@

Synopsis

-

Notes

+

Notes

Use createlang to add a language.

-

Examples

+

Examples

To remove the language pltcl: 

$ droplang pltcl dbname
@@ -133,7 +133,7 @@

Synopsis

-

See Also

+

See Also

createlang, DROP LANGUAGE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-dropuser.html b/docs/en_US/pg/app-dropuser.html index 84dd0719a4..a95bfa28ad 100644 --- a/docs/en_US/pg/app-dropuser.html +++ b/docs/en_US/pg/app-dropuser.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

dropuser — remove a PostgreSQL user account

-
+

Synopsis

dropuser [option...] [username]

-

Description

+

Description

dropuser removes an existing PostgreSQL user. Only superusers and users with the CREATEROLE privilege can @@ -36,7 +36,7 @@

Synopsis

-

Options

+

Options

dropuser accepts the following command-line arguments:

@@ -100,7 +100,7 @@

Synopsis

-

Environment

+

Environment

PGHOST

PGPORT

PGUSER @@ -110,7 +110,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see DROP ROLE and psql for discussions of potential problems and error messages. The database server must be running at the @@ -120,7 +120,7 @@

Synopsis

-

Examples

+

Examples

To remove user joe from the default database server:

@@ -141,7 +141,7 @@

Synopsis

-

See Also

+

See Also

createuser, DROP ROLE, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-ecpg.html b/docs/en_US/pg/app-ecpg.html index 238746f6d1..613b358a18 100644 --- a/docs/en_US/pg/app-ecpg.html +++ b/docs/en_US/pg/app-ecpg.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

ecpg — embedded SQL C preprocessor

-
+

Synopsis

ecpg [option...] file...

@@ -44,7 +44,7 @@

Synopsis

-

Options

+

Options

ecpg accepts the following command-line arguments: @@ -105,7 +105,7 @@

Synopsis

-

Notes

+

Notes

When compiling the preprocessed C code files, the compiler needs to be able to find the ECPG header files in the PostgreSQL include directory. Therefore, one might @@ -121,7 +121,7 @@

Synopsis

-

Examples

+

Examples

If you have an embedded SQL C source file named prog1.pgc, you can create an executable program using the following sequence of commands: diff --git a/docs/en_US/pg/app-initdb.html b/docs/en_US/pg/app-initdb.html index 8c70ab2d5d..e128c7a1cc 100644 --- a/docs/en_US/pg/app-initdb.html +++ b/docs/en_US/pg/app-initdb.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

initdb — create a new PostgreSQL database cluster

-
+

Synopsis

initdb [option...] [--pgdata ] | [-D ]directory

@@ -76,7 +76,7 @@

Synopsis

-

Options

+

Options

@@ -179,7 +179,7 @@

Synopsis

-

Environment

+

Environment

PGDATA

Specifies the directory where the database cluster is to be @@ -188,7 +188,7 @@

Synopsis

-

See Also

+

See Also

postgres
diff --git a/docs/en_US/pg/app-ipcclean.html b/docs/en_US/pg/app-ipcclean.html index 6998dfc693..6bd7449598 100644 --- a/docs/en_US/pg/app-ipcclean.html +++ b/docs/en_US/pg/app-ipcclean.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

ipcclean — remove shared memory and semaphores from a failed PostgreSQL server

-
+

Synopsis

ipcclean

@@ -39,7 +39,7 @@

Synopsis

-

Notes

+

Notes

This script is a hack, but in the many years since it was written, no one has come up with an equally effective and portable solution. Since postgres can now clean up by diff --git a/docs/en_US/pg/app-pg-ctl.html b/docs/en_US/pg/app-pg-ctl.html index b76307ef30..b8e98a66ee 100644 --- a/docs/en_US/pg/app-pg-ctl.html +++ b/docs/en_US/pg/app-pg-ctl.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

pg_ctl — start, stop, or restart a PostgreSQL server

-
+

Synopsis

pg_ctl start [-w] [-s] [-D datadir] [-l filename] [-o options] [-p path]
pg_ctl stop [-W] [-s] [-D datadir] [-m [s[mart]] | [f[ast]] | [i[mmediate]] @@ -167,7 +167,7 @@

Synopsis

-

Environment

+

Environment

PGDATA

Default data directory location. @@ -180,7 +180,7 @@

Synopsis

-

Files

+

Files

postmaster.pid

The existence of this file in the data directory is used to help @@ -210,7 +210,7 @@

Synopsis

-

Notes

+

Notes

Waiting for complete start is not a well-defined operation and may fail if access control is set up so that a local client cannot connect without manual interaction (e.g., password authentication). @@ -284,7 +284,7 @@

Synopsis

-

See Also

+

See Also

postgres

diff --git a/docs/en_US/pg/app-pg-dumpall.html b/docs/en_US/pg/app-pg-dumpall.html index abb5e9f371..13a4162da7 100644 --- a/docs/en_US/pg/app-pg-dumpall.html +++ b/docs/en_US/pg/app-pg-dumpall.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

pg_dumpall — extract a PostgreSQL database cluster into a script file

-
+

Synopsis

pg_dumpall [option...]

@@ -51,7 +51,7 @@

Synopsis

-

Options

+

Options

The following command-line options control the content and format of the output. @@ -218,7 +218,7 @@

Synopsis

-

Environment

+

Environment

PGHOST

PGPORT

PGUSER @@ -228,7 +228,7 @@

Synopsis

-

Notes

+

Notes

Since pg_dumpall calls pg_dump internally, some diagnostic messages will refer to pg_dump. @@ -263,7 +263,7 @@

Synopsis

-

See Also

+

See Also

pg_dump. Check there for details on possible error conditions. Also see supported environment variables (Section 29.12, “Environment Variables”). diff --git a/docs/en_US/pg/app-pgconfig.html b/docs/en_US/pg/app-pgconfig.html index 8e2de9cd2a..b436a32b85 100644 --- a/docs/en_US/pg/app-pgconfig.html +++ b/docs/en_US/pg/app-pgconfig.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

pg_config — retrieve information about the installed version of PostgreSQL

-
+

Synopsis

pg_config [option...]

-

Description

+

Description

The pg_config utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be used by software packages that want to interface @@ -31,7 +31,7 @@

Synopsis

-

Options

+

Options

To use pg_config, supply one or more of the following options:

@@ -133,7 +133,7 @@

Synopsis

-

Notes

+

Notes

The option --includedir-server was new in PostgreSQL 7.2. In prior releases, the server include files were installed in the same location as the client headers, which could @@ -155,7 +155,7 @@

Synopsis

-

Example

+

Example

To reproduce the build configuration of the current PostgreSQL installation, run the following command:

@@ -168,7 +168,7 @@

Synopsis

-

History

+

History

The pg_config utility first appeared in PostgreSQL 7.1.

diff --git a/docs/en_US/pg/app-pgcontroldata.html b/docs/en_US/pg/app-pgcontroldata.html index 00885f44b9..0f7f6b13fd 100644 --- a/docs/en_US/pg/app-pgcontroldata.html +++ b/docs/en_US/pg/app-pgcontroldata.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Name

pg_controldata — display control information of a PostgreSQL database cluster

-
+

Synopsis

pg_controldata [datadir]

@@ -36,7 +36,7 @@

Synopsis

-

Environment

+

Environment

PGDATA

Default data directory location diff --git a/docs/en_US/pg/app-pgdump.html b/docs/en_US/pg/app-pgdump.html index a1dae2bba8..5b6d5effb3 100644 --- a/docs/en_US/pg/app-pgdump.html +++ b/docs/en_US/pg/app-pgdump.html @@ -5,7 +5,7 @@ - + @@ -18,7 +18,7 @@

Name

pg_dump — extract a PostgreSQL database into a script file or other archive file

-
+

Synopsis

pg_dump [option...] [dbname]

@@ -462,7 +462,7 @@

Note

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -602,7 +602,7 @@

Note

-

History

+

History

The pg_dump utility first appeared in Postgres95 release 0.02. The non-plain-text output formats were introduced in @@ -610,7 +610,7 @@

Note

-

See Also

+

See Also

pg_dumpall, pg_restore, psql, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-pgresetxlog.html b/docs/en_US/pg/app-pgresetxlog.html index cbbe44a00c..6c89a20eba 100644 --- a/docs/en_US/pg/app-pgresetxlog.html +++ b/docs/en_US/pg/app-pgresetxlog.html @@ -5,7 +5,7 @@ - + @@ -131,7 +131,7 @@

Synopsis

-

Notes

+

Notes

This command must not be used when the server is running. pg_resetxlog will refuse to start up if it finds a server lock file in the data directory. If the diff --git a/docs/en_US/pg/app-pgrestore.html b/docs/en_US/pg/app-pgrestore.html index f1bf3135b3..caf85bba5a 100644 --- a/docs/en_US/pg/app-pgrestore.html +++ b/docs/en_US/pg/app-pgrestore.html @@ -5,7 +5,7 @@ - + @@ -18,7 +18,7 @@

Name

pg_restore — restore a PostgreSQL database from an archive file created by pg_dump

-
+

Synopsis

pg_restore [option...] [filename]

@@ -312,7 +312,7 @@

Synopsis

-

Environment

+

Environment

PGHOST

PGPORT

PGUSER @@ -451,13 +451,13 @@

Synopsis

-

History

+

History

The pg_restore utility first appeared in PostgreSQL 7.1.

-

See Also

+

See Also

pg_dump, pg_dumpall, psql, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-postgres.html b/docs/en_US/pg/app-postgres.html index 7bffd7400a..6ce9436828 100644 --- a/docs/en_US/pg/app-postgres.html +++ b/docs/en_US/pg/app-postgres.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

postgres — PostgreSQL database server

-
+

Synopsis

postgres [option...]

-

Description

+

Description

postgres is the PostgreSQL database server. In order for a client application to access a database it connects (over a @@ -42,30 +42,29 @@

Synopsis

-D option or the PGDATA environment variable; there is no default. Typically, -D or PGDATA points directly to the data area directory - created by initdb. Other possible file layouts are - discussed in Section 17.2, “File Locations”. A - data area is created with initdb. + created by initdb. Other possible file layouts are + discussed in Section 17.2, “File Locations”.

By default postgres starts in the foreground and prints log messages to the standard error stream. In - practical applications the postgres + practical applications postgres should be started as a background process, perhaps at boot time.

The postgres command can also be called in single-user mode. The primary use for this mode is during bootstrapping by initdb. Sometimes it is used - for debugging or disaster recovery. When invoked in interactive + for debugging or disaster recovery (but note that running a single-user + server is not truly suitable for debugging the server, since no + realistic interprocess communication and locking will happen). + When invoked in single-user mode from the shell, the user can enter queries and the results will be printed to the screen, but in a form that is more useful - for developers than end users. But note that running a single-user - server is not truly suitable for debugging the server since no - realistic interprocess communication and locking will happen. When - running a stand-alone server, the session user will be set to the - user with ID 1. This user does not actually have to exist, so a - stand-alone server can be used to manually recover from certain - kinds of accidental damage to the system catalogs. Implicit - superuser powers are granted to the user with ID 1 in single-user - mode. + for developers than end users. In the single-user mode, + the session user will be set to the user with ID 1, and implicit + superuser powers are granted to this user. + This user does not actually have to exist, so the single-user mode + can be used to manually recover from certain + kinds of accidental damage to the system catalogs.

@@ -81,7 +80,7 @@

Synopsis

postgres command-line options.

-

General Purpose

+

General Purpose

-A 0|1

Enables run-time assertion checks, which is a debugging aid to @@ -90,9 +89,9 @@

Synopsis

compiled. If so, the default is on.

-B nbuffers
-

Sets the number of shared buffers for use by the server - processes. The default value of this parameter is chosen - automatically by initdb; refer to Section 17.4.1, “Memory” for more information. +

Sets the number of shared buffers for use by the server + processes. The default value of this parameter is chosen + automatically by initdb; refer to Section 17.4.1, “Memory” for more information.

-c name=value

Sets a named run-time parameter. The configuration parameters @@ -107,7 +106,7 @@

Synopsis

debugging output is written to the server log. Values are from 1 to 5. It is also possible to pass -d 0 for a specific session, which will prevent the - server log level of the postgres from being + server log level of the parent postgres process from being propagated to this session.

-D datadir
@@ -117,22 +116,17 @@

Synopsis

-e

Sets the default date style to “European”, that is - DMY ordering of input date fields. This also causes - the day to be printed before the month in certain date output formats. - See Section 8.5, “Date/Time Types” for more information. + DMY ordering of input date fields. This also causes + the day to be printed before the month in certain date output formats. + See Section 8.5, “Date/Time Types” for more information.

-F
-
-

Disables fsync calls for improved +

Disables fsync calls for improved performance, at the risk of data corruption in the event of a system crash. Specifying this option is equivalent to disabling the fsync configuration parameter. Read the detailed documentation before using this! -

-

--fsync=true has the opposite effect - of this option. -

-
+

-h hostname

Specifies the IP host name or address on which postgres is to listen for TCP/IP @@ -141,7 +135,7 @@

Synopsis

listening on all available interfaces. An empty value specifies not listening on any IP addresses, in which case only Unix-domain sockets can be used to connect to the - postgres. Defaults to listening only on + server. Defaults to listening only on localhost. Specifying this option is equivalent to setting the listen_addresses configuration parameter.

@@ -159,74 +153,62 @@

Synopsis

-k directory
-

Specifies the directory of the Unix-domain socket on which - postgres is to listen for - connections from client applications. The default is normally - /tmp, but can be changed at build time. +

Specifies the directory of the Unix-domain socket on which + postgres is to listen for + connections from client applications. The default is normally + /tmp, but can be changed at build time.

-l
-

Enables secure connections using SSL. - PostgreSQL must have been compiled with - support for SSL for this option to be - available. For more information on using SSL, - refer to Section 16.7, “Secure TCP/IP Connections with SSL”. +

Enables secure connections using SSL. + PostgreSQL must have been compiled with + support for SSL for this option to be + available. For more information on using SSL, + refer to Section 16.7, “Secure TCP/IP Connections with SSL”.

-N max-connections
-

Sets the maximum number of client connections that this - postgres will accept. By - default, this value is 32, but it can be set as high as your - system will support. (Note that - -B is required to be at least twice - -N. See Section 16.4, “Managing Kernel Resources” for a discussion of - system resource requirements for large numbers of client - connections.) Specifying this option is equivalent to setting the - max_connections configuration parameter. +

Sets the maximum number of client connections that this + server will accept. By + default, this value is 32, but it can be set as high as your + system will support. (Note that + -B is required to be at least twice + -N. See Section 16.4, “Managing Kernel Resources” for a discussion of + system resource requirements for large numbers of client + connections.) Specifying this option is equivalent to setting the + max_connections configuration parameter.

-o extra-options
-

The command line-style options specified in extra-options are passed to - all server processes started by this - postgres. If the option string contains - any spaces, the entire string must be quoted. +

The command line-style options specified in extra-options are passed to + all server processes started by this + postgres process. If the option string contains + any spaces, the entire string must be quoted.

The use of this option is obsolete; all command-line options for server processes can be specified directly on the - postgres command line + postgres command line.

-p port
-

Specifies the TCP/IP port or local Unix domain socket file - extension on which postgres - is to listen for connections from client applications. - Defaults to the value of the PGPORT environment - variable, or if PGPORT is not set, then - defaults to the value established during compilation (normally - 5432). If you specify a port other than the default port, - then all client applications must specify the same port using - either command-line options or PGPORT. +

Specifies the TCP/IP port or local Unix domain socket file + extension on which postgres + is to listen for connections from client applications. + Defaults to the value of the PGPORT environment + variable, or if PGPORT is not set, then + defaults to the value established during compilation (normally + 5432). If you specify a port other than the default port, + then all client applications must specify the same port using + either command-line options or PGPORT.

-s
-

Print time information and other statistics at the end of each command. - This is useful for benchmarking or for use in tuning the number of - buffers. +

Print time information and other statistics at the end of each command. + This is useful for benchmarking or for use in tuning the number of + buffers. +

+
-S work-mem
+

Specifies the amount of memory to be used by internal sorts and hashes + before resorting to temporary disk files. See the description of the + work_mem configuration parameter in Section 17.4.1, “Memory”.

-
-S
-
-

Specifies that the postgres - process should start up in silent mode. That is, it will - disassociate from the user's (controlling) terminal, start its - own process group, and redirect its standard output and - standard error to /dev/null. -

-

Using this switch discards all logging output, which is - probably not what you want, since it makes it very difficult - to troubleshoot problems. See below for a better way to start - postgres in the background. -

-

--silent-mode=false has the opposite effect - of this option. -

-
--name=value

Sets a named run-time parameter; a shorter form of -c. @@ -239,7 +221,7 @@

Synopsis

-

Semi-internal Options

+

Semi-internal Options

There are several other options that may be specified, used mainly for debugging purposes and in some cases to assist with recovery of severely damaged databases. There should be no reason @@ -251,11 +233,11 @@

Synopsis

-f { s | i | m | n | h }
-

Forbids the use of particular scan and join methods: - s and i - disable sequential and index scans respectively, while - n, m, and h - disable nested-loop, merge and hash joins respectively. +

Forbids the use of particular scan and join methods: + s and i + disable sequential and index scans respectively, while + n, m, and h + disable nested-loop, merge and hash joins respectively.

Neither sequential scans nor nested-loop joins can be disabled completely; the -fs and @@ -276,18 +258,18 @@

Synopsis

memory and semaphore state.

-O
-

Allows the structure of system tables to be modified. This is - used by initdb. +

Allows the structure of system tables to be modified. This is + used by initdb.

-P
-

Ignore system indexes when reading system tables (but still update - the indexes when modifying the tables). This is useful when - recovering from damaged system indexes. +

Ignore system indexes when reading system tables (but still update + the indexes when modifying the tables). This is useful when + recovering from damaged system indexes.

-t pa[rser] | pl[anner] | e[xecutor]
-

Print timing statistics for each query relating to each of the - major system modules. This option cannot be used together - with the -s option. +

Print timing statistics for each query relating to each of the + major system modules. This option cannot be used together + with the -s option.

-T

This option is for debugging problems that cause a server @@ -303,9 +285,9 @@

Synopsis

dumps from all server processes by hand.

-v protocol
-

Specifies the version number of the frontend/backend protocol - to be used for a particular session. This option is for - internal use only. +

Specifies the version number of the frontend/backend protocol + to be used for a particular session. This option is for + internal use only.

-W seconds

A delay of this many seconds occurs when a new server process @@ -314,41 +296,41 @@

Synopsis

server process with a debugger.

-y database
-

Indicates that this is a subprocess started by - postgres and specifies the database to - use. This option is for internal use only. +

Indicates that this is a subprocess started by a parent + postgres process, and specifies the database to + use. This option is for internal use only.

-

Options for single-user mode

+

Options for single-user mode

The following options only apply to the single-user mode.

--single
-

Selects the single-user mode. This must be the first argument - on the command line. +

Selects the single-user mode. This must be the first argument + on the command line.

database
-

Specifies the name of the database to be accessed. If it is - omitted it defaults to the user name. +

Specifies the name of the database to be accessed. If it is + omitted it defaults to the user name.

-E
-

Echo all commands. +

Echo all commands.

-j
-

Disables use of newline as a statement delimiter. +

Disables use of newline as a statement delimiter.

-r filename
-

Send all server log output to filename. In normal multiuser - mode, this option is ignored, and stderr is - used by all processes. +

Send all server log output to filename. In normal multiuser + mode, this option is ignored, and stderr is + used by all processes.

-

Environment

+

Environment

PGCLIENTENCODING

Default character encoding used by clients. (The clients may @@ -371,7 +353,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

A failure message mentioning semget or shmget probably indicates you need to configure your kernel to provide adequate shared memory and semaphores. For more @@ -408,7 +390,7 @@

Synopsis

-

Notes

+

Notes

If at all possible, do not use SIGKILL to kill the main postgres server. Doing so will prevent @@ -454,7 +436,7 @@

Synopsis

-

Usage

+

Usage

To start a single-user mode server, use a command like 

postgres --single -D /usr/local/pgsql/data other-options my_database
@@ -500,8 +482,7 @@

Synopsis

This command will start up postgres communicating through the port 1234. In order to connect to this - postgres using psql, you would need to - run it as + server using psql, you would need to run it as 

$ psql -p 1234

@@ -526,7 +507,7 @@

Synopsis

-

See Also

+

See Also

initdb, pg_ctl

diff --git a/docs/en_US/pg/app-postmaster.html b/docs/en_US/pg/app-postmaster.html index 1ca4ad1d5d..383bd268f6 100644 --- a/docs/en_US/pg/app-postmaster.html +++ b/docs/en_US/pg/app-postmaster.html @@ -5,7 +5,7 @@ - + @@ -17,17 +17,17 @@

Name

postmaster — PostgreSQL database server

-
+

Synopsis

postmaster [option...]

-

Description

+

Description

postmaster is a deprecated alias of postgres.

-

See Also

+

See Also

postgres

diff --git a/docs/en_US/pg/app-psql.html b/docs/en_US/pg/app-psql.html index 2e18e75cfa..9748b33869 100644 --- a/docs/en_US/pg/app-psql.html +++ b/docs/en_US/pg/app-psql.html @@ -5,7 +5,7 @@ - + @@ -18,13 +18,13 @@

Name

psql — PostgreSQL interactive terminal

-
+

Synopsis

psql [option...] [dbname [username]]

-

Description

+

Description

psql is a terminal-based front-end to PostgreSQL. It enables you to type in queries interactively, issue them to @@ -64,9 +64,10 @@

Synopsis

it contains no psql specific features), or a single backslash command. Thus you cannot mix SQL and psql - meta-commands. To achieve that, you could pipe the string into - psql, like this: echo "\x \\ - select * from foo;" | psql. + meta-commands with this option. To achieve that, you could + pipe the string into psql, like + this: echo '\x \\ SELECT * FROM foo;' | psql. + (\\ is the separator meta-command.)

If the command string contains multiple SQL commands, they are processed in a single transaction, unless there are explicit @@ -329,7 +330,7 @@

Note

-

Exit Status

+

Exit Status

psql returns 0 to the shell if it finished normally, 1 if a fatal error of its own (out of memory, file not found) occurs, 2 if the connection to the server went bad @@ -338,7 +339,7 @@

Note

-

Usage

+

Usage

Connecting To A Database

psql is a regular @@ -383,7 +384,7 @@

Note

the string =>. For example, 

$ psql testdb
-Welcome to psql 8.2.0, the PostgreSQL interactive terminal.
+Welcome to psql 8.2.1, the PostgreSQL interactive terminal.
 
 Type:  \copyright for distribution terms
        \h for help with SQL commands
@@ -408,7 +409,7 @@ 
Note
-

Meta-Commands

+

Meta-Commands

Anything you enter in psql that begins with an unquoted backslash is a psql meta-command that is processed by psql @@ -1143,7 +1144,7 @@

Note

Patterns

-

The various \d commands accept a pattern parameter to specify the +

The various \d commands accept a pattern parameter to specify the object name(s) to be displayed. In the simplest case, a pattern is just the exact name of the object. The characters within a pattern are normally folded to lower case, just as in SQL names; @@ -1206,7 +1207,7 @@

Note

-

Advanced features

+

Advanced features

Variables

psql provides variable substitution @@ -1481,7 +1482,7 @@

Note

-

+

SQL Interpolation

An additional useful feature of psql variables is that you can substitute (“interpolate”) @@ -1658,7 +1659,7 @@

Note

-

Command-Line Editing

+

Command-Line Editing

psql supports the Readline library for convenient line editing and retrieval. The command history is automatically saved when psql @@ -1681,7 +1682,7 @@

Note

-

Environment

+

Environment

PAGER

If the query results do not fit on the screen, they are piped @@ -1719,7 +1720,7 @@

Note

-

Files

+

Files

  • Before starting up, psql attempts to read and execute commands from the system-wide @@ -1735,7 +1736,7 @@

    Note

  • Both the system-wide psqlrc file and the user's ~/.psqlrc file can be made version-specific by appending a dash and the PostgreSQL - release number, for example ~/.psqlrc-8.2.0. + release number, for example ~/.psqlrc-8.2.1. A matching version-specific file will be read in preference to a non-version-specific file.

    • @@ -1746,7 +1747,7 @@

    Note

-

Notes

+

Notes

  • In an earlier life psql allowed the @@ -1772,7 +1773,7 @@

    Note

-

Notes for Windows users

+

Notes for Windows users

psql is built as a “console application”. Since the Windows console windows use a different encoding than the rest of the system, you must take special care diff --git a/docs/en_US/pg/app-reindexdb.html b/docs/en_US/pg/app-reindexdb.html index 78be73ee42..76108aaee5 100644 --- a/docs/en_US/pg/app-reindexdb.html +++ b/docs/en_US/pg/app-reindexdb.html @@ -5,7 +5,7 @@ - + @@ -17,12 +17,12 @@

Name

reindexdb — reindex a PostgreSQL database

-
+

Synopsis

reindexdb [connection-option...] [--table | -t table ] [--index | -i index ] [dbname]
reindexdb [connection-option...] [--all | -a]
reindexdb [connection-option...] [--system | -s] [dbname]

-

Description

+

Description

reindexdb is a utility for rebuilding indexes in a PostgreSQL database.

@@ -33,7 +33,7 @@

Synopsis

-

Options

+

Options

reindexdb accepts the following command-line arguments:

@@ -116,7 +116,7 @@

Synopsis

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -126,7 +126,7 @@

Synopsis

-

Diagnostics

+

Diagnostics

In case of difficulty, see REINDEX and psql for discussions of potential problems and error messages. The database server must be running at the @@ -136,7 +136,7 @@

Synopsis

-

Notes

+

Notes

reindexdb might need to connect several times to the PostgreSQL server, asking for a password each time. It is convenient to have a @@ -144,7 +144,7 @@

Synopsis

-

Examples

+

Examples

To reindex the database test: 

$ reindexdb test
@@ -158,7 +158,7 @@

Synopsis

-

See Also

+

See Also

REINDEX, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/app-vacuumdb.html b/docs/en_US/pg/app-vacuumdb.html index c60536d14a..fa145c74b2 100644 --- a/docs/en_US/pg/app-vacuumdb.html +++ b/docs/en_US/pg/app-vacuumdb.html @@ -5,7 +5,7 @@ - + @@ -17,14 +17,14 @@

Name

vacuumdb — garbage-collect and analyze a PostgreSQL database

-
+

Synopsis

vacuumdb [connection-option...] [[--full] | [-f]] [[--verbose] | [-v]] [[--analyze] | [-z]] [--table | -t table [( column [,...] )] ] [dbname]
vacuumdb [connection-options...] [[--all] | [-a]] [[--full] | [-f]] [[--verbose] | [-v]] [[--analyze] | [-z]]

-

Description

+

Description

vacuumdb is a utility for cleaning a PostgreSQL database. vacuumdb will also generate internal statistics @@ -37,7 +37,7 @@

Synopsis

-

Options

+

Options

vacuumdb accepts the following command-line arguments:

@@ -136,7 +136,7 @@

Tip

-

Environment

+

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER @@ -146,7 +146,7 @@

Tip

-

Diagnostics

+

Diagnostics

In case of difficulty, see VACUUM and psql for discussions of potential problems and error messages. The database server must be running at the @@ -156,7 +156,7 @@

Tip

-

Notes

+

Notes

vacuumdb might need to connect several times to the PostgreSQL server, asking for a password each time. It is convenient to have a @@ -164,7 +164,7 @@

Tip

-

Examples

+

Examples

To clean the database test: 

$ vacuumdb test
@@ -186,7 +186,7 @@

Tip

-

See Also

+

See Also

VACUUM, Environment Variables (Section 29.12, “Environment Variables”)
diff --git a/docs/en_US/pg/appendixes.html b/docs/en_US/pg/appendixes.html index a86381bcc4..c7debd3545 100644 --- a/docs/en_US/pg/appendixes.html +++ b/docs/en_US/pg/appendixes.html @@ -5,8 +5,8 @@ - - + + @@ -20,7 +20,7 @@
A. PostgreSQL Error Codes
B. Date/Time Support
-
B.1. Date/Time Input Interpretation
+
B.1. Date/Time Input Interpretation
B.2. Date/Time Key Words
B.3. Date/Time Configuration Files
B.4. History of Units
@@ -33,433 +33,458 @@
E. Release Notes
-
E.1. Release 8.2
+
E.1. Release 8.2.1
-
E.1.1. Overview
-
E.1.2. Migration to version 8.2
-
E.1.3. Changes
+
E.1.1. Migration to version 8.2.1
+
E.1.2. Changes
-
E.2. Release 8.1.5
+
E.2. Release 8.2
-
E.2.1. Migration to version 8.1.5
-
E.2.2. Changes
+
E.2.1. Overview
+
E.2.2. Migration to version 8.2
+
E.2.3. Changes
-
E.3. Release 8.1.4
+
E.3. Release 8.1.6
-
E.3.1. Migration to version 8.1.4
-
E.3.2. Changes
+
E.3.1. Migration to version 8.1.6
+
E.3.2. Changes
-
E.4. Release 8.1.3
+
E.4. Release 8.1.5
-
E.4.1. Migration to version 8.1.3
-
E.4.2. Changes
+
E.4.1. Migration to version 8.1.5
+
E.4.2. Changes
-
E.5. Release 8.1.2
+
E.5. Release 8.1.4
-
E.5.1. Migration to version 8.1.2
-
E.5.2. Changes
+
E.5.1. Migration to version 8.1.4
+
E.5.2. Changes
-
E.6. Release 8.1.1
+
E.6. Release 8.1.3
-
E.6.1. Migration to version 8.1.1
-
E.6.2. Changes
+
E.6.1. Migration to version 8.1.3
+
E.6.2. Changes
-
E.7. Release 8.1
+
E.7. Release 8.1.2
-
E.7.1. Overview
-
E.7.2. Migration to version 8.1
-
E.7.3. Additional Changes
+
E.7.1. Migration to version 8.1.2
+
E.7.2. Changes
-
E.8. Release 8.0.9
+
E.8. Release 8.1.1
-
E.8.1. Migration to version 8.0.9
-
E.8.2. Changes
+
E.8.1. Migration to version 8.1.1
+
E.8.2. Changes
-
E.9. Release 8.0.8
+
E.9. Release 8.1
-
E.9.1. Migration to version 8.0.8
-
E.9.2. Changes
+
E.9.1. Overview
+
E.9.2. Migration to version 8.1
+
E.9.3. Additional Changes
-
E.10. Release 8.0.7
+
E.10. Release 8.0.10
-
E.10.1. Migration to version 8.0.7
-
E.10.2. Changes
+
E.10.1. Migration to version 8.0.10
+
E.10.2. Changes
-
E.11. Release 8.0.6
+
E.11. Release 8.0.9
-
E.11.1. Migration to version 8.0.6
-
E.11.2. Changes
+
E.11.1. Migration to version 8.0.9
+
E.11.2. Changes
-
E.12. Release 8.0.5
+
E.12. Release 8.0.8
-
E.12.1. Migration to version 8.0.5
-
E.12.2. Changes
+
E.12.1. Migration to version 8.0.8
+
E.12.2. Changes
-
E.13. Release 8.0.4
+
E.13. Release 8.0.7
-
E.13.1. Migration to version 8.0.4
-
E.13.2. Changes
+
E.13.1. Migration to version 8.0.7
+
E.13.2. Changes
-
E.14. Release 8.0.3
+
E.14. Release 8.0.6
-
E.14.1. Migration to version 8.0.3
-
E.14.2. Changes
+
E.14.1. Migration to version 8.0.6
+
E.14.2. Changes
-
E.15. Release 8.0.2
+
E.15. Release 8.0.5
-
E.15.1. Migration to version 8.0.2
-
E.15.2. Changes
+
E.15.1. Migration to version 8.0.5
+
E.15.2. Changes
-
E.16. Release 8.0.1
+
E.16. Release 8.0.4
-
E.16.1. Migration to version 8.0.1
-
E.16.2. Changes
+
E.16.1. Migration to version 8.0.4
+
E.16.2. Changes
-
E.17. Release 8.0
+
E.17. Release 8.0.3
-
E.17.1. Overview
-
E.17.2. Migration to version 8.0
-
E.17.3. Deprecated Features
-
E.17.4. Changes
+
E.17.1. Migration to version 8.0.3
+
E.17.2. Changes
-
E.18. Release 7.4.14
+
E.18. Release 8.0.2
-
E.18.1. Migration to version 7.4.14
-
E.18.2. Changes
+
E.18.1. Migration to version 8.0.2
+
E.18.2. Changes
-
E.19. Release 7.4.13
+
E.19. Release 8.0.1
-
E.19.1. Migration to version 7.4.13
-
E.19.2. Changes
+
E.19.1. Migration to version 8.0.1
+
E.19.2. Changes
-
E.20. Release 7.4.12
+
E.20. Release 8.0
-
E.20.1. Migration to version 7.4.12
-
E.20.2. Changes
+
E.20.1. Overview
+
E.20.2. Migration to version 8.0
+
E.20.3. Deprecated Features
+
E.20.4. Changes
-
E.21. Release 7.4.11
+
E.21. Release 7.4.15
-
E.21.1. Migration to version 7.4.11
-
E.21.2. Changes
+
E.21.1. Migration to version 7.4.15
+
E.21.2. Changes
-
E.22. Release 7.4.10
+
E.22. Release 7.4.14
-
E.22.1. Migration to version 7.4.10
-
E.22.2. Changes
+
E.22.1. Migration to version 7.4.14
+
E.22.2. Changes
-
E.23. Release 7.4.9
+
E.23. Release 7.4.13
-
E.23.1. Migration to version 7.4.9
-
E.23.2. Changes
+
E.23.1. Migration to version 7.4.13
+
E.23.2. Changes
-
E.24. Release 7.4.8
+
E.24. Release 7.4.12
-
E.24.1. Migration to version 7.4.8
-
E.24.2. Changes
+
E.24.1. Migration to version 7.4.12
+
E.24.2. Changes
-
E.25. Release 7.4.7
+
E.25. Release 7.4.11
-
E.25.1. Migration to version 7.4.7
-
E.25.2. Changes
+
E.25.1. Migration to version 7.4.11
+
E.25.2. Changes
-
E.26. Release 7.4.6
+
E.26. Release 7.4.10
-
E.26.1. Migration to version 7.4.6
-
E.26.2. Changes
+
E.26.1. Migration to version 7.4.10
+
E.26.2. Changes
-
E.27. Release 7.4.5
+
E.27. Release 7.4.9
-
E.27.1. Migration to version 7.4.5
-
E.27.2. Changes
+
E.27.1. Migration to version 7.4.9
+
E.27.2. Changes
-
E.28. Release 7.4.4
+
E.28. Release 7.4.8
-
E.28.1. Migration to version 7.4.4
-
E.28.2. Changes
+
E.28.1. Migration to version 7.4.8
+
E.28.2. Changes
-
E.29. Release 7.4.3
+
E.29. Release 7.4.7
-
E.29.1. Migration to version 7.4.3
-
E.29.2. Changes
+
E.29.1. Migration to version 7.4.7
+
E.29.2. Changes
-
E.30. Release 7.4.2
+
E.30. Release 7.4.6
-
E.30.1. Migration to version 7.4.2
-
E.30.2. Changes
+
E.30.1. Migration to version 7.4.6
+
E.30.2. Changes
-
E.31. Release 7.4.1
+
E.31. Release 7.4.5
-
E.31.1. Migration to version 7.4.1
-
E.31.2. Changes
+
E.31.1. Migration to version 7.4.5
+
E.31.2. Changes
-
E.32. Release 7.4
+
E.32. Release 7.4.4
-
E.32.1. Overview
-
E.32.2. Migration to version 7.4
-
E.32.3. Changes
+
E.32.1. Migration to version 7.4.4
+
E.32.2. Changes
-
E.33. Release 7.3.16
+
E.33. Release 7.4.3
-
E.33.1. Migration to version 7.3.16
-
E.33.2. Changes
+
E.33.1. Migration to version 7.4.3
+
E.33.2. Changes
-
E.34. Release 7.3.15
+
E.34. Release 7.4.2
-
E.34.1. Migration to version 7.3.15
-
E.34.2. Changes
+
E.34.1. Migration to version 7.4.2
+
E.34.2. Changes
-
E.35. Release 7.3.14
+
E.35. Release 7.4.1
-
E.35.1. Migration to version 7.3.14
-
E.35.2. Changes
+
E.35.1. Migration to version 7.4.1
+
E.35.2. Changes
-
E.36. Release 7.3.13
+
E.36. Release 7.4
-
E.36.1. Migration to version 7.3.13
-
E.36.2. Changes
+
E.36.1. Overview
+
E.36.2. Migration to version 7.4
+
E.36.3. Changes
-
E.37. Release 7.3.12
+
E.37. Release 7.3.17
-
E.37.1. Migration to version 7.3.12
-
E.37.2. Changes
+
E.37.1. Migration to version 7.3.17
+
E.37.2. Changes
-
E.38. Release 7.3.11
+
E.38. Release 7.3.16
-
E.38.1. Migration to version 7.3.11
-
E.38.2. Changes
+
E.38.1. Migration to version 7.3.16
+
E.38.2. Changes
-
E.39. Release 7.3.10
+
E.39. Release 7.3.15
-
E.39.1. Migration to version 7.3.10
-
E.39.2. Changes
+
E.39.1. Migration to version 7.3.15
+
E.39.2. Changes
-
E.40. Release 7.3.9
+
E.40. Release 7.3.14
-
E.40.1. Migration to version 7.3.9
-
E.40.2. Changes
+
E.40.1. Migration to version 7.3.14
+
E.40.2. Changes
-
E.41. Release 7.3.8
+
E.41. Release 7.3.13
-
E.41.1. Migration to version 7.3.8
-
E.41.2. Changes
+
E.41.1. Migration to version 7.3.13
+
E.41.2. Changes
-
E.42. Release 7.3.7
+
E.42. Release 7.3.12
-
E.42.1. Migration to version 7.3.7
-
E.42.2. Changes
+
E.42.1. Migration to version 7.3.12
+
E.42.2. Changes
-
E.43. Release 7.3.6
+
E.43. Release 7.3.11
-
E.43.1. Migration to version 7.3.6
-
E.43.2. Changes
+
E.43.1. Migration to version 7.3.11
+
E.43.2. Changes
-
E.44. Release 7.3.5
+
E.44. Release 7.3.10
-
E.44.1. Migration to version 7.3.5
-
E.44.2. Changes
+
E.44.1. Migration to version 7.3.10
+
E.44.2. Changes
-
E.45. Release 7.3.4
+
E.45. Release 7.3.9
-
E.45.1. Migration to version 7.3.4
-
E.45.2. Changes
+
E.45.1. Migration to version 7.3.9
+
E.45.2. Changes
-
E.46. Release 7.3.3
+
E.46. Release 7.3.8
-
E.46.1. Migration to version 7.3.3
-
E.46.2. Changes
+
E.46.1. Migration to version 7.3.8
+
E.46.2. Changes
-
E.47. Release 7.3.2
+
E.47. Release 7.3.7
-
E.47.1. Migration to version 7.3.2
-
E.47.2. Changes
+
E.47.1. Migration to version 7.3.7
+
E.47.2. Changes
-
E.48. Release 7.3.1
+
E.48. Release 7.3.6
-
E.48.1. Migration to version 7.3.1
-
E.48.2. Changes
+
E.48.1. Migration to version 7.3.6
+
E.48.2. Changes
-
E.49. Release 7.3
+
E.49. Release 7.3.5
-
E.49.1. Overview
-
E.49.2. Migration to version 7.3
-
E.49.3. Changes
+
E.49.1. Migration to version 7.3.5
+
E.49.2. Changes
-
E.50. Release 7.2.8
+
E.50. Release 7.3.4
-
E.50.1. Migration to version 7.2.8
-
E.50.2. Changes
+
E.50.1. Migration to version 7.3.4
+
E.50.2. Changes
-
E.51. Release 7.2.7
+
E.51. Release 7.3.3
-
E.51.1. Migration to version 7.2.7
-
E.51.2. Changes
+
E.51.1. Migration to version 7.3.3
+
E.51.2. Changes
-
E.52. Release 7.2.6
+
E.52. Release 7.3.2
-
E.52.1. Migration to version 7.2.6
-
E.52.2. Changes
+
E.52.1. Migration to version 7.3.2
+
E.52.2. Changes
-
E.53. Release 7.2.5
+
E.53. Release 7.3.1
-
E.53.1. Migration to version 7.2.5
-
E.53.2. Changes
+
E.53.1. Migration to version 7.3.1
+
E.53.2. Changes
-
E.54. Release 7.2.4
+
E.54. Release 7.3
-
E.54.1. Migration to version 7.2.4
-
E.54.2. Changes
+
E.54.1. Overview
+
E.54.2. Migration to version 7.3
+
E.54.3. Changes
-
E.55. Release 7.2.3
+
E.55. Release 7.2.8
-
E.55.1. Migration to version 7.2.3
-
E.55.2. Changes
+
E.55.1. Migration to version 7.2.8
+
E.55.2. Changes
-
E.56. Release 7.2.2
+
E.56. Release 7.2.7
-
E.56.1. Migration to version 7.2.2
-
E.56.2. Changes
+
E.56.1. Migration to version 7.2.7
+
E.56.2. Changes
-
E.57. Release 7.2.1
+
E.57. Release 7.2.6
-
E.57.1. Migration to version 7.2.1
-
E.57.2. Changes
+
E.57.1. Migration to version 7.2.6
+
E.57.2. Changes
-
E.58. Release 7.2
+
E.58. Release 7.2.5
-
E.58.1. Overview
-
E.58.2. Migration to version 7.2
-
E.58.3. Changes
+
E.58.1. Migration to version 7.2.5
+
E.58.2. Changes
-
E.59. Release 7.1.3
+
E.59. Release 7.2.4
-
E.59.1. Migration to version 7.1.3
-
E.59.2. Changes
+
E.59.1. Migration to version 7.2.4
+
E.59.2. Changes
-
E.60. Release 7.1.2
+
E.60. Release 7.2.3
-
E.60.1. Migration to version 7.1.2
-
E.60.2. Changes
+
E.60.1. Migration to version 7.2.3
+
E.60.2. Changes
-
E.61. Release 7.1.1
+
E.61. Release 7.2.2
-
E.61.1. Migration to version 7.1.1
-
E.61.2. Changes
+
E.61.1. Migration to version 7.2.2
+
E.61.2. Changes
-
E.62. Release 7.1
+
E.62. Release 7.2.1
-
E.62.1. Migration to version 7.1
-
E.62.2. Changes
+
E.62.1. Migration to version 7.2.1
+
E.62.2. Changes
-
E.63. Release 7.0.3
+
E.63. Release 7.2
-
E.63.1. Migration to version 7.0.3
-
E.63.2. Changes
+
E.63.1. Overview
+
E.63.2. Migration to version 7.2
+
E.63.3. Changes
-
E.64. Release 7.0.2
+
E.64. Release 7.1.3
-
E.64.1. Migration to version 7.0.2
-
E.64.2. Changes
+
E.64.1. Migration to version 7.1.3
+
E.64.2. Changes
-
E.65. Release 7.0.1
+
E.65. Release 7.1.2
-
E.65.1. Migration to version 7.0.1
-
E.65.2. Changes
+
E.65.1. Migration to version 7.1.2
+
E.65.2. Changes
-
E.66. Release 7.0
+
E.66. Release 7.1.1
-
E.66.1. Migration to version 7.0
-
E.66.2. Changes
+
E.66.1. Migration to version 7.1.1
+
E.66.2. Changes
-
E.67. Release 6.5.3
+
E.67. Release 7.1
-
E.67.1. Migration to version 6.5.3
-
E.67.2. Changes
+
E.67.1. Migration to version 7.1
+
E.67.2. Changes
-
E.68. Release 6.5.2
+
E.68. Release 7.0.3
-
E.68.1. Migration to version 6.5.2
-
E.68.2. Changes
+
E.68.1. Migration to version 7.0.3
+
E.68.2. Changes
-
E.69. Release 6.5.1
+
E.69. Release 7.0.2
-
E.69.1. Migration to version 6.5.1
-
E.69.2. Changes
+
E.69.1. Migration to version 7.0.2
+
E.69.2. Changes
-
E.70. Release 6.5
+
E.70. Release 7.0.1
-
E.70.1. Migration to version 6.5
-
E.70.2. Changes
+
E.70.1. Migration to version 7.0.1
+
E.70.2. Changes
-
E.71. Release 6.4.2
+
E.71. Release 7.0
-
E.71.1. Migration to version 6.4.2
-
E.71.2. Changes
+
E.71.1. Migration to version 7.0
+
E.71.2. Changes
-
E.72. Release 6.4.1
+
E.72. Release 6.5.3
-
E.72.1. Migration to version 6.4.1
-
E.72.2. Changes
+
E.72.1. Migration to version 6.5.3
+
E.72.2. Changes
-
E.73. Release 6.4
+
E.73. Release 6.5.2
-
E.73.1. Migration to version 6.4
-
E.73.2. Changes
+
E.73.1. Migration to version 6.5.2
+
E.73.2. Changes
-
E.74. Release 6.3.2
-
E.74.1. Changes
-
E.75. Release 6.3.1
-
E.75.1. Changes
-
E.76. Release 6.3
+
E.74. Release 6.5.1
-
E.76.1. Migration to version 6.3
-
E.76.2. Changes
+
E.74.1. Migration to version 6.5.1
+
E.74.2. Changes
-
E.77. Release 6.2.1
+
E.75. Release 6.5
-
E.77.1. Migration from version 6.2 to version 6.2.1
-
E.77.2. Changes
+
E.75.1. Migration to version 6.5
+
E.75.2. Changes
-
E.78. Release 6.2
+
E.76. Release 6.4.2
-
E.78.1. Migration from version 6.1 to version 6.2
-
E.78.2. Migration from version 1.x to version 6.2
-
E.78.3. Changes
+
E.76.1. Migration to version 6.4.2
+
E.76.2. Changes
-
E.79. Release 6.1.1
+
E.77. Release 6.4.1
-
E.79.1. Migration from version 6.1 to version 6.1.1
-
E.79.2. Changes
+
E.77.1. Migration to version 6.4.1
+
E.77.2. Changes
-
E.80. Release 6.1
+
E.78. Release 6.4
-
E.80.1. Migration to version 6.1
-
E.80.2. Changes
+
E.78.1. Migration to version 6.4
+
E.78.2. Changes
-
E.81. Release 6.0
+
E.79. Release 6.3.2
+
E.79.1. Changes
+
E.80. Release 6.3.1
+
E.80.1. Changes
+
E.81. Release 6.3
-
E.81.1. Migration from version 1.09 to version 6.0
-
E.81.2. Migration from pre-1.09 to version 6.0
-
E.81.3. Changes
+
E.81.1. Migration to version 6.3
+
E.81.2. Changes
-
E.82. Release 1.09
-
E.83. Release 1.02
+
E.82. Release 6.2.1
-
E.83.1. Migration from version 1.02 to version 1.02.1
-
E.83.2. Dump/Reload Procedure
-
E.83.3. Changes
+
E.82.1. Migration from version 6.2 to version 6.2.1
+
E.82.2. Changes
-
E.84. Release 1.01
+
E.83. Release 6.2
-
E.84.1. Migration from version 1.0 to version 1.01
-
E.84.2. Changes
+
E.83.1. Migration from version 6.1 to version 6.2
+
E.83.2. Migration from version 1.x to version 6.2
+
E.83.3. Changes
-
E.85. Release 1.0
-
E.85.1. Changes
-
E.86. Postgres95 Release 0.03
-
E.86.1. Changes
-
E.87. Postgres95 Release 0.02
-
E.87.1. Changes
-
E.88. Postgres95 Release 0.01
+
E.84. Release 6.1.1
+
+
E.84.1. Migration from version 6.1 to version 6.1.1
+
E.84.2. Changes
+
+
E.85. Release 6.1
+
+
E.85.1. Migration to version 6.1
+
E.85.2. Changes
+
+
E.86. Release 6.0
+
+
E.86.1. Migration from version 1.09 to version 6.0
+
E.86.2. Migration from pre-1.09 to version 6.0
+
E.86.3. Changes
+
+
E.87. Release 1.09
+
E.88. Release 1.02
+
+
E.88.1. Migration from version 1.02 to version 1.02.1
+
E.88.2. Dump/Reload Procedure
+
E.88.3. Changes
+
+
E.89. Release 1.01
+
+
E.89.1. Migration from version 1.0 to version 1.01
+
E.89.2. Changes
+
+
E.90. Release 1.0
+
E.90.1. Changes
+
E.91. Postgres95 Release 0.03
+
E.91.1. Changes
+
E.92. Postgres95 Release 0.02
+
E.92.1. Changes
+
E.93. Postgres95 Release 0.01
F. The CVS Repository
@@ -467,8 +492,8 @@
F.2. CVS Tree Organization
F.3. Getting The Source Via CVSup
-
F.3.1. Preparing A CVSup Client System
-
F.3.2. Running a CVSup Client
+
F.3.1. Preparing A CVSup Client System
+
F.3.2. Running a CVSup Client
G. Documentation
@@ -476,28 +501,28 @@
G.1. DocBook
G.2. Tool Sets
-
G.2.1. Linux RPM Installation
-
G.2.2. FreeBSD Installation
-
G.2.3. Debian Packages
-
G.2.4. Manual Installation from Source
+
G.2.1. Linux RPM Installation
+
G.2.2. FreeBSD Installation
+
G.2.3. Debian Packages
+
G.2.4. Manual Installation from Source
G.2.5. Detection by configure
G.3. Building The Documentation
-
G.3.1. HTML
-
G.3.2. Manpages
-
G.3.3. Print Output via JadeTex
-
G.3.4. Print Output via RTF
-
G.3.5. Plain Text Files
-
G.3.6. Syntax Check
+
G.3.1. HTML
+
G.3.2. Manpages
+
G.3.3. Print Output via JadeTex
+
G.3.4. Print Output via RTF
+
G.3.5. Plain Text Files
+
G.3.6. Syntax Check
G.4. Documentation Authoring
-
G.4.1. Emacs/PSGML
-
G.4.2. Other Emacs modes
+
G.4.1. Emacs/PSGML
+
G.4.2. Other Emacs modes
G.5. Style Guide
-
G.5.1. Reference Pages
+
G.5.1. Reference Pages
H. External Projects
diff --git a/docs/en_US/pg/applevel-consistency.html b/docs/en_US/pg/applevel-consistency.html index 6910272a3d..56a9619410 100644 --- a/docs/en_US/pg/applevel-consistency.html +++ b/docs/en_US/pg/applevel-consistency.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/arrays.html b/docs/en_US/pg/arrays.html index 0d3a35a8d9..0528edee01 100644 --- a/docs/en_US/pg/arrays.html +++ b/docs/en_US/pg/arrays.html @@ -5,7 +5,7 @@ - + @@ -14,14 +14,14 @@

8.10. Arrays

-

PostgreSQL allows columns of a table to be +

PostgreSQL allows columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type can be created. (Arrays of composite types or domains are not yet supported, however.)

-8.10.1. Declaration of Array Types

+8.10.1. Declaration of Array Types

To illustrate the use of array types, we create this table: 

CREATE TABLE sal_emp (
@@ -75,8 +75,8 @@
 
 

 

-8.10.2. Array Value Input

-
   To write an array value as a literal constant, enclose the element
+8.10.2. Array Value Input

+
   To write an array value as a literal constant, enclose the element
    values within curly braces and separate them by commas.  (If you
    know C, this is not unlike the C syntax for initializing
    structures.)  You may put double quotes around any element value,
@@ -167,7 +167,7 @@
 
 

 

-8.10.3. Accessing Arrays

+8.10.3. Accessing Arrays

 
  Now, we can run some queries on the table.
   First, we show how to access a single element of an array at a time.
   This query retrieves the names of the employees whose pay changed in
@@ -282,7 +282,7 @@
 
 

 

-8.10.4. Modifying Arrays

+8.10.4. Modifying Arrays

 
  An array value can be replaced completely:
 
 

@@ -438,7 +438,7 @@
 
 

 

-8.10.5. Searching in Arrays

+8.10.5. Searching in Arrays

 
  To search for a value in an array, you must check each value of the
   array. This can be done by hand, if you know the size of the array.
   For example:
@@ -479,7 +479,7 @@ 
Tip

 
 

 

-8.10.6. Array Input and Output Syntax

+8.10.6. Array Input and Output Syntax

 
   The external text representation of an array value consists of items that
    are interpreted according to the I/O conversion rules for the array's
    element type, plus decoration that indicates the array structure.
diff --git a/docs/en_US/pg/auth-methods.html b/docs/en_US/pg/auth-methods.html
index 8ee13f7115..c7767b0bc1 100644
--- a/docs/en_US/pg/auth-methods.html
+++ b/docs/en_US/pg/auth-methods.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -57,7 +57,7 @@
 

 

 20.2.2. Password authentication

-
    The password-based authentication methods are md5,
+
    The password-based authentication methods are md5,
     crypt, and password. These methods operate
     similarly except for the way that the password is sent across the
     connection: respectively, MD5-hashed, crypt-encrypted, and clear-text.
@@ -86,7 +86,7 @@
 

 

 20.2.3. Kerberos authentication

-
    Kerberos is an industry-standard secure
+
    Kerberos is an industry-standard secure
     authentication system suitable for distributed computing over a public
     network. A description of the Kerberos system
     is far beyond the scope of this document; in full generality it can be
@@ -164,7 +164,7 @@
 

 

 20.2.4. Ident-based authentication

-
    The ident authentication method works by obtaining the client's
+
    The ident authentication method works by obtaining the client's
     operating system user name, then determining the allowed database
     user names using a map file that lists the permitted
     corresponding pairs of names.  The determination of the client's
@@ -173,7 +173,7 @@
    

 

 

-20.2.4.1. Ident Authentication over TCP/IP

+20.2.4.1. Ident Authentication over TCP/IP

 
    The “Identification Protocol” is described in
     RFC 1413. Virtually every Unix-like
     operating system ships with an ident server that listens on TCP
@@ -223,7 +223,7 @@
 

 

 

-20.2.4.2. Ident Authentication over Local Sockets

+20.2.4.2. Ident Authentication over Local Sockets

 
    On systems supporting SO_PEERCRED requests for
     Unix-domain sockets (currently Linux, FreeBSD,
     NetBSD, OpenBSD, 
@@ -255,7 +255,7 @@
    

 
    Ident maps other than sameuser are defined in the
     ident map file, which by default is named
-    pg_ident.conf
+    pg_ident.conf
     and is stored in the
     cluster's data directory.  (It is possible to place the map file
     elsewhere, however; see the ident_file
@@ -276,7 +276,7 @@
    

 
   The pg_ident.conf file is read on start-up and
    when the main server process receives a
-   SIGHUP
+   SIGHUP
    signal. If you edit the file on an
    active system, you will need to signal the server
    (using pg_ctl reload or kill -HUP) to make it
@@ -311,7 +311,7 @@
 

 

 20.2.5. LDAP authentication

-
    This authentication method operates similarly to
+
    This authentication method operates similarly to
     password except that it uses LDAP
     as the authentication method. LDAP is used only to validate
     the user name/password pairs. Therefore the user must already
@@ -354,7 +354,7 @@
 

 

 20.2.6. PAM authentication

-
    This authentication method operates similarly to
+
    This authentication method operates similarly to
     password except that it uses PAM (Pluggable
     Authentication Modules) as the authentication mechanism. The
     default PAM service name is postgresql. You can
diff --git a/docs/en_US/pg/backup-file.html b/docs/en_US/pg/backup-file.html
index 257de200a9..f2893280a3 100644
--- a/docs/en_US/pg/backup-file.html
+++ b/docs/en_US/pg/backup-file.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/backup.html b/docs/en_US/pg/backup.html
index 666437518d..1c09f10df3 100644
--- a/docs/en_US/pg/backup.html
+++ b/docs/en_US/pg/backup.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -43,7 +43,7 @@
 
23.5. Migration Between Releases
-

As with everything that contains valuable data, PostgreSQL +

As with everything that contains valuable data, PostgreSQL databases should be backed up regularly. While the procedure is essentially simple, it is important to have a basic understanding of the underlying techniques and assumptions. diff --git a/docs/en_US/pg/biblio.html b/docs/en_US/pg/biblio.html index 720c08950a..606a6f6251 100644 --- a/docs/en_US/pg/biblio.html +++ b/docs/en_US/pg/biblio.html @@ -5,8 +5,8 @@ - - + + @@ -24,7 +24,7 @@

-SQL Reference Books

+SQL Reference Books

Reference texts for SQL features.

[bowman01] The Practical SQL Handbook. Bowman et al, 2001. Using SQL Variants. Fourth Edition. Judith Bowman, Sandra Emerson, and Marcy Darnovsky. 0-201-70309-2. 2001. Addison-Wesley Professional. Copyright © 2001.

@@ -47,7 +47,7 @@

-PostgreSQL-Specific Documentation

+PostgreSQL-Specific Documentation

This section is for related documentation.

[sim98] Enhancement of the ANSI SQL Implementation of PostgreSQL. Simkovics, 1998. Stefan Simkovics. November 29, 1998. Department of Information Systems, Vienna University of Technology. Vienna, Austria.

@@ -62,7 +62,7 @@

-Proceedings and Articles

+Proceedings and Articles

This section is for articles and newsletters.

[olson93] Partial indexing in POSTGRES: research project. Olson, 1993. Nels Olson. 1993. UCB Engin T7.49.1993 O676. University of California. Berkeley, California.

diff --git a/docs/en_US/pg/bki-commands.html b/docs/en_US/pg/bki-commands.html index facf1976fe..802f7d2f0d 100644 --- a/docs/en_US/pg/bki-commands.html +++ b/docs/en_US/pg/bki-commands.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/bki-example.html b/docs/en_US/pg/bki-example.html index 8ffcdc3666..d84ab534fa 100644 --- a/docs/en_US/pg/bki-example.html +++ b/docs/en_US/pg/bki-example.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/bki-structure.html b/docs/en_US/pg/bki-structure.html index 0c4993bb0d..555fc2ed5d 100644 --- a/docs/en_US/pg/bki-structure.html +++ b/docs/en_US/pg/bki-structure.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/bki.html b/docs/en_US/pg/bki.html index 1999e8354b..ae62e3cfd5 100644 --- a/docs/en_US/pg/bki.html +++ b/docs/en_US/pg/bki.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/bug-reporting.html b/docs/en_US/pg/bug-reporting.html index b9a1c0d9c0..74aacf2660 100644 --- a/docs/en_US/pg/bug-reporting.html +++ b/docs/en_US/pg/bug-reporting.html @@ -5,7 +5,7 @@ - + @@ -35,7 +35,7 @@

-1.5.1. Identifying Bugs

+1.5.1. Identifying Bugs

Before you report a bug, please read and re-read the documentation to verify that you can really do whatever it is you are trying. If it is not clear from the documentation whether you can do @@ -80,7 +80,7 @@

-1.5.2. What to report

+1.5.2. What to report

The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, or which part of the program has a fault. @@ -190,7 +190,7 @@

Note

subversion the package may have. If you are talking about a CVS snapshot, mention that, including its date and time.

-

If your version is older than 8.2.0 we will almost certainly +

If your version is older than 8.2.1 we will almost certainly tell you to upgrade. There are many bug fixes and improvements in each new release, so it is quite possible that a bug you have encountered in an older release of PostgreSQL @@ -241,7 +241,7 @@

Note

-1.5.3. Where to report bugs

+1.5.3. Where to report bugs

In general, send bug reports to the bug report mailing list at . You are requested to use a descriptive subject for your email diff --git a/docs/en_US/pg/catalog-pg-aggregate.html b/docs/en_US/pg/catalog-pg-aggregate.html index 8daf60421a..1e6b4245d9 100644 --- a/docs/en_US/pg/catalog-pg-aggregate.html +++ b/docs/en_US/pg/catalog-pg-aggregate.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.2. pg_aggregate

-

The catalog pg_aggregate stores information about +

The catalog pg_aggregate stores information about aggregate functions. An aggregate function is a function that operates on a set of values (typically one column from each row that matches a query condition) and returns a single value computed @@ -27,7 +27,7 @@ other information that is similar to ordinary functions.

-

Table 43.2. pg_aggregate Columns

+

Table 43.2. pg_aggregate Columns

diff --git a/docs/en_US/pg/catalog-pg-am.html b/docs/en_US/pg/catalog-pg-am.html index 57108f5678..76aa9fefda 100644 --- a/docs/en_US/pg/catalog-pg-am.html +++ b/docs/en_US/pg/catalog-pg-am.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.3. pg_am

-

The catalog pg_am stores information about index +

The catalog pg_am stores information about index access methods. There is one row for each index access method supported by the system. The contents of this catalog are discussed in detail in Chapter 49, Index Access Method Interface Definition.

-

Table 43.3. pg_am Columns

+

Table 43.3. pg_am Columns

diff --git a/docs/en_US/pg/catalog-pg-amop.html b/docs/en_US/pg/catalog-pg-amop.html index d727940bdf..68348b21d9 100644 --- a/docs/en_US/pg/catalog-pg-amop.html +++ b/docs/en_US/pg/catalog-pg-amop.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

43.4. pg_amop

-

The catalog pg_amop stores information about operators +

The catalog pg_amop stores information about operators associated with index access method operator classes. There is one row for each operator that is a member of an operator class.

-

Table 43.4. pg_amop Columns

+

Table 43.4. pg_amop Columns

diff --git a/docs/en_US/pg/catalog-pg-amproc.html b/docs/en_US/pg/catalog-pg-amproc.html index fd1ba51d9a..f7cc0d2c8a 100644 --- a/docs/en_US/pg/catalog-pg-amproc.html +++ b/docs/en_US/pg/catalog-pg-amproc.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.5. pg_amproc

-

The catalog pg_amproc stores information about support +

The catalog pg_amproc stores information about support procedures associated with index access method operator classes. There is one row for each support procedure belonging to an operator class.

-

Table 43.5. pg_amproc Columns

+

Table 43.5. pg_amproc Columns

diff --git a/docs/en_US/pg/catalog-pg-attrdef.html b/docs/en_US/pg/catalog-pg-attrdef.html index febe57d3fe..121c4afb2a 100644 --- a/docs/en_US/pg/catalog-pg-attrdef.html +++ b/docs/en_US/pg/catalog-pg-attrdef.html @@ -5,7 +5,7 @@ - + @@ -14,14 +14,14 @@

43.6. pg_attrdef

-

The catalog pg_attrdef stores column default values. The main information +

The catalog pg_attrdef stores column default values. The main information about columns is stored in pg_attribute (see below). Only columns that explicitly specify a default value (when the table is created or the column is added) will have an entry here.

-

Table 43.6. pg_attrdef Columns

+

Table 43.6. pg_attrdef Columns

diff --git a/docs/en_US/pg/catalog-pg-attribute.html b/docs/en_US/pg/catalog-pg-attribute.html index e160ebb857..20a158de0b 100644 --- a/docs/en_US/pg/catalog-pg-attribute.html +++ b/docs/en_US/pg/catalog-pg-attribute.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.7. pg_attribute

-

The catalog pg_attribute stores information about +

The catalog pg_attribute stores information about table columns. There will be exactly one pg_attribute row for every column in every table in the database. (There will also be attribute entries for @@ -25,7 +25,7 @@ historical reasons.

-

Table 43.7. pg_attribute Columns

+

Table 43.7. pg_attribute Columns

diff --git a/docs/en_US/pg/catalog-pg-auth-members.html b/docs/en_US/pg/catalog-pg-auth-members.html index f61cba857e..2848fb45c5 100644 --- a/docs/en_US/pg/catalog-pg-auth-members.html +++ b/docs/en_US/pg/catalog-pg-auth-members.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.9. pg_auth_members

-

The catalog pg_auth_members shows the membership +

The catalog pg_auth_members shows the membership relations between roles. Any non-circular set of relationships is allowed.

Because user identities are cluster-wide, @@ -24,7 +24,7 @@ one per database.

-

Table 43.9. pg_auth_members Columns

+

Table 43.9. pg_auth_members Columns

diff --git a/docs/en_US/pg/catalog-pg-authid.html b/docs/en_US/pg/catalog-pg-authid.html index ae7469d170..512943fec3 100644 --- a/docs/en_US/pg/catalog-pg-authid.html +++ b/docs/en_US/pg/catalog-pg-authid.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.8. pg_authid

-

The catalog pg_authid contains information about +

The catalog pg_authid contains information about database authorization identifiers (roles). A role subsumes the concepts of “users” and “groups”. A user is essentially just a role with the rolcanlogin flag set. Any role (with or @@ -36,7 +36,7 @@ one per database.

-

Table 43.8. pg_authid Columns

+

Table 43.8. pg_authid Columns

diff --git a/docs/en_US/pg/catalog-pg-autovacuum.html b/docs/en_US/pg/catalog-pg-autovacuum.html index 4228dfd332..344717f25f 100644 --- a/docs/en_US/pg/catalog-pg-autovacuum.html +++ b/docs/en_US/pg/catalog-pg-autovacuum.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.10. pg_autovacuum

-

The catalog pg_autovacuum stores optional +

The catalog pg_autovacuum stores optional per-relation configuration parameters for the autovacuum daemon. If there is an entry here for a particular relation, the given parameters will be used for autovacuuming that table. If no entry @@ -22,7 +22,7 @@ about the autovacuum daemon, see Section 22.1.4, “The auto-vacuum daemon”.

-

Table 43.10. pg_autovacuum Columns

+

Table 43.10. pg_autovacuum Columns

diff --git a/docs/en_US/pg/catalog-pg-cast.html b/docs/en_US/pg/catalog-pg-cast.html index b653ea6b92..eaf3716c76 100644 --- a/docs/en_US/pg/catalog-pg-cast.html +++ b/docs/en_US/pg/catalog-pg-cast.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

43.11. pg_cast

-

The catalog pg_cast stores data type conversion paths, +

The catalog pg_cast stores data type conversion paths, both built-in paths and those defined with CREATE CAST.

-

Table 43.11. pg_cast Columns

+

Table 43.11. pg_cast Columns

diff --git a/docs/en_US/pg/catalog-pg-class.html b/docs/en_US/pg/catalog-pg-class.html index a1095bca5d..f4c1ad1dce 100644 --- a/docs/en_US/pg/catalog-pg-class.html +++ b/docs/en_US/pg/catalog-pg-class.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.12. pg_class

-

The catalog pg_class catalogs tables and most +

The catalog pg_class catalogs tables and most everything else that has columns or is otherwise similar to a table. This includes indexes (but see also pg_index), sequences, views, composite types, @@ -24,7 +24,7 @@ columns are meaningful for all relation types.

-

Table 43.12. pg_class Columns

+

Table 43.12. pg_class Columns

diff --git a/docs/en_US/pg/catalog-pg-constraint.html b/docs/en_US/pg/catalog-pg-constraint.html index 75cc30cc5b..af0dffe450 100644 --- a/docs/en_US/pg/catalog-pg-constraint.html +++ b/docs/en_US/pg/catalog-pg-constraint.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.13. pg_constraint

-

The catalog pg_constraint stores check, primary key, unique, and foreign +

The catalog pg_constraint stores check, primary key, unique, and foreign key constraints on tables. (Column constraints are not treated specially. Every column constraint is equivalent to some table constraint.) Not-null constraints are represented in the @@ -23,7 +23,7 @@

Check constraints on domains are stored here, too.

-

Table 43.13. pg_constraint Columns

+

Table 43.13. pg_constraint Columns

diff --git a/docs/en_US/pg/catalog-pg-conversion.html b/docs/en_US/pg/catalog-pg-conversion.html index f7a503e4b7..4c31133335 100644 --- a/docs/en_US/pg/catalog-pg-conversion.html +++ b/docs/en_US/pg/catalog-pg-conversion.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.14. pg_conversion

-

The catalog pg_conversion describes the +

The catalog pg_conversion describes the available encoding conversion procedures. See CREATE CONVERSION for more information.

-

Table 43.14. pg_conversion Columns

+

Table 43.14. pg_conversion Columns

diff --git a/docs/en_US/pg/catalog-pg-database.html b/docs/en_US/pg/catalog-pg-database.html index 4a3f23db59..31af703caf 100644 --- a/docs/en_US/pg/catalog-pg-database.html +++ b/docs/en_US/pg/catalog-pg-database.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.15. pg_database

-

The catalog pg_database stores information about +

The catalog pg_database stores information about the available databases. Databases are created with the CREATE DATABASE command. Consult Chapter 19, Managing Databases for details about the meaning of some of the parameters. @@ -25,7 +25,7 @@ one per database.

-

Table 43.15. pg_database Columns

+

Table 43.15. pg_database Columns

diff --git a/docs/en_US/pg/catalog-pg-depend.html b/docs/en_US/pg/catalog-pg-depend.html index af1d28723a..72622601d1 100644 --- a/docs/en_US/pg/catalog-pg-depend.html +++ b/docs/en_US/pg/catalog-pg-depend.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.16. pg_depend

-

The catalog pg_depend records the dependency +

The catalog pg_depend records the dependency relationships between database objects. This information allows DROP commands to find which other objects must be dropped by DROP CASCADE or prevent dropping in the DROP @@ -25,7 +25,7 @@ that are shared across a database cluster.

-

Table 43.16. pg_depend Columns

+

Table 43.16. pg_depend Columns

diff --git a/docs/en_US/pg/catalog-pg-description.html b/docs/en_US/pg/catalog-pg-description.html index 1ff9cfc324..70e4807a3f 100644 --- a/docs/en_US/pg/catalog-pg-description.html +++ b/docs/en_US/pg/catalog-pg-description.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.17. pg_description

-

The catalog pg_description stores optional descriptions +

The catalog pg_description stores optional descriptions (comments) for each database object. Descriptions can be manipulated with the COMMENT command and viewed with psql's \d commands. @@ -26,7 +26,7 @@ are shared across a database cluster.

-

Table 43.17. pg_description Columns

+

Table 43.17. pg_description Columns

diff --git a/docs/en_US/pg/catalog-pg-index.html b/docs/en_US/pg/catalog-pg-index.html index 56dbf69c2d..b5e7429bcd 100644 --- a/docs/en_US/pg/catalog-pg-index.html +++ b/docs/en_US/pg/catalog-pg-index.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

43.18. pg_index

-

The catalog pg_index contains part of the information +

The catalog pg_index contains part of the information about indexes. The rest is mostly in pg_class.

-

Table 43.18. pg_index Columns

+

Table 43.18. pg_index Columns

diff --git a/docs/en_US/pg/catalog-pg-inherits.html b/docs/en_US/pg/catalog-pg-inherits.html index 5a3255799e..1d5221dad2 100644 --- a/docs/en_US/pg/catalog-pg-inherits.html +++ b/docs/en_US/pg/catalog-pg-inherits.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.19. pg_inherits

-

The catalog pg_inherits records information about +

The catalog pg_inherits records information about table inheritance hierarchies. There is one entry for each direct child table in the database. (Indirect inheritance can be determined by following chains of entries.)

-

Table 43.19. pg_inherits Columns

+

Table 43.19. pg_inherits Columns

diff --git a/docs/en_US/pg/catalog-pg-language.html b/docs/en_US/pg/catalog-pg-language.html index 90b4016bb1..93f624c0e4 100644 --- a/docs/en_US/pg/catalog-pg-language.html +++ b/docs/en_US/pg/catalog-pg-language.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.20. pg_language

-

The catalog pg_language registers +

The catalog pg_language registers languages in which you can write functions or stored procedures. See CREATE LANGUAGE and Chapter 36, Procedural Languages for more information about language handlers.

-

Table 43.20. pg_language Columns

+

Table 43.20. pg_language Columns

diff --git a/docs/en_US/pg/catalog-pg-largeobject.html b/docs/en_US/pg/catalog-pg-largeobject.html index 2ffbb83f51..98190e7a7d 100644 --- a/docs/en_US/pg/catalog-pg-largeobject.html +++ b/docs/en_US/pg/catalog-pg-largeobject.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.21. pg_largeobject

-

The catalog pg_largeobject holds the data making up +

The catalog pg_largeobject holds the data making up “large objects”. A large object is identified by an OID assigned when it is created. Each large object is broken into segments or “pages” small enough to be conveniently stored as rows @@ -23,7 +23,7 @@ BLCKSZ/4, or typically 2 kB).

-

Table 43.21. pg_largeobject Columns

+

Table 43.21. pg_largeobject Columns

diff --git a/docs/en_US/pg/catalog-pg-listener.html b/docs/en_US/pg/catalog-pg-listener.html index 93f6039933..a85a7db51a 100644 --- a/docs/en_US/pg/catalog-pg-listener.html +++ b/docs/en_US/pg/catalog-pg-listener.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.22. pg_listener

-

The catalog pg_listener supports the +

The catalog pg_listener supports the LISTEN and NOTIFY commands. A listener creates an entry in @@ -25,7 +25,7 @@ to awaken the listener from sleep.

-

Table 43.22. pg_listener Columns

+

Table 43.22. pg_listener Columns

diff --git a/docs/en_US/pg/catalog-pg-namespace.html b/docs/en_US/pg/catalog-pg-namespace.html index e8cc4ac1d5..57f0060703 100644 --- a/docs/en_US/pg/catalog-pg-namespace.html +++ b/docs/en_US/pg/catalog-pg-namespace.html @@ -5,7 +5,7 @@ - + @@ -14,13 +14,13 @@

43.23. pg_namespace

-

The catalog pg_namespace stores namespaces. +

The catalog pg_namespace stores namespaces. A namespace is the structure underlying SQL schemas: each namespace can have a separate collection of relations, types, etc. without name conflicts.

-

Table 43.23. pg_namespace Columns

+

Table 43.23. pg_namespace Columns

diff --git a/docs/en_US/pg/catalog-pg-opclass.html b/docs/en_US/pg/catalog-pg-opclass.html index af230c137e..d4f1fa8b10 100644 --- a/docs/en_US/pg/catalog-pg-opclass.html +++ b/docs/en_US/pg/catalog-pg-opclass.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.24. pg_opclass

-

The catalog pg_opclass defines +

The catalog pg_opclass defines index access method operator classes. Each operator class defines semantics for index columns of a particular data type and a particular index access method. Note that there can be multiple operator classes @@ -24,7 +24,7 @@

Operator classes are described at length in Section 33.14, “Interfacing Extensions To Indexes”.

-

Table 43.24. pg_opclass Columns

+

Table 43.24. pg_opclass Columns

diff --git a/docs/en_US/pg/catalog-pg-operator.html b/docs/en_US/pg/catalog-pg-operator.html index 901cfdd264..439057433f 100644 --- a/docs/en_US/pg/catalog-pg-operator.html +++ b/docs/en_US/pg/catalog-pg-operator.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

43.25. pg_operator

-

The catalog pg_operator stores information about operators. +

The catalog pg_operator stores information about operators. See CREATE OPERATOR and Section 33.12, “User-Defined Operators” for more information.

-

Table 43.25. pg_operator Columns

+

Table 43.25. pg_operator Columns

diff --git a/docs/en_US/pg/catalog-pg-pltemplate.html b/docs/en_US/pg/catalog-pg-pltemplate.html index 07f788542a..c967a61bac 100644 --- a/docs/en_US/pg/catalog-pg-pltemplate.html +++ b/docs/en_US/pg/catalog-pg-pltemplate.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.26. pg_pltemplate

-

The catalog pg_pltemplate stores +

The catalog pg_pltemplate stores “template” information for procedural languages. A template for a language allows the language to be created in a particular database by a simple CREATE LANGUAGE command, @@ -27,7 +27,7 @@ each database as it is needed.

-

Table 43.26. pg_pltemplate Columns

+

Table 43.26. pg_pltemplate Columns

diff --git a/docs/en_US/pg/catalog-pg-proc.html b/docs/en_US/pg/catalog-pg-proc.html index d9b91131d8..b703079cc6 100644 --- a/docs/en_US/pg/catalog-pg-proc.html +++ b/docs/en_US/pg/catalog-pg-proc.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.27. pg_proc

-

The catalog pg_proc stores information about functions (or procedures). +

The catalog pg_proc stores information about functions (or procedures). See CREATE FUNCTION and Section 33.3, “User-Defined Functions” for more information.

@@ -23,7 +23,7 @@ row in pg_aggregate.

-

Table 43.27. pg_proc Columns

+

Table 43.27. pg_proc Columns

diff --git a/docs/en_US/pg/catalog-pg-rewrite.html b/docs/en_US/pg/catalog-pg-rewrite.html index 25953a8cf7..85a9894fc8 100644 --- a/docs/en_US/pg/catalog-pg-rewrite.html +++ b/docs/en_US/pg/catalog-pg-rewrite.html @@ -5,7 +5,7 @@ - + @@ -14,10 +14,10 @@

43.28. pg_rewrite

-

The catalog pg_rewrite stores rewrite rules for tables and views. +

The catalog pg_rewrite stores rewrite rules for tables and views.

-

Table 43.28. pg_rewrite Columns

+

Table 43.28. pg_rewrite Columns

diff --git a/docs/en_US/pg/catalog-pg-shdepend.html b/docs/en_US/pg/catalog-pg-shdepend.html index 2548bdbf89..d03ef124cc 100644 --- a/docs/en_US/pg/catalog-pg-shdepend.html +++ b/docs/en_US/pg/catalog-pg-shdepend.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.29. pg_shdepend

-

The catalog pg_shdepend records the +

The catalog pg_shdepend records the dependency relationships between database objects and shared objects, such as roles. This information allows PostgreSQL to ensure that those objects are @@ -30,7 +30,7 @@ one per database.

-

Table 43.29. pg_shdepend Columns

+

Table 43.29. pg_shdepend Columns

diff --git a/docs/en_US/pg/catalog-pg-shdescription.html b/docs/en_US/pg/catalog-pg-shdescription.html index 32c612bc3a..2e351a1c08 100644 --- a/docs/en_US/pg/catalog-pg-shdescription.html +++ b/docs/en_US/pg/catalog-pg-shdescription.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.30. pg_shdescription

-

The catalog pg_shdescription stores optional +

The catalog pg_shdescription stores optional descriptions (comments) for shared database objects. Descriptions can be manipulated with the COMMENT command and viewed with psql's \d commands. @@ -29,7 +29,7 @@ one per database.

-

Table 43.30. pg_shdescription Columns

+

Table 43.30. pg_shdescription Columns

diff --git a/docs/en_US/pg/catalog-pg-statistic.html b/docs/en_US/pg/catalog-pg-statistic.html index 405b507950..69cf5b37d6 100644 --- a/docs/en_US/pg/catalog-pg-statistic.html +++ b/docs/en_US/pg/catalog-pg-statistic.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.31. pg_statistic

-

The catalog pg_statistic stores statistical data +

The catalog pg_statistic stores statistical data about the contents of the database. Entries are created by ANALYZE and subsequently used by the query planner. There is one entry for each table column that has been analyzed. @@ -48,7 +48,7 @@ about those tables that are readable by the current user.

-

Table 43.31. pg_statistic Columns

+

Table 43.31. pg_statistic Columns

diff --git a/docs/en_US/pg/catalog-pg-tablespace.html b/docs/en_US/pg/catalog-pg-tablespace.html index 30e692fdcc..95c666aac3 100644 --- a/docs/en_US/pg/catalog-pg-tablespace.html +++ b/docs/en_US/pg/catalog-pg-tablespace.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.32. pg_tablespace

-

The catalog pg_tablespace stores information +

The catalog pg_tablespace stores information about the available tablespaces. Tables can be placed in particular tablespaces to aid administration of disk layout.

@@ -24,7 +24,7 @@ one per database.

-

Table 43.32. pg_tablespace Columns

+

Table 43.32. pg_tablespace Columns

diff --git a/docs/en_US/pg/catalog-pg-trigger.html b/docs/en_US/pg/catalog-pg-trigger.html index adc6c06663..6858e9ee71 100644 --- a/docs/en_US/pg/catalog-pg-trigger.html +++ b/docs/en_US/pg/catalog-pg-trigger.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

43.33. pg_trigger

-

The catalog pg_trigger stores triggers on tables. +

The catalog pg_trigger stores triggers on tables. See CREATE TRIGGER for more information.

-

Table 43.33. pg_trigger Columns

+

Table 43.33. pg_trigger Columns

diff --git a/docs/en_US/pg/catalog-pg-type.html b/docs/en_US/pg/catalog-pg-type.html index 64123377c8..8984d2952d 100644 --- a/docs/en_US/pg/catalog-pg-type.html +++ b/docs/en_US/pg/catalog-pg-type.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

43.34. pg_type

-

The catalog pg_type stores information about data +

The catalog pg_type stores information about data types. Base types (scalar types) are created with CREATE TYPE, and domains with @@ -24,7 +24,7 @@ composite types with CREATE TYPE AS.

-

Table 43.34. pg_type Columns

+

Table 43.34. pg_type Columns

diff --git a/docs/en_US/pg/catalogs.html b/docs/en_US/pg/catalogs.html index dc80812b5f..f321949c00 100644 --- a/docs/en_US/pg/catalogs.html +++ b/docs/en_US/pg/catalogs.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/charset.html b/docs/en_US/pg/charset.html index de48afb9e4..9beabd304e 100644 --- a/docs/en_US/pg/charset.html +++ b/docs/en_US/pg/charset.html @@ -5,7 +5,7 @@ - + @@ -19,16 +19,16 @@
21.1. Locale Support
-
21.1.1. Overview
-
21.1.2. Behavior
-
21.1.3. Problems
+
21.1.1. Overview
+
21.1.2. Behavior
+
21.1.3. Problems
21.2. Character Set Support
21.2.1. Supported Character Sets
-
21.2.2. Setting the Character Set
-
21.2.3. Automatic Character Set Conversion Between Server and Client
-
21.2.4. Further Reading
+
21.2.2. Setting the Character Set
+
21.2.3. Automatic Character Set Conversion Between Server and Client
+
21.2.4. Further Reading
@@ -55,7 +55,7 @@

21.1. Locale Support

-

Locale support refers to an application respecting +

Locale support refers to an application respecting cultural preferences regarding alphabets, sorting, number formatting, etc. PostgreSQL uses the standard ISO C and POSIX locale facilities provided by the server operating @@ -64,7 +64,7 @@

-21.1.1. Overview

+21.1.1. Overview

Locale support is automatically initialized when a database cluster is created using initdb. initdb will initialize the database cluster @@ -191,24 +191,24 @@

Note

-21.1.2. Behavior

+21.1.2. Behavior

The locale settings influence the following SQL features:

  • Sort order in queries using ORDER BY on textual data - +

  • The ability to use indexes with LIKE clauses - +

  • The upper, lower, and initcap functions - - + +

  • The to_char family of functions - +

@@ -229,7 +229,7 @@

Note

-21.1.3. Problems

+21.1.3. Problems

If locale support doesn't work in spite of the explanation above, check that the locale support in your operating system is correctly configured. To check what locales are installed on your diff --git a/docs/en_US/pg/client-authentication-problems.html b/docs/en_US/pg/client-authentication-problems.html index dfea82adda..5de154f879 100644 --- a/docs/en_US/pg/client-authentication-problems.html +++ b/docs/en_US/pg/client-authentication-problems.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/client-authentication.html b/docs/en_US/pg/client-authentication.html index 2b9bd0025e..0b43d9b7ac 100644 --- a/docs/en_US/pg/client-authentication.html +++ b/docs/en_US/pg/client-authentication.html @@ -5,7 +5,7 @@ - + @@ -30,7 +30,7 @@

20.3. Authentication problems
-

When a client application connects to the database server, it +

When a client application connects to the database server, it specifies which PostgreSQL database user name it wants to connect as, much the same way one logs into a Unix computer as a particular user. Within the SQL environment the active database @@ -70,7 +70,7 @@

Note

20.1. The pg_hba.conf file

-

Client authentication is controlled by a configuration file, +

Client authentication is controlled by a configuration file, which traditionally is named pg_hba.conf and is stored in the database cluster's data directory. @@ -326,7 +326,7 @@

Note

The pg_hba.conf file is read on start-up and when the main server process receives a - SIGHUP + SIGHUP signal. If you edit the file on an active system, you will need to signal the server (using pg_ctl reload or kill -HUP) to make it diff --git a/docs/en_US/pg/client-interfaces.html b/docs/en_US/pg/client-interfaces.html index 221d897458..039349a44c 100644 --- a/docs/en_US/pg/client-interfaces.html +++ b/docs/en_US/pg/client-interfaces.html @@ -5,8 +5,8 @@ - - + + @@ -14,7 +14,7 @@

Part IV. Client Interfaces

-
+

This part describes the client programming interfaces distributed with PostgreSQL. Each of these chapters can be @@ -69,16 +69,16 @@

30.2. Implementation Features
30.3. Client Interfaces
-
30.3.1. Creating a Large Object
-
30.3.2. Importing a Large Object
-
30.3.3. Exporting a Large Object
-
30.3.4. Opening an Existing Large Object
-
30.3.5. Writing Data to a Large Object
-
30.3.6. Reading Data from a Large Object
-
30.3.7. Seeking in a Large Object
-
30.3.8. Obtaining the Seek Position of a Large Object
-
30.3.9. Closing a Large Object Descriptor
-
30.3.10. Removing a Large Object
+
30.3.1. Creating a Large Object
+
30.3.2. Importing a Large Object
+
30.3.3. Exporting a Large Object
+
30.3.4. Opening an Existing Large Object
+
30.3.5. Writing Data to a Large Object
+
30.3.6. Reading Data from a Large Object
+
30.3.7. Seeking in a Large Object
+
30.3.8. Obtaining the Seek Position of a Large Object
+
30.3.9. Closing a Large Object Descriptor
+
30.3.10. Removing a Large Object
30.4. Server-Side Functions
30.5. Example Program
@@ -92,41 +92,41 @@
31.5. Choosing a Connection
31.6. Using Host Variables
-
31.6.1. Overview
-
31.6.2. Declare Sections
-
31.6.3. Different types of host variables
-
31.6.4. SELECT INTO and FETCH INTO
-
31.6.5. Indicators
+
31.6.1. Overview
+
31.6.2. Declare Sections
+
31.6.3. Different types of host variables
+
31.6.4. SELECT INTO and FETCH INTO
+
31.6.5. Indicators
31.7. Dynamic SQL
31.8. pgtypes library
-
31.8.1. The numeric type
-
31.8.2. The date type
-
31.8.3. The timestamp type
-
31.8.4. The interval type
-
31.8.5. The decimal type
-
31.8.6. errno values of pgtypeslib
-
31.8.7. Special constants of pgtypeslib
+
31.8.1. The numeric type
+
31.8.2. The date type
+
31.8.3. The timestamp type
+
31.8.4. The interval type
+
31.8.5. The decimal type
+
31.8.6. errno values of pgtypeslib
+
31.8.7. Special constants of pgtypeslib
31.9. Informix compatibility mode
-
31.9.1. Additional embedded SQL statements
-
31.9.2. Additional functions
-
31.9.3. Additional constants
+
31.9.1. Additional embedded SQL statements
+
31.9.2. Additional functions
+
31.9.3. Additional constants
31.10. Using SQL Descriptor Areas
31.11. Error Handling
-
31.11.1. Setting Callbacks
-
31.11.2. sqlca
-
31.11.3. SQLSTATE vs SQLCODE
+
31.11.1. Setting Callbacks
+
31.11.2. sqlca
+
31.11.3. SQLSTATE vs SQLCODE
31.12. Preprocessor directives
-
31.12.1. Including files
-
31.12.2. The #define and #undef directives
-
31.12.3. ifdef, ifndef, else, elif and endif directives
+
31.12.1. Including files
+
31.12.2. The #define and #undef directives
+
31.12.3. ifdef, ifndef, else, elif and endif directives
31.13. Processing Embedded SQL Programs
31.14. Library Functions
diff --git a/docs/en_US/pg/connect-estab.html b/docs/en_US/pg/connect-estab.html index 457b874485..af655cd66f 100644 --- a/docs/en_US/pg/connect-estab.html +++ b/docs/en_US/pg/connect-estab.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/continuous-archiving.html b/docs/en_US/pg/continuous-archiving.html index 7c9883659f..73b2e22471 100644 --- a/docs/en_US/pg/continuous-archiving.html +++ b/docs/en_US/pg/continuous-archiving.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

23.3. Continuous Archiving and Point-In-Time Recovery (PITR)

-

At all times, PostgreSQL maintains a +

At all times, PostgreSQL maintains a write ahead log (WAL) in the pg_xlog/ subdirectory of the cluster's data directory. The log describes every change made to the database's data files. This log exists @@ -580,7 +580,7 @@

Note

23.3.4. Timelines

-

The ability to restore the database to a previous point in time creates +

The ability to restore the database to a previous point in time creates some complexities that are akin to science-fiction stories about time travel and parallel universes. In the original history of the database, perhaps you dropped a critical table at 5:15PM on Tuesday evening. diff --git a/docs/en_US/pg/creating-cluster.html b/docs/en_US/pg/creating-cluster.html index 71d6deba6b..9723d9625c 100644 --- a/docs/en_US/pg/creating-cluster.html +++ b/docs/en_US/pg/creating-cluster.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

16.2. Creating a Database Cluster

-

Before you can do anything, you must initialize a database storage +

Before you can do anything, you must initialize a database storage area on disk. We call this a database cluster. (SQL uses the term catalog cluster.) A database cluster is a collection of databases that is managed by a @@ -37,7 +37,7 @@ default, although locations such as /usr/local/pgsql/data or /var/lib/pgsql/data are popular. To initialize a - database cluster, use the command initdb, which is + database cluster, use the command initdb, which is installed with PostgreSQL. The desired file system location of your database cluster is indicated by the -D option, for example @@ -52,7 +52,7 @@

Tip

As an alternative to the -D option, you can set the environment variable PGDATA. - +

initdb will attempt to create the directory you @@ -83,7 +83,7 @@

Tip

trust other local users, we recommend you use one of initdb's -W, --pwprompt or --pwfile options to assign a password to the - database superuser. Also, specify -A md5 or + database superuser. Also, specify -A md5 or -A password so that the default trust authentication mode is not used; or modify the generated pg_hba.conf file after running initdb, @@ -92,7 +92,7 @@

Tip

or file system permissions to restrict connections. See Chapter 20, Client Authentication for more information.)

initdb also initializes the default - locale for the database cluster. + locale for the database cluster. Normally, it will just take the locale settings in the environment and apply them to the initialized database. It is possible to specify a different locale for the database; more information about diff --git a/docs/en_US/pg/cvs-tree.html b/docs/en_US/pg/cvs-tree.html index 792fa46ad6..fbd3ef2758 100644 --- a/docs/en_US/pg/cvs-tree.html +++ b/docs/en_US/pg/cvs-tree.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/cvs.html b/docs/en_US/pg/cvs.html index 153756dc69..dd7550e811 100644 --- a/docs/en_US/pg/cvs.html +++ b/docs/en_US/pg/cvs.html @@ -5,9 +5,9 @@ - + - + @@ -34,8 +34,8 @@

F.2. CVS Tree Organization
F.3. Getting The Source Via CVSup
-
F.3.1. Preparing A CVSup Client System
-
F.3.2. Running a CVSup Client
+
F.3.1. Preparing A CVSup Client System
+
F.3.2. Running a CVSup Client
@@ -56,7 +56,7 @@ retrieve updates from time to time.

-

Anonymous CVS

+

Anonymous CVS

  1. You will need a local copy of CVS (Concurrent Version Control System), which you can get from diff --git a/docs/en_US/pg/cvsup.html b/docs/en_US/pg/cvsup.html index 992eb56e8a..31623c9c30 100644 --- a/docs/en_US/pg/cvsup.html +++ b/docs/en_US/pg/cvsup.html @@ -5,7 +5,7 @@ - + @@ -32,7 +32,7 @@

    -F.3.1. Preparing A CVSup Client System

    +F.3.1. Preparing A CVSup Client System

Two directory areas are required for CVSup to do its job: a local CVS repository (or simply a directory area if you are fetching a snapshot rather @@ -76,7 +76,7 @@

-F.3.2. Running a CVSup Client

+F.3.2. Running a CVSup Client

Verify that cvsup is in your path; on most systems you can do this by typing diff --git a/docs/en_US/pg/datatype-binary.html b/docs/en_US/pg/datatype-binary.html index b1e94fead9..416d7721f3 100644 --- a/docs/en_US/pg/datatype-binary.html +++ b/docs/en_US/pg/datatype-binary.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.4. Binary Data Types

-

The bytea data type allows storage of binary strings; +

The bytea data type allows storage of binary strings; see Table 8.6, “Binary Data Types”.

diff --git a/docs/en_US/pg/datatype-bit.html b/docs/en_US/pg/datatype-bit.html index 4b1b362c5b..e9b92b982d 100644 --- a/docs/en_US/pg/datatype-bit.html +++ b/docs/en_US/pg/datatype-bit.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.9. Bit String Types

-

Bit strings are strings of 1's and 0's. They can be used to store +

Bit strings are strings of 1's and 0's. They can be used to store or visualize bit masks. There are two SQL bit types: bit(n) and bit varying(n), where @@ -45,7 +45,7 @@

Note

manipulation functions are available; see Section 9.6, “Bit String Functions and Operators”.

-

Example 8.3. Using the bit string types

+

Example 8.3. Using the bit string types

CREATE TABLE test (a BIT(3), b BIT VARYING(5));
 INSERT INTO test VALUES (B'101', B'00');
 INSERT INTO test VALUES (B'10', B'101');
diff --git a/docs/en_US/pg/datatype-boolean.html b/docs/en_US/pg/datatype-boolean.html
index 3f98b0c656..5343deb422 100644
--- a/docs/en_US/pg/datatype-boolean.html
+++ b/docs/en_US/pg/datatype-boolean.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 8.6. Boolean Type

-
    PostgreSQL provides the
+
    PostgreSQL provides the
     standard SQL type boolean.
     boolean can have one of only two states:
     “true” or “false”.  A third state,
diff --git a/docs/en_US/pg/datatype-character.html b/docs/en_US/pg/datatype-character.html
index 424ea609c5..5d3a38e4c8 100644
--- a/docs/en_US/pg/datatype-character.html
+++ b/docs/en_US/pg/datatype-character.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 8.3. Character Types

-

+

 
Table 8.4. Character Types
@@ -130,7 +130,7 @@

Tip

refer to Section 21.2, “Character Set Support”.

-

Example 8.1. Using the character types

+

Example 8.1. Using the character types

CREATE TABLE test1 (a character(4));
 INSERT INTO test1 VALUES ('ok');
diff --git a/docs/en_US/pg/datatype-datetime.html b/docs/en_US/pg/datatype-datetime.html
index d99cbd7311..c229058022 100644
--- a/docs/en_US/pg/datatype-datetime.html
+++ b/docs/en_US/pg/datatype-datetime.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 8.5. Date/Time Types

-
    PostgreSQL supports the full set of
+
    PostgreSQL supports the full set of
     SQL date and time types, shown in Table 8.9, “Date/Time Types”.  The operations available
     on these data types are described in
     Section 9.9, “Date/Time Functions and Operators”.
@@ -181,8 +181,8 @@ 
Note

     

 

 

-8.5.1.1. Dates

-
     Table 8.10, “Date Input” shows some possible
+8.5.1.1. Dates
+

Table 8.10, “Date Input” shows some possible inputs for the date type.

@@ -274,8 +274,8 @@

Note

-8.5.1.2. Times

-

The time-of-day types are time [ +8.5.1.2. Times

+

The time-of-day types are time [ (p) ] without time zone and time [ (p) ] with time zone. Writing just time is equivalent to @@ -410,8 +410,8 @@

Note

-8.5.1.3. Time Stamps

-

Valid input for the time stamp types consists of a concatenation +8.5.1.3. Time Stamps

+

Valid input for the time stamp types consists of a concatenation of a date and a time, followed by an optional time zone, followed by an optional AD or BC. (Alternatively, AD/BC can appear @@ -484,8 +484,8 @@

Note

-8.5.1.4. Intervals

-

interval values can be written with the following syntax: +8.5.1.4. Intervals

+

interval values can be written with the following syntax: 

[@] quantity unit [quantity unit...] [direction]
@@ -522,8 +522,8 @@

Note

-8.5.1.5. Special Values

-

PostgreSQL supports several +8.5.1.5. Special Values

+

PostgreSQL supports several special date/time input values for convenience, as shown in Table 8.13, “Special Date/Time Inputs”. The values infinity and -infinity are specially represented inside the system and will be displayed @@ -614,7 +614,7 @@

Note

8.5.2. Date/Time Output

-

The output format of the date/time types can be set to one of the four +

The output format of the date/time types can be set to one of the four styles ISO 8601, SQL (Ingres), traditional POSTGRES, and German, using the command SET datestyle. The default @@ -732,7 +732,7 @@

Note

8.5.3. Time Zones

-

Time zones, and time-zone conventions, are influenced by +

Time zones, and time-zone conventions, are influenced by political decisions, not just earth geometry. Time zones around the world became somewhat standardized during the 1900's, but continue to be prone to arbitrary changes, particularly with diff --git a/docs/en_US/pg/datatype-geometric.html b/docs/en_US/pg/datatype-geometric.html index c5f6cddbb8..ab64476bd5 100644 --- a/docs/en_US/pg/datatype-geometric.html +++ b/docs/en_US/pg/datatype-geometric.html @@ -5,7 +5,7 @@ - + @@ -93,8 +93,8 @@

-8.7.1. Points

-

Points are the fundamental two-dimensional building block for geometric types. +8.7.1. Points

+

Points are the fundamental two-dimensional building block for geometric types. Values of type point are specified using the following syntax:

@@ -108,8 +108,8 @@

-8.7.2. Line Segments

-

Line segments (lseg) are represented by pairs of points. +8.7.2. Line Segments

+

Line segments (lseg) are represented by pairs of points. Values of type lseg are specified using the following syntax:

@@ -127,8 +127,8 @@

-8.7.3. Boxes

-

Boxes are represented by pairs of points that are opposite +8.7.3. Boxes

+

Boxes are represented by pairs of points that are opposite corners of the box. Values of type box are specified using the following syntax: @@ -153,8 +153,8 @@

-8.7.4. Paths

-

Paths are represented by lists of connected points. Paths can be +8.7.4. Paths

+

Paths are represented by lists of connected points. Paths can be open, where the first and last points in the list are not considered connected, or closed, @@ -180,8 +180,8 @@

-8.7.5. Polygons

-

Polygons are represented by lists of points (the vertexes of the +8.7.5. Polygons

+

Polygons are represented by lists of points (the vertexes of the polygon). Polygons should probably be considered equivalent to closed paths, but are stored differently and have their own set of support routines. @@ -203,8 +203,8 @@

-8.7.6. Circles

-

Circles are represented by a center point and a radius. +8.7.6. Circles

+

Circles are represented by a center point and a radius. Values of type circle are specified using the following syntax:

diff --git a/docs/en_US/pg/datatype-money.html b/docs/en_US/pg/datatype-money.html index a59bd51c6a..58aa27ecd1 100644 --- a/docs/en_US/pg/datatype-money.html +++ b/docs/en_US/pg/datatype-money.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/datatype-net-types.html b/docs/en_US/pg/datatype-net-types.html index a6fb259803..72e57a26d4 100644 --- a/docs/en_US/pg/datatype-net-types.html +++ b/docs/en_US/pg/datatype-net-types.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.8. Network Address Types

-

PostgreSQL offers data types to store IPv4, IPv6, and MAC +

PostgreSQL offers data types to store IPv4, IPv6, and MAC addresses, as shown in Table 8.17, “Network Address Types”. It is preferable to use these types instead of plain text types to store network addresses, because @@ -61,7 +61,7 @@

8.8.1. inet

-

The inet type holds an IPv4 or IPv6 host address, and +

The inet type holds an IPv4 or IPv6 host address, and optionally the identity of the subnet it is in, all in one field. The subnet identity is represented by stating how many bits of the host address represent the network address (the @@ -90,7 +90,7 @@

8.8.2. cidr

-

The cidr type holds an IPv4 or IPv6 network specification. +

The cidr type holds an IPv4 or IPv6 network specification. Input and output formats follow Classless Internet Domain Routing conventions. The format for specifying networks is address/y where address is the network represented as an @@ -222,7 +222,7 @@

Tip

8.8.4. macaddr

-

The macaddr type stores MAC addresses, i.e., Ethernet +

The macaddr type stores MAC addresses, i.e., Ethernet card hardware addresses (although MAC addresses are used for other purposes as well). Input is accepted in various customary formats, including diff --git a/docs/en_US/pg/datatype-oid.html b/docs/en_US/pg/datatype-oid.html index e39d630831..f907314b0d 100644 --- a/docs/en_US/pg/datatype-oid.html +++ b/docs/en_US/pg/datatype-oid.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.12. Object Identifier Types

-

Object identifiers (OIDs) are used internally by +

Object identifiers (OIDs) are used internally by PostgreSQL as primary keys for various system tables. OIDs are not added to user-created tables, unless WITH OIDS is specified when the table is diff --git a/docs/en_US/pg/datatype-pseudo.html b/docs/en_US/pg/datatype-pseudo.html index 4025116fcb..e2b6cdfe4d 100644 --- a/docs/en_US/pg/datatype-pseudo.html +++ b/docs/en_US/pg/datatype-pseudo.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.13. Pseudo-Types

-

The PostgreSQL type system contains a +

The PostgreSQL type system contains a number of special-purpose entries that are collectively called pseudo-types. A pseudo-type cannot be used as a column data type, but it can be used to declare a function's diff --git a/docs/en_US/pg/datatype-xml.html b/docs/en_US/pg/datatype-xml.html index ebfec98282..c054e13c38 100644 --- a/docs/en_US/pg/datatype-xml.html +++ b/docs/en_US/pg/datatype-xml.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

8.14. XML Document Support

-

XML (Extensible Markup Language) support is not one +

XML (Extensible Markup Language) support is not one capability, but a variety of features supported by a database system. These capabilities include storage, import/export, validation, indexing, efficiency of modification, searching, diff --git a/docs/en_US/pg/datatype.html b/docs/en_US/pg/datatype.html index c1bf0a5d2c..63c3c69cee 100644 --- a/docs/en_US/pg/datatype.html +++ b/docs/en_US/pg/datatype.html @@ -5,7 +5,7 @@ - + @@ -37,12 +37,12 @@

8.6. Boolean Type
8.7. Geometric Types
-
8.7.1. Points
-
8.7.2. Line Segments
-
8.7.3. Boxes
-
8.7.4. Paths
-
8.7.5. Polygons
-
8.7.6. Circles
+
8.7.1. Points
+
8.7.2. Line Segments
+
8.7.3. Boxes
+
8.7.4. Paths
+
8.7.5. Polygons
+
8.7.6. Circles
8.8. Network Address Types
@@ -54,27 +54,27 @@
8.9. Bit String Types
8.10. Arrays
-
8.10.1. Declaration of Array Types
-
8.10.2. Array Value Input
-
8.10.3. Accessing Arrays
-
8.10.4. Modifying Arrays
-
8.10.5. Searching in Arrays
-
8.10.6. Array Input and Output Syntax
+
8.10.1. Declaration of Array Types
+
8.10.2. Array Value Input
+
8.10.3. Accessing Arrays
+
8.10.4. Modifying Arrays
+
8.10.5. Searching in Arrays
+
8.10.6. Array Input and Output Syntax
8.11. Composite Types
-
8.11.1. Declaration of Composite Types
-
8.11.2. Composite Value Input
-
8.11.3. Accessing Composite Types
-
8.11.4. Modifying Composite Types
-
8.11.5. Composite Type Input and Output Syntax
+
8.11.1. Declaration of Composite Types
+
8.11.2. Composite Value Input
+
8.11.3. Accessing Composite Types
+
8.11.4. Modifying Composite Types
+
8.11.5. Composite Type Input and Output Syntax
8.12. Object Identifier Types
8.13. Pseudo-Types
8.14. XML Document Support
-

PostgreSQL has a rich set of native data +

PostgreSQL has a rich set of native data types available to users. Users may add new types to PostgreSQL using the CREATE TYPE command.

@@ -292,7 +292,7 @@

Compatibility

8.1. Numeric Types

-

Numeric types consist of two-, four-, and eight-byte integers, +

Numeric types consist of two-, four-, and eight-byte integers, four- and eight-byte floating-point numbers, and selectable-precision decimals. Table 8.2, “Numeric Types” lists the available types. @@ -379,7 +379,7 @@

Compatibility

8.1.1. Integer Types

-

The types smallint, integer, and +

The types smallint, integer, and bigint store whole numbers, that is, numbers without fractional components, of various ranges. Attempts to store values outside of the allowed range will result in an error. @@ -409,7 +409,7 @@

Compatibility

8.1.2. Arbitrary Precision Numbers

-

The type numeric can store numbers with up to 1000 +

The type numeric can store numbers with up to 1000 digits of precision and perform calculations exactly. It is especially recommended for storing monetary amounts and other quantities where exactness is required. However, arithmetic on @@ -483,7 +483,7 @@

Compatibility

8.1.3. Floating-Point Types

-

The data types real and double +

The data types real and double precision are inexact, variable-precision numeric types. In practice, these types are usually implementations of IEEE Standard 754 for Binary Floating-Point @@ -571,7 +571,7 @@

Note

8.1.4. Serial Types

-

The data types serial and bigserial +

The data types serial and bigserial are not true types, but merely a notational convenience for setting up unique identifier columns (similar to the AUTO_INCREMENT property diff --git a/docs/en_US/pg/datetime-appendix.html b/docs/en_US/pg/datetime-appendix.html index 5c212b07d9..cb9c5eddef 100644 --- a/docs/en_US/pg/datetime-appendix.html +++ b/docs/en_US/pg/datetime-appendix.html @@ -5,7 +5,7 @@ - + @@ -17,7 +17,7 @@

Table of Contents

-
B.1. Date/Time Input Interpretation
+
B.1. Date/Time Input Interpretation
B.2. Date/Time Key Words
B.3. Date/Time Configuration Files
B.4. History of Units
@@ -38,7 +38,7 @@

-B.1. Date/Time Input Interpretation

+B.1. Date/Time Input Interpretation

The date/time type inputs are all decoded using the following procedure.

    diff --git a/docs/en_US/pg/datetime-config-files.html b/docs/en_US/pg/datetime-config-files.html index 49bb2ab30e..7967ea4c35 100644 --- a/docs/en_US/pg/datetime-config-files.html +++ b/docs/en_US/pg/datetime-config-files.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

    B.3. Date/Time Configuration Files

    -

    Since timezone abbreviations are not well standardized, +

    Since timezone abbreviations are not well standardized, PostgreSQL provides a means to customize the set of abbreviations accepted by the server. The timezone_abbreviations run-time parameter diff --git a/docs/en_US/pg/datetime-keywords.html b/docs/en_US/pg/datetime-keywords.html index 967e924c50..852949650f 100644 --- a/docs/en_US/pg/datetime-keywords.html +++ b/docs/en_US/pg/datetime-keywords.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/datetime-units-history.html b/docs/en_US/pg/datetime-units-history.html index a25eae49db..d2934c3f89 100644 --- a/docs/en_US/pg/datetime-units-history.html +++ b/docs/en_US/pg/datetime-units-history.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ddl-alter.html b/docs/en_US/pg/ddl-alter.html index 96df1bbfb7..ba2e356848 100644 --- a/docs/en_US/pg/ddl-alter.html +++ b/docs/en_US/pg/ddl-alter.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

    5.5. Modifying Tables

    -

    When you create a table and you realize that you made a mistake, or +

    When you create a table and you realize that you made a mistake, or the requirements of the application change, then you can drop the table and create it again. But this is not a convenient option if the table is already filled with data, or if the table is @@ -45,8 +45,8 @@

    -5.5.1. Adding a Column

    -

    To add a column, use a command like this: +5.5.1. Adding a Column

    +

    To add a column, use a command like this: 

    ALTER TABLE products ADD COLUMN description text;

    @@ -79,8 +79,8 @@

    Tip

-5.5.2. Removing a Column

-

To remove a column, use a command like this: +5.5.2. Removing a Column

+

To remove a column, use a command like this: 

ALTER TABLE products DROP COLUMN description;

@@ -99,8 +99,8 @@

Tip

-5.5.3. Adding a Constraint

-

To add a constraint, the table constraint syntax is used. For example: +5.5.3. Adding a Constraint

+

To add a constraint, the table constraint syntax is used. For example: 

ALTER TABLE products ADD CHECK (name <> '');
 ALTER TABLE products ADD CONSTRAINT some_name UNIQUE (product_no);
@@ -118,8 +118,8 @@ 
Tip

-5.5.4. Removing a Constraint

-

To remove a constraint you need to know its name. If you gave it +5.5.4. Removing a Constraint

+

To remove a constraint you need to know its name. If you gave it a name then that's easy. Otherwise the system assigned a generated name, which you need to find out. The psql command \d @@ -148,8 +148,8 @@

Tip

-5.5.5. Changing a Column's Default Value

-

To set a new default for a column, use a command like this: +5.5.5. Changing a Column's Default Value

+

To set a new default for a column, use a command like this: 

ALTER TABLE products ALTER COLUMN price SET DEFAULT 7.77;

@@ -168,8 +168,8 @@

Tip

-5.5.6. Changing a Column's Data Type

-

To convert a column to a different data type, use a command like this: +5.5.6. Changing a Column's Data Type

+

To convert a column to a different data type, use a command like this: 

ALTER TABLE products ALTER COLUMN price TYPE numeric(10,2);

@@ -188,8 +188,8 @@

Tip

-5.5.7. Renaming a Column

-

To rename a column: +5.5.7. Renaming a Column

+

To rename a column: 

ALTER TABLE products RENAME COLUMN product_no TO product_number;

@@ -197,8 +197,8 @@

Tip

-5.5.8. Renaming a Table

-

To rename a table: +5.5.8. Renaming a Table

+

To rename a table: 

ALTER TABLE products RENAME TO items;

diff --git a/docs/en_US/pg/ddl-constraints.html b/docs/en_US/pg/ddl-constraints.html index aa55453687..7f032480a3 100644 --- a/docs/en_US/pg/ddl-constraints.html +++ b/docs/en_US/pg/ddl-constraints.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.3. Constraints

-

Data types are a way to limit the kind of data that can be stored +

Data types are a way to limit the kind of data that can be stored in a table. For many applications, however, the constraint they provide is too coarse. For example, a column containing a product price should probably only accept positive values. But there is no @@ -31,8 +31,8 @@

-5.3.1. Check Constraints

-

A check constraint is the most generic constraint type. It allows +5.3.1. Check Constraints

+

A check constraint is the most generic constraint type. It allows you to specify that the value in a certain column must satisfy a Boolean (truth-value) expression. For instance, to require positive product prices, you could use: @@ -52,7 +52,7 @@ involve the column thus constrained, otherwise the constraint would not make too much sense.

-

You can also give the constraint a separate name. This clarifies +

You can also give the constraint a separate name. This clarifies error messages and allows you to refer to the constraint when you need to change it. The syntax is:

@@ -132,7 +132,7 @@ );

-

It should be noted that a check constraint is satisfied if the +

It should be noted that a check constraint is satisfied if the check expression evaluates to true or the null value. Since most expressions will evaluate to the null value if any operand is null, they will not prevent null values in the constrained columns. To @@ -142,8 +142,8 @@

-5.3.2. Not-Null Constraints

-

A not-null constraint simply specifies that a column must not +5.3.2. Not-Null Constraints

+

A not-null constraint simply specifies that a column must not assume the null value. A syntax example: 

CREATE TABLE products (
@@ -202,8 +202,8 @@ 
Tip

 
 

 

-5.3.3. Unique Constraints

-
    Unique constraints ensure that the data contained in a column or a
+5.3.3. Unique Constraints

+
    Unique constraints ensure that the data contained in a column or a
     group of columns is unique with respect to all the rows in the
     table.  The syntax is
 

@@ -247,7 +247,7 @@ 
Tip

 );

-

In general, a unique constraint is violated when there are two or +

In general, a unique constraint is violated when there are two or more rows in the table where the values of all of the columns included in the constraint are equal. However, two null values are not considered equal in this @@ -262,8 +262,8 @@

Tip

-5.3.4. Primary Keys

-

Technically, a primary key constraint is simply a combination of a +5.3.4. Primary Keys

+

Technically, a primary key constraint is simply a combination of a unique constraint and a not-null constraint. So, the following two table definitions accept the same data:

@@ -315,7 +315,7 @@

Tip

5.3.5. Foreign Keys

-

A foreign key constraint specifies that the values in a column (or +

A foreign key constraint specifies that the values in a column (or a group of columns) must match the values appearing in some row of another table. We say this maintains the referential @@ -406,7 +406,7 @@

Tip

Notice that the primary key overlaps with the foreign keys in the last table.

-

We know that the foreign keys disallow creation of orders that +

We know that the foreign keys disallow creation of orders that do not relate to any products. But what if a product is removed after an order is created that references it? SQL allows you to handle that as well. Intuitively, we have a few options: diff --git a/docs/en_US/pg/ddl-default.html b/docs/en_US/pg/ddl-default.html index 9ba0857a8e..434c8693f4 100644 --- a/docs/en_US/pg/ddl-default.html +++ b/docs/en_US/pg/ddl-default.html @@ -5,7 +5,7 @@ - + @@ -14,14 +14,14 @@

5.2. Default Values

-

A column can be assigned a default value. When a new row is +

A column can be assigned a default value. When a new row is created and no values are specified for some of the columns, those columns will be filled with their respective default values. A data manipulation command can also request explicitly that a column be set to its default value, without having to know what that value is. (Details about data manipulation commands are in Chapter 6, Data Manipulation.)

-

+

If no default value is declared explicitly, the default value is the null value. This usually makes sense because a null value can be considered to represent unknown data. diff --git a/docs/en_US/pg/ddl-depend.html b/docs/en_US/pg/ddl-depend.html index 9d0a9e0a6f..3e73d780e3 100644 --- a/docs/en_US/pg/ddl-depend.html +++ b/docs/en_US/pg/ddl-depend.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.11. Dependency Tracking

-

When you create complex database structures involving many tables +

When you create complex database structures involving many tables with foreign key constraints, views, triggers, functions, etc. you will implicitly create a net of dependencies between the objects. For instance, a table with a foreign key constraint depends on the diff --git a/docs/en_US/pg/ddl-inherit.html b/docs/en_US/pg/ddl-inherit.html index 5355667b79..7069fdea4e 100644 --- a/docs/en_US/pg/ddl-inherit.html +++ b/docs/en_US/pg/ddl-inherit.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.8. Inheritance

-

PostgreSQL implements table inheritance, +

PostgreSQL implements table inheritance, which can be a useful tool for database designers. (SQL:1999 and later define a type inheritance feature, which differs in many respects from the features described here.) diff --git a/docs/en_US/pg/ddl-others.html b/docs/en_US/pg/ddl-others.html index 4d68a5aa16..1a1d4ba07c 100644 --- a/docs/en_US/pg/ddl-others.html +++ b/docs/en_US/pg/ddl-others.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ddl-partitioning.html b/docs/en_US/pg/ddl-partitioning.html index 579caed4b3..0a8b6fbf93 100644 --- a/docs/en_US/pg/ddl-partitioning.html +++ b/docs/en_US/pg/ddl-partitioning.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.9. Partitioning

-

PostgreSQL supports basic table +

PostgreSQL supports basic table partitioning. This section describes why and how to implement partitioning as part of your database design.

@@ -382,7 +382,7 @@

5.9.4. Partitioning and Constraint Exclusion

-

Constraint exclusion is a query optimization technique +

Constraint exclusion is a query optimization technique that improves performance for partitioned tables defined in the fashion described above. As an example: diff --git a/docs/en_US/pg/ddl-priv.html b/docs/en_US/pg/ddl-priv.html index 99f825df7e..ee03b62898 100644 --- a/docs/en_US/pg/ddl-priv.html +++ b/docs/en_US/pg/ddl-priv.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.6. Privileges

-

When you create a database object, you become its owner. By +

When you create a database object, you become its owner. By default, only the owner of an object can do anything with the object. In order to allow other users to use it, privileges must be granted. (However, diff --git a/docs/en_US/pg/ddl-schemas.html b/docs/en_US/pg/ddl-schemas.html index 942e84d15b..b634264ede 100644 --- a/docs/en_US/pg/ddl-schemas.html +++ b/docs/en_US/pg/ddl-schemas.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

5.7. Schemas

-

A PostgreSQL database cluster +

A PostgreSQL database cluster contains one or more named databases. Users and groups of users are shared across the entire cluster, but no other data is shared across databases. Any given client connection to the server can access @@ -62,13 +62,13 @@

Note

5.7.1. Creating a Schema

-

To create a schema, use the CREATE SCHEMA command. Give the schema a name +

To create a schema, use the CREATE SCHEMA command. Give the schema a name of your choice. For example: 

CREATE SCHEMA myschema;

-

To create or access objects in a schema, write a +

To create or access objects in a schema, write a qualified name consisting of the schema name and table name separated by a dot:

@@ -95,7 +95,7 @@

Note

);

-

To drop a schema if it's empty (all objects in it have been +

To drop a schema if it's empty (all objects in it have been dropped), use 

DROP SCHEMA myschema;
@@ -123,7 +123,7 @@

Note

5.7.2. The Public Schema

-

In the previous sections we created tables without specifying any +

In the previous sections we created tables without specifying any schema names. By default, such tables (and other objects) are automatically put into a schema named “public”. Every new database contains such a schema. Thus, the following are equivalent: @@ -139,7 +139,7 @@

Note

5.7.3. The Schema Search Path

-

Qualified names are tedious to write, and it's often best not to +

Qualified names are tedious to write, and it's often best not to wire a particular schema name into applications anyway. Therefore tables are often referred to by unqualified names, which consist of just the table name. The system determines which table @@ -149,12 +149,12 @@

Note

path, an error is reported, even if matching table names exist in other schemas in the database.

-

The first schema named in the search path is called the current schema. +

The first schema named in the search path is called the current schema. Aside from being the first schema searched, it is also the schema in which new tables will be created if the CREATE TABLE command does not specify a schema name.

-

To show the current search path, use the following command: +

To show the current search path, use the following command: 

SHOW search_path;

@@ -221,7 +221,7 @@

Note

5.7.4. Schemas and Privileges

-

By default, users cannot access any objects in schemas they do not +

By default, users cannot access any objects in schemas they do not own. To allow that, the owner of the schema needs to grant the USAGE privilege on the schema. To allow users to make use of the objects in the schema, additional privileges @@ -249,7 +249,7 @@

Note

5.7.5. The System Catalog Schema

-

In addition to public and user-created schemas, each +

In addition to public and user-created schemas, each database contains a pg_catalog schema, which contains the system tables and all the built-in data types, functions, and operators. pg_catalog is always effectively part of diff --git a/docs/en_US/pg/ddl-system-columns.html b/docs/en_US/pg/ddl-system-columns.html index ff99581948..6df9bbe318 100644 --- a/docs/en_US/pg/ddl-system-columns.html +++ b/docs/en_US/pg/ddl-system-columns.html @@ -5,7 +5,7 @@ - + @@ -22,9 +22,9 @@ restrictions.) You do not really need to be concerned about these columns, just know they exist.

-
+
oid
-

+

The object identifier (object ID) of a row. This column is only present if the table was created using WITH OIDS, or if the default_with_oids @@ -33,7 +33,7 @@

tableoid
-

The OID of the table containing this row. This column is +

The OID of the table containing this row. This column is particularly handy for queries that select from inheritance hierarchies (see Section 5.8, “Inheritance”), since without it, it's difficult to tell which individual table a row came from. The @@ -44,7 +44,7 @@

xmin
-

The identity (transaction ID) of the inserting transaction for +

The identity (transaction ID) of the inserting transaction for this row version. (A row version is an individual state of a row; each update of a row creates a new row version for the same logical row.) @@ -52,13 +52,13 @@

cmin
-

The command identifier (starting at zero) within the inserting +

The command identifier (starting at zero) within the inserting transaction.

xmax
-

The identity (transaction ID) of the deleting transaction, or +

The identity (transaction ID) of the deleting transaction, or zero for an undeleted row version. It is possible for this column to be nonzero in a visible row version. That usually indicates that the deleting transaction hasn't committed yet, or that an attempted @@ -67,12 +67,12 @@

cmax
-

The command identifier within the deleting transaction, or zero. +

The command identifier within the deleting transaction, or zero.

ctid
-

The physical location of the row version within its table. Note that +

The physical location of the row version within its table. Note that although the ctid can be used to locate the row version very quickly, a row's ctid will change each time it is diff --git a/docs/en_US/pg/ddl.html b/docs/en_US/pg/ddl.html index 6a48fc4ff3..7d9a8c2312 100644 --- a/docs/en_US/pg/ddl.html +++ b/docs/en_US/pg/ddl.html @@ -5,7 +5,7 @@ - + @@ -21,23 +21,23 @@

5.2. Default Values
5.3. Constraints
-
5.3.1. Check Constraints
-
5.3.2. Not-Null Constraints
-
5.3.3. Unique Constraints
-
5.3.4. Primary Keys
+
5.3.1. Check Constraints
+
5.3.2. Not-Null Constraints
+
5.3.3. Unique Constraints
+
5.3.4. Primary Keys
5.3.5. Foreign Keys
5.4. System Columns
5.5. Modifying Tables
-
5.5.1. Adding a Column
-
5.5.2. Removing a Column
-
5.5.3. Adding a Constraint
-
5.5.4. Removing a Constraint
-
5.5.5. Changing a Column's Default Value
-
5.5.6. Changing a Column's Data Type
-
5.5.7. Renaming a Column
-
5.5.8. Renaming a Table
+
5.5.1. Adding a Column
+
5.5.2. Removing a Column
+
5.5.3. Adding a Constraint
+
5.5.4. Removing a Constraint
+
5.5.5. Changing a Column's Default Value
+
5.5.6. Changing a Column's Data Type
+
5.5.7. Renaming a Column
+
5.5.8. Renaming a Table
5.6. Privileges
5.7. Schemas
@@ -77,7 +77,7 @@

5.1. Table Basics

-

A table in a relational database is much like a table on paper: It +

A table in a relational database is much like a table on paper: It consists of rows and columns. The number and order of the columns is fixed, and each column has a name. The number of rows is variable — it reflects how much data is stored at a given moment. @@ -110,7 +110,7 @@ time-of-day values, and timestamp for values containing both date and time.

-

To create a table, you use the aptly named CREATE TABLE command. +

To create a table, you use the aptly named CREATE TABLE command. In this command you specify at least a name for the new table, the names of the columns and the data type of each column. For example: @@ -157,7 +157,7 @@

Tip

However, defining a table with anywhere near this many columns is highly unusual and often a questionable design.

-

If you no longer need a table, you can remove it using the DROP TABLE command. +

If you no longer need a table, you can remove it using the DROP TABLE command. For example: 

DROP TABLE my_first_table;
diff --git a/docs/en_US/pg/disk-full.html b/docs/en_US/pg/disk-full.html
index 0f348a6e0e..28868eaf9a 100644
--- a/docs/en_US/pg/disk-full.html
+++ b/docs/en_US/pg/disk-full.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/diskusage.html b/docs/en_US/pg/diskusage.html
index d62008b792..abb933dc23 100644
--- a/docs/en_US/pg/diskusage.html
+++ b/docs/en_US/pg/diskusage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 

 

 26.1. Determining Disk Usage

-
   Each table has a primary heap disk file where most of the data is
+
   Each table has a primary heap disk file where most of the data is
    stored. If the table has any columns with potentially-wide values,
    there is also a TOAST file associated with the table,
    which is used to store values too wide to fit comfortably in the main
diff --git a/docs/en_US/pg/dml-delete.html b/docs/en_US/pg/dml-delete.html
index 7be6e590d7..79defaeb8a 100644
--- a/docs/en_US/pg/dml-delete.html
+++ b/docs/en_US/pg/dml-delete.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 6.3. Deleting Data

-
   So far we have explained how to add data to tables and how to
+
   So far we have explained how to add data to tables and how to
    change data.  What remains is to discuss how to remove data that is
    no longer needed.  Just as adding data is only possible in whole
    rows, you can only remove entire rows from a table.  In the
diff --git a/docs/en_US/pg/dml-update.html b/docs/en_US/pg/dml-update.html
index ce84b8edf9..882c990bb6 100644
--- a/docs/en_US/pg/dml-update.html
+++ b/docs/en_US/pg/dml-update.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 6.2. Updating Data

-
   The modification of data that is already in the database is
+
   The modification of data that is already in the database is
    referred to as updating.  You can update individual rows, all the
    rows in a table, or a subset of all rows.  Each column can be
    updated separately; the other columns are not affected.
diff --git a/docs/en_US/pg/dml.html b/docs/en_US/pg/dml.html
index aeb644e736..22fd2b56bc 100644
--- a/docs/en_US/pg/dml.html
+++ b/docs/en_US/pg/dml.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -33,7 +33,7 @@
 

 

 6.1. Inserting Data

-
   When a table is created, it contains no data.  The first thing to
+
   When a table is created, it contains no data.  The first thing to
    do before a database can be of much use is to insert data.  Data is
    conceptually inserted one row at a time.  Of course you can also
    insert more than one row, but there is no way to insert less than
diff --git a/docs/en_US/pg/docguide-authoring.html b/docs/en_US/pg/docguide-authoring.html
index 2623771666..26614cdb7f 100644
--- a/docs/en_US/pg/docguide-authoring.html
+++ b/docs/en_US/pg/docguide-authoring.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -23,7 +23,7 @@
    

 

 

-G.4.1. Emacs/PSGML

+G.4.1. Emacs/PSGML

 
     PSGML is the most common and most
      powerful mode for editing SGML documents.
      When properly configured, it will allow you to use
@@ -98,7 +98,7 @@
 

 

 

-G.4.2. Other Emacs modes

+G.4.2. Other Emacs modes

GNU Emacs ships with a different SGML mode, which is not quite as powerful as PSGML, but it's less confusing and diff --git a/docs/en_US/pg/docguide-build.html b/docs/en_US/pg/docguide-build.html index 343babaead..3be0501fea 100644 --- a/docs/en_US/pg/docguide-build.html +++ b/docs/en_US/pg/docguide-build.html @@ -5,7 +5,7 @@ - + @@ -21,7 +21,7 @@

-G.3.1. HTML

+G.3.1. HTML

To build the HTML version of the documentation: 

doc/src/sgml$ gmake html
@@ -49,7 +49,7 @@

-G.3.2. Manpages

+G.3.2. Manpages

We use the docbook2man utility to convert DocBook refentry pages to *roff output suitable for man @@ -71,7 +71,7 @@

-G.3.3. Print Output via JadeTex

+G.3.3. Print Output via JadeTex

If you want to use JadeTex to produce a printable rendition of the documentation, you can use one of the following commands: @@ -108,7 +108,7 @@

-G.3.4. Print Output via RTF

+G.3.4. Print Output via RTF

You can also create a printable version of the PostgreSQL documentation by converting it to RTF and applying minor formatting corrections using an office suite. @@ -128,7 +128,7 @@

Note

-

Applixware RTF Cleanup

+

Applixware RTF Cleanup

OpenJade omits specifying a default style for body text. In the past, this undiagnosed problem led to a long process of table of contents generation. However, with @@ -278,7 +278,7 @@

Note

-G.3.5. Plain Text Files

+G.3.5. Plain Text Files

Several files are distributed as plain text, for reading during the installation process. The INSTALL file corresponds to Chapter 14, Installation Instructions, with some minor @@ -301,7 +301,7 @@

Note

-G.3.6. Syntax Check

+G.3.6. Syntax Check

Building the documentation can take very long. But there is a method to just check the correct syntax of the documentation files, which only takes a few seconds: diff --git a/docs/en_US/pg/docguide-style.html b/docs/en_US/pg/docguide-style.html index cfdc3581d0..543009004b 100644 --- a/docs/en_US/pg/docguide-style.html +++ b/docs/en_US/pg/docguide-style.html @@ -5,7 +5,7 @@ - + @@ -16,7 +16,7 @@ G.5. Style Guide

-G.5.1. Reference Pages

+G.5.1. Reference Pages

Reference pages should follow a standard layout. This allows users to find the desired information more quickly, and it also encourages writers to document all relevant aspects of a command. diff --git a/docs/en_US/pg/docguide-toolsets.html b/docs/en_US/pg/docguide-toolsets.html index bfe590f2ea..f051c96e27 100644 --- a/docs/en_US/pg/docguide-toolsets.html +++ b/docs/en_US/pg/docguide-toolsets.html @@ -5,7 +5,7 @@ - + @@ -76,7 +76,7 @@

-G.2.1. Linux RPM Installation

+G.2.1. Linux RPM Installation

Most vendors provide a complete RPM set for DocBook processing in their distribution. Look for an “SGML” option while installing, or the following packages: @@ -90,7 +90,7 @@

-G.2.2. FreeBSD Installation

+G.2.2. FreeBSD Installation

The FreeBSD Documentation Project is itself a heavy user of DocBook, so it comes as no surprise that there is a full set of “ports” of the documentation tools available on @@ -127,7 +127,7 @@

-G.2.3. Debian Packages

+G.2.3. Debian Packages

There is a full set of packages of the documentation tools available for Debian GNU/Linux. To install, simply use: @@ -140,7 +140,7 @@

-G.2.4. Manual Installation from Source

+G.2.4. Manual Installation from Source

The manual installation process of the DocBook tools is somewhat complex, so if you have pre-built packages available, use them. We describe here only a standard setup, with reasonably standard @@ -150,7 +150,7 @@

-G.2.4.1. Installing OpenJade

+G.2.4.1. Installing OpenJade

  1. The installation of OpenJade offers a GNU-style @@ -201,7 +201,7 @@

-G.2.4.2. Installing the DocBook DTD Kit

+G.2.4.2. Installing the DocBook DTD Kit

  1. Obtain the DocBook V4.2 distribution.

    2. @@ -257,7 +257,7 @@

-G.2.4.3. Installing the DocBook DSSSL Style Sheets

+G.2.4.3. Installing the DocBook DSSSL Style Sheets

To install the style sheets, unzip and untar the distribution and move it to a suitable place, for example /usr/local/share/sgml. (The archive will @@ -282,7 +282,7 @@

-G.2.4.4. Installing JadeTeX

+G.2.4.4. Installing JadeTeX

To install and use JadeTeX, you will need a working installation of TeX and LaTeX2e, including the supported diff --git a/docs/en_US/pg/docguide.html b/docs/en_US/pg/docguide.html index f07b221ba7..9985d35fbf 100644 --- a/docs/en_US/pg/docguide.html +++ b/docs/en_US/pg/docguide.html @@ -5,7 +5,7 @@ - + @@ -20,28 +20,28 @@

G.1. DocBook
G.2. Tool Sets
-
G.2.1. Linux RPM Installation
-
G.2.2. FreeBSD Installation
-
G.2.3. Debian Packages
-
G.2.4. Manual Installation from Source
+
G.2.1. Linux RPM Installation
+
G.2.2. FreeBSD Installation
+
G.2.3. Debian Packages
+
G.2.4. Manual Installation from Source
G.2.5. Detection by configure
G.3. Building The Documentation
-
G.3.1. HTML
-
G.3.2. Manpages
-
G.3.3. Print Output via JadeTex
-
G.3.4. Print Output via RTF
-
G.3.5. Plain Text Files
-
G.3.6. Syntax Check
+
G.3.1. HTML
+
G.3.2. Manpages
+
G.3.3. Print Output via JadeTex
+
G.3.4. Print Output via RTF
+
G.3.5. Plain Text Files
+
G.3.6. Syntax Check
G.4. Documentation Authoring
-
G.4.1. Emacs/PSGML
-
G.4.2. Other Emacs modes
+
G.4.1. Emacs/PSGML
+
G.4.2. Other Emacs modes
G.5. Style Guide
-
G.5.1. Reference Pages
+
G.5.1. Reference Pages

PostgreSQL has four primary documentation diff --git a/docs/en_US/pg/dynamic-trace.html b/docs/en_US/pg/dynamic-trace.html index 60b39183d3..561e274f45 100644 --- a/docs/en_US/pg/dynamic-trace.html +++ b/docs/en_US/pg/dynamic-trace.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

25.4. Dynamic Tracing

-

PostgreSQL provides facilities to support +

PostgreSQL provides facilities to support dynamic tracing of the database server. This allows an external utility to be called at specific points in the code and thereby trace execution. Currently, this facility is primarily intended for use by @@ -35,27 +35,11 @@

-25.4.1. Compiling for Dynamic Trace

+25.4.1. Compiling for Dynamic Tracing

By default, trace points are disabled, so you will need to explicitly tell the configure script to make the probes available in PostgreSQL. To include DTrace support - in a 32-bit binary, specify --enable-dtrace to configure. - For example: -

-
      $ ./configure --enable-dtrace ...
-

- To include DTrace support in a 64-bit binary, specify - --enable-dtrace - and DTRACEFLAGS="-64" to configure. For example, - using the gcc compiler: -

-
      $ ./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ...
-

- Using Sun's compiler: -

-
            
-      $ ./configure CC='/path_to_sun_compiler/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64' ...
-

+ specify --enable-dtrace to configure. See Section 14.5, “Installation Procedure” for further information.

@@ -63,7 +47,7 @@ 25.4.2. Built-in Trace Points

A few standard trace points are provided in the source code (of course, more can be added as needed for a particular problem). - These are: + These are shown in Table 25.3, “Built-in Trace Points”.

Table 25.3. Built-in Trace Points

@@ -182,12 +166,11 @@ be replaced by a hyphen when using D script. When executed, the example D script gives output such as:

-
# ./txn_count.d `pgrep -n postgres`
+
# ./txn_count.d `pgrep -n postgres`
 ^C
 
 Start                                          71
 Commit                                         70
-Abort                                           1
 Total time (ns)                        2312105013

 

   

@@ -203,7 +186,7 @@
 

 25.4.4. Defining Trace Points

 
   New trace points can be defined within the code wherever the developer
-   desires, though this will require a re-compile.
+   desires, though this will require a recompilation.
   

 
   A trace point can be inserted by using one of the
    trace macros. These are chosen according to how many variables will
@@ -211,14 +194,14 @@
    occurrence of an event can be achieved with a single line, using
    just the trace point name, e.g.
 

-
      PG_TRACE (my__new__trace__point);

+
PG_TRACE (my__new__trace__point);

 

    More complex trace points can be provided with one or more variables
    for inspection by the dynamic tracing utility by using the
    PG_TRACEn macro that corresponds to the number
    of parameters after the trace point name:
 

-
      PG_TRACE3 (my__complex__event, varX, varY, varZ);

+
PG_TRACE3 (my__complex__event, varX, varY, varZ);

 

    The definition of the transaction__start trace point is shown below:
 

@@ -253,7 +236,7 @@
  };

-

You should take care that the datatypes specified for the probe arguments +

You should take care that the data types specified for the probe arguments match the datatypes of the variables used in the PG_TRACE macro. This is not checked at compile time. You can check that your newly added trace point is available by recompiling, then running the new binary, diff --git a/docs/en_US/pg/ecpg-commands.html b/docs/en_US/pg/ecpg-commands.html index 0b54799d0d..a36f6206d7 100644 --- a/docs/en_US/pg/ecpg-commands.html +++ b/docs/en_US/pg/ecpg-commands.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-connect.html b/docs/en_US/pg/ecpg-connect.html index d90673322f..8d02506b31 100644 --- a/docs/en_US/pg/ecpg-connect.html +++ b/docs/en_US/pg/ecpg-connect.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-descriptors.html b/docs/en_US/pg/ecpg-descriptors.html index 8068f356a0..0f1dfd739f 100644 --- a/docs/en_US/pg/ecpg-descriptors.html +++ b/docs/en_US/pg/ecpg-descriptors.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-develop.html b/docs/en_US/pg/ecpg-develop.html index d26d4b47dc..8aadf7a90b 100644 --- a/docs/en_US/pg/ecpg-develop.html +++ b/docs/en_US/pg/ecpg-develop.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-disconnect.html b/docs/en_US/pg/ecpg-disconnect.html index ec3508d96a..0dd1d9e574 100644 --- a/docs/en_US/pg/ecpg-disconnect.html +++ b/docs/en_US/pg/ecpg-disconnect.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-dynamic.html b/docs/en_US/pg/ecpg-dynamic.html index fda33af139..d17b2e39d6 100644 --- a/docs/en_US/pg/ecpg-dynamic.html +++ b/docs/en_US/pg/ecpg-dynamic.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-errors.html b/docs/en_US/pg/ecpg-errors.html index 21e2140f68..4d415ec7d3 100644 --- a/docs/en_US/pg/ecpg-errors.html +++ b/docs/en_US/pg/ecpg-errors.html @@ -5,7 +5,7 @@ - + @@ -20,7 +20,7 @@

-31.11.1. Setting Callbacks

+31.11.1. Setting Callbacks

One simple method to catch errors and warnings is to set a specific action to be executed whenever a particular condition occurs. In general: @@ -142,7 +142,7 @@

-31.11.2. sqlca

+31.11.2. sqlca

For more powerful error handling, the embedded SQL interface provides a global variable with the name sqlca that has the following structure: @@ -226,7 +226,7 @@

-31.11.3. SQLSTATE vs SQLCODE

+31.11.3. SQLSTATE vs SQLCODE

The fields sqlca.sqlstate and sqlca.sqlcode are two different schemes that provide error codes. Both are derived from the SQL standard, but diff --git a/docs/en_US/pg/ecpg-informix-compat.html b/docs/en_US/pg/ecpg-informix-compat.html index a18909c9fd..57160155a6 100644 --- a/docs/en_US/pg/ecpg-informix-compat.html +++ b/docs/en_US/pg/ecpg-informix-compat.html @@ -5,7 +5,7 @@ - + @@ -51,7 +51,7 @@

-31.9.1. Additional embedded SQL statements

+31.9.1. Additional embedded SQL statements

CLOSE DATABASE
@@ -70,7 +70,7 @@

-31.9.2. Additional functions

+31.9.2. Additional functions

decadd
@@ -820,7 +820,7 @@

-31.9.3. Additional constants

+31.9.3. Additional constants

Note that all constants here describe errors and all of them are defined to represent negative values. In the descriptions of the different constants you can also find the value that the constants represent in the diff --git a/docs/en_US/pg/ecpg-library.html b/docs/en_US/pg/ecpg-library.html index bfbabcad6b..e1f9f2efe2 100644 --- a/docs/en_US/pg/ecpg-library.html +++ b/docs/en_US/pg/ecpg-library.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-pgtypes.html b/docs/en_US/pg/ecpg-pgtypes.html index 1961c8bde7..98368de4bb 100644 --- a/docs/en_US/pg/ecpg-pgtypes.html +++ b/docs/en_US/pg/ecpg-pgtypes.html @@ -5,7 +5,7 @@ - + @@ -37,7 +37,7 @@

-31.8.1. The numeric type

+31.8.1. The numeric type

The numeric type offers to do calculations with arbitrary precision. See Section 8.1, “Numeric Types” for the equivalent type in the PostgreSQL server. Because of the arbitrary precision this @@ -282,7 +282,7 @@

-31.8.2. The date type

+31.8.2. The date type

The date type in C enables your programs to deal with data of the SQL type date. See Section 8.5, “Date/Time Types” for the equivalent type in the PostgreSQL server. @@ -322,7 +322,7 @@

The following input formats are allowed:

-

Table 31.1. Valid input formats for PGTYPESdate_from_asc

+

Table 31.1. Valid input formats for PGTYPESdate_from_asc

@@ -533,7 +533,7 @@ the same date: November, 23rd, 1959.

-

Table 31.2. Valid input formats for PGTYPESdate_fmt_asc

+

Table 31.2. Valid input formats for PGTYPESdate_fmt_asc

@@ -624,7 +624,7 @@ you an idea of how to use this function.

-

Table 31.3. Valid input formats for rdefmtdate

+

Table 31.3. Valid input formats for rdefmtdate

@@ -713,7 +713,7 @@

-31.8.3. The timestamp type

+31.8.3. The timestamp type

The timestamp type in C enables your programs to deal with data of the SQL type timestamp. See Section 8.5, “Date/Time Types” for the equivalent type in the PostgreSQL server. @@ -752,7 +752,7 @@

The following table contains a few examples for input strings:

-

Table 31.4. Valid input formats for PGTYPEStimestamp_from_asc

+

Table 31.4. Valid input formats for PGTYPEStimestamp_from_asc

@@ -1081,7 +1081,7 @@

-31.8.4. The interval type

+31.8.4. The interval type

The interval type in C enables your programs to deal with data of the SQL type interval. See Section 8.5, “Date/Time Types” for the equivalent type in the PostgreSQL server. @@ -1158,7 +1158,7 @@

-31.8.5. The decimal type

+31.8.5. The decimal type

The decimal type is similar to the numeric type. However it is limited to a maximal precision of 30 significant digits. In contrast to the numeric type which can be created on the heap only, the decimal type can be @@ -1193,7 +1193,7 @@

-31.8.6. errno values of pgtypeslib

+31.8.6. errno values of pgtypeslib

PGTYPES_NUM_BAD_NUMERIC
@@ -1243,7 +1243,7 @@

-31.8.7. Special constants of pgtypeslib

+31.8.7. Special constants of pgtypeslib

diff --git a/docs/en_US/pg/ecpg-preproc.html b/docs/en_US/pg/ecpg-preproc.html index fac795ff40..426bdb4065 100644 --- a/docs/en_US/pg/ecpg-preproc.html +++ b/docs/en_US/pg/ecpg-preproc.html @@ -5,7 +5,7 @@ - + @@ -16,7 +16,7 @@ 31.12. Preprocessor directives

-31.12.1. Including files

+31.12.1. Including files

To include an external file into your embedded SQL program, use: 

EXEC SQL INCLUDE filename;
@@ -45,7 +45,7 @@

Note

-31.12.2. The #define and #undef directives

+31.12.2. The #define and #undef directives

Similar to the directive #define that is known from C, embedded SQL has a similar concept:

@@ -85,7 +85,7 @@

Note

-31.12.3. ifdef, ifndef, else, elif and endif directives

+31.12.3. ifdef, ifndef, else, elif and endif directives

You can use the following directives to compile code sections conditionally:

diff --git a/docs/en_US/pg/ecpg-process.html b/docs/en_US/pg/ecpg-process.html index c4bd077e72..3fae920f3d 100644 --- a/docs/en_US/pg/ecpg-process.html +++ b/docs/en_US/pg/ecpg-process.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-set-connection.html b/docs/en_US/pg/ecpg-set-connection.html index e0a84190dd..76bf5c6c08 100644 --- a/docs/en_US/pg/ecpg-set-connection.html +++ b/docs/en_US/pg/ecpg-set-connection.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/ecpg-variables.html b/docs/en_US/pg/ecpg-variables.html index 9f1703528b..9327a6b826 100644 --- a/docs/en_US/pg/ecpg-variables.html +++ b/docs/en_US/pg/ecpg-variables.html @@ -5,7 +5,7 @@ - + @@ -30,7 +30,7 @@

-31.6.1. Overview

+31.6.1. Overview

Passing data between the C program and the SQL statements is particularly simple in embedded SQL. Instead of having the program paste the data into the statement, which entails various @@ -51,7 +51,7 @@

-31.6.2. Declare Sections

+31.6.2. Declare Sections

To pass data from the program to the database, for example as parameters in a query, or to pass data from the database back to the program, the C variables that are intended to contain this @@ -94,7 +94,7 @@

-31.6.3. Different types of host variables

+31.6.3. Different types of host variables

As a host variable you can also use arrays, typedefs, structs and pointers. Moreover there are special types of host variables that exist only in ECPG. @@ -174,7 +174,7 @@

-31.6.4. SELECT INTO and FETCH INTO

+31.6.4. SELECT INTO and FETCH INTO

Now you should be able to pass data generated by your program into an SQL command. But how do you retrieve the results of a query? For that purpose, embedded SQL provides special variants of the @@ -234,7 +234,7 @@

-31.6.5. Indicators

+31.6.5. Indicators

The examples above do not handle null values. In fact, the retrieval examples will raise an error if they fetch a null value from the database. To be able to pass null values to the database diff --git a/docs/en_US/pg/ecpg.html b/docs/en_US/pg/ecpg.html index 372a60030c..7951053fd1 100644 --- a/docs/en_US/pg/ecpg.html +++ b/docs/en_US/pg/ecpg.html @@ -5,7 +5,7 @@ - + @@ -24,48 +24,48 @@

31.5. Choosing a Connection
31.6. Using Host Variables
-
31.6.1. Overview
-
31.6.2. Declare Sections
-
31.6.3. Different types of host variables
-
31.6.4. SELECT INTO and FETCH INTO
-
31.6.5. Indicators
+
31.6.1. Overview
+
31.6.2. Declare Sections
+
31.6.3. Different types of host variables
+
31.6.4. SELECT INTO and FETCH INTO
+
31.6.5. Indicators
31.7. Dynamic SQL
31.8. pgtypes library
-
31.8.1. The numeric type
-
31.8.2. The date type
-
31.8.3. The timestamp type
-
31.8.4. The interval type
-
31.8.5. The decimal type
-
31.8.6. errno values of pgtypeslib
-
31.8.7. Special constants of pgtypeslib
+
31.8.1. The numeric type
+
31.8.2. The date type
+
31.8.3. The timestamp type
+
31.8.4. The interval type
+
31.8.5. The decimal type
+
31.8.6. errno values of pgtypeslib
+
31.8.7. Special constants of pgtypeslib
31.9. Informix compatibility mode
-
31.9.1. Additional embedded SQL statements
-
31.9.2. Additional functions
-
31.9.3. Additional constants
+
31.9.1. Additional embedded SQL statements
+
31.9.2. Additional functions
+
31.9.3. Additional constants
31.10. Using SQL Descriptor Areas
31.11. Error Handling
-
31.11.1. Setting Callbacks
-
31.11.2. sqlca
-
31.11.3. SQLSTATE vs SQLCODE
+
31.11.1. Setting Callbacks
+
31.11.2. sqlca
+
31.11.3. SQLSTATE vs SQLCODE
31.12. Preprocessor directives
-
31.12.1. Including files
-
31.12.2. The #define and #undef directives
-
31.12.3. ifdef, ifndef, else, elif and endif directives
+
31.12.1. Including files
+
31.12.2. The #define and #undef directives
+
31.12.3. ifdef, ifndef, else, elif and endif directives
31.13. Processing Embedded SQL Programs
31.14. Library Functions
31.15. Internals
-

This chapter describes the embedded SQL package +

This chapter describes the embedded SQL package for PostgreSQL. It was written by Linus Tolke () and Michael Meskes (). Originally it was written to work with diff --git a/docs/en_US/pg/encryption-options.html b/docs/en_US/pg/encryption-options.html index 3ed48a0528..4b9c595cf5 100644 --- a/docs/en_US/pg/encryption-options.html +++ b/docs/en_US/pg/encryption-options.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

16.6. Encryption Options

-

PostgreSQL offers encryption at several +

PostgreSQL offers encryption at several levels, and provides flexibility in protecting data from disclosure due to database server theft, unscrupulous administrators, and insecure networks. Encryption might also be required to secure diff --git a/docs/en_US/pg/errcodes-appendix.html b/docs/en_US/pg/errcodes-appendix.html index ab07a7bca3..0434de76d0 100644 --- a/docs/en_US/pg/errcodes-appendix.html +++ b/docs/en_US/pg/errcodes-appendix.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

Appendix A. PostgreSQL Error Codes

-

All messages emitted by the PostgreSQL +

All messages emitted by the PostgreSQL server are assigned five-character error codes that follow the SQL standard's conventions for “SQLSTATE” codes. Applications that need to know which error condition has occurred should usually @@ -34,7 +34,7 @@ what to do from the error class.

Table A.1, “PostgreSQL Error Codes” lists all the error codes defined in - PostgreSQL 8.2.0. (Some are not actually + PostgreSQL 8.2.1. (Some are not actually used at present, but are defined by the SQL standard.) The error classes are also shown. For each error class there is a “standard” error code having the last three characters diff --git a/docs/en_US/pg/error-message-reporting.html b/docs/en_US/pg/error-message-reporting.html index 711adf31e7..a1a26624aa 100644 --- a/docs/en_US/pg/error-message-reporting.html +++ b/docs/en_US/pg/error-message-reporting.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

45.2. Reporting Errors Within the Server

-

Error, warning, and log messages generated within the server code +

Error, warning, and log messages generated within the server code should be created using ereport, or its older cousin elog. The use of this function is complex enough to require some explanation. @@ -77,7 +77,7 @@ the standard format codes accepted by sprintf, the format code %m can be used to insert the error message returned by strerror for the current value of errno. - [9] + [9] %m does not require any corresponding entry in the parameter list for errmsg. Note that the message string will be run through gettext @@ -154,7 +154,7 @@


-

[9] That is, the value that was current when the ereport call +

[9] That is, the value that was current when the ereport call was reached; changes of errno within the auxiliary reporting routines will not affect it. That would not be true if you were to write strerror(errno) explicitly in errmsg's diff --git a/docs/en_US/pg/error-style-guide.html b/docs/en_US/pg/error-style-guide.html index d14f7765bd..6f792bdf90 100644 --- a/docs/en_US/pg/error-style-guide.html +++ b/docs/en_US/pg/error-style-guide.html @@ -5,7 +5,7 @@ - + @@ -20,7 +20,7 @@

-What goes where

+What goes where

The primary message should be short, factual, and avoid reference to implementation details such as specific function names. “Short” means “should fit on one line under normal @@ -54,7 +54,7 @@

-Formatting

+Formatting

Don't put any specific assumptions about formatting into the message texts. Expect clients and the server log to wrap lines to fit their own needs. In long messages, newline characters (\n) may be used to indicate @@ -70,7 +70,7 @@

-Quotation marks

+Quotation marks

English text should use double quotes when quoting is appropriate. Text in other languages should consistently use one kind of quotes that is consistent with publishing customs and computer output of other programs. @@ -86,7 +86,7 @@

-Use of quotes

+Use of quotes

Use quotes always to delimit file names, user-supplied identifiers, and other variables that might contain words. Do not use them to mark up variables that will not contain words (for example, operator names). @@ -103,7 +103,7 @@

-Grammar and punctuation

+Grammar and punctuation

The rules are different for primary error messages and for detail/hint messages:

@@ -125,7 +125,7 @@

-Upper case vs. lower case

+Upper case vs. lower case

Use lower case for message wording, including the first letter of a primary error message. Use upper case for SQL commands and key words if they appear in the message. @@ -136,7 +136,7 @@

-Avoid passive voice

+Avoid passive voice

Use the active voice. Use complete sentences when there is an acting subject (“A could not do B”). Use telegram style without subject if the subject would be the program itself; do not use @@ -147,7 +147,7 @@

-Present vs past tense

+Present vs past tense

Use past tense if an attempt to do something failed, but could perhaps succeed next time (perhaps after fixing some problem). Use present tense if the failure is certainly permanent. @@ -178,7 +178,7 @@

-Type of the object

+Type of the object

When citing the name of an object, state what kind of object it is.

Rationale: Otherwise no one will know what “foo.bar.baz” @@ -187,7 +187,7 @@

-Brackets

+Brackets

Square brackets are only to be used (1) in command synopses to denote optional arguments, or (2) to denote an array subscript.

@@ -197,7 +197,7 @@

-Assembling error messages

+Assembling error messages

When a message includes text that is generated elsewhere, embed it in this style:

@@ -213,7 +213,7 @@

-Reasons for errors

+Reasons for errors

Messages should always state the reason why an error occurred. For example:

@@ -225,7 +225,7 @@

-Function names

+Function names

Don't include the name of the reporting routine in the error text. We have other mechanisms for finding that out when needed, and for most users it's not helpful information. If the error text doesn't make as much sense @@ -250,7 +250,7 @@

-Tricky words to avoid

+Tricky words to avoid

Unable.  “Unable” is nearly the passive voice. Better use “cannot” or “could not”, as appropriate.

@@ -280,7 +280,7 @@

-Proper spelling

+Proper spelling

Spell out words in full. For instance, avoid:

    @@ -302,7 +302,7 @@

-Localization

+Localization

Keep in mind that error message texts need to be translated into other languages. Follow the guidelines in Section 46.2.2, “Message-writing guidelines” to avoid making life difficult for translators. diff --git a/docs/en_US/pg/executor.html b/docs/en_US/pg/executor.html index a70bbea648..556d57590b 100644 --- a/docs/en_US/pg/executor.html +++ b/docs/en_US/pg/executor.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/explicit-joins.html b/docs/en_US/pg/explicit-joins.html index 05512ab53a..f4d2247bfa 100644 --- a/docs/en_US/pg/explicit-joins.html +++ b/docs/en_US/pg/explicit-joins.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

13.3. Controlling the Planner with Explicit JOIN Clauses

-

It is possible +

It is possible to control the query planner to some extent by using the explicit JOIN syntax. To see why this matters, we first need some background.

diff --git a/docs/en_US/pg/explicit-locking.html b/docs/en_US/pg/explicit-locking.html index 3139f3d98e..c7d5a05e8b 100644 --- a/docs/en_US/pg/explicit-locking.html +++ b/docs/en_US/pg/explicit-locking.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

12.3. Explicit Locking

-

PostgreSQL provides various lock modes +

PostgreSQL provides various lock modes to control concurrent access to data in tables. These modes can be used for application-controlled locking in situations where MVCC does not give the desired behavior. Also, @@ -34,7 +34,7 @@

12.3.1. Table-Level Locks

-

The list below shows the available lock modes and the contexts in +

The list below shows the available lock modes and the contexts in which they are used automatically by PostgreSQL. You can also acquire any of these locks explicitly with the command LOCK. @@ -233,7 +233,7 @@

Tip

12.3.3. Deadlocks

-

The use of explicit locking can increase the likelihood of +

The use of explicit locking can increase the likelihood of deadlocks, wherein two (or more) transactions each hold locks that the other wants. For example, if transaction 1 acquires an exclusive lock on table A and then tries to acquire @@ -305,7 +305,7 @@

Tip

12.3.4. Advisory Locks

-

PostgreSQL provides a means for +

PostgreSQL provides a means for creating locks that have application-defined meanings. These are called advisory locks, because the system does not enforce their use — it is up to the application to use them diff --git a/docs/en_US/pg/extend-type-system.html b/docs/en_US/pg/extend-type-system.html index 8c64295844..7dc8d1dca7 100644 --- a/docs/en_US/pg/extend-type-system.html +++ b/docs/en_US/pg/extend-type-system.html @@ -5,7 +5,7 @@ - + @@ -14,12 +14,12 @@

33.2. The PostgreSQL Type System

-

PostgreSQL data types are divided into base +

PostgreSQL data types are divided into base types, composite types, domains, and pseudo-types.

-33.2.1. Base Types

+33.2.1. Base Types

Base types are those, like int4, that are implemented below the level of the SQL language (typically in a low-level language such as C). They generally @@ -35,7 +35,7 @@

-33.2.2. Composite Types

+33.2.2. Composite Types

Composite types, or row types, are created whenever the user creates a table. It is also possible to use CREATE TYPE to define a “stand-alone” composite type with no associated @@ -48,7 +48,7 @@

-33.2.3. Domains

+33.2.3. Domains

A domain is based on a particular base type and for many purposes is interchangeable with its base type. However, a domain may have constraints that restrict its valid values to a subset of @@ -61,7 +61,7 @@

-33.2.4. Pseudo-Types

+33.2.4. Pseudo-Types

There are a few “pseudo-types” for special purposes. Pseudo-types cannot appear as columns of tables or attributes of composite types, but they can be used to declare the argument and @@ -73,7 +73,7 @@

33.2.5. Polymorphic Types

-

Two pseudo-types of special interest are anyelement and +

Two pseudo-types of special interest are anyelement and anyarray, which are collectively called polymorphic types. Any function declared using these types is said to be a polymorphic function. A polymorphic function can diff --git a/docs/en_US/pg/extend.html b/docs/en_US/pg/extend.html index 4fe69c45ff..8b4443278b 100644 --- a/docs/en_US/pg/extend.html +++ b/docs/en_US/pg/extend.html @@ -5,7 +5,7 @@ - + @@ -20,21 +20,21 @@

33.1. How Extensibility Works
33.2. The PostgreSQL Type System
-
33.2.1. Base Types
-
33.2.2. Composite Types
-
33.2.3. Domains
-
33.2.4. Pseudo-Types
+
33.2.1. Base Types
+
33.2.2. Composite Types
+
33.2.3. Domains
+
33.2.4. Pseudo-Types
33.2.5. Polymorphic Types
33.3. User-Defined Functions
33.4. Query Language (SQL) Functions
33.4.1. SQL Functions on Base Types
-
33.4.2. SQL Functions on Composite Types
+
33.4.2. SQL Functions on Composite Types
33.4.3. Functions with Output Parameters
33.4.4. SQL Functions as Table Sources
-
33.4.5. SQL Functions Returning Sets
-
33.4.6. Polymorphic SQL Functions
+
33.4.5. SQL Functions Returning Sets
+
33.4.6. Polymorphic SQL Functions
33.5. Function Overloading
33.6. Function Volatility Categories
@@ -44,28 +44,28 @@
33.9.1. Dynamic Loading
33.9.2. Base Types in C-Language Functions
-
33.9.3. Version 0 Calling Conventions
-
33.9.4. Version 1 Calling Conventions
-
33.9.5. Writing Code
+
33.9.3. Version 0 Calling Conventions
+
33.9.4. Version 1 Calling Conventions
+
33.9.5. Writing Code
33.9.6. Compiling and Linking Dynamically-Loaded Functions
33.9.7. Extension Building Infrastructure
-
33.9.8. Composite-Type Arguments
-
33.9.9. Returning Rows (Composite Types)
+
33.9.8. Composite-Type Arguments
+
33.9.9. Returning Rows (Composite Types)
33.9.10. Returning Sets
-
33.9.11. Polymorphic Arguments and Return Types
-
33.9.12. Shared Memory and LWLocks
+
33.9.11. Polymorphic Arguments and Return Types
+
33.9.12. Shared Memory and LWLocks
33.10. User-Defined Aggregates
33.11. User-Defined Types
33.12. User-Defined Operators
33.13. Operator Optimization Information
-
33.13.1. COMMUTATOR
-
33.13.2. NEGATOR
-
33.13.3. RESTRICT
-
33.13.4. JOIN
-
33.13.5. HASHES
-
33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
+
33.13.1. COMMUTATOR
+
33.13.2. NEGATOR
+
33.13.3. RESTRICT
+
33.13.4. JOIN
+
33.13.5. HASHES
+
33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
33.14. Interfacing Extensions To Indexes
@@ -79,7 +79,7 @@
-

In the sections that follow, we will discuss how you +

In the sections that follow, we will discuss how you can extend the PostgreSQL SQL query language by adding: diff --git a/docs/en_US/pg/external-extensions.html b/docs/en_US/pg/external-extensions.html index 14f27fc41e..c775a839de 100644 --- a/docs/en_US/pg/external-extensions.html +++ b/docs/en_US/pg/external-extensions.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

H.3. Extensions

-

PostgreSQL is designed to be easily extensible. For +

PostgreSQL is designed to be easily extensible. For this reason, extensions loaded into the database can function just like features that are packaged with the database. The contrib/ directory shipped with the source code diff --git a/docs/en_US/pg/external-pl.html b/docs/en_US/pg/external-pl.html index 02de0775a6..0cc040a4b6 100644 --- a/docs/en_US/pg/external-pl.html +++ b/docs/en_US/pg/external-pl.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

H.2. Procedural Languages

-

PostgreSQL includes several procedural +

PostgreSQL includes several procedural languages with the base distribution: PL/PgSQL, PL/Tcl, PL/Perl, and PL/Python.

diff --git a/docs/en_US/pg/external-projects.html b/docs/en_US/pg/external-projects.html index 7e05c2aa1d..0a954e9631 100644 --- a/docs/en_US/pg/external-projects.html +++ b/docs/en_US/pg/external-projects.html @@ -5,7 +5,7 @@ - + @@ -53,7 +53,7 @@

Note

H.1. Client Interfaces

-

There are only two client interfaces included in the base +

There are only two client interfaces included in the base PostgreSQL distribution:

    diff --git a/docs/en_US/pg/features.html b/docs/en_US/pg/features.html index 2054859c71..18da5530e6 100644 --- a/docs/en_US/pg/features.html +++ b/docs/en_US/pg/features.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/functions-admin.html b/docs/en_US/pg/functions-admin.html index f82db9f9b6..bb568242e0 100644 --- a/docs/en_US/pg/functions-admin.html +++ b/docs/en_US/pg/functions-admin.html @@ -5,7 +5,7 @@ - + @@ -48,7 +48,7 @@
-

The function current_setting yields the +

The function current_setting yields the current value of the setting setting_name. It corresponds to the SQL command SHOW. An example: @@ -78,7 +78,7 @@ (1 row)

-

The functions shown in Table 9.46, “Server Signalling Functions” send control signals to +

The functions shown in Table 9.46, “Server Signalling Functions” send control signals to other server processes. Use of these functions is restricted to superusers.

@@ -137,7 +137,7 @@ redirect_stderr is used for logging, since otherwise there is no log-file manager subprocess.

-

The functions shown in Table 9.47, “Backup Control Functions” assist in making on-line backups. +

The functions shown in Table 9.47, “Backup Control Functions” assist in making on-line backups. Use of the first three functions is restricted to superusers.

@@ -268,7 +268,7 @@

The functions shown in Table 9.48, “Database Object Size Functions” calculate the actual disk space usage of database objects.

-
+

Table 9.48. Database Object Size Functions

@@ -412,16 +412,16 @@
-

pg_ls_dir returns all the names in the specified +

pg_ls_dir returns all the names in the specified directory, except the special entries “.” and “..”.

-

pg_read_file returns part of a text file, starting +

pg_read_file returns part of a text file, starting at the given offset, returning at most length bytes (less if the end of file is reached first). If offset is negative, it is relative to the end of the file.

-

pg_stat_file returns a record containing the file +

pg_stat_file returns a record containing the file size, last accessed time stamp, last modified time stamp, last file status change time stamp (Unix platforms only), file creation time stamp (Windows only), and a boolean @@ -530,7 +530,7 @@

-

pg_advisory_lock locks an application-defined resource, +

pg_advisory_lock locks an application-defined resource, which may be identified either by a single 64-bit key value or two 32-bit key values (note that these two key spaces do not overlap). If another session already holds a lock on the same resource, the @@ -539,32 +539,32 @@ is locked three times it must be also unlocked three times to be released for other sessions' use.

-

pg_advisory_lock_shared works the same as +

pg_advisory_lock_shared works the same as pg_advisory_lock, except the lock can be shared with other sessions requesting shared locks. Only would-be exclusive lockers are locked out.

-

pg_try_advisory_lock is similar to +

pg_try_advisory_lock is similar to pg_advisory_lock, except the function will not wait for the lock to become available. It will either obtain the lock immediately and return true, or return false if the lock cannot be acquired now.

-

pg_try_advisory_lock_shared works the same as +

pg_try_advisory_lock_shared works the same as pg_try_advisory_lock, except it attempts to acquire shared rather than exclusive lock.

-

pg_advisory_unlock will release a previously-acquired +

pg_advisory_unlock will release a previously-acquired exclusive advisory lock. It will return true if the lock is successfully released. If the lock was in fact not held, it will return false, and in addition, an SQL warning will be raised by the server.

-

pg_advisory_unlock_shared works the same as +

pg_advisory_unlock_shared works the same as pg_advisory_unlock, except to release a shared advisory lock.

-

pg_advisory_unlock_all will release all advisory locks +

pg_advisory_unlock_all will release all advisory locks held by the current session. (This function is implicitly invoked at session end, even if the client disconnects ungracefully.)

diff --git a/docs/en_US/pg/functions-aggregate.html b/docs/en_US/pg/functions-aggregate.html index 0f6c113ca4..9dd71f82c0 100644 --- a/docs/en_US/pg/functions-aggregate.html +++ b/docs/en_US/pg/functions-aggregate.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.15. Aggregate Functions

-

Aggregate functions compute a single result +

Aggregate functions compute a single result value from a set of input values. The built-in aggregate functions are listed in Table 9.37, “General-Purpose Aggregate Functions” and @@ -41,7 +41,7 @@ - + avg(expression) smallint, int, @@ -55,7 +55,7 @@ the average (arithmetic mean) of all input values - + bit_and(expression) smallint, int, bigint, or @@ -66,7 +66,7 @@ the bitwise AND of all non-null input values, or null if none - + bit_or(expression) smallint, int, bigint, or @@ -77,7 +77,7 @@ the bitwise OR of all non-null input values, or null if none - + bool_and(expression) bool @@ -87,7 +87,7 @@ true if all input values are true, otherwise false - + bool_or(expression) bool @@ -110,7 +110,7 @@ - + every(expression) bool @@ -162,7 +162,7 @@

Note

-

Boolean aggregates bool_and and +

Boolean aggregates bool_and and bool_or correspond to standard SQL aggregates every and any or some. @@ -198,7 +198,7 @@

Note

In all cases, null is returned if the computation is meaningless, for example when N is zero.

-
+

Table 9.38. Aggregate Functions for Statistics

@@ -215,7 +215,7 @@

Note

- - - - - - - - - - - @@ -59,7 +59,7 @@ get_bit(string, offset) @@ -69,7 +69,7 @@ get_byte(string, offset) @@ -94,7 +94,7 @@ offset, newvalue) @@ -105,7 +105,7 @@ offset, newvalue) @@ -114,7 +114,7 @@ @@ -195,8 +195,8 @@ diff --git a/docs/en_US/pg/functions-bitstring.html b/docs/en_US/pg/functions-bitstring.html index 36f848e5c2..12c13f24c5 100644 --- a/docs/en_US/pg/functions-bitstring.html +++ b/docs/en_US/pg/functions-bitstring.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.6. Bit String Functions and Operators

-

This section describes functions and operators for examining and +

This section describes functions and operators for examining and manipulating bit strings, that is values of the types bit and bit varying. Aside from the usual comparison operators, the operators diff --git a/docs/en_US/pg/functions-comparison.html b/docs/en_US/pg/functions-comparison.html index c835995a5c..99a27c288c 100644 --- a/docs/en_US/pg/functions-comparison.html +++ b/docs/en_US/pg/functions-comparison.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.2. Comparison Operators

-

The usual comparison operators are available, shown in Table 9.1, “Comparison Operators”. +

The usual comparison operators are available, shown in Table 9.1, “Comparison Operators”.

Table 9.1. Comparison Operators

@@ -70,7 +70,7 @@

Note

no < operator to compare a Boolean value with 3).

-

+

In addition to the comparison operators, the special BETWEEN construct is available.

@@ -91,15 +91,15 @@

Note

There is no difference between the two respective forms apart from the CPU cycles required to rewrite the first one into the second one internally. - + BETWEEN SYMMETRIC is the same as BETWEEN except there is no requirement that the argument to the left of AND be less than or equal to the argument on the right; the proper range is automatically determined.

-

- - - +

+ + + To check whether a value is or is not null, use the constructs 

expression IS NULL
@@ -110,7 +110,7 @@ 
Note

 
expression ISNULL
 expression NOTNULL

 

-    
+    
    

 
    Do not write
     expression = NULL
@@ -146,8 +146,8 @@ 
Note

     versions prior to 8.2.
-

- +

+ The ordinary comparison operators yield null (signifying “unknown”) when either input is null. Another way to do comparisons is with the IS [ NOT ] DISTINCT FROM construct: @@ -164,12 +164,12 @@

Note

one input is null. Thus, these constructs effectively act as though null were a normal data value, rather than “unknown”.

-

- - - - - +

+ + + + + Boolean values can also be tested using the constructs 

expression IS TRUE
diff --git a/docs/en_US/pg/functions-comparisons.html b/docs/en_US/pg/functions-comparisons.html
index 874d45235f..9323b2b5fc 100644
--- a/docs/en_US/pg/functions-comparisons.html
+++ b/docs/en_US/pg/functions-comparisons.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 9.17. Row and Array Comparisons

-
   This section describes several specialized constructs for making
+
   This section describes several specialized constructs for making
    multiple comparisons between groups of values.  These forms are
    syntactically related to the subquery forms of the previous section,
    but do not involve subqueries.
@@ -26,7 +26,7 @@
   

 

 

-9.17.1. IN

+9.17.1. IN
expression IN (value [, ...])

The right-hand side is a parenthesized list of scalar expressions. The result is “true” if the left-hand expression's @@ -50,7 +50,7 @@

-9.17.2. NOT IN

+9.17.2. NOT IN
expression NOT IN (value [, ...])

The right-hand side is a parenthesized list of scalar expressions. The result is “true” if the left-hand expression's @@ -83,7 +83,7 @@

Tip

-9.17.3. ANY/SOME (array)

+9.17.3. ANY/SOME (array)
expression operator ANY (array expression)
 expression operator SOME (array expression)

The right-hand side is a parenthesized expression, which must yield an @@ -111,7 +111,7 @@

Tip

-9.17.4. ALL (array)

+9.17.4. ALL (array)
expression operator ALL (array expression)

The right-hand side is a parenthesized expression, which must yield an array value. diff --git a/docs/en_US/pg/functions-conditional.html b/docs/en_US/pg/functions-conditional.html index 8b9583e421..bf75267d72 100644 --- a/docs/en_US/pg/functions-conditional.html +++ b/docs/en_US/pg/functions-conditional.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.13. Conditional Expressions

-

This section describes the SQL-compliant conditional expressions +

This section describes the SQL-compliant conditional expressions available in PostgreSQL.

@@ -26,7 +26,7 @@

Tip

-9.13.1. CASE

+9.13.1. CASE

The SQL CASE expression is a generic conditional expression, similar to if/else statements in other languages: @@ -125,8 +125,8 @@

Tip

-9.13.2. COALESCE

-
COALESCE(value [, ...])
+9.13.2. COALESCE
+
COALESCE(value [, ...])

The COALESCE function returns the first of its arguments that is not null. Null is returned only if all arguments are null. It is often used to substitute a default value for @@ -145,8 +145,8 @@

Tip

-9.13.3. NULLIF

-
NULLIF(value1, value2)
+9.13.3. NULLIF
+
NULLIF(value1, value2)

The NULLIF function returns a null value if value1 and value2 are equal; otherwise it returns value1. @@ -162,8 +162,8 @@

Tip

-9.13.4. GREATEST and LEAST

-
GREATEST(value [, ...])
+9.13.4. GREATEST and LEAST
+
GREATEST(value [, ...])
LEAST(value [, ...])

The GREATEST and LEAST functions select the largest or smallest value from a list of any number of expressions. diff --git a/docs/en_US/pg/functions-datetime.html b/docs/en_US/pg/functions-datetime.html index 154901931c..6749418540 100644 --- a/docs/en_US/pg/functions-datetime.html +++ b/docs/en_US/pg/functions-datetime.html @@ -5,7 +5,7 @@ - + @@ -142,7 +142,7 @@

+ corr(Y, , X) double precision @@ -225,7 +225,7 @@

Note

correlation coefficient
+ covar_pop(Y, , X) double precision @@ -235,7 +235,7 @@

Note

population covariance
+ covar_samp(Y, , X) double precision @@ -274,7 +274,7 @@

Note

number of input rows in which both expressions are nonnull
+ regr_intercept(Y, , X) double precision @@ -294,7 +294,7 @@

Note

square of the correlation coefficient
+ regr_slope(Y, , X) double precision @@ -340,7 +340,7 @@

Note

squares” of the dependent variable)
+ stddev(expression) smallint, int, @@ -354,7 +354,7 @@

Note
+ stddev_pop(expression) smallint, int, @@ -367,7 +367,7 @@

Note

population standard deviation of the input values
+ stddev_samp(expression) smallint, int, @@ -380,7 +380,7 @@

Note

sample standard deviation of the input values
+ variance(expression) smallint, int, @@ -394,7 +394,7 @@

Note
+ var_pop(expression) smallint, int, @@ -407,7 +407,7 @@

Note

population variance of the input values (square of the population standard deviation)
+ var_samp(expression) smallint, int, diff --git a/docs/en_US/pg/functions-array.html b/docs/en_US/pg/functions-array.html index 1e160e27a2..32acb69a2b 100644 --- a/docs/en_US/pg/functions-array.html +++ b/docs/en_US/pg/functions-array.html @@ -5,7 +5,7 @@ - + diff --git a/docs/en_US/pg/functions-binarystring.html b/docs/en_US/pg/functions-binarystring.html index e30f46bfdb..cab1925068 100644 --- a/docs/en_US/pg/functions-binarystring.html +++ b/docs/en_US/pg/functions-binarystring.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.5. Binary String Functions and Operators

-

This section describes functions and operators for examining and +

This section describes functions and operators for examining and manipulating values of type bytea.

SQL defines some string functions with a @@ -49,7 +49,7 @@ string

 bytea String concatenation - + '\\\\Post'::bytea || '\\047gres\\000'::bytea \\Post'gres\000 int Extract bit from string - + get_bit('Th\\000omas'::bytea, 45) 1 int Extract byte from string - + get_byte('Th\\000omas'::bytea, 4) 109 bytea Set bit in string - + set_bit('Th\\000omas'::bytea, 45, 0) Th\000omAs bytea Set byte in string - + set_byte('Th\\000omas'::bytea, 4, 64) Th\000o@assubstring(string [from int] [for int]) bytea Extract substring - + substring('Th\\000omas'::bytea from 2 for 3) h\000olength(string) int Length of binary string - - + + length('jo\\000se'::bytea) 5
-
+

Table 9.26. Date/Time Functions

@@ -385,7 +385,7 @@

9.9.1. EXTRACT, date_part

-
EXTRACT(field FROM source)
+
EXTRACT(field FROM source)

The extract function retrieves subfields such as year or hour from date/time values. source must be a value expression of @@ -541,7 +541,7 @@

second

The seconds field, including fractional parts (0 - - 59[5]) + 59[5]) 

SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
 Result: 40
@@ -611,7 +611,7 @@
 

 

 9.9.2. date_trunc

-
    The function date_trunc is conceptually
+
    The function date_trunc is conceptually
     similar to the trunc function for numbers.
    

 
date_trunc('field', source)

@@ -659,7 +659,7 @@
 

 

 9.9.3. AT TIME ZONE

-
    The AT TIME ZONE construct allows conversions
+
    The AT TIME ZONE construct allows conversions
     of time stamps to different time zones.  Table 9.27, “AT TIME ZONE Variants” shows its
     variants.
    

@@ -725,7 +725,7 @@
 

 

 9.9.4. Current Date/Time

-
    PostgreSQL provides a number of functions
+
    PostgreSQL provides a number of functions
     that return values related to the current date and time.  These
     SQL-standard functions all return values based on the start time of
     the current transaction:
@@ -844,7 +844,7 @@ 
Tip

 

 

 9.9.5. Delaying Execution

-
    The following function is available to delay execution of the server
+
    The following function is available to delay execution of the server
     process:
 

 
pg_sleep(seconds)

@@ -878,7 +878,7 @@ 
Warning

 

 

 

-
[5] 60 if leap seconds are
+
[5] 60 if leap seconds are
         implemented by the operating system

 

 

diff --git a/docs/en_US/pg/functions-formatting.html b/docs/en_US/pg/functions-formatting.html
index 05bcf8ce39..9a61b65644 100644
--- a/docs/en_US/pg/functions-formatting.html
+++ b/docs/en_US/pg/functions-formatting.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 9.8. Data Type Formatting Functions

-
    The PostgreSQL formatting functions
+
    The PostgreSQL formatting functions
     provide a powerful set of tools for converting various data types
     (date/time, integer, floating point, numeric) to formatted strings
     and for converting from formatted strings to specific data types.
diff --git a/docs/en_US/pg/functions-geometry.html b/docs/en_US/pg/functions-geometry.html
index 4ea490ccf2..70b18cf3a1 100644
--- a/docs/en_US/pg/functions-geometry.html
+++ b/docs/en_US/pg/functions-geometry.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -210,7 +210,7 @@ 
Note

      available, but are deprecated and will eventually be retired.
     

 

-

+

 
Table 9.29. Geometric Functions
diff --git a/docs/en_US/pg/functions-info.html b/docs/en_US/pg/functions-info.html index 18d54f6047..4bf0413f44 100644 --- a/docs/en_US/pg/functions-info.html +++ b/docs/en_US/pg/functions-info.html @@ -5,7 +5,7 @@ - + @@ -106,7 +106,7 @@
-

The session_user is normally the user who initiated +

The session_user is normally the user who initiated the current database connection; but superusers can change this setting with SET SESSION AUTHORIZATION. The current_user is the user identifier @@ -142,7 +142,7 @@

Note

-

inet_client_addr returns the IP address of the +

inet_client_addr returns the IP address of the current client, and inet_client_port returns the port number. inet_server_addr returns the IP address on which @@ -151,7 +151,7 @@

Note

All these functions return NULL if the current connection is via a Unix-domain socket.

-

pg_my_temp_schema returns the OID of the current +

pg_my_temp_schema returns the OID of the current session's temporary schema, or 0 if it has none (because it has not created any temporary tables). pg_is_other_temp_schema returns true if the @@ -159,14 +159,14 @@

Note

(This can be useful, for example, to exclude other sessions' temporary tables from a catalog display.)

-

pg_postmaster_start_time returns the +

pg_postmaster_start_time returns the timestamp with time zone when the server started.

-

version returns a string describing the +

version returns a string describing the PostgreSQL server's version.

-

Table 9.41, “Access Privilege Inquiry Functions” lists functions that +

Table 9.41, “Access Privilege Inquiry Functions” lists functions that allow the user to query object access privileges programmatically. See Section 5.6, “Privileges” for more information about privileges. @@ -307,7 +307,7 @@

Note

-

has_database_privilege checks whether a user +

has_database_privilege checks whether a user can access a database in a particular way. The possibilities for its arguments are analogous to has_table_privilege. The desired access privilege type must evaluate to @@ -456,7 +456,7 @@

Note

-

pg_conversion_is_visible, +

pg_conversion_is_visible, pg_function_is_visible, pg_operator_is_visible, pg_opclass_is_visible, @@ -480,7 +480,7 @@

Note

Note that it would not make much sense to test an unqualified name in this way — if the name can be recognized at all, it must be visible.

-

Table 9.43, “System Catalog Information Functions” lists functions that +

Table 9.43, “System Catalog Information Functions” lists functions that extract information from the system catalogs.

@@ -633,7 +633,7 @@

Note

pg_tablespace_databases and query their pg_class catalogs.

-

The functions shown in Table 9.44, “Comment Information Functions” +

The functions shown in Table 9.44, “Comment Information Functions” extract comments previously stored with the COMMENT command. A null value is returned if no comment could be found matching the specified parameters.

diff --git a/docs/en_US/pg/functions-matching.html b/docs/en_US/pg/functions-matching.html index e6d41a468e..94f9308921 100644 --- a/docs/en_US/pg/functions-matching.html +++ b/docs/en_US/pg/functions-matching.html @@ -5,7 +5,7 @@ - + @@ -14,7 +14,7 @@

9.7. Pattern Matching

-

There are three separate approaches to pattern matching provided +

There are three separate approaches to pattern matching provided by PostgreSQL: the traditional SQL LIKE operator, the more recent SIMILAR TO operator (added in @@ -34,7 +34,7 @@

Tip

9.7.1. LIKE

-
string LIKE pattern [ESCAPE escape-character]
+
string LIKE pattern [ESCAPE escape-character]
 string NOT LIKE pattern [ESCAPE escape-character]

 
     Every pattern defines a set of strings.
      The LIKE expression returns true if the
@@ -105,7 +105,7 @@ 
Tip

 

 

 9.7.2. SIMILAR TO Regular Expressions

-
string SIMILAR TO pattern [ESCAPE escape-character]
+
string SIMILAR TO pattern [ESCAPE escape-character]
 string NOT SIMILAR TO pattern [ESCAPE escape-character]

 
     The SIMILAR TO operator returns true or
      false depending on whether its pattern matches the given string.
@@ -188,7 +188,7 @@ 
Tip

 

 

 9.7.3. POSIX Regular Expressions

-
    Table 9.11, “Regular Expression Match Operators” lists the available
+
    Table 9.11, “Regular Expression Match Operators” lists the available
     operators for pattern matching using POSIX regular expressions.
    

 

diff --git a/docs/en_US/pg/functions-math.html b/docs/en_US/pg/functions-math.html
index 47f3627fd2..b3110d58a4 100644
--- a/docs/en_US/pg/functions-math.html
+++ b/docs/en_US/pg/functions-math.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -159,7 +159,7 @@
    implemented on top of the host system's C library; accuracy and behavior in
    boundary cases may therefore vary depending on the host system.
   

-

+

 
Table 9.3. Mathematical Functions

 
@@ -366,7 +366,7 @@
    take arguments and return values of type double
    precision.
   

-

+

 
Table 9.4. Trigonometric Functions

 

 

diff --git a/docs/en_US/pg/functions-net.html b/docs/en_US/pg/functions-net.html
index 98231dbd4a..dcc8ee4be1 100644
--- a/docs/en_US/pg/functions-net.html
+++ b/docs/en_US/pg/functions-net.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/functions-sequence.html b/docs/en_US/pg/functions-sequence.html
index 6300354e1f..ae9bd4af9a 100644
--- a/docs/en_US/pg/functions-sequence.html
+++ b/docs/en_US/pg/functions-sequence.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 

 

 9.12. Sequence Manipulation Functions

-
   This section describes PostgreSQL's functions
+
   This section describes PostgreSQL's functions
    for operating on sequence objects.
    Sequence objects (also called sequence generators or
    just sequences) are special single-row tables created with
diff --git a/docs/en_US/pg/functions-srf.html b/docs/en_US/pg/functions-srf.html
index 396349457c..8a35f9376e 100644
--- a/docs/en_US/pg/functions-srf.html
+++ b/docs/en_US/pg/functions-srf.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 9.18. Set Returning Functions

-
   This section describes functions that possibly return more than one row.
+
   This section describes functions that possibly return more than one row.
    Currently the only functions in this class are series generating functions,
    as detailed in Table 9.39, “Series Generating Functions”.
   

diff --git a/docs/en_US/pg/functions-string.html b/docs/en_US/pg/functions-string.html
index 3f32aeb122..59b28859d4 100644
--- a/docs/en_US/pg/functions-string.html
+++ b/docs/en_US/pg/functions-string.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -31,7 +31,7 @@
     These functions are also implemented using the regular syntax for
     function invocation.  (See Table 9.6, “Other String Functions”.)
    

-

+

 
Table 9.5. SQL String Functions and Operators

 

 

 
 
 
 
 
 
 
 
 
 
@@ -54,7 +54,7 @@
         string
@@ -72,8 +72,8 @@
 
@@ -175,7 +175,7 @@
     listed in Table 9.6, “Other String Functions”.  Some of them are used internally to implement the
     SQL-standard string functions listed in Table 9.5, “SQL String Functions and Operators”.
    

-

+

 
Table 9.6. Other String Functions

 

 

 
 text 
         String concatenation
-        
+        
        
 'Post' || 'greSQL'
 PostgreSQL
 int
         Number of characters in string
-        
-        
+        
+        
        
 char_length('jose')
 4
@@ -479,7 +479,7 @@
 
@@ -1086,7 +1086,7 @@
 
-
-
+
diff --git a/docs/en_US/pg/runtime-config-preset.html b/docs/en_US/pg/runtime-config-preset.html
index f0c7da62dd..0bee706d1e 100644
--- a/docs/en_US/pg/runtime-config-preset.html
+++ b/docs/en_US/pg/runtime-config-preset.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/runtime-config-query.html b/docs/en_US/pg/runtime-config-query.html
index 0a42212d2e..4c475b258e 100644
--- a/docs/en_US/pg/runtime-config-query.html
+++ b/docs/en_US/pg/runtime-config-query.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/runtime-config-resource.html b/docs/en_US/pg/runtime-config-resource.html
index bf0dcab284..a95cc89100 100644
--- a/docs/en_US/pg/runtime-config-resource.html
+++ b/docs/en_US/pg/runtime-config-resource.html
@@ -5,7 +5,7 @@
 
-
+
@@ -147,7 +147,7 @@
 

 

 17.4.2. Free Space Map

-
      These parameters control the size of the shared free space
+
      These parameters control the size of the shared free space
       map, which tracks the locations of unused space in the database.
       An undersized free space map may cause the database to consume
       increasing amounts of disk space over time, because free space that
diff --git a/docs/en_US/pg/runtime-config-short.html b/docs/en_US/pg/runtime-config-short.html
index 585bdde17a..98befcf669 100644
--- a/docs/en_US/pg/runtime-config-short.html
+++ b/docs/en_US/pg/runtime-config-short.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-statistics.html b/docs/en_US/pg/runtime-config-statistics.html
index a86ad90436..a8a4505562 100644
--- a/docs/en_US/pg/runtime-config-statistics.html
+++ b/docs/en_US/pg/runtime-config-statistics.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-wal.html b/docs/en_US/pg/runtime-config-wal.html
index 3d54f21dc8..94af613eac 100644
--- a/docs/en_US/pg/runtime-config-wal.html
+++ b/docs/en_US/pg/runtime-config-wal.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config.html b/docs/en_US/pg/runtime-config.html
index 7f442aeeb1..ac94098095 100644
--- a/docs/en_US/pg/runtime-config.html
+++ b/docs/en_US/pg/runtime-config.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -77,7 +77,7 @@
 
17.16. Short Options

 
 

-
   There are many configuration parameters that affect the behavior of
+
   There are many configuration parameters that affect the behavior of
    the database system. In the first section of this chapter, we
    describe how to set configuration parameters. The subsequent sections
    discuss each parameter in detail.
@@ -106,7 +106,7 @@
     memory units is 1024, not 1000.
    

 
    One way to set these parameters is to edit the file
-    postgresql.conf,
+    postgresql.conf,
     which is normally kept in the data directory. (initdb
     installs a default copy there.) An example of what this file might look
     like is:
@@ -124,7 +124,7 @@
     numbers must be single-quoted.  To embed a single quote in a parameter
     value, write either two quotes (preferred) or backslash-quote.
    

-
    
+
    
     In addition to parameter settings, the postgresql.conf
     file can contain include directives, which specify
     another file to read and process as if it were inserted into the
@@ -136,7 +136,7 @@
     the directory containing the referencing configuration file.
     Inclusions can be nested.
    

-
    
+
    
     The configuration file is reread whenever the main server process receives a
     SIGHUP signal (which is most easily sent by means
     of pg_ctl reload). The main server process
diff --git a/docs/en_US/pg/runtime.html b/docs/en_US/pg/runtime.html
index c152937b2f..8a1b476104 100644
--- a/docs/en_US/pg/runtime.html
+++ b/docs/en_US/pg/runtime.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -27,8 +27,8 @@
 
16.4. Managing Kernel Resources

 

 
16.4.1. Shared Memory and Semaphores

-
16.4.2. Resource Limits

-
16.4.3. Linux Memory Overcommit

+
16.4.2. Resource Limits

+
16.4.3. Linux Memory Overcommit

 

 
16.5. Shutting Down the Server

 
16.6. Encryption Options

@@ -42,7 +42,7 @@
 

 

 16.1. The PostgreSQL User Account

-
   As with any other server daemon that is accessible to the outside world,
+
   As with any other server daemon that is accessible to the outside world,
    it is advisable to run PostgreSQL under a
    separate user account. This user account should only own the data
    that is managed by the server, and should not be shared with other
diff --git a/docs/en_US/pg/server-programming.html b/docs/en_US/pg/server-programming.html
index 30da7afdaa..f82a3f5d7e 100644
--- a/docs/en_US/pg/server-programming.html
+++ b/docs/en_US/pg/server-programming.html
@@ -5,8 +5,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -14,7 +14,7 @@
 

 

 Part V. Server Programming

-

+

 

 
    This part is about extending the server functionality with
     user-defined functions, data types, triggers, etc.  These are
@@ -35,21 +35,21 @@
 
33.1. How Extensibility Works

 
33.2. The PostgreSQL Type System

 

-
33.2.1. Base Types

-
33.2.2. Composite Types

-
33.2.3. Domains

-
33.2.4. Pseudo-Types

+
33.2.1. Base Types

+
33.2.2. Composite Types

+
33.2.3. Domains

+
33.2.4. Pseudo-Types

 
33.2.5. Polymorphic Types

 

 
33.3. User-Defined Functions

 
33.4. Query Language (SQL) Functions

 

 
33.4.1. SQL Functions on Base Types

-
33.4.2. SQL Functions on Composite Types

+
33.4.2. SQL Functions on Composite Types

 
33.4.3. Functions with Output Parameters

 
33.4.4. SQL Functions as Table Sources

-
33.4.5. SQL Functions Returning Sets

-
33.4.6. Polymorphic SQL Functions

+
33.4.5. SQL Functions Returning Sets

+
33.4.6. Polymorphic SQL Functions

 

 
33.5. Function Overloading

 
33.6. Function Volatility Categories

@@ -59,28 +59,28 @@
 

 
33.9.1. Dynamic Loading

 
33.9.2. Base Types in C-Language Functions

-
33.9.3. Version 0 Calling Conventions

-
33.9.4. Version 1 Calling Conventions

-
33.9.5. Writing Code

+
33.9.3. Version 0 Calling Conventions

+
33.9.4. Version 1 Calling Conventions

+
33.9.5. Writing Code

 
33.9.6. Compiling and Linking Dynamically-Loaded Functions

 
33.9.7. Extension Building Infrastructure

-
33.9.8. Composite-Type Arguments

-
33.9.9. Returning Rows (Composite Types)

+
33.9.8. Composite-Type Arguments

+
33.9.9. Returning Rows (Composite Types)

 
33.9.10. Returning Sets

-
33.9.11. Polymorphic Arguments and Return Types

-
33.9.12. Shared Memory and LWLocks

+
33.9.11. Polymorphic Arguments and Return Types

+
33.9.12. Shared Memory and LWLocks

 

 
33.10. User-Defined Aggregates

 
33.11. User-Defined Types

 
33.12. User-Defined Operators

 
33.13. Operator Optimization Information

 

-
33.13.1. COMMUTATOR

-
33.13.2. NEGATOR

-
33.13.3. RESTRICT

-
33.13.4. JOIN

-
33.13.5. HASHES

-
33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)

+
33.13.1. COMMUTATOR

+
33.13.2. NEGATOR

+
33.13.3. RESTRICT

+
33.13.4. JOIN

+
33.13.5. HASHES

+
33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)

 

 
33.14. Interfacing Extensions To Indexes

 

@@ -106,13 +106,13 @@
 
35.2. Views and the Rule System

 

 
35.2.1. How SELECT Rules Work

-
35.2.2. View Rules in Non-SELECT Statements

-
35.2.3. The Power of Views in PostgreSQL

+
35.2.2. View Rules in Non-SELECT Statements

+
35.2.3. The Power of Views in PostgreSQL

 
35.2.4. Updating a View

 

 
35.3. Rules on INSERT, UPDATE, and DELETE

 

-
35.3.1. How Update Rules Work

+
35.3.1. How Update Rules Work

 
35.3.2. Cooperation with Views

 

 
35.4. Rules and Privileges

@@ -167,7 +167,7 @@
 
37.10. Trigger Procedures

 
37.11. Porting from Oracle PL/SQL

 

-
37.11.1. Porting Examples

+
37.11.1. Porting Examples

 
37.11.2. Other Things to Watch For

 
37.11.3. Appendix

 

diff --git a/docs/en_US/pg/server-shutdown.html b/docs/en_US/pg/server-shutdown.html
index dbc358a708..319b407d1a 100644
--- a/docs/en_US/pg/server-shutdown.html
+++ b/docs/en_US/pg/server-shutdown.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,27 +14,27 @@
 

 

 16.5. Shutting Down the Server

-
   There are several ways to shut down the database server. You control
+
   There are several ways to shut down the database server. You control
    the type of shutdown by sending different signals to the master
    postgres process.
 
    

 

-
SIGTERM

+
SIGTERM

 
       After receiving SIGTERM, the server
        disallows new connections, but lets existing sessions end their
        work normally. It shuts down only after all of the sessions
        terminate normally. This is the Smart
        Shutdown.
       

-
SIGINT

+
SIGINT

 
       The server disallows new connections and sends all existing
        server processes SIGTERM, which will cause them
        to abort their current transactions and exit promptly. It then
        waits for the server processes to exit and finally shuts down. This is the
        Fast Shutdown.
       

-
SIGQUIT

+
SIGQUIT

 
      This is the Immediate Shutdown, which
       will cause the master postgres process to send a
       SIGQUIT to all child processes and exit
diff --git a/docs/en_US/pg/server-start.html b/docs/en_US/pg/server-start.html
index f78df2556f..df89a353bd 100644
--- a/docs/en_US/pg/server-start.html
+++ b/docs/en_US/pg/server-start.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -16,7 +16,7 @@
 16.3. Starting the Database Server

 
   Before anyone can access the database, you must start the database
    server. The database server program is called
-   postgres.
+   postgres.
    The postgres program must know where to
    find the data it is supposed to use. This is done with the
    -D option. Thus, the simplest way to start the
@@ -47,7 +47,7 @@
   

 
   This shell syntax can get tedious quickly.  Therefore the wrapper
    program
-   pg_ctl
+   pg_ctl
    is provided to simplify some tasks.  For example:
 

 
pg_ctl start -l logfile

@@ -58,7 +58,7 @@
    is also capable of stopping the server.
   

 
   Normally, you will want to start the database server when the
-   computer boots. Autostart scripts are operating-system-specific.
+   computer boots. Autostart scripts are operating-system-specific.
    There are a few distributed with
    PostgreSQL in the
    contrib/start-scripts directory. Installing one will require
@@ -86,12 +86,12 @@
 
  •       For FreeBSD, look at the file
       contrib/start-scripts/freebsd in the
       PostgreSQL source distribution.
-      
+      
      
    • 
 
  • 
 
          On OpenBSD, add the following lines
       to the file /etc/rc.local:
-      
+      
 
    
 
    if [ -x /usr/local/pgsql/bin/pg_ctl -a -x /usr/local/pgsql/bin/postgres ]; then
     su - -c '/usr/local/pgsql/bin/pg_ctl start -l /var/postgresql/log -s' postgres
@@ -102,7 +102,7 @@
 
    • 
 
  • 
 
          On Linux systems either add
-      
+      
 
    
 
    /usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data
    
 
    
@@ -114,13 +114,13 @@
 
  •       On NetBSD, either use the
       FreeBSD or
       Linux start scripts, depending on
-      preference. 
+      preference. 
      
    • 
 
  • 
 
          On Solaris, create a file called
       /etc/init.d/postgresql that contains
       the following line:
-      
+      
 
    
 
    su - postgres -c "/usr/local/pgsql/bin/pg_ctl start -l logfile -D /usr/local/pgsql/data"
    
 
    
diff --git a/docs/en_US/pg/source.html b/docs/en_US/pg/source.html
index 145ee54a38..f8d5978f21 100644
--- a/docs/en_US/pg/source.html
+++ b/docs/en_US/pg/source.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/spi-examples.html b/docs/en_US/pg/spi-examples.html
index f734a2bd56..94783f949d 100644
--- a/docs/en_US/pg/spi-examples.html
+++ b/docs/en_US/pg/spi-examples.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/spi-interface-support.html b/docs/en_US/pg/spi-interface-support.html
index 8d9bcee282..fd6760bcfb 100644
--- a/docs/en_US/pg/spi-interface-support.html
+++ b/docs/en_US/pg/spi-interface-support.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/spi-memory.html b/docs/en_US/pg/spi-memory.html
index 3bfc53d9fc..6ea05f4679 100644
--- a/docs/en_US/pg/spi-memory.html
+++ b/docs/en_US/pg/spi-memory.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -15,7 +15,7 @@
 
    
 41.3. Memory Management
    
 
       PostgreSQL allocates memory within
-   memory contexts, which provide a convenient method of
+   memory contexts, which provide a convenient method of
    managing allocations made in many different places that need to
    live for differing amounts of time.  Destroying a context releases
    all the memory that was allocated in it.  Thus, it is not necessary
diff --git a/docs/en_US/pg/spi-realloc.html b/docs/en_US/pg/spi-realloc.html
index 46bd71aa50..732f72845e 100644
--- a/docs/en_US/pg/spi-realloc.html
+++ b/docs/en_US/pg/spi-realloc.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_repalloc — reallocate memory in the upper executor context
    
 
    • 
-
    
+
    
 
    Synopsis
    
 
    void * SPI_repalloc(void * pointer, Size size)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_repalloc changes the size of a memory
    segment previously allocated using SPI_palloc.
   
    
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * pointer
    
 
          pointer to existing storage to change
@@ -43,7 +43,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       pointer to new storage space of specified size with the contents
    copied from the existing area
   
    
diff --git a/docs/en_US/pg/spi-spi-connect.html b/docs/en_US/pg/spi-spi-connect.html
index 065408b2c6..84a6890c08 100644
--- a/docs/en_US/pg/spi-spi-connect.html
+++ b/docs/en_US/pg/spi-spi-connect.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_connect — connect a procedure to the SPI manager
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_connect(void)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_connect opens a connection from a
    procedure invocation to the SPI manager.  You must call this
    function if you want to execute commands through SPI.  Some utility
@@ -43,7 +43,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
    
 
    SPI_OK_CONNECT
    
 
          on success
diff --git a/docs/en_US/pg/spi-spi-copytuple.html b/docs/en_US/pg/spi-spi-copytuple.html
index f970acc47a..148a941641 100644
--- a/docs/en_US/pg/spi-spi-copytuple.html
+++ b/docs/en_US/pg/spi-spi-copytuple.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_copytuple — make a copy of a row in the upper executor context
    
 
    
-
    
+
    
 
    Synopsis
    
 
    HeapTuple SPI_copytuple(HeapTuple row)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_copytuple makes a copy of a row in the
    upper executor context.  This is normally used to return a modified
    row from a trigger.  In a function declared to return a composite
@@ -30,7 +30,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    HeapTuple row
    
 
          row to be copied
@@ -38,7 +38,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       the copied row; NULL only if
    tuple is NULL
   
    
diff --git a/docs/en_US/pg/spi-spi-cursor-close.html b/docs/en_US/pg/spi-spi-cursor-close.html
index 2241af1d9e..62b15250ba 100644
--- a/docs/en_US/pg/spi-spi-cursor-close.html
+++ b/docs/en_US/pg/spi-spi-cursor-close.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_cursor_close — close a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_cursor_close(Portal portal)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_cursor_close closes a previously created
    cursor and releases its portal storage.
   
    
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Portal portal
    
 
          portal containing the cursor
diff --git a/docs/en_US/pg/spi-spi-cursor-fetch.html b/docs/en_US/pg/spi-spi-cursor-fetch.html
index 6d073c7910..d7fd89442c 100644
--- a/docs/en_US/pg/spi-spi-cursor-fetch.html
+++ b/docs/en_US/pg/spi-spi-cursor-fetch.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    SPI_cursor_fetch — fetch some rows from a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_cursor_fetch(Portal portal, bool forward, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_cursor_fetch fetches some rows from a
    cursor.  This is equivalent to the SQL command FETCH.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Portal portal
    
 
          portal containing the cursor
@@ -42,7 +42,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       SPI_processed and
    SPI_tuptable are set as in
    SPI_execute if successful.
diff --git a/docs/en_US/pg/spi-spi-cursor-find.html b/docs/en_US/pg/spi-spi-cursor-find.html
index ee7ae461a3..86f4d41643 100644
--- a/docs/en_US/pg/spi-spi-cursor-find.html
+++ b/docs/en_US/pg/spi-spi-cursor-find.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_cursor_find — find an existing cursor by name
    
 
    
-
    
+
    
 
    Synopsis
    
 
    Portal SPI_cursor_find(const char * name)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_cursor_find finds an existing portal by
    name.  This is primarily useful to resolve a cursor name returned
    as text by some other function.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    const char * name
    
 
          name of the portal
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       pointer to the portal with the specified name, or
    NULL if none was found
   
    
diff --git a/docs/en_US/pg/spi-spi-cursor-move.html b/docs/en_US/pg/spi-spi-cursor-move.html
index 3db4cbd798..4a8a6be2aa 100644
--- a/docs/en_US/pg/spi-spi-cursor-move.html
+++ b/docs/en_US/pg/spi-spi-cursor-move.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_cursor_move — move a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_cursor_move(Portal portal, bool forward, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_cursor_move skips over some number of rows
    in a cursor.  This is equivalent to the SQL command
    MOVE.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Portal portal
    
 
          portal containing the cursor
diff --git a/docs/en_US/pg/spi-spi-cursor-open.html b/docs/en_US/pg/spi-spi-cursor-open.html
index bc6832420a..52f363baed 100644
--- a/docs/en_US/pg/spi-spi-cursor-open.html
+++ b/docs/en_US/pg/spi-spi-cursor-open.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    SPI_cursor_open — set up a cursor using a plan created with SPI_prepare
    
 
    
-
    
+
    
 
    Synopsis
    
 
    Portal SPI_cursor_open(const char * name, void * plan,
                        Datum * values, const char * nulls,
                        bool read_only)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_cursor_open sets up a cursor (internally,
    a portal) that will execute a plan prepared by
    SPI_prepare.  The parameters have the same
@@ -41,7 +41,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    const char * name
    
 
          name for portal, or NULL to let the system
@@ -73,7 +73,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       pointer to portal containing the cursor, or NULL
    on error
   
    
diff --git a/docs/en_US/pg/spi-spi-exec.html b/docs/en_US/pg/spi-spi-exec.html
index dc509aff57..d24d2d7e1d 100644
--- a/docs/en_US/pg/spi-spi-exec.html
+++ b/docs/en_US/pg/spi-spi-exec.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_exec — execute a read/write command
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_exec(const char * command, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_exec is the same as
    SPI_execute, with the latter's
    read_only parameter always taken as
@@ -30,7 +30,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    const char * command
    
 
          string containing command to execute
@@ -41,7 +41,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       See SPI_execute.
   
    
 
    
diff --git a/docs/en_US/pg/spi-spi-execp.html b/docs/en_US/pg/spi-spi-execp.html
index d1e0f60201..052e65a1a4 100644
--- a/docs/en_US/pg/spi-spi-execp.html
+++ b/docs/en_US/pg/spi-spi-execp.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_execp — execute a plan in read/write mode
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_execp(void * plan, Datum * values, const char * nulls, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_execp is the same as
    SPI_execute_plan, with the latter's
    read_only parameter always taken as
@@ -30,7 +30,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          execution plan (returned by SPI_prepare)
@@ -58,7 +58,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       See SPI_execute_plan.
   
    
 
       SPI_processed and
diff --git a/docs/en_US/pg/spi-spi-execute-plan.html b/docs/en_US/pg/spi-spi-execute-plan.html
index 22de61a4d7..ecb5530c3e 100644
--- a/docs/en_US/pg/spi-spi-execute-plan.html
+++ b/docs/en_US/pg/spi-spi-execute-plan.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    SPI_execute_plan — execute a plan prepared by SPI_prepare
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_execute_plan(void * plan, Datum * values, const char * nulls,
                      bool read_only, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_execute_plan executes a plan prepared by
    SPI_prepare.  read_only and
    count have the same interpretation as in
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          execution plan (returned by SPI_prepare)
@@ -62,7 +62,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The return value is the same as for SPI_execute,
    with the following additional possible error (negative) results:
 
@@ -85,7 +85,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       If one of the objects (a table, function, etc.) referenced by the
    prepared plan is dropped during the session then the result of
    SPI_execute_plan for this plan will be unpredictable.
diff --git a/docs/en_US/pg/spi-spi-execute.html b/docs/en_US/pg/spi-spi-execute.html
index 740b918faf..cfcdf972b4 100644
--- a/docs/en_US/pg/spi-spi-execute.html
+++ b/docs/en_US/pg/spi-spi-execute.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_execute — execute a command
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_execute(const char * command, bool read_only, long count)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_execute executes the specified SQL command
    for count rows.  If read_only
    is true, the command must be read-only, and execution overhead
@@ -109,7 +109,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    const char * command
    
 
          string containing command to execute
@@ -123,7 +123,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       If the execution of the command was successful then one of the
    following (nonnegative) values will be returned:
 
@@ -199,7 +199,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       The functions SPI_execute,
    SPI_exec,
    SPI_execute_plan, and
diff --git a/docs/en_US/pg/spi-spi-finish.html b/docs/en_US/pg/spi-spi-finish.html
index af6cd844e9..46298882fa 100644
--- a/docs/en_US/pg/spi-spi-finish.html
+++ b/docs/en_US/pg/spi-spi-finish.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_finish — disconnect a procedure from the SPI manager
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_finish(void)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_finish closes an existing connection to
    the SPI manager.  You must call this function after completing the
    SPI operations needed during your procedure's current invocation.
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
    
 
    SPI_OK_FINISH
    
 
          if properly disconnected
diff --git a/docs/en_US/pg/spi-spi-fname.html b/docs/en_US/pg/spi-spi-fname.html
index 6c597cb193..75b5f184e2 100644
--- a/docs/en_US/pg/spi-spi-fname.html
+++ b/docs/en_US/pg/spi-spi-fname.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_fname — determine the column name for the specified column number
    
 
    
-
    
+
    
 
    Synopsis
    
 
    char * SPI_fname(TupleDesc rowdesc, int colnumber)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_fname returns a copy of the column name of the
    specified column.  (You can use pfree to
    release the copy of the name when you don't need it anymore.)
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    TupleDesc rowdesc
    
 
          input row description
@@ -40,7 +40,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The column name; NULL if
    colnumber is out of range.
    SPI_result set to
diff --git a/docs/en_US/pg/spi-spi-fnumber.html b/docs/en_US/pg/spi-spi-fnumber.html
index b2d472422b..6078b7cbec 100644
--- a/docs/en_US/pg/spi-spi-fnumber.html
+++ b/docs/en_US/pg/spi-spi-fnumber.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_fnumber — determine the column number for the specified column name
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_fnumber(TupleDesc rowdesc, const char * colname)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_fnumber returns the column number for the
    column with the specified name.
   
    
@@ -35,7 +35,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    TupleDesc rowdesc
    
 
          input row description
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       Column number (count starts at 1), or
    SPI_ERROR_NOATTRIBUTE if the named column was not
    found.
diff --git a/docs/en_US/pg/spi-spi-freeplan.html b/docs/en_US/pg/spi-spi-freeplan.html
index 2119600d40..6c76369935 100644
--- a/docs/en_US/pg/spi-spi-freeplan.html
+++ b/docs/en_US/pg/spi-spi-freeplan.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_freeplan — free a previously saved plan
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_freeplan(void *plan)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_freeplan releases a command execution plan
    previously returned by SPI_prepare or saved by
    SPI_saveplan.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          pointer to plan to free
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       SPI_ERROR_ARGUMENT if plan
    is NULL.
   
    
diff --git a/docs/en_US/pg/spi-spi-freetuple.html b/docs/en_US/pg/spi-spi-freetuple.html
index a06b38aa54..a7373c1536 100644
--- a/docs/en_US/pg/spi-spi-freetuple.html
+++ b/docs/en_US/pg/spi-spi-freetuple.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_freetuple — free a row allocated in the upper executor context
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_freetuple(HeapTuple row)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_freetuple frees a row previously allocated
    in the upper executor context.
   
    
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    HeapTuple row
    
 
          row to free
diff --git a/docs/en_US/pg/spi-spi-freetupletable.html b/docs/en_US/pg/spi-spi-freetupletable.html
index 25a986335c..1184c379a5 100644
--- a/docs/en_US/pg/spi-spi-freetupletable.html
+++ b/docs/en_US/pg/spi-spi-freetupletable.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,12 +18,12 @@ 
    Name
    
 
    SPI_freetuptable — free a row set created by SPI_execute or a similar
   function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_freetuptable(SPITupleTable * tuptable)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_freetuptable frees a row set created by a
    prior SPI command execution function, such as
    SPI_execute.  Therefore, this function is usually called
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    SPITupleTable * tuptable
    
 
          pointer to row set to free
diff --git a/docs/en_US/pg/spi-spi-getargcount.html b/docs/en_US/pg/spi-spi-getargcount.html
index e110c82440..9c7847a215 100644
--- a/docs/en_US/pg/spi-spi-getargcount.html
+++ b/docs/en_US/pg/spi-spi-getargcount.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,18 +18,18 @@ 
    Name
    
 
    SPI_getargcount — return the number of arguments needed by a plan
   prepared by SPI_prepare
    
 
    
-
    
+
    
 
    Synopsis
    
 
    int SPI_getargcount(void * plan)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getargcount returns the number of arguments needed
    to execute a plan prepared by SPI_prepare.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          execution plan (returned by SPI_prepare)
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
        The expected argument count for the plan, or
     SPI_ERROR_ARGUMENT if the plan
      is NULL
diff --git a/docs/en_US/pg/spi-spi-getargtypeid.html b/docs/en_US/pg/spi-spi-getargtypeid.html
index 95accd56cd..960e10a801 100644
--- a/docs/en_US/pg/spi-spi-getargtypeid.html
+++ b/docs/en_US/pg/spi-spi-getargtypeid.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,19 +18,19 @@ 
    Name
    
 
    SPI_getargtypeid — return the data type OID for an argument of
   a plan prepared by SPI_prepare
    
 
    
-
    
+
    
 
    Synopsis
    
 
    Oid SPI_getargtypeid(void * plan, int argIndex)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getargtypeid returns the OID representing the type
    id for the argIndex'th argument of a plan prepared by
    SPI_prepare. First argument is at index zero.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          execution plan (returned by SPI_prepare)
@@ -41,7 +41,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
        The type id of the argument at the given index, or
     SPI_ERROR_ARGUMENT if the plan is
     NULL or argIndex is less than 0 or
diff --git a/docs/en_US/pg/spi-spi-getbinval.html b/docs/en_US/pg/spi-spi-getbinval.html
index a29240bfbd..c2e76ffb7f 100644
--- a/docs/en_US/pg/spi-spi-getbinval.html
+++ b/docs/en_US/pg/spi-spi-getbinval.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_getbinval — return the binary value of the specified column
    
 
    
-
    
+
    
 
    Synopsis
    
 
    Datum SPI_getbinval(HeapTuple row, TupleDesc rowdesc, int colnumber, bool * isnull)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getbinval returns the value of the
    specified column in the internal form (as type Datum).
   
    
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    HeapTuple row
    
 
          input row to be examined
@@ -49,7 +49,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The binary value of the column is returned.  The variable pointed
    to by isnull is set to true if the column is
    null, else to false.
diff --git a/docs/en_US/pg/spi-spi-getnspname.html b/docs/en_US/pg/spi-spi-getnspname.html
index d0c72cd50a..c44b64c5ed 100644
--- a/docs/en_US/pg/spi-spi-getnspname.html
+++ b/docs/en_US/pg/spi-spi-getnspname.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_getnspname — return the namespace of the specified relation
    
 
    
-
    
+
    
 
    Synopsis
    
 
    char * SPI_getnspname(Relation rel)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getnspname returns a copy of the name of
    the namespace that the specified Relation
    belongs to. This is equivalent to the relation's schema. You should
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Relation rel
    
 
          input relation
@@ -39,7 +39,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The name of the specified relation's namespace.
   
    
 
    
diff --git a/docs/en_US/pg/spi-spi-getrelname.html b/docs/en_US/pg/spi-spi-getrelname.html
index daad34f85d..fd24d1d645 100644
--- a/docs/en_US/pg/spi-spi-getrelname.html
+++ b/docs/en_US/pg/spi-spi-getrelname.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_getrelname — return the name of the specified relation
    
 
    
-
    
+
    
 
    Synopsis
    
 
    char * SPI_getrelname(Relation rel)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getrelname returns a copy of the name of the
    specified relation.  (You can use pfree to
    release the copy of the name when you don't need it anymore.)
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Relation rel
    
 
          input relation
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The name of the specified relation.
   
    
 
    
diff --git a/docs/en_US/pg/spi-spi-gettype.html b/docs/en_US/pg/spi-spi-gettype.html
index 4b41042b73..ca2d58ba7b 100644
--- a/docs/en_US/pg/spi-spi-gettype.html
+++ b/docs/en_US/pg/spi-spi-gettype.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_gettype — return the data type name of the specified column
    
 
    
-
    
+
    
 
    Synopsis
    
 
    char * SPI_gettype(TupleDesc rowdesc, int colnumber)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_gettype returns a copy of the data type name of the
    specified column.  (You can use pfree to
    release the copy of the name when you don't need it anymore.)
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    TupleDesc rowdesc
    
 
          input row description
@@ -40,7 +40,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The data type name of the specified column, or
    NULL on error.  SPI_result is
    set to SPI_ERROR_NOATTRIBUTE on error.
diff --git a/docs/en_US/pg/spi-spi-gettypeid.html b/docs/en_US/pg/spi-spi-gettypeid.html
index fc7c96420a..7100d6af36 100644
--- a/docs/en_US/pg/spi-spi-gettypeid.html
+++ b/docs/en_US/pg/spi-spi-gettypeid.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    SPI_gettypeid — return the data type OID of the specified column
    
 
    
-
    
+
    
 
    Synopsis
    
 
    Oid SPI_gettypeid(TupleDesc rowdesc, int colnumber)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_gettypeid returns the
    OID of the data type of the specified column.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    TupleDesc rowdesc
    
 
          input row description
@@ -39,7 +39,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       The OID of the data type of the specified column
    or InvalidOid on error.  On error,
    SPI_result is set to
diff --git a/docs/en_US/pg/spi-spi-getvalue.html b/docs/en_US/pg/spi-spi-getvalue.html
index cab8e239ab..789d7fc711 100644
--- a/docs/en_US/pg/spi-spi-getvalue.html
+++ b/docs/en_US/pg/spi-spi-getvalue.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_getvalue — return the string value of the specified column
    
 
    
-
    
+
    
 
    Synopsis
    
 
    char * SPI_getvalue(HeapTuple row, TupleDesc rowdesc, int colnumber)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_getvalue returns the string representation
    of the value of the specified column.
   
    
@@ -33,7 +33,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    HeapTuple row
    
 
          input row to be examined
@@ -47,7 +47,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       Column value, or NULL if the column is null,
    colnumber is out of range
    (SPI_result is set to
diff --git a/docs/en_US/pg/spi-spi-is-cursor-plan.html b/docs/en_US/pg/spi-spi-is-cursor-plan.html
index 2593b9f486..fdd8b53508 100644
--- a/docs/en_US/pg/spi-spi-is-cursor-plan.html
+++ b/docs/en_US/pg/spi-spi-is-cursor-plan.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,12 +19,12 @@ 
    Name
    
   prepared by SPI_prepare can be used with
   SPI_cursor_open
    
 
    
-
    
+
    
 
    Synopsis
    
 
    bool SPI_is_cursor_plan(void * plan)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_is_cursor_plan returns true
    if a plan prepared by SPI_prepare can be passed
    as an argument to SPI_cursor_open, or
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          execution plan (returned by SPI_prepare)
@@ -45,7 +45,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
        true or false to indicate if the
     plan can produce a cursor or not, or
     SPI_ERROR_ARGUMENT if the plan
diff --git a/docs/en_US/pg/spi-spi-modifytuple.html b/docs/en_US/pg/spi-spi-modifytuple.html
index 60fffe81b6..c00d45c9ba 100644
--- a/docs/en_US/pg/spi-spi-modifytuple.html
+++ b/docs/en_US/pg/spi-spi-modifytuple.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    SPI_modifytuple — create a row by replacing selected fields of a given row
    
 
    
-
    
+
    
 
    Synopsis
    
 
    HeapTuple SPI_modifytuple(Relation rel, HeapTuple row, ncols, colnum, Datum * values, const char * nulls)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_modifytuple creates a new row by
    substituting new values for selected columns, copying the original
    row's columns at other positions.  The input row is not modified.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Relation rel
    
 
          Used only as the source of the row descriptor for the row.
@@ -57,7 +57,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       new row with modifications, allocated in the upper executor
    context; NULL only if row
    is NULL
diff --git a/docs/en_US/pg/spi-spi-palloc.html b/docs/en_US/pg/spi-spi-palloc.html
index 918d0a38c6..f328cc6b3a 100644
--- a/docs/en_US/pg/spi-spi-palloc.html
+++ b/docs/en_US/pg/spi-spi-palloc.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    SPI_palloc — allocate memory in the upper executor context
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void * SPI_palloc(Size size)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_palloc allocates memory in the upper
    executor context.
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    Size size
    
 
          size in bytes of storage to allocate
@@ -36,7 +36,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       pointer to new storage space of the specified size
   
    
 
    
diff --git a/docs/en_US/pg/spi-spi-pfree.html b/docs/en_US/pg/spi-spi-pfree.html
index c5eb5dab3d..ab54a1b293 100644
--- a/docs/en_US/pg/spi-spi-pfree.html
+++ b/docs/en_US/pg/spi-spi-pfree.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_pfree — free memory in the upper executor context
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_pfree(void * pointer)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_pfree frees memory previously allocated
    using SPI_palloc or
    SPI_repalloc.
@@ -33,7 +33,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * pointer
    
 
          pointer to existing storage to free
diff --git a/docs/en_US/pg/spi-spi-pop.html b/docs/en_US/pg/spi-spi-pop.html
index cc636602dd..6d32b6423b 100644
--- a/docs/en_US/pg/spi-spi-pop.html
+++ b/docs/en_US/pg/spi-spi-pop.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_pop — pop SPI stack to return from recursive SPI usage
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_pop(void)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_pop pops the previous environment from the 
    SPI call stack.  See SPI_push.
   
    
diff --git a/docs/en_US/pg/spi-spi-prepare.html b/docs/en_US/pg/spi-spi-prepare.html
index 8365f56baf..6530a3af5e 100644
--- a/docs/en_US/pg/spi-spi-prepare.html
+++ b/docs/en_US/pg/spi-spi-prepare.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_prepare — prepare a plan for a command, without executing it yet
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void * SPI_prepare(const char * command, int nargs, Oid * argtypes)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_prepare creates and returns an execution
    plan for the specified command but doesn't execute the command.
    This function should only be called from a connected procedure.
@@ -48,7 +48,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    const char * command
    
 
          command string
@@ -63,7 +63,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       SPI_prepare returns a non-null pointer to an
    execution plan.  On error, NULL will be returned,
    and SPI_result will be set to one of the same
@@ -75,7 +75,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       There is a disadvantage to using parameters: since the planner does
    not know the values that will be supplied for the parameters, it
    may make worse planning choices than it would make for a normal
diff --git a/docs/en_US/pg/spi-spi-push.html b/docs/en_US/pg/spi-spi-push.html
index f66ac59a57..3420d68418 100644
--- a/docs/en_US/pg/spi-spi-push.html
+++ b/docs/en_US/pg/spi-spi-push.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_push — push SPI stack to allow recursive SPI usage
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void SPI_push(void)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_push should be called before executing another
    procedure that might itself wish to use SPI.
    After SPI_push, SPI is no longer in a
diff --git a/docs/en_US/pg/spi-spi-returntuple.html b/docs/en_US/pg/spi-spi-returntuple.html
index ad597318ec..5c1684d8a3 100644
--- a/docs/en_US/pg/spi-spi-returntuple.html
+++ b/docs/en_US/pg/spi-spi-returntuple.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_returntuple — prepare to return a tuple as a Datum
    
 
    
-
    
+
    
 
    Synopsis
    
 
    HeapTupleHeader SPI_returntuple(HeapTuple row, TupleDesc rowdesc)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_returntuple makes a copy of a row in
    the upper executor context, returning it in the form of a row type Datum.
    The returned pointer need only be converted to Datum via PointerGetDatum
@@ -34,7 +34,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    HeapTuple row
    
 
          row to be copied
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       HeapTupleHeader pointing to copied row;
    NULL only if
    row or rowdesc is
diff --git a/docs/en_US/pg/spi-spi-saveplan.html b/docs/en_US/pg/spi-spi-saveplan.html
index c884002f9d..338705d9ab 100644
--- a/docs/en_US/pg/spi-spi-saveplan.html
+++ b/docs/en_US/pg/spi-spi-saveplan.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SPI_saveplan — save a plan
    
 
    
-
    
+
    
 
    Synopsis
    
 
    void * SPI_saveplan(void * plan)
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SPI_saveplan saves a passed plan (prepared by
    SPI_prepare) in memory protected from freeing
    by SPI_finish and by the transaction manager
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Arguments
    
+
    Arguments
    
 
    
 
    void * plan
    
 
          the plan to be saved
@@ -40,7 +40,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Return Value
    
+
    Return Value
    
 
       Pointer to the saved plan; NULL if unsuccessful.
    On error, SPI_result is set thus:
 
@@ -57,7 +57,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       If one of the objects (a table, function, etc.) referenced by the
    prepared plan is dropped during the session then the results of
    SPI_execute_plan for this plan will be unpredictable.
diff --git a/docs/en_US/pg/spi-visibility.html b/docs/en_US/pg/spi-visibility.html
index 4f82b256d8..d9eeaf3fc2 100644
--- a/docs/en_US/pg/spi-visibility.html
+++ b/docs/en_US/pg/spi-visibility.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/spi.html b/docs/en_US/pg/spi.html
index 7dce794ba6..acd3d71ccd 100644
--- a/docs/en_US/pg/spi.html
+++ b/docs/en_US/pg/spi.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
 
    41.5. Examples
    
 
 
    
-
      The Server Programming Interface
+
      The Server Programming Interface
   (SPI) gives writers of user-defined
   C functions the ability to run
   SQL commands inside their functions.
diff --git a/docs/en_US/pg/sql-abort.html b/docs/en_US/pg/sql-abort.html
index 68c3f90f0c..1af59e391a 100644
--- a/docs/en_US/pg/sql-abort.html
+++ b/docs/en_US/pg/sql-abort.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    ABORT — abort the current transaction
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ABORT [ WORK | TRANSACTION ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ABORT rolls back the current transaction and causes
    all the updates made by the transaction to be discarded. 
    This command is identical
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 WORK

    TRANSACTION
@@ -42,7 +42,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use COMMIT to
    successfully terminate a transaction.
   
    
@@ -51,7 +51,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To abort all changes:
 
    
 
    ABORT;
    
@@ -59,14 +59,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command is a PostgreSQL extension
    present for historical reasons. ROLLBACK is the
    equivalent standard SQL command.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, ROLLBACK
 
    
 
    
diff --git a/docs/en_US/pg/sql-alteraggregate.html b/docs/en_US/pg/sql-alteraggregate.html
index 3e573c11e1..79260c7a63 100644
--- a/docs/en_US/pg/sql-alteraggregate.html
+++ b/docs/en_US/pg/sql-alteraggregate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    ALTER AGGREGATE — change the definition of an aggregate function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER AGGREGATE name ( type [ , ... ] ) RENAME TO new_name
 ALTER AGGREGATE name ( type [ , ... ] ) OWNER TO new_owner
 ALTER AGGREGATE name ( type [ , ... ] ) SET SCHEMA new_schema
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER AGGREGATE changes the definition of an
    aggregate function.
   
    
@@ -40,7 +40,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of an existing aggregate function.
@@ -62,7 +62,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To rename the aggregate function myavg for type
    integer to my_average:
 
    
@@ -83,13 +83,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER AGGREGATE statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE AGGREGATE, DROP AGGREGATE
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterconversion.html b/docs/en_US/pg/sql-alterconversion.html
index 9af9a003e6..2cb37abc80 100644
--- a/docs/en_US/pg/sql-alterconversion.html
+++ b/docs/en_US/pg/sql-alterconversion.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    ALTER CONVERSION — change the definition of a conversion
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER CONVERSION name RENAME TO newname
 ALTER CONVERSION name OWNER TO newowner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER CONVERSION changes the definition of a
    conversion.
   
    
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of an existing conversion.
@@ -51,7 +51,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To rename the conversion iso_8859_1_to_utf8 to
    latin1_to_unicode:
 
    
@@ -66,13 +66,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER CONVERSION statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE CONVERSION, DROP CONVERSION
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterdatabase.html b/docs/en_US/pg/sql-alterdatabase.html
index b85094c18b..830e035f78 100644
--- a/docs/en_US/pg/sql-alterdatabase.html
+++ b/docs/en_US/pg/sql-alterdatabase.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER DATABASE — change a database
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER DATABASE name [ [ WITH ] option [ ... ] ]
 
@@ -33,7 +33,7 @@ 
    Synopsis
    
 ALTER DATABASE name OWNER TO new_owner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER DATABASE changes the attributes
    of a database.
   
    
@@ -66,7 +66,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name of the database whose attributes are to be altered.
@@ -101,7 +101,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       It is also possible to tie a session default to a specific user
    rather than to a database; see
    ALTER USER.
@@ -110,7 +110,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To disable index scans by default in the database
    test:
 
@@ -120,13 +120,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The ALTER DATABASE statement is a
    PostgreSQL extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE DATABASE, DROP DATABASE, SET
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterdomain.html b/docs/en_US/pg/sql-alterdomain.html
index bba6eccb7b..80c25fedc7 100644
--- a/docs/en_US/pg/sql-alterdomain.html
+++ b/docs/en_US/pg/sql-alterdomain.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@ 
    Name
    
    —    change the definition of a domain
   
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER DOMAIN name
     { SET DEFAULT expression | DROP DEFAULT }
@@ -36,7 +36,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER DOMAIN changes the definition of an existing domain.
    There are several sub-forms:
   
    
@@ -79,7 +79,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
        
    
 
    
 
    name
    
@@ -110,7 +110,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To add a NOT NULL constraint to a domain:
    
    
 
    ALTER DOMAIN zipcode SET NOT NULL;
diff --git a/docs/en_US/pg/sql-alterfunction.html b/docs/en_US/pg/sql-alterfunction.html
index 8f850a6a17..c137490937 100644
--- a/docs/en_US/pg/sql-alterfunction.html
+++ b/docs/en_US/pg/sql-alterfunction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER FUNCTION — change the definition of a function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER FUNCTION name ( [ [ argmode ] [ argname ] argtype [, ...] ] )
     action [, ... ] [ RESTRICT ]
@@ -35,7 +35,7 @@ 
    Synopsis
    
     [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER FUNCTION changes the definition of a
    function.
   
    
@@ -50,7 +50,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of an existing function.
@@ -115,7 +115,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To rename the function sqrt for type
    integer to square_root:
 
    
@@ -136,7 +136,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This statement is partially compatible with the ALTER
    FUNCTION statement in the SQL standard. The standard allows more
    properties of a function to be modified, but does not provide the
@@ -147,7 +147,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE FUNCTION, DROP FUNCTION
 
    
 
    
diff --git a/docs/en_US/pg/sql-altergroup.html b/docs/en_US/pg/sql-altergroup.html
index 57f833a97d..3ffa712343 100644
--- a/docs/en_US/pg/sql-altergroup.html
+++ b/docs/en_US/pg/sql-altergroup.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER GROUP — change role name or membership
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER GROUP groupname ADD USER username [, ... ]
 ALTER GROUP groupname DROP USER username [, ... ]
@@ -25,7 +25,7 @@ 
    Synopsis
    
 ALTER GROUP groupname RENAME TO newname
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER GROUP changes the attributes of a user group.
    This is an obsolete command, though still accepted for backwards
    compatibility, because groups (and users too) have been superseded by the
@@ -45,7 +45,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    groupname
    
 
          The name of the group (role) to modify.
@@ -61,7 +61,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Add users to a group:
 
 
    
@@ -77,13 +77,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER GROUP statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 GRANT, REVOKE, ALTER ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterindex.html b/docs/en_US/pg/sql-alterindex.html
index 5c936685ee..922564bc91 100644
--- a/docs/en_US/pg/sql-alterindex.html
+++ b/docs/en_US/pg/sql-alterindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER INDEX — change the definition of an index
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER INDEX name RENAME TO new_name
 ALTER INDEX name SET TABLESPACE tablespace_name
@@ -25,7 +25,7 @@ 
    Synopsis
    
 ALTER INDEX name RESET ( storage_parameter [, ... ] )
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER INDEX changes the definition of an existing index.
    There are several subforms:
 
@@ -61,7 +61,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name (possibly schema-qualified) of an existing index to
@@ -83,7 +83,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        These operations are also possible using
     ALTER TABLE.
     ALTER INDEX is in fact just an alias for the forms
@@ -98,7 +98,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To rename an existing index:
 
    
 
    ALTER INDEX distributors RENAME TO suppliers;
    
@@ -120,13 +120,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       ALTER INDEX is a PostgreSQL
    extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE INDEX, REINDEX
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterlanguage.html b/docs/en_US/pg/sql-alterlanguage.html
index e3904fb142..2c95d33c81 100644
--- a/docs/en_US/pg/sql-alterlanguage.html
+++ b/docs/en_US/pg/sql-alterlanguage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    ALTER LANGUAGE — change the definition of a procedural language
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER LANGUAGE name RENAME TO newname
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER LANGUAGE changes the definition of a
    language.  The only functionality is to rename the language.  Only
    a superuser can rename languages.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          Name of a language
@@ -40,13 +40,13 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER LANGUAGE statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE LANGUAGE, DROP LANGUAGE
 
    
 
    
diff --git a/docs/en_US/pg/sql-alteropclass.html b/docs/en_US/pg/sql-alteropclass.html
index 692dfc92db..8ecc0cce87 100644
--- a/docs/en_US/pg/sql-alteropclass.html
+++ b/docs/en_US/pg/sql-alteropclass.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    ALTER OPERATOR CLASS — change the definition of an operator class
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER OPERATOR CLASS name USING index_method RENAME TO newname
 ALTER OPERATOR CLASS name USING index_method OWNER TO newowner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER OPERATOR CLASS changes the definition of
    an operator class.
   
    
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of an existing operator
@@ -55,13 +55,13 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER OPERATOR CLASS statement in
    the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE OPERATOR CLASS, DROP OPERATOR CLASS
 
    
 
    
diff --git a/docs/en_US/pg/sql-alteroperator.html b/docs/en_US/pg/sql-alteroperator.html
index bcf56e45ea..a382958214 100644
--- a/docs/en_US/pg/sql-alteroperator.html
+++ b/docs/en_US/pg/sql-alteroperator.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    ALTER OPERATOR — change the definition of an operator
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER OPERATOR name ( { lefttype | NONE } , { righttype | NONE } ) OWNER TO newowner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER OPERATOR changes the definition of
    an operator.  The only currently available functionality is to change the
    owner of the operator.
@@ -36,7 +36,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of an existing operator.
@@ -55,7 +55,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Change the owner of a custom operator a @@ b for type text:
 
    
 
    ALTER OPERATOR @@ (text, text) OWNER TO joe;
    
@@ -63,13 +63,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER OPERATOR statement in
    the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE OPERATOR, DROP OPERATOR
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterrole.html b/docs/en_US/pg/sql-alterrole.html
index 111281dd72..25f2a06c24 100644
--- a/docs/en_US/pg/sql-alterrole.html
+++ b/docs/en_US/pg/sql-alterrole.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER ROLE — change a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER ROLE name [ [ WITH ] option [ ... ] ]
 
@@ -39,7 +39,7 @@ 
    Synopsis
    
 ALTER ROLE name RESET configuration_parameter
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER ROLE changes the attributes of a
    PostgreSQL role.
   
    
@@ -82,7 +82,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name of the role whose attributes are to be altered.
@@ -116,7 +116,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use CREATE ROLE
    to add new roles, and DROP ROLE to remove a role.
   
    
@@ -140,7 +140,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Change a role's password:
 
 
    
@@ -174,13 +174,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The ALTER ROLE statement is a
    PostgreSQL extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE ROLE, DROP ROLE, SET
 
    
 
    
diff --git a/docs/en_US/pg/sql-alterschema.html b/docs/en_US/pg/sql-alterschema.html
index 8716e3dbcb..029cb46471 100644
--- a/docs/en_US/pg/sql-alterschema.html
+++ b/docs/en_US/pg/sql-alterschema.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    ALTER SCHEMA — change the definition of a schema
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER SCHEMA name RENAME TO newname
 ALTER SCHEMA name OWNER TO newowner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER SCHEMA changes the definition of a schema.
   
    
 
       You must own the schema to use ALTER SCHEMA.
@@ -36,7 +36,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of an existing schema.
@@ -52,13 +52,13 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER SCHEMA statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE SCHEMA, DROP SCHEMA
 
    
 
    
diff --git a/docs/en_US/pg/sql-altersequence.html b/docs/en_US/pg/sql-altersequence.html
index f308218d18..bb56555579 100644
--- a/docs/en_US/pg/sql-altersequence.html
+++ b/docs/en_US/pg/sql-altersequence.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@ 
    Name
    
    —    change the definition of a sequence generator
   
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER SEQUENCE name [ INCREMENT [ BY ] increment ]
     [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
@@ -29,7 +29,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER SEQUENCE changes the parameters of an existing
    sequence generator.  Any parameters not specifically set in the
    ALTER SEQUENCE command retain their prior settings.
@@ -40,7 +40,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
        
    
 
    
 
    name
    
@@ -124,7 +124,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Restart a sequence called serial, at 105:
 
    
 
    ALTER SEQUENCE serial RESTART WITH 105;
    
@@ -132,7 +132,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       To avoid blocking of concurrent transactions that obtain numbers from the
    same sequence, ALTER SEQUENCE's effects on the sequence
    generation parameters are never rolled back;
@@ -153,7 +153,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       ALTER SEQUENCE conforms to the SQL
    standard,
    except for the OWNED BY and SET SCHEMA
@@ -161,7 +161,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE SEQUENCE, DROP SEQUENCE
 
    
 
    
diff --git a/docs/en_US/pg/sql-altertable.html b/docs/en_US/pg/sql-altertable.html
index 8decde10f8..7a28d5c8e3 100644
--- a/docs/en_US/pg/sql-altertable.html
+++ b/docs/en_US/pg/sql-altertable.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER TABLE — change the definition of a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER TABLE [ ONLY ] name [ * ]
     action [, ... ]
@@ -53,7 +53,7 @@ 
    Synopsis
    
     SET TABLESPACE new_tablespace
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER TABLE changes the definition of an existing table.
    There are several subforms:
 
@@ -258,7 +258,7 @@ 
    Note
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name (possibly schema-qualified) of an existing table to
@@ -335,7 +335,7 @@ 
    Note
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        The key word COLUMN is noise and can be omitted.
    
    
 
        When a column is added with ADD COLUMN, all existing
@@ -417,7 +417,7 @@ 
    Note
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To add a column of type varchar to a table:
 
    
 
    ALTER TABLE distributors ADD COLUMN address varchar(30);
    
@@ -519,7 +519,7 @@ 
    Note
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The ADD, DROP, and SET DEFAULT
    forms conform with the SQL standard.  The other forms are
    PostgreSQL extensions of the SQL standard.
diff --git a/docs/en_US/pg/sql-altertablespace.html b/docs/en_US/pg/sql-altertablespace.html
index a616790f5d..8db543e4ca 100644
--- a/docs/en_US/pg/sql-altertablespace.html
+++ b/docs/en_US/pg/sql-altertablespace.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    ALTER TABLESPACE — change the definition of a tablespace
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER TABLESPACE name RENAME TO newname
 ALTER TABLESPACE name OWNER TO newowner
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER TABLESPACE changes the definition of
    a tablespace.
   
    
@@ -34,7 +34,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of an existing tablespace.
@@ -50,7 +50,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Rename tablespace index_space to fast_raid:
 
    
 
    ALTER TABLESPACE index_space RENAME TO fast_raid;
    
@@ -63,13 +63,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER TABLESPACE statement in
    the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE TABLESPACE, DROP TABLESPACE
 
    
 
    
diff --git a/docs/en_US/pg/sql-altertrigger.html b/docs/en_US/pg/sql-altertrigger.html
index 096dc26854..f4a96b20a1 100644
--- a/docs/en_US/pg/sql-altertrigger.html
+++ b/docs/en_US/pg/sql-altertrigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    ALTER TRIGGER — change the definition of a trigger
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER TRIGGER name ON table RENAME TO newname
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER TRIGGER changes properties of an existing
    trigger.  The RENAME clause changes the name of
    the given trigger without otherwise changing the trigger
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of an existing trigger to alter.
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        The ability to temporarily enable or disable a trigger is provided by
     ALTER TABLE, not by
     ALTER TRIGGER, because ALTER TRIGGER has no
@@ -55,7 +55,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To rename an existing trigger:
 
    
 
    ALTER TRIGGER emp_stamp ON emp RENAME TO emp_track_chgs;
    
@@ -63,13 +63,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       ALTER TRIGGER is a PostgreSQL
    extension of the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER TABLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-altertype.html b/docs/en_US/pg/sql-altertype.html
index 7bd0f6f99f..ba87dc7a62 100644
--- a/docs/en_US/pg/sql-altertype.html
+++ b/docs/en_US/pg/sql-altertype.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,14 +19,14 @@ 
    Name
    
    —    change the definition of a type
   
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER TYPE name OWNER TO new_owner 
 ALTER TYPE name SET SCHEMA new_schema
   
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER TYPE changes the definition of an existing type.
    The only currently available capabilities are changing the owner and schema
    of a type.
@@ -42,7 +42,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
        
    
 
    
 
    name
    
@@ -60,7 +60,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
     
    To change the owner of the user-defined type email
    to joe:
@@ -78,7 +78,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ALTER TYPE statement in the SQL
    standard.
   
    
diff --git a/docs/en_US/pg/sql-alteruser.html b/docs/en_US/pg/sql-alteruser.html
index 92eb357e3b..65eeff2fed 100644
--- a/docs/en_US/pg/sql-alteruser.html
+++ b/docs/en_US/pg/sql-alteruser.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    ALTER USER — change a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ALTER USER name [ [ WITH ] option [ ... ] ]
 
@@ -39,21 +39,21 @@ 
    Synopsis
    
 ALTER USER name RESET configuration_parameter
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ALTER USER is now an alias for
    ALTER ROLE,
    which see for more information.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The ALTER USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-analyze.html b/docs/en_US/pg/sql-analyze.html
index e9c4e34694..bf70a08f21 100644
--- a/docs/en_US/pg/sql-analyze.html
+++ b/docs/en_US/pg/sql-analyze.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    ANALYZE — collect statistics about a database
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ANALYZE [ VERBOSE ] [ table [ (column [, ...] ) ] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ANALYZE collects statistics about the contents
    of tables in the database, and stores the results in the system
    table pg_statistic.  Subsequently, the query
@@ -36,7 +36,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    VERBOSE
    
 
          Enables display of progress messages.
@@ -51,14 +51,14 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
        When VERBOSE is specified, ANALYZE emits
     progress messages to indicate which table is currently being
     processed.  Various statistics about the tables are printed as well.
    
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       It is a good idea to run ANALYZE periodically, or
    just after making major changes in the contents of a table.  Accurate
    statistics will help the planner to choose the most appropriate query
@@ -116,7 +116,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no ANALYZE statement in the SQL standard.
   
    
 
    
diff --git a/docs/en_US/pg/sql-begin.html b/docs/en_US/pg/sql-begin.html
index 459761ecd5..77e2ef9142 100644
--- a/docs/en_US/pg/sql-begin.html
+++ b/docs/en_US/pg/sql-begin.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    BEGIN — start a transaction block
    
 
    
-
    
+
    
 
    Synopsis
    
 
    BEGIN [ WORK | TRANSACTION ] [ transaction_mode [, ...] ]
 
@@ -27,7 +27,7 @@ 
    Synopsis
    
     READ WRITE | READ ONLY
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       BEGIN initiates a transaction block, that is,
    all statements after a BEGIN command will be
    executed in a single transaction until an explicit COMMIT or ROLLBACK is given.
@@ -52,7 +52,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 WORK

    TRANSACTION
@@ -65,7 +65,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       START TRANSACTION has the same functionality
    as BEGIN.
   
    
@@ -84,7 +84,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To begin a transaction block:
 
 
    
@@ -93,7 +93,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       BEGIN is a PostgreSQL
    language extension.  It is equivalent to the SQL-standard command
    START TRANSACTION, which see for additional
@@ -105,7 +105,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 COMMIT, ROLLBACK, START TRANSACTION, SAVEPOINT
 
    
 
    
diff --git a/docs/en_US/pg/sql-checkpoint.html b/docs/en_US/pg/sql-checkpoint.html
index c3a0111467..d5b91a8690 100644
--- a/docs/en_US/pg/sql-checkpoint.html
+++ b/docs/en_US/pg/sql-checkpoint.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    CHECKPOINT — force a transaction log checkpoint
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CHECKPOINT
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       Write-Ahead Logging (WAL) puts a checkpoint in the transaction log
    every so often. (To adjust the automatic checkpoint interval, see
    the run-time configuration options checkpoint_segments
@@ -41,7 +41,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The CHECKPOINT command is a
    PostgreSQL language extension.
   
    
diff --git a/docs/en_US/pg/sql-close.html b/docs/en_US/pg/sql-close.html
index dabc60bb38..0e5ff7c2f1 100644
--- a/docs/en_US/pg/sql-close.html
+++ b/docs/en_US/pg/sql-close.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    CLOSE — close a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CLOSE name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CLOSE frees the resources associated with an open cursor.
    After the cursor is closed, no subsequent operations
    are allowed on it. A cursor should be closed when it is
@@ -39,7 +39,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of an open cursor to close.
@@ -47,7 +47,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       PostgreSQL does not have an explicit
    OPEN cursor statement; a cursor is considered
    open when it is declared.  Use the
@@ -59,7 +59,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Close the cursor liahona:
 
    
 
    CLOSE liahona;
    
@@ -67,12 +67,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CLOSE is fully conforming with the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DECLARE, FETCH, MOVE
 
    
 
    
diff --git a/docs/en_US/pg/sql-cluster.html b/docs/en_US/pg/sql-cluster.html
index adbcf006f6..636558ed45 100644
--- a/docs/en_US/pg/sql-cluster.html
+++ b/docs/en_US/pg/sql-cluster.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    CLUSTER — cluster a table according to an index
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CLUSTER indexname ON tablename
 CLUSTER tablename
 CLUSTER
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CLUSTER instructs PostgreSQL 
    to cluster the table specified
    by tablename
@@ -59,7 +59,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    indexname
    
 
          The name of an index.
@@ -70,7 +70,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        In cases where you are accessing single rows randomly
     within a table, the actual order of the data in the
     table is unimportant. However, if you tend to access some
@@ -129,7 +129,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Cluster the table employees on the basis of
    its index emp_ind:
 
    
@@ -149,12 +149,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no CLUSTER statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 clusterdb
 
    
 
    
diff --git a/docs/en_US/pg/sql-commands.html b/docs/en_US/pg/sql-commands.html
index 312d104b26..c4b0b3a44e 100644
--- a/docs/en_US/pg/sql-commands.html
+++ b/docs/en_US/pg/sql-commands.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 SQL Commands
    
 
    
 
    
-
    
+
    
 
    
 
        This part contains reference information for the
     SQL commands supported by
diff --git a/docs/en_US/pg/sql-comment.html b/docs/en_US/pg/sql-comment.html
index ae15427470..fcea857cb5 100644
--- a/docs/en_US/pg/sql-comment.html
+++ b/docs/en_US/pg/sql-comment.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    COMMENT — define or change the comment of an object
    
 
    
-
    
+
    
 
    Synopsis
    
 
    COMMENT ON
 {
@@ -46,7 +46,7 @@ 
    Synopsis
    
 } IS 'text'
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       COMMENT stores a comment about a database object.
   
    
 
        To modify a comment, issue a new COMMENT command for the
@@ -66,7 +66,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 object_name

    table_name.column_name

    agg_name

    constraint_name

    func_name

    op

    rule_name

    trigger_name
@@ -118,7 +118,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       There is presently no security mechanism for comments: any user
    connected to a database can see all the comments for objects in
    that database (although only superusers can change comments for
@@ -130,7 +130,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Attach a comment to the table mytable:
 
 
    
@@ -172,7 +172,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no COMMENT command in the SQL standard.
   
    
 
    
diff --git a/docs/en_US/pg/sql-commit-prepared.html b/docs/en_US/pg/sql-commit-prepared.html
index 24f50c87b9..77e9aa0837 100644
--- a/docs/en_US/pg/sql-commit-prepared.html
+++ b/docs/en_US/pg/sql-commit-prepared.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit
    
 
    
-
    
+
    
 
    Synopsis
    
 
    COMMIT PREPARED transaction_id
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       COMMIT PREPARED commits a transaction that is in 
    prepared state.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    transaction_id
    
 
          The transaction identifier of the transaction that is to be
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       To commit a prepared transaction, you must be either the same user that
    executed the transaction originally, or a superuser.  But you do not
    have to be in the same session that executed the transaction.
@@ -61,7 +61,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 PREPARE TRANSACTION, ROLLBACK PREPARED
 
    
 
    
diff --git a/docs/en_US/pg/sql-commit.html b/docs/en_US/pg/sql-commit.html
index 9e66c0b743..4b83f7e6a2 100644
--- a/docs/en_US/pg/sql-commit.html
+++ b/docs/en_US/pg/sql-commit.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    COMMIT — commit the current transaction
    
 
    
-
    
+
    
 
    Synopsis
    
 
    COMMIT [ WORK | TRANSACTION ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       COMMIT commits the current transaction. All
    changes made by the transaction become visible to others
    and are guaranteed to be durable if a crash occurs.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 WORK

    TRANSACTION
@@ -39,7 +39,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use ROLLBACK to
    abort a transaction.
   
    
@@ -48,7 +48,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To commit the current transaction and make all changes permanent:
 
    
 
    COMMIT;
    
@@ -56,14 +56,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard only specifies the two forms
    COMMIT and COMMIT
    WORK. Otherwise, this command is fully conforming.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, ROLLBACK
 
    
 
    
diff --git a/docs/en_US/pg/sql-copy.html b/docs/en_US/pg/sql-copy.html
index d47ade6f04..01e449a6a6 100644
--- a/docs/en_US/pg/sql-copy.html
+++ b/docs/en_US/pg/sql-copy.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    COPY — copy data between a file and a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    COPY tablename [ ( column [, ...] ) ]
     FROM { 'filename' | STDIN }
@@ -45,7 +45,7 @@ 
    Synopsis
    
                 [ FORCE QUOTE column [, ...] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       COPY moves data between
    PostgreSQL tables and standard file-system
    files. COPY TO copies the contents of a table
@@ -70,7 +70,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    tablename
    
 
          The name (optionally schema-qualified) of an existing table.
@@ -160,7 +160,7 @@ 
    Note
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, a COPY command returns a command
    tag of the form
 
    
@@ -171,7 +171,7 @@ 
    Note
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        COPY can only be used with plain tables, not
     with views.  However, you can write COPY (SELECT * FROM
     viewname) TO ....
@@ -234,9 +234,9 @@ 
    Note
    
    
    
 
    
 
    
-
    File Formats
    
+
    File Formats
    
 
    
-
    Text Format
    
+
    Text Format
    
 
        When COPY is used without the BINARY
     or CSV options,
     the data read or written is a text file with one line per table row.
@@ -361,7 +361,7 @@ 
    Note
    
    
    
 
    
 
    
-
    CSV Format
    
+
    CSV Format
    
 
        This format is used for importing and exporting the Comma
     Separated Value (CSV) file format used by many other
     programs, such as spreadsheets. Instead of the escaping used by
@@ -433,14 +433,14 @@ 
    Note
    
 
    
 
    
 
    
-
    Binary Format
    
+
    Binary Format
    
 
        The file format used for COPY BINARY changed in
     PostgreSQL 7.4. The new format consists
     of a file header, zero or more tuples containing the row data, and
     a file trailer. Headers and data are now in network byte order.
    
    
 
    
-
    File Header
    
+
    File Header
    
 
         The file header consists of 15 bytes of fixed fields, followed
      by a variable-length header extension area.  The fixed fields are:
 
@@ -495,7 +495,7 @@ 
    Note
    
     
    
 
    
 
    
-
    Tuples
    
+
    Tuples
    
 
    Each tuple begins with a 16-bit integer count of the number of fields in the
 tuple.  (Presently, all tuples in a table will have the same count, but that
 might not always be true.)  Then, repeated for each field in the tuple, there
@@ -525,7 +525,7 @@ 
    Note
    
     
    
 
    
 
    
-
    File Trailer
    
+
    File Trailer
    
 
         The file trailer consists of a 16-bit integer word containing -1.  This
      is easily distinguished from a tuple's field-count word.
     
    
@@ -537,7 +537,7 @@ 
    Note
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       The following example copies a table to the client
    using the vertical bar (|) as the field delimiter:
 
    
@@ -585,7 +585,7 @@ 
    Note
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no COPY statement in the SQL standard.
   
    
 
       The following syntax was used before PostgreSQL
diff --git a/docs/en_US/pg/sql-createaggregate.html b/docs/en_US/pg/sql-createaggregate.html
index 9989865a2c..fb7dd31858 100644
--- a/docs/en_US/pg/sql-createaggregate.html
+++ b/docs/en_US/pg/sql-createaggregate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE AGGREGATE — define a new aggregate function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE AGGREGATE name ( input_data_type [ , ... ] ) (
     SFUNC = sfunc,
@@ -39,7 +39,7 @@ 
    Synopsis
    
 )
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE AGGREGATE defines a new aggregate
    function. Some basic and commonly-used aggregate functions are
    included with the distribution; they are documented in Section 9.15, “Aggregate Functions”. If one defines new types or needs
@@ -140,7 +140,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of the aggregate function
@@ -201,19 +201,19 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       See Section 33.10, “User-Defined Aggregates”.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE AGGREGATE is a
    PostgreSQL language extension.  The SQL
    standard does not provide for user-defined aggregate functions.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER AGGREGATE, DROP AGGREGATE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createcast.html b/docs/en_US/pg/sql-createcast.html
index c4bfe0b66a..4bcde2fdd8 100644
--- a/docs/en_US/pg/sql-createcast.html
+++ b/docs/en_US/pg/sql-createcast.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE CAST — define a new cast
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE CAST (sourcetype AS targettype)
     WITH FUNCTION funcname (argtypes)
@@ -102,7 +102,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    sourcetype
    
 
           The name of the source data type of the cast.
diff --git a/docs/en_US/pg/sql-createconstraint.html b/docs/en_US/pg/sql-createconstraint.html
index 011ca1b6de..a0f9b5ce76 100644
--- a/docs/en_US/pg/sql-createconstraint.html
+++ b/docs/en_US/pg/sql-createconstraint.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE CONSTRAINT TRIGGER — define a new constraint trigger
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE CONSTRAINT TRIGGER name
     AFTER event [ OR ... ]
@@ -28,7 +28,7 @@ 
    Synopsis
    
     EXECUTE PROCEDURE funcname ( arguments )
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE CONSTRAINT TRIGGER is used within
    CREATE TABLE/ALTER TABLE and by
    pg_dump to create the special triggers for
@@ -37,7 +37,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of the constraint trigger. The actual name of the
@@ -72,7 +72,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE CONTRAINT TRIGGER is a
    PostgreSQL extension of the SQL
    standard.
diff --git a/docs/en_US/pg/sql-createconversion.html b/docs/en_US/pg/sql-createconversion.html
index 42fd080eb8..2b43b66b1b 100644
--- a/docs/en_US/pg/sql-createconversion.html
+++ b/docs/en_US/pg/sql-createconversion.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE CONVERSION — define a new encoding conversion
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ DEFAULT ] CONVERSION name
     FOR source_encoding TO dest_encoding FROM funcname
    
@@ -38,7 +38,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    DEFAULT
    
 
           The DEFAULT clause indicates that this conversion
diff --git a/docs/en_US/pg/sql-createdatabase.html b/docs/en_US/pg/sql-createdatabase.html
index 7df0ade633..e1ac02404c 100644
--- a/docs/en_US/pg/sql-createdatabase.html
+++ b/docs/en_US/pg/sql-createdatabase.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE DATABASE — create a new database
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE DATABASE name
     [ [ WITH ] [ OWNER [=] dbowner ]
@@ -27,7 +27,7 @@ 
    Synopsis
    
            [ CONNECTION LIMIT [=] connlimit ] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE DATABASE creates a new
    PostgreSQL database.
   
    
@@ -54,7 +54,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name of a database to create.
@@ -97,7 +97,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        CREATE DATABASE cannot be executed inside a transaction
     block.
    
    
@@ -127,7 +127,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To create a new database:
 
 
    
@@ -150,14 +150,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no CREATE DATABASE statement in the SQL
    standard.  Databases are equivalent to catalogs, whose creation is
    implementation-defined.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER DATABASE, DROP DATABASE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createdomain.html b/docs/en_US/pg/sql-createdomain.html
index 931c20ac07..889da5d2b7 100644
--- a/docs/en_US/pg/sql-createdomain.html
+++ b/docs/en_US/pg/sql-createdomain.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE DOMAIN — define a new domain
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE DOMAIN name [ AS ] data_type
     [ DEFAULT expression ]
@@ -29,7 +29,7 @@ 
    Synopsis
    
 { NOT NULL | NULL | CHECK (expression) }
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE DOMAIN creates a new domain.  A domain is
    essentially a data type with optional constraints (restrictions on
    the allowed set of values).
@@ -50,7 +50,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name (optionally schema-qualified) of a domain to be created.
@@ -107,7 +107,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       This example creates the us_postal_code data type and
    then uses the type in a table definition.  A regular expression test
    is used to verify that the value looks like a valid US postal code.
diff --git a/docs/en_US/pg/sql-createfunction.html b/docs/en_US/pg/sql-createfunction.html
index b2d96e0d66..ccfdd2e0df 100644
--- a/docs/en_US/pg/sql-createfunction.html
+++ b/docs/en_US/pg/sql-createfunction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE FUNCTION — define a new function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ OR REPLACE ] FUNCTION
     name ( [ [ argmode ] [ argname ] argtype [, ...] ] )
@@ -64,7 +64,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
           The name (optionally schema-qualified) of the function to create.
@@ -342,7 +342,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER FUNCTION, DROP FUNCTION, GRANT, LOAD, REVOKE, createlang
 
    
 
    
diff --git a/docs/en_US/pg/sql-creategroup.html b/docs/en_US/pg/sql-creategroup.html
index 9c710e2717..b8ef2e5a7c 100644
--- a/docs/en_US/pg/sql-creategroup.html
+++ b/docs/en_US/pg/sql-creategroup.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE GROUP — define a new database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE GROUP name [ [ WITH ] option [ ... ] ]
 
@@ -39,20 +39,20 @@ 
    Synopsis
    
     | SYSID uid 
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE GROUP is now an alias for
    CREATE ROLE,
    which see for more information.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no CREATE GROUP statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createindex.html b/docs/en_US/pg/sql-createindex.html
index 1f4e14513b..b2b81d8960 100644
--- a/docs/en_US/pg/sql-createindex.html
+++ b/docs/en_US/pg/sql-createindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE INDEX — define a new index
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name ON table [ USING method ]
     ( { column | ( expression ) } [ opclass ] [, ...] )
@@ -26,7 +26,7 @@ 
    Synopsis
    
     [ WHERE predicate ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE INDEX constructs an index index_name on the specified table.
    Indexes are primarily used to enhance database performance (though
    inappropriate use can result in slower performance).
@@ -75,7 +75,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    UNIQUE
    
 
            Causes the system to check for
@@ -157,7 +157,7 @@ 
    Synopsis
    
 
    
 
    
 
    Building Indexes Concurrently
    
-
        Creating an index can interfere with regular operation of a database.
+
        Creating an index can interfere with regular operation of a database.
     Normally PostgreSQL locks the table to be indexed against
     writes and performs the entire index build with a single scan of the
     table. Other transactions can still read the table, but if they try to
@@ -212,7 +212,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       See Chapter 11, Indexes for information about when indexes can
    be used, when they are not used, and in which particular situations
    they can be useful.
@@ -253,7 +253,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To create a B-tree index on the column title in
    the table films:
 
    
@@ -285,14 +285,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE INDEX is a
    PostgreSQL language extension.  There
    are no provisions for indexes in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER INDEX, DROP INDEX
 
    
 
    
diff --git a/docs/en_US/pg/sql-createlanguage.html b/docs/en_US/pg/sql-createlanguage.html
index 747600e1f8..90c480afcc 100644
--- a/docs/en_US/pg/sql-createlanguage.html
+++ b/docs/en_US/pg/sql-createlanguage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE LANGUAGE — define a new procedural language
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ PROCEDURAL ] LANGUAGE name
 CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
@@ -183,7 +183,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER LANGUAGE, CREATE FUNCTION, DROP LANGUAGE, GRANT, REVOKE, createlang, droplang
 
    
 
    
diff --git a/docs/en_US/pg/sql-createopclass.html b/docs/en_US/pg/sql-createopclass.html
index 0b54f4e643..8df4205064 100644
--- a/docs/en_US/pg/sql-createopclass.html
+++ b/docs/en_US/pg/sql-createopclass.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE OPERATOR CLASS — define a new operator class
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE OPERATOR CLASS name [ DEFAULT ] FOR TYPE data_type USING index_method AS
   {  OPERATOR strategy_number operator_name [ ( op_type, op_type ) ] [ RECHECK ]
@@ -26,7 +26,7 @@ 
    Synopsis
    
   } [, ... ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE OPERATOR CLASS creates a new operator class.
    An operator class defines how a particular data type can be used with
    an index.  The operator class specifies that certain operators will fill
@@ -57,7 +57,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of the operator class to be created.  The name may be
@@ -118,7 +118,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Because the index machinery does not check access permissions on functions
    before using them, including a function or operator in an operator class
    is tantamount to granting public execute permission on it.  This is usually
@@ -131,7 +131,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       The following example command defines a GiST index operator class
    for the data type _int4 (array of int4).  See
    contrib/intarray/ for the complete example.
@@ -152,7 +152,7 @@ 
    Synopsis
    
         FUNCTION        7       g_int_same (_int4, _int4, internal);
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE OPERATOR CLASS is a
    PostgreSQL extension.  There is no
    CREATE OPERATOR CLASS statement in the SQL
@@ -160,7 +160,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER OPERATOR CLASS, DROP OPERATOR CLASS
 
    
 
    
diff --git a/docs/en_US/pg/sql-createoperator.html b/docs/en_US/pg/sql-createoperator.html
index 066a2e7c74..0d22869019 100644
--- a/docs/en_US/pg/sql-createoperator.html
+++ b/docs/en_US/pg/sql-createoperator.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE OPERATOR — define a new operator
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE OPERATOR name (
     PROCEDURE = funcname
@@ -30,7 +30,7 @@ 
    Synopsis
    
 )
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE OPERATOR defines a new operator,
    name.  The user who
    defines an operator becomes its owner.  If a schema name is given
@@ -84,7 +84,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name of the operator to be defined. See above for allowable
@@ -149,7 +149,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Refer to Section 33.12, “User-Defined Operators” for further information.
   
    
 
       Use DROP OPERATOR to delete user-defined operators
@@ -158,7 +158,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       The following command defines a new operator, area-equality, for
    the data type box:
 
    
@@ -180,14 +180,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE OPERATOR is a
    PostgreSQL extension.  There are no
    provisions for user-defined operators in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER OPERATOR, CREATE OPERATOR CLASS, DROP OPERATOR
 
    
 
    
diff --git a/docs/en_US/pg/sql-createrole.html b/docs/en_US/pg/sql-createrole.html
index 86715cb7df..37cc9280c2 100644
--- a/docs/en_US/pg/sql-createrole.html
+++ b/docs/en_US/pg/sql-createrole.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE ROLE — define a new database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE ROLE name [ [ WITH ] option [ ... ] ]
 
@@ -40,7 +40,7 @@ 
    Synopsis
    
     | SYSID uid 
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE ROLE adds a new role to a
    PostgreSQL database cluster.  A role is
    an entity that can own database objects and have database privileges;
@@ -55,7 +55,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
            The name of the new role.
@@ -198,7 +198,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use ALTER ROLE to
    change the attributes of a role, and DROP ROLE to remove a role.  All the attributes
    specified by CREATE ROLE can be modified by later
@@ -260,7 +260,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a role that can log in, but don't give it a password:
 
    
 
    CREATE ROLE jonathan LOGIN;
    
@@ -289,7 +289,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The CREATE ROLE statement is in the SQL standard,
    but the standard only requires the syntax
 
    
@@ -312,7 +312,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 SET ROLE, ALTER ROLE, DROP ROLE, GRANT, REVOKE, createuser
 
    
 
    
diff --git a/docs/en_US/pg/sql-createrule.html b/docs/en_US/pg/sql-createrule.html
index 9b5a60363a..256c185c27 100644
--- a/docs/en_US/pg/sql-createrule.html
+++ b/docs/en_US/pg/sql-createrule.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    CREATE RULE — define a new rewrite rule
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ OR REPLACE ] RULE name AS ON event
     TO table [ WHERE condition ]
     DO [ ALSO | INSTEAD ] { NOTHING | command | ( command ; command ... ) }
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE RULE defines a new rule applying to a specified
    table or view.
    CREATE OR REPLACE RULE will either create a
@@ -81,7 +81,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of a rule to create.  This must be distinct from the
@@ -138,7 +138,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       You must be the owner of a table to create or change rules for it.
   
    
 
       In a rule for INSERT, UPDATE, or
@@ -194,7 +194,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE RULE is a
    PostgreSQL language extension, as is the
    entire query rewrite system.
diff --git a/docs/en_US/pg/sql-createschema.html b/docs/en_US/pg/sql-createschema.html
index b346111113..ddbae5b383 100644
--- a/docs/en_US/pg/sql-createschema.html
+++ b/docs/en_US/pg/sql-createschema.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    CREATE SCHEMA — define a new schema
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE SCHEMA schemaname [ AUTHORIZATION username ] [ schema_element [ ... ] ]
 CREATE SCHEMA AUTHORIZATION username [ schema_element [ ... ] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE SCHEMA enters a new schema
    into the current database.
    The schema name must be distinct from the name of any existing schema
@@ -47,7 +47,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    schemaname
    
 
            The name of a schema to be created.  If this is omitted, the user name
@@ -72,14 +72,14 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       To create a schema, the invoking user must have the
    CREATE privilege for the current database.
    (Of course, superusers bypass this check.)
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a schema:
 
    
 
    CREATE SCHEMA myschema;
    
@@ -110,7 +110,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard allows a DEFAULT CHARACTER SET clause
    in CREATE SCHEMA, as well as more subcommand
    types than are presently accepted by
@@ -131,7 +131,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER SCHEMA, DROP SCHEMA
 
    
 
    
diff --git a/docs/en_US/pg/sql-createsequence.html b/docs/en_US/pg/sql-createsequence.html
index 4f714f56bc..ef6a594a68 100644
--- a/docs/en_US/pg/sql-createsequence.html
+++ b/docs/en_US/pg/sql-createsequence.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE SEQUENCE — define a new sequence generator
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ TEMPORARY | TEMP ] SEQUENCE name [ INCREMENT [ BY ] increment ]
     [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE ]
@@ -25,7 +25,7 @@ 
    Synopsis
    
     [ OWNED BY { table.column | NONE } ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE SEQUENCE creates a new sequence number
    generator.  This involves creating and initializing a new special
    single-row table with the name name.  The generator will be
@@ -59,7 +59,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    TEMPORARY or TEMP
    
 
          If specified, the sequence object is created only for this
@@ -140,7 +140,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use DROP SEQUENCE to remove a sequence.
   
    
 
       Sequences are based on bigint arithmetic, so the range
@@ -185,7 +185,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create an ascending sequence called serial, starting at 101:
 
    
 
    CREATE SEQUENCE serial START 101;
    
@@ -215,7 +215,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE SEQUENCE conforms to the SQL
    standard, with the following exceptions:
    
    
@@ -235,7 +235,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER SEQUENCE, DROP SEQUENCE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createtable.html b/docs/en_US/pg/sql-createtable.html
index 4bf1e1765d..ed08c97da2 100644
--- a/docs/en_US/pg/sql-createtable.html
+++ b/docs/en_US/pg/sql-createtable.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE TABLE — define a new table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name ( [
   { column_name data_type [ DEFAULT default_expr ] [ column_constraint [ ... ] ]
@@ -91,7 +91,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    TEMPORARY or TEMP
    
 
    
@@ -686,7 +686,7 @@ 
    Tip
    
    SQL standard, with exceptions listed below.
   
    
 
    
-
    Temporary Tables
    
+
    Temporary Tables
    
 
        Although the syntax of CREATE TEMPORARY TABLE
     resembles that of the SQL standard, the effect is not the same.  In the
     standard,
@@ -721,7 +721,7 @@ 
    Tip
    
    
    
 
    
 
    
-
    Column Check Constraints
    
+
    Column Check Constraints
    
 
        The SQL standard says that CHECK column constraints
     may only refer to the column they apply to; only CHECK
     table constraints may refer to multiple columns.
@@ -730,7 +730,7 @@ 
    Tip
    
    
    
 
    
 
    
-
    
+
    
 NULL “Constraint”
    
 
        The NULL “constraint” (actually a
     non-constraint) is a PostgreSQL
@@ -741,7 +741,7 @@ 
    Tip
    
    
    
 
    
 
    
-
    Inheritance
    
+
    Inheritance
    
 
        Multiple inheritance via the INHERITS clause is
     a PostgreSQL language extension.
     SQL:1999 and later define single inheritance using a
@@ -751,7 +751,7 @@ 
    Tip
    
    
    
 
    
 
    
-
    Zero-column tables
    
+
    Zero-column tables
    
 
        PostgreSQL allows a table of no columns
     to be created (for example, CREATE TABLE foo();).  This
     is an extension from the SQL standard, which does not allow zero-column
@@ -761,14 +761,14 @@ 
    Tip
    
    
    
 
    
 
    
-
    
+
    
 WITH clause
    
 
        The WITH clause is a PostgreSQL
     extension; neither storage parameters nor OIDs are in the standard.
    
    
 
    
 
    
-
    Tablespaces
    
+
    Tablespaces
    
 
        The PostgreSQL concept of tablespaces is not
     part of the standard.  Hence, the clauses TABLESPACE
     and USING INDEX TABLESPACE are extensions.
@@ -776,7 +776,7 @@ 
    Tip
    
 
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER TABLE, DROP TABLE, CREATE TABLESPACE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createtableas.html b/docs/en_US/pg/sql-createtableas.html
index 459278e4f5..7221b1b081 100644
--- a/docs/en_US/pg/sql-createtableas.html
+++ b/docs/en_US/pg/sql-createtableas.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE TABLE AS — define a new table from the results of a query
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name
     [ (column_name [, ...] ) ]
@@ -27,7 +27,7 @@ 
    Synopsis
    
     AS query
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE TABLE AS creates a table and fills it
    with data computed by a SELECT command.
    The table columns have the
@@ -45,7 +45,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    GLOBAL or LOCAL
    
 
          Ignored for compatibility. Refer to CREATE TABLE for
@@ -127,7 +127,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       This command is functionally similar to SELECT INTO, but it is
    preferred since it is less likely to be confused with other uses of
    the SELECT INTO syntax. Furthermore, CREATE
@@ -150,7 +150,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a new table films_recent consisting of only
    recent entries from the table films:
 
@@ -172,7 +172,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE TABLE AS conforms to the SQL
    standard, with the following exceptions:
 
@@ -206,7 +206,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE TABLE, EXECUTE, SELECT, SELECT INTO, VALUES
 
    
 
    
diff --git a/docs/en_US/pg/sql-createtablespace.html b/docs/en_US/pg/sql-createtablespace.html
index 86354b6a90..898cf09338 100644
--- a/docs/en_US/pg/sql-createtablespace.html
+++ b/docs/en_US/pg/sql-createtablespace.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    CREATE TABLESPACE — define a new tablespace
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE TABLESPACE tablespacename [ OWNER username ] LOCATION 'directory'
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE TABLESPACE registers a new cluster-wide
    tablespace.  The tablespace name must be distinct from the name of any
    existing tablespace in the database cluster.
@@ -39,7 +39,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    tablespacename
    
 
            The name of a tablespace to be created.  The name cannot
@@ -61,7 +61,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Tablespaces are only supported on systems that support symbolic links.
   
    
 
        CREATE TABLESPACE cannot be executed inside a transaction
@@ -69,7 +69,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a tablespace dbspace at /data/dbs:
 
    
 
    CREATE TABLESPACE dbspace LOCATION '/data/dbs';
    
@@ -83,13 +83,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       CREATE TABLESPACE is a PostgreSQL
    extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE DATABASE, CREATE TABLE, CREATE INDEX, DROP TABLESPACE, ALTER TABLESPACE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createtrigger.html b/docs/en_US/pg/sql-createtrigger.html
index 3b2c20f395..7718463c3f 100644
--- a/docs/en_US/pg/sql-createtrigger.html
+++ b/docs/en_US/pg/sql-createtrigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    CREATE TRIGGER — define a new trigger
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }
     ON table [ FOR [ EACH ] { ROW | STATEMENT } ]
     EXECUTE PROCEDURE funcname ( arguments )
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE TRIGGER creates a new trigger.  The
    trigger will be associated with the specified table and will
    execute the specified function funcname when certain events occur.
@@ -65,7 +65,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name to give the new trigger.  This must be distinct from
@@ -181,7 +181,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE FUNCTION, ALTER TRIGGER, DROP TRIGGER
 
    
 
    
diff --git a/docs/en_US/pg/sql-createtype.html b/docs/en_US/pg/sql-createtype.html
index cbe00401af..a968fe6829 100644
--- a/docs/en_US/pg/sql-createtype.html
+++ b/docs/en_US/pg/sql-createtype.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE TYPE — define a new data type
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE TYPE name AS
     ( attribute_name data_type [, ... ] )
@@ -40,7 +40,7 @@ 
    Synopsis
    
 CREATE TYPE name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE TYPE registers a new data type for use in
    the current database.  The user who defines a type becomes its
    owner.
@@ -53,7 +53,7 @@ 
    Synopsis
    
    table in the same schema.)
   
    
 
    
-
    Composite Types
    
+
    Composite Types
    
 
       The first form of CREATE TYPE
    creates a composite type.
    The composite type is specified by a list of attribute names and data types.
@@ -65,7 +65,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Base Types
    
+
    Base Types
    
 
       The second form of CREATE TYPE creates a new base type
    (scalar type).  The parameters may appear in any order, not only that
    illustrated above, and most are optional.  You must register
@@ -224,7 +224,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Array Types
    
+
    Array Types
    
 
        Whenever a user-defined base data type is created, 
     PostgreSQL automatically creates an
     associated array type, whose name consists of the base type's
@@ -257,7 +257,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of a type to be created.
@@ -363,7 +363,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       This example creates a composite type and uses it in
    a function definition:
 
    
diff --git a/docs/en_US/pg/sql-createuser.html b/docs/en_US/pg/sql-createuser.html
index ef3df1f25e..9dccba752d 100644
--- a/docs/en_US/pg/sql-createuser.html
+++ b/docs/en_US/pg/sql-createuser.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    CREATE USER — define a new database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE USER name [ [ WITH ] option [ ... ] ]
 
@@ -40,7 +40,7 @@ 
    Synopsis
    
     | SYSID uid 
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE USER is now an alias for
    CREATE ROLE,
    which see for more information.
@@ -52,14 +52,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The CREATE USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-createview.html b/docs/en_US/pg/sql-createview.html
index 6e6c487938..c90ff89857 100644
--- a/docs/en_US/pg/sql-createview.html
+++ b/docs/en_US/pg/sql-createview.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    CREATE VIEW — define a new view
    
 
    
-
    
+
    
 
    Synopsis
    
 
    CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW name [ ( column_name [, ...] ) ]
     AS query
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       CREATE VIEW defines a view of a query.  The view
    is not physically materialized. Instead, the query is run every time
    the view is referenced in a query.
@@ -43,7 +43,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    TEMPORARY or TEMP
    
 
    
@@ -74,7 +74,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        Currently, views are read only: the system will not allow an insert,
     update, or delete on a view.  You can get the effect of an updatable
     view by creating rules that rewrite inserts, etc. on the view into
@@ -104,7 +104,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a view consisting of all comedy films:
 
 
    
@@ -116,7 +116,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard specifies some additional capabilities for the
    CREATE VIEW statement:
 
    
@@ -153,7 +153,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DROP VIEW
 
    
 
    
diff --git a/docs/en_US/pg/sql-deallocate.html b/docs/en_US/pg/sql-deallocate.html
index 1025ee8530..983d31b8c4 100644
--- a/docs/en_US/pg/sql-deallocate.html
+++ b/docs/en_US/pg/sql-deallocate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DEALLOCATE — deallocate a prepared statement
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DEALLOCATE [ PREPARE ] name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DEALLOCATE is used to deallocate a previously
    prepared SQL statement. If you do not explicitly deallocate a
    prepared statement, it is deallocated when the session ends.
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    PREPARE
    
 
          This key word is ignored.
@@ -42,13 +42,13 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard includes a DEALLOCATE
    statement, but it is only for use in embedded SQL.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 EXECUTE, PREPARE
 
    
 
    
diff --git a/docs/en_US/pg/sql-declare.html b/docs/en_US/pg/sql-declare.html
index ea6ee3a789..af2336d063 100644
--- a/docs/en_US/pg/sql-declare.html
+++ b/docs/en_US/pg/sql-declare.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    DECLARE — define a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DECLARE name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
     CURSOR [ { WITH | WITHOUT } HOLD ] FOR query
     [ FOR { READ ONLY | UPDATE [ OF column [, ...] ] } ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DECLARE allows a user to create cursors, which
    can be used to retrieve
    a small number of rows at a time out of a larger query. Cursors can
@@ -66,7 +66,7 @@ 
    Note
    
 
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of the cursor to be created.
@@ -185,7 +185,7 @@ 
    Note
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To declare a cursor:
 
    
 
    DECLARE liahona CURSOR FOR SELECT * FROM films;
    
@@ -195,7 +195,7 @@ 
    Note
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard allows cursors only in embedded
    SQL and in modules. PostgreSQL
    permits cursors to be used interactively.
@@ -208,7 +208,7 @@ 
    Note
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CLOSE, FETCH, MOVE
 
    
 
    
diff --git a/docs/en_US/pg/sql-delete.html b/docs/en_US/pg/sql-delete.html
index 4b6645e41a..c28c5ea158 100644
--- a/docs/en_US/pg/sql-delete.html
+++ b/docs/en_US/pg/sql-delete.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    DELETE — delete rows of a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DELETE FROM [ ONLY ] table [ [ AS ] alias ]
     [ USING usinglist ]
@@ -25,7 +25,7 @@ 
    Synopsis
    
     [ RETURNING * | output_expression [ AS output_name ] [, ...] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DELETE deletes rows that satisfy the
    WHERE clause from the specified table.  If the
    WHERE clause is absent, the effect is to delete
@@ -63,7 +63,7 @@ 
    Tip
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    ONLY
    
 
          If specified, delete rows from the named table only.  When not
@@ -106,7 +106,7 @@ 
    Tip
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, a DELETE command returns a command
    tag of the form
 
    
@@ -125,7 +125,7 @@ 
    Tip
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       PostgreSQL lets you reference columns of
    other tables in the WHERE condition by specifying the
    other tables in the USING clause.  For example,
@@ -147,7 +147,7 @@ 
    Tip
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Delete all films but musicals:
 
    
 
    DELETE FROM films WHERE kind <> 'Musical';
    
@@ -165,7 +165,7 @@ 
    Tip
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command conforms to the SQL standard, except
    that the USING and RETURNING clauses
    are PostgreSQL extensions.
diff --git a/docs/en_US/pg/sql-drop-owned.html b/docs/en_US/pg/sql-drop-owned.html
index b86cf33a96..f6069966b4 100644
--- a/docs/en_US/pg/sql-drop-owned.html
+++ b/docs/en_US/pg/sql-drop-owned.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP OWNED — remove database objects owned by a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP OWNED BY name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP OWNED drops all the objects in the current
    database that are owned by one of the specified roles. Any
    privileges granted to the given roles on objects in the current
@@ -30,7 +30,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of a role whose objects will be dropped, and whose
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       DROP OWNED is often used to prepare for the
    removal of one or more roles. Because DROP OWNED
    only affects the objects in the current database, it is usually
@@ -62,13 +62,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The DROP OWNED statement is a
    PostgreSQL extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 REASSIGN OWNED, DROP ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropaggregate.html b/docs/en_US/pg/sql-dropaggregate.html
index 78b9ceaa03..1ec8715944 100644
--- a/docs/en_US/pg/sql-dropaggregate.html
+++ b/docs/en_US/pg/sql-dropaggregate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    DROP AGGREGATE — remove an aggregate function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP AGGREGATE [ IF EXISTS ] name ( type [ , ... ] ) [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP AGGREGATE will delete an existing
    aggregate function. To execute this command the current
    user must be the owner of the aggregate function.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the aggregate does not exist. A notice is issued
@@ -53,7 +53,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To remove the aggregate function myavg for type
    integer:
 
    
@@ -62,13 +62,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP AGGREGATE statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER AGGREGATE, CREATE AGGREGATE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropcast.html b/docs/en_US/pg/sql-dropcast.html
index 7e42029fa1..60a7268fe3 100644
--- a/docs/en_US/pg/sql-dropcast.html
+++ b/docs/en_US/pg/sql-dropcast.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    DROP CAST — remove a cast
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP CAST [ IF EXISTS ] (sourcetype AS targettype) [ CASCADE | RESTRICT ]
    
 
    
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the cast does not exist. A notice is issued 
@@ -65,7 +65,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE CAST
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropconversion.html b/docs/en_US/pg/sql-dropconversion.html
index 02fcdaaf43..2db3a26261 100644
--- a/docs/en_US/pg/sql-dropconversion.html
+++ b/docs/en_US/pg/sql-dropconversion.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    DROP CONVERSION — remove a conversion
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP CONVERSION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
    
 
    
@@ -28,7 +28,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
           Do not throw an error if the conversion does not exist. 
@@ -61,7 +61,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER CONVERSION, CREATE CONVERSION
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropdatabase.html b/docs/en_US/pg/sql-dropdatabase.html
index 2ed0ffb0cd..d7ddbf8fd1 100644
--- a/docs/en_US/pg/sql-dropdatabase.html
+++ b/docs/en_US/pg/sql-dropdatabase.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP DATABASE — remove a database
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP DATABASE [ IF EXISTS ] name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP DATABASE drops a database. It removes the
    catalog entries for the database and deletes the directory
    containing the data.  It can only be executed by the database owner.
@@ -34,7 +34,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the database does not exist. A notice is issued 
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        DROP DATABASE cannot be executed inside a transaction
     block.
    
    
@@ -57,12 +57,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP DATABASE statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE DATABASE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropdomain.html b/docs/en_US/pg/sql-dropdomain.html
index 8838589536..70f59aad52 100644
--- a/docs/en_US/pg/sql-dropdomain.html
+++ b/docs/en_US/pg/sql-dropdomain.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    DROP DOMAIN — remove a domain
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP DOMAIN [IF EXISTS ] name [, ...]  [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP DOMAIN will remove a domain.  Only the
    owner of a domain can remove it.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the domain does not exist. A notice is issued 
diff --git a/docs/en_US/pg/sql-dropfunction.html b/docs/en_US/pg/sql-dropfunction.html
index c37351af42..29561ed94a 100644
--- a/docs/en_US/pg/sql-dropfunction.html
+++ b/docs/en_US/pg/sql-dropfunction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    DROP FUNCTION — remove a function
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP FUNCTION [ IF EXISTS ] name ( [ [ argmode ] [ argname ] argtype [, ...] ] )
     [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP FUNCTION removes the definition of an existing
    function. To execute this command the user must be the
    owner of the function. The argument types to the
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the function does not exist. A notice is issued 
@@ -86,7 +86,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE FUNCTION, ALTER FUNCTION
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropgroup.html b/docs/en_US/pg/sql-dropgroup.html
index d0c61b21a6..311cc90562 100644
--- a/docs/en_US/pg/sql-dropgroup.html
+++ b/docs/en_US/pg/sql-dropgroup.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,24 +17,24 @@
 
    Name
    
 
    DROP GROUP — remove a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP GROUP [ IF EXISTS ] name [, ...]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP GROUP is now an alias for
    DROP ROLE,
    which see for more information.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP GROUP statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DROP ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropindex.html b/docs/en_US/pg/sql-dropindex.html
index 2897b4927c..6e87277a4d 100644
--- a/docs/en_US/pg/sql-dropindex.html
+++ b/docs/en_US/pg/sql-dropindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    DROP INDEX — remove an index
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP INDEX [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP INDEX drops an existing index from the database
    system. To execute this command you must be the owner of
    the index.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the index does not exist. A notice is issued 
@@ -48,7 +48,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       This command will remove the index title_idx:
 
 
    
@@ -57,14 +57,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       DROP INDEX is a
    PostgreSQL language extension.  There
    are no provisions for indexes in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE INDEX
 
    
 
    
diff --git a/docs/en_US/pg/sql-droplanguage.html b/docs/en_US/pg/sql-droplanguage.html
index 6ad8392f2d..d70e24be85 100644
--- a/docs/en_US/pg/sql-droplanguage.html
+++ b/docs/en_US/pg/sql-droplanguage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    DROP LANGUAGE — remove a procedural language
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP LANGUAGE will remove the definition
    of the previously registered procedural language called
    name.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the function does not exist. A notice is issued 
@@ -50,7 +50,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       This command removes the procedural language
    plsample:
 
@@ -60,13 +60,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP LANGUAGE statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER LANGUAGE, CREATE LANGUAGE, droplang
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropopclass.html b/docs/en_US/pg/sql-dropopclass.html
index 59b1379cdf..ef99aad161 100644
--- a/docs/en_US/pg/sql-dropopclass.html
+++ b/docs/en_US/pg/sql-dropopclass.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    DROP OPERATOR CLASS — remove an operator class
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP OPERATOR CLASS [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP OPERATOR CLASS drops an existing operator class.
    To execute this command you must be the owner of the operator class.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the operator class does not exist. A notice is issued 
@@ -50,7 +50,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Remove the B-tree operator class widget_ops:
 
 
    
@@ -63,13 +63,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP OPERATOR CLASS statement in the
    SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER OPERATOR CLASS, CREATE OPERATOR CLASS
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropoperator.html b/docs/en_US/pg/sql-dropoperator.html
index ebe9cc753a..a760f43b01 100644
--- a/docs/en_US/pg/sql-dropoperator.html
+++ b/docs/en_US/pg/sql-dropoperator.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    DROP OPERATOR — remove an operator
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP OPERATOR [ IF EXISTS ] name ( { lefttype | NONE } , { righttype | NONE } ) [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP OPERATOR drops an existing operator from
    the database system.  To execute this command you must be the owner
    of the operator.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the operator does not exist. A notice is issued 
@@ -56,7 +56,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Remove the power operator a^b for type integer:
 
    
 
    DROP OPERATOR ^ (integer, integer);
    
@@ -76,12 +76,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP OPERATOR statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE OPERATOR, ALTER OPERATOR
 
    
 
    
diff --git a/docs/en_US/pg/sql-droprole.html b/docs/en_US/pg/sql-droprole.html
index 60d1fb38e5..a8a6a1db41 100644
--- a/docs/en_US/pg/sql-droprole.html
+++ b/docs/en_US/pg/sql-droprole.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP ROLE — remove a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP ROLE [ IF EXISTS ] name [, ...]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP ROLE removes the specified role(s).
    To drop a superuser role, you must be a superuser yourself;
    to drop non-superuser roles, you must have CREATEROLE
@@ -42,7 +42,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the role does not exist. A notice is issued 
@@ -54,14 +54,14 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       PostgreSQL includes a program dropuser that has the
    same functionality as this command (in fact, it calls this command)
    but can be run from the command shell.
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To drop a role:
 
    
 
    DROP ROLE jonathan;
    
@@ -69,14 +69,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard defines DROP ROLE, but it allows
    only one role to be dropped at a time, and it specifies different
    privilege requirements than PostgreSQL uses.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE ROLE, ALTER ROLE, SET ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-droprule.html b/docs/en_US/pg/sql-droprule.html
index 3ccd90b506..1c32fa77e4 100644
--- a/docs/en_US/pg/sql-droprule.html
+++ b/docs/en_US/pg/sql-droprule.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,17 +17,17 @@
 
    Name
    
 
    DROP RULE — remove a rewrite rule
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP RULE [ IF EXISTS ] name ON relation [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP RULE drops a rewrite rule.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the rule does not exist. A notice is issued 
@@ -50,7 +50,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To drop the rewrite rule newrule:
 
 
    
@@ -59,12 +59,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no DROP RULE statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE RULE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropschema.html b/docs/en_US/pg/sql-dropschema.html
index 3d130d59aa..03546a4e0a 100644
--- a/docs/en_US/pg/sql-dropschema.html
+++ b/docs/en_US/pg/sql-dropschema.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP SCHEMA — remove a schema
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP SCHEMA [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP SCHEMA removes schemas from the database.
   
    
 
       A schema can only be dropped by its owner or a superuser.  Note that
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the schema does not exist. A notice is issued 
@@ -51,7 +51,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To remove schema mystuff from the database,
    along with everything it contains:
 
@@ -61,7 +61,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       DROP SCHEMA is fully conforming with the SQL
    standard, except that the standard only allows one schema to be
    dropped per command, and apart from the 
@@ -70,7 +70,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER SCHEMA, CREATE SCHEMA
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropsequence.html b/docs/en_US/pg/sql-dropsequence.html
index 7ed640bf4d..0bebb650af 100644
--- a/docs/en_US/pg/sql-dropsequence.html
+++ b/docs/en_US/pg/sql-dropsequence.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,17 +17,17 @@
 
    Name
    
 
    DROP SEQUENCE — remove a sequence
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP SEQUENCE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP SEQUENCE removes sequence number generators.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the sequence does not exist. A notice is issued 
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To remove the sequence serial:
 
 
    
@@ -55,7 +55,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       DROP SEQUENCE conforms to the SQL
    standard, except that the standard only allows one
    sequence to be dropped per command, and apart from the 
@@ -64,7 +64,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE SEQUENCE, ALTER SEQUENCE
 
    
 
    
diff --git a/docs/en_US/pg/sql-droptable.html b/docs/en_US/pg/sql-droptable.html
index 9af8753a4c..2f59ba53a1 100644
--- a/docs/en_US/pg/sql-droptable.html
+++ b/docs/en_US/pg/sql-droptable.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP TABLE — remove a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP TABLE removes tables from the database.
    Only its owner may destroy a table.  To empty a table of rows
    without destroying the table, use DELETE or TRUNCATE.
@@ -37,7 +37,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the table does not exist. A notice is issued 
@@ -57,7 +57,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To destroy two tables, films and 
    distributors:
 
@@ -67,7 +67,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command conforms to the SQL standard, except that the standard only
    allows one table to be dropped per command, and apart from the 
    IF EXISTS option, which is a PostgreSQL 
@@ -75,7 +75,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ALTER TABLE, CREATE TABLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-droptablespace.html b/docs/en_US/pg/sql-droptablespace.html
index 3f58beb274..8f75ff10fd 100644
--- a/docs/en_US/pg/sql-droptablespace.html
+++ b/docs/en_US/pg/sql-droptablespace.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    DROP TABLESPACE — remove a tablespace
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP TABLESPACE [ IF EXISTS ] tablespacename
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP TABLESPACE removes a tablespace from the system.
   
    
 
       A tablespace can only be dropped by its owner or a superuser.
@@ -33,7 +33,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the tablespace does not exist. A notice is issued 
@@ -45,12 +45,12 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        DROP TABLESPACE cannot be executed inside a transaction block.
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To remove tablespace mystuff from the system:
 
    
 
    DROP TABLESPACE mystuff;
    
@@ -58,13 +58,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       DROP TABLESPACE is a PostgreSQL
    extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE TABLESPACE, ALTER TABLESPACE
 
    
 
    
diff --git a/docs/en_US/pg/sql-droptrigger.html b/docs/en_US/pg/sql-droptrigger.html
index 222a8ec207..0c197227c6 100644
--- a/docs/en_US/pg/sql-droptrigger.html
+++ b/docs/en_US/pg/sql-droptrigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    DROP TRIGGER — remove a trigger
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP TRIGGER [ IF EXISTS ] name ON table [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP TRIGGER will remove an existing
    trigger definition. To execute this command, the current
    user must be the owner of the table for which the trigger is defined.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the trigger does not exist. A notice is issued 
@@ -71,7 +71,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE TRIGGER
 
    
 
    
diff --git a/docs/en_US/pg/sql-droptype.html b/docs/en_US/pg/sql-droptype.html
index 8efc51aa65..cf0b914169 100644
--- a/docs/en_US/pg/sql-droptype.html
+++ b/docs/en_US/pg/sql-droptype.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    DROP TYPE — remove a data type
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP TYPE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP TYPE will remove a user-defined data type.
    Only the owner of a type can remove it.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the type does not exist. A notice is issued 
diff --git a/docs/en_US/pg/sql-dropuser.html b/docs/en_US/pg/sql-dropuser.html
index 011fdfa62d..598d2099a6 100644
--- a/docs/en_US/pg/sql-dropuser.html
+++ b/docs/en_US/pg/sql-dropuser.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,26 +17,26 @@
 
    Name
    
 
    DROP USER — remove a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP USER [ IF EXISTS ] name [, ...]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP USER is now an alias for
    DROP ROLE,
    which see for more information.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The DROP USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DROP ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-dropview.html b/docs/en_US/pg/sql-dropview.html
index c7f9f34cce..fdc2c47277 100644
--- a/docs/en_US/pg/sql-dropview.html
+++ b/docs/en_US/pg/sql-dropview.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    DROP VIEW — remove a view
    
 
    
-
    
+
    
 
    Synopsis
    
 
    DROP VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       DROP VIEW drops an existing view.  To execute
    this command you must be the owner of the view.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    IF EXISTS
    
 
          Do not throw an error if the view does not exist. A notice is issued 
@@ -48,7 +48,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       This command will remove the view called kinds:
 
    
 
    DROP VIEW kinds;
    
@@ -56,7 +56,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command conforms to the SQL standard, except that the standard only
    allows one view to be dropped per command, and apart from the 
    IF EXISTS option, which is a PostgreSQL 
@@ -64,7 +64,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE VIEW
 
    
 
    
diff --git a/docs/en_US/pg/sql-end.html b/docs/en_US/pg/sql-end.html
index a2b108157a..34d816b9ef 100644
--- a/docs/en_US/pg/sql-end.html
+++ b/docs/en_US/pg/sql-end.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    END — commit the current transaction
    
 
    
-
    
+
    
 
    Synopsis
    
 
    END [ WORK | TRANSACTION ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       END commits the current transaction. All changes
    made by the transaction become visible to others and are guaranteed
    to be durable if a crash occurs.  This command is a
@@ -31,7 +31,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 WORK

    TRANSACTION
@@ -41,7 +41,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use ROLLBACK to
    abort a transaction.
   
    
@@ -50,7 +50,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To commit the current transaction and make all changes permanent:
 
    
 
    END;
    
@@ -58,14 +58,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       END is a PostgreSQL
    extension that provides functionality equivalent to COMMIT, which is
    specified in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, ROLLBACK
 
    
 
    
diff --git a/docs/en_US/pg/sql-execute.html b/docs/en_US/pg/sql-execute.html
index d99d2df051..165b820028 100644
--- a/docs/en_US/pg/sql-execute.html
+++ b/docs/en_US/pg/sql-execute.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    EXECUTE — execute a prepared statement
    
 
    
-
    
+
    
 
    Synopsis
    
 
    EXECUTE name [ (parameter [, ...] ) ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       EXECUTE is used to execute a previously prepared
    statement. Since prepared statements only exist for the duration of a
    session, the prepared statement must have been created by a
@@ -41,7 +41,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name of the prepared statement to execute.
@@ -55,18 +55,18 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       The command tag returned by EXECUTE
    is that of the prepared statement, and not EXECUTE.
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
        Examples are given in the Examples section of the PREPARE documentation.
    
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard includes an EXECUTE statement,
    but it is only for use in embedded SQL.  This version of the
    EXECUTE statement also uses a somewhat different
@@ -74,7 +74,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DEALLOCATE, PREPARE
 
    
 
    
diff --git a/docs/en_US/pg/sql-explain.html b/docs/en_US/pg/sql-explain.html
index 0b5fac7663..10c17184cf 100644
--- a/docs/en_US/pg/sql-explain.html
+++ b/docs/en_US/pg/sql-explain.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    EXPLAIN — show the execution plan of a statement
    
 
    
-
    
+
    
 
    Synopsis
    
 
    EXPLAIN [ ANALYZE ] [ VERBOSE ] statement
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       This command displays the execution plan that the
    PostgreSQL planner generates for the
    supplied statement.  The execution plan shows how the table(s)
@@ -69,7 +69,7 @@ 
    Important
    
 
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    ANALYZE
    
 
          Carry out the command and show the actual run times.
@@ -89,7 +89,7 @@ 
    Important
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       There is only sparse documentation on the optimizer's use of cost
    information in PostgreSQL.  Refer to
    Section 13.1, “Using EXPLAIN” for more information.
@@ -112,7 +112,7 @@ 
    Important
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To show the plan for a simple query on a table with a single
    integer column and 10000 rows:
 
@@ -184,12 +184,12 @@ 
    Important
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no EXPLAIN statement defined in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 ANALYZE
 
    
 
    
diff --git a/docs/en_US/pg/sql-expressions.html b/docs/en_US/pg/sql-expressions.html
index be3de994b7..cb135f9dc6 100644
--- a/docs/en_US/pg/sql-expressions.html
+++ b/docs/en_US/pg/sql-expressions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 4.2. Value Expressions
    
-
       Value expressions are used in a variety of contexts, such
+
       Value expressions are used in a variety of contexts, such
    as in the target list of the SELECT command, as
    new column values in INSERT or
    UPDATE, or in search conditions in a number of
@@ -57,7 +57,7 @@
      
    
 
  •       Another value expression in parentheses, useful to group
       subexpressions and override
-      precedence.
+      precedence.
      
    • 
 
    
 
    
@@ -73,8 +73,8 @@
   
    
 
    
 
    
-4.2.1. Column References
    
-
        A column can be referenced in the form
+4.2.1. Column References
    
+
        A column can be referenced in the form
 
    
 
    correlation.columnname
    
 
    
@@ -91,8 +91,8 @@
 
    
 
    
 
    
-4.2.2. Positional Parameters
    
-
        A positional parameter reference is used to indicate a value
+4.2.2. Positional Parameters
    
+
        A positional parameter reference is used to indicate a value
     that is supplied externally to an SQL statement.  Parameters are
     used in SQL function definitions and in prepared queries.  Some
     client libraries also support specifying data values separately
@@ -118,8 +118,8 @@
 
    
 
    
 
    
-4.2.3. Subscripts
    
-
        If an expression yields a value of an array type, then a specific
+4.2.3. Subscripts
    
+
        If an expression yields a value of an array type, then a specific
     element of the array value can be extracted by writing
 
    
 
    expression[subscript]
    
@@ -153,8 +153,8 @@
 
 
    
 
    
-4.2.4. Field Selection
    
-
        If an expression yields a value of a composite type (row type), then a
+4.2.4. Field Selection
    
+
        If an expression yields a value of a composite type (row type), then a
     specific field of the row can be extracted by writing
 
    
 
    expression.fieldname
    
@@ -177,8 +177,8 @@
 
 
    
 
    
-4.2.5. Operator Invocations
    
-
        There are three possible syntaxes for an operator invocation:
+4.2.5. Operator Invocations
    
+
        There are three possible syntaxes for an operator invocation:
     
    
 
    
 

 
    
 Conversion Name
-        [a]
+        [a]
        
 Source Encoding
 Destination EncodingUTF8
 
    
 
    [a]           The conversion names follow a standard naming scheme: The
+
    [a]           The conversion names follow a standard naming scheme: The
           official name of the source encoding with all
           non-alphanumeric characters replaced by underscores followed
           by _to_ followed by the equally processed
diff --git a/docs/en_US/pg/functions-subquery.html b/docs/en_US/pg/functions-subquery.html
index 1d7b556854..90170e9bc2 100644
--- a/docs/en_US/pg/functions-subquery.html
+++ b/docs/en_US/pg/functions-subquery.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,14 +14,14 @@
 
    
 
    
 9.16. Subquery Expressions
    
-
       This section describes the SQL-compliant subquery
+
       This section describes the SQL-compliant subquery
    expressions available in PostgreSQL.
    All of the expression forms documented in this section return
    Boolean (true/false) results.
   
    
 
    
 
    
-9.16.1. EXISTS
    
+9.16.1. EXISTS
    
 
    EXISTS (subquery)
    
 
       The argument of EXISTS is an arbitrary SELECT statement,
    or subquery.  The
@@ -57,7 +57,7 @@
 
 
    
 
    
-9.16.2. IN
    
+9.16.2. IN
    
 
    expression IN (subquery)
    
 
       The right-hand side is a parenthesized
    subquery, which must return exactly one column.  The left-hand expression
@@ -97,7 +97,7 @@
 
 
    
 
    
-9.16.3. NOT IN
    
+9.16.3. NOT IN
    
 
    expression NOT IN (subquery)
    
 
       The right-hand side is a parenthesized
    subquery, which must return exactly one column.  The left-hand expression
@@ -137,7 +137,7 @@
 
 
    
 
    
-9.16.4. ANY/SOME
    
+9.16.4. ANY/SOME
    
 
    expression operator ANY (subquery)
 expression operator SOME (subquery)
    
 
       The right-hand side is a parenthesized
@@ -184,7 +184,7 @@
 
 
    
 
    
-9.16.5. ALL
    
+9.16.5. ALL
    
 
    expression operator ALL (subquery)
    
 
       The right-hand side is a parenthesized
    subquery, which must return exactly one column.  The left-hand expression
@@ -224,8 +224,8 @@
 
 
    
 
    
-9.16.6. Row-wise Comparison
    
-
    row_constructor operator (subquery)
    
+9.16.6. Row-wise Comparison
    
+
    row_constructor operator (subquery)
    
 
       The left-hand side is a row constructor,
    as described in Section 4.2.11, “Row Constructors”.
    The right-hand side is a parenthesized subquery, which must return exactly
diff --git a/docs/en_US/pg/functions.html b/docs/en_US/pg/functions.html
index 75c5b89c0b..9ff7414589 100644
--- a/docs/en_US/pg/functions.html
+++ b/docs/en_US/pg/functions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -43,28 +43,28 @@
 
    9.12. Sequence Manipulation Functions
    
 
    9.13. Conditional Expressions
    
 
    
-
    9.13.1. CASE
    
-
    9.13.2. COALESCE
    
-
    9.13.3. NULLIF
    
-
    9.13.4. GREATEST and LEAST
    
+
    9.13.1. CASE
    
+
    9.13.2. COALESCE
    
+
    9.13.3. NULLIF
    
+
    9.13.4. GREATEST and LEAST
    
 
    
 
    9.14. Array Functions and Operators
    
 
    9.15. Aggregate Functions
    
 
    9.16. Subquery Expressions
    
 
    
-
    9.16.1. EXISTS
    
-
    9.16.2. IN
    
-
    9.16.3. NOT IN
    
-
    9.16.4. ANY/SOME
    
-
    9.16.5. ALL
    
-
    9.16.6. Row-wise Comparison
    
+
    9.16.1. EXISTS
    
+
    9.16.2. IN
    
+
    9.16.3. NOT IN
    
+
    9.16.4. ANY/SOME
    
+
    9.16.5. ALL
    
+
    9.16.6. Row-wise Comparison
    
 
    
 
    9.17. Row and Array Comparisons
    
 
    
-
    9.17.1. IN
    
-
    9.17.2. NOT IN
    
-
    9.17.3. ANY/SOME (array)
    
-
    9.17.4. ALL (array)
    
+
    9.17.1. IN
    
+
    9.17.2. NOT IN
    
+
    9.17.3. ANY/SOME (array)
    
+
    9.17.4. ALL (array)
    
 
    9.17.5. Row-wise Comparison
    
 
    
 
    9.18. Set Returning Functions
    
@@ -72,7 +72,7 @@
 
    9.20. System Administration Functions
    
 
 
-
       PostgreSQL provides a large number of
+
       PostgreSQL provides a large number of
    functions and operators for the built-in data types.  Users can also
    define their own functions and operators, as described in
    Part V, “Server Programming”.  The
@@ -94,19 +94,19 @@
 
    
 
    
 9.1. Logical Operators
    
-
        The usual logical operators are available:
+
        The usual logical operators are available:
 
-    
+    
 
-    
+    
 
-    
+    
 
-    
+    
 
-    
+    
 
-    
+    
 
     
    
 
diff --git a/docs/en_US/pg/geqo-biblio.html b/docs/en_US/pg/geqo-biblio.html
index f3cd8e0d01..b1a4a9c36f 100644
--- a/docs/en_US/pg/geqo-biblio.html
+++ b/docs/en_US/pg/geqo-biblio.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/geqo-intro2.html b/docs/en_US/pg/geqo-intro2.html
index d45c2802fb..f873bc1cde 100644
--- a/docs/en_US/pg/geqo-intro2.html
+++ b/docs/en_US/pg/geqo-intro2.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/geqo-pg-intro.html b/docs/en_US/pg/geqo-pg-intro.html
index 4bac41aefe..0fa66ba8f0 100644
--- a/docs/en_US/pg/geqo-pg-intro.html
+++ b/docs/en_US/pg/geqo-pg-intro.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/geqo.html b/docs/en_US/pg/geqo.html
index e15ce21107..61ddf5da96 100644
--- a/docs/en_US/pg/geqo.html
+++ b/docs/en_US/pg/geqo.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin-examples.html b/docs/en_US/pg/gin-examples.html
index b7e1b0979e..baf54daedb 100644
--- a/docs/en_US/pg/gin-examples.html
+++ b/docs/en_US/pg/gin-examples.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin-extensibility.html b/docs/en_US/pg/gin-extensibility.html
index 45c28075ae..5acefd2753 100644
--- a/docs/en_US/pg/gin-extensibility.html
+++ b/docs/en_US/pg/gin-extensibility.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin-implementation.html b/docs/en_US/pg/gin-implementation.html
index 1839fd24cd..982f127a4b 100644
--- a/docs/en_US/pg/gin-implementation.html
+++ b/docs/en_US/pg/gin-implementation.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin-limit.html b/docs/en_US/pg/gin-limit.html
index 6acd39565b..0503ea84a4 100644
--- a/docs/en_US/pg/gin-limit.html
+++ b/docs/en_US/pg/gin-limit.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin-tips.html b/docs/en_US/pg/gin-tips.html
index 8bcb1eb150..3fff7bc800 100644
--- a/docs/en_US/pg/gin-tips.html
+++ b/docs/en_US/pg/gin-tips.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/gin.html b/docs/en_US/pg/gin.html
index fdcc19a647..bd99941c54 100644
--- a/docs/en_US/pg/gin.html
+++ b/docs/en_US/pg/gin.html
@@ -5,7 +5,7 @@
 
-
+
@@ -25,7 +25,7 @@
 
    51.6. Examples
    
-
    
+
    
 
    
 51.1. Introduction
    
 
       GIN stands for Generalized Inverted Index.  It is
diff --git a/docs/en_US/pg/gist-examples.html b/docs/en_US/pg/gist-examples.html
index ff3954cdca..ffb9b42b5f 100644
--- a/docs/en_US/pg/gist-examples.html
+++ b/docs/en_US/pg/gist-examples.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/gist-extensibility.html b/docs/en_US/pg/gist-extensibility.html
index 1e2744300e..80c6138d84 100644
--- a/docs/en_US/pg/gist-extensibility.html
+++ b/docs/en_US/pg/gist-extensibility.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/gist-implementation.html b/docs/en_US/pg/gist-implementation.html
index baffe0a201..a14bfcae08 100644
--- a/docs/en_US/pg/gist-implementation.html
+++ b/docs/en_US/pg/gist-implementation.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/gist-recovery.html b/docs/en_US/pg/gist-recovery.html
index f4c3410b1a..4464d21f27 100644
--- a/docs/en_US/pg/gist-recovery.html
+++ b/docs/en_US/pg/gist-recovery.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/gist.html b/docs/en_US/pg/gist.html
index 3995688af4..e8a785a53c 100644
--- a/docs/en_US/pg/gist.html
+++ b/docs/en_US/pg/gist.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
 
    50.5. Crash Recovery
    
 
 
    
-
    
+
    
 
    
 50.1. Introduction
    
 
       GiST stands for Generalized Search Tree.  It is a
diff --git a/docs/en_US/pg/high-availability.html b/docs/en_US/pg/high-availability.html
index b1215c0995..5929dd9f98 100644
--- a/docs/en_US/pg/high-availability.html
+++ b/docs/en_US/pg/high-availability.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 Chapter 24. High Availability and Load Balancing
    
-
      Database servers can work together to allow a second server to
+
      Database servers can work together to allow a second server to
   take over quickly if the primary server fails (high
   availability), or to allow several computers to serve the same
   data (load balancing).  Ideally, database servers could work
diff --git a/docs/en_US/pg/history.html b/docs/en_US/pg/history.html
index fec7387c9f..2cc0d6fdc9 100644
--- a/docs/en_US/pg/history.html
+++ b/docs/en_US/pg/history.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 1.2. A Brief History of PostgreSQL
    
-
      The object-relational database management system now known as
+
      The object-relational database management system now known as
   PostgreSQL is derived from the
   POSTGRES package written at the
   University of California at Berkeley.  With over a decade of
@@ -24,7 +24,7 @@
 
    
 
    
 1.2.1. The Berkeley POSTGRES Project
    
-
       The POSTGRES project, led by Professor
+
       The POSTGRES project, led by Professor
    Michael Stonebraker, was sponsored by the Defense Advanced Research
    Projects Agency (DARPA), the Army Research
    Office (ARO), the National Science Foundation
@@ -75,7 +75,7 @@
 
    
 
    
 1.2.2. Postgres95
    
-
       In 1994, Andrew Yu and Jolly Chen added a SQL language interpreter
+
       In 1994, Andrew Yu and Jolly Chen added a SQL language interpreter
    to POSTGRES.  Under a new name,
    Postgres95 was subsequently released to
    the web to find its own way in the world as an open-source
@@ -137,7 +137,7 @@
 
    
 
    
 
    
-1.2.3. PostgreSQL
    
+1.2.3. PostgreSQL
    
 
       By 1996, it became clear that the name “Postgres95”
    would not stand the test of time. We chose a new name,
    PostgreSQL, to reflect the relationship
diff --git a/docs/en_US/pg/index-cost-estimation.html b/docs/en_US/pg/index-cost-estimation.html
index d2604a212f..daa041ecdb 100644
--- a/docs/en_US/pg/index-cost-estimation.html
+++ b/docs/en_US/pg/index-cost-estimation.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -120,7 +120,7 @@
    any one scan of the index.
   
    
 
    
-
    Cost Estimation
    
+
    Cost Estimation
    
 
        A typical cost estimator will proceed as follows:
    
    
 
      
diff --git a/docs/en_US/pg/index-functions.html b/docs/en_US/pg/index-functions.html
index 99a1a4c90c..e3dbe12399 100644
--- a/docs/en_US/pg/index-functions.html
+++ b/docs/en_US/pg/index-functions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/index-locking.html b/docs/en_US/pg/index-locking.html
index 00fe898033..fb8cc06a36 100644
--- a/docs/en_US/pg/index-locking.html
+++ b/docs/en_US/pg/index-locking.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/index-scanning.html b/docs/en_US/pg/index-scanning.html
index 2dba3771a8..0c99f78272 100644
--- a/docs/en_US/pg/index-scanning.html
+++ b/docs/en_US/pg/index-scanning.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/index-unique-checks.html b/docs/en_US/pg/index-unique-checks.html
index a1cdc69aef..4ab4ae9fcd 100644
--- a/docs/en_US/pg/index-unique-checks.html
+++ b/docs/en_US/pg/index-unique-checks.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/index.html b/docs/en_US/pg/index.html
index 8ec2fabdc5..fe2aafea01 100644
--- a/docs/en_US/pg/index.html
+++ b/docs/en_US/pg/index.html
@@ -1,11 +1,11 @@
 
 
 
-PostgreSQL 8.2.0 Documentation
+PostgreSQL 8.2.1 Documentation
 
 
 
-
+
 
 
 
@@ -13,7 +13,7 @@
 
      
 
      
 
      
-PostgreSQL 8.2.0 Documentation
      
+PostgreSQL 8.2.1 Documentation
      
 
      The PostgreSQL Global Development Group
      
 
      Copyright © 1996-2006 The PostgreSQL Global Development Group
      
 
@@ -30,15 +30,15 @@
 
      
 
      1.2.1. The Berkeley POSTGRES Project
      
 
      1.2.2. Postgres95
      
-
      1.2.3. PostgreSQL
      
+
      1.2.3. PostgreSQL
      
 
      
 
      1.3. Conventions
      
 
      1.4. Further Information
      
 
      1.5. Bug Reporting Guidelines
      
 
      
-
      1.5.1. Identifying Bugs
      
-
      1.5.2. What to report
      
-
      1.5.3. Where to report bugs
      
+
      1.5.1. Identifying Bugs
      
+
      1.5.2. What to report
      
+
      1.5.3. Where to report bugs
      
 
      
 
 
      I. Tutorial
      
@@ -81,18 +81,18 @@
 
      4.1.1. Identifiers and Key Words
      
 
      4.1.2. Constants
      
 
      4.1.3. Operators
      
-
      4.1.4. Special Characters
      
+
      4.1.4. Special Characters
      
 
      4.1.5. Comments
      
 
      4.1.6. Lexical Precedence
      
 
 
      4.2. Value Expressions
      
 
      
-
      4.2.1. Column References
      
-
      4.2.2. Positional Parameters
      
-
      4.2.3. Subscripts
      
-
      4.2.4. Field Selection
      
-
      4.2.5. Operator Invocations
      
-
      4.2.6. Function Calls
      
+
      4.2.1. Column References
      
+
      4.2.2. Positional Parameters
      
+
      4.2.3. Subscripts
      
+
      4.2.4. Field Selection
      
+
      4.2.5. Operator Invocations
      
+
      4.2.6. Function Calls
      
 
      4.2.7. Aggregate Expressions
      
 
      4.2.8. Type Casts
      
 
      4.2.9. Scalar Subqueries
      
@@ -107,23 +107,23 @@
 
      5.2. Default Values
      
 
      5.3. Constraints
      
 
      
-
      5.3.1. Check Constraints
      
-
      5.3.2. Not-Null Constraints
      
-
      5.3.3. Unique Constraints
      
-
      5.3.4. Primary Keys
      
+
      5.3.1. Check Constraints
      
+
      5.3.2. Not-Null Constraints
      
+
      5.3.3. Unique Constraints
      
+
      5.3.4. Primary Keys
      
 
      5.3.5. Foreign Keys
      
 
      
 
      5.4. System Columns
      
 
      5.5. Modifying Tables
      
 
      
-
      5.5.1. Adding a Column
      
-
      5.5.2. Removing a Column
      
-
      5.5.3. Adding a Constraint
      
-
      5.5.4. Removing a Constraint
      
-
      5.5.5. Changing a Column's Default Value
      
-
      5.5.6. Changing a Column's Data Type
      
-
      5.5.7. Renaming a Column
      
-
      5.5.8. Renaming a Table
      
+
      5.5.1. Adding a Column
      
+
      5.5.2. Removing a Column
      
+
      5.5.3. Adding a Constraint
      
+
      5.5.4. Removing a Constraint
      
+
      5.5.5. Changing a Column's Default Value
      
+
      5.5.6. Changing a Column's Data Type
      
+
      5.5.7. Renaming a Column
      
+
      5.5.8. Renaming a Table
      
 
      
 
      5.6. Privileges
      
 
      5.7. Schemas
      
@@ -197,12 +197,12 @@
 
      8.6. Boolean Type
      
 
      8.7. Geometric Types
      
 
      
-
      8.7.1. Points
      
-
      8.7.2. Line Segments
      
-
      8.7.3. Boxes
      
-
      8.7.4. Paths
      
-
      8.7.5. Polygons
      
-
      8.7.6. Circles
      
+
      8.7.1. Points
      
+
      8.7.2. Line Segments
      
+
      8.7.3. Boxes
      
+
      8.7.4. Paths
      
+
      8.7.5. Polygons
      
+
      8.7.6. Circles
      
 
      
 
      8.8. Network Address Types
      
 
      
@@ -214,20 +214,20 @@
 
      8.9. Bit String Types
      
 
      8.10. Arrays
      
 
      
-
      8.10.1. Declaration of Array Types
      
-
      8.10.2. Array Value Input
      
-
      8.10.3. Accessing Arrays
      
-
      8.10.4. Modifying Arrays
      
-
      8.10.5. Searching in Arrays
      
-
      8.10.6. Array Input and Output Syntax
      
+
      8.10.1. Declaration of Array Types
      
+
      8.10.2. Array Value Input
      
+
      8.10.3. Accessing Arrays
      
+
      8.10.4. Modifying Arrays
      
+
      8.10.5. Searching in Arrays
      
+
      8.10.6. Array Input and Output Syntax
      
 
      
 
      8.11. Composite Types
      
 
      
-
      8.11.1. Declaration of Composite Types
      
-
      8.11.2. Composite Value Input
      
-
      8.11.3. Accessing Composite Types
      
-
      8.11.4. Modifying Composite Types
      
-
      8.11.5. Composite Type Input and Output Syntax
      
+
      8.11.1. Declaration of Composite Types
      
+
      8.11.2. Composite Value Input
      
+
      8.11.3. Accessing Composite Types
      
+
      8.11.4. Modifying Composite Types
      
+
      8.11.5. Composite Type Input and Output Syntax
      
 
      
 
      8.12. Object Identifier Types
      
 
      8.13. Pseudo-Types
      
@@ -261,28 +261,28 @@
 
      9.12. Sequence Manipulation Functions
      
 
      9.13. Conditional Expressions
      
 
      
-
      9.13.1. CASE
      
-
      9.13.2. COALESCE
      
-
      9.13.3. NULLIF
      
-
      9.13.4. GREATEST and LEAST
      
+
      9.13.1. CASE
      
+
      9.13.2. COALESCE
      
+
      9.13.3. NULLIF
      
+
      9.13.4. GREATEST and LEAST
      
 
      
 
      9.14. Array Functions and Operators
      
 
      9.15. Aggregate Functions
      
 
      9.16. Subquery Expressions
      
 
      
-
      9.16.1. EXISTS
      
-
      9.16.2. IN
      
-
      9.16.3. NOT IN
      
-
      9.16.4. ANY/SOME
      
-
      9.16.5. ALL
      
-
      9.16.6. Row-wise Comparison
      
+
      9.16.1. EXISTS
      
+
      9.16.2. IN
      
+
      9.16.3. NOT IN
      
+
      9.16.4. ANY/SOME
      
+
      9.16.5. ALL
      
+
      9.16.6. Row-wise Comparison
      
 
      
 
      9.17. Row and Array Comparisons
      
 
      
-
      9.17.1. IN
      
-
      9.17.2. NOT IN
      
-
      9.17.3. ANY/SOME (array)
      
-
      9.17.4. ALL (array)
      
+
      9.17.1. IN
      
+
      9.17.2. NOT IN
      
+
      9.17.3. ANY/SOME (array)
      
+
      9.17.4. ALL (array)
      
 
      9.17.5. Row-wise Comparison
      
 
      
 
      9.18. Set Returning Functions
      
@@ -356,8 +356,8 @@
 
      14.5. Installation Procedure
      
 
      14.6. Post-Installation Setup
      
 
      
-
      14.6.1. Shared Libraries
      
-
      14.6.2. Environment Variables
      
+
      14.6.1. Shared Libraries
      
+
      14.6.2. Environment Variables
      
 
      
 
      14.7. Supported Platforms
      
 
      
@@ -374,8 +374,8 @@
 
      16.4. Managing Kernel Resources
      
 
      
 
      16.4.1. Shared Memory and Semaphores
      
-
      16.4.2. Resource Limits
      
-
      16.4.3. Linux Memory Overcommit
      
+
      16.4.2. Resource Limits
      
+
      16.4.3. Linux Memory Overcommit
      
 
      
 
      16.5. Shutting Down the Server
      
 
      16.6. Encryption Options
      
@@ -478,16 +478,16 @@
 
      
 
      21.1. Locale Support
      
 
      
-
      21.1.1. Overview
      
-
      21.1.2. Behavior
      
-
      21.1.3. Problems
      
+
      21.1.1. Overview
      
+
      21.1.2. Behavior
      
+
      21.1.3. Problems
      
 
      
 
      21.2. Character Set Support
      
 
      
 
      21.2.1. Supported Character Sets
      
-
      21.2.2. Setting the Character Set
      
-
      21.2.3. Automatic Character Set Conversion Between Server and Client
      
-
      21.2.4. Further Reading
      
+
      21.2.2. Setting the Character Set
      
+
      21.2.3. Automatic Character Set Conversion Between Server and Client
      
+
      21.2.4. Further Reading
      
 
      
 
      
 
      22. Routine Database Maintenance Tasks
      
@@ -541,7 +541,7 @@
 
      25.3. Viewing Locks
      
 
      25.4. Dynamic Tracing
      
 
      
-
      25.4.1. Compiling for Dynamic Trace
      
+
      25.4.1. Compiling for Dynamic Tracing
      
 
      25.4.2. Built-in Trace Points
      
 
      25.4.3. Using Trace Points
      
 
      25.4.4. Defining Trace Points
      
@@ -564,13 +564,13 @@
 
      28.1. Running the Tests
      
 
      28.2. Test Evaluation
      
 
      
-
      28.2.1. Error message differences
      
-
      28.2.2. Locale differences
      
-
      28.2.3. Date and time differences
      
-
      28.2.4. Floating-point differences
      
-
      28.2.5. Row ordering differences
      
-
      28.2.6. Insufficient stack depth
      
-
      28.2.7. The “random” test
      
+
      28.2.1. Error message differences
      
+
      28.2.2. Locale differences
      
+
      28.2.3. Date and time differences
      
+
      28.2.4. Floating-point differences
      
+
      28.2.5. Row ordering differences
      
+
      28.2.6. Insufficient stack depth
      
+
      28.2.7. The “random” test
      
 
      
 
      28.3. Variant Comparison Files
      
 
      
@@ -617,16 +617,16 @@
 
      30.2. Implementation Features
      
 
      30.3. Client Interfaces
      
 
      
-
      30.3.1. Creating a Large Object
      
-
      30.3.2. Importing a Large Object
      
-
      30.3.3. Exporting a Large Object
      
-
      30.3.4. Opening an Existing Large Object
      
-
      30.3.5. Writing Data to a Large Object
      
-
      30.3.6. Reading Data from a Large Object
      
-
      30.3.7. Seeking in a Large Object
      
-
      30.3.8. Obtaining the Seek Position of a Large Object
      
-
      30.3.9. Closing a Large Object Descriptor
      
-
      30.3.10. Removing a Large Object
      
+
      30.3.1. Creating a Large Object
      
+
      30.3.2. Importing a Large Object
      
+
      30.3.3. Exporting a Large Object
      
+
      30.3.4. Opening an Existing Large Object
      
+
      30.3.5. Writing Data to a Large Object
      
+
      30.3.6. Reading Data from a Large Object
      
+
      30.3.7. Seeking in a Large Object
      
+
      30.3.8. Obtaining the Seek Position of a Large Object
      
+
      30.3.9. Closing a Large Object Descriptor
      
+
      30.3.10. Removing a Large Object
      
 
      
 
      30.4. Server-Side Functions
      
 
      30.5. Example Program
      
@@ -640,41 +640,41 @@
 
      31.5. Choosing a Connection
      
 
      31.6. Using Host Variables
      
 
      
-
      31.6.1. Overview
      
-
      31.6.2. Declare Sections
      
-
      31.6.3. Different types of host variables
      
-
      31.6.4. SELECT INTO and FETCH INTO
      
-
      31.6.5. Indicators
      
+
      31.6.1. Overview
      
+
      31.6.2. Declare Sections
      
+
      31.6.3. Different types of host variables
      
+
      31.6.4. SELECT INTO and FETCH INTO
      
+
      31.6.5. Indicators
      
 
      
 
      31.7. Dynamic SQL
      
 
      31.8. pgtypes library
      
 
      
-
      31.8.1. The numeric type
      
-
      31.8.2. The date type
      
-
      31.8.3. The timestamp type
      
-
      31.8.4. The interval type
      
-
      31.8.5. The decimal type
      
-
      31.8.6. errno values of pgtypeslib 
      
-
      31.8.7. Special constants of pgtypeslib 
      
+
      31.8.1. The numeric type
      
+
      31.8.2. The date type
      
+
      31.8.3. The timestamp type
      
+
      31.8.4. The interval type
      
+
      31.8.5. The decimal type
      
+
      31.8.6. errno values of pgtypeslib 
      
+
      31.8.7. Special constants of pgtypeslib 
      
 
      
 
      31.9. Informix compatibility mode
      
 
      
-
      31.9.1. Additional embedded SQL statements
      
-
      31.9.2. Additional functions
      
-
      31.9.3. Additional constants
      
+
      31.9.1. Additional embedded SQL statements
      
+
      31.9.2. Additional functions
      
+
      31.9.3. Additional constants
      
 
      
 
      31.10. Using SQL Descriptor Areas
      
 
      31.11. Error Handling
      
 
      
-
      31.11.1. Setting Callbacks
      
-
      31.11.2. sqlca
      
-
      31.11.3. SQLSTATE vs SQLCODE
      
+
      31.11.1. Setting Callbacks
      
+
      31.11.2. sqlca
      
+
      31.11.3. SQLSTATE vs SQLCODE
      
 
      
 
      31.12. Preprocessor directives
      
 
      
-
      31.12.1. Including files
      
-
      31.12.2. The #define and #undef directives
      
-
      31.12.3. ifdef, ifndef, else, elif and endif directives
      
+
      31.12.1. Including files
      
+
      31.12.2. The #define and #undef directives
      
+
      31.12.3. ifdef, ifndef, else, elif and endif directives
      
 
      
 
      31.13. Processing Embedded SQL Programs
      
 
      31.14. Library Functions
      
@@ -738,21 +738,21 @@
 
      33.1. How Extensibility Works
      
 
      33.2. The PostgreSQL Type System
      
 
      
-
      33.2.1. Base Types
      
-
      33.2.2. Composite Types
      
-
      33.2.3. Domains
      
-
      33.2.4. Pseudo-Types
      
+
      33.2.1. Base Types
      
+
      33.2.2. Composite Types
      
+
      33.2.3. Domains
      
+
      33.2.4. Pseudo-Types
      
 
      33.2.5. Polymorphic Types
      
 
      
 
      33.3. User-Defined Functions
      
 
      33.4. Query Language (SQL) Functions
      
 
      
 
      33.4.1. SQL Functions on Base Types
      
-
      33.4.2. SQL Functions on Composite Types
      
+
      33.4.2. SQL Functions on Composite Types
      
 
      33.4.3. Functions with Output Parameters
      
 
      33.4.4. SQL Functions as Table Sources
      
-
      33.4.5. SQL Functions Returning Sets
      
-
      33.4.6. Polymorphic SQL Functions
      
+
      33.4.5. SQL Functions Returning Sets
      
+
      33.4.6. Polymorphic SQL Functions
      
 
      
 
      33.5. Function Overloading
      
 
      33.6. Function Volatility Categories
      
@@ -762,28 +762,28 @@
 
      
 
      33.9.1. Dynamic Loading
      
 
      33.9.2. Base Types in C-Language Functions
      
-
      33.9.3. Version 0 Calling Conventions
      
-
      33.9.4. Version 1 Calling Conventions
      
-
      33.9.5. Writing Code
      
+
      33.9.3. Version 0 Calling Conventions
      
+
      33.9.4. Version 1 Calling Conventions
      
+
      33.9.5. Writing Code
      
 
      33.9.6. Compiling and Linking Dynamically-Loaded Functions
      
 
      33.9.7. Extension Building Infrastructure
      
-
      33.9.8. Composite-Type Arguments
      
-
      33.9.9. Returning Rows (Composite Types)
      
+
      33.9.8. Composite-Type Arguments
      
+
      33.9.9. Returning Rows (Composite Types)
      
 
      33.9.10. Returning Sets
      
-
      33.9.11. Polymorphic Arguments and Return Types
      
-
      33.9.12. Shared Memory and LWLocks
      
+
      33.9.11. Polymorphic Arguments and Return Types
      
+
      33.9.12. Shared Memory and LWLocks
      
 
      
 
      33.10. User-Defined Aggregates
      
 
      33.11. User-Defined Types
      
 
      33.12. User-Defined Operators
      
 
      33.13. Operator Optimization Information
      
 
      
-
      33.13.1. COMMUTATOR
      
-
      33.13.2. NEGATOR
      
-
      33.13.3. RESTRICT
      
-
      33.13.4. JOIN
      
-
      33.13.5. HASHES
      
-
      33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
      
+
      33.13.1. COMMUTATOR
      
+
      33.13.2. NEGATOR
      
+
      33.13.3. RESTRICT
      
+
      33.13.4. JOIN
      
+
      33.13.5. HASHES
      
+
      33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
      
 
      
 
      33.14. Interfacing Extensions To Indexes
      
 
      
@@ -809,13 +809,13 @@
 
      35.2. Views and the Rule System
      
 
      
 
      35.2.1. How SELECT Rules Work
      
-
      35.2.2. View Rules in Non-SELECT Statements
      
-
      35.2.3. The Power of Views in PostgreSQL
      
+
      35.2.2. View Rules in Non-SELECT Statements
      
+
      35.2.3. The Power of Views in PostgreSQL
      
 
      35.2.4. Updating a View
      
 
      
 
      35.3. Rules on INSERT, UPDATE, and DELETE
      
 
      
-
      35.3.1. How Update Rules Work
      
+
      35.3.1. How Update Rules Work
      
 
      35.3.2. Cooperation with Views
      
 
      
 
      35.4. Rules and Privileges
      
@@ -870,7 +870,7 @@
 
      37.10. Trigger Procedures
      
 
      37.11. Porting from Oracle PL/SQL
      
 
      
-
      37.11.1. Porting Examples
      
+
      37.11.1. Porting Examples
      
 
      37.11.2. Other Things to Watch For
      
 
      37.11.3. Appendix
      
 
      
@@ -1339,12 +1339,12 @@
 
      42.2. How Connections are Established
      
 
      42.3. The Parser Stage
      
 
      
-
      42.3.1. Parser
      
-
      42.3.2. Transformation Process
      
+
      42.3.1. Parser
      
+
      42.3.2. Transformation Process
      
 
      
 
      42.4. The PostgreSQL Rule System
      
 
      42.5. Planner/Optimizer
      
-
      42.5.1. Generating Possible Plans
      
+
      42.5.1. Generating Possible Plans
      
 
      42.6. Executor
      
 
      
 
      43. System Catalogs
      
@@ -1411,15 +1411,15 @@
 
      
 
      44.2. Message Flow
      
 
      
-
      44.2.1. Start-Up
      
-
      44.2.2. Simple Query
      
+
      44.2.1. Start-Up
      
+
      44.2.2. Simple Query
      
 
      44.2.3. Extended Query
      
-
      44.2.4. Function Call
      
+
      44.2.4. Function Call
      
 
      44.2.5. COPY Operations
      
 
      44.2.6. Asynchronous Operations
      
-
      44.2.7. Cancelling Requests in Progress
      
-
      44.2.8. Termination
      
-
      44.2.9. SSL Session Encryption
      
+
      44.2.7. Cancelling Requests in Progress
      
+
      44.2.8. Termination
      
+
      44.2.9. SSL Session Encryption
      
 
      
 
      44.3. Message Data Types
      
 
      44.4. Message Formats
      
@@ -1436,10 +1436,10 @@
 
      
 
      46.1. For the Translator
      
 
      
-
      46.1.1. Requirements
      
-
      46.1.2. Concepts
      
-
      46.1.3. Creating and maintaining message catalogs
      
-
      46.1.4. Editing the PO files
      
+
      46.1.1. Requirements
      
+
      46.1.2. Concepts
      
+
      46.1.3. Creating and maintaining message catalogs
      
+
      46.1.4. Editing the PO files
      
 
      
 
      46.2. For the Programmer
      
 
      
@@ -1504,7 +1504,7 @@
 
      A. PostgreSQL Error Codes
      
 
      B. Date/Time Support
      
 
      
-
      B.1. Date/Time Input Interpretation
      
+
      B.1. Date/Time Input Interpretation
      
 
      B.2. Date/Time Key Words
      
 
      B.3. Date/Time Configuration Files
      
 
      B.4. History of Units
      
@@ -1517,433 +1517,458 @@
 
      
 
      E. Release Notes
      
 
      
-
      E.1. Release 8.2
      
+
      E.1. Release 8.2.1
      
 
      
-
      E.1.1. Overview
      
-
      E.1.2. Migration to version 8.2
      
-
      E.1.3. Changes
      
+
      E.1.1. Migration to version 8.2.1
      
+
      E.1.2. Changes
      
 
      
-
      E.2. Release 8.1.5
      
+
      E.2. Release 8.2
      
 
      
-
      E.2.1. Migration to version 8.1.5
      
-
      E.2.2. Changes
      
+
      E.2.1. Overview
      
+
      E.2.2. Migration to version 8.2
      
+
      E.2.3. Changes
      
 
      
-
      E.3. Release 8.1.4
      
+
      E.3. Release 8.1.6
      
 
      
-
      E.3.1. Migration to version 8.1.4
      
-
      E.3.2. Changes
      
+
      E.3.1. Migration to version 8.1.6
      
+
      E.3.2. Changes
      
 
      
-
      E.4. Release 8.1.3
      
+
      E.4. Release 8.1.5
      
 
      
-
      E.4.1. Migration to version 8.1.3
      
-
      E.4.2. Changes
      
+
      E.4.1. Migration to version 8.1.5
      
+
      E.4.2. Changes
      
 
      
-
      E.5. Release 8.1.2
      
+
      E.5. Release 8.1.4
      
 
      
-
      E.5.1. Migration to version 8.1.2
      
-
      E.5.2. Changes
      
+
      E.5.1. Migration to version 8.1.4
      
+
      E.5.2. Changes
      
 
      
-
      E.6. Release 8.1.1
      
+
      E.6. Release 8.1.3
      
 
      
-
      E.6.1. Migration to version 8.1.1
      
-
      E.6.2. Changes
      
+
      E.6.1. Migration to version 8.1.3
      
+
      E.6.2. Changes
      
 
      
-
      E.7. Release 8.1
      
+
      E.7. Release 8.1.2
      
 
      
-
      E.7.1. Overview
      
-
      E.7.2. Migration to version 8.1
      
-
      E.7.3. Additional Changes
      
+
      E.7.1. Migration to version 8.1.2
      
+
      E.7.2. Changes
      
 
      
-
      E.8. Release 8.0.9
      
+
      E.8. Release 8.1.1
      
 
      
-
      E.8.1. Migration to version 8.0.9
      
-
      E.8.2. Changes
      
+
      E.8.1. Migration to version 8.1.1
      
+
      E.8.2. Changes
      
 
      
-
      E.9. Release 8.0.8
      
+
      E.9. Release 8.1
      
 
      
-
      E.9.1. Migration to version 8.0.8
      
-
      E.9.2. Changes
      
+
      E.9.1. Overview
      
+
      E.9.2. Migration to version 8.1
      
+
      E.9.3. Additional Changes
      
 
      
-
      E.10. Release 8.0.7
      
+
      E.10. Release 8.0.10
      
 
      
-
      E.10.1. Migration to version 8.0.7
      
-
      E.10.2. Changes
      
+
      E.10.1. Migration to version 8.0.10
      
+
      E.10.2. Changes
      
 
      
-
      E.11. Release 8.0.6
      
+
      E.11. Release 8.0.9
      
 
      
-
      E.11.1. Migration to version 8.0.6
      
-
      E.11.2. Changes
      
+
      E.11.1. Migration to version 8.0.9
      
+
      E.11.2. Changes
      
 
      
-
      E.12. Release 8.0.5
      
+
      E.12. Release 8.0.8
      
 
      
-
      E.12.1. Migration to version 8.0.5
      
-
      E.12.2. Changes
      
+
      E.12.1. Migration to version 8.0.8
      
+
      E.12.2. Changes
      
 
      
-
      E.13. Release 8.0.4
      
+
      E.13. Release 8.0.7
      
 
      
-
      E.13.1. Migration to version 8.0.4
      
-
      E.13.2. Changes
      
+
      E.13.1. Migration to version 8.0.7
      
+
      E.13.2. Changes
      
 
      
-
      E.14. Release 8.0.3
      
+
      E.14. Release 8.0.6
      
 
      
-
      E.14.1. Migration to version 8.0.3
      
-
      E.14.2. Changes
      
+
      E.14.1. Migration to version 8.0.6
      
+
      E.14.2. Changes
      
 
      
-
      E.15. Release 8.0.2
      
+
      E.15. Release 8.0.5
      
 
      
-
      E.15.1. Migration to version 8.0.2
      
-
      E.15.2. Changes
      
+
      E.15.1. Migration to version 8.0.5
      
+
      E.15.2. Changes
      
 
      
-
      E.16. Release 8.0.1
      
+
      E.16. Release 8.0.4
      
 
      
-
      E.16.1. Migration to version 8.0.1
      
-
      E.16.2. Changes
      
+
      E.16.1. Migration to version 8.0.4
      
+
      E.16.2. Changes
      
 
      
-
      E.17. Release 8.0
      
+
      E.17. Release 8.0.3
      
 
      
-
      E.17.1. Overview
      
-
      E.17.2. Migration to version 8.0
      
-
      E.17.3. Deprecated Features
      
-
      E.17.4. Changes
      
+
      E.17.1. Migration to version 8.0.3
      
+
      E.17.2. Changes
      
 
      
-
      E.18. Release 7.4.14
      
+
      E.18. Release 8.0.2
      
 
      
-
      E.18.1. Migration to version 7.4.14
      
-
      E.18.2. Changes
      
+
      E.18.1. Migration to version 8.0.2
      
+
      E.18.2. Changes
      
 
      
-
      E.19. Release 7.4.13
      
+
      E.19. Release 8.0.1
      
 
      
-
      E.19.1. Migration to version 7.4.13
      
-
      E.19.2. Changes
      
+
      E.19.1. Migration to version 8.0.1
      
+
      E.19.2. Changes
      
 
      
-
      E.20. Release 7.4.12
      
+
      E.20. Release 8.0
      
 
      
-
      E.20.1. Migration to version 7.4.12
      
-
      E.20.2. Changes
      
+
      E.20.1. Overview
      
+
      E.20.2. Migration to version 8.0
      
+
      E.20.3. Deprecated Features
      
+
      E.20.4. Changes
      
 
      
-
      E.21. Release 7.4.11
      
+
      E.21. Release 7.4.15
      
 
      
-
      E.21.1. Migration to version 7.4.11
      
-
      E.21.2. Changes
      
+
      E.21.1. Migration to version 7.4.15
      
+
      E.21.2. Changes
      
 
      
-
      E.22. Release 7.4.10
      
+
      E.22. Release 7.4.14
      
 
      
-
      E.22.1. Migration to version 7.4.10
      
-
      E.22.2. Changes
      
+
      E.22.1. Migration to version 7.4.14
      
+
      E.22.2. Changes
      
 
      
-
      E.23. Release 7.4.9
      
+
      E.23. Release 7.4.13
      
 
      
-
      E.23.1. Migration to version 7.4.9
      
-
      E.23.2. Changes
      
+
      E.23.1. Migration to version 7.4.13
      
+
      E.23.2. Changes
      
 
      
-
      E.24. Release 7.4.8
      
+
      E.24. Release 7.4.12
      
 
      
-
      E.24.1. Migration to version 7.4.8
      
-
      E.24.2. Changes
      
+
      E.24.1. Migration to version 7.4.12
      
+
      E.24.2. Changes
      
 
      
-
      E.25. Release 7.4.7
      
+
      E.25. Release 7.4.11
      
 
      
-
      E.25.1. Migration to version 7.4.7
      
-
      E.25.2. Changes
      
+
      E.25.1. Migration to version 7.4.11
      
+
      E.25.2. Changes
      
 
      
-
      E.26. Release 7.4.6
      
+
      E.26. Release 7.4.10
      
 
      
-
      E.26.1. Migration to version 7.4.6
      
-
      E.26.2. Changes
      
+
      E.26.1. Migration to version 7.4.10
      
+
      E.26.2. Changes
      
 
      
-
      E.27. Release 7.4.5
      
+
      E.27. Release 7.4.9
      
 
      
-
      E.27.1. Migration to version 7.4.5
      
-
      E.27.2. Changes
      
+
      E.27.1. Migration to version 7.4.9
      
+
      E.27.2. Changes
      
 
      
-
      E.28. Release 7.4.4
      
+
      E.28. Release 7.4.8
      
 
      
-
      E.28.1. Migration to version 7.4.4
      
-
      E.28.2. Changes
      
+
      E.28.1. Migration to version 7.4.8
      
+
      E.28.2. Changes
      
 
      
-
      E.29. Release 7.4.3
      
+
      E.29. Release 7.4.7
      
 
      
-
      E.29.1. Migration to version 7.4.3
      
-
      E.29.2. Changes
      
+
      E.29.1. Migration to version 7.4.7
      
+
      E.29.2. Changes
      
 
      
-
      E.30. Release 7.4.2
      
+
      E.30. Release 7.4.6
      
 
      
-
      E.30.1. Migration to version 7.4.2
      
-
      E.30.2. Changes
      
+
      E.30.1. Migration to version 7.4.6
      
+
      E.30.2. Changes
      
 
      
-
      E.31. Release 7.4.1
      
+
      E.31. Release 7.4.5
      
 
      
-
      E.31.1. Migration to version 7.4.1
      
-
      E.31.2. Changes
      
+
      E.31.1. Migration to version 7.4.5
      
+
      E.31.2. Changes
      
 
      
-
      E.32. Release 7.4
      
+
      E.32. Release 7.4.4
      
 
      
-
      E.32.1. Overview
      
-
      E.32.2. Migration to version 7.4
      
-
      E.32.3. Changes
      
+
      E.32.1. Migration to version 7.4.4
      
+
      E.32.2. Changes
      
 
      
-
      E.33. Release 7.3.16
      
+
      E.33. Release 7.4.3
      
 
      
-
      E.33.1. Migration to version 7.3.16
      
-
      E.33.2. Changes
      
+
      E.33.1. Migration to version 7.4.3
      
+
      E.33.2. Changes
      
 
      
-
      E.34. Release 7.3.15
      
+
      E.34. Release 7.4.2
      
 
      
-
      E.34.1. Migration to version 7.3.15
      
-
      E.34.2. Changes
      
+
      E.34.1. Migration to version 7.4.2
      
+
      E.34.2. Changes
      
 
      
-
      E.35. Release 7.3.14
      
+
      E.35. Release 7.4.1
      
 
      
-
      E.35.1. Migration to version 7.3.14
      
-
      E.35.2. Changes
      
+
      E.35.1. Migration to version 7.4.1
      
+
      E.35.2. Changes
      
 
      
-
      E.36. Release 7.3.13
      
+
      E.36. Release 7.4
      
 
      
-
      E.36.1. Migration to version 7.3.13
      
-
      E.36.2. Changes
      
+
      E.36.1. Overview
      
+
      E.36.2. Migration to version 7.4
      
+
      E.36.3. Changes
      
 
      
-
      E.37. Release 7.3.12
      
+
      E.37. Release 7.3.17
      
 
      
-
      E.37.1. Migration to version 7.3.12
      
-
      E.37.2. Changes
      
+
      E.37.1. Migration to version 7.3.17
      
+
      E.37.2. Changes
      
 
      
-
      E.38. Release 7.3.11
      
+
      E.38. Release 7.3.16
      
 
      
-
      E.38.1. Migration to version 7.3.11
      
-
      E.38.2. Changes
      
+
      E.38.1. Migration to version 7.3.16
      
+
      E.38.2. Changes
      
 
      
-
      E.39. Release 7.3.10
      
+
      E.39. Release 7.3.15
      
 
      
-
      E.39.1. Migration to version 7.3.10
      
-
      E.39.2. Changes
      
+
      E.39.1. Migration to version 7.3.15
      
+
      E.39.2. Changes
      
 
      
-
      E.40. Release 7.3.9
      
+
      E.40. Release 7.3.14
      
 
      
-
      E.40.1. Migration to version 7.3.9
      
-
      E.40.2. Changes
      
+
      E.40.1. Migration to version 7.3.14
      
+
      E.40.2. Changes
      
 
      
-
      E.41. Release 7.3.8
      
+
      E.41. Release 7.3.13
      
 
      
-
      E.41.1. Migration to version 7.3.8
      
-
      E.41.2. Changes
      
+
      E.41.1. Migration to version 7.3.13
      
+
      E.41.2. Changes
      
 
      
-
      E.42. Release 7.3.7
      
+
      E.42. Release 7.3.12
      
 
      
-
      E.42.1. Migration to version 7.3.7
      
-
      E.42.2. Changes
      
+
      E.42.1. Migration to version 7.3.12
      
+
      E.42.2. Changes
      
 
      
-
      E.43. Release 7.3.6
      
+
      E.43. Release 7.3.11
      
 
      
-
      E.43.1. Migration to version 7.3.6
      
-
      E.43.2. Changes
      
+
      E.43.1. Migration to version 7.3.11
      
+
      E.43.2. Changes
      
 
      
-
      E.44. Release 7.3.5
      
+
      E.44. Release 7.3.10
      
 
      
-
      E.44.1. Migration to version 7.3.5
      
-
      E.44.2. Changes
      
+
      E.44.1. Migration to version 7.3.10
      
+
      E.44.2. Changes
      
 
      
-
      E.45. Release 7.3.4
      
+
      E.45. Release 7.3.9
      
 
      
-
      E.45.1. Migration to version 7.3.4
      
-
      E.45.2. Changes
      
+
      E.45.1. Migration to version 7.3.9
      
+
      E.45.2. Changes
      
 
      
-
      E.46. Release 7.3.3
      
+
      E.46. Release 7.3.8
      
 
      
-
      E.46.1. Migration to version 7.3.3
      
-
      E.46.2. Changes
      
+
      E.46.1. Migration to version 7.3.8
      
+
      E.46.2. Changes
      
 
      
-
      E.47. Release 7.3.2
      
+
      E.47. Release 7.3.7
      
 
      
-
      E.47.1. Migration to version 7.3.2
      
-
      E.47.2. Changes
      
+
      E.47.1. Migration to version 7.3.7
      
+
      E.47.2. Changes
      
 
      
-
      E.48. Release 7.3.1
      
+
      E.48. Release 7.3.6
      
 
      
-
      E.48.1. Migration to version 7.3.1
      
-
      E.48.2. Changes
      
+
      E.48.1. Migration to version 7.3.6
      
+
      E.48.2. Changes
      
 
      
-
      E.49. Release 7.3
      
+
      E.49. Release 7.3.5
      
 
      
-
      E.49.1. Overview
      
-
      E.49.2. Migration to version 7.3
      
-
      E.49.3. Changes
      
+
      E.49.1. Migration to version 7.3.5
      
+
      E.49.2. Changes
      
 
      
-
      E.50. Release 7.2.8
      
+
      E.50. Release 7.3.4
      
 
      
-
      E.50.1. Migration to version 7.2.8
      
-
      E.50.2. Changes
      
+
      E.50.1. Migration to version 7.3.4
      
+
      E.50.2. Changes
      
 
      
-
      E.51. Release 7.2.7
      
+
      E.51. Release 7.3.3
      
 
      
-
      E.51.1. Migration to version 7.2.7
      
-
      E.51.2. Changes
      
+
      E.51.1. Migration to version 7.3.3
      
+
      E.51.2. Changes
      
 
      
-
      E.52. Release 7.2.6
      
+
      E.52. Release 7.3.2
      
 
      
-
      E.52.1. Migration to version 7.2.6
      
-
      E.52.2. Changes
      
+
      E.52.1. Migration to version 7.3.2
      
+
      E.52.2. Changes
      
 
      
-
      E.53. Release 7.2.5
      
+
      E.53. Release 7.3.1
      
 
      
-
      E.53.1. Migration to version 7.2.5
      
-
      E.53.2. Changes
      
+
      E.53.1. Migration to version 7.3.1
      
+
      E.53.2. Changes
      
 
      
-
      E.54. Release 7.2.4
      
+
      E.54. Release 7.3
      
 
      
-
      E.54.1. Migration to version 7.2.4
      
-
      E.54.2. Changes
      
+
      E.54.1. Overview
      
+
      E.54.2. Migration to version 7.3
      
+
      E.54.3. Changes
      
 
      
-
      E.55. Release 7.2.3
      
+
      E.55. Release 7.2.8
      
 
      
-
      E.55.1. Migration to version 7.2.3
      
-
      E.55.2. Changes
      
+
      E.55.1. Migration to version 7.2.8
      
+
      E.55.2. Changes
      
 
      
-
      E.56. Release 7.2.2
      
+
      E.56. Release 7.2.7
      
 
      
-
      E.56.1. Migration to version 7.2.2
      
-
      E.56.2. Changes
      
+
      E.56.1. Migration to version 7.2.7
      
+
      E.56.2. Changes
      
 
      
-
      E.57. Release 7.2.1
      
+
      E.57. Release 7.2.6
      
 
      
-
      E.57.1. Migration to version 7.2.1
      
-
      E.57.2. Changes
      
+
      E.57.1. Migration to version 7.2.6
      
+
      E.57.2. Changes
      
 
      
-
      E.58. Release 7.2
      
+
      E.58. Release 7.2.5
      
 
      
-
      E.58.1. Overview
      
-
      E.58.2. Migration to version 7.2
      
-
      E.58.3. Changes
      
+
      E.58.1. Migration to version 7.2.5
      
+
      E.58.2. Changes
      
 
      
-
      E.59. Release 7.1.3
      
+
      E.59. Release 7.2.4
      
 
      
-
      E.59.1. Migration to version 7.1.3
      
-
      E.59.2. Changes
      
+
      E.59.1. Migration to version 7.2.4
      
+
      E.59.2. Changes
      
 
      
-
      E.60. Release 7.1.2
      
+
      E.60. Release 7.2.3
      
 
      
-
      E.60.1. Migration to version 7.1.2
      
-
      E.60.2. Changes
      
+
      E.60.1. Migration to version 7.2.3
      
+
      E.60.2. Changes
      
 
      
-
      E.61. Release 7.1.1
      
+
      E.61. Release 7.2.2
      
 
      
-
      E.61.1. Migration to version 7.1.1
      
-
      E.61.2. Changes
      
+
      E.61.1. Migration to version 7.2.2
      
+
      E.61.2. Changes
      
 
      
-
      E.62. Release 7.1
      
+
      E.62. Release 7.2.1
      
 
      
-
      E.62.1. Migration to version 7.1
      
-
      E.62.2. Changes
      
+
      E.62.1. Migration to version 7.2.1
      
+
      E.62.2. Changes
      
 
      
-
      E.63. Release 7.0.3
      
+
      E.63. Release 7.2
      
 
      
-
      E.63.1. Migration to version 7.0.3
      
-
      E.63.2. Changes
      
+
      E.63.1. Overview
      
+
      E.63.2. Migration to version 7.2
      
+
      E.63.3. Changes
      
 
      
-
      E.64. Release 7.0.2
      
+
      E.64. Release 7.1.3
      
 
      
-
      E.64.1. Migration to version 7.0.2
      
-
      E.64.2. Changes
      
+
      E.64.1. Migration to version 7.1.3
      
+
      E.64.2. Changes
      
 
      
-
      E.65. Release 7.0.1
      
+
      E.65. Release 7.1.2
      
 
      
-
      E.65.1. Migration to version 7.0.1
      
-
      E.65.2. Changes
      
+
      E.65.1. Migration to version 7.1.2
      
+
      E.65.2. Changes
      
 
      
-
      E.66. Release 7.0
      
+
      E.66. Release 7.1.1
      
 
      
-
      E.66.1. Migration to version 7.0
      
-
      E.66.2. Changes
      
+
      E.66.1. Migration to version 7.1.1
      
+
      E.66.2. Changes
      
 
      
-
      E.67. Release 6.5.3
      
+
      E.67. Release 7.1
      
 
      
-
      E.67.1. Migration to version 6.5.3
      
-
      E.67.2. Changes
      
+
      E.67.1. Migration to version 7.1
      
+
      E.67.2. Changes
      
 
      
-
      E.68. Release 6.5.2
      
+
      E.68. Release 7.0.3
      
 
      
-
      E.68.1. Migration to version 6.5.2
      
-
      E.68.2. Changes
      
+
      E.68.1. Migration to version 7.0.3
      
+
      E.68.2. Changes
      
 
      
-
      E.69. Release 6.5.1
      
+
      E.69. Release 7.0.2
      
 
      
-
      E.69.1. Migration to version 6.5.1
      
-
      E.69.2. Changes
      
+
      E.69.1. Migration to version 7.0.2
      
+
      E.69.2. Changes
      
 
      
-
      E.70. Release 6.5
      
+
      E.70. Release 7.0.1
      
 
      
-
      E.70.1. Migration to version 6.5
      
-
      E.70.2. Changes
      
+
      E.70.1. Migration to version 7.0.1
      
+
      E.70.2. Changes
      
 
      
-
      E.71. Release 6.4.2
      
+
      E.71. Release 7.0
      
 
      
-
      E.71.1. Migration to version 6.4.2
      
-
      E.71.2. Changes
      
+
      E.71.1. Migration to version 7.0
      
+
      E.71.2. Changes
      
 
      
-
      E.72. Release 6.4.1
      
+
      E.72. Release 6.5.3
      
 
      
-
      E.72.1. Migration to version 6.4.1
      
-
      E.72.2. Changes
      
+
      E.72.1. Migration to version 6.5.3
      
+
      E.72.2. Changes
      
 
      
-
      E.73. Release 6.4
      
+
      E.73. Release 6.5.2
      
 
      
-
      E.73.1. Migration to version 6.4
      
-
      E.73.2. Changes
      
+
      E.73.1. Migration to version 6.5.2
      
+
      E.73.2. Changes
      
 
      
-
      E.74. Release 6.3.2
      
-
      E.74.1. Changes
      
-
      E.75. Release 6.3.1
      
-
      E.75.1. Changes
      
-
      E.76. Release 6.3
      
+
      E.74. Release 6.5.1
      
 
      
-
      E.76.1. Migration to version 6.3
      
-
      E.76.2. Changes
      
+
      E.74.1. Migration to version 6.5.1
      
+
      E.74.2. Changes
      
 
      
-
      E.77. Release 6.2.1
      
+
      E.75. Release 6.5
      
 
      
-
      E.77.1. Migration from version 6.2 to version 6.2.1
      
-
      E.77.2. Changes
      
+
      E.75.1. Migration to version 6.5
      
+
      E.75.2. Changes
      
 
      
-
      E.78. Release 6.2
      
+
      E.76. Release 6.4.2
      
 
      
-
      E.78.1. Migration from version 6.1 to version 6.2
      
-
      E.78.2. Migration from version 1.x to version 6.2
      
-
      E.78.3. Changes
      
+
      E.76.1. Migration to version 6.4.2
      
+
      E.76.2. Changes
      
 
      
-
      E.79. Release 6.1.1
      
+
      E.77. Release 6.4.1
      
 
      
-
      E.79.1. Migration from version 6.1 to version 6.1.1
      
-
      E.79.2. Changes
      
+
      E.77.1. Migration to version 6.4.1
      
+
      E.77.2. Changes
      
 
      
-
      E.80. Release 6.1
      
+
      E.78. Release 6.4
      
 
      
-
      E.80.1. Migration to version 6.1
      
-
      E.80.2. Changes
      
+
      E.78.1. Migration to version 6.4
      
+
      E.78.2. Changes
      
 
      
-
      E.81. Release 6.0
      
+
      E.79. Release 6.3.2
      
+
      E.79.1. Changes
      
+
      E.80. Release 6.3.1
      
+
      E.80.1. Changes
      
+
      E.81. Release 6.3
      
 
      
-
      E.81.1. Migration from version 1.09 to version 6.0
      
-
      E.81.2. Migration from pre-1.09 to version 6.0
      
-
      E.81.3. Changes
      
+
      E.81.1. Migration to version 6.3
      
+
      E.81.2. Changes
      
 
      
-
      E.82. Release 1.09
      
-
      E.83. Release 1.02
      
+
      E.82. Release 6.2.1
      
 
      
-
      E.83.1. Migration from version 1.02 to version 1.02.1
      
-
      E.83.2. Dump/Reload Procedure
      
-
      E.83.3. Changes
      
+
      E.82.1. Migration from version 6.2 to version 6.2.1
      
+
      E.82.2. Changes
      
 
      
-
      E.84. Release 1.01
      
+
      E.83. Release 6.2
      
 
      
-
      E.84.1. Migration from version 1.0 to version 1.01
      
-
      E.84.2. Changes
      
+
      E.83.1. Migration from version 6.1 to version 6.2
      
+
      E.83.2. Migration from version 1.x to version 6.2
      
+
      E.83.3. Changes
      
 
      
-
      E.85. Release 1.0
      
-
      E.85.1. Changes
      
-
      E.86. Postgres95 Release 0.03
      
-
      E.86.1. Changes
      
-
      E.87. Postgres95 Release 0.02
      
-
      E.87.1. Changes
      
-
      E.88. Postgres95 Release 0.01
      
+
      E.84. Release 6.1.1
      
+
      
+
      E.84.1. Migration from version 6.1 to version 6.1.1
      
+
      E.84.2. Changes
      
+
      
+
      E.85. Release 6.1
      
+
      
+
      E.85.1. Migration to version 6.1
      
+
      E.85.2. Changes
      
+
      
+
      E.86. Release 6.0
      
+
      
+
      E.86.1. Migration from version 1.09 to version 6.0
      
+
      E.86.2. Migration from pre-1.09 to version 6.0
      
+
      E.86.3. Changes
      
+
      
+
      E.87. Release 1.09
      
+
      E.88. Release 1.02
      
+
      
+
      E.88.1. Migration from version 1.02 to version 1.02.1
      
+
      E.88.2. Dump/Reload Procedure
      
+
      E.88.3. Changes
      
+
      
+
      E.89. Release 1.01
      
+
      
+
      E.89.1. Migration from version 1.0 to version 1.01
      
+
      E.89.2. Changes
      
+
      
+
      E.90. Release 1.0
      
+
      E.90.1. Changes
      
+
      E.91. Postgres95 Release 0.03
      
+
      E.91.1. Changes
      
+
      E.92. Postgres95 Release 0.02
      
+
      E.92.1. Changes
      
+
      E.93. Postgres95 Release 0.01
      
 
      
 
      F. The CVS Repository
      
 
      
@@ -1951,8 +1976,8 @@
 
      F.2. CVS Tree Organization
      
 
      F.3. Getting The Source Via CVSup
      
 
      
-
      F.3.1. Preparing A CVSup Client System
      
-
      F.3.2. Running a CVSup Client
      
+
      F.3.1. Preparing A CVSup Client System
      
+
      F.3.2. Running a CVSup Client
      
 
      
 
      
 
      G. Documentation
      
@@ -1960,28 +1985,28 @@
 
      G.1. DocBook
      
 
      G.2. Tool Sets
      
 
      
-
      G.2.1. Linux RPM Installation
      
-
      G.2.2. FreeBSD Installation
      
-
      G.2.3. Debian Packages
      
-
      G.2.4. Manual Installation from Source
      
+
      G.2.1. Linux RPM Installation
      
+
      G.2.2. FreeBSD Installation
      
+
      G.2.3. Debian Packages
      
+
      G.2.4. Manual Installation from Source
      
 
      G.2.5. Detection by configure
      
 
      
 
      G.3. Building The Documentation
      
 
      
-
      G.3.1. HTML
      
-
      G.3.2. Manpages
      
-
      G.3.3. Print Output via JadeTex
      
-
      G.3.4. Print Output via RTF
      
-
      G.3.5. Plain Text Files
      
-
      G.3.6. Syntax Check
      
+
      G.3.1. HTML
      
+
      G.3.2. Manpages
      
+
      G.3.3. Print Output via JadeTex
      
+
      G.3.4. Print Output via RTF
      
+
      G.3.5. Plain Text Files
      
+
      G.3.6. Syntax Check
      
 
      
 
      G.4. Documentation Authoring
      
 
      
-
      G.4.1. Emacs/PSGML
      
-
      G.4.2. Other Emacs modes
      
+
      G.4.1. Emacs/PSGML
      
+
      G.4.2. Other Emacs modes
      
 
      
 
      G.5. Style Guide
      
-
      G.5.1. Reference Pages
      
+
      G.5.1. Reference Pages
      
 
      
 
      H. External Projects
      
 
      
@@ -2163,103 +2188,103 @@
 
 
      25.3. Built-in Trace Points
 
      
-
      31.1. Valid input formats for PGTYPESdate_from_asc
+
      31.1. Valid input formats for PGTYPESdate_from_asc
 
      
-
      31.2. Valid input formats for PGTYPESdate_fmt_asc
+
      31.2. Valid input formats for PGTYPESdate_fmt_asc
 
      
-
      31.3. Valid input formats for rdefmtdate
+
      31.3. Valid input formats for rdefmtdate
 
      
-
      31.4. Valid input formats for PGTYPEStimestamp_from_asc
+
      31.4. Valid input formats for PGTYPEStimestamp_from_asc
 
      
-
      32.1. information_schema_catalog_name Columns
+
      32.1. information_schema_catalog_name Columns
 
      
-
      32.2. administrable_role_authorizations Columns
+
      32.2. administrable_role_authorizations Columns
 
      
-
      32.3. applicable_roles Columns
+
      32.3. applicable_roles Columns
 
      
-
      32.4. attributes Columns
+
      32.4. attributes Columns
 
      
-
      32.5. check_constraint_routine_usage Columns
+
      32.5. check_constraint_routine_usage Columns
 
      
-
      32.6. check_constraints Columns
+
      32.6. check_constraints Columns
 
      
-
      32.7. column_domain_usage Columns
+
      32.7. column_domain_usage Columns
 
      
-
      32.8. column_privileges Columns
+
      32.8. column_privileges Columns
 
      
-
      32.9. column_udt_usage Columns
+
      32.9. column_udt_usage Columns
 
      
-
      32.10. columns Columns
+
      32.10. columns Columns
 
      
-
      32.11. constraint_column_usage Columns
+
      32.11. constraint_column_usage Columns
 
      
-
      32.12. constraint_table_usage Columns
+
      32.12. constraint_table_usage Columns
 
      
-
      32.13. data_type_privileges Columns
+
      32.13. data_type_privileges Columns
 
      
-
      32.14. domain_constraints Columns
+
      32.14. domain_constraints Columns
 
      
-
      32.15. domain_udt_usage Columns
+
      32.15. domain_udt_usage Columns
 
      
-
      32.16. domains Columns
+
      32.16. domains Columns
 
      
-
      32.17. element_types Columns
+
      32.17. element_types Columns
 
      
-
      32.18. enabled_roles Columns
+
      32.18. enabled_roles Columns
 
      
-
      32.19. key_column_usage Columns
+
      32.19. key_column_usage Columns
 
      
-
      32.20. parameters Columns
+
      32.20. parameters Columns
 
      
-
      32.21. referential_constraints Columns
+
      32.21. referential_constraints Columns
 
      
-
      32.22. role_column_grants Columns
+
      32.22. role_column_grants Columns
 
      
-
      32.23. role_routine_grants Columns
+
      32.23. role_routine_grants Columns
 
      
-
      32.24. role_table_grants Columns
+
      32.24. role_table_grants Columns
 
      
-
      32.25. role_usage_grants Columns
+
      32.25. role_usage_grants Columns
 
      
-
      32.26. routine_privileges Columns
+
      32.26. routine_privileges Columns
 
      
-
      32.27. routines Columns
+
      32.27. routines Columns
 
      
-
      32.28. schemata Columns
+
      32.28. schemata Columns
 
      
-
      32.29. sequences Columns
+
      32.29. sequences Columns
 
      
-
      32.30. sql_features Columns
+
      32.30. sql_features Columns
 
      
-
      32.31. sql_implementation_info Columns
+
      32.31. sql_implementation_info Columns
 
      
-
      32.32. sql_languages Columns
+
      32.32. sql_languages Columns
 
      
-
      32.33. sql_packages Columns
+
      32.33. sql_packages Columns
 
      
-
      32.34. sql_parts Columns
+
      32.34. sql_parts Columns
 
      
-
      32.35. sql_sizing Columns
+
      32.35. sql_sizing Columns
 
      
-
      32.36. sql_sizing_profiles Columns
+
      32.36. sql_sizing_profiles Columns
 
      
-
      32.37. table_constraints Columns
+
      32.37. table_constraints Columns
 
      
-
      32.38. table_privileges Columns
+
      32.38. table_privileges Columns
 
      
-
      32.39. tables Columns
+
      32.39. tables Columns
 
      
-
      32.40. triggers Columns
+
      32.40. triggers Columns
 
      
-
      32.41. usage_privileges Columns
+
      32.41. usage_privileges Columns
 
      
-
      32.42. view_column_usage Columns
+
      32.42. view_column_usage Columns
 
      
-
      32.43. view_routine_usage Columns
+
      32.43. view_routine_usage Columns
 
      
-
      32.44. view_table_usage Columns
+
      32.44. view_table_usage Columns
 
      
-
      32.45. views Columns
+
      32.45. views Columns
 
      
 
      33.1. Equivalent C Types for Built-In SQL Types
 
      
@@ -2281,105 +2306,105 @@
 
 
      43.1. System Catalogs
 
      
-
      43.2. pg_aggregate Columns
+
      43.2. pg_aggregate Columns
 
      
-
      43.3. pg_am Columns
+
      43.3. pg_am Columns
 
      
-
      43.4. pg_amop Columns
+
      43.4. pg_amop Columns
 
      
-
      43.5. pg_amproc Columns
+
      43.5. pg_amproc Columns
 
      
-
      43.6. pg_attrdef Columns
+
      43.6. pg_attrdef Columns
 
      
-
      43.7. pg_attribute Columns
+
      43.7. pg_attribute Columns
 
      
-
      43.8. pg_authid Columns
+
      43.8. pg_authid Columns
 
      
-
      43.9. pg_auth_members Columns
+
      43.9. pg_auth_members Columns
 
      
-
      43.10. pg_autovacuum Columns
+
      43.10. pg_autovacuum Columns
 
      
-
      43.11. pg_cast Columns
+
      43.11. pg_cast Columns
 
      
-
      43.12. pg_class Columns
+
      43.12. pg_class Columns
 
      
-
      43.13. pg_constraint Columns
+
      43.13. pg_constraint Columns
 
      
-
      43.14. pg_conversion Columns
+
      43.14. pg_conversion Columns
 
      
-
      43.15. pg_database Columns
+
      43.15. pg_database Columns
 
      
-
      43.16. pg_depend Columns
+
      43.16. pg_depend Columns
 
      
-
      43.17. pg_description Columns
+
      43.17. pg_description Columns
 
      
-
      43.18. pg_index Columns
+
      43.18. pg_index Columns
 
      
-
      43.19. pg_inherits Columns
+
      43.19. pg_inherits Columns
 
      
-
      43.20. pg_language Columns
+
      43.20. pg_language Columns
 
      
-
      43.21. pg_largeobject Columns
+
      43.21. pg_largeobject Columns
 
      
-
      43.22. pg_listener Columns
+
      43.22. pg_listener Columns
 
      
-
      43.23. pg_namespace Columns
+
      43.23. pg_namespace Columns
 
      
-
      43.24. pg_opclass Columns
+
      43.24. pg_opclass Columns
 
      
-
      43.25. pg_operator Columns
+
      43.25. pg_operator Columns
 
      
-
      43.26. pg_pltemplate Columns
+
      43.26. pg_pltemplate Columns
 
      
-
      43.27. pg_proc Columns
+
      43.27. pg_proc Columns
 
      
-
      43.28. pg_rewrite Columns
+
      43.28. pg_rewrite Columns
 
      
-
      43.29. pg_shdepend Columns
+
      43.29. pg_shdepend Columns
 
      
-
      43.30. pg_shdescription Columns
+
      43.30. pg_shdescription Columns
 
      
-
      43.31. pg_statistic Columns
+
      43.31. pg_statistic Columns
 
      
-
      43.32. pg_tablespace Columns
+
      43.32. pg_tablespace Columns
 
      
-
      43.33. pg_trigger Columns
+
      43.33. pg_trigger Columns
 
      
-
      43.34. pg_type Columns
+
      43.34. pg_type Columns
 
      
 
      43.35. System Views
 
      
-
      43.36. pg_cursors Columns
+
      43.36. pg_cursors Columns
 
      
-
      43.37. pg_group Columns
+
      43.37. pg_group Columns
 
      
-
      43.38. pg_indexes Columns
+
      43.38. pg_indexes Columns
 
      
-
      43.39. pg_locks Columns
+
      43.39. pg_locks Columns
 
      
-
      43.40. pg_prepared_statements Columns
+
      43.40. pg_prepared_statements Columns
 
      
-
      43.41. pg_prepared_xacts Columns
+
      43.41. pg_prepared_xacts Columns
 
      
-
      43.42. pg_roles Columns
+
      43.42. pg_roles Columns
 
      
-
      43.43. pg_rules Columns
+
      43.43. pg_rules Columns
 
      
-
      43.44. pg_settings Columns
+
      43.44. pg_settings Columns
 
      
-
      43.45. pg_shadow Columns
+
      43.45. pg_shadow Columns
 
      
-
      43.46. pg_stats Columns
+
      43.46. pg_stats Columns
 
      
-
      43.47. pg_tables Columns
+
      43.47. pg_tables Columns
 
      
-
      43.48. pg_timezone_abbrevs Columns
+
      43.48. pg_timezone_abbrevs Columns
 
      
-
      43.49. pg_timezone_names Columns
+
      43.49. pg_timezone_names Columns
 
      
-
      43.50. pg_user Columns
+
      43.50. pg_user Columns
 
      
-
      43.51. pg_views Columns
+
      43.51. pg_views Columns
 
      
 
      52.1. Contents of PGDATA
 
      
@@ -2408,29 +2433,29 @@
 
      
 
      List of Examples
      
 
      
-
      8.1. Using the character types
+
      8.1. Using the character types
 
      
 
      8.2. Using the boolean type
 
      
-
      8.3. Using the bit string types
+
      8.3. Using the bit string types
 
      
-
      10.1. Exponentiation Operator Type Resolution
+
      10.1. Exponentiation Operator Type Resolution
 
      
-
      10.2. String Concatenation Operator Type Resolution
+
      10.2. String Concatenation Operator Type Resolution
 
      
-
      10.3. Absolute-Value and Negation Operator Type Resolution
+
      10.3. Absolute-Value and Negation Operator Type Resolution
 
      
-
      10.4. Rounding Function Argument Type Resolution
+
      10.4. Rounding Function Argument Type Resolution
 
      
-
      10.5. Substring Function Type Resolution
+
      10.5. Substring Function Type Resolution
 
      
-
      10.6. character Storage Type Conversion
+
      10.6. character Storage Type Conversion
 
      
-
      10.7. Type Resolution with Underspecified Types in a Union
+
      10.7. Type Resolution with Underspecified Types in a Union
 
      
-
      10.8. Type Resolution in a Simple Union
+
      10.8. Type Resolution in a Simple Union
 
      
-
      10.9. Type Resolution in a Transposed Union
+
      10.9. Type Resolution in a Transposed Union
 
      
 
      11.1. Setting up a Partial Index to Exclude Common Values
 
      
diff --git a/docs/en_US/pg/indexam.html b/docs/en_US/pg/indexam.html
index c52a5ad3c0..b14bf03125 100644
--- a/docs/en_US/pg/indexam.html
+++ b/docs/en_US/pg/indexam.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/indexes-bitmap-scans.html b/docs/en_US/pg/indexes-bitmap-scans.html
index 367664595b..d5155f7902 100644
--- a/docs/en_US/pg/indexes-bitmap-scans.html
+++ b/docs/en_US/pg/indexes-bitmap-scans.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.4. Combining Multiple Indexes
      
-
         A single index scan can only use query clauses that use the index's
+
         A single index scan can only use query clauses that use the index's
    columns with operators of its operator class and are joined with
    AND.  For example, given an index on (a, b)
    a query condition like WHERE a = 5 AND b = 6 could
diff --git a/docs/en_US/pg/indexes-examine.html b/docs/en_US/pg/indexes-examine.html
index 714b8a5752..c3141d9292 100644
--- a/docs/en_US/pg/indexes-examine.html
+++ b/docs/en_US/pg/indexes-examine.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.9. Examining Index Usage
      
-
         Although indexes in PostgreSQL do not need
+
         Although indexes in PostgreSQL do not need
    maintenance and tuning, it is still important to check
    which indexes are actually used by the real-life query workload.
    Examining index usage for an individual query is done with the
diff --git a/docs/en_US/pg/indexes-expressional.html b/docs/en_US/pg/indexes-expressional.html
index e5438c11f0..d38851480c 100644
--- a/docs/en_US/pg/indexes-expressional.html
+++ b/docs/en_US/pg/indexes-expressional.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.6. Indexes on Expressions
      
-
         An index column need not be just a column of the underlying table,
+
         An index column need not be just a column of the underlying table,
    but can be a function or scalar expression computed from one or
    more columns of the table.  This feature is useful to obtain fast
    access to tables based on the results of computations.
diff --git a/docs/en_US/pg/indexes-multicolumn.html b/docs/en_US/pg/indexes-multicolumn.html
index d3067087a7..c349d6bb3f 100644
--- a/docs/en_US/pg/indexes-multicolumn.html
+++ b/docs/en_US/pg/indexes-multicolumn.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.3. Multicolumn Indexes
      
-
         An index can be defined on more than one column of a table.  For example, if
+
         An index can be defined on more than one column of a table.  For example, if
    you have a table of this form:
 
      
 
      CREATE TABLE test2 (
diff --git a/docs/en_US/pg/indexes-opclass.html b/docs/en_US/pg/indexes-opclass.html
index 1edc9d9106..dff236fa2e 100644
--- a/docs/en_US/pg/indexes-opclass.html
+++ b/docs/en_US/pg/indexes-opclass.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.8. Operator Classes
      
-
         An index definition may specify an operator
+
         An index definition may specify an operator
    class for each column of an index.
 
      
 
      CREATE INDEX name ON table (column opclass [, ...]);
      
diff --git a/docs/en_US/pg/indexes-partial.html b/docs/en_US/pg/indexes-partial.html
index 1a05faeb53..6de5a6d783 100644
--- a/docs/en_US/pg/indexes-partial.html
+++ b/docs/en_US/pg/indexes-partial.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.7. Partial Indexes
      
-
         A partial index is an index built over a
+
         A partial index is an index built over a
    subset of a table; the subset is defined by a conditional
    expression (called the predicate of the
    partial index).  The index contains entries for only those table
diff --git a/docs/en_US/pg/indexes-types.html b/docs/en_US/pg/indexes-types.html
index 3641e83f7c..f216d837af 100644
--- a/docs/en_US/pg/indexes-types.html
+++ b/docs/en_US/pg/indexes-types.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,8 +20,8 @@
    By default, the CREATE INDEX command will create a
    B-tree index, which fits the most common situations.
   
      
-
         
-   
+
         
+   
    B-trees can handle equality and range queries on data that can be sorted
    into some ordering.
    In particular, the PostgreSQL query planner
@@ -57,8 +57,8 @@
    non-alphabetic characters, i.e. characters that are not affected by
    upper/lower case conversion.
   
      
-
         
-   
+
         
+   
    Hash indexes can only handle simple equality comparisons.
    The query planner will consider using a hash index whenever an
    indexed column is involved in a comparison using the
@@ -79,8 +79,8 @@ 
      Note
      
     For these reasons, hash index use is presently discouraged.
    
      
 
      
-
         
-   
+
         
+   
    GiST indexes are not a single kind of index, but rather an infrastructure
    within which many different indexing strategies can be implemented.
    Accordingly, the particular operators with which a GiST index can be
@@ -113,8 +113,8 @@ 
      Note
      
    classes are available in the contrib collection or as separate
    projects.  For more information see Chapter 50, GiST Indexes.
   
      
-
         
-   
+
         
+   
    GIN indexes are inverted indexes which can handle values that contain more
    than one key, arrays for example. Like GiST, GIN can support
    many different user-defined indexing strategies and the particular 
diff --git a/docs/en_US/pg/indexes-unique.html b/docs/en_US/pg/indexes-unique.html
index b7aa593fdf..b64a96bd85 100644
--- a/docs/en_US/pg/indexes-unique.html
+++ b/docs/en_US/pg/indexes-unique.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 11.5. Unique Indexes
      
-
         Indexes may also be used to enforce uniqueness of a column's value,
+
         Indexes may also be used to enforce uniqueness of a column's value,
    or the uniqueness of the combined values of more than one column.
 
      
 
      CREATE UNIQUE INDEX name ON table (column [, ...]);
      
diff --git a/docs/en_US/pg/indexes.html b/docs/en_US/pg/indexes.html
index a899c257ce..160ce4ff33 100644
--- a/docs/en_US/pg/indexes.html
+++ b/docs/en_US/pg/indexes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -28,7 +28,7 @@
 
      11.9. Examining Index Usage
      
 
      
 
      
-
        Indexes are a common way to enhance database performance.  An index
+
        Indexes are a common way to enhance database performance.  An index
   allows the database server to find and retrieve specific rows much
   faster than it could do without an index.  But indexes also add
   overhead to the database system as a whole, so they should be used
diff --git a/docs/en_US/pg/information-schema.html b/docs/en_US/pg/information-schema.html
index a0b158f540..01b1692597 100644
--- a/docs/en_US/pg/information-schema.html
+++ b/docs/en_US/pg/information-schema.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -66,7 +66,7 @@
 
      32.47. views
      
 
      
 
      
-
        The information schema consists of a set of views that contain
+
        The information schema consists of a set of views that contain
   information about the objects defined in the current database.  The
   information schema is defined in the SQL standard and can therefore
   be expected to be portable and remain stable — unlike the system
diff --git a/docs/en_US/pg/infoschema-administrable-role-authorizations.html b/docs/en_US/pg/infoschema-administrable-role-authorizations.html
index d1d8509c80..3f0cd58364 100644
--- a/docs/en_US/pg/infoschema-administrable-role-authorizations.html
+++ b/docs/en_US/pg/infoschema-administrable-role-authorizations.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    for.
   
      
 
      
-
      Table 32.2. administrable_role_authorizations Columns
      
+
      Table 32.2. administrable_role_authorizations Columns
      
 
    
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
    diff --git a/docs/en_US/pg/infoschema-applicable-roles.html b/docs/en_US/pg/infoschema-applicable-roles.html
index de1f965a0e..152beb38bd 100644
--- a/docs/en_US/pg/infoschema-applicable-roles.html
+++ b/docs/en_US/pg/infoschema-applicable-roles.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,11 +19,11 @@
    some chain of role grants from the current user to the role in
    question.  The current user itself is also an applicable role.  The
    set of applicable roles is generally used for permission checking.
-   
-   
+   
+   
   
    
 
    
-
    Table 32.3. applicable_roles Columns
    
+
    Table 32.3. applicable_roles Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-attributes.html b/docs/en_US/pg/infoschema-attributes.html
index 921dd23db2..4bc067d930 100644
--- a/docs/en_US/pg/infoschema-attributes.html
+++ b/docs/en_US/pg/infoschema-attributes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    which are sometimes called attributes in PostgreSQL contexts.)
   
    
 
    
-
    Table 32.4. attributes Columns
    
+
    Table 32.4. attributes Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-check-constraint-routine-usage.html b/docs/en_US/pg/infoschema-check-constraint-routine-usage.html
index e7d7930c8a..fc262741d4 100644
--- a/docs/en_US/pg/infoschema-check-constraint-routine-usage.html
+++ b/docs/en_US/pg/infoschema-check-constraint-routine-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    a currently enabled role.
   
    
 
    
-
    Table 32.5. check_constraint_routine_usage Columns
    
+
    Table 32.5. check_constraint_routine_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-check-constraints.html b/docs/en_US/pg/infoschema-check-constraints.html
index 9c417571a2..4a162dd6e9 100644
--- a/docs/en_US/pg/infoschema-check-constraints.html
+++ b/docs/en_US/pg/infoschema-check-constraints.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    domain is the owner of the constraint.)
   
    
 
    
-
    Table 32.6. check_constraints Columns
    
+
    Table 32.6. check_constraints Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-column-domain-usage.html b/docs/en_US/pg/infoschema-column-domain-usage.html
index 51cb56ca63..c92a33a6d5 100644
--- a/docs/en_US/pg/infoschema-column-domain-usage.html
+++ b/docs/en_US/pg/infoschema-column-domain-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    in the current database and owned by a currently enabled role.
   
    
 
    
-
    Table 32.7. column_domain_usage Columns
    
+
    Table 32.7. column_domain_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-column-privileges.html b/docs/en_US/pg/infoschema-column-privileges.html
index cc68dcb66b..11f0882f20 100644
--- a/docs/en_US/pg/infoschema-column-privileges.html
+++ b/docs/en_US/pg/infoschema-column-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -33,7 +33,7 @@
    privilege types is concerned.
   
    
 
    
-
    Table 32.8. column_privileges Columns
    
+
    Table 32.8. column_privileges Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-column-udt-usage.html b/docs/en_US/pg/infoschema-column-udt-usage.html
index c748e12e19..755ee06e18 100644
--- a/docs/en_US/pg/infoschema-column-udt-usage.html
+++ b/docs/en_US/pg/infoschema-column-udt-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    also Section 32.12, “columns” for details.
   
    
 
    
-
    Table 32.9. column_udt_usage Columns
    
+
    Table 32.9. column_udt_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-columns.html b/docs/en_US/pg/infoschema-columns.html
index e53fc088dd..772d1d3534 100644
--- a/docs/en_US/pg/infoschema-columns.html
+++ b/docs/en_US/pg/infoschema-columns.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    owner or having some privilege).
   
    
 
    
-
    Table 32.10. columns Columns
    
+
    Table 32.10. columns Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-constraint-column-usage.html b/docs/en_US/pg/infoschema-constraint-column-usage.html
index 778cfee848..e6b0316ed9 100644
--- a/docs/en_US/pg/infoschema-constraint-column-usage.html
+++ b/docs/en_US/pg/infoschema-constraint-column-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
    this view identifies the constrained columns.
   
    
 
    
-
    Table 32.11. constraint_column_usage Columns
    
+
    Table 32.11. constraint_column_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-constraint-table-usage.html b/docs/en_US/pg/infoschema-constraint-table-usage.html
index 39cc5ff002..435cdd9755 100644
--- a/docs/en_US/pg/infoschema-constraint-table-usage.html
+++ b/docs/en_US/pg/infoschema-constraint-table-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -26,7 +26,7 @@
    view.
   
    
 
    
-
    Table 32.12. constraint_table_usage Columns
    
+
    Table 32.12. constraint_table_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-data-type-privileges.html b/docs/en_US/pg/infoschema-data-type-privileges.html
index 9f722940e7..9464e29413 100644
--- a/docs/en_US/pg/infoschema-data-type-privileges.html
+++ b/docs/en_US/pg/infoschema-data-type-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -29,7 +29,7 @@
    information schema.
   
    
 
    
-
    Table 32.13. data_type_privileges Columns
    
+
    Table 32.13. data_type_privileges Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-datatypes.html b/docs/en_US/pg/infoschema-datatypes.html
index e4a7da1cf8..382b7dc457 100644
--- a/docs/en_US/pg/infoschema-datatypes.html
+++ b/docs/en_US/pg/infoschema-datatypes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/infoschema-domain-constraints.html b/docs/en_US/pg/infoschema-domain-constraints.html
index 97d8ea848c..bad373d073 100644
--- a/docs/en_US/pg/infoschema-domain-constraints.html
+++ b/docs/en_US/pg/infoschema-domain-constraints.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,7 +18,7 @@
    constraints belonging to domains defined in the current database.
   
    
 
    
-
    Table 32.14. domain_constraints Columns
    
+
    Table 32.14. domain_constraints Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-domain-udt-usage.html b/docs/en_US/pg/infoschema-domain-udt-usage.html
index d88323c2cd..3d1dc53ade 100644
--- a/docs/en_US/pg/infoschema-domain-udt-usage.html
+++ b/docs/en_US/pg/infoschema-domain-udt-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    well.
   
    
 
    
-
    Table 32.15. domain_udt_usage Columns
    
+
    Table 32.15. domain_udt_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-domains.html b/docs/en_US/pg/infoschema-domains.html
index fae51e1d10..65ef9791cc 100644
--- a/docs/en_US/pg/infoschema-domains.html
+++ b/docs/en_US/pg/infoschema-domains.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,7 +18,7 @@
    the current database.
   
    
 
    
-
    Table 32.16. domains Columns
    
+
    Table 32.16. domains Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-element-types.html b/docs/en_US/pg/infoschema-element-types.html
index d107836202..144d79a78c 100644
--- a/docs/en_US/pg/infoschema-element-types.html
+++ b/docs/en_US/pg/infoschema-element-types.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -35,7 +35,7 @@
    to, by way of being the owner or having some privilege.
   
    
 
    
-
    Table 32.17. element_types Columns
    
+
    Table 32.17. element_types Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-enabled-roles.html b/docs/en_US/pg/infoschema-enabled-roles.html
index e7b2f18500..e8cc090c57 100644
--- a/docs/en_US/pg/infoschema-enabled-roles.html
+++ b/docs/en_US/pg/infoschema-enabled-roles.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,8 +20,8 @@
    granted to the enabled roles with automatic inheritance.  In other
    words, these are all roles that the current user has direct or
    indirect, automatically inheriting membership in.
-   
-   
+   
+   
   
    
 
       For permission checking, the set of “applicable roles”
    is applied, which may be broader than the set of enabled roles.  So
@@ -30,7 +30,7 @@
    there.
   
    
 
    
-
    Table 32.18. enabled_roles Columns
    
+
    Table 32.18. enabled_roles Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-information-schema-catalog-name.html b/docs/en_US/pg/infoschema-information-schema-catalog-name.html
index 33ac02b97c..781d4d298d 100644
--- a/docs/en_US/pg/infoschema-information-schema-catalog-name.html
+++ b/docs/en_US/pg/infoschema-information-schema-catalog-name.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    current database (current catalog, in SQL terminology).
   
    
 
    
-
    Table 32.1. information_schema_catalog_name Columns
    
+
    Table 32.1. information_schema_catalog_name Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-key-column-usage.html b/docs/en_US/pg/infoschema-key-column-usage.html
index 59cb1a1006..79c3f32398 100644
--- a/docs/en_US/pg/infoschema-key-column-usage.html
+++ b/docs/en_US/pg/infoschema-key-column-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    has access to, by way of being the owner or having some privilege.
   
    
 
    
-
    Table 32.19. key_column_usage Columns
    
+
    Table 32.19. key_column_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-parameters.html b/docs/en_US/pg/infoschema-parameters.html
index 30e6aaea80..73b5b739e2 100644
--- a/docs/en_US/pg/infoschema-parameters.html
+++ b/docs/en_US/pg/infoschema-parameters.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    (by way of being the owner or having some privilege).
   
    
 
    
-
    Table 32.20. parameters Columns
    
+
    Table 32.20. parameters Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-referential-constraints.html b/docs/en_US/pg/infoschema-referential-constraints.html
index ccf05e86c2..1f0a23367e 100644
--- a/docs/en_US/pg/infoschema-referential-constraints.html
+++ b/docs/en_US/pg/infoschema-referential-constraints.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    belong to a table owned by a currently enabled role.
   
    
 
    
-
    Table 32.21. referential_constraints Columns
    
+
    Table 32.21. referential_constraints Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-role-column-grants.html b/docs/en_US/pg/infoschema-role-column-grants.html
index 33415123b9..1f5f93e60a 100644
--- a/docs/en_US/pg/infoschema-role-column-grants.html
+++ b/docs/en_US/pg/infoschema-role-column-grants.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    column_privileges.
   
    
 
    
-
    Table 32.22. role_column_grants Columns
    
+
    Table 32.22. role_column_grants Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-role-routine-grants.html b/docs/en_US/pg/infoschema-role-routine-grants.html
index 8e9454c006..b1afb7c60a 100644
--- a/docs/en_US/pg/infoschema-role-routine-grants.html
+++ b/docs/en_US/pg/infoschema-role-routine-grants.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    routine_privileges.
   
    
 
    
-
    Table 32.23. role_routine_grants Columns
    
+
    Table 32.23. role_routine_grants Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-role-table-grants.html b/docs/en_US/pg/infoschema-role-table-grants.html
index 0fba2ae32f..1af1f3ee8a 100644
--- a/docs/en_US/pg/infoschema-role-table-grants.html
+++ b/docs/en_US/pg/infoschema-role-table-grants.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    under table_privileges.
   
    
 
    
-
    Table 32.24. role_table_grants Columns
    
+
    Table 32.24. role_table_grants Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-role-usage-grants.html b/docs/en_US/pg/infoschema-role-usage-grants.html
index 2ae1b74a9e..9ae97dd6f6 100644
--- a/docs/en_US/pg/infoschema-role-usage-grants.html
+++ b/docs/en_US/pg/infoschema-role-usage-grants.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -25,7 +25,7 @@
    contain more useful information.
   
    
 
    
-
    Table 32.25. role_usage_grants Columns
    
+
    Table 32.25. role_usage_grants Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-routine-privileges.html b/docs/en_US/pg/infoschema-routine-privileges.html
index 01d1fbf63c..341e82f632 100644
--- a/docs/en_US/pg/infoschema-routine-privileges.html
+++ b/docs/en_US/pg/infoschema-routine-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    grantor, and grantee.
   
    
 
    
-
    Table 32.26. routine_privileges Columns
    
+
    Table 32.26. routine_privileges Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-routines.html b/docs/en_US/pg/infoschema-routines.html
index e11742f864..bca55d6b25 100644
--- a/docs/en_US/pg/infoschema-routines.html
+++ b/docs/en_US/pg/infoschema-routines.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    privilege).
   
    
 
    
-
    Table 32.27. routines Columns
    
+
    Table 32.27. routines Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-schemata.html b/docs/en_US/pg/infoschema-schemata.html
index ea91e0e473..ef93a0933d 100644
--- a/docs/en_US/pg/infoschema-schemata.html
+++ b/docs/en_US/pg/infoschema-schemata.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,7 +18,7 @@
    current database that are owned by a currently enabled role.
   
    
 
    
-
    Table 32.28. schemata Columns
    
+
    Table 32.28. schemata Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sequences.html b/docs/en_US/pg/infoschema-sequences.html
index d0f341d86c..469d78f4cf 100644
--- a/docs/en_US/pg/infoschema-sequences.html
+++ b/docs/en_US/pg/infoschema-sequences.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    having some privilege).
   
    
 
    
-
    Table 32.29. sequences Columns
    
+
    Table 32.29. sequences Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-features.html b/docs/en_US/pg/infoschema-sql-features.html
index e87db510a8..9c89a94e1d 100644
--- a/docs/en_US/pg/infoschema-sql-features.html
+++ b/docs/en_US/pg/infoschema-sql-features.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    There you can also find some additional background information.
   
    
 
    
-
    Table 32.30. sql_features Columns
    
+
    Table 32.30. sql_features Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-implementation-info.html b/docs/en_US/pg/infoschema-sql-implementation-info.html
index ff9044c81c..6f4a85085f 100644
--- a/docs/en_US/pg/infoschema-sql-implementation-info.html
+++ b/docs/en_US/pg/infoschema-sql-implementation-info.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
    description of the ODBC interface.
   
    
 
    
-
    Table 32.31. sql_implementation_info Columns
    
+
    Table 32.31. sql_implementation_info Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-languages.html b/docs/en_US/pg/infoschema-sql-languages.html
index de568a7755..1cf98cff3e 100644
--- a/docs/en_US/pg/infoschema-sql-languages.html
+++ b/docs/en_US/pg/infoschema-sql-languages.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    embedded SQL in C; that is all you will learn from this table.
   
    
 
    
-
    Table 32.32. sql_languages Columns
    
+
    Table 32.32. sql_languages Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-packages.html b/docs/en_US/pg/infoschema-sql-packages.html
index 096d6ebcc4..35996f14f5 100644
--- a/docs/en_US/pg/infoschema-sql-packages.html
+++ b/docs/en_US/pg/infoschema-sql-packages.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    supported by PostgreSQL.  Refer to Appendix D, SQL Conformance for background information on feature packages.
   
    
 
    
-
    Table 32.33. sql_packages Columns
    
+
    Table 32.33. sql_packages Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-parts.html b/docs/en_US/pg/infoschema-sql-parts.html
index 712cf1dcc1..a515c42c25 100644
--- a/docs/en_US/pg/infoschema-sql-parts.html
+++ b/docs/en_US/pg/infoschema-sql-parts.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    PostgreSQL.
   
    
 
    
-
    Table 32.34. sql_parts Columns
    
+
    Table 32.34. sql_parts Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-sizing-profiles.html b/docs/en_US/pg/infoschema-sql-sizing-profiles.html
index c8ce278696..525c7dd618 100644
--- a/docs/en_US/pg/infoschema-sql-sizing-profiles.html
+++ b/docs/en_US/pg/infoschema-sql-sizing-profiles.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    not track any SQL profiles, so this table is empty.
   
    
 
    
-
    Table 32.36. sql_sizing_profiles Columns
    
+
    Table 32.36. sql_sizing_profiles Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-sql-sizing.html b/docs/en_US/pg/infoschema-sql-sizing.html
index fdbeaf93d8..e297e7dfc9 100644
--- a/docs/en_US/pg/infoschema-sql-sizing.html
+++ b/docs/en_US/pg/infoschema-sql-sizing.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
    ODBC interface.
   
    
 
    
-
    Table 32.35. sql_sizing Columns
    
+
    Table 32.35. sql_sizing Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-table-constraints.html b/docs/en_US/pg/infoschema-table-constraints.html
index 9f20128fa1..b051a166fb 100644
--- a/docs/en_US/pg/infoschema-table-constraints.html
+++ b/docs/en_US/pg/infoschema-table-constraints.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    some privilege on.
   
    
 
    
-
    Table 32.37. table_constraints Columns
    
+
    Table 32.37. table_constraints Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-table-privileges.html b/docs/en_US/pg/infoschema-table-privileges.html
index e515c177b1..5c3cf444ce 100644
--- a/docs/en_US/pg/infoschema-table-privileges.html
+++ b/docs/en_US/pg/infoschema-table-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    combination of table, grantor, and grantee.
   
    
 
    
-
    Table 32.38. table_privileges Columns
    
+
    Table 32.38. table_privileges Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-tables.html b/docs/en_US/pg/infoschema-tables.html
index fefafa5411..93094725b9 100644
--- a/docs/en_US/pg/infoschema-tables.html
+++ b/docs/en_US/pg/infoschema-tables.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
    owner or having some privilege).
   
    
 
    
-
    Table 32.39. tables Columns
    
+
    Table 32.39. tables Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-triggers.html b/docs/en_US/pg/infoschema-triggers.html
index aaa73aa0fa..ea30a28026 100644
--- a/docs/en_US/pg/infoschema-triggers.html
+++ b/docs/en_US/pg/infoschema-triggers.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    some privilege on.
   
    
 
    
-
    Table 32.40. triggers Columns
    
+
    Table 32.40. triggers Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-usage-privileges.html b/docs/en_US/pg/infoschema-usage-privileges.html
index 2b7b44350d..fcaba5f4bb 100644
--- a/docs/en_US/pg/infoschema-usage-privileges.html
+++ b/docs/en_US/pg/infoschema-usage-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -25,7 +25,7 @@
    view may contain more useful information.
   
    
 
    
-
    Table 32.41. usage_privileges Columns
    
+
    Table 32.41. usage_privileges Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-view-column-usage.html b/docs/en_US/pg/infoschema-view-column-usage.html
index 1592b3d951..cec3884d18 100644
--- a/docs/en_US/pg/infoschema-view-column-usage.html
+++ b/docs/en_US/pg/infoschema-view-column-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -27,7 +27,7 @@ 
    Note
    
    
    
 
 
    
-
    Table 32.42. view_column_usage Columns
    
+
    Table 32.42. view_column_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-view-routine-usage.html b/docs/en_US/pg/infoschema-view-routine-usage.html
index 5cbe744ad9..41b164c3fd 100644
--- a/docs/en_US/pg/infoschema-view-routine-usage.html
+++ b/docs/en_US/pg/infoschema-view-routine-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
    owned by a currently enabled role.
   
    
 
    
-
    Table 32.43. view_routine_usage Columns
    
+
    Table 32.43. view_routine_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-view-table-usage.html b/docs/en_US/pg/infoschema-view-table-usage.html
index 9af3ba3232..810eb1aa3c 100644
--- a/docs/en_US/pg/infoschema-view-table-usage.html
+++ b/docs/en_US/pg/infoschema-view-table-usage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -26,7 +26,7 @@ 
    Note
    
    
    
 
 
    
-
    Table 32.44. view_table_usage Columns
    
+
    Table 32.44. view_table_usage Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/infoschema-views.html b/docs/en_US/pg/infoschema-views.html
index fcbac4c482..0c724124b5 100644
--- a/docs/en_US/pg/infoschema-views.html
+++ b/docs/en_US/pg/infoschema-views.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    has access to (by way of being the owner or having some privilege).
   
    
 
    
-
    Table 32.45. views Columns
    
+
    Table 32.45. views Columns
    
 
    
 
 

    diff --git a/docs/en_US/pg/install-getsource.html b/docs/en_US/pg/install-getsource.html
index c75cede50d..0302f8bd54 100644
--- a/docs/en_US/pg/install-getsource.html
+++ b/docs/en_US/pg/install-getsource.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,17 +14,17 @@
 
    
 
    
 14.3. Getting The Source
    
-
       The PostgreSQL 8.2.0 sources can be obtained by
-   anonymous FTP from ftp://ftp.postgresql.org/pub/source/v8.2.0/postgresql-8.2.0.tar.gz.
+
       The PostgreSQL 8.2.1 sources can be obtained by
+   anonymous FTP from ftp://ftp.postgresql.org/pub/source/v8.2.1/postgresql-8.2.1.tar.gz.
    Other download options can be found on our website:
    http://www.postgresql.org/download/. After you
    have obtained the file, unpack it:
 
    
-
    gunzip postgresql-8.2.0.tar.gz
-tar xf postgresql-8.2.0.tar
    
+
    gunzip postgresql-8.2.1.tar.gz
+tar xf postgresql-8.2.1.tar
    
 
    
    This will create a directory
-   postgresql-8.2.0 under the current directory
+   postgresql-8.2.1 under the current directory
    with the PostgreSQL sources.
    Change into that directory for the rest
    of the installation procedure.
diff --git a/docs/en_US/pg/install-post.html b/docs/en_US/pg/install-post.html
index 7be5afbc39..33a78aac1d 100644
--- a/docs/en_US/pg/install-post.html
+++ b/docs/en_US/pg/install-post.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -16,8 +16,8 @@
 14.6. Post-Installation Setup
    
 
    
 
    
-14.6.1. Shared Libraries
    
-
        On some systems that have shared libraries (which most systems do)
+14.6.1. Shared Libraries
    
+
        On some systems that have shared libraries (which most systems do)
     you need to tell your system how to find the newly installed
     shared libraries.  The systems on which this is
     not necessary include BSD/OS, FreeBSD,
@@ -63,7 +63,7 @@
 
    
     then this step was necessary.  Simply take care of it then.
    
    
-
        
+
        
     If you are on BSD/OS, Linux, or SunOS 4
     and you have root access you can run
 
    
@@ -82,8 +82,8 @@
 
 
    
 
    
-14.6.2. Environment Variables
    
-
        If you installed into /usr/local/pgsql or some other
+14.6.2. Environment Variables
    
+
        If you installed into /usr/local/pgsql or some other
     location that is not searched for programs by default, you should
     add /usr/local/pgsql/bin (or whatever you set
     --bindir to in Step 1)
@@ -103,7 +103,7 @@
 
    set path = ( /usr/local/pgsql/bin $path )
    
 
    
    
    
-
        
+
        
     To enable your system to find the man
     documentation, you need to add lines like the following to a
     shell start-up file unless you installed into a location that is
diff --git a/docs/en_US/pg/install-procedure.html b/docs/en_US/pg/install-procedure.html
index a043c122f3..f5d74993cf 100644
--- a/docs/en_US/pg/install-procedure.html
+++ b/docs/en_US/pg/install-procedure.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
      
 
    1. 
 
      Configuration
      
-
          The first step of the installation procedure is to configure the
+
          The first step of the installation procedure is to configure the
     source tree for your system and choose the options you would like.
     This is done by running the configure script. For a
     default installation simply enter
@@ -239,11 +239,11 @@ 
      Note
      
          before proceeding.
         
      
 
      --with-pam
      
-
               Build with PAM
+
               Build with PAM
          (Pluggable Authentication Modules) support.
         
      
 
      --with-ldap
      
-
               Build with LDAP
+
               Build with LDAP
          support for authentication and connection parameter lookup (see 
          Section 29.15, “LDAP Lookup of Connection Parameters” and
          Section 20.2.5, “LDAP authentication” for more information). On Unix,
@@ -299,7 +299,7 @@ 
      Note
      
          threading support in your operating system.
         
      
 
      --without-zlib
      
-
               
+
               
          Prevents use of the Zlib library.  This disables
          support for compressed archives in pg_dump
          and pg_restore.
@@ -340,7 +340,7 @@ 
      Note
      
         
      
 
      --enable-dtrace
      
 
      
-
               
+
               
          Compiles with support for the dynamic tracing tool DTrace.
          Operating system support for DTrace is currently only
          available in Solaris.
@@ -354,6 +354,18 @@ 
      Note
      
          specified in the environment variable
          DTRACEFLAGS.
         
      
+
               To include DTrace support in a 64-bit binary, specify
+         DTRACEFLAGS="-64" to configure.  For example,
+         using the GCC compiler:
+
      
+
      ./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ...
      
+
                  
+         Using Sun's compiler:
+
      
+
                  
+./configure CC='/opt/SUNWspro/bin/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64' ...
      
+
      
+        
      
 
      
 
    
 
    
@@ -439,7 +451,7 @@ 
    Note
    
 
 
  • 
 
    Regression Tests
    
-
        If you want to test the newly built server before you install it,
+
        If you want to test the newly built server before you install it,
     you can run the regression tests at this point. The regression
     tests are a test suite to verify that PostgreSQL
     runs on your machine in the way the developers expected it
diff --git a/docs/en_US/pg/install-requirements.html b/docs/en_US/pg/install-requirements.html
index 8dde423041..e881e2e84e 100644
--- a/docs/en_US/pg/install-requirements.html
+++ b/docs/en_US/pg/install-requirements.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -28,7 +28,7 @@
    
    
 
    • 
 
 

    
 
-
         The most important
+
         The most important
     shared memory parameter is SHMMAX, the maximum size, in
     bytes, of a shared memory segment. If you get an error message from
     shmget like Invalid argument, it is
@@ -514,7 +514,7 @@
 
 
    
 
    
-16.4.2. Resource Limits
    
+16.4.2. Resource Limits
    
 
        Unix-like operating systems enforce various kinds of resource limits
     that might interfere with the operation of your
     PostgreSQL server. Of particular
@@ -582,7 +582,7 @@
 
 
    
 
    
-16.4.3. Linux Memory Overcommit
    
+16.4.3. Linux Memory Overcommit
    
 
        In Linux 2.4 and later, the default virtual memory behavior is not
     optimal for PostgreSQL. Because of the
     way that the kernel implements memory overcommit, the kernel may
diff --git a/docs/en_US/pg/largeobjects.html b/docs/en_US/pg/largeobjects.html
index e3cb55b232..4b17d6f633 100644
--- a/docs/en_US/pg/largeobjects.html
+++ b/docs/en_US/pg/largeobjects.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,22 +21,22 @@
 
    30.2. Implementation Features
    
 
    30.3. Client Interfaces
    
 
    
-
    30.3.1. Creating a Large Object
    
-
    30.3.2. Importing a Large Object
    
-
    30.3.3. Exporting a Large Object
    
-
    30.3.4. Opening an Existing Large Object
    
-
    30.3.5. Writing Data to a Large Object
    
-
    30.3.6. Reading Data from a Large Object
    
-
    30.3.7. Seeking in a Large Object
    
-
    30.3.8. Obtaining the Seek Position of a Large Object
    
-
    30.3.9. Closing a Large Object Descriptor
    
-
    30.3.10. Removing a Large Object
    
+
    30.3.1. Creating a Large Object
    
+
    30.3.2. Importing a Large Object
    
+
    30.3.3. Exporting a Large Object
    
+
    30.3.4. Opening an Existing Large Object
    
+
    30.3.5. Writing Data to a Large Object
    
+
    30.3.6. Reading Data from a Large Object
    
+
    30.3.7. Seeking in a Large Object
    
+
    30.3.8. Obtaining the Seek Position of a Large Object
    
+
    30.3.9. Closing a Large Object Descriptor
    
+
    30.3.10. Removing a Large Object
    
 
    
 
    30.4. Server-Side Functions
    
 
    30.5. Example Program
    
 
 
-
        PostgreSQL has a large object
+
        PostgreSQL has a large object
     facility, which provides stream-style access to user data that is stored
     in a special large-object structure.  Streaming access is useful
     when working with data values that are too large to manipulate
@@ -54,7 +54,7 @@
 
    
 
    
 30.1. Introduction
    
-
        All large objects are placed in a single system table called
+
        All large objects are placed in a single system table called
     pg_largeobject.
     PostgreSQL also supports a storage system called
     “TOAST” that automatically stores values
diff --git a/docs/en_US/pg/libpq-async.html b/docs/en_US/pg/libpq-async.html
index cb85624cf5..4ef15c554f 100644
--- a/docs/en_US/pg/libpq-async.html
+++ b/docs/en_US/pg/libpq-async.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.4. Asynchronous Command Processing
    
-
    The PQexec function is adequate for submitting commands in
+
    The PQexec function is adequate for submitting commands in
 normal, synchronous
 applications.  It has a couple of deficiencies, however, that can be of importance to some users:
 
@@ -51,7 +51,7 @@
 
 
    
 
    
-
    PQsendQuery
    
+
    PQsendQuery
    
 
    
 
              Submits a command to the server without
           waiting for the result(s).  1 is returned if the command was
@@ -67,7 +67,7 @@
           again (on the same connection) until PQgetResult has returned a null pointer,
           indicating that the command is done.
    
 
    
-
    PQsendQueryParams
    
+
    PQsendQueryParams
    
 
    
 
              Submits a command and separate parameters to the server without
           waiting for the result(s).
@@ -89,7 +89,7 @@
         PQexecParams, it will not work on 2.0-protocol
         connections, and it allows only one command in the query string.
    
 
    
-
    PQsendPrepare
    
+
    PQsendPrepare
    
 
    
 
            Sends a request to create a prepared statement with the given
         parameters, without waiting for completion.
@@ -111,7 +111,7 @@
         PQprepare, it will not work on 2.0-protocol
         connections.
    
 
    
-
    PQsendQueryPrepared
    
+
    PQsendQueryPrepared
    
 
    
 
              Sends a request to execute a prepared statement with given
           parameters, without waiting for the result(s).
@@ -133,7 +133,7 @@
         PQexecPrepared, it will not work on 2.0-protocol
         connections.
    
 
    
-
    PQsendDescribePrepared
    
+
    PQsendDescribePrepared
    
 
    
 
            Submits a request to obtain information about the specified
         prepared statement, without waiting for completion.
@@ -150,7 +150,7 @@
         PQdescribePrepared, it will not work on 2.0-protocol
         connections.
    
 
    
-
    PQsendDescribePortal
    
+
    PQsendDescribePortal
    
 
    
 
            Submits a request to obtain information about the specified
         portal, without waiting for completion.
@@ -167,7 +167,7 @@
         PQdescribePortal, it will not work on 2.0-protocol
         connections.
    
 
    
-
    PQgetResult
    
+
    PQgetResult
    
 
    
 
              Waits for the next result from a prior
           PQsendQuery,
@@ -201,7 +201,7 @@
 
 
    
 
    
-
    PQconsumeInput
    
+
    PQconsumeInput
    
 
    
 
              If input is available from the server, consume it.
 
    
@@ -221,7 +221,7 @@
 application can thus use PQconsumeInput to clear the
 select() condition immediately, and then examine the results at leisure.
    
 
    
-
    PQisBusy
    
+
    PQisBusy
    
 
    
 
    Returns 1 if a command is busy, that is, PQgetResult would block
 waiting for input.  A 0 return indicates that PQgetResult can
@@ -263,7 +263,7 @@
 
 
    
 
    
-
    PQsetnonblocking
    
+
    PQsetnonblocking
    
 
    
 
        Sets the nonblocking status of the connection.
 
    
@@ -283,7 +283,7 @@
     if it is called, it will act in blocking fashion anyway.
    
    
 
    
-
    PQisnonblocking
    
+
    PQisnonblocking
    
 
    
 
           Returns the blocking status of the database connection.
 
    
@@ -291,7 +291,7 @@
 
           Returns 1 if the connection is set to nonblocking mode and
        0 if blocking.
    
 
    
-
    PQflush
    
+
    PQflush
    
 
    
 
    Attempts to flush any queued output data to the server.
 Returns 0 if successful (or if the send queue is empty), -1 if it failed for
diff --git a/docs/en_US/pg/libpq-build.html b/docs/en_US/pg/libpq-build.html
index 8afda4e274..b6114ba3bc 100644
--- a/docs/en_US/pg/libpq-build.html
+++ b/docs/en_US/pg/libpq-build.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.18. Building libpq Programs
    
-
       To build (i.e., compile and link) a program using
+
       To build (i.e., compile and link) a program using
    libpq you need to 
    do all of the following things:
 
@@ -57,7 +57,7 @@
 
          If there is any chance that your program might be compiled by
       other users then you should not hardcode the directory location
       like that.  Instead, you can run the utility
-      pg_config to find out where the header
+      pg_config to find out where the header
       files are on the local system:
 
    
 
    $ pg_config --includedir
diff --git a/docs/en_US/pg/libpq-cancel.html b/docs/en_US/pg/libpq-cancel.html
index 49f834b4d3..0b0ef41445 100644
--- a/docs/en_US/pg/libpq-cancel.html
+++ b/docs/en_US/pg/libpq-cancel.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,27 +14,27 @@
 
    
 
    
 29.5. Cancelling Queries in Progress
    
-
    A client application can request cancellation of
+
    A client application can request cancellation of
 a command that is still being processed by the
 server, using the functions described in this section.
 
 
    
 
    
-
    PQgetCancel
    
+
    PQgetCancel
    
 
    
 
              Creates a data structure containing the information needed to cancel
           a command issued through a particular database connection.
 
    
 
    PGcancel *PQgetCancel(PGconn *conn);
    
 
    PQgetCancel creates a 
-PGcancel object given
+PGcancel object given
 a PGconn connection object.  It will return NULL if the
 given conn is NULL or an invalid connection.  The
 PGcancel object is an opaque structure that is not meant
 to be accessed directly by the application; it can only be passed to
 PQcancel or PQfreeCancel.
    
 
    
-
    PQfreeCancel
    
+
    PQfreeCancel
    
 
    
 
              Frees a data structure created by PQgetCancel.
 
    
@@ -42,7 +42,7 @@
 
    PQfreeCancel frees a data object previously created
 by PQgetCancel.
    
 
    
-
    PQcancel
    
+
    PQcancel
    
 
    
 
              Requests that the server abandon
           processing of the current command.
@@ -69,7 +69,7 @@
 
 
    
 
    
-
    PQrequestCancel
    
+
    PQrequestCancel
    
 
    
 
              Requests that the server abandon
           processing of the current command.
diff --git a/docs/en_US/pg/libpq-control.html b/docs/en_US/pg/libpq-control.html
index 82a8c9a5b3..1ed94f5f96 100644
--- a/docs/en_US/pg/libpq-control.html
+++ b/docs/en_US/pg/libpq-control.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    These functions control miscellaneous details of
 libpq's behavior.
    
 
    
-
    PQsetErrorVerbosity
    
+
    PQsetErrorVerbosity
    
 
    
 
    Determines the verbosity of messages returned by
 PQerrorMessage and PQresultErrorMessage.
@@ -40,7 +40,7 @@
 affect the messages available from already-existing
 PGresult objects, only subsequently-created ones.
    
 
    
-
    PQtrace
    
+
    PQtrace
    
 
    
 
              Enables  tracing of the client/server communication to a debugging file stream.
 
    
@@ -55,7 +55,7 @@ 
    Note
    
 library and all applications using that library.
    
 
    
 
    
-
    PQuntrace
    
+
    PQuntrace
    
 
    
 
              Disables tracing started by PQtrace.
 
    
diff --git a/docs/en_US/pg/libpq-copy.html b/docs/en_US/pg/libpq-copy.html
index ede5708d22..6805779563 100644
--- a/docs/en_US/pg/libpq-copy.html
+++ b/docs/en_US/pg/libpq-copy.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.8. Functions Associated with the COPY Command
    
-
     The COPY command in PostgreSQL
+
     The COPY command in PostgreSQL
  has options to read from or write to the network connection used by
  libpq.  The functions described in this section
  allow applications to take advantage of this capability by supplying or
@@ -52,16 +52,16 @@
 
 
    
 
    
-
    PQnfields
    
+
    PQnfields
    
 
              Returns the number of columns (fields) to be copied.
    
-
    PQbinaryTuples
    
+
    PQbinaryTuples
    
 
                    0 indicates the overall copy format is textual (rows
                 separated by newlines, columns separated by separator
                 characters, etc).
                 1 indicates the overall copy format is binary.
                 See COPY
                 for more information.
    
-
    PQfformat
    
+
    PQfformat
    
 
              Returns the format code (0 for text, 1 for binary) associated
           with each column of the copy operation.  The per-column format
           codes will always be zero when the overall copy format is textual,
@@ -82,7 +82,7 @@ 
    Note
    
  They will fail if called when the connection is not in COPY_IN
  state.
    
 
    
-
    PQputCopyData
    
+
    PQputCopyData
    
 
    
 
     Sends data to the server during COPY_IN state.
 
    
@@ -101,7 +101,7 @@ 
    Note
    
 by the COPY command; see
 COPY for details.
    
 
    
-
    PQputCopyEnd
    
+
    PQputCopyEnd
    
 
    
 
     Sends end-of-data indication to the server during COPY_IN state.
 
    
@@ -134,7 +134,7 @@ 
    Note
    
  They will fail if called when the connection is not in COPY_OUT
  state.
    
 
    
-
    PQgetCopyData
    
+
    PQgetCopyData
    
 
    
 
     Receives data from the server during COPY_OUT state.
 
    
@@ -181,7 +181,7 @@ 
    Note
    
  inconvenient methods of detecting end-of-data, and lack of support for binary
  or nonblocking transfers.
    
 
    
-
    PQgetline
    
+
    PQgetline
    
 
    
 
              Reads  a  newline-terminated  line  of  characters
           (transmitted  by the server) into a buffer
@@ -206,7 +206,7 @@ 
    Note
    
 (and does not, for example, mistake the end of a long data line
 for a terminator line).
    
 
    
-
    PQgetlineAsync
    
+
    PQgetlineAsync
    
 
    
 
              Reads a row of COPY data
           (transmitted  by the server) into a buffer
@@ -243,7 +243,7 @@ 
    Note
    
 terminating null, be sure to pass a bufsize one smaller
 than the room actually available.)
    
 
    
-
    PQputline
    
+
    PQputline
    
 
    
 
    Sends  a  null-terminated  string  to  the server.
 Returns 0 if OK and EOF if unable to send the string.
@@ -266,7 +266,7 @@ 
    Note
    
 having sent the actual data.
    
 
    
 
    
-
    PQputnbytes
    
+
    PQputnbytes
    
 
    
 
    Sends  a  non-null-terminated  string  to  the server.
 Returns 0 if OK and EOF if unable to send the string.
@@ -278,7 +278,7 @@ 
    Note
    
 buffer need not be null-terminated since the number of bytes to send is
 specified directly.  Use this procedure when sending binary data.
    
 
    
-
    PQendcopy
    
+
    PQendcopy
    
 
    
 
     Synchronizes with the server.
 
    
diff --git a/docs/en_US/pg/libpq-envars.html b/docs/en_US/pg/libpq-envars.html
index e539581757..e5115a8cee 100644
--- a/docs/en_US/pg/libpq-envars.html
+++ b/docs/en_US/pg/libpq-envars.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.12. Environment Variables
    
-
    The following environment variables can be used to select default
+
    The following environment variables can be used to select default
 connection parameter values, which will be used by
 PQconnectdb, PQsetdbLogin and
 PQsetdb if no value is directly specified by the calling
@@ -23,14 +23,14 @@
 
 
    
 
      
-
    • 
+
    • 
 PGHOST sets the database server name.
 If this begins with a slash, it specifies Unix-domain communication
 rather than TCP/IP communication; the value is then the name of the
 directory in which the socket file is stored (in a default installation
 setup this would be /tmp).
      • 
 
    • 
-
      
+
      
 PGHOSTADDR specifies the numeric IP address of the database
 server.  This can be set instead of or in addition to PGHOST
 to avoid DNS lookup overhead. See the documentation of
@@ -41,17 +41,17 @@
 machines without Unix-domain sockets, libpq will
 attempt to connect to localhost.
      
 
      • 
-
    • 
+
    • 
 PGPORT sets the TCP port number or Unix-domain
 socket file extension for communicating with the
 PostgreSQL server.
      • 
-
    • 
+
    • 
 PGDATABASE  sets the 
 PostgreSQL database name.
      • 
-
    • 
+
    • 
 PGUSER
 sets the user name used to connect to the database.
      • 
-
    • 
+
    • 
 PGPASSWORD
 sets the password used if the server demands password
 authentication.  Use of this environment variable is not 
@@ -59,16 +59,16 @@
 allow non-root users to see process environment variables via
 ps); instead consider using  the 
 ~/.pgpass file (see Section 29.13, “The Password File”).
      • 
-
    • 
+
    • 
 PGPASSFILE
 specifies the name of the password file to use for lookups.
 If not set, it defaults to ~/.pgpass
 (see Section 29.13, “The Password File”).
      • 
-
    • 
+
    • 
 PGSERVICE
 sets the service name to be looked up in pg_service.conf.
 This offers a shorthand way of setting all the parameters.
      • 
-
    • 
+
    • 
 PGREALM sets the Kerberos realm to  use  with  
 PostgreSQL, if  it is different from the local realm.
 If PGREALM is set, libpq
@@ -76,10 +76,10 @@
 separate ticket files to avoid conflicts with  local
 ticket  files.   This  environment  variable is only
 used if Kerberos authentication is selected by the server.
      • 
-
    • 
+
    • 
 PGOPTIONS sets additional run-time  options  for  
 the PostgreSQL server.
      • 
-
    • 
+
    • 
 PGSSLMODE determines whether and with what priority an
 SSL connection will be negotiated with the server. There are
 four modes: disable will attempt only an unencrypted
@@ -94,7 +94,7 @@
 allow and prefer will be accepted but
 libpq will not in fact attempt an SSL
 connection.
      • 
-
    • 
+
    • 
 PGREQUIRESSL sets whether or not the connection must be
 made over SSL. If set to
 “1”, libpq
@@ -104,10 +104,10 @@
 This option is deprecated in favor of the sslmode
 setting, and is only available if
 PostgreSQL is compiled with SSL support.
      • 
-
    • 
+
    • 
 PGKRBSRVNAME sets the Kerberos service name to use when
 authenticating with Kerberos 5.
      • 
-
    • 
+
    • 
 PGCONNECT_TIMEOUT sets the maximum number of seconds
 that libpq will wait when attempting to
 connect to the PostgreSQL server.  If unset
@@ -124,19 +124,19 @@
 
 
      
 
        
-
      • 
+
      • 
 PGDATESTYLE
 sets the default style of date/time representation.
 (Equivalent to SET datestyle TO ....)
        • 
-
      • 
+
      • 
 PGTZ
 sets the default time zone.
 (Equivalent to SET timezone TO ....)
        • 
-
      • 
+
      • 
 PGCLIENTENCODING
 sets the default client character set encoding.
 (Equivalent to SET client_encoding TO ....)
        • 
-
      • 
+
      • 
 PGGEQO
 sets the default mode for the genetic query optimizer.
 (Equivalent to SET geqo TO ....)
        • 
@@ -151,10 +151,10 @@
 
 
        
 
          
-
        • 
+
        • 
 PGSYSCONFDIR
 sets the directory containing the pg_service.conf file.
          • 
-
        • 
+
        • 
 PGLOCALEDIR
 sets the directory containing the locale files for message
 internationalization.
          • 
diff --git a/docs/en_US/pg/libpq-example.html b/docs/en_US/pg/libpq-example.html
index ddf3beb2f3..17c9f1b7a0 100644
--- a/docs/en_US/pg/libpq-example.html
+++ b/docs/en_US/pg/libpq-example.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/libpq-exec.html b/docs/en_US/pg/libpq-exec.html
index 78e4939ee0..c9b1b638c7 100644
--- a/docs/en_US/pg/libpq-exec.html
+++ b/docs/en_US/pg/libpq-exec.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
 
          
 29.3.1. Main Functions
          
 
          
-
          PQexec
          
+
          PQexec
          
 
          
 
                    Submits a command to the server
           and waits for the result.
@@ -49,7 +49,7 @@
 it and the returned PGresult describes the error
 condition.
          
 
          
-
          PQexecParams
          
+
          PQexecParams
          
 
          
 
                    Submits a command to the server and waits for the result,
           with the ability to pass parameters separately from the SQL
@@ -147,7 +147,7 @@ 
          Tip
          
 that the server will detect a type mismatch mistake for you.
          
 
          
 
          
-
          PQprepare
          
+
          PQprepare
          
 
          
 
                    Submits a request to create a prepared statement with the
           given parameters, and waits for completion.
@@ -200,7 +200,7 @@ 
          Tip
          
 function for deleting a prepared statement, the SQL DEALLOCATE statement can
 be used for that purpose.
          
 
          
-
          PQexecPrepared
          
+
          PQexecPrepared
          
 
          
 
                    Sends a request to execute a prepared statement with given
           parameters, and waits for the result.
@@ -226,7 +226,7 @@ 
          Tip
          
 paramTypes[] parameter is not present (it is not needed since
 the prepared statement's parameter types were determined when it was created).
          
 
          
-
          PQdescribePrepared
          
+
          PQdescribePrepared
          
 
          
 
                    Submits a request to obtain information about the specified
           prepared statement, and waits for completion.
@@ -247,7 +247,7 @@ 
          Tip
          
 PQftype, etc provide information about the result
 columns (if any) of the statement.
          
 
          
-
          PQdescribePortal
          
+
          PQdescribePortal
          
 
          
 
                    Submits a request to obtain information about the specified
           portal, and waits for completion.
@@ -270,7 +270,7 @@ 
          Tip
          
 
          
 
          
 
          The
-PGresult
+PGresult
 structure encapsulates the result returned by the server.
 libpq application programmers should be
 careful to maintain the PGresult abstraction.
@@ -281,7 +281,7 @@ 
          Tip
          
 
 
          
 
          
-
          PQresultStatus
          
+
          PQresultStatus
          
 
          
 
                    Returns the result status of the command.
 
          
@@ -323,7 +323,7 @@ 
          Tip
          
 execution functions; results of this kind are instead passed to the notice
 processor (see Section 29.11, “Notice Processing”).
          
 
          
-
          PQresStatus
          
+
          PQresStatus
          
 
          
 
                  Converts the enumerated type returned by PQresultStatus into
         a string constant describing the status code. The caller should not 
@@ -331,7 +331,7 @@ 
          Tip
          
 
          
 
          char *PQresStatus(ExecStatusType status);
          
 
          
-
          PQresultErrorMessage
          
+
          PQresultErrorMessage
          
 
          
 
          Returns the error message associated with the command, or an empty string
 if there was no error.
@@ -351,7 +351,7 @@ 
          Tip
          
 know the status associated with a particular PGresult; use PQerrorMessage
 when you want to know the status from the latest operation on the connection.
          
 
          
-
          PQresultErrorField
          
+
          PQresultErrorField
          
 
          
 
          Returns an individual field of an error report.
 
          
@@ -432,7 +432,7 @@ 
          Tip
          
 PGconn objects; there is no
 PQerrorField function.
          
 
          
-
          PQclear
          
+
          PQclear
          
 
          
 
                    Frees  the  storage  associated with a PGresult.
           Every command result should be freed via PQclear when
@@ -445,7 +445,7 @@ 
          Tip
          
           you must call PQclear.  Failure to do this will
           result in memory leaks in your application.
          
 
          
-
          PQmakeEmptyPGresult
          
+
          PQmakeEmptyPGresult
          
 
          
 
                    Constructs an empty PGresult object with the given status.
 
          
@@ -476,21 +476,21 @@ 
          Tip
          
 would provide, but it has zero rows.  For objects with other status values,
 these functions will act as though the result has zero rows and zero columns.
          
 
          
-
          PQntuples
          
+
          PQntuples
          
 
          
 
                    Returns the number of rows (tuples)
           in the query result.
 
          
 
          int PQntuples(const PGresult *res);
          
 
          
-
          PQnfields
          
+
          PQnfields
          
 
          
 
                    Returns the number of columns (fields)
           in each row of the query result.
 
          
 
          int PQnfields(const PGresult *res);
          
 
          
-
          PQfname
          
+
          PQfname
          
 
          
 
          Returns the column name associated with the given column number.
 Column numbers start at 0. The caller should not free the result
@@ -501,7 +501,7 @@ 
          Tip
          
               int column_number);
    
 
    NULL is returned if the column number is out of range.
    
 
    
-
    PQfnumber
    
+
    PQfnumber
    
 
    
 
              Returns the column number associated with the given column name.
 
    
@@ -523,7 +523,7 @@ 
    Tip
    
 PQfnumber(res, "BAR")        -1
 PQfnumber(res, "\"BAR\"")    1
 
    
-
    PQftable
    
+
    PQftable
    
 
    
 
     Returns the OID of the table from which the given column was fetched.
  Column numbers start at 0.
@@ -540,7 +540,7 @@ 
    Tip
    
           the libpq header file. They will
           both be some integer type.
    
 
    
-
    PQftablecol
    
+
    PQftablecol
    
 
    
 
     Returns the column number (within its table) of the column making up
  the specified query result column.
@@ -553,7 +553,7 @@ 
    Tip
    
 or if the specified column is not a simple reference to a table column,
 or when using pre-3.0 protocol.
    
 
    
-
    PQfformat
    
+
    PQfformat
    
 
    
 
     Returns the format code indicating the format of the given column.
  Column numbers start at 0.
@@ -564,7 +564,7 @@ 
    Tip
    
 code one indicates binary representation.  (Other codes are reserved
 for future definition.)
    
 
    
-
    PQftype
    
+
    PQftype
    
 
    
 
              Returns the data type associated with the
           given  column number.  The  integer  returned is the
@@ -578,7 +578,7 @@ 
    Tip
    
 of the built-in data types are defined in the file src/include/catalog/pg_type.h
 in the source tree.
    
 
    
-
    PQfmod
    
+
    PQfmod
    
 
    
 
              Returns  the type modifier of the column
           associated with the given column number.
@@ -591,7 +591,7 @@ 
    Tip
    
 “no information available”.  Most data types do not use modifiers,
 in which case the value is always -1.
    
 
    
-
    PQfsize
    
+
    PQfsize
    
 
    
 
              Returns  the  size  in bytes of the column
           associated with the given column number.
@@ -604,7 +604,7 @@ 
    Tip
    
 of the data type.  (Accordingly, it is not really very useful to clients.)
 A negative value indicates the data type is variable-length.
    
 
    
-
    PQbinaryTuples
    
+
    PQbinaryTuples
    
 
    
 
    Returns 1 if the PGresult contains binary data
 and 0 if it contains text data.
@@ -617,7 +617,7 @@ 
    Tip
    
 PQfformat is preferred.  PQbinaryTuples
 returns 1 only if all columns of the result are binary (format 1).
    
 
    
-
    PQgetvalue
    
+
    PQgetvalue
    
 
    
 
                Returns a single field value of one row of a
             PGresult.  Row and column numbers
@@ -645,7 +645,7 @@ 
    Tip
    
 copy the data into other storage if it is to
 be used past the lifetime of the  PGresult  structure itself.
    
 
    
-
    PQgetisnull
    
+
    PQgetisnull
    
 
    
 
               Tests a field for a null value.
            Row and column numbers start at 0.
@@ -657,7 +657,7 @@ 
    Tip
    
 it contains a non-null value.  (Note that PQgetvalue
 will return an empty string, not a null pointer, for a null field.)
    
 
    
-
    PQgetlength
    
+
    PQgetlength
    
 
    
 
              Returns the actual length of a field value in bytes.
           Row and column numbers start at 0.
@@ -671,7 +671,7 @@ 
    Tip
    
 this is essential information.  Note that one should not rely
 on PQfsize to obtain the actual data length.
    
 
    
-
    PQnparams
    
+
    PQnparams
    
 
    
 
              Returns the number of parameters of a prepared statement.
 
    
@@ -680,7 +680,7 @@ 
    Tip
    
 PQdescribePrepared.  For other types of queries it will
 return zero.
    
 
    
-
    PQparamtype
    
+
    PQparamtype
    
 
    
 
              Returns the data type of the indicated statement parameter.
           Parameter numbers start at 0.
@@ -690,7 +690,7 @@ 
    Tip
    
 PQdescribePrepared.  For other types of queries it will
 return zero.
    
 
    
-
    PQprint
    
+
    PQprint
    
 
    
 
              Prints out all the rows and,  optionally,  the
           column names  to  the specified output stream.
@@ -724,7 +724,7 @@ 
    Tip
    
 PGresult objects that are not SELECT
 results.
    
 
    
-
    PQcmdStatus
    
+
    PQcmdStatus
    
 
    
 
              Returns the command status tag from the SQL command that
           generated the PGresult.
@@ -736,7 +736,7 @@ 
    Tip
    
 associated PGresult handle is passed to
 PQclear.
    
 
    
-
    PQcmdTuples
    
+
    PQcmdTuples
    
 
    
 
              Returns the number of rows affected by the SQL command.
 
    
@@ -757,9 +757,9 @@ 
    Tip
    
           PGresult handle is passed to
           PQclear.
    
 
    
-
    PQoidValue
    
+
    PQoidValue
    
 
    
-
              Returns the OID of the inserted row, if the SQL
+
              Returns the OID of the inserted row, if the SQL
           command was an INSERT that inserted exactly one
           row into a table that has OIDs, or a EXECUTE of
           a prepared query containing a suitable INSERT
@@ -770,7 +770,7 @@ 
    Tip
    
 
    
 
    Oid PQoidValue(const PGresult *res);
    
 
    
-
    PQoidStatus
    
+
    PQoidStatus
    
 
    
 
              Returns a string with the OID of the inserted row, if the
           SQL command was an
@@ -791,7 +791,7 @@ 
    Tip
    
 
    
 
    
 29.3.4. Escaping Strings for Inclusion in SQL Commands
    
-
    PQescapeStringConn escapes a string for use within an SQL
+
    PQescapeStringConn escapes a string for use within an SQL
 command.  This is useful when inserting data values as literal constants
 in SQL commands.  Certain characters (such as quotes and backslashes) must
 be escaped to prevent them from being interpreted specially by the SQL parser.
@@ -856,8 +856,8 @@ 
    Tip
    
 
    
 
    
 29.3.5. Escaping Binary Strings for Inclusion in SQL Commands
    
-
    
-
    PQescapeByteaConn
    
+
    
+
    PQescapeByteaConn
    
 
    
 
       Escapes binary data for use within an SQL command with the type
    bytea.  As with PQescapeStringConn,
@@ -903,7 +903,7 @@ 
    Tip
    
    possible error is insufficient memory for the result string.
   
    
 
    
-
    PQescapeBytea
    
+
    PQescapeBytea
    
 
    
 
       PQescapeBytea is an older, deprecated version of
    PQescapeByteaConn.
@@ -926,7 +926,7 @@ 
    Tip
    
    avoided in favor of PQescapeByteaConn.
   
    
 
    
-
    PQunescapeBytea
    
+
    PQunescapeBytea
    
 
    
 
       Converts a string representation of binary data into binary
    data — the reverse of PQescapeBytea.
@@ -951,7 +951,7 @@ 
    Tip
    
    and so no need for a PGconn parameter.
   
    
 
    
-
    PQfreemem
    
+
    PQfreemem
    
 
    
 
       Frees memory allocated by libpq.
 
    
diff --git a/docs/en_US/pg/libpq-fastpath.html b/docs/en_US/pg/libpq-fastpath.html
index c36cd62dc1..709ee0d6c3 100644
--- a/docs/en_US/pg/libpq-fastpath.html
+++ b/docs/en_US/pg/libpq-fastpath.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.6. The Fast-Path Interface
    
-
    PostgreSQL provides a fast-path interface to send
+
    PostgreSQL provides a fast-path interface to send
 simple function calls to the server.
    
 
    
 
    Tip
    
@@ -23,7 +23,7 @@ 
    Tip
    
 function call.  Then, executing the statement with binary transmission of
 parameters and results substitutes for a fast-path function call.
    
 
    
-
    The function PQfn
+
    The function PQfn
 requests execution of a server function via the fast-path interface:
 
    
 
    PGresult *PQfn(PGconn *conn,
diff --git a/docs/en_US/pg/libpq-ldap.html b/docs/en_US/pg/libpq-ldap.html
index 94281f4eff..ab837bc8aa 100644
--- a/docs/en_US/pg/libpq-ldap.html
+++ b/docs/en_US/pg/libpq-ldap.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.15. LDAP Lookup of Connection Parameters
    
-
    If libpq has been compiled with LDAP support (option
+
    If libpq has been compiled with LDAP support (option
 --with-ldap for configure)
 it is possible to retrieve connection options like host
 or dbname via LDAP from a central server.
diff --git a/docs/en_US/pg/libpq-misc.html b/docs/en_US/pg/libpq-misc.html
index 3428ea47c5..8786a6ac46 100644
--- a/docs/en_US/pg/libpq-misc.html
+++ b/docs/en_US/pg/libpq-misc.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -16,7 +16,7 @@
 29.10. Miscellaneous Functions
    
 
    As always, there are some functions that just don't fit anywhere.
    
 
    
-
    PQencryptPassword
    
+
    PQencryptPassword
    
 
    
 
    Prepares the encrypted form of a PostgreSQL password.
 
    
diff --git a/docs/en_US/pg/libpq-notice-processing.html b/docs/en_US/pg/libpq-notice-processing.html
index b7999661aa..05d96724a2 100644
--- a/docs/en_US/pg/libpq-notice-processing.html
+++ b/docs/en_US/pg/libpq-notice-processing.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.11. Notice Processing
    
-
    Notice and warning messages generated by the server are not returned by the
+
    Notice and warning messages generated by the server are not returned by the
 query execution functions, since they do not imply failure of the query.
 Instead they are passed to a notice handling function, and execution continues
 normally after the handler returns.  The default notice handling function
@@ -27,10 +27,10 @@
 receiver will typically ignore the notice processor layer and just do all the
 work in the notice receiver.
    
 
    The function PQsetNoticeReceiver
-
+
 sets or examines the current notice receiver for a connection object.
 Similarly, PQsetNoticeProcessor
-
+
 sets or examines the current notice processor.
 
 
    
diff --git a/docs/en_US/pg/libpq-notify.html b/docs/en_US/pg/libpq-notify.html
index 3b19fd9375..73f93cfed1 100644
--- a/docs/en_US/pg/libpq-notify.html
+++ b/docs/en_US/pg/libpq-notify.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.7. Asynchronous Notification
    
-
    PostgreSQL offers asynchronous notification via the
+
    PostgreSQL offers asynchronous notification via the
 LISTEN and NOTIFY commands.  A client session registers its interest in a particular
 notification condition with the LISTEN command (and can stop listening
 with the UNLISTEN command).  All sessions listening on a
@@ -28,7 +28,7 @@
 LISTEN and UNLISTEN commands as
 ordinary SQL commands.  The arrival of NOTIFY
 messages can subsequently be detected by calling
-PQnotifies.
    
+PQnotifies.
    
 
    The function PQnotifies
           returns  the next notification from a list of unhandled
           notification messages received from the server.  It returns a null pointer if
diff --git a/docs/en_US/pg/libpq-pgpass.html b/docs/en_US/pg/libpq-pgpass.html
index 318d2e3ae2..e9657128b1 100644
--- a/docs/en_US/pg/libpq-pgpass.html
+++ b/docs/en_US/pg/libpq-pgpass.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.13. The Password File
    
-
    The file .pgpass in a user's home directory or the
+
    The file .pgpass in a user's home directory or the
 file referenced by PGPASSFILE can contain passwords to
 be used if the connection requires a password (and no password has been
 specified  otherwise). On Microsoft Windows the file is named
diff --git a/docs/en_US/pg/libpq-pgservice.html b/docs/en_US/pg/libpq-pgservice.html
index 2c69584ca3..63029afcf1 100644
--- a/docs/en_US/pg/libpq-pgservice.html
+++ b/docs/en_US/pg/libpq-pgservice.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.14. The Connection Service File
    
-
    The connection service file allows libpq connection parameters to be
+
    The connection service file allows libpq connection parameters to be
 associated with a single service name. That service name can then be
 specified by a libpq connection, and the associated settings will be
 used. This allows connection parameters to be modified without requiring
diff --git a/docs/en_US/pg/libpq-ssl.html b/docs/en_US/pg/libpq-ssl.html
index 6be9d87e91..26a4d45030 100644
--- a/docs/en_US/pg/libpq-ssl.html
+++ b/docs/en_US/pg/libpq-ssl.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.16. SSL Support
    
-
       PostgreSQL has native support for using
+
       PostgreSQL has native support for using
    SSL connections to encrypt client/server communications
    for increased security. See Section 16.7, “Secure TCP/IP Connections with SSL” for details
    about the server-side SSL functionality.
diff --git a/docs/en_US/pg/libpq-status.html b/docs/en_US/pg/libpq-status.html
index d97f9c55bf..144b39b32b 100644
--- a/docs/en_US/pg/libpq-status.html
+++ b/docs/en_US/pg/libpq-status.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,8 +19,8 @@
   
    
 
    
 
    Tip
    
-
    
-
+
    
+
 libpq application programmers should be careful to
 maintain the PGconn abstraction.  Use the accessor
 functions described below to get at the contents of PGconn.
@@ -33,37 +33,37 @@ 
    Tip
    
 
 
    
 
    
-
    PQdb
    
+
    PQdb
    
 
    
 
             Returns the database name of the connection.
 
    
 
    char *PQdb(const PGconn *conn);
    
 
    
-
    PQuser
    
+
    PQuser
    
 
    
 
             Returns the user name of the connection.
 
    
 
    char *PQuser(const PGconn *conn);
    
 
    
-
    PQpass
    
+
    PQpass
    
 
    
 
             Returns the password of the connection.
 
    
 
    char *PQpass(const PGconn *conn);
    
 
    
-
    PQhost
    
+
    PQhost
    
 
    
 
             Returns the server host name of the connection.
 
    
 
    char *PQhost(const PGconn *conn);
    
 
    
-
    PQport
    
+
    PQport
    
 
    
 
             Returns the port of the connection.
 
    
 
    char *PQport(const PGconn *conn);
    
 
    
-
    PQtty
    
+
    PQtty
    
 
    
 
             Returns the debug TTY of the connection.
          (This is obsolete, since the server no longer pays attention
@@ -72,7 +72,7 @@ 
    Tip
    
 
    
 
    char *PQtty(const PGconn *conn);
    
 
    
-
    PQoptions
    
+
    PQoptions
    
 
    
 
           Returns the command-line options passed in the connection request.
 
    
@@ -84,7 +84,7 @@ 
    Tip
    
 
 
    
 
    
-
    PQstatus
    
+
    PQstatus
    
 
    
 
             Returns the status of the connection. 
 
    
@@ -110,7 +110,7 @@ 
    Tip
    
        that might be seen.
       
    
 
    
-
    PQtransactionStatus
    
+
    PQtransactionStatus
    
 
    
 
             Returns the current in-transaction status of the server.
 
    
@@ -132,7 +132,7 @@ 
    Caution
    
 deprecated and does not exist in later server versions.
    
 
    
 
    
-
    PQparameterStatus
    
+
    PQparameterStatus
    
 
    
 
             Looks up a current parameter setting of the server.
 
    
@@ -183,7 +183,7 @@ 
    Caution
    
 points to mutable storage associated with the PGconn structure.
 It is unwise to assume the pointer will remain valid across queries.
    
 
    
-
    PQprotocolVersion
    
+
    PQprotocolVersion
    
 
    
 
             Interrogates the frontend/backend protocol being used.
 
    
@@ -198,7 +198,7 @@ 
    Caution
    
 PostgreSQL 7.4 or later servers; pre-7.4 servers support
 only protocol 2.0.  (Protocol 1.0 is obsolete and not supported by libpq.)
    
 
    
-
    PQserverVersion
    
+
    PQserverVersion
    
 
    
 
             Returns an integer representing the backend version.
 
    
@@ -211,9 +211,9 @@ 
    Caution
    
 8.2 will be returned as 80200 (leading zeroes are not shown).  Zero is
 returned if the connection is bad.
    
 
    
-
    PQerrorMessage
    
+
    PQerrorMessage
    
 
    
-
           
+
           
        Returns the error message most recently generated by
        an operation on the connection.
 
    
@@ -231,7 +231,7 @@ 
    Caution
    
        PGconn structure.
       
    
 
    
-
    PQsocket
    
+
    PQsocket
    
 
    
 
           Obtains the file descriptor number of the connection socket to
        the server.  A valid descriptor will be greater than or equal
@@ -243,10 +243,10 @@ 
    Caution
    
 
    
       
    
 
    
-
    PQbackendPID
    
+
    PQbackendPID
    
 
    
 
           Returns the process ID
-       (PID) of the backend server
+       (PID) of the backend server
        process handling this connection.
 
    
 
    int PQbackendPID(const PGconn *conn);
    
@@ -258,9 +258,9 @@ 
    Caution
    
        database server host, not the local host!
       
    
 
    
-
    PQgetssl
    
+
    PQgetssl
    
 
    
-
           
+
           
        Returns the SSL structure used in the connection, or null
        if SSL is not in use. 
 
    
diff --git a/docs/en_US/pg/libpq-threading.html b/docs/en_US/pg/libpq-threading.html
index 9e5379e747..9163c86133 100644
--- a/docs/en_US/pg/libpq-threading.html
+++ b/docs/en_US/pg/libpq-threading.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 29.17. Behavior in Threaded Programs
    
-
    libpq is reentrant and thread-safe if the
+
    libpq is reentrant and thread-safe if the
 configure command-line option
 --enable-thread-safety was used when the
 PostgreSQL distribution was built.  In
@@ -26,7 +26,7 @@
 and PTHREAD_LIBS.  This function allows the querying of
 libpq's thread-safe status:
    
 
    
-
    PQisthreadsafe
    
+
    PQisthreadsafe
    
 
    
 
           Returns the thread safety status of the libpq
        library.
diff --git a/docs/en_US/pg/libpq.html b/docs/en_US/pg/libpq.html
index e0526d8698..b771610604 100644
--- a/docs/en_US/pg/libpq.html
+++ b/docs/en_US/pg/libpq.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -50,7 +50,7 @@
 
    29.19. Example Programs
    
 
    
 
    
-
       libpq is the C
+
       libpq is the C
    application programmer's interface to PostgreSQL.
    libpq is a set of library functions that allow
    client programs to pass queries to the PostgreSQL
@@ -74,7 +74,7 @@
   
    
 
       Client programs that use libpq must
    include the header file
-   libpq-fe.h
+   libpq-fe.h
    and must link with the libpq library.
   
    
 
    
@@ -85,7 +85,7 @@
    application program can have several backend connections open at
    one time.  (One reason to do that is to access more than one
    database.)  Each connection is represented by a
-   PGconn object, which
+   PGconn object, which
    is obtained from the function PQconnectdb or
    PQsetdbLogin.  Note that these functions will always
    return a non-null object pointer, unless perhaps there is too
@@ -96,7 +96,7 @@
 
    
    
 
    
-
    PQconnectdb
    
+
    PQconnectdb
    
 
    
 
           Makes a new connection to the database server.
 
    
@@ -123,13 +123,13 @@
    
    
 
    
 
    host
    
-
          Name of host to connect to.
+
          Name of host to connect to.
       If this begins with a slash, it specifies Unix-domain
       communication rather than TCP/IP communication; the value is the
       name of the directory in which the socket file is stored.  The
       default behavior when host is not specified
       is to connect to a Unix-domain
-      socket in
+      socket in
       /tmp (or whatever socket directory was specified
       when PostgreSQL was built). On machines without
       Unix-domain sockets, the default is to connect to localhost.
@@ -170,7 +170,7 @@
 
    port
    
 
          Port number to connect to at the server host, or socket file
       name extension for Unix-domain
-      connections.
+      connections.
      
    
 
    dbname
    
 
          The database name.  Defaults to be the same as the user name.
@@ -213,7 +213,7 @@
        options allow and prefer will be
        accepted but libpq will not in fact attempt
        an SSL
-       connection.
+       connection.
       
    
 
    
 
    requiressl
    
@@ -253,7 +253,7 @@
    then the indicated built-in defaults are used.
    
    
 
    
-
    PQsetdbLogin
    
+
    PQsetdbLogin
    
 
    
 
           Makes a new connection to the database server.
 
    
@@ -270,7 +270,7 @@
    empty string for any one of the fixed parameters that is to be defaulted.
    
    
 
    
-
    PQsetdb
    
+
    PQsetdb
    
 
    
 
       Makes a new connection to the database server.
 
    
@@ -285,10 +285,10 @@
    
    
 
    
 
    
-PQconnectStart

    PQconnectPoll
+PQconnectStart

    PQconnectPoll
 
    
 
    
-
       
+
       
    Make a connection to the database server in a nonblocking manner.
 
    
 
    PGconn *PQconnectStart(const char *conninfo);
    
@@ -419,7 +419,7 @@
    the connection attempt fails or is abandoned.
   
    
 
    
-
    PQconndefaults
    
+
    PQconndefaults
    
 
    
 
       Returns the default connection options.
 
    
@@ -454,7 +454,7 @@
     is leaked for each call to PQconndefaults.
    
    
 
    
-
    PQfinish
    
+
    PQfinish
    
 
    
 
       Closes  the  connection to the server.  Also frees
    memory used by the PGconn object.
@@ -467,7 +467,7 @@
    PQfinish has been called.
    
    
 
    
-
    PQreset
    
+
    PQreset
    
 
    
 
       Resets the communication channel to the server.
 
    
@@ -480,7 +480,7 @@
    
    
 
    
 
    
-PQresetStart

    PQresetPoll
+PQresetStart

    PQresetPoll
 
    
 
    
 
       Reset the communication channel to the server, in a nonblocking manner.
diff --git a/docs/en_US/pg/lo-examplesect.html b/docs/en_US/pg/lo-examplesect.html
index 265719c28f..d060caec9a 100644
--- a/docs/en_US/pg/lo-examplesect.html
+++ b/docs/en_US/pg/lo-examplesect.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/lo-funcs.html b/docs/en_US/pg/lo-funcs.html
index 28c7330483..29e08cc10d 100644
--- a/docs/en_US/pg/lo-funcs.html
+++ b/docs/en_US/pg/lo-funcs.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,11 +19,11 @@
    most part the client-side functions are simply interfaces to the
    equivalent server-side functions.  The ones that are actually useful
    to call via SQL commands are
-   lo_creat,
-   lo_create,
-   lo_unlink,
-   lo_import, and
-   lo_export.
+   lo_creat,
+   lo_create,
+   lo_unlink,
+   lo_import, and
+   lo_export.
    Here are examples of their use:
 
 
    
diff --git a/docs/en_US/pg/lo-implementation.html b/docs/en_US/pg/lo-implementation.html
index 466d548689..10b21e6cda 100644
--- a/docs/en_US/pg/lo-implementation.html
+++ b/docs/en_US/pg/lo-implementation.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/lo-interfaces.html b/docs/en_US/pg/lo-interfaces.html
index 8d75790b90..3a3021f0cd 100644
--- a/docs/en_US/pg/lo-interfaces.html
+++ b/docs/en_US/pg/lo-interfaces.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -32,12 +32,12 @@
    
    
 
    
 
    
-30.3.1. Creating a Large Object
    
+30.3.1. Creating a Large Object
    
 
         The function
 
    
 
    Oid lo_creat(PGconn *conn, int mode);
    
 
    
-     
+     
      creates a new large object.  
      The return value is the OID that was assigned to the new large object,
      or InvalidOid (zero) on failure.
@@ -59,7 +59,7 @@
 
    
 
    Oid lo_create(PGconn *conn, Oid lobjId);
    
 
    
-     
+     
      also creates a new large object.  The OID to be assigned can be
      specified by lobjId;
      if so, failure occurs if that OID is already in use for some large
@@ -81,12 +81,12 @@
 
    
 
    
 
    
-30.3.2. Importing a Large Object
    
+30.3.2. Importing a Large Object
    
 
         To import an operating system file as a large object, call
 
    
 
    Oid lo_import(PGconn *conn, const char *filename);
    
 
    
-     
+     
      filename 
      specifies the operating system name of
      the file to be imported as a large object.
@@ -99,13 +99,13 @@
 
    
 
    
 
    
-30.3.3. Exporting a Large Object
    
+30.3.3. Exporting a Large Object
    
 
         To export a large object
      into an operating system file, call
 
    
 
    int lo_export(PGconn *conn, Oid lobjId, const char *filename);
    
 
    
-     
+     
      The lobjId argument specifies the OID of the large
      object to export and the filename argument
      specifies the operating system name of the file.  Note that the file is
@@ -115,12 +115,12 @@
 
    
 
    
 
    
-30.3.4. Opening an Existing Large Object
    
+30.3.4. Opening an Existing Large Object
    
 
         To open an existing large object for reading or writing, call
 
    
 
    int lo_open(PGconn *conn, Oid lobjId, int mode);
    
 
    
-     
+     
      The lobjId argument specifies the OID of the large
      object to open.   The mode bits control whether the
      object is opened for reading (INV_READ), writing
@@ -159,12 +159,12 @@
 
    
 
    
 
    
-30.3.5. Writing Data to a Large Object
    
+30.3.5. Writing Data to a Large Object
    
 
         The function
 
    
 
    int lo_write(PGconn *conn, int fd, const char *buf, size_t len);
    
 
    
-      writes
+      writes
      len bytes from buf
      to large object descriptor fd.  The fd
      argument must have been returned by a previous
@@ -174,12 +174,12 @@
 
    
 
    
 
    
-30.3.6. Reading Data from a Large Object
    
+30.3.6. Reading Data from a Large Object
    
 
         The function
 
    
 
    int lo_read(PGconn *conn, int fd, char *buf, size_t len);
    
 
    
-      reads
+      reads
      len bytes from large object descriptor
      fd into buf. The
      fd argument must have been returned by a
@@ -189,13 +189,13 @@
 
    
 
    
 
    
-30.3.7. Seeking in a Large Object
    
+30.3.7. Seeking in a Large Object
    
 
         To change the current read or write location associated with a
      large object descriptor, call
 
    
 
    int lo_lseek(PGconn *conn, int fd, int offset, int whence);
    
 
    
-      This function moves the
+      This function moves the
      current location pointer for the large object descriptor identified by
      fd to the new location specified by
      offset.  The valid values for whence
@@ -206,23 +206,23 @@
 
 
    
 
    
-30.3.8. Obtaining the Seek Position of a Large Object
    
+30.3.8. Obtaining the Seek Position of a Large Object
    
 
         To obtain the current read or write location of a large object descriptor,
      call
 
    
 
    int lo_tell(PGconn *conn, int fd);
    
 
    
-      If there is an error, the
+      If there is an error, the
      return value is negative.
    
 
 
    
 
    
-30.3.9. Closing a Large Object Descriptor
    
+30.3.9. Closing a Large Object Descriptor
    
 
         A large object descriptor may be closed by calling
 
    
 
    int lo_close(PGconn *conn, int fd);
    
 
    
-      where fd is a
+      where fd is a
      large object descriptor returned by lo_open.
      On success, lo_close returns zero.  On
      error, the return value is negative.
    
@@ -231,12 +231,12 @@
 
 
    
 
    
-30.3.10. Removing a Large Object
    
+30.3.10. Removing a Large Object
    
 
         To remove a large object from the database, call
 
    
 
    int lo_unlink(PGconn *conn, Oid lobjId);
    
 
    
-      The
+      The
      lobjId argument specifies the OID of the
      large object to remove.  Returns 1 if successful, -1 on failure.
     
    
diff --git a/docs/en_US/pg/locking-indexes.html b/docs/en_US/pg/locking-indexes.html
index cb2e3f50ef..9c4f611310 100644
--- a/docs/en_US/pg/locking-indexes.html
+++ b/docs/en_US/pg/locking-indexes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 12.5. Locking and Indexes
    
-
        Though PostgreSQL
+
        Though PostgreSQL
     provides nonblocking read/write access to table
     data, nonblocking read/write access is not currently offered for every
     index access method implemented
diff --git a/docs/en_US/pg/logfile-maintenance.html b/docs/en_US/pg/logfile-maintenance.html
index 6b67904561..28ad34adbe 100644
--- a/docs/en_US/pg/logfile-maintenance.html
+++ b/docs/en_US/pg/logfile-maintenance.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 22.3. Log File Maintenance
    
-
       It is a good idea to save the database server's log output
+
       It is a good idea to save the database server's log output
    somewhere, rather than just routing it to /dev/null.
    The log output is invaluable when it comes time to diagnose
    problems.  However, the log output tends to be voluminous
diff --git a/docs/en_US/pg/maintenance.html b/docs/en_US/pg/maintenance.html
index 6cc1087c68..6930db7da6 100644
--- a/docs/en_US/pg/maintenance.html
+++ b/docs/en_US/pg/maintenance.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -28,7 +28,7 @@
 
    22.3. Log File Maintenance
    
 
 
    
-
       PostgreSQL, like any database software, requires that certain tasks
+
       PostgreSQL, like any database software, requires that certain tasks
    be performed regularly to achieve optimum performance. The tasks
    discussed here are required, but they
    are repetitive in nature and can easily be automated using standard
@@ -61,7 +61,7 @@
 
    
 
    
 22.1. Routine Vacuuming
    
-
       PostgreSQL's VACUUM command
+
       PostgreSQL's VACUUM command
    must be run on a regular basis for several reasons:
 
     
    
@@ -103,7 +103,7 @@
 
    
 
    
 22.1.1. Recovering disk space
    
-
        In normal PostgreSQL operation, an
+
        In normal PostgreSQL operation, an
     UPDATE or DELETE of a row does not
     immediately remove the old version of the row.
     This approach is necessary to gain the benefits of multiversion
@@ -183,7 +183,7 @@
 
    
 
    
 22.1.2. Updating planner statistics
    
-
        The PostgreSQL query planner relies on
+
        The PostgreSQL query planner relies on
     statistical information about the contents of tables in order to
     generate good plans for queries.  These statistics are gathered by
     the ANALYZE command, which can be invoked by itself or
@@ -234,7 +234,7 @@ 
    Tip
    
 
    
 
    
 22.1.3. Preventing transaction ID wraparound failures
    
-
        PostgreSQL's MVCC transaction semantics
+
        PostgreSQL's MVCC transaction semantics
     depend on being able to compare transaction ID (XID)
     numbers: a row version with an insertion XID greater than the current
     transaction's XID is “in the future” and should not be visible
@@ -391,7 +391,7 @@ 
    Tip
    
 
    
 
    
 22.1.4. The auto-vacuum daemon
    
-
        Beginning in PostgreSQL  8.1, there is a
+
        Beginning in PostgreSQL  8.1, there is a
     separate optional server process called the autovacuum
     daemon, whose purpose is to automate the execution of
     VACUUM and ANALYZE  commands.
diff --git a/docs/en_US/pg/manage-ag-config.html b/docs/en_US/pg/manage-ag-config.html
index 9aa3403786..5d9b2ddcf8 100644
--- a/docs/en_US/pg/manage-ag-config.html
+++ b/docs/en_US/pg/manage-ag-config.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/manage-ag-createdb.html b/docs/en_US/pg/manage-ag-createdb.html
index 9c6ceabd40..faa6f65f00 100644
--- a/docs/en_US/pg/manage-ag-createdb.html
+++ b/docs/en_US/pg/manage-ag-createdb.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,7 +18,7 @@
    server must be up and running (see Section 16.3, “Starting the Database Server”).
   
    
 
       Databases are created with the SQL command
-   CREATE DATABASE:
+   CREATE DATABASE:
 
    
 
    CREATE DATABASE name;
    
 
    
@@ -37,12 +37,12 @@
    initdb command when the data storage area is
    initialized. (See Section 16.2, “Creating a Database Cluster”.)  This
    database is called
-   postgres. So to
+   postgres. So to
    create the first “ordinary” database you can connect to
    postgres.
   
    
 
       A second database,
-   template1,
+   template1,
    is also created by
    initdb.  Whenever a new database is created within the
    cluster, template1 is essentially cloned.
@@ -54,7 +54,7 @@
   
    
 
       As a convenience, there is a program that you can
    execute from the shell to create new databases,
-   createdb.
+   createdb.
 
 
    
 
    createdb dbname
    
diff --git a/docs/en_US/pg/manage-ag-dropdb.html b/docs/en_US/pg/manage-ag-dropdb.html
index e7d5cf7ffb..1f8745e965 100644
--- a/docs/en_US/pg/manage-ag-dropdb.html
+++ b/docs/en_US/pg/manage-ag-dropdb.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -15,7 +15,7 @@
 
    
 19.5. Destroying a Database
    
 
       Databases are destroyed with the command 
-   DROP DATABASE:
+   DROP DATABASE:
 
    
 
    DROP DATABASE name;
    
 
    
@@ -33,7 +33,7 @@
    given cluster.
   
    
 
       For convenience, there is also a shell program to drop
-   databases, dropdb:
+   databases, dropdb:
 
    
 
    dropdb dbname
    
 
    
diff --git a/docs/en_US/pg/manage-ag-tablespaces.html b/docs/en_US/pg/manage-ag-tablespaces.html
index fd45685c21..4ce0a447e6 100644
--- a/docs/en_US/pg/manage-ag-tablespaces.html
+++ b/docs/en_US/pg/manage-ag-tablespaces.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 19.6. Tablespaces
    
-
        Tablespaces in PostgreSQL allow database administrators to
+
        Tablespaces in PostgreSQL allow database administrators to
     define locations in the file system where the files representing
     database objects can be stored. Once created, a tablespace can be referred
     to by name when creating database objects.
@@ -35,7 +35,7 @@
     expensive, slower disk system.
    
    
 
        To define a tablespace, use the CREATE TABLESPACE
-    command, for example:
+    command, for example:
 
    
 
    CREATE TABLESPACE fastspace LOCATION '/mnt/sda1/postgresql/data';
    
 
    
diff --git a/docs/en_US/pg/manage-ag-templatedbs.html b/docs/en_US/pg/manage-ag-templatedbs.html
index ef26eb37f0..9f3a6a7fd2 100644
--- a/docs/en_US/pg/manage-ag-templatedbs.html
+++ b/docs/en_US/pg/manage-ag-templatedbs.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -16,7 +16,7 @@
 19.3. Template Databases
    
 
       CREATE DATABASE actually works by copying an existing
    database.  By default, it copies the standard system database named
-   template1. Thus that
+   template1. Thus that
    database is the “template” from which new databases are
    made.  If you add objects to template1, these objects
    will be copied into subsequently created user databases.  This
@@ -27,7 +27,7 @@
    action being taken when those databases are made.
   
    
 
       There is a second standard system database named
-   template0. This
+   template0. This
    database contains the same data as the initial contents of
    template1, that is, only the standard objects
    predefined by your version of
@@ -63,7 +63,7 @@
    otherwise, new connections to the source database are locked out
    until CREATE DATABASE completes.
   
    
-
       Two useful flags exist in pg_database for each
+
       Two useful flags exist in pg_database for each
    database: the columns datistemplate and
    datallowconn.  datistemplate
    may be set to indicate that a database is intended as a template for
diff --git a/docs/en_US/pg/managing-databases.html b/docs/en_US/pg/managing-databases.html
index c7e9a87660..749e4b057e 100644
--- a/docs/en_US/pg/managing-databases.html
+++ b/docs/en_US/pg/managing-databases.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -25,7 +25,7 @@
 
    19.6. Tablespaces
    
 
 
    
-
      Every instance of a running PostgreSQL
+
      Every instance of a running PostgreSQL
   server manages one or more databases.  Databases are therefore the
   topmost hierarchical level for organizing SQL
   objects (“database objects”).  This chapter describes
@@ -35,7 +35,7 @@
 
    
 
    
 19.1. Overview
    
-
       A database is a named collection of SQL objects
+
       A database is a named collection of SQL objects
    (“database objects”).  Generally, every database
    object (tables, functions, etc.) belongs to one and only one
    database.  (But there are a few system catalogs, for example
diff --git a/docs/en_US/pg/migration.html b/docs/en_US/pg/migration.html
index f353da3498..cc069823a9 100644
--- a/docs/en_US/pg/migration.html
+++ b/docs/en_US/pg/migration.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 23.5. Migration Between Releases
    
-
       This section discusses how to migrate your database data from one
+
       This section discusses how to migrate your database data from one
    PostgreSQL release to a newer one.
    The software installation procedure per se is not the
    subject of this section; those details are in Chapter 14,   Installation Instructions.
@@ -70,7 +70,7 @@
 
    pg_dumpall > backup
 pg_ctl stop
 mv /usr/local/pgsql /usr/local/pgsql.old
-cd ~/postgresql-8.2.0
+cd ~/postgresql-8.2.1
 gmake install
 initdb -D /usr/local/pgsql/data
 postgres -D /usr/local/pgsql/data
diff --git a/docs/en_US/pg/monitoring-locks.html b/docs/en_US/pg/monitoring-locks.html
index 1de09c9630..c99d8ad99b 100644
--- a/docs/en_US/pg/monitoring-locks.html
+++ b/docs/en_US/pg/monitoring-locks.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 25.3. Viewing Locks
    
-
       Another useful tool for monitoring database activity is the
+
       Another useful tool for monitoring database activity is the
    pg_locks system table.  It allows the
    database administrator to view information about the outstanding
    locks in the lock manager. For example, this capability can be used
diff --git a/docs/en_US/pg/monitoring-stats.html b/docs/en_US/pg/monitoring-stats.html
index 0582c9fcf6..48ecae3839 100644
--- a/docs/en_US/pg/monitoring-stats.html
+++ b/docs/en_US/pg/monitoring-stats.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 25.2. The Statistics Collector
    
-
       PostgreSQL's statistics collector
+
       PostgreSQL's statistics collector
    is a subsystem that supports collection and reporting of information about
    server activity.  Presently, the collector can count accesses to tables
    and indexes in both disk-block and individual-row terms.
diff --git a/docs/en_US/pg/monitoring.html b/docs/en_US/pg/monitoring.html
index 0f07d229c7..65b133330c 100644
--- a/docs/en_US/pg/monitoring.html
+++ b/docs/en_US/pg/monitoring.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -26,14 +26,14 @@
 
    25.3. Viewing Locks
    
 
    25.4. Dynamic Tracing
    
 
    
-
    25.4.1. Compiling for Dynamic Trace
    
+
    25.4.1. Compiling for Dynamic Tracing
    
 
    25.4.2. Built-in Trace Points
    
 
    25.4.3. Using Trace Points
    
 
    25.4.4. Defining Trace Points
    
 
    
 
 
    
-
      A database administrator frequently wonders, “What is the system
+
      A database administrator frequently wonders, “What is the system
   doing right now?”
   This chapter discusses how to find that out.
  
    
@@ -52,7 +52,7 @@
 
    
 
    
 25.1. Standard Unix Tools
    
-
       On most platforms, PostgreSQL modifies its
+
       On most platforms, PostgreSQL modifies its
    command title as reported by ps, so that individual server
    processes can readily be identified.  A sample display is
 
diff --git a/docs/en_US/pg/multibyte.html b/docs/en_US/pg/multibyte.html
index d0450dbc97..0d1fc3ee4e 100644
--- a/docs/en_US/pg/multibyte.html
+++ b/docs/en_US/pg/multibyte.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 21.2. Character Set Support
    
-
       The character set support in PostgreSQL
+
       The character set support in PostgreSQL
    allows you to store text in a variety of character sets, including
    single-byte character sets such as the ISO 8859 series and
    multiple-byte character sets such as EUC (Extended Unix
@@ -400,7 +400,7 @@
 
    
 
    
 
    
-21.2.2. Setting the Character Set
    
+21.2.2. Setting the Character Set
    
 
         initdb defines the default character set
      for a PostgreSQL cluster. For example,
 
@@ -476,7 +476,7 @@ 
    Important
    
 
    
 
    
 
    
-21.2.3. Automatic Character Set Conversion Between Server and Client
    
+21.2.3. Automatic Character Set Conversion Between Server and Client
    
 
         PostgreSQL supports automatic
      character set conversion between server and client for certain
      character set combinations. The conversion information is stored in the
@@ -911,7 +911,7 @@ 
    Important
    
 
    
 
    
 
    
-21.2.4. Further Reading
    
+21.2.4. Further Reading
    
 
         These are good sources to start learning about various kinds of encoding
      systems.
 
diff --git a/docs/en_US/pg/mvcc.html b/docs/en_US/pg/mvcc.html
index 2283247458..97d199fec8 100644
--- a/docs/en_US/pg/mvcc.html
+++ b/docs/en_US/pg/mvcc.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -34,7 +34,7 @@
 
    12.5. Locking and Indexes
    
 
 
-
       This chapter describes the behavior of the
+
       This chapter describes the behavior of the
    PostgreSQL database system when two or
    more sessions try to access the same data at the same time.  The
    goals in that situation are to allow efficient access for all
@@ -45,7 +45,7 @@
 
    
 
    
 12.1. Introduction
    
-
        PostgreSQL provides a rich set of tools 
+
        PostgreSQL provides a rich set of tools 
     for developers to manage concurrent access to data.  Internally,
     data consistency is maintained by using a multiversion 
     model (Multiversion Concurrency Control, MVCC). 
diff --git a/docs/en_US/pg/nls-programmer.html b/docs/en_US/pg/nls-programmer.html
index 046ee1eb1d..709e3d285f 100644
--- a/docs/en_US/pg/nls-programmer.html
+++ b/docs/en_US/pg/nls-programmer.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -23,7 +23,7 @@
    Currently, it only applies to C programs.
   
    
 
    
-
    Adding NLS support to a program
    
+
    Adding NLS support to a program
    
 
      
 
    1. 
 
           Insert this code into the start-up sequence of the program:
diff --git a/docs/en_US/pg/nls.html b/docs/en_US/pg/nls.html
index 7012090f35..af195ad273 100644
--- a/docs/en_US/pg/nls.html
+++ b/docs/en_US/pg/nls.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,10 +24,10 @@
 
      
 
      46.1. For the Translator
      
 
      
-
      46.1.1. Requirements
      
-
      46.1.2. Concepts
      
-
      46.1.3. Creating and maintaining message catalogs
      
-
      46.1.4. Editing the PO files
      
+
      46.1.1. Requirements
      
+
      46.1.2. Concepts
      
+
      46.1.3. Creating and maintaining message catalogs
      
+
      46.1.4. Editing the PO files
      
 
      
 
      46.2. For the Programmer
      
 
      
@@ -50,7 +50,7 @@
   
      
 
      
 
      
-46.1.1. Requirements
      
+46.1.1. Requirements
    
 
        We won't judge your language skills — this section is about
     software tools.  Theoretically, you only need a text editor.  But
     this is only in the unlikely event that you do not want to try out
@@ -77,7 +77,7 @@
 
 
    
 
    
-46.1.2. Concepts
    
+46.1.2. Concepts
    
 
        The pairs of original (English) messages and their (possibly)
     translated equivalents are kept in message
     catalogs, one for each program (although related
@@ -149,7 +149,7 @@
 
 
    
 
    
-46.1.3. Creating and maintaining message catalogs
    
+46.1.3. Creating and maintaining message catalogs
    
 
        OK, so how does one create a “blank” message
     catalog?  First, go into the directory that contains the program
     whose messages you want to translate.  If there is a file
@@ -208,7 +208,7 @@
 
 
    
 
    
-46.1.4. Editing the PO files
    
+46.1.4. Editing the PO files
    
 
        The PO files can be edited with a regular text editor.  The
     translator should only change the area between the quotes after
     the msgstr directive, may add comments and alter the fuzzy flag.
diff --git a/docs/en_US/pg/notation.html b/docs/en_US/pg/notation.html
index d1b41999b6..58d295c680 100644
--- a/docs/en_US/pg/notation.html
+++ b/docs/en_US/pg/notation.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/overview.html b/docs/en_US/pg/overview.html
index beb3af4597..102ccdaef3 100644
--- a/docs/en_US/pg/overview.html
+++ b/docs/en_US/pg/overview.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,12 +21,12 @@
 
    42.2. How Connections are Established
    
 
    42.3. The Parser Stage
    
 
    
-
    42.3.1. Parser
    
-
    42.3.2. Transformation Process
    
+
    42.3.1. Parser
    
+
    42.3.2. Transformation Process
    
 
    
 
    42.4. The PostgreSQL Rule System
    
 
    42.5. Planner/Optimizer
    
-
    42.5.1. Generating Possible Plans
    
+
    42.5.1. Generating Possible Plans
    
 
    42.6. Executor
    
 
 
diff --git a/docs/en_US/pg/parser-stage.html b/docs/en_US/pg/parser-stage.html
index 1cc97139b0..e3b386059a 100644
--- a/docs/en_US/pg/parser-stage.html
+++ b/docs/en_US/pg/parser-stage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -31,7 +31,7 @@
    
    
 
    
 
    
-42.3.1. Parser
    
+42.3.1. Parser
    
 
         The parser has to check the query string (which arrives as plain
      ASCII text) for valid syntax. If the syntax is correct a
      parse tree is built up and handed back;
@@ -85,7 +85,7 @@ 
    Note
    
 
 
    
 
    
-42.3.2. Transformation Process
    
+42.3.2. Transformation Process
    
 
         The parser stage creates a parse tree using only fixed rules about
      the syntactic structure of SQL.  It does not make any lookups in the
      system catalogs, so there is no possibility to understand the detailed
diff --git a/docs/en_US/pg/performance-tips.html b/docs/en_US/pg/performance-tips.html
index 8be8285ee7..d48432089f 100644
--- a/docs/en_US/pg/performance-tips.html
+++ b/docs/en_US/pg/performance-tips.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -33,7 +33,7 @@
 
 
 
-
       Query performance can be affected by many things. Some of these can 
+
       Query performance can be affected by many things. Some of these can 
    be manipulated by the user, while others are fundamental to the underlying
    design of the system.  This chapter provides some hints about understanding
    and tuning PostgreSQL performance.
@@ -41,7 +41,7 @@
 
    
 
    
 13.1. Using EXPLAIN
    
-
        PostgreSQL devises a query
+
        PostgreSQL devises a query
     plan for each query it is given.  Choosing the right
     plan to match the query structure and the properties of the data
     is absolutely critical for good performance, so the system includes
@@ -68,7 +68,7 @@
     that the planner seeks to minimize.
    
    
 
        Here is a trivial example, just to show what the output looks like.
-    [7]
+    [7]
 
 
    
 
    EXPLAIN SELECT * FROM tenk1;
@@ -400,7 +400,7 @@
 
    
 
    
 
    
-
    [7]       Examples in this section are drawn from the regression test database
+
    [7]       Examples in this section are drawn from the regression test database
       after doing a VACUUM ANALYZE, using 8.2 development sources.
       You should be able to get similar results if you try the examples yourself,
       but your estimated costs and row counts will probably vary slightly
diff --git a/docs/en_US/pg/perm-functions.html b/docs/en_US/pg/perm-functions.html
index 61d5689d51..888ba091f1 100644
--- a/docs/en_US/pg/perm-functions.html
+++ b/docs/en_US/pg/perm-functions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/planner-optimizer.html b/docs/en_US/pg/planner-optimizer.html
index 16e1f27657..251eabad79 100644
--- a/docs/en_US/pg/planner-optimizer.html
+++ b/docs/en_US/pg/planner-optimizer.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -43,7 +43,7 @@ 
    Note
    
    
    
 
    
 
    
-42.5.1. Generating Possible Plans
    
+42.5.1. Generating Possible Plans
    
 
         The planner/optimizer starts by generating plans for scanning each
      individual relation (table) used in the query.  The possible plans
      are determined by the available indexes on each relation.
diff --git a/docs/en_US/pg/planner-stats-details.html b/docs/en_US/pg/planner-stats-details.html
index ba0e78badf..8db36ab45d 100644
--- a/docs/en_US/pg/planner-stats-details.html
+++ b/docs/en_US/pg/planner-stats-details.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -36,7 +36,7 @@
 
    
 
    
 54.1. Row Estimation Examples
    
-
       Using examples drawn from the regression test database, let's start with a 
+
       Using examples drawn from the regression test database, let's start with a 
    very simple query:
 
    
 
    EXPLAIN SELECT * FROM tenk1;
diff --git a/docs/en_US/pg/planner-stats.html b/docs/en_US/pg/planner-stats.html
index e652cffb37..d97550e7c5 100644
--- a/docs/en_US/pg/planner-stats.html
+++ b/docs/en_US/pg/planner-stats.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 13.2. Statistics Used by the Planner
    
-
       As we saw in the previous section, the query planner needs to estimate
+
       As we saw in the previous section, the query planner needs to estimate
    the number of rows retrieved by a query in order to make good choices
    of query plans.  This section provides a quick look at the statistics
    that the system uses for these estimates.
@@ -56,7 +56,7 @@
    to match the current physical table size, thus obtaining a closer
    approximation.
   
    
-
       Most queries retrieve only a fraction of the rows in a table, due
+
       Most queries retrieve only a fraction of the rows in a table, due
    to having WHERE clauses that restrict the rows to be
    examined.  The planner thus needs to make an estimate of the
    selectivity of WHERE clauses, that is,
@@ -68,7 +68,7 @@
    ANALYZE commands, and are always approximate even when freshly
    updated.
   
    
-
       Rather than look at pg_statistic directly,
+
       Rather than look at pg_statistic directly,
    it's better to look at its view pg_stats
    when examining the statistics manually.  pg_stats
    is designed to be more easily readable.  Furthermore,
diff --git a/docs/en_US/pg/plhandler.html b/docs/en_US/pg/plhandler.html
index 9f746be8fa..4ca9bd9c23 100644
--- a/docs/en_US/pg/plhandler.html
+++ b/docs/en_US/pg/plhandler.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 Chapter 47. Writing A Procedural Language Handler
    
-
        All calls to functions that are written in a language other than
+
        All calls to functions that are written in a language other than
     the current “version 1” interface for compiled
     languages (this includes functions in user-defined procedural languages,
     functions written in SQL, and functions using the version 0 compiled
diff --git a/docs/en_US/pg/plperl-data.html b/docs/en_US/pg/plperl-data.html
index 084e7d531d..4fa0975f64 100644
--- a/docs/en_US/pg/plperl-data.html
+++ b/docs/en_US/pg/plperl-data.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plperl-database.html b/docs/en_US/pg/plperl-database.html
index 343885afbc..fead4b0d19 100644
--- a/docs/en_US/pg/plperl-database.html
+++ b/docs/en_US/pg/plperl-database.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -22,7 +22,7 @@
    DBI-compliant database-handle named
    $pg_dbh that can be used to perform queries with
    normal DBI
-   syntax.
+   syntax.
   
    
 
       PL/Perl provides additional Perl commands:
 
diff --git a/docs/en_US/pg/plperl-global.html b/docs/en_US/pg/plperl-global.html
index 21196af41e..f73160dcbb 100644
--- a/docs/en_US/pg/plperl-global.html
+++ b/docs/en_US/pg/plperl-global.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plperl-missing.html b/docs/en_US/pg/plperl-missing.html
index 097115e270..e210f38663 100644
--- a/docs/en_US/pg/plperl-missing.html
+++ b/docs/en_US/pg/plperl-missing.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plperl-triggers.html b/docs/en_US/pg/plperl-triggers.html
index 6aff7599ab..8d1d02afd5 100644
--- a/docs/en_US/pg/plperl-triggers.html
+++ b/docs/en_US/pg/plperl-triggers.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plperl-trusted.html b/docs/en_US/pg/plperl-trusted.html
index a84afaedad..783db1cbc6 100644
--- a/docs/en_US/pg/plperl-trusted.html
+++ b/docs/en_US/pg/plperl-trusted.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 39.5. Trusted and Untrusted PL/Perl
    
-
       Normally, PL/Perl is installed as a “trusted” programming
+
       Normally, PL/Perl is installed as a “trusted” programming
    language named plperl.  In this setup, certain Perl
    operations are disabled to preserve security.  In general, the
    operations that are restricted are those that interact with the
@@ -45,7 +45,7 @@
    restricted.  For example, one might want a Perl function that sends
    mail.  To handle these cases, PL/Perl can also be installed as an
    “untrusted” language (usually called
-   PL/PerlU).
+   PL/PerlU).
    In this case the full Perl language is available.  If the
    createlang program is used to install the
    language, the language name plperlu will select
diff --git a/docs/en_US/pg/plperl.html b/docs/en_US/pg/plperl.html
index 76f38bb86d..12d2afe83e 100644
--- a/docs/en_US/pg/plperl.html
+++ b/docs/en_US/pg/plperl.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -26,7 +26,7 @@
 
    39.7. Limitations and Missing Features
    
 
 
    
-
       PL/Perl is a loadable procedural language that enables you to write
+
       PL/Perl is a loadable procedural language that enables you to write
    PostgreSQL functions in the 
    Perl programming language.
   
    
@@ -102,7 +102,7 @@ 
    Note
    
 $$ LANGUAGE plperl;
    
 
    
   
    
-
       If an SQL null value is passed to a function,
+
       If an SQL null value is passed to a function,
    the argument value will appear as “undefined” in Perl.  The
    above function definition will not behave very nicely with null
    inputs (in fact, it will act as though they are zeroes).  We could
diff --git a/docs/en_US/pg/plpgsql-control-structures.html b/docs/en_US/pg/plpgsql-control-structures.html
index dd865af686..b4e5215376 100644
--- a/docs/en_US/pg/plpgsql-control-structures.html
+++ b/docs/en_US/pg/plpgsql-control-structures.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -29,7 +29,7 @@
     
    
 
    
 
    
-37.7.1.1. RETURN
    
+37.7.1.1. RETURN
    
 
    RETURN expression;
    
 
          RETURN with an expression terminates the
       function and returns the value of
@@ -63,7 +63,7 @@
 
 
    
 
    
-37.7.1.2. RETURN NEXT
    
+37.7.1.2. RETURN NEXT
    
 
    RETURN NEXT expression;
    
 
          When a PL/pgSQL function is declared to return
       SETOF sometype, the procedure
@@ -143,7 +143,7 @@ 
    Note
    
     
    
 
    
 
    
-37.7.2.1. IF-THEN
    
+37.7.2.1. IF-THEN
    
 
    IF boolean-expression THEN
     statements
 END IF;
    
@@ -163,7 +163,7 @@ 
    Note
    
 
 
    
 
    
-37.7.2.2. IF-THEN-ELSE
    
+37.7.2.2. IF-THEN-ELSE
    
 
    IF boolean-expression THEN
     statements
 ELSE
@@ -196,7 +196,7 @@ 
    Note
    
 
 
    
 
    
-37.7.2.3. IF-THEN-ELSE IF
    
+37.7.2.3. IF-THEN-ELSE IF
    
 
            IF statements can be nested, as in the
         following example:
 
@@ -222,7 +222,7 @@ 
    Note
    
 
 
    
 
    
-37.7.2.4. IF-THEN-ELSIF-ELSE
    
+37.7.2.4. IF-THEN-ELSIF-ELSE
    
 
    IF boolean-expression THEN
     statements
 [ ELSIF boolean-expression THEN
@@ -257,7 +257,7 @@ 
    Note
    
 
 
    
 
    
-37.7.2.5. IF-THEN-ELSEIF-ELSE
    
+37.7.2.5. IF-THEN-ELSEIF-ELSE
    
 
           ELSEIF is an alias for ELSIF.
       
    
 
@@ -265,14 +265,14 @@ 
    Note
    
 
    
 
    
 37.7.3. Simple Loops
    
-
         With the LOOP, EXIT,
+
         With the LOOP, EXIT,
      CONTINUE, WHILE, and FOR
      statements, you can arrange for your PL/pgSQL
      function to repeat a series of commands.
     
    
 
    
 
    
-37.7.3.1. LOOP
    
+37.7.3.1. LOOP
    
 
    [ <<label>> ]
 LOOP
     statements
@@ -287,8 +287,8 @@ 
    Note
    
 
 
    
 
    
-37.7.3.2. EXIT
    
-
    EXIT [ label ] [ WHEN expression ];
    
+37.7.3.2. EXIT
    
+
    EXIT [ label ] [ WHEN expression ];
    
 
            If no label is given, the innermost
         loop is terminated and the statement following END
         LOOP is executed next.  If label
@@ -331,8 +331,8 @@ 
    Note
    
 
 
    
 
    
-37.7.3.3. CONTINUE
    
-
    CONTINUE [ label ] [ WHEN expression ];
    
+37.7.3.3. CONTINUE
    
+
    CONTINUE [ label ] [ WHEN expression ];
    
 
            If no label is given, the next iteration of
         the innermost loop is begun. That is, control is passed back
         to the loop control expression (if any), and the body of the
@@ -361,8 +361,8 @@ 
    Note
    
 
 
    
 
    
-37.7.3.4. WHILE
    
-
    [ <<label>> ]
+37.7.3.4. WHILE
    
+
    [ <<label>> ]
 WHILE expression LOOP
     statements
 END LOOP [ label ];
    
@@ -385,7 +385,7 @@ 
    Note
    
 
 
    
 
    
-37.7.3.5. FOR (integer variant)
    
+37.7.3.5. FOR (integer variant)
    
 
    [ <<label>> ]
 FOR name IN [ REVERSE ] expression .. expression [ BY expression ] LOOP
     statements
@@ -505,7 +505,7 @@ 
    Note
    
 
    
 
    
 37.7.5. Trapping Errors
    
-
         By default, any error occurring in a PL/pgSQL
+
         By default, any error occurring in a PL/pgSQL
      function aborts execution of the function, and indeed of the
      surrounding transaction as well.  You can trap errors and recover
      from them by using a BEGIN block with an
diff --git a/docs/en_US/pg/plpgsql-cursors.html b/docs/en_US/pg/plpgsql-cursors.html
index 8499d3b8c9..93f213fbd2 100644
--- a/docs/en_US/pg/plpgsql-cursors.html
+++ b/docs/en_US/pg/plpgsql-cursors.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 37.8. Cursors
    
-
        Rather than executing a whole query at once, it is possible to set
+
        Rather than executing a whole query at once, it is possible to set
     up a cursor that encapsulates the query, and then read
     the query result a few rows at a time. One reason for doing this is
     to avoid memory overrun when the result contains a large number of
@@ -74,7 +74,7 @@
     
    
 
    
 
    
-37.8.2.1. OPEN FOR query
    
+37.8.2.1. OPEN FOR query
    
 
    OPEN unbound_cursor FOR query;
    
 
            The cursor variable is opened and given the specified query to
         execute.  The cursor cannot be open already, and it must have been
@@ -95,7 +95,7 @@
 
 
    
 
    
-37.8.2.2. OPEN FOR EXECUTE
    
+37.8.2.2. OPEN FOR EXECUTE
    
 
    OPEN unbound_cursor FOR EXECUTE query_string;
    
 
              The cursor variable is opened and given the specified query to
           execute.  The cursor cannot be open already, and it must have been
@@ -113,7 +113,7 @@
 
 
    
 
    
-37.8.2.3. Opening a Bound Cursor
    
+37.8.2.3. Opening a Bound Cursor
    
 
    OPEN bound_cursor [ ( argument_values ) ];
    
 
              This form of OPEN is used to open a cursor
           variable whose query was bound to it when it was declared.  The
@@ -151,7 +151,7 @@
     
    
 
    
 
    
-37.8.3.1. FETCH
    
+37.8.3.1. FETCH
    
 
    FETCH cursor INTO target;
    
 
              FETCH retrieves the next row from the
           cursor into a target, which may be a row variable, a record
@@ -169,7 +169,7 @@
 
 
    
 
    
-37.8.3.2. CLOSE
    
+37.8.3.2. CLOSE
    
 
    CLOSE cursor;
    
 
            CLOSE closes the portal underlying an open
         cursor.  This can be used to release resources earlier than end of
@@ -183,7 +183,7 @@
 
 
    
 
    
-37.8.3.3. Returning Cursors
    
+37.8.3.3. Returning Cursors
    
 
            PL/pgSQL functions can return cursors to the
         caller. This is useful to return multiple rows or columns,
         especially with very large result sets.  To do this, the function
diff --git a/docs/en_US/pg/plpgsql-declarations.html b/docs/en_US/pg/plpgsql-declarations.html
index 90c58ef079..c1e7e00c4e 100644
--- a/docs/en_US/pg/plpgsql-declarations.html
+++ b/docs/en_US/pg/plpgsql-declarations.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plpgsql-development-tips.html b/docs/en_US/pg/plpgsql-development-tips.html
index ff03a100f3..4fba20afda 100644
--- a/docs/en_US/pg/plpgsql-development-tips.html
+++ b/docs/en_US/pg/plpgsql-development-tips.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plpgsql-errors-and-messages.html b/docs/en_US/pg/plpgsql-errors-and-messages.html
index b758e5dd15..6f24ee9744 100644
--- a/docs/en_US/pg/plpgsql-errors-and-messages.html
+++ b/docs/en_US/pg/plpgsql-errors-and-messages.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 37.9. Errors and Messages
    
-
        Use the RAISE statement to report messages and
+
        Use the RAISE statement to report messages and
     raise errors.
 
 
    
diff --git a/docs/en_US/pg/plpgsql-expressions.html b/docs/en_US/pg/plpgsql-expressions.html
index f213cc8cde..c886ef0661 100644
--- a/docs/en_US/pg/plpgsql-expressions.html
+++ b/docs/en_US/pg/plpgsql-expressions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plpgsql-porting.html b/docs/en_US/pg/plpgsql-porting.html
index a2ef75d6b0..eaa857c24d 100644
--- a/docs/en_US/pg/plpgsql-porting.html
+++ b/docs/en_US/pg/plpgsql-porting.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 37.11. Porting from Oracle PL/SQL
    
-
       This section explains differences between
+
       This section explains differences between
    PostgreSQL's PL/pgSQL
    language and Oracle's PL/SQL language,
    to help developers who port applications from
@@ -60,7 +60,7 @@
    
    
 
    
 
    
-37.11.1. Porting Examples
    
+37.11.1. Porting Examples
    
 
        Example 37.5, “Porting a Simple Function from PL/SQL to PL/pgSQL” shows how to port a simple
     function from PL/SQL to PL/pgSQL.
    
    
@@ -225,7 +225,7 @@
     PostgreSQL does not have a built-in
     instr function, but you can create one
     using a combination of other
-    functions. In Section 37.11.3, “Appendix” there is a
+    functions. In Section 37.11.3, “Appendix” there is a
     PL/pgSQL implementation of
     instr that you can use to make your porting
     easier.
@@ -496,7 +496,7 @@
 
 
    
 
    
-37.11.2.2. EXECUTE
    
+37.11.2.2. EXECUTE
    
 
         The PL/pgSQL version of
      EXECUTE works similarly to the
      PL/SQL version, but you have to remember to use
diff --git a/docs/en_US/pg/plpgsql-statements.html b/docs/en_US/pg/plpgsql-statements.html
index 0da320c9f5..526ef0757b 100644
--- a/docs/en_US/pg/plpgsql-statements.html
+++ b/docs/en_US/pg/plpgsql-statements.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -139,7 +139,7 @@ 
    Note
    
 
    
 
    
 37.6.3. Executing a Query with a Single-Row Result
    
-
         The result of a SQL command yielding a single row (possibly of multiple
+
         The result of a SQL command yielding a single row (possibly of multiple
      columns) can be assigned to a record variable, row-type variable, or list
      of scalar variables.  This is done by writing the base SQL command and
      adding an INTO clause.  For example,
@@ -351,7 +351,7 @@ 
    Note
    
         || quote_literal(keyvalue);
    
 
    
     
    
-
         This example demonstrates the use of the
+
         This example demonstrates the use of the
      quote_ident and
      quote_literal functions.  For safety,
      expressions containing column and table identifiers should be
diff --git a/docs/en_US/pg/plpgsql-structure.html b/docs/en_US/pg/plpgsql-structure.html
index 364c702f5e..c347b0ad73 100644
--- a/docs/en_US/pg/plpgsql-structure.html
+++ b/docs/en_US/pg/plpgsql-structure.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/plpgsql-trigger.html b/docs/en_US/pg/plpgsql-trigger.html
index b74a846cb6..3d5868abc8 100644
--- a/docs/en_US/pg/plpgsql-trigger.html
+++ b/docs/en_US/pg/plpgsql-trigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 37.10. Trigger Procedures
    
-
            PL/pgSQL can be used to define trigger
+
            PL/pgSQL can be used to define trigger
         procedures. A trigger procedure is created with the
         CREATE FUNCTION command, declaring it as a function with
         no arguments and a return type of trigger.  Note that
diff --git a/docs/en_US/pg/plpgsql.html b/docs/en_US/pg/plpgsql.html
index bedd617d1d..ef88ad3054 100644
--- a/docs/en_US/pg/plpgsql.html
+++ b/docs/en_US/pg/plpgsql.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -61,13 +61,13 @@
 
    37.10. Trigger Procedures
    
 
    37.11. Porting from Oracle PL/SQL
    
 
    
-
    37.11.1. Porting Examples
    
+
    37.11.1. Porting Examples
    
 
    37.11.2. Other Things to Watch For
    
 
    37.11.3. Appendix
    
 
    
 
 
    
-
      PL/pgSQL is a loadable procedural
+
      PL/pgSQL is a loadable procedural
   language for the PostgreSQL database
   system.  The design goals of PL/pgSQL were to create
   a loadable procedural language that
@@ -112,7 +112,7 @@
     creates a prepared execution plan (using the
     SPI manager's SPI_prepare
     and SPI_saveplan
-    functions). Subsequent visits to that expression or command
+    functions). Subsequent visits to that expression or command
     reuse the prepared plan.  Thus, a function with conditional code
     that contains many statements for which execution plans might be
     required will only prepare and save those plans that are really
diff --git a/docs/en_US/pg/plpython-database.html b/docs/en_US/pg/plpython-database.html
index 39d349c387..cde04c62a0 100644
--- a/docs/en_US/pg/plpython-database.html
+++ b/docs/en_US/pg/plpython-database.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -25,7 +25,7 @@
    plpy.notice(msg),
    plpy.warning(msg),
    plpy.error(msg), and
-   plpy.fatal(msg).
+   plpy.fatal(msg).
    plpy.error and 
    plpy.fatal actually raise a Python exception
    which, if uncaught, propagates out to the calling query, causing
@@ -67,7 +67,7 @@
 
    foo = rv[i]["my_column"]
    
 
    
   
    
-
       
+
       
    The second function, plpy.prepare, prepares
    the execution plan for a query.  It is called with a query string
    and a list of parameter types, if you have parameter references in
diff --git a/docs/en_US/pg/plpython-trigger.html b/docs/en_US/pg/plpython-trigger.html
index 965dcb78f2..17ef28b310 100644
--- a/docs/en_US/pg/plpython-trigger.html
+++ b/docs/en_US/pg/plpython-trigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 40.2. Trigger Functions
    
-
       When a function is used as a trigger, the dictionary
+
       When a function is used as a trigger, the dictionary
    TD contains trigger-related values.  The trigger
    rows are in TD["new"] and/or TD["old"]
    depending on the trigger event.  TD["event"] contains
diff --git a/docs/en_US/pg/plpython.html b/docs/en_US/pg/plpython.html
index 422fb112c3..72f3451a9a 100644
--- a/docs/en_US/pg/plpython.html
+++ b/docs/en_US/pg/plpython.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -22,7 +22,7 @@
 
    40.3. Database Access
    
 
 
    
-
      The PL/Python procedural language allows
+
      The PL/Python procedural language allows
   PostgreSQL functions to be written in the
   Python language.
  
    
@@ -105,7 +105,7 @@ 
    Note
    
    value. Alternatively, one can use named parameters as shown in the example
    above.  Use of named parameters is usually more readable.
   
    
-
       If an SQL null value is passed to a
+
       If an SQL null value is passed to a
    function, the argument value will appear as None in
    Python. The above function definition will return the wrong answer for null
    inputs. We could add STRICT to the function definition
@@ -326,7 +326,7 @@ 
    Warning
    
    data between function calls.  This variable is private static data.
    The global dictionary GD is public data,
    available to all Python functions within a session.  Use with
-   care.
+   care.
   
    
 
       Each function gets its own execution environment in the
    Python interpreter, so that global data and function arguments from
diff --git a/docs/en_US/pg/pltcl-data.html b/docs/en_US/pg/pltcl-data.html
index 7d6d9b9977..651e718f39 100644
--- a/docs/en_US/pg/pltcl-data.html
+++ b/docs/en_US/pg/pltcl-data.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/pltcl-dbaccess.html b/docs/en_US/pg/pltcl-dbaccess.html
index a6fb231c4c..4cc6b989a4 100644
--- a/docs/en_US/pg/pltcl-dbaccess.html
+++ b/docs/en_US/pg/pltcl-dbaccess.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -85,7 +85,7 @@
 
    
 
            Prepares and saves a query plan for later execution.  The
         saved plan will be retained for the life of the current
-        session.
+        session.
        
    
 
            The query may use parameters, that is, placeholders for
         values to be supplied whenever the plan is actually executed.
diff --git a/docs/en_US/pg/pltcl-functions.html b/docs/en_US/pg/pltcl-functions.html
index a69c70b960..8d65fc1ea3 100644
--- a/docs/en_US/pg/pltcl-functions.html
+++ b/docs/en_US/pg/pltcl-functions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/pltcl-global.html b/docs/en_US/pg/pltcl-global.html
index f2f660cacd..9348a8661f 100644
--- a/docs/en_US/pg/pltcl-global.html
+++ b/docs/en_US/pg/pltcl-global.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 38.4. Global Data in PL/Tcl
    
-
         Sometimes it
+
         Sometimes it
      is useful to have some global data that is held between two
      calls to a function or is shared between different functions.
      This is easily done since
diff --git a/docs/en_US/pg/pltcl-procnames.html b/docs/en_US/pg/pltcl-procnames.html
index d1cd1b006d..ec2e20a6a5 100644
--- a/docs/en_US/pg/pltcl-procnames.html
+++ b/docs/en_US/pg/pltcl-procnames.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/pltcl-trigger.html b/docs/en_US/pg/pltcl-trigger.html
index f0025f0a95..2f3abf9774 100644
--- a/docs/en_US/pg/pltcl-trigger.html
+++ b/docs/en_US/pg/pltcl-trigger.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 38.6. Trigger Procedures in PL/Tcl
    
-
         Trigger procedures can be written in PL/Tcl.
+
         Trigger procedures can be written in PL/Tcl.
      PostgreSQL requires that a procedure that is to be called
      as a trigger must be declared as a function with no arguments
      and a return type of trigger.
diff --git a/docs/en_US/pg/pltcl-unknown.html b/docs/en_US/pg/pltcl-unknown.html
index 31d6e5db60..df14a49486 100644
--- a/docs/en_US/pg/pltcl-unknown.html
+++ b/docs/en_US/pg/pltcl-unknown.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/pltcl.html b/docs/en_US/pg/pltcl.html
index ea7bbd32ff..7fc1003450 100644
--- a/docs/en_US/pg/pltcl.html
+++ b/docs/en_US/pg/pltcl.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 
    38.8. Tcl Procedure Names
    
 
 
-
       PL/Tcl is a loadable procedural language for the
+
       PL/Tcl is a loadable procedural language for the
    PostgreSQL database system
    that enables the    Tcl language to be used to write functions and
    trigger procedures.
diff --git a/docs/en_US/pg/populate.html b/docs/en_US/pg/populate.html
index a1b721d4e3..446e98e333 100644
--- a/docs/en_US/pg/populate.html
+++ b/docs/en_US/pg/populate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,7 +21,7 @@
 
    
 
    
 13.4.1. Disable Autocommit
    
-
        Turn off autocommit and just do one commit at the end.  (In plain
+
        Turn off autocommit and just do one commit at the end.  (In plain
     SQL, this means issuing BEGIN at the start and
     COMMIT at the end.  Some client libraries may
     do this behind your back, in which case you need to make sure the
@@ -152,7 +152,7 @@
     drop or recreate indexes, and it does not normally touch foreign
     keys.
 
-     [8]
+     [8]
 
     So when loading a data-only dump, it is up to you to drop and recreate
     indexes and foreign keys if you wish to use those techniques.
@@ -165,7 +165,7 @@
 
    
 
    
 
    
-
    [8]        You can get the effect of disabling foreign keys by using
+
    [8]        You can get the effect of disabling foreign keys by using
        the --disable-triggers option — but realize that
        that eliminates, rather than just postponing, foreign key
        validation, and so it is possible to insert bad data if you use it.
diff --git a/docs/en_US/pg/preface.html b/docs/en_US/pg/preface.html
index 14c8fd4fef..b93528fc68 100644
--- a/docs/en_US/pg/preface.html
+++ b/docs/en_US/pg/preface.html
@@ -5,9 +5,9 @@
 
 
 
-
-
-
+
+
+
 
 
 
@@ -22,15 +22,15 @@
 
    
 
    1.2.1. The Berkeley POSTGRES Project
    
 
    1.2.2. Postgres95
    
-
    1.2.3. PostgreSQL
    
+
    1.2.3. PostgreSQL
    
 
    
 
    1.3. Conventions
    
 
    1.4. Further Information
    
 
    1.5. Bug Reporting Guidelines
    
 
    
-
    1.5.1. Identifying Bugs
    
-
    1.5.2. What to report
    
-
    1.5.3. Where to report bugs
    
+
    1.5.1. Identifying Bugs
    
+
    1.5.2. What to report
    
+
    1.5.3. Where to report bugs
    
 
    
 
 
    
diff --git a/docs/en_US/pg/privileges.html b/docs/en_US/pg/privileges.html
index e1e8a0b407..a5802be87b 100644
--- a/docs/en_US/pg/privileges.html
+++ b/docs/en_US/pg/privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 18.3. Privileges
    
-
       When an object is created, it is assigned an owner. The
+
       When an object is created, it is assigned an owner. The
    owner is normally the role that executed the creation statement.
    For most kinds of objects, the initial state is that only the owner
    (or a superuser) can do anything with the object. To allow
diff --git a/docs/en_US/pg/protocol-changes.html b/docs/en_US/pg/protocol-changes.html
index 27eca64408..f1307e2ee3 100644
--- a/docs/en_US/pg/protocol-changes.html
+++ b/docs/en_US/pg/protocol-changes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/protocol-error-fields.html b/docs/en_US/pg/protocol-error-fields.html
index 5ad43e541e..315788d94f 100644
--- a/docs/en_US/pg/protocol-error-fields.html
+++ b/docs/en_US/pg/protocol-error-fields.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/protocol-flow.html b/docs/en_US/pg/protocol-flow.html
index 0d943c5045..2216bf4c74 100644
--- a/docs/en_US/pg/protocol-flow.html
+++ b/docs/en_US/pg/protocol-flow.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -26,7 +26,7 @@
   
    
 
    
 
    
-44.2.1. Start-Up
    
+44.2.1. Start-Up
    
 
        To begin a session, a frontend opens a connection to the server and sends
     a startup message.  This message includes the names of the user and of the
     database the user wants to connect to; it also identifies the particular
@@ -160,7 +160,7 @@
 
    
 
    
 
    
-44.2.2. Simple Query
    
+44.2.2. Simple Query
    
 
        A simple query cycle is initiated by the frontend sending a Query message
     to the backend.  The message includes an SQL command (or commands)
     expressed as a text string.
@@ -476,7 +476,7 @@ 
    Note
    
 
 
    
 
    
-44.2.4. Function Call
    
+44.2.4. Function Call
    
 
        The Function Call sub-protocol allows the client to request a direct
     call of any function that exists in the database's
     pg_proc system catalog.  The client must have
@@ -658,7 +658,7 @@ 
    Note
    
 
 
    
 
    
-44.2.7. Cancelling Requests in Progress
    
+44.2.7. Cancelling Requests in Progress
    
 
        During the processing of a query, the frontend may request
     cancellation of the query.  The cancel request is not sent
     directly on the open connection to the backend for reasons of
@@ -710,7 +710,7 @@ 
    Note
    
 
 
    
 
    
-44.2.8. Termination
    
+44.2.8. Termination
    
 
        The normal, graceful termination procedure is that the frontend
     sends a Terminate message and immediately closes the connection.
     On receipt of this message, the backend closes the connection and
@@ -742,7 +742,7 @@ 
    Note
    
 
 
    
 
    
-44.2.9. SSL Session Encryption
    
+44.2.9. SSL Session Encryption
    
 
        If PostgreSQL was built with
     SSL support, frontend/backend communications
     can be encrypted using SSL.  This provides
diff --git a/docs/en_US/pg/protocol-message-formats.html b/docs/en_US/pg/protocol-message-formats.html
index fe83dc9561..6c3086f568 100644
--- a/docs/en_US/pg/protocol-message-formats.html
+++ b/docs/en_US/pg/protocol-message-formats.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/protocol-message-types.html b/docs/en_US/pg/protocol-message-types.html
index af80a39e7c..670b6ba073 100644
--- a/docs/en_US/pg/protocol-message-types.html
+++ b/docs/en_US/pg/protocol-message-types.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/protocol.html b/docs/en_US/pg/protocol.html
index 242406dcc7..d281f1c59c 100644
--- a/docs/en_US/pg/protocol.html
+++ b/docs/en_US/pg/protocol.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -25,15 +25,15 @@
 
 
    44.2. Message Flow
    
 
    
-
    44.2.1. Start-Up
    
-
    44.2.2. Simple Query
    
+
    44.2.1. Start-Up
    
+
    44.2.2. Simple Query
    
 
    44.2.3. Extended Query
    
-
    44.2.4. Function Call
    
+
    44.2.4. Function Call
    
 
    44.2.5. COPY Operations
    
 
    44.2.6. Asynchronous Operations
    
-
    44.2.7. Cancelling Requests in Progress
    
-
    44.2.8. Termination
    
-
    44.2.9. SSL Session Encryption
    
+
    44.2.7. Cancelling Requests in Progress
    
+
    44.2.8. Termination
    
+
    44.2.9. SSL Session Encryption
    
 
    
 
    44.3. Message Data Types
    
 
    44.4. Message Formats
    
diff --git a/docs/en_US/pg/queries-limit.html b/docs/en_US/pg/queries-limit.html
index d6d238fe6e..bd1d7d50a3 100644
--- a/docs/en_US/pg/queries-limit.html
+++ b/docs/en_US/pg/queries-limit.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.6. LIMIT and OFFSET
    
-
       LIMIT and OFFSET allow you to retrieve just
+
       LIMIT and OFFSET allow you to retrieve just
    a portion of the rows that are generated by the rest of the query:
 
    
 
    SELECT select_list
diff --git a/docs/en_US/pg/queries-order.html b/docs/en_US/pg/queries-order.html
index c67450b77e..87de997222 100644
--- a/docs/en_US/pg/queries-order.html
+++ b/docs/en_US/pg/queries-order.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.5. Sorting Rows
    
-
       After a query has produced an output table (after the select list
+
       After a query has produced an output table (after the select list
    has been processed) it can optionally be sorted.  If sorting is not
    chosen, the rows will be returned in an unspecified order.  The actual
    order in that case will depend on the scan and join plan types and
@@ -42,7 +42,7 @@
    “smaller” is defined in terms of the
    < operator.  Similarly, descending order is
    determined with the > operator.
-    [4]
+    [4]
   
    
 
       For backwards compatibility with the SQL92 version of the standard,
    a sort_expression can instead be the name or number
@@ -71,7 +71,7 @@
   
    
 
    
 
    
-
    [4]       Actually, PostgreSQL uses the default B-tree
+
    [4]       Actually, PostgreSQL uses the default B-tree
       operator class for the expression's data type to determine the sort
       ordering for ASC and DESC.  Conventionally,
       data types will be set up so that the < and
diff --git a/docs/en_US/pg/queries-select-lists.html b/docs/en_US/pg/queries-select-lists.html
index c89988288c..4c7dead602 100644
--- a/docs/en_US/pg/queries-select-lists.html
+++ b/docs/en_US/pg/queries-select-lists.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.3. Select Lists
    
-
       As shown in the previous section,
+
       As shown in the previous section,
    the table expression in the SELECT command
    constructs an intermediate virtual table by possibly combining
    tables, views, eliminating rows, grouping, etc.  This table is
@@ -25,7 +25,7 @@
 
    
 
    
 7.3.1. Select-List Items
    
-
        The simplest kind of select list is * which
+
        The simplest kind of select list is * which
     emits all columns that the table expression produces.  Otherwise,
     a select list is a comma-separated list of value expressions (as
     defined in Section 4.2, “Value Expressions”).  For instance, it
@@ -66,7 +66,7 @@
 
    
 
    
 7.3.2. Column Labels
    
-
        The entries in the select list can be assigned names for further
+
        The entries in the select list can be assigned names for further
     processing.  The “further processing” in this case is
     an optional sort specification and the client application (e.g.,
     column headers for display).  For example:
@@ -92,7 +92,7 @@ 
    Note
    
 
    
 
    
 7.3.3. DISTINCT
    
-
        After the select list has been processed, the result table may
+
        After the select list has been processed, the result table may
     optionally be subject to the elimination of duplicate rows.  The
     DISTINCT key word is written directly after
     SELECT to specify this:
@@ -102,7 +102,7 @@ 
    Note
    
     (Instead of DISTINCT the key word ALL
     can be used to specify the default behavior of retaining all rows.)
    
    
-
        
+
        
     Obviously, two rows are considered distinct if they differ in at
     least one column value.  Null values are considered equal in this
     comparison.
diff --git a/docs/en_US/pg/queries-table-expressions.html b/docs/en_US/pg/queries-table-expressions.html
index 9ae6899ea4..769d687ff1 100644
--- a/docs/en_US/pg/queries-table-expressions.html
+++ b/docs/en_US/pg/queries-table-expressions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.2. Table Expressions
    
-
       A table expression computes a table.  The
+
       A table expression computes a table.  The
    table expression contains a FROM clause that is
    optionally followed by WHERE, GROUP BY, and
    HAVING clauses.  Trivial table expressions simply refer
@@ -48,7 +48,7 @@
     and HAVING clauses and is finally the result of the
     overall table expression.
    
    
-
        When a table reference names a table that is the parent of a
+
        When a table reference names a table that is the parent of a
     table inheritance hierarchy, the table reference produces rows of
     not only that table but all of its descendant tables, unless the
     key word ONLY precedes the table name.  However, the
@@ -58,7 +58,7 @@
 
    
 
    
 7.2.1.1. Joined Tables
    
-
         A joined table is a table derived from two other (real or
+
         A joined table is a table derived from two other (real or
      derived) tables according to the rules of the particular join
      type.  Inner, outer, and cross-joins are available.
     
    
@@ -120,8 +120,8 @@
         a, b, and c in the result,
         whereas with USING there will be only one of each.
        
    
-
            
-        
+
            
+        
         Finally, NATURAL is a shorthand form of
         USING: it forms a USING list
         consisting of exactly those column names that appear in both
@@ -276,7 +276,7 @@
 
    
 
    
 7.2.1.2. Table and Column Aliases
    
-
         A temporary name can be given to tables and complex table
+
         A temporary name can be given to tables and complex table
      references to be used for references to the derived table in
      the rest of the query.  This is called a table
      alias.
@@ -360,7 +360,7 @@
 
    
 
    
 7.2.1.3. Subqueries
    
-
         Subqueries specifying a derived table must be enclosed in
+
         Subqueries specifying a derived table must be enclosed in
      parentheses and must be assigned a table
      alias name.  (See Section 7.2.1.2, “Table and Column Aliases”.)  For
      example:
@@ -386,7 +386,7 @@
 
    
 
    
 7.2.1.4. Table Functions
    
-
         Table functions are functions that produce a set of rows, made up
+
         Table functions are functions that produce a set of rows, made up
      of either base data types (scalar types) or composite data types
      (table rows).  They are used like a table, view, or subquery in
      the FROM clause of a query. Columns returned by table
@@ -448,7 +448,7 @@
 
    
 
    
 7.2.2. The WHERE Clause
    
-
        The syntax of the WHERE Clause is
+
        The syntax of the WHERE Clause is
 
    
 
    WHERE search_condition
    
 
    
@@ -523,7 +523,7 @@ 
    Note
    
 
    
 
    
 7.2.3. The GROUP BY and HAVING Clauses
    
-
        After passing the WHERE filter, the derived input
+
        After passing the WHERE filter, the derived input
     table may be subject to grouping, using the GROUP BY
     clause, and elimination of group rows using the HAVING
     clause.
@@ -614,7 +614,7 @@ 
    Tip
    
     select list.  Grouping by value expressions instead of simple
     column names is also allowed.
    
    
-
        If a table has been grouped using a GROUP BY
+
        If a table has been grouped using a GROUP BY
     clause, but then only certain groups are of interest, the
     HAVING clause can be used, much like a
     WHERE clause, to eliminate groups from a grouped
diff --git a/docs/en_US/pg/queries-union.html b/docs/en_US/pg/queries-union.html
index 118639a3bc..4614d47113 100644
--- a/docs/en_US/pg/queries-union.html
+++ b/docs/en_US/pg/queries-union.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.4. Combining Queries
    
-
       The results of two queries can be combined using the set operations
+
       The results of two queries can be combined using the set operations
    union, intersection, and difference.  The syntax is
 
    
 
    query1 UNION [ALL] query2
diff --git a/docs/en_US/pg/queries-values.html b/docs/en_US/pg/queries-values.html
index e60ecc0d71..e302affa20 100644
--- a/docs/en_US/pg/queries-values.html
+++ b/docs/en_US/pg/queries-values.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 7.7. VALUES Lists
    
-
       VALUES provides a way to generate a “constant table”
+
       VALUES provides a way to generate a “constant table”
    that can be used in a query without having to actually create and populate
    a table on-disk.  The syntax is
 
    
diff --git a/docs/en_US/pg/queries.html b/docs/en_US/pg/queries.html
index 552de4b169..a5ea7981a1 100644
--- a/docs/en_US/pg/queries.html
+++ b/docs/en_US/pg/queries.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -36,7 +36,7 @@
 
    7.7. VALUES Lists
    
 
 
    
-
      The previous chapters explained how to create tables, how to fill
+
      The previous chapters explained how to create tables, how to fill
   them with data, and how to manipulate that data.  Now we finally
   discuss how to retrieve the data out of the database.
  
    
diff --git a/docs/en_US/pg/reference-client.html b/docs/en_US/pg/reference-client.html
index 92d58ae609..03d526246a 100644
--- a/docs/en_US/pg/reference-client.html
+++ b/docs/en_US/pg/reference-client.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 PostgreSQL Client Applications
    
 
    
 
    
-
    
+
    
 
    
 
        This part contains reference information for
     PostgreSQL client applications and
diff --git a/docs/en_US/pg/reference-server.html b/docs/en_US/pg/reference-server.html
index d0ee1e8ea1..b8c500a0e8 100644
--- a/docs/en_US/pg/reference-server.html
+++ b/docs/en_US/pg/reference-server.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 PostgreSQL Server Applications
    
 
    
 
    
-
    
+
    
 
    
 
        This part contains reference information for
     PostgreSQL server applications and
diff --git a/docs/en_US/pg/reference.html b/docs/en_US/pg/reference.html
index 1630321868..7215c1dcde 100644
--- a/docs/en_US/pg/reference.html
+++ b/docs/en_US/pg/reference.html
@@ -5,8 +5,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 Part VI. Reference
    
-
    
+
    
 
    
 
       The entries in this Reference are meant to provide in reasonable
    length an authoritative, complete, and formal summary about their
diff --git a/docs/en_US/pg/regress-evaluation.html b/docs/en_US/pg/regress-evaluation.html
index 6b6c4a07fb..e6d12dde9a 100644
--- a/docs/en_US/pg/regress-evaluation.html
+++ b/docs/en_US/pg/regress-evaluation.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -45,7 +45,7 @@
    
    
 
    
 
    
-28.2.1. Error message differences
    
+28.2.1. Error message differences
    
 
         Some of the regression tests involve intentional invalid input
      values.  Error messages can come from either the
      PostgreSQL code or from the host
@@ -58,7 +58,7 @@
 
    
 
    
 
    
-28.2.2. Locale differences
    
+28.2.2. Locale differences
    
 
         If you run the tests against an already-installed server that was
      initialized with a collation-order locale other than C, then
      there may be differences due to sort order and follow-up
@@ -69,7 +69,7 @@
 
    
 
    
 
    
-28.2.3. Date and time differences
    
+28.2.3. Date and time differences
    
 
         Most of the date and time results are dependent on the time zone
      environment.  The reference files are generated for time zone
      PST8PDT (Berkeley, California), and there will be
@@ -81,7 +81,7 @@
 
    
 
    
 
    
-28.2.4. Floating-point differences
    
+28.2.4. Floating-point differences
    
 
         Some of the tests involve computing 64-bit floating-point numbers (double
      precision) from table columns. Differences in
      results involving mathematical functions of double
@@ -103,7 +103,7 @@
 
    
 
    
 
    
-28.2.5. Row ordering differences
    
+28.2.5. Row ordering differences
    
 
    You might see differences in which the same rows are output in a
 different order than what appears in the expected file.  In most cases
 this is not, strictly speaking, a bug.  Most of the regression test
@@ -133,7 +133,7 @@
 
    
 
    
 
    
-28.2.6. Insufficient stack depth
    
+28.2.6. Insufficient stack depth
    
 
         If the errors test results in a server crash
      at the select infinite_recurse() command, it means that
      the platform's limit on process stack size is smaller than the
@@ -148,7 +148,7 @@
 
    
 
    
 
    
-28.2.7. The “random” test
    
+28.2.7. The “random” test
    
 
         The random test script is intended to produce 
      random results.   In rare cases, this causes the random regression
      test to fail.  Typing
diff --git a/docs/en_US/pg/regress-variant.html b/docs/en_US/pg/regress-variant.html
index 05e772b8d9..a1e8e4d0b1 100644
--- a/docs/en_US/pg/regress-variant.html
+++ b/docs/en_US/pg/regress-variant.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/regress.html b/docs/en_US/pg/regress.html
index fd8224cd16..c776fa0316 100644
--- a/docs/en_US/pg/regress.html
+++ b/docs/en_US/pg/regress.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,18 +20,18 @@
 
    28.1. Running the Tests
    
 
    28.2. Test Evaluation
    
 
    
-
    28.2.1. Error message differences
    
-
    28.2.2. Locale differences
    
-
    28.2.3. Date and time differences
    
-
    28.2.4. Floating-point differences
    
-
    28.2.5. Row ordering differences
    
-
    28.2.6. Insufficient stack depth
    
-
    28.2.7. The “random” test
    
+
    28.2.1. Error message differences
    
+
    28.2.2. Locale differences
    
+
    28.2.3. Date and time differences
    
+
    28.2.4. Floating-point differences
    
+
    28.2.5. Row ordering differences
    
+
    28.2.6. Insufficient stack depth
    
+
    28.2.7. The “random” test
    
 
    
 
    28.3. Variant Comparison Files
    
 
 
-
       The regression tests are a comprehensive set of tests for the SQL
+
       The regression tests are a comprehensive set of tests for the SQL
    implementation in PostgreSQL.  They test
    standard SQL operations as well as the extended capabilities of
    PostgreSQL.
diff --git a/docs/en_US/pg/release-0-01.html b/docs/en_US/pg/release-0-01.html
index a244428bf7..9e248e1680 100644
--- a/docs/en_US/pg/release-0-01.html
+++ b/docs/en_US/pg/release-0-01.html
@@ -1,19 +1,19 @@
 
 
 
-E.88. Postgres95 Release 0.01
+E.93. Postgres95 Release 0.01
 
 
 
-
+
 
-
+
 
 
 
 
    
 
    
-E.88. Postgres95 Release 0.01
    
+E.93. Postgres95 Release 0.01
    
 
    
 
    Release date
    
 
    1995-05-01
    
diff --git a/docs/en_US/pg/release-0-02.html b/docs/en_US/pg/release-0-02.html
index 4cc642e56f..59668b4298 100644
--- a/docs/en_US/pg/release-0-02.html
+++ b/docs/en_US/pg/release-0-02.html
@@ -1,26 +1,26 @@
 
 
 
-E.87. Postgres95 Release 0.02
+E.92. Postgres95 Release 0.02
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.87. Postgres95 Release 0.02
    
+E.92. Postgres95 Release 0.02
    
 
    
 
    Release date
    
 
    1995-05-25
    
 
    
 
    
 
    
-E.87.1. Changes
    
+E.92.1. Changes
    
 
    Incompatible changes:
  * The SQL statement for creating a database is 'CREATE DATABASE' instead
    of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE' instead
diff --git a/docs/en_US/pg/release-0-03.html b/docs/en_US/pg/release-0-03.html
index b521482a46..f2b2148111 100644
--- a/docs/en_US/pg/release-0-03.html
+++ b/docs/en_US/pg/release-0-03.html
@@ -1,26 +1,26 @@
 
 
 
-E.86. Postgres95 Release 0.03
+E.91. Postgres95 Release 0.03
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.86. Postgres95 Release 0.03
    
+E.91. Postgres95 Release 0.03
    
 
    
 
    Release date
    
 
    1995-07-21
    
 
    
 
    
 
    
-E.86.1. Changes
    
+E.91.1. Changes
    
 
    Incompatible changes:
  * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
    (due to system catalog changes and indexing structure changes).
diff --git a/docs/en_US/pg/release-1-0.html b/docs/en_US/pg/release-1-0.html
index cf066f504c..948ed8c44e 100644
--- a/docs/en_US/pg/release-1-0.html
+++ b/docs/en_US/pg/release-1-0.html
@@ -1,26 +1,26 @@
 
 
 
-E.85. Release 1.0
+E.90. Release 1.0
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.85. Release 1.0
    
+E.90. Release 1.0
    
 
    
 
    Release date
    
 
    1995-09-05
    
 
    
 
    
 
    
-E.85.1. Changes
    
+E.90.1. Changes
    
 
    Copyright change:
  * The copyright of Postgres 1.0 has been loosened to be freely modifiable
    and modifiable for any purpose.  Please read the COPYRIGHT file.
diff --git a/docs/en_US/pg/release-1-01.html b/docs/en_US/pg/release-1-01.html
index d2f3352b2c..c2a991f2a9 100644
--- a/docs/en_US/pg/release-1-01.html
+++ b/docs/en_US/pg/release-1-01.html
@@ -1,26 +1,26 @@
 
 
 
-E.84. Release 1.01
+E.89. Release 1.01
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.84. Release 1.01
    
+E.89. Release 1.01
    
 
    
 
    Release date
    
 
    1996-02-23
    
 
    
 
    
 
    
-E.84.1. Migration from version 1.0 to version 1.01
    
+E.89.1. Migration from version 1.0 to version 1.01
    
 
    The following notes are for the benefit of users who want to migrate
 databases from Postgres95 1.0 to Postgres95 1.01.  
    
 
    If you are starting afresh with Postgres95 1.01 and do not need
@@ -116,7 +116,7 @@ 
    Release date
    
 
 
    
 
    
-E.84.2. Changes
    
+E.89.2. Changes
    
 
    Incompatibilities:
  * 1.01 is backwards compatible with 1.0 database provided the user
    follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
diff --git a/docs/en_US/pg/release-1-02.html b/docs/en_US/pg/release-1-02.html
index bb6a7a5d05..44acb699af 100644
--- a/docs/en_US/pg/release-1-02.html
+++ b/docs/en_US/pg/release-1-02.html
@@ -1,26 +1,26 @@
 
 
 
-E.83. Release 1.02
+E.88. Release 1.02
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.83. Release 1.02
    
+E.88. Release 1.02
    
 
    
 
    Release date
    
 
    1996-08-01
    
 
    
 
    
 
    
-E.83.1. Migration from version 1.02 to version 1.02.1
    
+E.88.1. Migration from version 1.02 to version 1.02.1
    
 
    Here is a new migration file for 1.02.1.  It includes the 'copy' change
 and a script to convert old ASCII files.
    
 
    
@@ -53,7 +53,7 @@ 
    Note
    
 
    
 
    
 
    
-E.83.2. Dump/Reload Procedure
    
+E.88.2. Dump/Reload Procedure
    
 
    If you are trying to reload a pg_dump or text-mode, copy tablename to
 stdout generated with a previous version, you will need to run the
 attached sed script on the ASCII file before loading it into the
@@ -76,7 +76,7 @@ 
    Note
    
 
 
    
 
    
-E.83.3. Changes
    
+E.88.3. Changes
    
 
    Source code maintenance and development
  * worldwide team of volunteers
  * the source tree now in CVS at ftp.ki.net
diff --git a/docs/en_US/pg/release-1-09.html b/docs/en_US/pg/release-1-09.html
index 84ee6f559b..4b45d7da07 100644
--- a/docs/en_US/pg/release-1-09.html
+++ b/docs/en_US/pg/release-1-09.html
@@ -1,19 +1,19 @@
 
 
 
-E.82. Release 1.09
+E.87. Release 1.09
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.82. Release 1.09
    
+E.87. Release 1.09
    
 
    
 
    Release date
    
 
    1996-11-04
    
diff --git a/docs/en_US/pg/release-6-0.html b/docs/en_US/pg/release-6-0.html
index 277caea584..7d2a4beded 100644
--- a/docs/en_US/pg/release-6-0.html
+++ b/docs/en_US/pg/release-6-0.html
@@ -1,19 +1,19 @@
 
 
 
-E.81. Release 6.0
+E.86. Release 6.0
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.81. Release 6.0
    
+E.86. Release 6.0
    
 
    
 
    Release date
    
 
    1997-01-29
    
@@ -22,19 +22,19 @@ 
    Release date
    
 previous releases of PostgreSQL.
    
 
    
 
    
-E.81.1. Migration from version 1.09 to version 6.0
    
+E.86.1. Migration from version 1.09 to version 6.0
    
 
    This migration requires a complete dump of the 1.09 database and a
 restore of the database in 6.0.
    
 
 
    
 
    
-E.81.2. Migration from pre-1.09 to version 6.0
    
+E.86.2. Migration from pre-1.09 to version 6.0
    
 
    Those migrating from earlier 1.* releases should first upgrade to 1.09
 because the COPY output format was improved from the 1.02 release.
    
 
 
    
 
    
-E.81.3. Changes
    
+E.86.3. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-6-1-1.html b/docs/en_US/pg/release-6-1-1.html
index dd4d33235f..afa1882f59 100644
--- a/docs/en_US/pg/release-6-1-1.html
+++ b/docs/en_US/pg/release-6-1-1.html
@@ -1,33 +1,33 @@
 
 
 
-E.79. Release 6.1.1
+E.84. Release 6.1.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.79. Release 6.1.1
    
+E.84. Release 6.1.1
    
 
    
 
    Release date
    
 
    1997-07-22
    
 
    
 
    
 
    
-E.79.1. Migration from version 6.1 to version 6.1.1
    
+E.84.1. Migration from version 6.1 to version 6.1.1
    
 
    This is a minor bug-fix release. A dump/reload is not required from version 6.1,
 but is required from any release prior to 6.1.
 Refer to the release notes for 6.1 for more details.
    
 
 
    
 
    
-E.79.2. Changes
    
+E.84.2. Changes
    
 
         
    
 
    fix for SET with options (Thomas)
 allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
diff --git a/docs/en_US/pg/release-6-1.html b/docs/en_US/pg/release-6-1.html
index 28be9d8fa5..a84115dc6f 100644
--- a/docs/en_US/pg/release-6-1.html
+++ b/docs/en_US/pg/release-6-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.80. Release 6.1
+E.85. Release 6.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.80. Release 6.1
    
+E.85. Release 6.1
    
 
    
 
    Release date
    
 
    1997-06-08
    
@@ -49,7 +49,7 @@ 
    Release date
    
   machine (Linux/gcc/i686).
    
 
    
 
    
-E.80.1. Migration to version 6.1
    
+E.85.1. Migration to version 6.1
    
 
    This migration requires a complete dump of the 6.0 database and a
 restore of the database in 6.1.
    
 
    Those migrating from earlier 1.* releases should first upgrade to 1.09
@@ -57,7 +57,7 @@ 
    Release date
    
 
 
    
 
    
-E.80.2. Changes
    
+E.85.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-6-2-1.html b/docs/en_US/pg/release-6-2-1.html
index 01525fc43e..18888e6bb1 100644
--- a/docs/en_US/pg/release-6-2-1.html
+++ b/docs/en_US/pg/release-6-2-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.77. Release 6.2.1
+E.82. Release 6.2.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.77. Release 6.2.1
    
+E.82. Release 6.2.1
    
 
    
 
    Release date
    
 
    1997-10-17
    
@@ -31,7 +31,7 @@ 
    Release date
    
 Refer to the 6.2 release notes for instructions.
    
 
    
 
    
-E.77.1. Migration from version 6.2 to version 6.2.1
    
+E.82.1. Migration from version 6.2 to version 6.2.1
    
 
    This is a minor bug-fix release. A dump/reload is not required from version 6.2,
 but is required from any release prior to 6.2.
    
 
    In upgrading from version 6.2, if you choose to dump/reload you will find that
@@ -47,7 +47,7 @@ 
    Release date
    
 
 
    
 
    
-E.77.2. Changes
    
+E.82.2. Changes
    
 
         
    
 
    Allow TIME and TYPE column names(Thomas)
 Allow larger range of true/false as boolean values(Thomas)
diff --git a/docs/en_US/pg/release-6-2.html b/docs/en_US/pg/release-6-2.html
index 82fb9804ab..c0bff60219 100644
--- a/docs/en_US/pg/release-6-2.html
+++ b/docs/en_US/pg/release-6-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.78. Release 6.2
+E.83. Release 6.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.78. Release 6.2
    
+E.83. Release 6.2
    
 
    
 
    Release date
    
 
    1997-10-02
    
@@ -22,7 +22,7 @@ 
    Release date
    
 previous releases of PostgreSQL.
    
 
    
 
    
-E.78.1. Migration from version 6.1 to version 6.2
    
+E.83.1. Migration from version 6.1 to version 6.2
    
 
    This migration requires a complete dump of the 6.1 database and a
 restore of the database in 6.2.
    
 
    Note that the pg_dump and pg_dumpall utility from 6.2 should be used
@@ -30,13 +30,13 @@ 
    Release date
    
 
 
    
 
    
-E.78.2. Migration from version 1.x to version 6.2
    
+E.83.2. Migration from version 1.x to version 6.2
    
 
    Those migrating from earlier 1.* releases should first upgrade to 1.09
 because the COPY output format was improved from the 1.02 release.
    
 
 
    
 
    
-E.78.3. Changes
    
+E.83.3. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-6-3-1.html b/docs/en_US/pg/release-6-3-1.html
index ce8547088f..86ed2ab885 100644
--- a/docs/en_US/pg/release-6-3-1.html
+++ b/docs/en_US/pg/release-6-3-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.75. Release 6.3.1
+E.80. Release 6.3.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.75. Release 6.3.1
    
+E.80. Release 6.3.1
    
 
    
 
    Release date
    
 
    1998-03-23
    
@@ -35,7 +35,7 @@ 
    Release date
    
 refer to the installation and migration instructions for version 6.3.
    
 
    
 
    
-E.75.1. Changes
    
+E.80.1. Changes
    
 
         
    
 
    ecpg cleanup/fixes, now version 1.1(Michael Meskes)
 pg_user cleanup(Bruce)
diff --git a/docs/en_US/pg/release-6-3-2.html b/docs/en_US/pg/release-6-3-2.html
index e93cb50be6..c7050fd1eb 100644
--- a/docs/en_US/pg/release-6-3-2.html
+++ b/docs/en_US/pg/release-6-3-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.74. Release 6.3.2
+E.79. Release 6.3.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.74. Release 6.3.2
    
+E.79. Release 6.3.2
    
 
    
 
    Release date
    
 
    1998-04-07
    
@@ -36,7 +36,7 @@ 
    Release date
    
 refer to the installation and migration instructions for version 6.3.
    
 
    
 
    
-E.74.1. Changes
    
+E.79.1. Changes
    
 
         
    
 
    Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
 Manual page improvements(Bruce)
diff --git a/docs/en_US/pg/release-6-3.html b/docs/en_US/pg/release-6-3.html
index 9a8506f991..00724ec83b 100644
--- a/docs/en_US/pg/release-6-3.html
+++ b/docs/en_US/pg/release-6-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.76. Release 6.3
+E.81. Release 6.3
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.76. Release 6.3
    
+E.81. Release 6.3
    
 
    
 
    Release date
    
 
    1998-03-01
    
@@ -108,7 +108,7 @@ 
    Note
    
    
    
 
    
 
    
-E.76.1. Migration to version 6.3
    
+E.81.1. Migration to version 6.3
    
 
         A dump/restore using pg_dump 
      or pg_dumpall
      is required for those wishing to migrate data from any
@@ -117,7 +117,7 @@ 
    Note
    
 
 
    
 
    
-E.76.2. Changes
    
+E.81.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-6-4-1.html b/docs/en_US/pg/release-6-4-1.html
index 7d49c3b42f..51d859e8a5 100644
--- a/docs/en_US/pg/release-6-4-1.html
+++ b/docs/en_US/pg/release-6-4-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.72. Release 6.4.1
+E.77. Release 6.4.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.72. Release 6.4.1
    
+E.77. Release 6.4.1
    
 
    
 
    Release date
    
 
    1998-12-18
    
@@ -22,13 +22,13 @@ 
    Release date
    
 problems reported by 6.4 users.
    
 
    
 
    
-E.72.1. Migration to version 6.4.1
    
+E.77.1. Migration to version 6.4.1
    
 
    A dump/restore is not required for those running
 6.4.
    
 
 
    
 
    
-E.72.2. Changes
    
+E.77.2. Changes
    
 
    Add pg_dump -N flag to force double quotes around identifiers.  This is
         the default(Thomas)
 Fix for NOT in where clause causing crash(Bruce)
diff --git a/docs/en_US/pg/release-6-4-2.html b/docs/en_US/pg/release-6-4-2.html
index 69f47f972b..8f07ae90b8 100644
--- a/docs/en_US/pg/release-6-4-2.html
+++ b/docs/en_US/pg/release-6-4-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.71. Release 6.4.2
+E.76. Release 6.4.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.71. Release 6.4.2
    
+E.76. Release 6.4.2
    
 
    
 
    Release date
    
 
    1998-12-20
    
@@ -22,13 +22,13 @@ 
    Release date
    
 bug fix.
    
 
    
 
    
-E.71.1. Migration to version 6.4.2
    
+E.76.1. Migration to version 6.4.2
    
 
    A dump/restore is not required for those running
 6.4.*.
    
 
 
    
 
    
-E.71.2. Changes
    
+E.76.2. Changes
    
 
    Fix for datetime constant problem on some platforms(Thomas)
    
 
 
diff --git a/docs/en_US/pg/release-6-4.html b/docs/en_US/pg/release-6-4.html
index 3d1332e98e..f0f3440e84 100644
--- a/docs/en_US/pg/release-6-4.html
+++ b/docs/en_US/pg/release-6-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.73. Release 6.4
+E.78. Release 6.4
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.73. Release 6.4
    
+E.78. Release 6.4
    
 
    
 
    Release date
    
 
    1998-10-30
    
@@ -55,7 +55,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.73.1. Migration to version 6.4
    
+E.78.1. Migration to version 6.4
    
 
    A dump/restore using pg_dump 
 or pg_dumpall
 is required for those wishing to migrate data from any
@@ -63,7 +63,7 @@ 
    Release date
    
 
 
    
 
    
-E.73.2. Changes
    
+E.78.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-6-5-1.html b/docs/en_US/pg/release-6-5-1.html
index 89c4defd02..c1bb979c3a 100644
--- a/docs/en_US/pg/release-6-5-1.html
+++ b/docs/en_US/pg/release-6-5-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.69. Release 6.5.1
+E.74. Release 6.5.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.69. Release 6.5.1
    
+E.74. Release 6.5.1
    
 
    
 
    Release date
    
 
    1999-07-15
    
@@ -23,14 +23,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.69.1. Migration to version 6.5.1
    
+E.74.1. Migration to version 6.5.1
    
 
         A dump/restore is not required for those running
      6.5.
     
    
 
 
    
 
    
-E.69.2. Changes
    
+E.74.2. Changes
    
 
         
    
 
    Add NT README file
 Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
diff --git a/docs/en_US/pg/release-6-5-2.html b/docs/en_US/pg/release-6-5-2.html
index de65f2297b..0aa63f30cf 100644
--- a/docs/en_US/pg/release-6-5-2.html
+++ b/docs/en_US/pg/release-6-5-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.68. Release 6.5.2
+E.73. Release 6.5.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.68. Release 6.5.2
    
+E.73. Release 6.5.2
    
 
    
 
    Release date
    
 
    1999-09-15
    
@@ -23,14 +23,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.68.1. Migration to version 6.5.2
    
+E.73.1. Migration to version 6.5.2
    
 
         A dump/restore is not required for those running
      6.5.*.
     
    
 
 
    
 
    
-E.68.2. Changes
    
+E.73.2. Changes
    
 
         
    
 
    subselect+CASE fixes(Tom)
 Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
diff --git a/docs/en_US/pg/release-6-5-3.html b/docs/en_US/pg/release-6-5-3.html
index 4b5747f90b..fddf3003e7 100644
--- a/docs/en_US/pg/release-6-5-3.html
+++ b/docs/en_US/pg/release-6-5-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.67. Release 6.5.3
+E.72. Release 6.5.3
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.67. Release 6.5.3
    
+E.72. Release 6.5.3
    
 
    
 
    Release date
    
 
    1999-10-13
    
@@ -23,14 +23,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.67.1. Migration to version 6.5.3
    
+E.72.1. Migration to version 6.5.3
    
 
         A dump/restore is not required for those running
      6.5.*.
     
    
 
 
    
 
    
-E.67.2. Changes
    
+E.72.2. Changes
    
 
         
    
 
    Updated version of pgaccess 0.98
 NT-specific patch
diff --git a/docs/en_US/pg/release-6-5.html b/docs/en_US/pg/release-6-5.html
index b8e125d4f8..d00eeef251 100644
--- a/docs/en_US/pg/release-6-5.html
+++ b/docs/en_US/pg/release-6-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.70. Release 6.5
+E.75. Release 6.5
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.70. Release 6.5
    
+E.75. Release 6.5
    
 
    
 
    Release date
    
 
    1999-06-09
    
@@ -105,7 +105,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.70.1. Migration to version 6.5
    
+E.75.1. Migration to version 6.5
    
 
         A dump/restore using pg_dump
      is required for those wishing to migrate data from any
      previous release of PostgreSQL.
@@ -121,7 +121,7 @@ 
    Release date
    
     
    
 
    
 
    
-E.70.1.1. Multiversion Concurrency Control
    
+E.75.1.1. Multiversion Concurrency Control
    
 
          Because readers in 6.5 don't lock data, regardless of transaction
       isolation level, data read by one transaction can be overwritten by
       another. In other words, if a row is returned by
@@ -166,7 +166,7 @@ 
    Note
    
 
 
    
 
    
-E.70.2. Changes
    
+E.75.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-7-0-1.html b/docs/en_US/pg/release-7-0-1.html
index 2825676256..e5210d9d6b 100644
--- a/docs/en_US/pg/release-7-0-1.html
+++ b/docs/en_US/pg/release-7-0-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.65. Release 7.0.1
+E.70. Release 7.0.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.65. Release 7.0.1
    
+E.70. Release 7.0.1
    
 
    
 
    Release date
    
 
    2000-06-01
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.65.1. Migration to version 7.0.1
    
+E.70.1. Migration to version 7.0.1
    
 
         A dump/restore is not required for those running
      7.0.
     
    
 
 
    
 
    
-E.65.2. Changes
    
+E.70.2. Changes
    
 
         
    
 
    Fix many CLUSTER failures (Tom)
 Allow ALTER TABLE RENAME works on indexes (Tom)
diff --git a/docs/en_US/pg/release-7-0-2.html b/docs/en_US/pg/release-7-0-2.html
index 088930b083..b7e969b9b5 100644
--- a/docs/en_US/pg/release-7-0-2.html
+++ b/docs/en_US/pg/release-7-0-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.64. Release 7.0.2
+E.69. Release 7.0.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.64. Release 7.0.2
    
+E.69. Release 7.0.2
    
 
    
 
    Release date
    
 
    2000-06-05
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.64.1. Migration to version 7.0.2
    
+E.69.1. Migration to version 7.0.2
    
 
         A dump/restore is not required for those running
      7.*.
     
    
 
 
    
 
    
-E.64.2. Changes
    
+E.69.2. Changes
    
 
         
    
 
    Added documentation to tarball.
      
    
diff --git a/docs/en_US/pg/release-7-0-3.html b/docs/en_US/pg/release-7-0-3.html
index 646e74ca86..9aa9b83b9a 100644
--- a/docs/en_US/pg/release-7-0-3.html
+++ b/docs/en_US/pg/release-7-0-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.63. Release 7.0.3
+E.68. Release 7.0.3
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.63. Release 7.0.3
    
+E.68. Release 7.0.3
    
 
    
 
    Release date
    
 
    2000-11-11
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.63.1. Migration to version 7.0.3
    
+E.68.1. Migration to version 7.0.3
    
 
         A dump/restore is not required for those running
      7.0.*.
     
    
 
 
    
 
    
-E.63.2. Changes
    
+E.68.2. Changes
    
 
         
    
 
    Jdbc fixes (Peter)
 Large object fix (Tom)
diff --git a/docs/en_US/pg/release-7-0.html b/docs/en_US/pg/release-7-0.html
index b2ecac99a5..6b0974b28b 100644
--- a/docs/en_US/pg/release-7-0.html
+++ b/docs/en_US/pg/release-7-0.html
@@ -1,19 +1,19 @@
 
 
 
-E.66. Release 7.0
+E.71. Release 7.0
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.66. Release 7.0
    
+E.71. Release 7.0
    
 
    
 
    Release date
    
 
    2000-05-08
    
@@ -57,7 +57,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.66.1. Migration to version 7.0
    
+E.71.1. Migration to version 7.0
    
 
         A dump/restore using pg_dump
      is required for those wishing to migrate data from any
      previous release of PostgreSQL.
@@ -102,7 +102,7 @@ 
    Release date
    
 
 
    
 
    
-E.66.2. Changes
    
+E.71.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-7-1-1.html b/docs/en_US/pg/release-7-1-1.html
index dea5a40e61..a29430987e 100644
--- a/docs/en_US/pg/release-7-1-1.html
+++ b/docs/en_US/pg/release-7-1-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.61. Release 7.1.1
+E.66. Release 7.1.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.61. Release 7.1.1
    
+E.66. Release 7.1.1
    
 
    
 
    Release date
    
 
    2001-05-05
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.61.1. Migration to version 7.1.1
    
+E.66.1. Migration to version 7.1.1
    
 
         A dump/restore is not required for those running
      7.1.
     
    
 
 
    
 
    
-E.61.2. Changes
    
+E.66.2. Changes
    
 
         
    
 
    Fix for numeric MODULO operator (Tom)
 pg_dump fixes (Philip)
diff --git a/docs/en_US/pg/release-7-1-2.html b/docs/en_US/pg/release-7-1-2.html
index d57d5b59d3..e752a5e28f 100644
--- a/docs/en_US/pg/release-7-1-2.html
+++ b/docs/en_US/pg/release-7-1-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.60. Release 7.1.2
+E.65. Release 7.1.2
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.60. Release 7.1.2
    
+E.65. Release 7.1.2
    
 
    
 
    Release date
    
 
    2001-05-11
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.60.1. Migration to version 7.1.2
    
+E.65.1. Migration to version 7.1.2
    
 
         A dump/restore is not required for those running
      7.1.X.
     
    
 
 
    
 
    
-E.60.2. Changes
    
+E.65.2. Changes
    
 
         
    
 
    Fix PL/pgSQL SELECTs when returning no rows
 Fix for psql backslash core dump
diff --git a/docs/en_US/pg/release-7-1-3.html b/docs/en_US/pg/release-7-1-3.html
index b57c162c3d..76c125dc56 100644
--- a/docs/en_US/pg/release-7-1-3.html
+++ b/docs/en_US/pg/release-7-1-3.html
@@ -1,33 +1,33 @@
 
 
 
-E.59. Release 7.1.3
+E.64. Release 7.1.3
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.59. Release 7.1.3
    
+E.64. Release 7.1.3
    
 
    
 
    Release date
    
 
    2001-08-15
    
 
    
 
    
 
    
-E.59.1. Migration to version 7.1.3
    
+E.64.1. Migration to version 7.1.3
    
 
         A dump/restore is not required for those running
      7.1.X.
     
    
 
 
    
 
    
-E.59.2. Changes
    
+E.64.2. Changes
    
 
         
    
 
    Remove unused WAL segments of large transactions (Tom)
 Multiaction rule fix (Tom)
diff --git a/docs/en_US/pg/release-7-1.html b/docs/en_US/pg/release-7-1.html
index 54d120211c..87a63ccae5 100644
--- a/docs/en_US/pg/release-7-1.html
+++ b/docs/en_US/pg/release-7-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.62. Release 7.1
+E.67. Release 7.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.62. Release 7.1
    
+E.67. Release 7.1
    
 
    
 
    Release date
    
 
    2001-04-13
    
@@ -65,14 +65,14 @@ 
    Release date
    
 
    
 
    
 
    
-E.62.1. Migration to version 7.1
    
+E.67.1. Migration to version 7.1
    
 
            A dump/restore using pg_dump is required for those wishing to migrate
         data from any previous release.
     
    
 
 
    
 
    
-E.62.2. Changes
    
+E.67.2. Changes
    
 
         
    
 
    Bug Fixes
 ---------
diff --git a/docs/en_US/pg/release-7-2-1.html b/docs/en_US/pg/release-7-2-1.html
index 1b28242a1c..837694dd74 100644
--- a/docs/en_US/pg/release-7-2-1.html
+++ b/docs/en_US/pg/release-7-2-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.57. Release 7.2.1
+E.62. Release 7.2.1
 
 
 
-
+
 
-
-
+
+
 
 
 
    
 
    
-E.57. Release 7.2.1
    
+E.62. Release 7.2.1
    
 
    
 
    Release date
    
 
    2002-03-21
    
@@ -22,14 +22,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.57.1. Migration to version 7.2.1
    
+E.62.1. Migration to version 7.2.1
    
 
        A dump/restore is not required for those
     running version 7.2.
    
    
 
 
    
 
    
-E.57.2. Changes
    
+E.62.2. Changes
    
 
      
 
    • Ensure that sequence counters do not go backwards after a crash (Tom)
      • 
 
    • Fix pgaccess kanji-conversion key binding (Tatsuo)
      • 
diff --git a/docs/en_US/pg/release-7-2-2.html b/docs/en_US/pg/release-7-2-2.html
index 8fe84087d0..ff14813832 100644
--- a/docs/en_US/pg/release-7-2-2.html
+++ b/docs/en_US/pg/release-7-2-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.56. Release 7.2.2
+E.61. Release 7.2.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.56. Release 7.2.2
      
+E.61. Release 7.2.2
    
 
    
 
    Release date
    
 
    2002-08-23
    
@@ -22,14 +22,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.56.1. Migration to version 7.2.2
    
+E.61.1. Migration to version 7.2.2
    
 
        A dump/restore is not required for those
     running version 7.2.*.
    
    
 
 
    
 
    
-E.56.2. Changes
    
+E.61.2. Changes
    
 
      
 
    • Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
      • 
 
    • Fix for compressed transaction log id wraparound (Tom)
      • 
diff --git a/docs/en_US/pg/release-7-2-3.html b/docs/en_US/pg/release-7-2-3.html
index f21a002963..4c37c031bc 100644
--- a/docs/en_US/pg/release-7-2-3.html
+++ b/docs/en_US/pg/release-7-2-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.55. Release 7.2.3
+E.60. Release 7.2.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.55. Release 7.2.3
      
+E.60. Release 7.2.3
    
 
    
 
    Release date
    
 
    2002-10-01
    
@@ -23,14 +23,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.55.1. Migration to version 7.2.3
    
+E.60.1. Migration to version 7.2.3
    
 
        A dump/restore is not required for those
     running version 7.2.*.
    
    
 
 
    
 
    
-E.55.2. Changes
    
+E.60.2. Changes
    
 
      
 
    • Prevent possible compressed transaction log loss (Tom)
      • 
 
    • Prevent non-superuser from increasing most recent vacuum info (Tom)
      • 
diff --git a/docs/en_US/pg/release-7-2-4.html b/docs/en_US/pg/release-7-2-4.html
index ebbee54130..57ead1bd36 100644
--- a/docs/en_US/pg/release-7-2-4.html
+++ b/docs/en_US/pg/release-7-2-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.54. Release 7.2.4
+E.59. Release 7.2.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.54. Release 7.2.4
      
+E.59. Release 7.2.4
    
 
    
 
    Release date
    
 
    2003-01-30
    
@@ -23,14 +23,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.54.1. Migration to version 7.2.4
    
+E.59.1. Migration to version 7.2.4
    
 
        A dump/restore is not required for those
     running version 7.2.*.
    
    
 
 
    
 
    
-E.54.2. Changes
    
+E.59.2. Changes
    
 
      
 
    • Fix some additional cases of VACUUM "No one parent tuple was found" error
      • 
 
    • Prevent VACUUM from being called inside a function  (Bruce)
      • 
diff --git a/docs/en_US/pg/release-7-2-5.html b/docs/en_US/pg/release-7-2-5.html
index 3a6fa9d585..8fd69e3918 100644
--- a/docs/en_US/pg/release-7-2-5.html
+++ b/docs/en_US/pg/release-7-2-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.53. Release 7.2.5
+E.58. Release 7.2.5
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.53. Release 7.2.5
      
+E.58. Release 7.2.5
    
 
    
 
    Release date
    
 
    2004-08-16
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.53.1. Migration to version 7.2.5
    
+E.58.1. Migration to version 7.2.5
    
 
         A dump/restore is not required for those running 7.2.X.
     
    
 
 
    
 
    
-E.53.2. Changes
    
+E.58.2. Changes
    
 
      
 
    • 
 
      Prevent possible loss of committed transactions during crash
      
diff --git a/docs/en_US/pg/release-7-2-6.html b/docs/en_US/pg/release-7-2-6.html
index 83d2402484..88c6d581d6 100644
--- a/docs/en_US/pg/release-7-2-6.html
+++ b/docs/en_US/pg/release-7-2-6.html
@@ -1,19 +1,19 @@
 
 
 
-E.52. Release 7.2.6
+E.57. Release 7.2.6
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.52. Release 7.2.6
      
+E.57. Release 7.2.6
    
 
    
 
    Release date
    
 
    2004-10-22
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.52.1. Migration to version 7.2.6
    
+E.57.1. Migration to version 7.2.6
    
 
         A dump/restore is not required for those running 7.2.X.
     
    
 
 
    
 
    
-E.52.2. Changes
    
+E.57.2. Changes
    
 
      
 
    • 
 
      Repair possible failure to update hint bits on disk
      
diff --git a/docs/en_US/pg/release-7-2-7.html b/docs/en_US/pg/release-7-2-7.html
index f5a9b51278..ee6c117f90 100644
--- a/docs/en_US/pg/release-7-2-7.html
+++ b/docs/en_US/pg/release-7-2-7.html
@@ -1,19 +1,19 @@
 
 
 
-E.51. Release 7.2.7
+E.56. Release 7.2.7
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.51. Release 7.2.7
      
+E.56. Release 7.2.7
    
 
    
 
    Release date
    
 
    2005-01-31
    
@@ -23,13 +23,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.51.1. Migration to version 7.2.7
    
+E.56.1. Migration to version 7.2.7
    
 
         A dump/restore is not required for those running 7.2.X.
     
    
 
 
    
 
    
-E.51.2. Changes
    
+E.56.2. Changes
    
 
      
 
    • 
 
      Disallow LOAD to non-superusers
      
diff --git a/docs/en_US/pg/release-7-2-8.html b/docs/en_US/pg/release-7-2-8.html
index c72d12f08c..1d403c45d2 100644
--- a/docs/en_US/pg/release-7-2-8.html
+++ b/docs/en_US/pg/release-7-2-8.html
@@ -1,19 +1,19 @@
 
 
 
-E.50. Release 7.2.8
+E.55. Release 7.2.8
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.50. Release 7.2.8
      
+E.55. Release 7.2.8
    
 
    
 
    Release date
    
 
    2005-05-09
    
@@ -23,13 +23,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.50.1. Migration to version 7.2.8
    
+E.55.1. Migration to version 7.2.8
    
 
         A dump/restore is not required for those running 7.2.X.
     
    
 
 
    
 
    
-E.50.2. Changes
    
+E.55.2. Changes
    
 
      
 
    • 
 
      Repair ancient race condition that allowed a transaction to be
diff --git a/docs/en_US/pg/release-7-2.html b/docs/en_US/pg/release-7-2.html
index 8f4358a5eb..fd9835b450 100644
--- a/docs/en_US/pg/release-7-2.html
+++ b/docs/en_US/pg/release-7-2.html
@@ -1,26 +1,26 @@
 
 
 
-E.58. Release 7.2
+E.63. Release 7.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.58. Release 7.2
      
+E.63. Release 7.2
    
 
    
 
    Release date
    
 
    2002-02-04
    
 
    
 
    
 
    
-E.58.1. Overview
    
+E.63.1. Overview
    
 
        This release improves PostgreSQL for use in
     high-volume applications.
    
    
@@ -62,7 +62,7 @@ 
    Release date
    
 
 
    
 
    
-E.58.2. Migration to version 7.2
    
+E.63.2. Migration to version 7.2
    
 
        A dump/restore using pg_dump is required for
     those wishing to migrate data from any previous release.
    
    
@@ -102,10 +102,10 @@ 
    Release date
    
 
 
    
 
    
-E.58.3. Changes
    
+E.63.3. Changes
    
 
    
 
    
-E.58.3.1. Server Operation
    
+E.63.3.1. Server Operation
    
 
      
 
    • Create temporary files in a separate directory (Bruce)
      • 
 
    • Delete orphaned temporary files on postmaster startup (Bruce)
      • 
@@ -131,7 +131,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.2. Performance
    
+E.63.3.2. Performance
    
 
      
 
    • Optimizer improvements (Tom)
      • 
 
    • New histogram column statistics for optimizer (Tom)
      • 
@@ -147,7 +147,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.3. Privileges
    
+E.63.3.3. Privileges
    
 
      
 
    • Change UPDATE, DELETE privileges to be distinct (Peter E)
      • 
 
    • New REFERENCES, TRIGGER privileges (Peter E)
      • 
@@ -161,7 +161,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.4. Client Authentication
    
+E.63.3.4. Client Authentication
    
 
      
 
    • Fork postmaster before doing authentication to prevent hangs (Peter E)
      • 
 
    • Add ident authentication over Unix domain sockets on Linux, *BSD (Helge Bahmann, Oliver Elphick, Teodor Sigaev, Bruce)
      • 
@@ -173,7 +173,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.5. Server Configuration
    
+E.63.3.5. Server Configuration
    
 
      
 
    • Interpretation of some time zone abbreviations as Australian rather than North American now settable at run time (Bruce)
      • 
 
    • New parameter to set default transaction isolation level (Peter E)
      • 
@@ -185,7 +185,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.6. Queries
    
+E.63.3.6. Queries
    
 
      
 
    • Statements added by INSERT rules now execute after the INSERT (Jan)
      • 
 
    • Prevent unadorned relation names in target list (Bruce)
      • 
@@ -200,7 +200,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.7. Schema Manipulation
    
+E.63.3.7. Schema Manipulation
    
 
      
 
    • Fix SERIAL in temporary tables (Bruce)
      • 
 
    • Allow temporary sequences (Bruce)
      • 
@@ -223,7 +223,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.8. Utility Commands
    
+E.63.3.8. Utility Commands
    
 
      
 
    • Add RESET ALL, SHOW ALL (Marko Kreen)
      • 
 
    • CREATE/ALTER USER/GROUP now allow options in any order (Vince)
      • 
@@ -239,7 +239,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.9. Data Types and Functions
    
+E.63.3.9. Data Types and Functions
    
 
      
 
    • SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom)
      • 
 
    • Add convert(), convert2() (Tatsuo)
      • 
@@ -282,7 +282,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.10. Internationalization
    
+E.63.3.10. Internationalization
    
 
      
 
    • National language support in psql, pg_dump, libpq, and server (Peter E)
      • 
 
    • Message translations in Chinese (simplified, traditional), Czech, French, German, Hungarian, Russian, Swedish (Peter E, Serguei A. Mokhov, Karel Zak, Weiping He, Zhenbang Wei, Kovacs Zoltan)
      • 
@@ -296,7 +296,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.11. PL/pgSQL
    
+E.63.3.11. PL/pgSQL
    
 
      
 
    • Now uses portals for SELECT loops, allowing huge result sets (Jan)
      • 
 
    • CURSOR and REFCURSOR support (Jan)
      • 
@@ -313,7 +313,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.12. PL/Perl
    
+E.63.3.12. PL/Perl
    
 
      
 
    • New untrusted PL/Perl (Alex Pilosov)
      • 
 
    • PL/Perl is now built on some platforms even if libperl is not shared (Peter E)
      • 
@@ -321,7 +321,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.13. PL/Tcl
    
+E.63.3.13. PL/Tcl
    
 
      
 
    • Now reports errorInfo (Vsevolod Lobko)
      • 
 
    • Add spi_lastoid function (bob@redivi.com)
      • 
@@ -329,12 +329,12 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.14. PL/Python
    
+E.63.3.14. PL/Python
    
 
    • ...is new (Andrew Bosma)
    
 
 
    
 
    
-E.58.3.15. psql
    
+E.63.3.15. psql
    
 
      
 
    • \d displays indexes in unique, primary groupings (Christopher Kings-Lynne)
      • 
 
    • Allow trailing semicolons in backslash commands (Greg Sabino Mullane)
      • 
@@ -345,7 +345,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.16. libpq
    
+E.63.3.16. libpq
    
 
      
 
    • New function PQescapeString() to escape quotes in command strings (Florian Weimer)
      • 
 
    • New function PQescapeBytea() escapes binary strings for use as SQL string literals
      • 
@@ -353,7 +353,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.17. JDBC
    
+E.63.3.17. JDBC
    
 
      
 
    • Return OID of INSERT (Ken K)
      • 
 
    • Handle more data types (Ken K)
      • 
@@ -391,7 +391,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.18. ODBC
    
+E.63.3.18. ODBC
    
 
      
 
    • Remove query size limit (Hiroshi)
      • 
 
    • Remove text field size limit (Hiroshi)
      • 
@@ -407,7 +407,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.19. ECPG
    
+E.63.3.19. ECPG
    
 
      
 
    • EXECUTE ... INTO implemented (Christof Petig)
      • 
 
    • Multiple row descriptor support (e.g. CARDINALITY) (Christof Petig)
      • 
@@ -423,7 +423,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.20. Misc. Interfaces
    
+E.63.3.20. Misc. Interfaces
    
 
      
 
    • Python fix fetchone() (Gerhard Haring)
      • 
 
    • Use UTF, Unicode in Tcl where appropriate (Vsevolod Lobko, Reinhard Max)
      • 
@@ -434,7 +434,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.21. Build and Install
    
+E.63.3.21. Build and Install
    
 
      
 
    • Configure, dynamic loader, and shared library fixes (Peter E)
      • 
 
    • Fixes in QNX 4 port (Bernd Tegge)
      • 
@@ -452,7 +452,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.22. Source Code
    
+E.63.3.22. Source Code
    
 
      
 
    • Remove SEP_CHAR (Bruce)
      • 
 
    • New GUC hooks (Tom)
      • 
@@ -469,7 +469,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.58.3.23. Contrib
    
+E.63.3.23. Contrib
    
 
      
 
    • New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev)
      • 
 
    • New contrib/tsearch full-text indexing (Oleg, Teodor Sigaev)
      • 
diff --git a/docs/en_US/pg/release-7-3-1.html b/docs/en_US/pg/release-7-3-1.html
index 22d0a2de26..ea97a5a7e2 100644
--- a/docs/en_US/pg/release-7-3-1.html
+++ b/docs/en_US/pg/release-7-3-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.48. Release 7.3.1
+E.53. Release 7.3.1
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.48. Release 7.3.1
      
+E.53. Release 7.3.1
    
 
    
 
    Release date
    
 
    2002-12-18
    
@@ -22,7 +22,7 @@ 
    Release date
    
   
    
 
    
 
    
-E.48.1. Migration to version 7.3.1
    
+E.53.1. Migration to version 7.3.1
    
 
        A dump/restore is not required for those
     running version 7.3. However, it should be noted that the main
     PostgreSQL interface library, libpq,
@@ -32,7 +32,7 @@ 
    Release date
    
 
 
    
 
    
-E.48.2. Changes
    
+E.53.2. Changes
    
 
      
 
    • Fix a core dump of COPY TO when client/server encodings don't match (Tom)
      • 
 
    • Allow pg_dump to work with pre-7.2 servers (Philip)
      • 
diff --git a/docs/en_US/pg/release-7-3-10.html b/docs/en_US/pg/release-7-3-10.html
index 7d3478e3f0..ea9f9c5658 100644
--- a/docs/en_US/pg/release-7-3-10.html
+++ b/docs/en_US/pg/release-7-3-10.html
@@ -1,19 +1,19 @@
 
 
 
-E.39. Release 7.3.10
+E.44. Release 7.3.10
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.39. Release 7.3.10
      
+E.44. Release 7.3.10
    
 
    
 
    Release date
    
 
    2005-05-09
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.39.1. Migration to version 7.3.10
    
+E.44.1. Migration to version 7.3.10
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      it is one possible way of handling a significant security problem
      that has been found in the initial contents of 7.3.X system
@@ -78,7 +78,7 @@ 
    Release date
    
 
 
    
 
    
-E.39.2. Changes
    
+E.44.2. Changes
    
 
      
 
    • Change encoding function signature to prevent
 misuse
      • 
diff --git a/docs/en_US/pg/release-7-3-11.html b/docs/en_US/pg/release-7-3-11.html
index b96cb22f95..bfb29b2e71 100644
--- a/docs/en_US/pg/release-7-3-11.html
+++ b/docs/en_US/pg/release-7-3-11.html
@@ -1,19 +1,19 @@
 
 
 
-E.38. Release 7.3.11
+E.43. Release 7.3.11
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.38. Release 7.3.11
      
+E.43. Release 7.3.11
    
 
    
 
    Release date
    
 
    2005-10-04
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.38.1. Migration to version 7.3.11
    
+E.43.1. Migration to version 7.3.11
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.10, see the release
      notes for 7.3.10.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.38.2. Changes
    
+E.43.2. Changes
    
 
      
 
    • 
 
      Fix error that allowed VACUUM to remove
diff --git a/docs/en_US/pg/release-7-3-12.html b/docs/en_US/pg/release-7-3-12.html
index 858756e5b7..b2ff1cd073 100644
--- a/docs/en_US/pg/release-7-3-12.html
+++ b/docs/en_US/pg/release-7-3-12.html
@@ -1,19 +1,19 @@
 
 
 
-E.37. Release 7.3.12
+E.42. Release 7.3.12
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.37. Release 7.3.12
      
+E.42. Release 7.3.12
    
 
    
 
    Release date
    
 
    2005-12-12
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.37.1. Migration to version 7.3.12
    
+E.42.1. Migration to version 7.3.12
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.10, see the release
      notes for 7.3.10.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.37.2. Changes
    
+E.42.2. Changes
    
 
      
 
    • 
 
      Fix race condition in transaction log management
      
diff --git a/docs/en_US/pg/release-7-3-13.html b/docs/en_US/pg/release-7-3-13.html
index 8a500f56ec..6c13423bc0 100644
--- a/docs/en_US/pg/release-7-3-13.html
+++ b/docs/en_US/pg/release-7-3-13.html
@@ -1,19 +1,19 @@
 
 
 
-E.36. Release 7.3.13
+E.41. Release 7.3.13
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.36. Release 7.3.13
      
+E.41. Release 7.3.13
    
 
    
 
    Release date
    
 
    2006-01-09
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.36.1. Migration to version 7.3.13
    
+E.41.1. Migration to version 7.3.13
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.10, see the release
      notes for 7.3.10.
@@ -33,7 +33,7 @@ 
    Release date
    
 
 
    
 
    
-E.36.2. Changes
    
+E.41.2. Changes
    
 
      
 
    • 
 
      Fix character string comparison for locales that consider
diff --git a/docs/en_US/pg/release-7-3-14.html b/docs/en_US/pg/release-7-3-14.html
index 2b48eac765..a18e63a4dc 100644
--- a/docs/en_US/pg/release-7-3-14.html
+++ b/docs/en_US/pg/release-7-3-14.html
@@ -1,19 +1,19 @@
 
 
 
-E.35. Release 7.3.14
+E.40. Release 7.3.14
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.35. Release 7.3.14
      
+E.40. Release 7.3.14
    
 
    
 
    Release date
    
 
    2006-02-14
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.35.1. Migration to version 7.3.14
    
+E.40.1. Migration to version 7.3.14
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.13, see the release
      notes for 7.3.13.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.35.2. Changes
    
+E.40.2. Changes
    
 
      
 
    • 
 
      Fix potential crash in SET
diff --git a/docs/en_US/pg/release-7-3-15.html b/docs/en_US/pg/release-7-3-15.html
index 05f897b526..8a9efe5358 100644
--- a/docs/en_US/pg/release-7-3-15.html
+++ b/docs/en_US/pg/release-7-3-15.html
@@ -1,19 +1,19 @@
 
 
 
-E.34. Release 7.3.15
+E.39. Release 7.3.15
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.34. Release 7.3.15
      
+E.39. Release 7.3.15
    
 
    
 
    Release date
    
 
    2006-05-23
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.34.1. Migration to version 7.3.15
    
+E.39.1. Migration to version 7.3.15
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.13, see the release
      notes for 7.3.13.
@@ -41,7 +41,7 @@ 
    Release date
    
 
 
    
 
    
-E.34.2. Changes
    
+E.39.2. Changes
    
 
      
 
    • 
 
      Change the server to reject invalidly-encoded multibyte
diff --git a/docs/en_US/pg/release-7-3-16.html b/docs/en_US/pg/release-7-3-16.html
index 0f6dc57882..987368d714 100644
--- a/docs/en_US/pg/release-7-3-16.html
+++ b/docs/en_US/pg/release-7-3-16.html
@@ -1,19 +1,19 @@
 
 
 
-E.33. Release 7.3.16
+E.38. Release 7.3.16
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.33. Release 7.3.16
      
+E.38. Release 7.3.16
    
 
    
 
    Release date
    
 
    2006-10-16
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.33.1. Migration to version 7.3.16
    
+E.38.1. Migration to version 7.3.16
    
 
         A dump/restore is not required for those running 7.3.X.  However,
      if you are upgrading from a version earlier than 7.3.13, see the release
      notes for 7.3.13.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.33.2. Changes
    
+E.38.2. Changes
    
 
      
 
    • Fix corner cases in pattern matching for
   psql's \d commands
      • 
diff --git a/docs/en_US/pg/release-7-3-17.html b/docs/en_US/pg/release-7-3-17.html
new file mode 100644
index 0000000000..9f95726055
--- /dev/null
+++ b/docs/en_US/pg/release-7-3-17.html
@@ -0,0 +1,54 @@
+
+
+
+E.37. Release 7.3.17
+
+
+
+
+
+
+
+
+
+
      
+
      
+E.37. Release 7.3.17
      
+
      
+
      Release date
      
+
      2007-01-08
      
+
      
+
          This release contains a variety of fixes from 7.3.16.
+   
      
+
      
+
      
+E.37.1. Migration to version 7.3.17
      
+
           A dump/restore is not required for those running 7.3.X.  However,
+     if you are upgrading from a version earlier than 7.3.13, see the release
+     notes for 7.3.13.
+    
      
+
      
+
      
+
      
+E.37.2. Changes
      
+
        
+
      • 
+
               to_number() and to_char(numeric)
+       are now STABLE, not IMMUTABLE, for
+       new initdb
+       installs (Tom)
+      
        
+
               This is because lc_numeric can potentially
+       change the output of these functions.
+      
        
+
        • 
+
      • 
+
               Improve index usage of regular expressions that use parentheses (Tom)
+      
        
+
               This improves psql \d performance also.
+      
        
+
        • 
+
      
+
      
+
      
+
diff --git a/docs/en_US/pg/release-7-3-2.html b/docs/en_US/pg/release-7-3-2.html
index f4ee90e00a..8261882787 100644
--- a/docs/en_US/pg/release-7-3-2.html
+++ b/docs/en_US/pg/release-7-3-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.47. Release 7.3.2
+E.52. Release 7.3.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.47. Release 7.3.2
      
+E.52. Release 7.3.2
    
 
    
 
    Release date
    
 
    2003-02-04
    
@@ -22,14 +22,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.47.1. Migration to version 7.3.2
    
+E.52.1. Migration to version 7.3.2
    
 
        A dump/restore is not required for those
     running version 7.3.*.
    
    
 
 
    
 
    
-E.47.2. Changes
    
+E.52.2. Changes
    
 
      
 
    • Restore creation of OID column in CREATE TABLE AS / SELECT INTO
      • 
 
    • Fix pg_dump core dump when dumping views having comments
      • 
diff --git a/docs/en_US/pg/release-7-3-3.html b/docs/en_US/pg/release-7-3-3.html
index e511e240dc..9d885537f3 100644
--- a/docs/en_US/pg/release-7-3-3.html
+++ b/docs/en_US/pg/release-7-3-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.46. Release 7.3.3
+E.51. Release 7.3.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.46. Release 7.3.3
      
+E.51. Release 7.3.3
    
 
    
 
    Release date
    
 
    2003-05-22
    
@@ -22,14 +22,14 @@ 
    Release date
    
   
    
 
    
 
    
-E.46.1. Migration to version 7.3.3
    
+E.51.1. Migration to version 7.3.3
    
 
        A dump/restore is not required for those
     running version 7.3.*.
    
    
 
 
    
 
    
-E.46.2. Changes
    
+E.51.2. Changes
    
 
      
 
    • Repair sometimes-incorrect computation of StartUpID after a crash
      • 
 
    • Avoid slowness with lots of deferred triggers in one transaction (Stephan)
      • 
diff --git a/docs/en_US/pg/release-7-3-4.html b/docs/en_US/pg/release-7-3-4.html
index b5ca5988d7..5a4012f305 100644
--- a/docs/en_US/pg/release-7-3-4.html
+++ b/docs/en_US/pg/release-7-3-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.45. Release 7.3.4
+E.50. Release 7.3.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.45. Release 7.3.4
      
+E.50. Release 7.3.4
    
 
    
 
    Release date
    
 
    2003-07-24
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.45.1. Migration to version 7.3.4
    
+E.50.1. Migration to version 7.3.4
    
 
         A dump/restore is not required for those
      running 7.3.*.
     
    
 
 
    
 
    
-E.45.2. Changes
    
+E.50.2. Changes
    
 
      
 
    • Repair breakage in timestamp-to-date conversion for dates before 2000
      • 
 
    • Prevent rare possibility of server startup failure (Tom)
      • 
diff --git a/docs/en_US/pg/release-7-3-5.html b/docs/en_US/pg/release-7-3-5.html
index 2362c2b293..0632f86e02 100644
--- a/docs/en_US/pg/release-7-3-5.html
+++ b/docs/en_US/pg/release-7-3-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.44. Release 7.3.5
+E.49. Release 7.3.5
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.44. Release 7.3.5
      
+E.49. Release 7.3.5
    
 
    
 
    Release date
    
 
    2003-12-03
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.44.1. Migration to version 7.3.5
    
+E.49.1. Migration to version 7.3.5
    
 
         A dump/restore is not required for those
      running 7.3.*.
     
    
 
 
    
 
    
-E.44.2. Changes
    
+E.49.2. Changes
    
 
      
 
    • Force zero_damaged_pages to be on during recovery from WAL
      • 
 
    • Prevent some obscure cases of “variable not in subplan target lists”
      • 
diff --git a/docs/en_US/pg/release-7-3-6.html b/docs/en_US/pg/release-7-3-6.html
index 9da902aa96..837f4f28e7 100644
--- a/docs/en_US/pg/release-7-3-6.html
+++ b/docs/en_US/pg/release-7-3-6.html
@@ -1,19 +1,19 @@
 
 
 
-E.43. Release 7.3.6
+E.48. Release 7.3.6
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.43. Release 7.3.6
      
+E.48. Release 7.3.6
    
 
    
 
    Release date
    
 
    2004-03-02
    
@@ -22,14 +22,14 @@ 
    Release date
    
    
    
 
    
 
    
-E.43.1. Migration to version 7.3.6
    
+E.48.1. Migration to version 7.3.6
    
 
         A dump/restore is not required for those
      running 7.3.*.
     
    
 
 
    
 
    
-E.43.2. Changes
    
+E.48.2. Changes
    
 
      
 
    • 
 
      Revert erroneous changes in rule permissions checking
      
diff --git a/docs/en_US/pg/release-7-3-7.html b/docs/en_US/pg/release-7-3-7.html
index 8db8a4db94..6249e7a3a0 100644
--- a/docs/en_US/pg/release-7-3-7.html
+++ b/docs/en_US/pg/release-7-3-7.html
@@ -1,19 +1,19 @@
 
 
 
-E.42. Release 7.3.7
+E.47. Release 7.3.7
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.42. Release 7.3.7
      
+E.47. Release 7.3.7
    
 
    
 
    Release date
    
 
    2004-08-16
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.42.1. Migration to version 7.3.7
    
+E.47.1. Migration to version 7.3.7
    
 
         A dump/restore is not required for those running 7.3.X.
     
    
 
 
    
 
    
-E.42.2. Changes
    
+E.47.2. Changes
    
 
      
 
    • 
 
      Prevent possible loss of committed transactions during crash
      
diff --git a/docs/en_US/pg/release-7-3-8.html b/docs/en_US/pg/release-7-3-8.html
index 9ca2bb5a9f..775fb9a23b 100644
--- a/docs/en_US/pg/release-7-3-8.html
+++ b/docs/en_US/pg/release-7-3-8.html
@@ -1,19 +1,19 @@
 
 
 
-E.41. Release 7.3.8
+E.46. Release 7.3.8
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.41. Release 7.3.8
      
+E.46. Release 7.3.8
    
 
    
 
    Release date
    
 
    2004-10-22
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.41.1. Migration to version 7.3.8
    
+E.46.1. Migration to version 7.3.8
    
 
         A dump/restore is not required for those running 7.3.X.
     
    
 
 
    
 
    
-E.41.2. Changes
    
+E.46.2. Changes
    
 
      
 
    • 
 
      Repair possible failure to update hint bits on disk
      
diff --git a/docs/en_US/pg/release-7-3-9.html b/docs/en_US/pg/release-7-3-9.html
index 589ade01d8..aa00665178 100644
--- a/docs/en_US/pg/release-7-3-9.html
+++ b/docs/en_US/pg/release-7-3-9.html
@@ -1,19 +1,19 @@
 
 
 
-E.40. Release 7.3.9
+E.45. Release 7.3.9
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.40. Release 7.3.9
      
+E.45. Release 7.3.9
    
 
    
 
    Release date
    
 
    2005-01-31
    
@@ -23,13 +23,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.40.1. Migration to version 7.3.9
    
+E.45.1. Migration to version 7.3.9
    
 
         A dump/restore is not required for those running 7.3.X.
     
    
 
 
    
 
    
-E.40.2. Changes
    
+E.45.2. Changes
    
 
      
 
    • 
 
      Disallow LOAD to non-superusers
      
diff --git a/docs/en_US/pg/release-7-3.html b/docs/en_US/pg/release-7-3.html
index 8180a5bb1d..aa2d93a6b7 100644
--- a/docs/en_US/pg/release-7-3.html
+++ b/docs/en_US/pg/release-7-3.html
@@ -1,26 +1,26 @@
 
 
 
-E.49. Release 7.3
+E.54. Release 7.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.49. Release 7.3
      
+E.54. Release 7.3
    
 
    
 
    Release date
    
 
    2002-11-27
    
 
    
 
    
 
    
-E.49.1. Overview
    
+E.54.1. Overview
    
 
        Major changes in this release:
    
    
 
    
@@ -80,7 +80,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.49.2. Migration to version 7.3
    
+E.54.2. Migration to version 7.3
    
 
        A dump/restore using pg_dump is required for those
     wishing to migrate data from any previous release. If your
     application examines the system catalogs, additional changes will
@@ -138,10 +138,10 @@ 
    Release date
    
 
 
    
 
    
-E.49.3. Changes
    
+E.54.3. Changes
    
 
    
 
    
-E.49.3.1. Server Operation
    
+E.54.3.1. Server Operation
    
 
      
 
    • Add pg_locks view to show locks (Neil)
      • 
 
    • Security fixes for password negotiation memory allocation (Neil)
      • 
@@ -151,7 +151,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.2. Performance
    
+E.54.3.2. Performance
    
 
      
 
    • Improve startup by calling localtime() only once (Tom)
      • 
 
    • Cache system catalog information in flat files for faster startup (Tom)
      • 
@@ -175,7 +175,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.3. Privileges
    
+E.54.3.3. Privileges
    
 
      
 
    • Add privileges on functions and procedural languages (Peter)
      • 
 
    • Add OWNER to CREATE DATABASE so superusers can create databases on behalf of unprivileged users (Gavin Sherry, Tom)
      • 
@@ -186,7 +186,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.4. Server Configuration
    
+E.54.3.4. Server Configuration
    
 
      
 
    • Server log messages now tagged with LOG, not DEBUG (Bruce)
      • 
 
    • Add user column to pg_hba.conf (Bruce)
      • 
@@ -208,7 +208,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.5. Queries
    
+E.54.3.5. Queries
    
 
      
 
    • Make cursors insensitive, meaning their contents do not change (Tom)
      • 
 
    • Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)
      • 
@@ -232,7 +232,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.6. Object Manipulation
    
+E.54.3.6. Object Manipulation
    
 
      
 
    • Make equals signs optional in CREATE DATABASE (Gavin Sherry)
      • 
 
    • Make ALTER TABLE OWNER change index ownership too (Neil)
      • 
@@ -269,7 +269,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.7. Utility Commands
    
+E.54.3.7. Utility Commands
    
 
      
 
    • Have COPY TO output embedded carriage returns and newlines as \r and \n (Tom)
      • 
 
    • Allow DELIMITER in COPY FROM to be 8-bit clean (Tatsuo)
      • 
@@ -309,7 +309,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.8. Data Types and Functions
    
+E.54.3.8. Data Types and Functions
    
 
      
 
    • Fix factorial(0) to return 1 (Bruce)
      • 
 
    • Date/time/timezone improvements (Thomas)
      • 
@@ -355,7 +355,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.9. Internationalization
    
+E.54.3.9. Internationalization
    
 
      
 
    • Add additional encodings: Korean (JOHAB), Thai (WIN874), Vietnamese (TCVN), Arabic (WIN1256), Simplified Chinese (GBK), Korean (UHC) (Eiji Tokuya)
      • 
 
    • Enable locale support by default (Peter)
      • 
@@ -373,7 +373,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.10. Server-side Languages
    
+E.54.3.10. Server-side Languages
    
 
      
 
    • Allow recursive SQL function (Peter)
      • 
 
    • Change PL/Tcl build to use configured compiler and Makefile.shlib (Peter)
      • 
@@ -386,7 +386,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.11. psql
    
+E.54.3.11. psql
    
 
      
 
    • Don't lowercase psql \connect database name for 7.2.0 compatibility (Tom)
      • 
 
    • Add psql \timing to time user queries (Greg Sabino Mullane)
      • 
@@ -403,7 +403,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.12. libpq
    
+E.54.3.12. libpq
    
 
      
 
    • Add ~/.pgpass to store host/user password combinations (Alvaro Herrera)
      • 
 
    • Add PQunescapeBytea() function to libpq (Patrick Welche)
      • 
@@ -417,7 +417,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.13. JDBC
    
+E.54.3.13. JDBC
    
 
      
 
    • Allow JDBC to compile with JDK 1.4 (Dave)
      • 
 
    • Add JDBC 3 support (Barry)
      • 
@@ -433,7 +433,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.14. Miscellaneous Interfaces
    
+E.54.3.14. Miscellaneous Interfaces
    
 
      
 
    • Fixed ECPG bug concerning octal numbers in single quotes (Michael)
      • 
 
    • Move src/interfaces/libpgeasy to http://gborg.postgresql.org (Marc, Bruce)
      • 
@@ -449,7 +449,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.15. Source Code
    
+E.54.3.15. Source Code
    
 
      
 
    • Fix for parallel make (Peter)
      • 
 
    • AIX fixes for linking Tcl (Andreas Zeugswetter)
      • 
@@ -504,7 +504,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.49.3.16. Contrib
    
+E.54.3.16. Contrib
    
 
      
 
    • Allow inet arrays in /contrib/array (Neil)
      • 
 
    • GiST fixes (Teodor Sigaev, Neil)
      • 
diff --git a/docs/en_US/pg/release-7-4-1.html b/docs/en_US/pg/release-7-4-1.html
index 51ea764407..81464b0c7b 100644
--- a/docs/en_US/pg/release-7-4-1.html
+++ b/docs/en_US/pg/release-7-4-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.31. Release 7.4.1
+E.35. Release 7.4.1
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.31. Release 7.4.1
      
+E.35. Release 7.4.1
    
 
    
 
    Release date
    
 
    2003-12-22
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.31.1. Migration to version 7.4.1
    
+E.35.1. Migration to version 7.4.1
    
 
         A dump/restore is not required for those
      running 7.4.
     
    
@@ -42,7 +42,7 @@ 
    Release date
    
 
 
    
 
    
-E.31.2. Changes
    
+E.35.2. Changes
    
 
      
 
    • Fixed bug in CREATE SCHEMA parsing in ECPG (Michael)
      • 
 
    • Fix compile error when --enable-thread-safety and --with-perl are used together (Peter)
      • 
diff --git a/docs/en_US/pg/release-7-4-10.html b/docs/en_US/pg/release-7-4-10.html
index dfbf6dde95..3cb3b512b7 100644
--- a/docs/en_US/pg/release-7-4-10.html
+++ b/docs/en_US/pg/release-7-4-10.html
@@ -1,19 +1,19 @@
 
 
 
-E.22. Release 7.4.10
+E.26. Release 7.4.10
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.22. Release 7.4.10
      
+E.26. Release 7.4.10
    
 
    
 
    Release date
    
 
    2005-12-12
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.22.1. Migration to version 7.4.10
    
+E.26.1. Migration to version 7.4.10
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.8, see the release
      notes for 7.4.8.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.22.2. Changes
    
+E.26.2. Changes
    
 
      
 
    • 
 
      Fix race condition in transaction log management
      
diff --git a/docs/en_US/pg/release-7-4-11.html b/docs/en_US/pg/release-7-4-11.html
index ae7ea75dc2..3434a1ba74 100644
--- a/docs/en_US/pg/release-7-4-11.html
+++ b/docs/en_US/pg/release-7-4-11.html
@@ -1,19 +1,19 @@
 
 
 
-E.21. Release 7.4.11
+E.25. Release 7.4.11
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.21. Release 7.4.11
      
+E.25. Release 7.4.11
    
 
    
 
    Release date
    
 
    2006-01-09
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.21.1. Migration to version 7.4.11
    
+E.25.1. Migration to version 7.4.11
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.8, see the release
      notes for 7.4.8.
@@ -33,7 +33,7 @@ 
    Release date
    
 
 
    
 
    
-E.21.2. Changes
    
+E.25.2. Changes
    
 
      
 
    • Fix for protocol-level Describe messages issued
 outside a transaction or in a failed transaction (Tom)
      • 
diff --git a/docs/en_US/pg/release-7-4-12.html b/docs/en_US/pg/release-7-4-12.html
index 408c9078f0..9c6f576f00 100644
--- a/docs/en_US/pg/release-7-4-12.html
+++ b/docs/en_US/pg/release-7-4-12.html
@@ -1,19 +1,19 @@
 
 
 
-E.20. Release 7.4.12
+E.24. Release 7.4.12
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.20. Release 7.4.12
      
+E.24. Release 7.4.12
    
 
    
 
    Release date
    
 
    2006-02-14
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.20.1. Migration to version 7.4.12
    
+E.24.1. Migration to version 7.4.12
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.11, see the release
      notes for 7.4.11.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.20.2. Changes
    
+E.24.2. Changes
    
 
      
 
    • 
 
      Fix potential crash in SET
diff --git a/docs/en_US/pg/release-7-4-13.html b/docs/en_US/pg/release-7-4-13.html
index 753545e726..eefb862ca8 100644
--- a/docs/en_US/pg/release-7-4-13.html
+++ b/docs/en_US/pg/release-7-4-13.html
@@ -1,19 +1,19 @@
 
 
 
-E.19. Release 7.4.13
+E.23. Release 7.4.13
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.19. Release 7.4.13
      
+E.23. Release 7.4.13
    
 
    
 
    Release date
    
 
    2006-05-23
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.19.1. Migration to version 7.4.13
    
+E.23.1. Migration to version 7.4.13
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.11, see the release
      notes for 7.4.11.
@@ -41,7 +41,7 @@ 
    Release date
    
 
 
    
 
    
-E.19.2. Changes
    
+E.23.2. Changes
    
 
      
 
    • 
 
      Change the server to reject invalidly-encoded multibyte
diff --git a/docs/en_US/pg/release-7-4-14.html b/docs/en_US/pg/release-7-4-14.html
index 3f16180552..87790916a1 100644
--- a/docs/en_US/pg/release-7-4-14.html
+++ b/docs/en_US/pg/release-7-4-14.html
@@ -1,19 +1,19 @@
 
 
 
-E.18. Release 7.4.14
+E.22. Release 7.4.14
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.18. Release 7.4.14
      
+E.22. Release 7.4.14
    
 
    
 
    Release date
    
 
    2006-10-16
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.18.1. Migration to version 7.4.14
    
+E.22.1. Migration to version 7.4.14
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.11, see the release
      notes for 7.4.11.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.18.2. Changes
    
+E.22.2. Changes
    
 
      
 
    • Fix core dump when an untyped literal is taken as
 ANYARRAY
      • 
diff --git a/docs/en_US/pg/release-7-4-15.html b/docs/en_US/pg/release-7-4-15.html
new file mode 100644
index 0000000000..9b1a318051
--- /dev/null
+++ b/docs/en_US/pg/release-7-4-15.html
@@ -0,0 +1,69 @@
+
+
+
+E.21. Release 7.4.15
+
+
+
+
+
+
+
+
+
+
      
+
      
+E.21. Release 7.4.15
      
+
      
+
      Release date
      
+
      2007-01-08
      
+
      
+
          This release contains a variety of fixes from 7.4.14.
+   
      
+
      
+
      
+E.21.1. Migration to version 7.4.15
      
+
           A dump/restore is not required for those running 7.4.X.  However,
+     if you are upgrading from a version earlier than 7.4.11, see the release
+     notes for 7.4.11.
+    
      
+
      
+
      
+
      
+E.21.2. Changes
      
+
        
+
      • 
+
               Improve handling of getaddrinfo() on AIX (Tom)
+      
        
+
               This fixes a problem with starting the statistics collector,
+       among other things.
+      
        
+
        • 
+
      •         Fix “failed to re-find parent key” errors in
+        VACUUM (Tom)
+       
        • 
+
      •         Fix bugs affecting multi-gigabyte hash indexes (Tom)
+       
        • 
+
      •        Fix error when constructing an ARRAY[] made up of multiple
+       empty elements (Tom)
+      
        • 
+
      • 
+
               to_number() and to_char(numeric)
+       are now STABLE, not IMMUTABLE, for
+       new initdb
+       installs (Tom)
+      
        
+
               This is because lc_numeric can potentially
+       change the output of these functions.
+      
        
+
        • 
+
      • 
+
               Improve index usage of regular expressions that use parentheses (Tom)
+      
        
+
               This improves psql \d performance also.
+      
        
+
        • 
+
      
+
      
+
      
+
diff --git a/docs/en_US/pg/release-7-4-2.html b/docs/en_US/pg/release-7-4-2.html
index ffd6102ea8..d17a4ad85d 100644
--- a/docs/en_US/pg/release-7-4-2.html
+++ b/docs/en_US/pg/release-7-4-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.30. Release 7.4.2
+E.34. Release 7.4.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.30. Release 7.4.2
      
+E.34. Release 7.4.2
    
 
    
 
    Release date
    
 
    2004-03-08
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.30.1. Migration to version 7.4.2
    
+E.34.1. Migration to version 7.4.2
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      it may be advisable as the easiest method of incorporating fixes for
      two errors that have been found in the initial contents of 7.4.X system
@@ -96,7 +96,7 @@ 
    Release date
    
 
 
    
 
    
-E.30.2. Changes
    
+E.34.2. Changes
    
 
        Release 7.4.2 incorporates all the fixes included in release 7.3.6,
     plus the following fixes:
    
 
      
diff --git a/docs/en_US/pg/release-7-4-3.html b/docs/en_US/pg/release-7-4-3.html
index 847a2f5ee4..5c84e47854 100644
--- a/docs/en_US/pg/release-7-4-3.html
+++ b/docs/en_US/pg/release-7-4-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.29. Release 7.4.3
+E.33. Release 7.4.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.29. Release 7.4.3
      
+E.33. Release 7.4.3
    
 
    
 
    Release date
    
 
    2004-06-14
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.29.1. Migration to version 7.4.3
    
+E.33.1. Migration to version 7.4.3
    
 
         A dump/restore is not required for those running 7.4.X.
     
    
 
 
    
 
    
-E.29.2. Changes
    
+E.33.2. Changes
    
 
      
 
    • Fix temporary memory leak when using non-hashed aggregates (Tom)
      • 
 
    • ECPG fixes, including some for Informix compatibility (Michael)
      • 
diff --git a/docs/en_US/pg/release-7-4-4.html b/docs/en_US/pg/release-7-4-4.html
index 0a7db647df..745d7bda30 100644
--- a/docs/en_US/pg/release-7-4-4.html
+++ b/docs/en_US/pg/release-7-4-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.28. Release 7.4.4
+E.32. Release 7.4.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.28. Release 7.4.4
      
+E.32. Release 7.4.4
    
 
    
 
    Release date
    
 
    2004-08-16
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.28.1. Migration to version 7.4.4
    
+E.32.1. Migration to version 7.4.4
    
 
         A dump/restore is not required for those running 7.4.X.
     
    
 
 
    
 
    
-E.28.2. Changes
    
+E.32.2. Changes
    
 
      
 
    • 
 
      Prevent possible loss of committed transactions during crash
      
diff --git a/docs/en_US/pg/release-7-4-5.html b/docs/en_US/pg/release-7-4-5.html
index 9bf4cf7072..365b53048b 100644
--- a/docs/en_US/pg/release-7-4-5.html
+++ b/docs/en_US/pg/release-7-4-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.27. Release 7.4.5
+E.31. Release 7.4.5
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.27. Release 7.4.5
      
+E.31. Release 7.4.5
    
 
    
 
    Release date
    
 
    2004-08-18
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.27.1. Migration to version 7.4.5
    
+E.31.1. Migration to version 7.4.5
    
 
         A dump/restore is not required for those running 7.4.X.
     
    
 
 
    
 
    
-E.27.2. Changes
    
+E.31.2. Changes
    
 
    • 
 
      Repair possible crash during concurrent B-tree index insertions
      
 
      This patch fixes a rare case in which concurrent insertions into a B-tree index
diff --git a/docs/en_US/pg/release-7-4-6.html b/docs/en_US/pg/release-7-4-6.html
index a60a9b2bc0..0ae44eec62 100644
--- a/docs/en_US/pg/release-7-4-6.html
+++ b/docs/en_US/pg/release-7-4-6.html
@@ -1,19 +1,19 @@
 
 
 
-E.26. Release 7.4.6
+E.30. Release 7.4.6
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.26. Release 7.4.6
      
+E.30. Release 7.4.6
    
 
    
 
    Release date
    
 
    2004-10-22
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.26.1. Migration to version 7.4.6
    
+E.30.1. Migration to version 7.4.6
    
 
         A dump/restore is not required for those running 7.4.X.
     
    
 
 
    
 
    
-E.26.2. Changes
    
+E.30.2. Changes
    
 
      
 
    • 
 
      Repair possible failure to update hint bits on disk
      
diff --git a/docs/en_US/pg/release-7-4-7.html b/docs/en_US/pg/release-7-4-7.html
index 7605937adb..2bf166eff6 100644
--- a/docs/en_US/pg/release-7-4-7.html
+++ b/docs/en_US/pg/release-7-4-7.html
@@ -1,19 +1,19 @@
 
 
 
-E.25. Release 7.4.7
+E.29. Release 7.4.7
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.25. Release 7.4.7
      
+E.29. Release 7.4.7
    
 
    
 
    Release date
    
 
    2005-01-31
    
@@ -23,13 +23,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.25.1. Migration to version 7.4.7
    
+E.29.1. Migration to version 7.4.7
    
 
         A dump/restore is not required for those running 7.4.X.
     
    
 
 
    
 
    
-E.25.2. Changes
    
+E.29.2. Changes
    
 
      
 
    • 
 
      Disallow LOAD to non-superusers
      
diff --git a/docs/en_US/pg/release-7-4-8.html b/docs/en_US/pg/release-7-4-8.html
index c17b4c32d5..08d8bf7d1d 100644
--- a/docs/en_US/pg/release-7-4-8.html
+++ b/docs/en_US/pg/release-7-4-8.html
@@ -1,19 +1,19 @@
 
 
 
-E.24. Release 7.4.8
+E.28. Release 7.4.8
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.24. Release 7.4.8
      
+E.28. Release 7.4.8
    
 
    
 
    Release date
    
 
    2005-05-09
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.24.1. Migration to version 7.4.8
    
+E.28.1. Migration to version 7.4.8
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      it is one possible way of handling two significant security problems
      that have been found in the initial contents of 7.4.X system
@@ -106,7 +106,7 @@ 
    Release date
    
 
 
    
 
    
-E.24.2. Changes
    
+E.28.2. Changes
    
 
      
 
    • Change encoding function signature to prevent
 misuse
      • 
diff --git a/docs/en_US/pg/release-7-4-9.html b/docs/en_US/pg/release-7-4-9.html
index 6e99a79bb9..7888abe8c3 100644
--- a/docs/en_US/pg/release-7-4-9.html
+++ b/docs/en_US/pg/release-7-4-9.html
@@ -1,19 +1,19 @@
 
 
 
-E.23. Release 7.4.9
+E.27. Release 7.4.9
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.23. Release 7.4.9
      
+E.27. Release 7.4.9
    
 
    
 
    Release date
    
 
    2005-10-04
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.23.1. Migration to version 7.4.9
    
+E.27.1. Migration to version 7.4.9
    
 
         A dump/restore is not required for those running 7.4.X.  However,
      if you are upgrading from a version earlier than 7.4.8, see the release
      notes for 7.4.8.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.23.2. Changes
    
+E.27.2. Changes
    
 
      
 
    • 
 
      Fix error that allowed VACUUM to remove
diff --git a/docs/en_US/pg/release-7-4.html b/docs/en_US/pg/release-7-4.html
index bfaddf9a04..82ce09c11d 100644
--- a/docs/en_US/pg/release-7-4.html
+++ b/docs/en_US/pg/release-7-4.html
@@ -1,26 +1,26 @@
 
 
 
-E.32. Release 7.4
+E.36. Release 7.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.32. Release 7.4
      
+E.36. Release 7.4
    
 
    
 
    Release date
    
 
    2003-11-17
    
 
    
 
    
 
    
-E.32.1. Overview
    
+E.36.1. Overview
    
 
        Major changes in this release:
    
    
 
    
@@ -154,7 +154,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.32.2. Migration to version 7.4
    
+E.36.2. Migration to version 7.4
    
 
        A dump/restore using pg_dump is
     required for those wishing to migrate data from any previous
     release.
@@ -251,13 +251,13 @@ 
    Release date
    
 
 
    
 
    
-E.32.3. Changes
    
+E.36.3. Changes
    
 
        Below you will find a detailed account of the changes between
     release 7.4 and the previous major release.
    
    
 
    
 
    
-E.32.3.1. Server Operation Changes
    
+E.36.3.1. Server Operation Changes
    
 
      
 
    •       Allow IPv6 server connections (Nigel Kukard, Johan Jordaan,
       Bruce, Tom, Kurt Roeckx, Andrew Dunstan)
@@ -329,7 +329,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.2. Performance Improvements
    
+E.36.3.2. Performance Improvements
    
 
      
 
    • Add hashing for GROUP BY aggregates (Tom)
      • 
 
    • Make nested-loop joins be smarter about multicolumn indexes (Tom)
      • 
@@ -434,7 +434,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.3. Server Configuration Changes
    
+E.36.3.3. Server Configuration Changes
    
 
      
 
    • 
 
      Rename server parameter server_min_messages to log_min_messages (Bruce)
      
@@ -543,7 +543,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.4. Query Changes
    
+E.36.3.4. Query Changes
    
 
      
 
    • New SQL-standard information schema (Peter)
      • 
 
    • Add read-only transactions (Peter)
      • 
@@ -591,7 +591,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.5. Object Manipulation Changes
    
+E.36.3.5. Object Manipulation Changes
    
 
      
 
    • Make CREATE SEQUENCE grammar more conforming to SQL:2003 (Neil)
      • 
 
    • 
@@ -661,7 +661,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.6. Utility Command Changes
    
+E.36.3.6. Utility Command Changes
    
 
      
 
    • 
 
      Add ON COMMIT clause to CREATE TABLE for temporary tables (Gavin)
      
@@ -775,7 +775,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.7. Data Type and Function Changes
    
+E.36.3.7. Data Type and Function Changes
    
 
      
 
    • 
 
            New server parameter extra_float_digits to
@@ -916,7 +916,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.8. Server-Side Language Changes
    
+E.36.3.8. Server-Side Language Changes
    
 
      
 
    •       Prevent PL/pgSQL crash when RETURN NEXT is
       used on a zero-row record variable (Tom)
@@ -952,7 +952,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.9. psql Changes
    
+E.36.3.9. psql Changes
    
 
      
 
    • 
 
      Add \pset pager always to always use pager (Greg)
      
@@ -997,7 +997,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.10. pg_dump Changes
    
+E.36.3.10. pg_dump Changes
    
 
      
 
    • Multiple pg_dump fixes, including tar format and large objects
      • 
 
    • Allow pg_dump to dump specific schemas (Neil)
      • 
@@ -1033,7 +1033,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.11. libpq Changes
    
+E.36.3.11. libpq Changes
    
 
      
 
    • 
 
            Add function PQfreemem for freeing memory on
@@ -1090,7 +1090,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.12. JDBC Changes
    
+E.36.3.12. JDBC Changes
    
 
      
 
    • Allow setNull on updateable result sets
      • 
 
    • Allow executeBatch on a prepared statement (Barry)
      • 
@@ -1101,7 +1101,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.13. Miscellaneous Interface Changes
    
+E.36.3.13. Miscellaneous Interface Changes
    
 
      
 
    • Prevent possible memory leak or core dump during libpgtcl shutdown (Tom)
      • 
 
    • 
@@ -1125,7 +1125,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.14. Source Code Changes
    
+E.36.3.14. Source Code Changes
    
 
      
 
    • Prevent need for separate platform geometry regression result files (Tom)
      • 
 
    • Improved PPC locking primitive (Reinhard Max)
      • 
@@ -1161,7 +1161,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.32.3.15. Contrib Changes
    
+E.36.3.15. Contrib Changes
    
 
      
 
    • Change dbmirror license to BSD
      • 
 
    • Improve earthdistance (Bruno Wolff III)
      • 
diff --git a/docs/en_US/pg/release-8-0-1.html b/docs/en_US/pg/release-8-0-1.html
index 761f59afcf..7676d0df9a 100644
--- a/docs/en_US/pg/release-8-0-1.html
+++ b/docs/en_US/pg/release-8-0-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.16. Release 8.0.1
+E.19. Release 8.0.1
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.16. Release 8.0.1
      
+E.19. Release 8.0.1
    
 
    
 
    Release date
    
 
    2005-01-31
    
@@ -23,13 +23,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.16.1. Migration to version 8.0.1
    
+E.19.1. Migration to version 8.0.1
    
 
         A dump/restore is not required for those running 8.0.0.
     
    
 
 
    
 
    
-E.16.2. Changes
    
+E.19.2. Changes
    
 
      
 
    • 
 
      Disallow LOAD to non-superusers
      
diff --git a/docs/en_US/pg/release-8-0-10.html b/docs/en_US/pg/release-8-0-10.html
new file mode 100644
index 0000000000..e7b82160dc
--- /dev/null
+++ b/docs/en_US/pg/release-8-0-10.html
@@ -0,0 +1,83 @@
+
+
+
+E.10. Release 8.0.10
+
+
+
+
+
+
+
+
+
+
      
+
      
+E.10. Release 8.0.10
      
+
      
+
      Release date
      
+
      2007-01-08
      
+
      
+
          This release contains a variety of fixes from 8.0.9.
+   
      
+
      
+
      
+E.10.1. Migration to version 8.0.10
      
+
           A dump/restore is not required for those running 8.0.X.  However,
+     if you are upgrading from a version earlier than 8.0.6, see the release
+     notes for 8.0.6.
+    
      
+
      
+
      
+
      
+E.10.2. Changes
      
+
        
+
      • 
+
               Improve handling of getaddrinfo() on AIX (Tom)
+      
        
+
               This fixes a problem with starting the statistics collector,
+       among other things.
+      
        
+
        • 
+
      •         Fix “failed to re-find parent key” errors in
+        VACUUM (Tom)
+       
        • 
+
      •         Fix race condition for truncation of a large relation across a
+        gigabyte boundary by VACUUM (Tom)
+       
        • 
+
      •         Fix bugs affecting multi-gigabyte hash indexes (Tom)
+       
        • 
+
      •        Fix possible deadlock in Windows signal handling (Teodor)
+      
        • 
+
      •        Fix error when constructing an ARRAY[] made up of multiple
+       empty elements (Tom)
+      
        • 
+
      •        Fix ecpg memory leak during connection (Michael)
+      
        • 
+
      • 
+
               to_number() and to_char(numeric)
+       are now STABLE, not IMMUTABLE, for
+       new initdb
+       installs (Tom)
+      
        
+
               This is because lc_numeric can potentially
+       change the output of these functions.
+      
        
+
        • 
+
      • 
+
               Improve index usage of regular expressions that use parentheses (Tom)
+      
        
+
               This improves psql \d performance also.
+      
        
+
        • 
+
      • 
+
               Update timezone database
+      
        
+
               This affects Australian and Canadian daylight-savings rules in
+       particular.
+      
        
+
        • 
+
      
+
      
+
      
+
diff --git a/docs/en_US/pg/release-8-0-2.html b/docs/en_US/pg/release-8-0-2.html
index 52710df0e5..1faf9e7a38 100644
--- a/docs/en_US/pg/release-8-0-2.html
+++ b/docs/en_US/pg/release-8-0-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.15. Release 8.0.2
+E.18. Release 8.0.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.15. Release 8.0.2
      
+E.18. Release 8.0.2
    
 
    
 
    Release date
    
 
    2005-04-07
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.15.1. Migration to version 8.0.2
    
+E.18.1. Migration to version 8.0.2
    
 
         A dump/restore is not required for those running 8.0.*.
      This release updates the major version number of the
      PostgreSQL libraries, so it might be
@@ -32,7 +32,7 @@ 
    Release date
    
 
 
    
 
    
-E.15.2. Changes
    
+E.18.2. Changes
    
 
      
 
    • 
 
      Increment the major version number of all interface 
diff --git a/docs/en_US/pg/release-8-0-3.html b/docs/en_US/pg/release-8-0-3.html
index 27b57587f3..fb92191cbd 100644
--- a/docs/en_US/pg/release-8-0-3.html
+++ b/docs/en_US/pg/release-8-0-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.14. Release 8.0.3
+E.17. Release 8.0.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.14. Release 8.0.3
      
+E.17. Release 8.0.3
    
 
    
 
    Release date
    
 
    2005-05-09
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.14.1. Migration to version 8.0.3
    
+E.17.1. Migration to version 8.0.3
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      it is one possible way of handling two significant security problems
      that have been found in the initial contents of 8.0.X system
@@ -51,13 +51,13 @@ 
    Release date
    
      privileges of a database superuser.
     
    
 
         If you wish not to do an initdb, perform the same manual repair
-     procedures shown in the 7.4.8 release
+     procedures shown in the 7.4.8 release
      notes.
     
    
 
 
    
 
    
-E.14.2. Changes
    
+E.17.2. Changes
    
 
      
 
    • Change encoding function signature to prevent
 misuse
      • 
diff --git a/docs/en_US/pg/release-8-0-4.html b/docs/en_US/pg/release-8-0-4.html
index 50ff60d2a6..719e35e375 100644
--- a/docs/en_US/pg/release-8-0-4.html
+++ b/docs/en_US/pg/release-8-0-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.13. Release 8.0.4
+E.16. Release 8.0.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.13. Release 8.0.4
      
+E.16. Release 8.0.4
    
 
    
 
    Release date
    
 
    2005-10-04
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.13.1. Migration to version 8.0.4
    
+E.16.1. Migration to version 8.0.4
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.3, see the release
      notes for 8.0.3.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.13.2. Changes
    
+E.16.2. Changes
    
 
      
 
    • 
 
      Fix error that allowed VACUUM to remove
diff --git a/docs/en_US/pg/release-8-0-5.html b/docs/en_US/pg/release-8-0-5.html
index cb76db8e3a..1a41187ac4 100644
--- a/docs/en_US/pg/release-8-0-5.html
+++ b/docs/en_US/pg/release-8-0-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.12. Release 8.0.5
+E.15. Release 8.0.5
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.12. Release 8.0.5
      
+E.15. Release 8.0.5
    
 
    
 
    Release date
    
 
    2005-12-12
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.12.1. Migration to version 8.0.5
    
+E.15.1. Migration to version 8.0.5
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.3, see the release
      notes for 8.0.3.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.12.2. Changes
    
+E.15.2. Changes
    
 
      
 
    • 
 
      Fix race condition in transaction log management
      
diff --git a/docs/en_US/pg/release-8-0-6.html b/docs/en_US/pg/release-8-0-6.html
index 27cb738027..121ed7cfe2 100644
--- a/docs/en_US/pg/release-8-0-6.html
+++ b/docs/en_US/pg/release-8-0-6.html
@@ -1,19 +1,19 @@
 
 
 
-E.11. Release 8.0.6
+E.14. Release 8.0.6
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.11. Release 8.0.6
      
+E.14. Release 8.0.6
    
 
    
 
    Release date
    
 
    2006-01-09
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.11.1. Migration to version 8.0.6
    
+E.14.1. Migration to version 8.0.6
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.3, see the release
      notes for 8.0.3.
@@ -33,7 +33,7 @@ 
    Release date
    
 
 
    
 
    
-E.11.2. Changes
    
+E.14.2. Changes
    
 
      
 
    • 
 
      Fix Windows code so that postmaster will continue rather
diff --git a/docs/en_US/pg/release-8-0-7.html b/docs/en_US/pg/release-8-0-7.html
index be0d980225..6bb962a388 100644
--- a/docs/en_US/pg/release-8-0-7.html
+++ b/docs/en_US/pg/release-8-0-7.html
@@ -1,19 +1,19 @@
 
 
 
-E.10. Release 8.0.7
+E.13. Release 8.0.7
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.10. Release 8.0.7
      
+E.13. Release 8.0.7
    
 
    
 
    Release date
    
 
    2006-02-14
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.10.1. Migration to version 8.0.7
    
+E.13.1. Migration to version 8.0.7
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.6, see the release
      notes for 8.0.6.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.10.2. Changes
    
+E.13.2. Changes
    
 
      
 
    • 
 
      Fix potential crash in SET
diff --git a/docs/en_US/pg/release-8-0-8.html b/docs/en_US/pg/release-8-0-8.html
index 7e9a5df2e7..47ee5e75f6 100644
--- a/docs/en_US/pg/release-8-0-8.html
+++ b/docs/en_US/pg/release-8-0-8.html
@@ -1,19 +1,19 @@
 
 
 
-E.9. Release 8.0.8
+E.12. Release 8.0.8
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.9. Release 8.0.8
      
+E.12. Release 8.0.8
    
 
    
 
    Release date
    
 
    2006-05-23
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.9.1. Migration to version 8.0.8
    
+E.12.1. Migration to version 8.0.8
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.6, see the release
      notes for 8.0.6.
@@ -41,7 +41,7 @@ 
    Release date
    
 
 
    
 
    
-E.9.2. Changes
    
+E.12.2. Changes
    
 
      
 
    • 
 
      Change the server to reject invalidly-encoded multibyte
diff --git a/docs/en_US/pg/release-8-0-9.html b/docs/en_US/pg/release-8-0-9.html
index 85d9eeccde..2963a6b7fa 100644
--- a/docs/en_US/pg/release-8-0-9.html
+++ b/docs/en_US/pg/release-8-0-9.html
@@ -1,19 +1,19 @@
 
 
 
-E.8. Release 8.0.9
+E.11. Release 8.0.9
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.8. Release 8.0.9
      
+E.11. Release 8.0.9
    
 
    
 
    Release date
    
 
    2006-10-16
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.8.1. Migration to version 8.0.9
    
+E.11.1. Migration to version 8.0.9
    
 
         A dump/restore is not required for those running 8.0.X.  However,
      if you are upgrading from a version earlier than 8.0.6, see the release
      notes for 8.0.6.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.8.2. Changes
    
+E.11.2. Changes
    
 
      
 
    • Fix crash when referencing NEW row
 values in rule WHERE expressions (Tom)
      • 
diff --git a/docs/en_US/pg/release-8-0.html b/docs/en_US/pg/release-8-0.html
index 45f456c6d1..aa9deb8c44 100644
--- a/docs/en_US/pg/release-8-0.html
+++ b/docs/en_US/pg/release-8-0.html
@@ -1,26 +1,26 @@
 
 
 
-E.17. Release 8.0
+E.20. Release 8.0
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.17. Release 8.0
      
+E.20. Release 8.0
    
 
    
 
    Release date
    
 
    2005-01-19
    
 
    
 
    
 
    
-E.17.1. Overview
    
+E.20.1. Overview
    
 
         Major changes in this release:
     
    
 
    
@@ -107,7 +107,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.17.2. Migration to version 8.0
    
+E.20.2. Migration to version 8.0
    
 
         A dump/restore using pg_dump is
      required for those wishing to migrate data from any previous
      release.
@@ -241,7 +241,7 @@ 
    Release date
    
 
 
    
 
    
-E.17.3. Deprecated Features
    
+E.20.3. Deprecated Features
    
 
         Some aspects of PostgreSQL's behavior
      have been determined to be suboptimal. For the sake of backward
      compatibility these have not been removed in 8.0, but they are
@@ -272,13 +272,13 @@ 
    Release date
    
 
 
    
 
    
-E.17.4. Changes
    
+E.20.4. Changes
    
 
         Below you will find a detailed account of the changes between
      release 8.0 and the previous major release.
     
    
 
    
 
    
-E.17.4.1. Performance Improvements
    
+E.20.4.1. Performance Improvements
    
 
      
 
    • 
 
              Support cross-data-type index usage (Tom)
@@ -428,7 +428,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.2. Server Changes
    
+E.20.4.2. Server Changes
    
 
      
 
    •         Add WAL file archiving and point-in-time recovery (Simon Riggs)
        
      • 
@@ -571,7 +571,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.3. Query Changes
    
+E.20.4.3. Query Changes
    
 
      
 
    •         Add savepoints (nested transactions) (Alvaro)
        
      • 
@@ -678,7 +678,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.4. Object Manipulation Changes
    
+E.20.4.4. Object Manipulation Changes
    
 
      
 
    •         Add COMMENT ON for casts, conversions, languages,
         operator classes, and large objects (Christopher)
@@ -786,7 +786,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.5. Utility Command Changes
    
+E.20.4.5. Utility Command Changes
    
 
      
 
    •         Allow CREATE SCHEMA to create triggers,
         indexes, and sequences (Neil)
@@ -879,7 +879,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.6. Data Type and Function Changes
    
+E.20.4.6. Data Type and Function Changes
    
 
      
 
    • 
 
              More complete support for composite types (row types)  (Tom)
@@ -1049,7 +1049,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.7. Server-Side Language Changes
    
+E.20.4.7. Server-Side Language Changes
    
 
      
 
    •         In READ COMMITTED serialization mode, volatile functions
         now see the results of concurrent transactions committed up to the
@@ -1131,7 +1131,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.8. psql Changes
    
+E.20.4.8. psql Changes
    
 
      
 
    •         Improve psql information display about database
         objects (Christopher)
@@ -1189,7 +1189,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.9. pg_dump Changes
    
+E.20.4.9. pg_dump Changes
    
 
      
 
    • 
 
              Use dependency information to improve the reliability of
@@ -1236,7 +1236,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.10. libpq Changes
    
+E.20.4.10. libpq Changes
    
 
      
 
    •         Make libpq's SIGPIPE handling thread-safe (Bruce)
        
      • 
@@ -1263,7 +1263,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.11. Source Code Changes
    
+E.20.4.11. Source Code Changes
    
 
      
 
    •         Allow the database server to run natively on Windows (Claudio, Magnus, Andrew)
        
      • 
@@ -1375,7 +1375,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.17.4.12. Contrib Changes
    
+E.20.4.12. Contrib Changes
    
 
      
 
    •         Overhaul of contrib/dblink (Joe)
        
      • 
diff --git a/docs/en_US/pg/release-8-1-1.html b/docs/en_US/pg/release-8-1-1.html
index bddb93256e..8b98f7158a 100644
--- a/docs/en_US/pg/release-8-1-1.html
+++ b/docs/en_US/pg/release-8-1-1.html
@@ -1,19 +1,19 @@
 
 
 
-E.6. Release 8.1.1
+E.8. Release 8.1.1
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.6. Release 8.1.1
      
+E.8. Release 8.1.1
    
 
    
 
    Release date
    
 
    2005-12-12
    
@@ -22,13 +22,13 @@ 
    Release date
    
    
    
 
    
 
    
-E.6.1. Migration to version 8.1.1
    
+E.8.1. Migration to version 8.1.1
    
 
         A dump/restore is not required for those running 8.1.X.
     
    
 
 
    
 
    
-E.6.2. Changes
    
+E.8.2. Changes
    
 
      
 
    • Fix incorrect optimizations of outer-join conditions
 (Tom)
      • 
diff --git a/docs/en_US/pg/release-8-1-2.html b/docs/en_US/pg/release-8-1-2.html
index c66b2ee157..485bee9366 100644
--- a/docs/en_US/pg/release-8-1-2.html
+++ b/docs/en_US/pg/release-8-1-2.html
@@ -1,19 +1,19 @@
 
 
 
-E.5. Release 8.1.2
+E.7. Release 8.1.2
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.5. Release 8.1.2
      
+E.7. Release 8.1.2
    
 
    
 
    Release date
    
 
    2006-01-09
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.5.1. Migration to version 8.1.2
    
+E.7.1. Migration to version 8.1.2
    
 
         A dump/restore is not required for those running 8.1.X.
      However, you might need to REINDEX indexes on textual
      columns after updating, if you are affected by the locale or
@@ -31,7 +31,7 @@ 
    Release date
    
 
 
    
 
    
-E.5.2. Changes
    
+E.7.2. Changes
    
 
      
 
    • 
 
      Fix Windows code so that postmaster will continue rather
diff --git a/docs/en_US/pg/release-8-1-3.html b/docs/en_US/pg/release-8-1-3.html
index 2adde02470..9f0a7f8ff7 100644
--- a/docs/en_US/pg/release-8-1-3.html
+++ b/docs/en_US/pg/release-8-1-3.html
@@ -1,19 +1,19 @@
 
 
 
-E.4. Release 8.1.3
+E.6. Release 8.1.3
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.4. Release 8.1.3
      
+E.6. Release 8.1.3
    
 
    
 
    Release date
    
 
    2006-02-14
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.4.1. Migration to version 8.1.3
    
+E.6.1. Migration to version 8.1.3
    
 
         A dump/restore is not required for those running 8.1.X.
      However, if you are upgrading from a version earlier than 8.1.2, 
      see the release notes for 8.1.2.
@@ -31,7 +31,7 @@ 
    Release date
    
 
 
    
 
    
-E.4.2. Changes
    
+E.6.2. Changes
    
 
      
 
    • 
 
      Fix bug that allowed any logged-in user to SET
diff --git a/docs/en_US/pg/release-8-1-4.html b/docs/en_US/pg/release-8-1-4.html
index cb6522960d..864c51b9b2 100644
--- a/docs/en_US/pg/release-8-1-4.html
+++ b/docs/en_US/pg/release-8-1-4.html
@@ -1,19 +1,19 @@
 
 
 
-E.3. Release 8.1.4
+E.5. Release 8.1.4
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.3. Release 8.1.4
      
+E.5. Release 8.1.4
    
 
    
 
    Release date
    
 
    2006-05-23
    
@@ -23,7 +23,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.3.1. Migration to version 8.1.4
    
+E.5.1. Migration to version 8.1.4
    
 
         A dump/restore is not required for those running 8.1.X.
      However, if you are upgrading from a version earlier than 8.1.2,
      see the release notes for 8.1.2.
@@ -41,7 +41,7 @@ 
    Release date
    
 
 
    
 
    
-E.3.2. Changes
    
+E.5.2. Changes
    
 
      
 
    • 
 
      Change the server to reject invalidly-encoded multibyte
diff --git a/docs/en_US/pg/release-8-1-5.html b/docs/en_US/pg/release-8-1-5.html
index 55333f17d6..f9337f8b06 100644
--- a/docs/en_US/pg/release-8-1-5.html
+++ b/docs/en_US/pg/release-8-1-5.html
@@ -1,19 +1,19 @@
 
 
 
-E.2. Release 8.1.5
+E.4. Release 8.1.5
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.2. Release 8.1.5
      
+E.4. Release 8.1.5
    
 
    
 
    Release date
    
 
    2006-10-16
    
@@ -22,7 +22,7 @@ 
    Release date
    
    
    
 
    
 
    
-E.2.1. Migration to version 8.1.5
    
+E.4.1. Migration to version 8.1.5
    
 
         A dump/restore is not required for those running 8.1.X.
      However, if you are upgrading from a version earlier than 8.1.2,
      see the release notes for 8.1.2.
@@ -30,7 +30,7 @@ 
    Release date
    
 
 
    
 
    
-E.2.2. Changes
    
+E.4.2. Changes
    
 
      
 
    • 
 
      Disallow aggregate functions in UPDATE
diff --git a/docs/en_US/pg/release-8-1-6.html b/docs/en_US/pg/release-8-1-6.html
new file mode 100644
index 0000000000..e92dd09c12
--- /dev/null
+++ b/docs/en_US/pg/release-8-1-6.html
@@ -0,0 +1,98 @@
+
+
+
+E.3. Release 8.1.6
+
+
+
+
+
+
+
+
+
+
      
+
      
+E.3. Release 8.1.6
      
+
      
+
      Release date
      
+
      2007-01-08
      
+
      
+
          This release contains a variety of fixes from 8.1.5.
+   
      
+
      
+
      
+E.3.1. Migration to version 8.1.6
      
+
           A dump/restore is not required for those running 8.1.X.
+     However, if you are upgrading from a version earlier than 8.1.2,
+     see the release notes for 8.1.2.
+    
      
+
      
+
      
+
      
+E.3.2. Changes
      
+
        
+
      • 
+
               Improve handling of getaddrinfo() on AIX (Tom)
+      
        
+
               This fixes a problem with starting the statistics collector,
+       among other things.
+      
        
+
        • 
+
      •        Fix pg_restore to handle a tar-format backup
+       that contains large objects (blobs) with comments (Tom)
+      
        • 
+
      •         Fix “failed to re-find parent key” errors in
+        VACUUM (Tom)
+       
        • 
+
      • 
+
                Clean out pg_internal.init cache files during server
+        restart (Simon)
+       
        
+
                This avoids a hazard that the cache files might contain stale
+        data after PITR recovery.
+       
        
+
        • 
+
      •         Fix race condition for truncation of a large relation across a
+        gigabyte boundary by VACUUM (Tom)
+       
        • 
+
      •         Fix bug causing needless deadlock errors on row-level locks (Tom)
+       
        • 
+
      •         Fix bugs affecting multi-gigabyte hash indexes (Tom)
+       
        • 
+
      •        Fix possible deadlock in Windows signal handling (Teodor)
+      
        • 
+
      •        Fix error when constructing an ARRAY[] made up of multiple
+       empty elements (Tom)
+      
        • 
+
      •        Fix ecpg memory leak during connection (Michael)
+      
        • 
+
      •        Fix for Darwin (OS X) compilation (Tom)
+      
        • 
+
      • 
+
               to_number() and to_char(numeric)
+       are now STABLE, not IMMUTABLE, for
+       new initdb
+       installs (Tom)
+      
        
+
               This is because lc_numeric can potentially
+       change the output of these functions.
+      
        
+
        • 
+
      • 
+
               Improve index usage of regular expressions that use parentheses (Tom)
+      
        
+
               This improves psql \d performance also.
+      
        
+
        • 
+
      • 
+
               Update timezone database
+      
        
+
               This affects Australian and Canadian daylight-savings rules in
+       particular.
+      
        
+
        • 
+
      
+
      
+
      
+
diff --git a/docs/en_US/pg/release-8-1.html b/docs/en_US/pg/release-8-1.html
index a05d0ab0a3..a441bad787 100644
--- a/docs/en_US/pg/release-8-1.html
+++ b/docs/en_US/pg/release-8-1.html
@@ -1,26 +1,26 @@
 
 
 
-E.7. Release 8.1
+E.9. Release 8.1
 
 
 
-
+
 
-
-
+
+
 
 
 
      
 
      
-E.7. Release 8.1
      
+E.9. Release 8.1
    
 
    
 
    Release date
    
 
    2005-11-08
    
 
    
 
    
 
    
-E.7.1. Overview
    
+E.9.1. Overview
    
 
         Major changes in this release:
     
    
 
    
@@ -146,7 +146,7 @@ 
    Release date
    
 
    
 
    
 
    
-E.7.2. Migration to version 8.1
    
+E.9.2. Migration to version 8.1
    
 
         A dump/restore using pg_dump is required
      for those wishing to migrate data from any previous release.
     
    
@@ -381,14 +381,14 @@ 
    Release date
    
 
 
    
 
    
-E.7.3. Additional Changes
    
+E.9.3. Additional Changes
    
 
         Below you will find a detailed account of the additional changes
      between PostgreSQL 8.1 and the
      previous major release.
     
    
 
    
 
    
-E.7.3.1. Performance Improvements
    
+E.9.3.1. Performance Improvements
    
 
      
 
    •         Improve GiST and R-tree index performance (Neil)
        
      • 
@@ -465,7 +465,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.2. Server Changes
    
+E.9.3.2. Server Changes
    
 
      
 
    • 
 
              Prevent problems due to transaction ID (XID) wraparound (Tom)
@@ -559,7 +559,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.3. Query Changes
    
+E.9.3.3. Query Changes
    
 
      
 
    •         Add temporary views (Koju Iijima, Neil) 
        
      • 
@@ -614,7 +614,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.4. Object Manipulation Changes
    
+E.9.3.4. Object Manipulation Changes
    
 
      
 
    • 
 
              Track dependencies of shared objects (Alvaro)
@@ -654,7 +654,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.5. Utility Command Changes
    
+E.9.3.5. Utility Command Changes
    
 
      
 
    • 
 
              Allow TRUNCATE to truncate multiple tables in a
@@ -739,7 +739,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.6. Data Type and Function Changes
    
+E.9.3.6. Data Type and Function Changes
    
 
      
 
    •         Add MAX() and MIN() aggregates for
         array types (Koju Iijima)
@@ -929,7 +929,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.7. Encoding and Locale Changes
    
+E.9.3.7. Encoding and Locale Changes
    
 
      
 
    • 
 
              Rename some encodings to be more consistent and to follow
@@ -976,7 +976,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.8. General Server-Side Language Changes
    
+E.9.3.8. General Server-Side Language Changes
    
 
      
 
    •         Fix ALTER LANGUAGE RENAME (Sergey Yatskevich)
        
      • 
@@ -1012,7 +1012,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.9. PL/PgSQL Server-Side Language Changes
    
+E.9.3.9. PL/PgSQL Server-Side Language Changes
    
 
      
 
    • 
 
              Overhaul the memory management of PL/PgSQL functions (Neil)
@@ -1067,7 +1067,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.10. PL/Perl Server-Side Language Changes
    
+E.9.3.10. PL/Perl Server-Side Language Changes
    
 
      
 
    • 
 
              Allow large result sets to be returned efficiently (Abhijit
@@ -1112,7 +1112,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.11. psql Changes
    
+E.9.3.11. psql Changes
    
 
      
 
    • 
 
              Add \set ON_ERROR_ROLLBACK to allow statements in
@@ -1186,7 +1186,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.12. pg_dump Changes
    
+E.9.3.12. pg_dump Changes
    
 
      
 
    • 
 
              Add -n / --schema switch to 
@@ -1232,7 +1232,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.13. libpq Changes
    
+E.9.3.13. libpq Changes
    
 
      
 
    •         Add a PGPASSFILE environment variable to specify the
         password file's filename (Andrew)
@@ -1249,7 +1249,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.14. Source Code Changes
    
+E.9.3.14. Source Code Changes
    
 
      
 
    •         Fix pgxs to support building against a relocated
         installation
@@ -1327,7 +1327,7 @@ 
      Release date
      
 
    
 
    
 
    
-E.7.3.15. Contrib Changes
    
+E.9.3.15. Contrib Changes
    
 
    
 
    
 
    Release date
    
-
    2006-12-05
    
+
    2007-01-08
    
 
    
+
        This release contains a variety of fixes from 8.2.
+   
    
 
    
 
    
-E.1.1. Overview
    
-
         This release adds many functionality and performance improvements that
-     were requested by users, including:
-
+E.1.1. Migration to version 8.2.1
    
+
         A dump/restore is not required for those running 8.2.
     
    
-
      
-
    •         Query language enhancements including INSERT/UPDATE/DELETE
-        RETURNING, multirow VALUES lists, and
-        optional target-table alias in
-        UPDATE/DELETE
-       
      • 
-
    •         Index creation without blocking concurrent
-        INSERT/UPDATE/DELETE
-        operations
-       
      • 
-
    •         Many query optimization improvements, including support for
-        reordering outer joins
-       
      • 
-
    •         Improved sorting performance with lower memory usage
-       
      • 
-
    •         More efficient locking with better concurrency
-       
      • 
-
    •         More efficient vacuuming
-       
      • 
-
    •         Easier administration of warm standby servers
-       
      • 
-
    •         New FILLFACTOR support for tables and indexes
-       
      • 
-
    •         Monitoring, logging, and performance tuning additions
-       
      • 
-
    •         More control over creating and dropping objects
-       
      • 
-
    •         Table inheritance relationships can be defined
-        for and removed from pre-existing tables
-       
      • 
-
    •         COPY TO can copy the output of an arbitrary
-        SELECT statement
-       
      • 
-
    •         Array improvements, including nulls in arrays
-       
      • 
-
    •         Aggregate-function improvements, including multiple-input
-        aggregates and SQL:2003 statistical functions
-       
      • 
-
    •         Many contrib/ improvements
-       
      • 
-
    
-
    
-
-    
    
-
-
    
-
    
-E.1.2. Migration to version 8.2
    
-
         A dump/restore using pg_dump is
-     required for those wishing to migrate data from any previous
-     release.
-    
    
-
         Observe the following incompatibilities:
-    
    
-
      
-
    • 
-
              Set escape_string_warning
-        to on by default (Bruce)
-       
      
-
              This issues a warning if backslash escapes are used in
-        non-escape (non-E'')
-        strings.
-       
      
-
      • 
-
    • 
-
              Change the row
-        constructor syntax (ROW(...)) so that
-        list elements foo.* will be expanded to a list
-        of their member fields, rather than creating a nested
-        row type field as formerly (Tom)
-       
      
-
              The new behavior is substantially more useful since it
-        allows, for example, triggers to check for data changes
-        with IF row(new.*) IS DISTINCT FROM row(old.*).
-        The old behavior is still available by omitting .*.
-       
      
-
      • 
-
    • 
-
              Make row comparisons
-        follow SQL standard semantics and allow them
-        to be used in index scans (Tom)
-       
      
-
              Previously, row = and <> comparisons followed the
-        standard but < <= > >= did not.  A row comparison
-        can now be used as an index constraint for a multicolumn
-        index matching the row value.
-       
      
-
      • 
-
    • 
-
              Make row IS [NOT] NULL
-        tests follow SQL standard semantics (Tom)
-       
      
-
              The former behavior conformed to the standard for simple cases
-        with IS NULL, but IS NOT NULL would return
-        true if any row field was non-null, whereas the standard says it
-        should return true only when all fields are non-null.
-       
      
-
      • 
-
    • 
-
              Make SET
-        CONSTRAINT affect only one constraint (Kris Jurka)
-       
      
-
              In previous releases, SET CONSTRAINT modified
-        all constraints with a matching name.  In this release,
-        the schema search path is used to modify only the first
-        matching constraint.  A schema specification is also
-        supported.  This more nearly conforms to the SQL standard.
-       
      
-
      • 
-
    • 
-
              Remove RULE permission for tables, for security reasons
-        (Tom)
-       
      
-
              As of this release, only a table's owner can create or modify
-        rules for the table.  For backwards compatibility,
-        GRANT/REVOKE RULE is still accepted,
-        but it does nothing.
-       
      
-
      • 
-
    • 
-
              Array comparison improvements (Tom)
-       
      
-
              Now array dimensions are also compared.
-       
      
-
      • 
-
    • 
-
              Change array concatenation
-        to match documented behavior (Tom)
-       
      
-
              This changes the previous behavior where concatenation
-        would modify the array lower bound.
-       
      
-
      • 
-
    • 
-
              Make command-line options of postmaster
-        and postgres
-        identical (Peter)
-       
      
-
              This allows the postmaster to pass arguments to each backend
-        without using -o.
-       
      
-
      • 
-
    • 
-
              Deprecate use of postmaster symbolic link (Peter)
-       
      
-
              postmaster and postgres
-        commands now act identically, with the behavior determined
-        by command-line options.  The postmaster symbolic link is
-        kept for compatibility, but is not really needed.
-       
      
-
      • 
-
    • 
-
              Change log_duration
-        to output even if the query is not output (Tom)
-       
      
-
              In prior releases, log_duration only printed if
-        the query appeared earlier in the log.
-       
      
-
      • 
-
    • 
-
              Make to_char(time)
-        and to_char(interval)
-        treat HH and HH12 as 12-hour
-        intervals
-       
      
-
              Most applications should use HH24 unless they
-        want a 12-hour display.
-       
      
-
      • 
-
    • 
-
              Zero unmasked bits in conversion from INET to CIDR (Tom)
-       
      
-
              This ensures that the converted value is actually valid for
-        CIDR.
-       
      
-
      • 
-
    • 
-
              Remove australian_timezones configuration variable
-        (Joachim Wieland)
-       
      
-
              This variable has been superseded by a more general facility
-        for configuring timezone abbreviations.
-       
      
-
      • 
-
    • 
-
              Improve cost estimation for nested-loop index scans (Tom)
-       
      
-
              This may eliminate the need to set unrealistically small
-        values of random_page_cost.
-        If you have been using a very small random_page_cost,
-        please recheck your test cases.
-       
      
-
      • 
-
    •         Change libpq
-        PQdsplen() to return a useful value (Martijn
-        van Oosterhout)
-       
      • 
-
    • 
-
              Declare libpq
-        PQgetssl() as returning void *,
-        rather than SSL * (Martijn van Oosterhout)
-       
      
-
              This allows applications to use the function without including
-        the OpenSSL headers.
-       
      
-
      • 
-
    •         C-language loadable modules must now include a
-        PG_MODULE_MAGIC
-        macro call for version compatibility checking
-        (Martijn van Oosterhout)
-       
      • 
-
    • 
-
              For security's sake, modules used by a PL/PerlU function are no
-        longer available to PL/Perl functions (Andrew)
-       
      
-
      
-
      Note
      
-
               This also implies that data can no longer be shared between a PL/Perl
-         function and a PL/PerlU function.
-         Some Perl installations have not been compiled with the correct flags
-         to allow multiple interpreters to exist within a single process.
-         In this situation PL/Perl and PL/PerlU cannot both be used in a
-         single backend. The solution is to get a Perl installation which
-         supports multiple interpreters.
-        
      
-
      
-
      • 
-
    • 
-
              In contrib/xml2/, rename xml_valid() to
-        xml_is_well_formed() (Tom)
-       
      
-
              xml_valid() will remain for backward compatibility,
-        but its behavior will change to do schema checking in a future
-        release.
-       
      
-
      • 
-
    •         Remove contrib/ora2pg/, now at http://www.samse.fr/GPL/ora2pg
-       
      • 
-
    •         Remove contrib modules that have been migrated to PgFoundry:
-        adddepend, dbase, dbmirror,
-        fulltextindex, mac, userlock
-       
      • 
-
    •         Remove abandoned contrib modules:
-        mSQL-interface, tips
-       
      • 
-
    • 
-
              Remove QNX and BEOS ports (Bruce)
-       
      
-
              These ports no longer had active maintainers.
-       
      
-
      • 
-
    
 
    
 
    
 
    
-E.1.3. Changes
    
-
         Below you will find a detailed account of the
-     changes between PostgreSQL 8.2 and
-     the previous major release.
-    
    
-
    
-
    
-E.1.3.1. Performance Improvements
    
+E.1.2. Changes
    
 
      
-
    • 
-
              Allow the planner to reorder outer
-        joins in some circumstances (Tom)
-       
      
-
              In previous releases, outer joins would always be evaluated in
-        the order written in the query. This change allows the
-        query optimizer to consider reordering outer joins, in cases where
-        it can determine that the join order can be changed without
-        altering the meaning of the query.  This can make a
-        considerable performance difference for queries involving
-        multiple outer joins or mixed inner and outer joins.
-       
      
+
    •        Fix crash with SELECT ... LIMIT ALL (also
+       LIMIT NULL) (Tom)
+      
      • 
+
    •        Several /contrib/tsearch2 fixes (Teodor)
+      
      • 
+
    • 
+
             On Windows, make log messages coming from the operating system use
+       ASCII encoding (Hiroshi Saito)
+      
      
+
             This fixes a conversion problem when there is a mismatch between
+       the encoding of the operating system and database server.
+      
      
+
      • 
+
    •        Fix Windows linking of pg_dump using
+       win32.mak
+       (Hiroshi Saito)
+      
      • 
+
    •        Fix planner mistakes for outer join queries (Tom)
+      
      • 
+
    •        Fix several problems in queries involving sub-SELECTs (Tom)
+      
      • 
+
    • 
+
             Fix potential crash in SPI during subtransaction abort (Tom)
+      
      
+
             This affects all PL functions since they all use SPI.
+      
      
+
      • 
+
    •        Improve build speed of PDF documentation (Peter)
+      
      • 
+
    •        Re-add JST (Japan) timezone abbreviation (Tom)
+      
      • 
+
    •        Improve optimization decisions related to index scans (Tom)
+      
      • 
+
    •        Have psql print multi-byte combining characters as
+       before, rather than output as \u (Tom)
+      
      • 
+
    • 
+
             Improve index usage of regular expressions that use parentheses (Tom)
+      
      
+
             This improves psql \d performance also.
+      
      
+
      • 
+
    • 
+
             Make pg_dumpall assume that databases have public
+       CONNECT privilege, when dumping from a pre-8.2 server (Tom)
+      
      
+
             This preserves the previous behavior that anyone can connect to a
+       database if allowed by pg_hba.conf.
+      
      
 
      • 
-
    •         Improve efficiency of IN
-        (list-of-expressions) clauses (Tom)
-       
      • 
-
    •         Improve sorting speed and reduce memory usage (Simon, Tom)
-       
      • 
-
    •         Improve subtransaction performance (Alvaro, Itagaki Takahiro,
-        Tom)
-       
      • 
-
    • 
-
              Add FILLFACTOR to table and index creation (ITAGAKI
-        Takahiro)
-       
      
-
              This leaves extra free space in each table or index page,
-        allowing improved performance as the database grows.  This
-        is particularly valuable to maintain clustering.
-       
      
-
      • 
-
    •         Increase default values for shared_buffers
-        and max_fsm_pages
-        (Andrew)
-       
      • 
-
    • 
-
              Improve locking performance by breaking the lock manager tables into
-        sections
-        (Tom)
-       
      
-
              This allows locking to be more fine-grained, reducing
-        contention.
-       
      
-
      • 
-
    •         Reduce locking requirements of sequential scans (Qingqing
-        Zhou)
-       
      • 
-
    •         Reduce locking required for database creation and destruction
-        (Tom)
-       
      • 
-
    •         Improve the optimizer's selectivity estimates for LIKE, ILIKE, and
-        regular expression
-        operations (Tom)
-       
      • 
-
    •         Improve planning of joins to inherited
-        tables and UNION
-        ALL views (Tom)
-       
      • 
-
    • 
-
              Allow constraint
-        exclusion to be applied to inherited UPDATE and
-        DELETE queries (Tom)
-       
      
-
              SELECT already honored constraint exclusion.
-       
      
-
      • 
-
    •         Improve planning of constant WHERE clauses, such as
-        a condition that depends only on variables inherited from an
-        outer query level (Tom)
-       
      • 
-
    • 
-
              Protocol-level unnamed prepared statements are re-planned
-        for each set of BIND values (Tom)
-       
      
-
              This improves performance because the exact parameter values
-        can be used in the plan.
-       
      
-
      • 
-
    •         Speed up vacuuming of B-Tree indexes (Heikki Linnakangas,
-        Tom)
-       
      • 
-
    •         Avoid extra scan of tables without indexes during VACUUM (Greg Stark)
-       
      • 
-
    •         Improve multicolumn GiST
-        indexing (Oleg, Teodor)
-       
      • 
-
    •         Remove dead index entries before B-Tree page split (Junji
-        Teramoto)
-       
      • 
 
    
 
-
    
-
    
-E.1.3.2. Server Changes
    
-
      
-
    • 
-
              Allow a forced switch to a new transaction log file (Simon, Tom)
-       
      
-
              This is valuable for keeping warm standby slave servers
-        in sync with the master.  Transaction log file switching now also happens
-        automatically during pg_stop_backup().
-        This ensures that all
-        transaction log files needed for recovery can be archived immediately.
-       
      
-
      • 
-
    • 
-
              Add WAL informational functions (Simon)
-       
      
-
              Add functions for interrogating the current transaction log insertion
-        point and determining WAL filenames from the
-        hex WAL locations displayed by pg_stop_backup()
-        and related functions.
-       
      
-
      • 
-
    • 
-
              Improve recovery from a crash during WAL replay (Simon)
-       
      
-
              The server now does periodic checkpoints during WAL
-        recovery, so if there is a crash, future WAL
-        recovery is shortened.  This also eliminates the need for
-        warm standby servers to replay the entire log since the
-        base backup if they crash.
-       
      
-
      • 
-
    • 
-
              Improve reliability of long-term WAL replay
-        (Heikki, Simon, Tom)
-       
      
-
              Formerly, trying to roll forward through more than 2 billion
-        transactions would not work due to XID wraparound.  This meant
-        warm standby servers had to be reloaded
-        from fresh base backups periodically.
-       
      
-
      • 
-
    • 
-
              Add archive_timeout
-        to force transaction log file switches at a given interval (Simon)
-       
      
-
              This enforces a maximum replication delay for warm standby servers.
-       
      
-
      • 
-
    • 
-
              Add native LDAP
-        authentication (Magnus Hagander)
-       
      
-
              This is particularly useful for platforms that do not
-        support PAM, such as Win32.
-       
      
-
      • 
-
    • 
-
              Add GRANT
-        CONNECT ON DATABASE (Gevik Babakhani)
-       
      
-
              This gives SQL-level control over database access.  It works as
-        an additional filter on top of the existing
-        pg_hba.conf
-        controls.
-       
      
-
      • 
-
    • 
-
              Add support for SSL
-        Certificate Revocation List (CRL) files
-        (Libor Hoho[scaron])
-       
      
-
              The server and libpq both recognize CRL
-        files now.
-       
      
-
      • 
-
    •         GiST indexes are
-        now clusterable (Teodor)
-       
      • 
-
    • 
-
              Remove routine autovacuum server log entries (Bruce)
-       
      
-
              pg_stat_activity
-        now shows autovacuum activity.
-       
      
-
      • 
-
    • 
-
              Track maximum XID age within individual tables, instead of whole databases (Alvaro)
-       
      
-
              This reduces the overhead involved in preventing transaction
-        ID wraparound, by avoiding unnecessary VACUUMs.
-       
      
-
      • 
-
    • 
-
              Add last vacuum and analyze timestamp columns to the stats
-        collector (Larry Rosenman)
-       
      
-
              These values now appear in the pg_stat_*_tables
-        system views.
-       
      
-
      • 
-
    • 
-
              Improve performance of statistics monitoring, especially
-        stats_command_string
-        (Tom, Bruce)
-       
      
-
              This release enables stats_command_string by
-        default, now that its overhead is minimal.  This means
-        pg_stat_activity
-        will now show all active queries by default.
-       
      
-
      • 
-
    • 
-
              Add a waiting column to pg_stat_activity
-        (Tom)
-       
      
-
              This allows pg_stat_activity to show all the
-        information included in the ps display.
-       
      
-
      • 
-
    • 
-
              Add configuration parameter update_process_title
-        to control whether the ps display is updated
-        for every command (Bruce)
-       
      
-
              On platforms where it is expensive to update the ps
-        display, it may be worthwhile to turn this off and rely solely on
-        pg_stat_activity for status information.
-       
      
-
      • 
-
    • 
-
              Allow units to be specified in configuration settings
-        (Peter)
-       
      
-
              For example, you can now set shared_buffers
-        to 32MB rather than mentally converting sizes.
-       
      
-
      • 
-
    •         Add support for include
-        directives in postgresql.conf (Joachim
-        Wieland)
-       
      • 
-
    • 
-
              Improve logging of protocol-level prepare/bind/execute
-        messages (Bruce, Tom)
-       
      
-
              Such logging now shows statement names, bind parameter
-        values, and the text of the query being executed.  Also,
-        the query text is properly included in logged error messages
-        when enabled by log_min_error_statement.
-       
      
-
      • 
-
    • 
-
              Prevent max_stack_depth
-        from being set to unsafe values
-       
      
-
              On platforms where we can determine the actual kernel stack depth
-        limit (which is most), make sure that the initial default value of
-        max_stack_depth is safe, and reject attempts to set it
-        to unsafely large values.
-       
      
-
      • 
-
    • 
-
              Enable highlighting of error location in query in more
-        cases (Tom)
-       
      
-
              The server is now able to report a specific error location for
-        some semantic errors (such as unrecognized column name), rather
-        than just for basic syntax errors as before.
-       
      
-
      • 
-
    •         Fix “failed to re-find parent key” errors in
-        VACUUM (Tom)
-       
      • 
-
    • 
-
              Clean out pg_internal.init cache files during server
-        restart (Simon)
-       
      
-
              This avoids a hazard that the cache files might contain stale
-        data after PITR recovery.
-       
      
-
      • 
-
    •         Fix race condition for truncation of a large relation across a
-        gigabyte boundary by VACUUM (Tom)
-       
      • 
-
    •         Fix bug causing needless deadlock errors on row-level locks (Tom)
-       
      • 
-
    •         Fix bugs affecting multi-gigabyte hash indexes (Tom)
-       
      • 
-
    • 
-
              Each backend process is now its own process group leader (Tom)
-       
      
-
              This allows query cancel to abort subprocesses invoked from a
-        backend or archive/recovery process.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.3. Query Changes
    
-
      
-
    • 
-
              Add INSERT/UPDATE/DELETE
-        RETURNING (Jonah Harris, Tom)
-       
      
-
              This allows these commands to return values, such as the
-        computed serial key for a new row.  In the UPDATE
-        case, values from the updated version of the row are returned.
-       
      
-
      • 
-
    • 
-
              Add support for multiple-row VALUES clauses,
-        per SQL standard (Joe, Tom)
-       
      
-
              This allows INSERT to insert multiple rows of
-        constants, or queries to generate result sets using constants.
-        For example, INSERT ...  VALUES (...), (...),
-        ...., and SELECT * FROM (VALUES (...), (...),
-        ....) AS alias(f1, ...).
-       
      
-
      • 
-
    • 
-
              Allow UPDATE
-        and DELETE
-        to use an alias for the target table (Atsushi Ogawa)
-       
      
-
              The SQL standard does not permit an alias in these commands, but
-        many database systems allow one anyway for notational convenience.
-       
      
-
      • 
-
    • 
-
              Allow UPDATE
-        to set multiple columns with a list of values (Susanne
-        Ebrecht)
-       
      
-
              This is basically a short-hand for assigning the columns
-        and values in pairs.  The syntax is UPDATE tab
-        SET (column, ...) = (val, ...).
-       
      
-
      • 
-
    • 
-
              Make row comparisons work per standard (Tom)
-       
      
-
              The forms <, <=, >, >= now compare rows lexicographically,
-        that is, compare the first elements, if equal compare the second
-        elements, and so on.  Formerly they expanded to an AND condition
-        across all the elements, which was neither standard nor very useful.
-       
      
-
      • 
-
    • 
-
              Add CASCADE
-        option to TRUNCATE (Joachim Wieland)
-       
      
-
              This causes TRUNCATE to automatically include all tables
-        that reference the specified table(s) via foreign keys.  While
-        convenient, this is a dangerous tool — use with caution!
-       
      
-
      • 
-
    •         Support FOR UPDATE and FOR SHARE
-        in the same SELECT
-        command (Tom)
-       
      • 
-
    • 
-
              Add IS NOT
-        DISTINCT FROM (Pavel Stehule)
-       
      
-
              This operator is similar to equality (=), but
-        evaluates to true when both left and right operands are
-        NULL, and to false when just one is, rather than
-        yielding NULL in these cases.
-       
      
-
      • 
-
    • 
-
              Improve the length output used by UNION/INTERSECT/EXCEPT
-        (Tom)
-       
      
-
              When all corresponding columns are of the same defined length, that
-        length is used for the result, rather than a generic length.
-       
      
-
      • 
-
    • 
-
              Allow ILIKE
-        to work for multi-byte encodings (Tom)
-       
      
-
              Internally, ILIKE now calls lower()
-        and then uses LIKE.  Locale-specific regular
-        expression patterns still do not work in these encodings.
-       
      
-
      • 
-
    • 
-
              Enable standard_conforming_strings
-        to be turned on (Kevin Grittner)
-       
      
-
              This allows backslash escaping in strings to be disabled,
-        making PostgreSQL more
-        standards-compliant.  The default is off for backwards
-        compatibility, but future releases will default this to on.
-       
      
-
      • 
-
    • 
-
              Do not flatten subqueries that contain volatile
-        functions in their target lists (Jaime Casanova)
-       
      
-
              This prevents surprising behavior due to multiple evaluation
-        of a volatile function (such as random()
-        or nextval()).  It may cause performance
-        degradation in the presence of functions that are unnecessarily
-        marked as volatile.
-       
      
-
      • 
-
    • 
-
              Add system views pg_prepared_statements
-        and pg_cursors
-        to show prepared statements and open cursors (Joachim Wieland, Neil)
-       
      
-
              These are very useful in pooled connection setups.
-       
      
-
      • 
-
    • 
-
              Support portal parameters in EXPLAIN and EXECUTE (Tom)
-       
      
-
              This allows, for example, JDBC ? parameters to
-        work in these commands.
-       
      
-
      • 
-
    • 
-
              If SQL-level PREPARE parameters
-        are unspecified, infer their types from the content of the
-        query (Neil)
-       
      
-
              Protocol-level PREPARE already did this.
-       
      
-
      • 
-
    •         Allow LIMIT and OFFSET to exceed
-        two billion (Dhanaraj M)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.4. Object Manipulation Changes
    
-
      
-
    • 
-
              Add TABLESPACE clause to CREATE TABLE AS
-        (Neil)
-       
      
-
              This allows a tablespace to be specified for the new table.
-       
      
-
      • 
-
    • 
-
              Add ON COMMIT clause to CREATE TABLE AS
-        (Neil)
-       
      
-
              This allows temporary tables to be truncated or dropped on
-        transaction commit.  The default behavior is for the table
-        to remain until the session ends.
-       
      
-
      • 
-
    • 
-
              Add INCLUDING CONSTRAINTS to CREATE TABLE LIKE
-        (Greg Stark)
-       
      
-
              This allows easy copying of CHECK constraints to a new
-        table.
-       
      
-
      • 
-
    • 
-
              Allow the creation of placeholder (shell) types (Martijn van Oosterhout)
-       
      
-
              A shell type declaration creates a type name, without specifying
-        any of the details of the type.  Making a shell type is useful
-        because it allows cleaner declaration of the type's input/output
-        functions, which must exist before the type can be defined “for
-        real”.  The syntax is CREATE TYPE typename.
-       
      
-
      • 
-
    •         Aggregate functions
-        now support multiple input parameters (Sergey Koposov, Tom)
-       
      • 
-
    • 
-
              Add new aggregate creation syntax (Tom)
-       
      
-
              The new syntax is CREATE AGGREGATE
-        aggname (input_type)
-        (parameter_list).  This more
-        naturally supports the new multi-parameter aggregate
-        functionality.  The previous syntax is still supported.
-       
      
-
      • 
-
    •         Add ALTER ROLE PASSWORD NULL
-        to remove a previously set role password (Peter)
-       
      • 
-
    • 
-
              Add DROP object IF EXISTS for many
-        object types (Andrew)
-       
      
-
              This allows DROP operations on non-existent
-        objects without generating an error.
-       
      
-
      • 
-
    •         Add DROP OWNED
-        to drop all objects owned by a role (Alvaro)
-       
      • 
-
    • 
-
              Add REASSIGN
-        OWNED to reassign ownership of all objects owned
-        by a role (Alvaro)
-       
      
-
              This, and DROP OWNED above, facilitate dropping
-        roles.
-       
      
-
      • 
-
    • 
-
              Add GRANT ON SEQUENCE
-        syntax (Bruce)
-       
      
-
              This was added for setting sequence-specific permissions.
-        GRANT ON TABLE for sequences is still supported
-        for backward compatibility.
-       
      
-
      • 
-
    • 
-
              Add USAGE
-        permission for sequences that allows only currval()
-        and nextval(), not setval()
-        (Bruce)
-       
      
-
              USAGE permission allows more fine-grained
-        control over sequence access.  Granting USAGE
-        allows users to increment
-        a sequence, but prevents them from setting the sequence to
-        an arbitrary value using setval().
-       
      
-
      • 
-
    • 
-
              Add ALTER TABLE
-        [ NO ] INHERIT (Greg Stark)
-       
      
-
              This allows inheritance to be adjusted dynamically, rather than
-        just at table creation and destruction.  This is very valuable
-        when using inheritance to implement table partitioning.
-       
      
-
      • 
-
    • 
-
              Allow comments on global
-        objects to be stored globally (Kris Jurka)
-       
      
-
              Previously, comments attached to databases were stored in individual
-        databases, making them ineffective, and there was no provision
-        at all for comments on roles or tablespaces.  This change adds a new
-        shared catalog pg_shdescription
-        and stores comments on databases, roles, and tablespaces therein.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.5. Utility Command Changes
    
-
      
-
    • 
-
              Add option to allow indexes to be created without blocking
-        concurrent writes to the table (Greg Stark, Tom)
-       
      
-
              The new syntax is CREATE
-        INDEX CONCURRENTLY.  The default behavior is
-        still to block table modification while a index is being
-        created.
-       
      
-
      • 
-
    • 
-
              Provide advisory
-        locking functionality (Abhijit Menon-Sen, Tom)
-       
      
-
              This is a new locking API designed to replace what used to be
-        in /contrib/userlock.  The userlock code is now on pgfoundry.
-       
      
-
      • 
-
    • 
-
              Allow COPY to
-        dump a SELECT query (Zoltan Boszormenyi, Karel
-        Zak)
-       
      
-
              This allows COPY to dump arbitrary SQL
-        queries. The syntax is COPY (SELECT ...) TO.
-       
      
-
      • 
-
    •         Make the COPY
-        command return a command tag that includes the number of
-        rows copied (Volkan YAZICI)
-       
      • 
-
    •         Allow VACUUM
-        to expire rows without being affected by other concurrent
-        VACUUM operations (Hannu Krossing, Alvaro, Tom)
-       
      • 
-
    • 
-
              Make initdb
-        detect the operating system locale and set the default
-        DateStyle accordingly (Peter)
-       
      
-
              This makes it more likely that the installed
-        postgresql.conf DateStyle value will
-        be as desired.
-       
      
-
      • 
-
    •         Reduce number of progress messages displayed by initdb (Tom)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.6. Date/Time Changes
    
-
      
-
    • 
-
              Allow full timezone names in timestamp input values
-        (Joachim Wieland)
-       
      
-
              For example, '2006-05-24 21:11
-        America/New_York'::timestamptz.
-       
      
-
      • 
-
    • 
-
              Support configurable timezone abbreviations (Joachim Wieland)
-       
      
-
              A desired set of timezone abbreviations can be chosen via the
-        configuration parameter timezone_abbreviations.
-       
      
-
      • 
-
    •         Add pg_timezone_abbrevs
-        and pg_timezone_names
-        views to show supported timezones (Magnus Hagander)
-       
      • 
-
    • 
-
              Add clock_timestamp(),
-        statement_timestamp(),
-        and transaction_timestamp()
-        (Bruce)
-       
      
-
              clock_timestamp() is the current wall-clock time,
-        statement_timestamp() is the time the current
-        statement arrived at the server, and
-        transaction_timestamp() is an alias for
-        now().
-       
      
-
      • 
-
    •         Allow to_char()
-        to print localized month and day names (Euler Taveira de
-        Oliveira)
-       
      • 
-
    • 
-
              Allow to_char(time)
-        and to_char(interval)
-        to output AM/PM specifications
-        (Bruce)
-       
      
-
              Intervals and times are treated as 24-hour periods, e.g.
-        25 hours is considered AM.
-       
      
-
      • 
-
    •         Add new function justify_interval()
-        to adjust interval units (Mark Dilger)
-       
      • 
-
    • 
-
              Allow timezone offsets up to 14:59 away from GMT
-       
      
-
              Kiribati uses GMT+14, so we'd better accept that.
-       
      
-
      • 
-
    •         Interval computation improvements (Michael Glaesemann, Bruce)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.7. Other Data Type and Function Changes
    
-
      
-
    •         Allow arrays to contain NULL elements (Tom)
-       
      • 
-
    • 
-
              Allow assignment to array elements not contiguous with the existing
-        entries (Tom)
-       
      
-
              The intervening array positions will be filled with nulls.
-        This is per SQL standard.
-       
      
-
      • 
-
    • 
-
              New built-in operators
-        for array-subset comparisons (@>,
-        <@, &&) (Teodor, Tom)
-       
      
-
              These operators can be indexed for many data types using
-        GiST or GIN indexes.
-       
      
-
      • 
-
    • 
-
              Add convenient arithmetic operations on
-        INET/CIDR values (Stephen R. van den
-        Berg)
-       
      
-
              The new operators are & (and), |
-        (or), ~ (not), inet + int8,
-        inet - int8, and
-        inet - inet.
-       
      
-
      • 
-
    • 
-
              Add new aggregate functions
-        from SQL:2003 (Neil)
-       
      
-
              The new functions are var_pop(),
-        var_samp(), stddev_pop(), and
-        stddev_samp().  var_samp() and
-        stddev_samp() are merely renamings of the
-        existing aggregates variance() and
-        stddev().  The latter names remain available
-        for backward compatibility.
-       
      
-
      • 
-
    • 
-
              Add SQL:2003 statistical aggregates
-        (Sergey Koposov)
-       
      
-
              New functions:  regr_intercept(),
-        regr_slope(), regr_r2(),
-        corr(), covar_samp(),
-        covar_pop(), regr_avgx(),
-        regr_avgy(), regr_sxy(),
-        regr_sxx(), regr_syy(),
-        regr_count().
-       
      
-
      • 
-
    •         Allow domains to be
-        based on other domains (Tom)
-       
      • 
-
    • 
-
              Properly enforce domain CHECK constraints
-        everywhere (Neil, Tom)
-       
      
-
              For example, the result of a user-defined function that is
-        declared to return a domain type is now checked against the
-        domain's constraints. This closes a significant hole in the domain
-        implementation.
-       
      
-
      • 
-
    • 
-
              Fix problems with dumping renamed SERIAL columns
-        (Tom)
-       
      
-
              The fix is to dump a SERIAL column by explicitly
-        specifying its DEFAULT and sequence elements,
-        and reconstructing the SERIAL column on reload
-        using a new ALTER
-        SEQUENCE OWNED BY command.  This also allows
-        dropping a SERIAL column specification.
-       
      
-
      • 
-
    •         Add a server-side sleep function pg_sleep()
-        (Joachim Wieland)
-       
      • 
-
    •         Add all comparison operators for the tid (tuple id) data
-        type (Mark Kirkwood, Greg Stark, Tom)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.8. PL/PgSQL Server-Side Language Changes
    
-
      
-
    • 
-
              Add TG_table_name and TG_table_schema to
-        trigger parameters (Andrew)
-       
      
-
              TG_relname is now deprecated.  Comparable
-        changes have been made in the trigger parameters for the other
-        PLs as well.
-       
      
-
      • 
-
    •         Allow FOR statements to return values to scalars
-        as well as records and row types (Pavel Stehule)
-       
      • 
-
    •         Add a BY clause to the FOR loop,
-        to control the iteration increment (Jaime Casanova)
-       
      • 
-
    • 
-
              Add STRICT to SELECT
-        INTO (Matt Miller)
-       
      
-
              STRICT mode throws an exception if more or less
-        than one row is returned by the SELECT, for
-        Oracle PL/SQL compatibility.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.9. PL/Perl Server-Side Language Changes
    
-
      
-
    •         Add table_name and table_schema to
-        trigger parameters (Adam Sj[oslash]gren)
-       
      • 
-
    •         Add prepared queries (Dmitry Karasik)
-       
      • 
-
    • 
-
              Make $_TD trigger data a global variable (Andrew)
-       
      
-
              Previously, it was lexical, which caused unexpected sharing
-        violations.
-       
      
-
      • 
-
    • 
-
              Run PL/Perl and PL/PerlU in separate interpreters, for security
-        reasons (Andrew)
-       
      
-
              In consequence, they can no longer share data nor loaded modules.
-        Also, if Perl has not been compiled with the requisite flags to
-        allow multiple interpreters, only one of these languages can be used
-        in any given backend process.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.10. PL/Python Server-Side Language Changes
    
-
      
-
    •         Named parameters are passed as ordinary variables, as well as in the
-        args[] array (Sven Suursoho)
-       
      • 
-
    •         Add table_name and table_schema to
-        trigger parameters (Andrew)
-       
      • 
-
    •         Allow returning of composite types and result sets (Sven Suursoho)
-       
      • 
-
    •         Return result-set as list, iterator,
-        or generator (Sven Suursoho)
-       
      • 
-
    •         Allow functions to return void (Neil)
-       
      • 
-
    •         Python 2.5 is now supported (Tom)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.11. psql Changes
    
-
      
-
    •         Add new command \password for changing role
-        password with client-side password encryption (Peter)
-       
      • 
-
    •         Allow \c to connect to a new host and port
-        number (David, Volkan YAZICI)
-       
      • 
-
    •         Add tablespace display to \l+ (Philip Yarra)
-       
      • 
-
    •         Improve \df slash command to include the argument
-        names and modes (OUT or INOUT) of
-        the function (David Fetter)
-       
      • 
-
    •         Support binary COPY (Andreas Pflug)
-       
      • 
-
    • 
-
              Add option to run the entire session in a single transaction
-        (Simon)
-       
      
-
              Use option -1 or --single-transaction.
-       
      
-
      • 
-
    • 
-
              Support for automatically retrieving SELECT
-        results in batches using a cursor (Chris Mair)
-       
      
-
              This is enabled using \set FETCH_COUNT
-        n. This
-        feature allows large result sets to be retrieved in
-        psql without attempting to buffer the entire
-        result set in memory.
-       
      
-
      • 
-
    • 
-
              Make multi-line values align in the proper column
-        (Martijn van Oosterhout)
-       
      
-
              Field values containing newlines are now displayed in a more
-        readable fashion.
-       
      
-
      • 
-
    • 
-
              Save multi-line statements as a single entry, rather than
-        one line at a time (Sergey E. Koposov)
-       
      
-
              This makes up-arrow recall of queries easier.  (This is
-        not available on Win32, because that platform uses the native
-        command-line editing present in the operating system.)
-       
      
-
      • 
-
    •         Make the line counter 64-bit so it can handle files with more
-        than two billion lines (David Fetter)
-       
      • 
-
    •         Report both the returned data and the command status tag
-        for INSERT/UPDATE/DELETE
-        RETURNING (Tom)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.12. pg_dump Changes
    
-
      
-
    • 
-
              Allow complex selection of objects to be included or excluded
-        by pg_dump (Greg Sabino Mullane)
-       
      
-
              pg_dump now supports multiple -n
-        (schema) and -t (table) options, and adds
-        -N and -T options to exclude objects.
-        Also, the arguments of these switches can now be wild-card expressions
-        rather than single object names, for example
-        -t 'foo*', and a schema can be part of
-        a -t or -T switch, for example
-        -t schema1.table1.
-       
      
-
      • 
-
    •         Add pg_restore
-        --no-data-for-failed-tables option to suppress
-        loading data if table creation failed (i.e., the table already
-        exists) (Martin Pitt)
-       
      • 
-
    • 
-
              Add pg_restore
-        option to run the entire session in a single transaction
-        (Simon)
-       
      
-
              Use option -1 or --single-transaction.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.13. libpq Changes
    
-
      
-
    • 
-
              Add PQencryptPassword()
-        to encrypt passwords (Tom)
-       
      
-
              This allows passwords to be sent pre-encrypted for commands
-        like ALTER ROLE ...
-        PASSWORD.
-       
      
-
      • 
-
    • 
-
              Add function PQisthreadsafe()
-        (Bruce)
-       
      
-
              This allows applications to query the thread-safety status
-        of the library.
-       
      
-
      • 
-
    •         Add PQdescribePrepared(),
-        PQdescribePortal(),
-        and related functions to return information about previously
-        prepared statements and open cursors (Volkan YAZICI)
-       
      • 
-
    •         Allow LDAP lookups
-        from pg_service.conf
-        (Laurenz Albe)
-       
      • 
-
    • 
-
              Allow a hostname in ~/.pgpass
-        to match the default socket directory (Bruce)
-       
      
-
              A blank hostname continues to match any Unix-socket connection,
-        but this addition allows entries that are specific to one of
-        several postmasters on the machine.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.14. ecpg Changes
    
-
      
-
    •         Allow SHOW to
-        put its result into a variable (Joachim Wieland)
-       
      • 
-
    •         Add COPY TO STDOUT
-        (Joachim Wieland)
-       
      • 
-
    •         Add regression tests (Joachim Wieland, Michael)
-       
      • 
-
    •         Major source code cleanups (Joachim Wieland, Michael)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.15. Win32 Port
    
-
      
-
    •         Allow MSVC to compile the PostgreSQL
-        server (Magnus, Hiroshi Saito)
-       
      • 
-
    •         Add MSVC support for utility commands and pg_dump (Hiroshi
-        Saito)
-       
      • 
-
    •         Add support for Windows code pages 1253,
-        1254, 1255, and 1257
-        (Kris Jurka)
-       
      • 
-
    •         Drop privileges on startup, so that the server can be started from
-        an administrative account (Magnus)
-       
      • 
-
    •         Stability fixes (Qingqing Zhou, Magnus)
-       
      • 
-
    • 
-
              Add native semaphore implementation (Qingqing Zhou)
-       
      
-
              The previous code mimicked SysV semaphores.
-       
      
-
      • 
-
    
-
    
-
    
-
    
-E.1.3.16. Source Code Changes
    
-
      
-
    •         Add GIN (Generalized
-        Inverted iNdex) index access method (Teodor, Oleg)
-       
      • 
-
    • 
-
              Remove R-tree indexing (Tom)
-       
      
-
              Rtree has been re-implemented using GiST. Among other
-        differences, this means that rtree indexes now have support
-        for crash recovery via write-ahead logging (WAL).
-       
      
-
      • 
-
    •         Reduce libraries needlessly linked into the backend (Martijn
-        van Oosterhout, Tom)
-       
      • 
-
    • 
-
              Add a configure flag to allow libedit to be preferred over
-        GNU readline (Bruce)
-       
      
-
              Use configure --with-libedit-preferred.
-       
      
-
      • 
-
    •         Allow installation into directories containing spaces
-        (Peter)
-       
      • 
-
    •         Improve ability to relocate installation directories (Tom)
-       
      • 
-
    •         Add support for Solaris x86_64 using the
-        Solaris compiler (Pierre Girard, Theo
-        Schlossnagle, Bruce)
-       
      • 
-
    •         Add DTrace support (Robert Lor)
-       
      • 
-
    •         Add PG_VERSION_NUM for use by third-party
-        applications wanting to test the backend version in C using >
-        and < comparisons (Bruce)
-       
      • 
-
    •         Add XLOG_BLCKSZ as independent from BLCKSZ
-        (Mark Wong)
-       
      • 
-
    •         Add LWLOCK_STATS define to report locking
-        activity (Tom)
-       
      • 
-
    •         Emit warnings for unknown configure options
-        (Martijn van Oosterhout)
-       
      • 
-
    • 
-
              Add server support for “plugin” libraries
-        that can be used for add-on tasks such as debugging and performance
-        measurement (Korry Douglas)
-       
      
-
              This consists of two features: a table of “rendezvous
-        variables” that allows separately-loaded shared libraries to
-        communicate, and a new configuration parameter local_preload_libraries
-        that allows libraries to be loaded into specific sessions without
-        explicit cooperation from the client application.  This allows
-        external add-ons to implement features such as a PL/PgSQL debugger.
-       
      
-
      • 
-
    • 
-
              Rename existing configuration parameter
-        preload_libraries to shared_preload_libraries
-        (Tom)
-       
      
-
              This was done for clarity in comparison to
-        local_preload_libraries.
-       
      
-
      • 
-
    • 
-
              Add new configuration parameter server_version_num
-        (Greg Sabino Mullane)
-       
      
-
              This is like server_version, but is an
-        integer, e.g.  80200. This allows applications to
-        make version checks more easily.
-       
      
-
      • 
-
    •         Add a configuration parameter seq_page_cost
-        (Tom)
-       
      • 
-
    •         Re-implement the regression test script as a C program
-        (Magnus, Tom)
-       
      • 
-
    •         Allow loadable modules to allocate shared memory and
-        lightweight locks (Marc Munro)
-       
      • 
-
    • 
-
              Add automatic initialization and finalization of dynamically
-        loaded libraries (Ralf Engelschall, Tom)
-       
      
-
              New functions
-        _PG_init() and _PG_fini() are
-        called if the library defines such symbols.  Hence we no
-        longer need to specify an initialization function in
-        shared_preload_libraries; we can assume that
-        the library used the _PG_init() convention
-        instead.
-       
      
-
      • 
-
    • 
-
              Add PG_MODULE_MAGIC
-        header block to all shared object files (Martijn van
-        Oosterhout)
-       
      
-
              The magic block prevents version mismatches between loadable object
-        files and servers.
-       
      
-
      • 
-
    •          Add shared library support for AIX (Laurenz Albe)
-       
      • 
-
    •         New XML
-        documentation section (Bruce)
-       
      • 
-
    
-
    
-
    
-
    
-E.1.3.17. Contrib Changes
    
-
      
-
    • 
-
              Major tsearch2 improvements (Oleg, Teodor)
-       
      
-
        
-
      •           multibyte encoding support, including UTF8
-         
        • 
-
      •           query rewriting support
-         
        • 
-
      •           improved ranking functions
-         
        • 
-
      •           thesaurus dictionary support
-         
        • 
-
      •           Ispell dictionaries now recognize MySpell
-          format, used by OpenOffice
-         
        • 
-
      •           GIN support
-         
        • 
-
      
-
      • 
-
    • 
-
              Add adminpack module containing Pgadmin administration
-        functions (Dave)
-       
      
-
              These functions provide additional file system access
-        routines not present in the default PostgreSQL
-        server.
-       
      
-
      • 
-
    • 
-
              Add sslinfo module (Victor Wagner)
-       
      
-
              Reports information about the current connection's SSL
-        certificate.
-       
      
-
      • 
-
    • 
-
              Add pgrowlocks module (Tatsuo)
-       
      
-
              This shows row locking information for a specified table.
-       
      
-
      • 
-
    •         Add hstore module (Oleg, Teodor)
-       
      • 
-
    • 
-
              Add isn module, replacing isbn_issn (Jeremy Kronuz)
-       
      
-
              This new implementation supports EAN13, UPC,
-        ISBN (books), ISMN (music), and
-        ISSN (serials).
-       
      
-
      • 
-
    •         Add index information functions to pgstattuple (ITAGAKI Takahiro,
-        Satoshi Nagayasu)
-       
      • 
-
    •         Add pg_freespacemap module to display free space map information
-        (Mark Kirkwood)
-       
      • 
-
    • 
-
              pgcrypto now has all planned functionality (Marko Kreen)
-       
      
-
        
-
      •           Include iMath library in pgcrypto to have the public-key encryption
-          functions always available.
-         
        • 
-
      •           Add SHA224 algorithm that was missing in OpenBSD code.
-         
        • 
-
      •           Activate builtin code for SHA224/256/384/512 hashes on older
-          OpenSSL to have those algorithms always available.
-         
        • 
-
      •           New function gen_random_bytes() that returns cryptographically strong
-          randomness.  Useful for generating encryption keys.
-         
        • 
-
      •           Remove digest_exists(), hmac_exists() and cipher_exists() functions.
-         
        • 
-
      
-
      • 
-
    • 
-
              Improvements to cube module (Joshua Reich)
-       
      
-
              New functions are cube(float[]),
-        cube(float[], float[]), and
-        cube_subset(cube, int4[]).
-       
      
-
      • 
-
    •         Add async query capability to dblink (Kai Londenberg,
-        Joe Conway)
-       
      • 
-
    • 
-
              New operators for array-subset comparisons (@>,
-        <@, &&) (Tom)
-       
      
-
              Various contrib packages already had these operators for their
-        datatypes, but the naming wasn't consistent.  We have now added
-        consistently named array-subset comparison operators to the core code
-        and all the contrib packages that have such functionality.
-        (The old names remain available, but are deprecated.)
-       
      
-
      • 
-
    •         Add uninstall scripts for all contrib packages that have install
-        scripts (David, Josh Drake)
-       
      • 
-
    
-
    
-
 
 
 
diff --git a/docs/en_US/pg/resources.html b/docs/en_US/pg/resources.html
index dbf432a049..ebed61ee28 100644
--- a/docs/en_US/pg/resources.html
+++ b/docs/en_US/pg/resources.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -20,7 +20,7 @@
   
    
 
    
 
    FAQs
    
-
          The FAQ list  contains
+
          The FAQ list  contains
       continuously updated answers to frequently asked questions.
      
    
 
    READMEs
    
diff --git a/docs/en_US/pg/role-attributes.html b/docs/en_US/pg/role-attributes.html
index e8a1866f71..8310f4a415 100644
--- a/docs/en_US/pg/role-attributes.html
+++ b/docs/en_US/pg/role-attributes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
 
     
    
 
    
-
    login privilege
    
+
    login privilege
    
 
    
 
            Only roles that have the LOGIN attribute can be used
         as the initial role name for a database connection.  A role with
@@ -35,7 +35,7 @@
         default, while CREATE ROLE does not.)
        
    
 
    
-
    superuser status
    
+
    superuser status
    
 
            A database superuser bypasses all permission checks.  This is a
         dangerous privilege and should not be used carelessly; it is best
         to do most of your work as a role that is not a superuser.
@@ -43,13 +43,13 @@
         name SUPERUSER.  You must do
         this as a role that is already a superuser.
        
    
-
    database creation
    
+
    database creation
    
 
            A role must be explicitly given permission to create databases
         (except for superusers, since those bypass all permission
         checks). To create such a role, use CREATE ROLE
         name CREATEDB.
        
    
-
    role creation
    
+
    role creation
    
 
            A role must be explicitly given permission to create more roles
         (except for superusers, since those bypass all permission
         checks). To create such a role, use CREATE ROLE
@@ -60,7 +60,7 @@
         superuser role, superuser status is required;
         CREATEROLE is not sufficient for that.
        
    
-
    password
    
+
    password
    
 
            A password is only significant if the client authentication
         method requires the user to supply a password when connecting
         to the database. The password,
@@ -74,7 +74,7 @@
 
    
 
     A role's attributes can be modified after creation with
-    ALTER ROLE.
+    ALTER ROLE.
     See the reference pages for the CREATE ROLE and ALTER ROLE commands for details.
    
    
 
    
diff --git a/docs/en_US/pg/role-membership.html b/docs/en_US/pg/role-membership.html
index a5e14660fb..e844c27f1e 100644
--- a/docs/en_US/pg/role-membership.html
+++ b/docs/en_US/pg/role-membership.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 18.4. Role Membership
    
-
       It is frequently convenient to group users together to ease
+
       It is frequently convenient to group users together to ease
    management of privileges: that way, privileges can be granted to, or
    revoked from, a group as a whole.  In PostgreSQL
    this is done by creating a role that represents the group, and then
diff --git a/docs/en_US/pg/routine-reindex.html b/docs/en_US/pg/routine-reindex.html
index aa2ddbead8..3dfbcb2dbf 100644
--- a/docs/en_US/pg/routine-reindex.html
+++ b/docs/en_US/pg/routine-reindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 22.2. Routine Reindexing
    
-
       In some situations it is worthwhile to rebuild indexes periodically
+
       In some situations it is worthwhile to rebuild indexes periodically
    with the REINDEX
    command.
   
    
diff --git a/docs/en_US/pg/rowtypes.html b/docs/en_US/pg/rowtypes.html
index 75fd1188b8..7706b9cf9f 100644
--- a/docs/en_US/pg/rowtypes.html
+++ b/docs/en_US/pg/rowtypes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 8.11. Composite Types
    
-
      A composite type describes the structure of a row or record;
+
      A composite type describes the structure of a row or record;
   it is in essence just a list of field names and their data types.
   PostgreSQL allows values of composite types to be
   used in many of the same ways that simple types can be used.  For example, a
@@ -22,7 +22,7 @@
  
    
 
    
 
    
-8.11.1. Declaration of Composite Types
    
+8.11.1. Declaration of Composite Types
    
 
      Here are two simple examples of defining composite types:
 
    
 
    CREATE TYPE complex AS (
@@ -86,8 +86,8 @@
 
    
 
    
 
    
-8.11.2. Composite Value Input
    
-
       To write a composite value as a literal constant, enclose the field
+8.11.2. Composite Value Input
    
+
       To write a composite value as a literal constant, enclose the field
    values within parentheses and separate them by commas.  You may put double
    quotes around any field value, and must do so if it contains commas or
    parentheses.  (More details appear below.)  Thus, the general format of a
@@ -137,7 +137,7 @@
 
    
 
    
 
    
-8.11.3. Accessing Composite Types
    
+8.11.3. Accessing Composite Types
    
 
      To access a field of a composite column, one writes a dot and the field
   name, much like selecting a field from a table name.  In fact, it's so
   much like selecting from a table name that you often have to use parentheses
@@ -179,7 +179,7 @@
 
 
    
 
    
-8.11.4. Modifying Composite Types
    
+8.11.4. Modifying Composite Types
    
 
      Here are some examples of the proper syntax for inserting and updating
   composite columns.
   First, inserting or updating a whole column:
@@ -216,7 +216,7 @@
 
 
    
 
    
-8.11.5. Composite Type Input and Output Syntax
    
+8.11.5. Composite Type Input and Output Syntax
    
 
       The external text representation of a composite value consists of items that
    are interpreted according to the I/O conversion rules for the individual
    field types, plus decoration that indicates the composite structure.
diff --git a/docs/en_US/pg/rule-system.html b/docs/en_US/pg/rule-system.html
index 317c81c7dc..375a799550 100644
--- a/docs/en_US/pg/rule-system.html
+++ b/docs/en_US/pg/rule-system.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/rules-privileges.html b/docs/en_US/pg/rules-privileges.html
index c712b90e2d..d60ae426e6 100644
--- a/docs/en_US/pg/rules-privileges.html
+++ b/docs/en_US/pg/rules-privileges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 35.4. Rules and Privileges
    
-
        Due to rewriting of queries by the PostgreSQL
+
        Due to rewriting of queries by the PostgreSQL
     rule system, other tables/views than those used in the original
     query get accessed. When update rules are used, this can include write access
     to tables.
    
diff --git a/docs/en_US/pg/rules-status.html b/docs/en_US/pg/rules-status.html
index a52aca07de..95dfd84cca 100644
--- a/docs/en_US/pg/rules-status.html
+++ b/docs/en_US/pg/rules-status.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/rules-triggers.html b/docs/en_US/pg/rules-triggers.html
index 32f7de2ccc..1dead238ed 100644
--- a/docs/en_US/pg/rules-triggers.html
+++ b/docs/en_US/pg/rules-triggers.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 35.6. Rules versus Triggers
    
-
        Many things that can be done using triggers can also be
+
        Many things that can be done using triggers can also be
     implemented using the PostgreSQL
     rule system.  One of the things that cannot be implemented by
     rules are some kinds of constraints, especially foreign keys. It is possible
diff --git a/docs/en_US/pg/rules-update.html b/docs/en_US/pg/rules-update.html
index 8eccf6c55e..8d7d090d81 100644
--- a/docs/en_US/pg/rules-update.html
+++ b/docs/en_US/pg/rules-update.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 35.3. Rules on INSERT, UPDATE, and DELETE
    
-
        Rules that are defined on INSERT, UPDATE,
+
        Rules that are defined on INSERT, UPDATE,
     and DELETE are significantly different from the view rules
     described in the previous section. First, their CREATE
     RULE command allows more:
@@ -39,7 +39,7 @@
     original one.
    
 
    
 
    
-35.3.1. How Update Rules Work
    
+35.3.1. How Update Rules Work
    
 
        Keep the syntax
 
 
    
@@ -124,7 +124,7 @@
     there is no need to apply update rules to the output of view rewriting.
    
 
    
 
    
-35.3.1.1. A First Rule Step by Step
    
+35.3.1.1. A First Rule Step by Step
    
 
        Say we want to trace changes to the sl_avail column in the
     shoelace_data relation. So we set up a log table
     and a rule that conditionally writes a log entry when an
@@ -344,7 +344,7 @@
 
    
 
    
 35.3.2. Cooperation with Views
    
-
        A simple way to protect view relations from the mentioned
+
        A simple way to protect view relations from the mentioned
     possibility that someone can try to run INSERT,
     UPDATE, or DELETE on them is
     to let those query trees get thrown away.  So we could create the rules
diff --git a/docs/en_US/pg/rules-views.html b/docs/en_US/pg/rules-views.html
index 472e4f3fcd..a743ad0bcb 100644
--- a/docs/en_US/pg/rules-views.html
+++ b/docs/en_US/pg/rules-views.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 35.2. Views and the Rule System
    
-
        Views in PostgreSQL are implemented
+
        Views in PostgreSQL are implemented
     using the rule system. In fact, there is essentially no difference
     between
 
@@ -40,7 +40,7 @@
 
    
 
    
 35.2.1. How SELECT Rules Work
    
-
        Rules ON SELECT are applied to all queries as the last step, even
+
        Rules ON SELECT are applied to all queries as the last step, even
     if the command given is an INSERT,
     UPDATE or DELETE. And they
     have different semantics from rules on the other command types in that they modify the
@@ -341,24 +341,10 @@ 
    Note
    
     collapsing the query tree is an optimization that the rewrite
     system doesn't have to concern itself with.
    
    
-
    
-
    Note
    
-
        There is currently no recursion stopping mechanism for view rules
-    in the rule system (only for the other kinds of rules).  This
-    doesn't hurt much, because the only way to push this into an
-    endless loop (bloating up the server process until it reaches the memory
-    limit) is to create tables and then setup the view rules by hand
-    with CREATE RULE in such a way, that one
-    selects from the other that selects from the one.  This could
-    never happen if CREATE VIEW is used because for
-    the first CREATE VIEW, the second relation does
-    not exist and thus the first view cannot select from the second.
-    
    
-
    
 
    
 
    
 
    
-35.2.2. View Rules in Non-SELECT Statements
    
+35.2.2. View Rules in Non-SELECT Statements
    
 
        Two details of the query tree aren't touched in the description of
     view rules above. These are the command type and the result relation.
     In fact, view rules don't need this information.
    
@@ -374,7 +360,7 @@ 
    Note
    
 
    
 
    SELECT t2.b FROM t1, t2 WHERE t1.a = t2.a;
 
-UPDATE t1 SET b = t2.b WHERE t1.a = t2.a;
    
+UPDATE t1 SET b = t2.b FROM t2 WHERE t1.a = t2.a;
    
 
    
 
     are nearly identical.  In particular:
@@ -401,7 +387,7 @@ 
    Note
    
     as
 
 
    
-
    UPDATE t1 SET a = t1.a, b = t2.b WHERE t1.a = t2.a;
    
+
    UPDATE t1 SET a = t1.a, b = t2.b FROM t2 WHERE t1.a = t2.a;
    
 
    
 
     and thus the executor run over the join will produce exactly the
@@ -424,11 +410,12 @@ 
    Note
    
 
        To resolve this problem, another entry is added to the target list
     in UPDATE (and also in
     DELETE) statements: the current tuple ID
-    (CTID).  This is a system column containing the
+    (CTID).
+    This is a system column containing the
     file block number and position in the block for the row. Knowing
     the table, the CTID can be used to retrieve the
-    original row of t1 to be updated.  After adding the CTID
-    to the target list, the query actually looks like
+    original row of t1 to be updated.  After adding the
+    CTID to the target list, the query actually looks like
 
 
    
 
    SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a;
    
@@ -442,14 +429,13 @@ 
    Note
    
     CTID pointed to, the cmax and
     xmax entries are set to the current command counter
     and current transaction ID. Thus the old row is hidden, and after
-    the transaction committed the vacuum cleaner can really move it
-    out.
    
+    the transaction commits the vacuum cleaner can really remove it.
    
 
        Knowing all that, we can simply apply view rules in absolutely
     the same way to any command. There is no difference.
    
 
 
    
 
    
-35.2.3. The Power of Views in PostgreSQL
    
+35.2.3. The Power of Views in PostgreSQL
    
 
        The above demonstrates how the rule system incorporates view
     definitions into the original query tree. In the second example, a
     simple SELECT from one view created a final
diff --git a/docs/en_US/pg/rules.html b/docs/en_US/pg/rules.html
index 79b5a35acb..7a5386257e 100644
--- a/docs/en_US/pg/rules.html
+++ b/docs/en_US/pg/rules.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -21,13 +21,13 @@
 
    35.2. Views and the Rule System
    
 
    
 
    35.2.1. How SELECT Rules Work
    
-
    35.2.2. View Rules in Non-SELECT Statements
    
-
    35.2.3. The Power of Views in PostgreSQL
    
+
    35.2.2. View Rules in Non-SELECT Statements
    
+
    35.2.3. The Power of Views in PostgreSQL
    
 
    35.2.4. Updating a View
    
 
    
 
    35.3. Rules on INSERT, UPDATE, and DELETE
    
 
    
-
    35.3.1. How Update Rules Work
    
+
    35.3.1. How Update Rules Work
    
 
    35.3.2. Cooperation with Views
    
 
    
 
    35.4. Rules and Privileges
    
@@ -35,7 +35,7 @@
 
    35.6. Rules versus Triggers
    
 
 
-
         This chapter discusses the rule system in
+
         This chapter discusses the rule system in
      PostgreSQL.  Production rule systems
      are conceptually simple, but there are many subtle points
      involved in actually using them.
    
@@ -54,7 +54,7 @@
 
    
 
    
 35.1. The Query Tree
    
-
        To understand how the rule system works it is necessary to know
+
        To understand how the rule system works it is necessary to know
     when it is invoked and what its input and results are.
    
 
        The rule system is located between the parser and the planner.
     It takes the output of the parser, one query tree, and the user-defined
diff --git a/docs/en_US/pg/runtime-config-autovacuum.html b/docs/en_US/pg/runtime-config-autovacuum.html
index 4fbcc6a62e..8f050247a4 100644
--- a/docs/en_US/pg/runtime-config-autovacuum.html
+++ b/docs/en_US/pg/runtime-config-autovacuum.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 17.9. Automatic Vacuuming
    
-
          These settings control the behavior of the autovacuum
+
          These settings control the behavior of the autovacuum
       feature.  Refer to Section 22.1.4, “The auto-vacuum daemon” for
       more information.
      
    
diff --git a/docs/en_US/pg/runtime-config-client.html b/docs/en_US/pg/runtime-config-client.html
index ef9dbfcd32..1d66d448f0 100644
--- a/docs/en_US/pg/runtime-config-client.html
+++ b/docs/en_US/pg/runtime-config-client.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-compatible.html b/docs/en_US/pg/runtime-config-compatible.html
index 2d6666fea5..5baee06be6 100644
--- a/docs/en_US/pg/runtime-config-compatible.html
+++ b/docs/en_US/pg/runtime-config-compatible.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-connection.html b/docs/en_US/pg/runtime-config-connection.html
index 00a9ca5079..ef9877ce36 100644
--- a/docs/en_US/pg/runtime-config-connection.html
+++ b/docs/en_US/pg/runtime-config-connection.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-custom.html b/docs/en_US/pg/runtime-config-custom.html
index 0c3d354449..f8bf71d423 100644
--- a/docs/en_US/pg/runtime-config-custom.html
+++ b/docs/en_US/pg/runtime-config-custom.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-developer.html b/docs/en_US/pg/runtime-config-developer.html
index 78e46dce73..9d2072a306 100644
--- a/docs/en_US/pg/runtime-config-developer.html
+++ b/docs/en_US/pg/runtime-config-developer.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-file-locations.html b/docs/en_US/pg/runtime-config-file-locations.html
index 40ff1d048d..35e614ba06 100644
--- a/docs/en_US/pg/runtime-config-file-locations.html
+++ b/docs/en_US/pg/runtime-config-file-locations.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-locks.html b/docs/en_US/pg/runtime-config-locks.html
index 641b64f79d..c8e62a479f 100644
--- a/docs/en_US/pg/runtime-config-locks.html
+++ b/docs/en_US/pg/runtime-config-locks.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/runtime-config-logging.html b/docs/en_US/pg/runtime-config-logging.html
index 5c2ffdd9d8..f4b391ade9 100644
--- a/docs/en_US/pg/runtime-config-logging.html
+++ b/docs/en_US/pg/runtime-config-logging.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,10 +14,10 @@
 
    
 
    
 17.7. Error Reporting and Logging
    
-
    
+
    
 
    
 17.7.1. Where To Log
    
-
    
+
    
 
    
 log_destination (string)
 
    
@@ -422,7 +422,7 @@ 
    Note
    
 
    
 
    
 %tTime stamp (no milliseconds)Time stamp (no milliseconds, no timezone on Windows)
 no
 
    
 
    
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
    
 
    
@@ -204,8 +204,8 @@
 
 
    
 
    
-4.2.6. Function Calls
    
-
        The syntax for a function call is the name of a function
+4.2.6. Function Calls
    
+
        The syntax for a function call is the name of a function
     (possibly qualified with a schema name), followed by its argument list
     enclosed in parentheses:
 
@@ -225,7 +225,7 @@
 
    
 
    
 4.2.7. Aggregate Expressions
    
-
        An aggregate expression represents the
+
        An aggregate expression represents the
     application of an aggregate function across the rows selected by a
     query.  An aggregate function reduces multiple inputs to a single
     output value, such as the sum or average of the inputs.  The
@@ -294,7 +294,7 @@ 
    Note
    
 
    
 
    
 4.2.8. Type Casts
    
-
        A type cast specifies a conversion from one data type to another.
+
        A type cast specifies a conversion from one data type to another.
     PostgreSQL accepts two equivalent syntaxes
     for type casts:
 
    
@@ -351,7 +351,7 @@ 
    Note
    
 
    
 
    
 4.2.9. Scalar Subqueries
    
-
        A scalar subquery is an ordinary
+
        A scalar subquery is an ordinary
     SELECT query in parentheses that returns exactly one
     row with one column.  (See Chapter 7, Queries for information about writing queries.)
     The SELECT query is executed
@@ -375,7 +375,7 @@ 
    Note
    
 
    
 
    
 4.2.10. Array Constructors
    
-
        An array constructor is an expression that builds an
+
        An array constructor is an expression that builds an
     array value from values for its member elements.  A simple array
     constructor 
     consists of the key word ARRAY, a left square bracket
@@ -454,7 +454,7 @@ 
    Note
    
 
    
 
    
 4.2.11. Row Constructors
    
-
        A row constructor is an expression that builds a row value (also
+
        A row constructor is an expression that builds a row value (also
     called a composite value) from values
     for its member fields.  A row constructor consists of the key word
     ROW, a left parenthesis, zero or more
@@ -544,7 +544,7 @@ 
    Note
    
 
    
 
    
 4.2.12. Expression Evaluation Rules
    
-
        The order of evaluation of subexpressions is not defined.  In
+
        The order of evaluation of subexpressions is not defined.  In
     particular, the inputs of an operator or function are not necessarily
     evaluated left-to-right or in any other fixed order.
    
    
diff --git a/docs/en_US/pg/sql-fetch.html b/docs/en_US/pg/sql-fetch.html
index 1e497d6416..4be2ba94db 100644
--- a/docs/en_US/pg/sql-fetch.html
+++ b/docs/en_US/pg/sql-fetch.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    FETCH — retrieve rows from a query using a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    FETCH [ direction { FROM | IN } ] cursorname
 
@@ -39,7 +39,7 @@ 
    Synopsis
    
     BACKWARD ALL
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       FETCH retrieves rows using a previously-created cursor.
   
    
 
       A cursor has an associated position, which is used by
@@ -74,7 +74,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    direction
    
 
    
@@ -156,7 +156,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, a FETCH command returns a command
    tag of the form
 
    
@@ -170,7 +170,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       The cursor should be declared with the SCROLL
    option if one intends to use any variants of FETCH
    other than FETCH NEXT or FETCH FORWARD with
@@ -198,7 +198,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       The following example traverses a table using a cursor.
 
 
    
@@ -232,7 +232,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard defines FETCH for use in
    embedded SQL only.  The variant of FETCH
    described here returns the data as if it were a
@@ -251,7 +251,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CLOSE, DECLARE, MOVE
 
    
 
    
diff --git a/docs/en_US/pg/sql-grant.html b/docs/en_US/pg/sql-grant.html
index 729bf694c6..7b4a239c6a 100644
--- a/docs/en_US/pg/sql-grant.html
+++ b/docs/en_US/pg/sql-grant.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    GRANT — define access privileges
    
 
    
-
    
+
    
 
    Synopsis
    
 
    GRANT { { SELECT | INSERT | UPDATE | DELETE | REFERENCES | TRIGGER }
     [,...] | ALL [ PRIVILEGES ] }
@@ -405,7 +405,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 
       REVOKE
   
    
 
    
diff --git a/docs/en_US/pg/sql-insert.html b/docs/en_US/pg/sql-insert.html
index afd6619243..ae75637a21 100644
--- a/docs/en_US/pg/sql-insert.html
+++ b/docs/en_US/pg/sql-insert.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    INSERT — create new rows in a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    INSERT INTO table [ ( column [, ...] ) ]
     { DEFAULT VALUES | VALUES ( { expression | DEFAULT } [, ...] ) [, ...] | query }
     [ RETURNING * | output_expression [ AS output_name ] [, ...] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       INSERT inserts new rows into a table.
    One can insert one or more rows specified by value expressions,
    or zero or more rows resulting from a query.
@@ -60,7 +60,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    table
    
 
          The name (optionally schema-qualified) of an existing table.
@@ -99,7 +99,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, an INSERT command returns a command
    tag of the form
 
    
@@ -120,7 +120,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Insert a single row into table films:
 
 
    
@@ -189,7 +189,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       INSERT conforms to the SQL standard, except that
    the RETURNING clause is a
    PostgreSQL extension.  Also, the case in
diff --git a/docs/en_US/pg/sql-keywords-appendix.html b/docs/en_US/pg/sql-keywords-appendix.html
index ccaf0c254f..713d68a0b6 100644
--- a/docs/en_US/pg/sql-keywords-appendix.html
+++ b/docs/en_US/pg/sql-keywords-appendix.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,9 +14,9 @@
 
    
 
    
 Appendix C. SQL Key Words
    
-
      Table C.1, “SQL Key Words” lists all tokens that are key words
+
      Table C.1, “SQL Key Words” lists all tokens that are key words
   in the SQL standard and in PostgreSQL
-  8.2.0.  Background information can be found in Section 4.1.1, “Identifiers and Key Words”.
+  8.2.1.  Background information can be found in Section 4.1.1, “Identifiers and Key Words”.
  
    
 
      SQL distinguishes between reserved and
   non-reserved key words.  According to the standard,
diff --git a/docs/en_US/pg/sql-listen.html b/docs/en_US/pg/sql-listen.html
index 8c8ea1eb26..da311d036f 100644
--- a/docs/en_US/pg/sql-listen.html
+++ b/docs/en_US/pg/sql-listen.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    LISTEN — listen for a notification
    
 
    
-
    
+
    
 
    Synopsis
    
 
    LISTEN name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       LISTEN registers the current session as a
    listener on the notification condition name.
    If the current session is already registered as a listener for
@@ -57,7 +57,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          Name of a notify condition (any identifier).
@@ -65,7 +65,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Configure and execute a listen/notify sequence from
    psql:
 
@@ -77,13 +77,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no LISTEN statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 NOTIFY, UNLISTEN
 
    
 
    
diff --git a/docs/en_US/pg/sql-load.html b/docs/en_US/pg/sql-load.html
index f864c16656..4e48c4ea1f 100644
--- a/docs/en_US/pg/sql-load.html
+++ b/docs/en_US/pg/sql-load.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    LOAD — load or reload a shared library file
    
 
    
-
    
+
    
 
    Synopsis
    
 
    LOAD 'filename'
    
 
    
@@ -37,7 +37,7 @@ 
    Synopsis
    
    shared library file name extension.  See Section 33.9, “C-Language Functions” for
    more information on this topic.
   
    
-
       Non-superusers may only apply LOAD to library files
+
       Non-superusers may only apply LOAD to library files
    located in $libdir/plugins/ — the specified
    filename must begin
    with exactly that string.  (It is the database administrator's
@@ -52,7 +52,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 
       CREATE FUNCTION
   
    
 
    
diff --git a/docs/en_US/pg/sql-lock.html b/docs/en_US/pg/sql-lock.html
index 129b657626..5a23121eb4 100644
--- a/docs/en_US/pg/sql-lock.html
+++ b/docs/en_US/pg/sql-lock.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    LOCK — lock a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    LOCK [ TABLE ] name [, ...] [ IN lockmode MODE ] [ NOWAIT ]
 
@@ -27,7 +27,7 @@ 
    Synopsis
    
     | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       LOCK TABLE obtains a table-level lock, waiting
    if necessary for any conflicting locks to be released.  If
    NOWAIT is specified, LOCK
@@ -85,7 +85,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
    
@@ -116,7 +116,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        LOCK TABLE ... IN ACCESS SHARE MODE requires SELECT
     privileges on the target table.  All other forms of LOCK
     require UPDATE and/or DELETE privileges.
@@ -142,7 +142,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Obtain a SHARE lock on a primary key table when going to perform
    inserts into a foreign key table:
 
@@ -171,7 +171,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no LOCK TABLE in the SQL standard,
    which instead uses SET TRANSACTION to specify
    concurrency levels on transactions.  PostgreSQL supports that too;
diff --git a/docs/en_US/pg/sql-move.html b/docs/en_US/pg/sql-move.html
index ceebf94c1e..bfe89ba8ba 100644
--- a/docs/en_US/pg/sql-move.html
+++ b/docs/en_US/pg/sql-move.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    MOVE — position a cursor
    
 
    
-
    
+
    
 
    Synopsis
    
 
    MOVE [ direction { FROM | IN } ] cursorname
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       MOVE repositions a cursor without retrieving any data.
    MOVE works exactly like the FETCH
    command, except it only positions the cursor and does not return rows.
@@ -33,7 +33,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, a MOVE command returns a command
    tag of the form
 
    
@@ -45,7 +45,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
    BEGIN WORK;
 DECLARE liahona CURSOR FOR SELECT * FROM films;
 
@@ -65,12 +65,12 @@ 
    Synopsis
    
 COMMIT WORK;
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no MOVE statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CLOSE, DECLARE, FETCH
 
    
 
    
diff --git a/docs/en_US/pg/sql-notify.html b/docs/en_US/pg/sql-notify.html
index ef32bc8b08..3b28b0d600 100644
--- a/docs/en_US/pg/sql-notify.html
+++ b/docs/en_US/pg/sql-notify.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    NOTIFY — generate a notification
    
 
    
-
    
+
    
 
    Synopsis
    
 
    NOTIFY name        
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       The NOTIFY command sends a notification event to each
    client application that has previously executed
    LISTEN name
@@ -100,7 +100,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          Name of the notification to be signaled (any identifier).
@@ -108,7 +108,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Configure and execute a listen/notify sequence from
    psql:
 
@@ -120,13 +120,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no NOTIFY statement in the SQL
    standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 LISTEN, UNLISTEN
 
    
 
    
diff --git a/docs/en_US/pg/sql-prepare-transaction.html b/docs/en_US/pg/sql-prepare-transaction.html
index 2ca6c67890..fd6eaacdcc 100644
--- a/docs/en_US/pg/sql-prepare-transaction.html
+++ b/docs/en_US/pg/sql-prepare-transaction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    PREPARE TRANSACTION — prepare the current transaction for two-phase commit
    
 
    
-
    
+
    
 
    Synopsis
    
 
    PREPARE TRANSACTION transaction_id
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       PREPARE TRANSACTION prepares the current transaction
    for two-phase commit. After this command, the transaction is no longer 
    associated with the current session; instead, its state is fully stored on
@@ -48,7 +48,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    transaction_id
    
 
          An arbitrary identifier that later identifies this transaction for
@@ -60,7 +60,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       This command must be used inside a transaction block. Use BEGIN to start one.
   
    
 
       It is not currently allowed to PREPARE a transaction that
@@ -107,7 +107,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 COMMIT PREPARED, ROLLBACK PREPARED
 
    
 
    
diff --git a/docs/en_US/pg/sql-prepare.html b/docs/en_US/pg/sql-prepare.html
index a0da41ebe2..bc20bb7b35 100644
--- a/docs/en_US/pg/sql-prepare.html
+++ b/docs/en_US/pg/sql-prepare.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    PREPARE — prepare a statement for execution
    
 
    
-
    
+
    
 
    Synopsis
    
 
    PREPARE name [ (datatype [, ...] ) ] AS statement
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       PREPARE creates a prepared statement. A prepared
    statement is a server-side object that can be used to optimize
    performance. When the PREPARE statement is
@@ -63,7 +63,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          An arbitrary name given to this particular prepared
@@ -86,7 +86,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       In some situations, the query plan produced for a prepared
    statement will be inferior to the query plan that would have been
    chosen if the statement had been submitted and executed
@@ -136,7 +136,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard includes a PREPARE statement,
    but it is only for use in embedded SQL. This version of the
    PREPARE statement also uses a somewhat different
@@ -144,7 +144,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DEALLOCATE, EXECUTE
 
    
 
    
diff --git a/docs/en_US/pg/sql-reassign-owned.html b/docs/en_US/pg/sql-reassign-owned.html
index ab88387c20..40b08679cb 100644
--- a/docs/en_US/pg/sql-reassign-owned.html
+++ b/docs/en_US/pg/sql-reassign-owned.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,19 +17,19 @@
 
    Name
    
 
    REASSIGN OWNED — change the ownership of database objects owned by a database role
    
 
    
-
    
+
    
 
    Synopsis
    
 
    REASSIGN OWNED BY old_role [, ...] TO new_role
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       REASSIGN OWNED instructs the system to change
    the ownership of the database objects owned by one of the
    old_roles, to new_role.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    old_role
    
 
          The name of a role. The ownership of all the objects in the
@@ -43,7 +43,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       REASSIGN OWNED is often used to prepare for the
    removal of one or more roles. Because REASSIGN
    OWNED only affects the objects in the current database,
@@ -60,13 +60,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The REASSIGN OWNED statement is a
    PostgreSQL extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 DROP OWNED, DROP ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-reindex.html b/docs/en_US/pg/sql-reindex.html
index a551f00d0b..7609806461 100644
--- a/docs/en_US/pg/sql-reindex.html
+++ b/docs/en_US/pg/sql-reindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    REINDEX — rebuild indexes
    
 
    
-
    
+
    
 
    Synopsis
    
 
    REINDEX { INDEX | TABLE | DATABASE | SYSTEM } name [ FORCE ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       REINDEX rebuilds an index using the data
    stored in the index's table, replacing the old copy of the index. There are
    several scenarios in which to use REINDEX:
@@ -57,7 +57,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    INDEX
    
 
          Recreate the specified index.
@@ -92,7 +92,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       If you suspect corruption of an index on a user table, you can
    simply rebuild that index, or all indexes on the table, using
    REINDEX INDEX or REINDEX TABLE.  
@@ -134,7 +134,8 @@ 
    Synopsis
    
    pg_auth_members,
    pg_database,
    pg_pltemplate,
-   pg_shdepend, and
+   pg_shdepend,
+   pg_shdescription, and
    pg_tablespace), then a standalone server
    must be used to repair it.  REINDEX will not process
    shared catalogs in multiuser mode.
@@ -180,7 +181,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Rebuild a single index:
 
 
    
@@ -206,7 +207,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no REINDEX command in the SQL standard.
   
    
 
    
diff --git a/docs/en_US/pg/sql-release-savepoint.html b/docs/en_US/pg/sql-release-savepoint.html
index a01f1d88f8..1aa3e2a728 100644
--- a/docs/en_US/pg/sql-release-savepoint.html
+++ b/docs/en_US/pg/sql-release-savepoint.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    RELEASE SAVEPOINT — destroy a previously defined savepoint
    
 
    
-
    
+
    
 
    Synopsis
    
 
    RELEASE [ SAVEPOINT ] savepoint_name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       RELEASE SAVEPOINT destroys a savepoint previously defined
    in the current transaction.
   
    
@@ -38,7 +38,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    savepoint_name
    
 
          The name of the savepoint to destroy.
@@ -46,7 +46,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Specifying a savepoint name that was not previously defined is an error.
   
    
 
       It is not possible to release a savepoint when the transaction is in
@@ -57,7 +57,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To establish and later destroy a savepoint:
 
    
 
    BEGIN;
@@ -71,7 +71,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command conforms to the SQL standard.  The standard
    specifies that the key word SAVEPOINT is
    mandatory, but PostgreSQL allows it to
@@ -79,7 +79,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, ROLLBACK, ROLLBACK TO SAVEPOINT, SAVEPOINT
 
    
 
    
diff --git a/docs/en_US/pg/sql-reset.html b/docs/en_US/pg/sql-reset.html
index 3bad66d6b7..cca2e0cd79 100644
--- a/docs/en_US/pg/sql-reset.html
+++ b/docs/en_US/pg/sql-reset.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    RESET — restore the value of a run-time parameter to the default value
    
 
-
    
+
    
 
    Synopsis
    
 
    RESET configuration_parameter
 RESET ALL
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       RESET restores run-time parameters to their
    default values.  RESET is an alternative
    spelling for
@@ -44,7 +44,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    configuration_parameter
    
 
          The name of a run-time parameter. See SET for a list.
@@ -55,7 +55,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Set the geqo configuration variable to its default value:
 
    
 
    RESET geqo;
    
@@ -63,7 +63,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       RESET is a PostgreSQL extension.
   
    
 
    
diff --git a/docs/en_US/pg/sql-revoke.html b/docs/en_US/pg/sql-revoke.html
index 2ec5faa890..e186b0e01f 100644
--- a/docs/en_US/pg/sql-revoke.html
+++ b/docs/en_US/pg/sql-revoke.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    REVOKE — remove access privileges
    
 
    
-
    
+
    
 
    Synopsis
    
 
    REVOKE [ GRANT OPTION FOR ]
     { { SELECT | INSERT | UPDATE | DELETE | REFERENCES | TRIGGER }
@@ -206,7 +206,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 
       GRANT
   
    
 
    
diff --git a/docs/en_US/pg/sql-rollback-prepared.html b/docs/en_US/pg/sql-rollback-prepared.html
index 116864bc90..14684cb1d4 100644
--- a/docs/en_US/pg/sql-rollback-prepared.html
+++ b/docs/en_US/pg/sql-rollback-prepared.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    ROLLBACK PREPARED — cancel a transaction that was earlier prepared for two-phase commit
    
 
    
-
    
+
    
 
    Synopsis
    
 
    ROLLBACK PREPARED transaction_id
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ROLLBACK PREPARED rolls back a transaction that is in 
    prepared state.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    transaction_id
    
 
          The transaction identifier of the transaction that is to be
@@ -37,7 +37,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       To roll back a prepared transaction, you must be either the same user that
    executed the transaction originally, or a superuser.  But you do not
    have to be in the same session that executed the transaction.
@@ -61,7 +61,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 PREPARE TRANSACTION, COMMIT PREPARED
 
    
 
    
diff --git a/docs/en_US/pg/sql-rollback-to.html b/docs/en_US/pg/sql-rollback-to.html
index af86aa422b..a4ade05995 100644
--- a/docs/en_US/pg/sql-rollback-to.html
+++ b/docs/en_US/pg/sql-rollback-to.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    ROLLBACK TO SAVEPOINT — roll back to a savepoint
    
 
-
    
+
    
 
    Synopsis
    
 
    ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       Roll back all commands that were executed after the savepoint was
    established.  The savepoint remains valid and can be rolled back to
    again later, if needed.
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    savepoint_name
    
 
          The savepoint to roll back to.
@@ -40,7 +40,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use RELEASE SAVEPOINT to destroy a savepoint without
    discarding the effects of commands executed after it was established.
   
    
@@ -60,7 +60,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To undo the effects of the commands executed after my_savepoint
    was established:
 
    
@@ -92,7 +92,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard specifies that the key word
    SAVEPOINT is mandatory, but PostgreSQL
    and Oracle allow it to be omitted.  SQL allows
@@ -104,7 +104,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, RELEASE SAVEPOINT, ROLLBACK, SAVEPOINT
 
    
 
    
diff --git a/docs/en_US/pg/sql-rollback.html b/docs/en_US/pg/sql-rollback.html
index 142be5e846..a9e8b468ca 100644
--- a/docs/en_US/pg/sql-rollback.html
+++ b/docs/en_US/pg/sql-rollback.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,18 +17,18 @@
 
    Name
    
 
    ROLLBACK — abort the current transaction
    
 
-
    
+
    
 
    Synopsis
    
 
    ROLLBACK [ WORK | TRANSACTION ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       ROLLBACK rolls back the current transaction and causes
    all the updates made by the transaction to be discarded.
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 WORK

    TRANSACTION
@@ -38,7 +38,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use COMMIT to
    successfully terminate a transaction.
   
    
@@ -47,7 +47,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To abort all changes:
 
    
 
    ROLLBACK;
    
@@ -55,14 +55,14 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard only specifies the two forms
    ROLLBACK and ROLLBACK
    WORK. Otherwise, this command is fully conforming.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, ROLLBACK TO SAVEPOINT
 
    
 
    
diff --git a/docs/en_US/pg/sql-savepoint.html b/docs/en_US/pg/sql-savepoint.html
index e3b6061555..c33e81bffc 100644
--- a/docs/en_US/pg/sql-savepoint.html
+++ b/docs/en_US/pg/sql-savepoint.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SAVEPOINT — define a new savepoint within the current transaction
    
 
-
    
+
    
 
    Synopsis
    
 
    SAVEPOINT savepoint_name
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SAVEPOINT establishes a new savepoint within
    the current transaction.
   
    
@@ -32,7 +32,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    savepoint_name
    
 
          The name to give to the new savepoint.
@@ -40,7 +40,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Use ROLLBACK TO SAVEPOINT to
    rollback to a savepoint.  Use RELEASE SAVEPOINT to destroy a savepoint, keeping
    the effects of commands executed after it was established.
@@ -50,7 +50,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To establish a savepoint and later undo the effects of all commands executed
    after it was established:
 
    
@@ -77,7 +77,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       SQL requires a savepoint to be destroyed automatically when another
    savepoint with the same name is established.  In
    PostgreSQL, the old savepoint is kept, though only the more
@@ -88,7 +88,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, RELEASE SAVEPOINT, ROLLBACK, ROLLBACK TO SAVEPOINT
 
    
 
    
diff --git a/docs/en_US/pg/sql-select.html b/docs/en_US/pg/sql-select.html
index 1d75bca3c8..2fba498de0 100644
--- a/docs/en_US/pg/sql-select.html
+++ b/docs/en_US/pg/sql-select.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    SELECT — retrieve rows from a table or view
    
 
-
    
+
    
 
    Synopsis
    
 
    SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
     * | expression [ AS output_name ] [, ...]
@@ -40,7 +40,7 @@ 
    Synopsis
    
     from_item [ NATURAL ] join_type from_item [ ON join_condition | USING ( join_column [, ...] ) ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SELECT retrieves rows from zero or more tables.
    The general processing of SELECT is as follows:
 
@@ -114,7 +114,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    
 FROM Clause
    
@@ -705,7 +705,7 @@ 
    Caution
    
 
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To join the table films with the table
    distributors:
 
@@ -835,13 +835,13 @@ 
    Caution
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       Of course, the SELECT statement is compatible
    with the SQL standard.  But there are some extensions and some
    missing features.
   
    
 
    
-
    Omitted FROM Clauses
    
+
    Omitted FROM Clauses
    
 
        PostgreSQL allows one to omit the
     FROM clause.  It has a straightforward use to
     compute the results of simple expressions:
@@ -873,7 +873,7 @@ 
    Caution
    
    
    
 
    
 
    
-
    The AS Key Word
    
+
    The AS Key Word
    
 
        In the SQL standard, the optional key word AS is just
     noise and can be omitted without affecting the meaning.  The
     PostgreSQL parser requires this key
@@ -884,7 +884,7 @@ 
    Caution
    
    
    
 
    
 
    
-
    Namespace Available to GROUP BY and ORDER BY
+
    Namespace Available to GROUP BY and ORDER BY
 
    
 
        In the SQL-92 standard, an ORDER BY clause may
     only use result column names or numbers, while a GROUP
@@ -905,7 +905,7 @@ 
    Caution
    
    
    
 
    
 
    
-
    Nonstandard Clauses
    
+
    Nonstandard Clauses
    
 
        The clauses DISTINCT ON,
     LIMIT, and OFFSET are not
     defined in the SQL standard.
diff --git a/docs/en_US/pg/sql-selectinto.html b/docs/en_US/pg/sql-selectinto.html
index dd95c5e073..8324e28c28 100644
--- a/docs/en_US/pg/sql-selectinto.html
+++ b/docs/en_US/pg/sql-selectinto.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    SELECT INTO — define a new table from the results of a query
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
     * | expression [ AS output_name ] [, ...]
@@ -33,7 +33,7 @@ 
    Synopsis
    
     [ FOR { UPDATE | SHARE } [ OF table_name [, ...] ] [ NOWAIT ] [...] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SELECT INTO creates a new table and fills it
    with data computed by a query.  The data is not returned to the
    client, as it is with a normal SELECT.  The new
@@ -42,7 +42,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    TEMPORARY or TEMP
    
 
         If specified, the table is created as a temporary table.  Refer
@@ -56,7 +56,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       CREATE TABLE AS is functionally similar to
    SELECT INTO.  CREATE TABLE AS
    is the recommended syntax, since this form of SELECT
@@ -75,7 +75,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Create a new table films_recent consisting of only
    recent entries from the table films:
 
@@ -85,7 +85,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard uses SELECT INTO to
    represent selecting values into scalar variables of a host program,
    rather than creating a new table.  This indeed is the usage found
@@ -98,7 +98,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 CREATE TABLE AS
 
    
 
    
diff --git a/docs/en_US/pg/sql-set-constraints.html b/docs/en_US/pg/sql-set-constraints.html
index 0e6c37ad57..9e6197e7dc 100644
--- a/docs/en_US/pg/sql-set-constraints.html
+++ b/docs/en_US/pg/sql-set-constraints.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    SET CONSTRAINTS — set constraint checking modes for the current transaction
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SET CONSTRAINTS { ALL | name [, ...] } { DEFERRED | IMMEDIATE }
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SET CONSTRAINTS sets the behavior of constraint
    checking within the current transaction. IMMEDIATE
    constraints are checked at the end of each
@@ -62,7 +62,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       This command only alters the behavior of constraints within the
    current transaction. Thus, if you execute this command outside of a
    transaction block
@@ -71,7 +71,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command complies with the behavior defined in the SQL
    standard, except for the limitation that, in
    PostgreSQL, it only applies to
diff --git a/docs/en_US/pg/sql-set-role.html b/docs/en_US/pg/sql-set-role.html
index f91cd22398..ec0a418571 100644
--- a/docs/en_US/pg/sql-set-role.html
+++ b/docs/en_US/pg/sql-set-role.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    SET ROLE — set the current user identifier of the current session
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SET [ SESSION | LOCAL ] ROLE rolename
 SET [ SESSION | LOCAL ] ROLE NONE
 RESET ROLE
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       This command sets the current user
    identifier of the current SQL-session context to be rolename.  The role name may be
    written as either an identifier or a string literal.
@@ -46,7 +46,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Using this command, it is possible to either add privileges or restrict
    one's privileges.  If the session user role has the INHERITS
    attribute, then it automatically has all the privileges of every role that
@@ -71,7 +71,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
    SELECT SESSION_USER, CURRENT_USER;
 
  session_user | current_user 
@@ -87,7 +87,7 @@ 
    Synopsis
    
  peter        | paul
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       PostgreSQL
    allows identifier syntax ("rolename"), while
    the SQL standard requires the role name to be written as a string
@@ -100,7 +100,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 SET SESSION AUTHORIZATION
 
    
 
    
diff --git a/docs/en_US/pg/sql-set-session-authorization.html b/docs/en_US/pg/sql-set-session-authorization.html
index 8cc1e6c06e..ee54817fca 100644
--- a/docs/en_US/pg/sql-set-session-authorization.html
+++ b/docs/en_US/pg/sql-set-session-authorization.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,14 +17,14 @@
 
    Name
    
 
    SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SET [ SESSION | LOCAL ] SESSION AUTHORIZATION username
 SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
 RESET SESSION AUTHORIZATION
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       This command sets the session user identifier and the current user
    identifier of the current SQL-session context to be username.  The user name may be
    written as either an identifier or a string literal.  Using this
@@ -54,7 +54,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
    SELECT SESSION_USER, CURRENT_USER;
 
  session_user | current_user 
@@ -70,7 +70,7 @@ 
    Synopsis
    
  paul         | paul
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SQL standard allows some other expressions to appear in place
    of the literal username, but these options
    are not important in practice.  PostgreSQL
@@ -87,7 +87,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 SET ROLE
 
    
 
    
diff --git a/docs/en_US/pg/sql-set-transaction.html b/docs/en_US/pg/sql-set-transaction.html
index 58bde15f76..db8b4ff721 100644
--- a/docs/en_US/pg/sql-set-transaction.html
+++ b/docs/en_US/pg/sql-set-transaction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    SET TRANSACTION — set the characteristics of the current transaction
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SET TRANSACTION transaction_mode [, ...]
 SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
@@ -28,7 +28,7 @@ 
    Synopsis
    
     READ WRITE | READ ONLY
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       The SET TRANSACTION command sets the
    characteristics of the current transaction. It has no effect on any
    subsequent transactions.  SET SESSION
@@ -89,7 +89,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       If SET TRANSACTION is executed without a prior
    START TRANSACTION or  BEGIN,
    it will appear to have no effect, since the transaction will immediately
diff --git a/docs/en_US/pg/sql-set.html b/docs/en_US/pg/sql-set.html
index 16e6bfdc85..617173be5a 100644
--- a/docs/en_US/pg/sql-set.html
+++ b/docs/en_US/pg/sql-set.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    SET — change a run-time parameter
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SET [ SESSION | LOCAL ] configuration_parameter { TO | = } { value | 'value' | DEFAULT }
 SET [ SESSION | LOCAL ] TIME ZONE { timezone | LOCAL | DEFAULT }
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       The SET command changes run-time configuration
    parameters.  Many of the run-time parameters listed in
    Chapter 17, Server Configuration can be changed on-the-fly with
@@ -52,7 +52,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    SESSION
    
 
          Specifies that the command takes effect for the current session.
@@ -144,13 +144,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       The function set_config provides equivalent
    functionality. See Section 9.20, “System Administration Functions”.
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Set the schema search path:
 
    
 
    SET search_path TO my_schema, public;
    
@@ -175,7 +175,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       SET TIME ZONE extends syntax defined in the SQL
    standard.  The standard allows only numeric time zone offsets while
    PostgreSQL allows more flexible
@@ -184,7 +184,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 RESET, SHOW
 
    
 
    
diff --git a/docs/en_US/pg/sql-show.html b/docs/en_US/pg/sql-show.html
index 8c22cb9bb6..e56b23b873 100644
--- a/docs/en_US/pg/sql-show.html
+++ b/docs/en_US/pg/sql-show.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    SHOW — show the value of a run-time parameter
    
 
    
-
    
+
    
 
    Synopsis
    
 
    SHOW name
 SHOW ALL
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       SHOW will display the current setting of
    run-time parameters. These variables can be set using the
    SET statement, by editing the
@@ -35,7 +35,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
    
@@ -80,13 +80,13 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       The function current_setting produces
    equivalent output. See Section 9.20, “System Administration Functions”.
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Show the current setting of the parameter DateStyle:
 
 
    
@@ -123,13 +123,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       The SHOW command is a
    PostgreSQL extension.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 SET, RESET
 
    
 
    
diff --git a/docs/en_US/pg/sql-start-transaction.html b/docs/en_US/pg/sql-start-transaction.html
index dd8dc8fd53..06a1745901 100644
--- a/docs/en_US/pg/sql-start-transaction.html
+++ b/docs/en_US/pg/sql-start-transaction.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    START TRANSACTION — start a transaction block
    
 
    
-
    
+
    
 
    Synopsis
    
 
    START TRANSACTION [ transaction_mode [, ...] ]
 
@@ -27,7 +27,7 @@ 
    Synopsis
    
     READ WRITE | READ ONLY
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       This command begins a new transaction block. If the isolation level or
    read/write mode is specified, the new transaction has those
    characteristics, as if SET TRANSACTION was executed. This is the same
@@ -35,13 +35,13 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
       Refer to SET TRANSACTION for information on the meaning
    of the parameters to this statement.
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       In the standard, it is not necessary to issue START TRANSACTION
    to start a transaction block: any SQL command implicitly begins a block.
    PostgreSQL's behavior can be seen as implicitly
@@ -59,7 +59,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 BEGIN, COMMIT, ROLLBACK, SAVEPOINT, SET TRANSACTION
 
    
 
    
diff --git a/docs/en_US/pg/sql-syntax.html b/docs/en_US/pg/sql-syntax.html
index 43c3550f23..9892215915 100644
--- a/docs/en_US/pg/sql-syntax.html
+++ b/docs/en_US/pg/sql-syntax.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -22,18 +22,18 @@
 
    4.1.1. Identifiers and Key Words
    
 
    4.1.2. Constants
    
 
    4.1.3. Operators
    
-
    4.1.4. Special Characters
    
+
    4.1.4. Special Characters
    
 
    4.1.5. Comments
    
 
    4.1.6. Lexical Precedence
    
 
 
    4.2. Value Expressions
    
 
    
-
    4.2.1. Column References
    
-
    4.2.2. Positional Parameters
    
-
    4.2.3. Subscripts
    
-
    4.2.4. Field Selection
    
-
    4.2.5. Operator Invocations
    
-
    4.2.6. Function Calls
    
+
    4.2.1. Column References
    
+
    4.2.2. Positional Parameters
    
+
    4.2.3. Subscripts
    
+
    4.2.4. Field Selection
    
+
    4.2.5. Operator Invocations
    
+
    4.2.6. Function Calls
    
 
    4.2.7. Aggregate Expressions
    
 
    4.2.8. Type Casts
    
 
    4.2.9. Scalar Subqueries
    
@@ -43,7 +43,7 @@
 
    
 
 
    
-
      This chapter describes the syntax of SQL.  It forms the foundation
+
      This chapter describes the syntax of SQL.  It forms the foundation
   for understanding the following chapters which will go into detail
   about how the SQL commands are applied to define and modify data.
  
    
@@ -55,7 +55,7 @@
 
    
 
    
 4.1. Lexical Structure
    
-
       SQL input consists of a sequence of
+
       SQL input consists of a sequence of
    commands.  A command is composed of a
    sequence of tokens, terminated by a
    semicolon (“;”).  The end of the input stream also
@@ -98,7 +98,7 @@
 
    
 
    
 4.1.1. Identifiers and Key Words
    
-
        Tokens such as SELECT, UPDATE, or
+
        Tokens such as SELECT, UPDATE, or
     VALUES in the example above are examples of
     key words, that is, words that have a fixed
     meaning in the SQL language.  The tokens MY_TABLE
@@ -125,7 +125,7 @@
     form are safe against possible conflict with future extensions of the
     standard.
    
    
-
        
+
        
     The system uses no more than NAMEDATALEN-1
     characters of an identifier; longer names can be written in
     commands, but they will be truncated.  By default,
@@ -134,7 +134,7 @@
     changing the NAMEDATALEN constant in
     src/include/postgres_ext.h.
    
    
-
        
+
        
     Identifier and key word names are case insensitive.  Therefore
 
    
 
    UPDATE MY_TABLE SET A = 5;
    
@@ -149,7 +149,7 @@
 
    UPDATE my_table SET a = 5;
    
 
    
    
    
-
        
+
        
     There is a second kind of identifier:  the delimited
     identifier or quoted
     identifier.  It is formed by enclosing an arbitrary
@@ -191,7 +191,7 @@
 
    
 
    
 4.1.2. Constants
    
-
        There are three kinds of implicitly-typed
+
        There are three kinds of implicitly-typed
     constants in PostgreSQL:
     strings, bit strings, and numbers.
     Constants can also be specified with explicit types, which can
@@ -202,7 +202,7 @@
 
    
 
    
 4.1.2.1. String Constants
    
-
         
+
         
      A string constant in SQL is an arbitrary sequence of characters
      bounded by single quotes ('), for example
      'This is a string'.  To include
@@ -232,8 +232,8 @@
      by SQL; PostgreSQL is
      following the standard.)
     
    
-
         
-     
+
         
+     
      PostgreSQL also accepts “escape”
      string constants, which are an extension to the SQL standard.
      An escape string constant is specified by writing the letter
@@ -289,7 +289,7 @@ 
    Caution
    
 
    
 
    
 4.1.2.2. Dollar-Quoted String Constants
    
-
         While the standard syntax for specifying string constants is usually
+
         While the standard syntax for specifying string constants is usually
      convenient, it can be difficult to understand when the desired string
      contains many single quotes or backslashes, since each of those must
      be doubled. To allow more readable queries in such situations,
@@ -355,7 +355,7 @@ 
    Caution
    
 
    
 
    
 4.1.2.3. Bit-String Constants
    
-
         Bit-string constants look like regular string constants with a
+
         Bit-string constants look like regular string constants with a
      B (upper or lower case) immediately before the
      opening quote (no intervening whitespace), e.g.,
      B'1001'.  The only characters allowed within
@@ -374,8 +374,8 @@ 
    Caution
    
 
    
 
    
 
    
-4.1.2.4. Numeric Constants
    
-
         Numeric constants are accepted in these general forms:
+4.1.2.4. Numeric Constants
    
+
         Numeric constants are accepted in these general forms:
 
    
 
    digits
 digits.[digits][e[+-]digits]
@@ -401,9 +401,9 @@ 
    Caution
    
 1.925e-3
    
 
    
     
    
-
         
-     
-     
+
         
+     
+     
      A numeric constant that contains neither a decimal point nor an
      exponent is initially presumed to be type integer if its
      value fits in type integer (32 bits); otherwise it is
@@ -418,7 +418,7 @@ 
    Caution
    
      the constant will be automatically coerced to the most
      appropriate type depending on context.  When necessary, you can
      force a numeric value to be interpreted as a specific data type
-     by casting it.
+     by casting it.
      For example, you can force a numeric value to be treated as type
      real (float4) by writing
 
@@ -434,7 +434,7 @@ 
    Caution
    
 
    
 
    
 4.1.2.5. Constants of Other Types
    
-
         A constant of an arbitrary type can be
+
         A constant of an arbitrary type can be
      entered using any one of the following notations:
 
    
 
    type 'string'
@@ -481,7 +481,7 @@ 
    Caution
    
 
    
 
    
 4.1.3. Operators
    
-
        An operator name is a sequence of up to NAMEDATALEN-1
+
        An operator name is a sequence of up to NAMEDATALEN-1
     (63 by default) characters from the following list:
 
    
 
    + - * / < > = ~ ! @ # % ^ & | ` ?
    
@@ -520,7 +520,7 @@ 
    Caution
    
 
    
 
    
 
    
-4.1.4. Special Characters
    
+4.1.4. Special Characters
    
 
       Some characters that are not alphanumeric have a special meaning
    that is different from being an operator.  Details on the usage can
    be found at the location where the respective syntax element is
@@ -572,7 +572,7 @@ 
    Caution
    
 
    
 
    
 4.1.5. Comments
    
-
        A comment is an arbitrary sequence of characters beginning with
+
        A comment is an arbitrary sequence of characters beginning with
     double dashes and extending to the end of the line, e.g.:
 
    
 
    -- This is a standard SQL comment
    
@@ -597,7 +597,7 @@ 
    Caution
    
 
    
 
    
 4.1.6. Lexical Precedence
    
-
        Table 4.1, “Operator Precedence (decreasing)” shows the precedence and
+
        Table 4.1, “Operator Precedence (decreasing)” shows the precedence and
     associativity of the operators in PostgreSQL.
     Most operators have the same precedence and are left-associative.
     The precedence and associativity of the operators is hard-wired
diff --git a/docs/en_US/pg/sql-truncate.html b/docs/en_US/pg/sql-truncate.html
index 2035bc95dc..7e52631b20 100644
--- a/docs/en_US/pg/sql-truncate.html
+++ b/docs/en_US/pg/sql-truncate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    TRUNCATE — empty a table or set of tables
    
 
    
-
    
+
    
 
    Synopsis
    
 
    TRUNCATE [ TABLE ] name [, ...] [ CASCADE | RESTRICT ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       TRUNCATE quickly removes all rows from a set of
    tables. It has the same effect as an unqualified
    DELETE on each table, but since it does not actually
@@ -30,7 +30,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          The name (optionally schema-qualified) of a table to be truncated.
@@ -47,7 +47,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       Only the owner of a table may TRUNCATE it.
   
    
 
       TRUNCATE cannot be used on a table that has foreign-key
@@ -63,7 +63,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Truncate the tables bigtable and fattable:
 
 
    
@@ -80,7 +80,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no TRUNCATE command in the SQL standard.
   
    
 
    
diff --git a/docs/en_US/pg/sql-unlisten.html b/docs/en_US/pg/sql-unlisten.html
index 577e676537..42ffe5038a 100644
--- a/docs/en_US/pg/sql-unlisten.html
+++ b/docs/en_US/pg/sql-unlisten.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,12 +17,12 @@
 
    Name
    
 
    UNLISTEN — stop listening for a notification
    
 
    
-
    
+
    
 
    Synopsis
    
 
    UNLISTEN { name | * }
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       UNLISTEN is used to remove an existing
    registration for NOTIFY events.
    UNLISTEN cancels any existing registration of
@@ -38,7 +38,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    name
    
 
          Name of a notification (any identifier).
@@ -49,7 +49,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       You may unlisten something you were not listening for; no warning or error
    will appear.
   
    
@@ -58,7 +58,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       To make a registration:
 
 
    
@@ -78,12 +78,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no UNLISTEN command in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 LISTEN, NOTIFY
 
    
 
    
diff --git a/docs/en_US/pg/sql-update.html b/docs/en_US/pg/sql-update.html
index f6b037ff37..232f8e96ba 100644
--- a/docs/en_US/pg/sql-update.html
+++ b/docs/en_US/pg/sql-update.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    UPDATE — update rows of a table
    
 
    
-
    
+
    
 
    Synopsis
    
 
    UPDATE [ ONLY ] table [ [ AS ] alias ]
     SET { column = { expression | DEFAULT } |
@@ -27,7 +27,7 @@ 
    Synopsis
    
     [ RETURNING * | output_expression [ AS output_name ] [, ...] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       UPDATE changes the values of the specified
    columns in all rows that satisfy the condition. Only the columns to
    be modified need be mentioned in the SET clause;
@@ -60,7 +60,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    table
    
 
          The name (optionally schema-qualified) of the table to update.
@@ -114,7 +114,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
       On successful completion, an UPDATE command returns a command
    tag of the form
 
    
@@ -133,7 +133,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       When a FROM clause is present, what essentially happens
    is that the target table is joined to the tables mentioned in the
    fromlist, and each output row of the join
@@ -151,7 +151,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       Change the word Drama to Dramatic in the
    column kind of the table films:
 
@@ -215,7 +215,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       This command conforms to the SQL standard, except
    that the FROM and RETURNING clauses
    are PostgreSQL extensions.
diff --git a/docs/en_US/pg/sql-vacuum.html b/docs/en_US/pg/sql-vacuum.html
index 288116ac06..86d824ca5d 100644
--- a/docs/en_US/pg/sql-vacuum.html
+++ b/docs/en_US/pg/sql-vacuum.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,13 +17,13 @@
 
    Name
    
 
    VACUUM — garbage-collect and optionally analyze a database
    
 
    
-
    
+
    
 
    Synopsis
    
 
    VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ table ]
 VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ table [ (column [, ...] ) ] ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       VACUUM reclaims storage occupied by deleted tuples.
    In normal PostgreSQL operation, tuples that
    are deleted or obsoleted by an update are not physically removed from
@@ -53,7 +53,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    FULL
    
 
          Selects “full” vacuum, which may reclaim more
@@ -84,14 +84,14 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Outputs
    
+
    Outputs
    
 
        When VERBOSE is specified, VACUUM emits
     progress messages to indicate which table is currently being
     processed.  Various statistics about the tables are printed as well.
    
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
        VACUUM cannot be executed inside a transaction block.
    
    
 
        We recommend that active production databases be
@@ -124,7 +124,7 @@ 
    Synopsis
    
    
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       The following is an example from running VACUUM on a
    table in the regression database:
 
@@ -161,12 +161,12 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       There is no VACUUM statement in the SQL standard.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 vacuumdb,        Cost-Based Vacuum Delay
      
 
    
diff --git a/docs/en_US/pg/sql-values.html b/docs/en_US/pg/sql-values.html
index da5b794963..900f09f49d 100644
--- a/docs/en_US/pg/sql-values.html
+++ b/docs/en_US/pg/sql-values.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -17,7 +17,7 @@
 
    Name
    
 
    VALUES — compute a set of rows
    
 
    
-
    
+
    
 
    Synopsis
    
 
    VALUES ( expression [, ...] ) [, ...]
     [ ORDER BY sort_expression [ ASC | DESC | USING operator ] [, ...] ]
@@ -25,7 +25,7 @@ 
    Synopsis
    
     [ OFFSET start ]
    
 
    
 
    
-
    Description
    
+
    Description
    
 
       VALUES computes a row value or set of row values
    specified by value expressions.  It is most commonly used to generate
    a “constant table” within a larger command, but it can be
@@ -45,7 +45,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Parameters
    
+
    Parameters
    
 
    
 
    expression
    
 
          A constant or expression to compute and insert at the indicated place
@@ -79,7 +79,7 @@ 
    Synopsis
    
 
    
 
    
 
    
-
    Notes
    
+
    Notes
    
 
       VALUES lists with very large numbers of rows should be avoided,
    as you may encounter out-of-memory failures or poor performance.
    VALUES appearing within INSERT is a special case
@@ -89,7 +89,7 @@ 
    Synopsis
    
   
    
 
    
 
    
-
    Examples
    
+
    Examples
    
 
       A bare VALUES command:
 
 
    
@@ -168,14 +168,14 @@ 
    Tip
    
 
    
 
    
 
    
-
    Compatibility
    
+
    Compatibility
    
 
       VALUES conforms to the SQL standard, except that
    LIMIT and OFFSET are
    PostgreSQL extensions.
   
    
 
    
 
    
-
    See Also
    
+
    See Also
    
 INSERT, SELECT
 
    
 
    
diff --git a/docs/en_US/pg/sql.html b/docs/en_US/pg/sql.html
index fd83956eee..ad214fe334 100644
--- a/docs/en_US/pg/sql.html
+++ b/docs/en_US/pg/sql.html
@@ -5,8 +5,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 Part II. The SQL Language
    
-
    
+
    
 
    
 
        This part describes the use of the SQL language
     in PostgreSQL.  We start with
@@ -54,18 +54,18 @@
 
    4.1.1. Identifiers and Key Words
    
 
    4.1.2. Constants
    
 
    4.1.3. Operators
    
-
    4.1.4. Special Characters
    
+
    4.1.4. Special Characters
    
 
    4.1.5. Comments
    
 
    4.1.6. Lexical Precedence
    
 
 
    4.2. Value Expressions
    
 
    
-
    4.2.1. Column References
    
-
    4.2.2. Positional Parameters
    
-
    4.2.3. Subscripts
    
-
    4.2.4. Field Selection
    
-
    4.2.5. Operator Invocations
    
-
    4.2.6. Function Calls
    
+
    4.2.1. Column References
    
+
    4.2.2. Positional Parameters
    
+
    4.2.3. Subscripts
    
+
    4.2.4. Field Selection
    
+
    4.2.5. Operator Invocations
    
+
    4.2.6. Function Calls
    
 
    4.2.7. Aggregate Expressions
    
 
    4.2.8. Type Casts
    
 
    4.2.9. Scalar Subqueries
    
@@ -80,23 +80,23 @@
 
    5.2. Default Values
    
 
    5.3. Constraints
    
 
    
-
    5.3.1. Check Constraints
    
-
    5.3.2. Not-Null Constraints
    
-
    5.3.3. Unique Constraints
    
-
    5.3.4. Primary Keys
    
+
    5.3.1. Check Constraints
    
+
    5.3.2. Not-Null Constraints
    
+
    5.3.3. Unique Constraints
    
+
    5.3.4. Primary Keys
    
 
    5.3.5. Foreign Keys
    
 
    
 
    5.4. System Columns
    
 
    5.5. Modifying Tables
    
 
    
-
    5.5.1. Adding a Column
    
-
    5.5.2. Removing a Column
    
-
    5.5.3. Adding a Constraint
    
-
    5.5.4. Removing a Constraint
    
-
    5.5.5. Changing a Column's Default Value
    
-
    5.5.6. Changing a Column's Data Type
    
-
    5.5.7. Renaming a Column
    
-
    5.5.8. Renaming a Table
    
+
    5.5.1. Adding a Column
    
+
    5.5.2. Removing a Column
    
+
    5.5.3. Adding a Constraint
    
+
    5.5.4. Removing a Constraint
    
+
    5.5.5. Changing a Column's Default Value
    
+
    5.5.6. Changing a Column's Data Type
    
+
    5.5.7. Renaming a Column
    
+
    5.5.8. Renaming a Table
    
 
    
 
    5.6. Privileges
    
 
    5.7. Schemas
    
@@ -170,12 +170,12 @@
 
    8.6. Boolean Type
    
 
    8.7. Geometric Types
    
 
    
-
    8.7.1. Points
    
-
    8.7.2. Line Segments
    
-
    8.7.3. Boxes
    
-
    8.7.4. Paths
    
-
    8.7.5. Polygons
    
-
    8.7.6. Circles
    
+
    8.7.1. Points
    
+
    8.7.2. Line Segments
    
+
    8.7.3. Boxes
    
+
    8.7.4. Paths
    
+
    8.7.5. Polygons
    
+
    8.7.6. Circles
    
 
    
 
    8.8. Network Address Types
    
 
    
@@ -187,20 +187,20 @@
 
    8.9. Bit String Types
    
 
    8.10. Arrays
    
 
    
-
    8.10.1. Declaration of Array Types
    
-
    8.10.2. Array Value Input
    
-
    8.10.3. Accessing Arrays
    
-
    8.10.4. Modifying Arrays
    
-
    8.10.5. Searching in Arrays
    
-
    8.10.6. Array Input and Output Syntax
    
+
    8.10.1. Declaration of Array Types
    
+
    8.10.2. Array Value Input
    
+
    8.10.3. Accessing Arrays
    
+
    8.10.4. Modifying Arrays
    
+
    8.10.5. Searching in Arrays
    
+
    8.10.6. Array Input and Output Syntax
    
 
    
 
    8.11. Composite Types
    
 
    
-
    8.11.1. Declaration of Composite Types
    
-
    8.11.2. Composite Value Input
    
-
    8.11.3. Accessing Composite Types
    
-
    8.11.4. Modifying Composite Types
    
-
    8.11.5. Composite Type Input and Output Syntax
    
+
    8.11.1. Declaration of Composite Types
    
+
    8.11.2. Composite Value Input
    
+
    8.11.3. Accessing Composite Types
    
+
    8.11.4. Modifying Composite Types
    
+
    8.11.5. Composite Type Input and Output Syntax
    
 
    
 
    8.12. Object Identifier Types
    
 
    8.13. Pseudo-Types
    
@@ -234,28 +234,28 @@
 
    9.12. Sequence Manipulation Functions
    
 
    9.13. Conditional Expressions
    
 
    
-
    9.13.1. CASE
    
-
    9.13.2. COALESCE
    
-
    9.13.3. NULLIF
    
-
    9.13.4. GREATEST and LEAST
    
+
    9.13.1. CASE
    
+
    9.13.2. COALESCE
    
+
    9.13.3. NULLIF
    
+
    9.13.4. GREATEST and LEAST
    
 
    
 
    9.14. Array Functions and Operators
    
 
    9.15. Aggregate Functions
    
 
    9.16. Subquery Expressions
    
 
    
-
    9.16.1. EXISTS
    
-
    9.16.2. IN
    
-
    9.16.3. NOT IN
    
-
    9.16.4. ANY/SOME
    
-
    9.16.5. ALL
    
-
    9.16.6. Row-wise Comparison
    
+
    9.16.1. EXISTS
    
+
    9.16.2. IN
    
+
    9.16.3. NOT IN
    
+
    9.16.4. ANY/SOME
    
+
    9.16.5. ALL
    
+
    9.16.6. Row-wise Comparison
    
 
    
 
    9.17. Row and Array Comparisons
    
 
    
-
    9.17.1. IN
    
-
    9.17.2. NOT IN
    
-
    9.17.3. ANY/SOME (array)
    
-
    9.17.4. ALL (array)
    
+
    9.17.1. IN
    
+
    9.17.2. NOT IN
    
+
    9.17.3. ANY/SOME (array)
    
+
    9.17.4. ALL (array)
    
 
    9.17.5. Row-wise Comparison
    
 
    
 
    9.18. Set Returning Functions
    
diff --git a/docs/en_US/pg/ssh-tunnels.html b/docs/en_US/pg/ssh-tunnels.html
index 213615e443..6e78e0ab18 100644
--- a/docs/en_US/pg/ssh-tunnels.html
+++ b/docs/en_US/pg/ssh-tunnels.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 16.8. Secure TCP/IP Connections with SSH Tunnels
    
-
       One can use SSH to encrypt the network
+
       One can use SSH to encrypt the network
    connection between clients and a
    PostgreSQL server. Done properly, this
    provides an adequately secure network connection, even for non-SSL-capable
diff --git a/docs/en_US/pg/ssl-tcp.html b/docs/en_US/pg/ssl-tcp.html
index 20c46fcff3..078b409211 100644
--- a/docs/en_US/pg/ssl-tcp.html
+++ b/docs/en_US/pg/ssl-tcp.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 16.7. Secure TCP/IP Connections with SSL
    
-
       PostgreSQL has native support for using
+
       PostgreSQL has native support for using
    SSL connections to encrypt client/server communications
    for increased security. This requires that
    OpenSSL is installed on both client and
diff --git a/docs/en_US/pg/storage-page-layout.html b/docs/en_US/pg/storage-page-layout.html
index e7f2ad5406..6e6713b2c5 100644
--- a/docs/en_US/pg/storage-page-layout.html
+++ b/docs/en_US/pg/storage-page-layout.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -15,7 +15,7 @@
 
    
 52.3. Database Page Layout
    
 
    This section provides an overview of the page format used within
-PostgreSQL tables and indexes.[10]
+PostgreSQL tables and indexes.[10]
 Sequences and TOAST tables are formatted just like a regular table.
    
 
    In the following explanation, a
 byte
@@ -316,7 +316,7 @@
  
    
 
    
 
    
-
    [10]     Actually, index access methods need not use this page format.
+
    [10]     Actually, index access methods need not use this page format.
     All the existing index methods do use this basic format,
     but the data kept on index metapages usually doesn't follow
     the item layout rules.
diff --git a/docs/en_US/pg/storage-toast.html b/docs/en_US/pg/storage-toast.html
index a335fcfb06..74e366779b 100644
--- a/docs/en_US/pg/storage-toast.html
+++ b/docs/en_US/pg/storage-toast.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 52.2. TOAST
    
-
    This section provides an overview of TOAST (The
+
    This section provides an overview of TOAST (The
 Oversized-Attribute Storage Technique).
    
 
    PostgreSQL uses a fixed page size (commonly
 8 kB), and does not allow tuples to span multiple pages.  Therefore,  it is
diff --git a/docs/en_US/pg/storage.html b/docs/en_US/pg/storage.html
index 4df5b91c08..2ad9f86f25 100644
--- a/docs/en_US/pg/storage.html
+++ b/docs/en_US/pg/storage.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/supported-platforms.html b/docs/en_US/pg/supported-platforms.html
index ae5f8088c3..c875b69c8e 100644
--- a/docs/en_US/pg/supported-platforms.html
+++ b/docs/en_US/pg/supported-platforms.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/transaction-iso.html b/docs/en_US/pg/transaction-iso.html
index 8b556a4e7b..66f7abb3b5 100644
--- a/docs/en_US/pg/transaction-iso.html
+++ b/docs/en_US/pg/transaction-iso.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 12.2. Transaction Isolation
    
-
        The SQL standard defines four levels of
+
        The SQL standard defines four levels of
     transaction isolation in terms of three phenomena that must be
     prevented between concurrent transactions.  These undesirable
     phenomena are:
@@ -22,19 +22,19 @@
     
    
 
    
 
           dirty read
-       
+       
       
    
 
            A transaction reads data written by a concurrent uncommitted transaction.
        
    
 
           nonrepeatable read
-       
+       
       
    
 
            A transaction re-reads data it has previously read and finds that data
         has been modified by another transaction (that committed since the
         initial read).
        
    
 
           phantom read
-       
+       
       
    
 
            A transaction re-executes a query returning a set of rows that satisfy a
         search condition and finds that the set of rows satisfying the condition
@@ -43,7 +43,7 @@
 
    
 
    
    
    
-
        
+
        
     The four transaction isolation levels and the corresponding
     behaviors are described in Table 12.1, “SQL Transaction Isolation Levels”.
    
    
@@ -131,7 +131,7 @@
 
    
 
    
 12.2.1. Read Committed Isolation Level
    
-
        Read Committed
+
        Read Committed
     is the default isolation level in PostgreSQL. 
     When a transaction runs on this isolation level,
     a SELECT query sees only data committed before the
@@ -206,7 +206,7 @@
 
    
 
    
 12.2.2. Serializable Isolation Level
    
-
        The level Serializable provides the strictest transaction
+
        The level Serializable provides the strictest transaction
     isolation.  This level emulates serial transaction execution,
     as if transactions had been executed one after another, serially,
     rather than concurrently.  However, applications using this level must
@@ -272,7 +272,7 @@
 
    
 
    
 12.2.2.1. Serializable Isolation versus True Serializability
    
-
        The intuitive meaning (and mathematical definition) of
+
        The intuitive meaning (and mathematical definition) of
     “serializable” execution is that any two successfully committed
     concurrent transactions will appear to have executed strictly serially,
     one after the other — although which one appeared to occur first may
@@ -316,7 +316,7 @@
     SELECT ... WHERE class = 1, a predicate-locking system
     would forbid transaction B from inserting any new row with class 1
     until A has committed.
-     [6]
+     [6]
     Such a locking system is complex to
     implement and extremely expensive in execution, since every session must
     be aware of the details of every query executed by every concurrent
@@ -336,7 +336,7 @@
 
    
 
    
 
    
-
    [6]        Essentially, a predicate-locking system prevents phantom reads
+
    [6]        Essentially, a predicate-locking system prevents phantom reads
        by restricting what is written, whereas MVCC prevents them by
        restricting what is read.
       
    
diff --git a/docs/en_US/pg/trigger-datachanges.html b/docs/en_US/pg/trigger-datachanges.html
index 585acd64ff..eaf51f9be5 100644
--- a/docs/en_US/pg/trigger-datachanges.html
+++ b/docs/en_US/pg/trigger-datachanges.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/trigger-example.html b/docs/en_US/pg/trigger-example.html
index 8e235d592d..c5d27e493b 100644
--- a/docs/en_US/pg/trigger-example.html
+++ b/docs/en_US/pg/trigger-example.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/trigger-interface.html b/docs/en_US/pg/trigger-interface.html
index bc1d19ce86..93d008e833 100644
--- a/docs/en_US/pg/trigger-interface.html
+++ b/docs/en_US/pg/trigger-interface.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 34.3. Writing Trigger Functions in C
    
-
        This section describes the low-level details of the interface to a
+
        This section describes the low-level details of the interface to a
     trigger function.  This information is only needed when writing
     trigger functions in C.  If you are using a higher-level language then
     these details are handled for you.  In most cases you should consider
diff --git a/docs/en_US/pg/triggers.html b/docs/en_US/pg/triggers.html
index 9ec2444f9b..5ff1ba975b 100644
--- a/docs/en_US/pg/triggers.html
+++ b/docs/en_US/pg/triggers.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -23,7 +23,7 @@
 
    34.4. A Complete Example
    
 
    
 
    
-
       This chapter provides general information about writing trigger functions.
+
       This chapter provides general information about writing trigger functions.
    Trigger functions can be written in most of the available procedural
    languages, including
    PL/pgSQL (Chapter 37, PL/pgSQL - SQL Procedural Language),
@@ -150,7 +150,7 @@
     to avoid infinite recursion in such scenarios.
    
    
 
        When a trigger is being defined, arguments can be specified for
-    it. The purpose of including arguments in the
+    it. The purpose of including arguments in the
     trigger definition is to allow different triggers with similar
     requirements to call the same function.  As an example, there
     could be a generalized trigger function that takes as its
diff --git a/docs/en_US/pg/tutorial-accessdb.html b/docs/en_US/pg/tutorial-accessdb.html
index 2d4bcea68c..a4415bdfb4 100644
--- a/docs/en_US/pg/tutorial-accessdb.html
+++ b/docs/en_US/pg/tutorial-accessdb.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
    
 
    
 1.4. Accessing a Database
    
-
        Once you have created a database, you can access it by:
+
        Once you have created a database, you can access it by:
 
     
    
 
      
@@ -49,7 +49,7 @@
 
          In psql, you will be greeted with the following
     message:
 
      
-
      Welcome to psql 8.2.0, the PostgreSQL interactive terminal.
+
      Welcome to psql 8.2.1, the PostgreSQL interactive terminal.
  
 Type:  \copyright for distribution terms
        \h for help with SQL commands
@@ -59,7 +59,7 @@
  
 mydb=>
      
 
      
-    
+    
     The last line could also be
 
      
 
      mydb=#
      
@@ -80,12 +80,12 @@
     to you and that you can type SQL queries into a
     work space maintained by psql.  Try out these
     commands:
-    
+    
 
      
 
      mydb=> SELECT version();
                             version
 ----------------------------------------------------------------
- PostgreSQL 8.2.0 on i586-pc-linux-gnu, compiled by GCC 2.96
+ PostgreSQL 8.2.1 on i586-pc-linux-gnu, compiled by GCC 2.96
 (1 row)
 
 mydb=> SELECT current_date;
diff --git a/docs/en_US/pg/tutorial-advanced.html b/docs/en_US/pg/tutorial-advanced.html
index 1d967741dd..2cb9d561be 100644
--- a/docs/en_US/pg/tutorial-advanced.html
+++ b/docs/en_US/pg/tutorial-advanced.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/tutorial-agg.html b/docs/en_US/pg/tutorial-agg.html
index 511f6f0fc3..22bb0ede9d 100644
--- a/docs/en_US/pg/tutorial-agg.html
+++ b/docs/en_US/pg/tutorial-agg.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,11 +14,11 @@
 
      
 
      
 2.7. Aggregate Functions
      
-
          
-    
-    
-    
-    
+
          
+    
+    
+    
+    
 
     Like  most  other relational database products, 
     PostgreSQL supports
@@ -43,7 +43,7 @@
 (1 row)
      
 
      
    
      
-
          
+
          
 
     If we wanted to know what city (or cities) that reading occurred in,
     we might try
@@ -78,8 +78,8 @@
     that computes its own aggregate separately from what is happening
     in the outer query.
    
      
-
          
-    
+
          
+    
 
     Aggregates are also very useful in combination with GROUP
     BY clauses.  For example, we can get the maximum low
diff --git a/docs/en_US/pg/tutorial-arch.html b/docs/en_US/pg/tutorial-arch.html
index 5dc4a468c0..02fd63ce12 100644
--- a/docs/en_US/pg/tutorial-arch.html
+++ b/docs/en_US/pg/tutorial-arch.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -32,7 +32,7 @@
        performs actions on the database on behalf of the clients.  The
        database server program is called
        postgres.
-       
+       
       
      
 
    •        The user's client (frontend) application that wants to perform
        database operations.  Client applications can be very diverse
diff --git a/docs/en_US/pg/tutorial-concepts.html b/docs/en_US/pg/tutorial-concepts.html
index 7380ce130a..3e916814ef 100644
--- a/docs/en_US/pg/tutorial-concepts.html
+++ b/docs/en_US/pg/tutorial-concepts.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,11 +14,11 @@
 
      
 
      
 2.2. Concepts
      
-
          
-    
-    
-    
-    
+
          
+    
+    
+    
+    
 
     PostgreSQL is a relational
     database management system (RDBMS).
@@ -31,8 +31,8 @@
     operating systems form an example of a hierarchical database.  A
     more modern development is the object-oriented database.
    
      
-
          
-    
+
          
+    
 
     Each table is a named collection of rows.
     Each row of a given table has the same set of named
@@ -42,8 +42,8 @@
     does not guarantee the order of the rows within the table in any
     way (although they can be explicitly sorted for display).
    
      
-
          
-    
+
          
+    
 
     Tables are grouped into databases, and a collection of databases
     managed by a single PostgreSQL server
diff --git a/docs/en_US/pg/tutorial-conclusion.html b/docs/en_US/pg/tutorial-conclusion.html
index 1e4945e3ca..9f46b7a708 100644
--- a/docs/en_US/pg/tutorial-conclusion.html
+++ b/docs/en_US/pg/tutorial-conclusion.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/tutorial-createdb.html b/docs/en_US/pg/tutorial-createdb.html
index a255551676..d4caf000e4 100644
--- a/docs/en_US/pg/tutorial-createdb.html
+++ b/docs/en_US/pg/tutorial-createdb.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 1.3. Creating a Database
      
-
          The first test to see whether you can access the database server
+
          The first test to see whether you can access the database server
     is to try to create a database.  A running
     PostgreSQL server can manage many
     databases.  Typically, a separate database is used for each
@@ -91,7 +91,7 @@
     yourself then you should log in for the purposes of this tutorial
     under the user account that you started the server as.
 
-    [1]
+    [1]
    
      
 
          You can also create databases with other names.
     PostgreSQL allows you to create any
@@ -124,7 +124,7 @@
    
      
 
      
 
      
-
      [1]       As an explanation for why this works:
+
      [1]       As an explanation for why this works:
       PostgreSQL user names are separate
       from operating system user accounts.  When you connect to a
       database, you can choose what
diff --git a/docs/en_US/pg/tutorial-delete.html b/docs/en_US/pg/tutorial-delete.html
index 31fcd290ca..dd7b34293e 100644
--- a/docs/en_US/pg/tutorial-delete.html
+++ b/docs/en_US/pg/tutorial-delete.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 2.9. Deletions
      
-
          Rows can be removed from a table using the DELETE
+
          Rows can be removed from a table using the DELETE
     command.
     Suppose you are no longer interested in the weather of Hayward.
     Then you can do the following to delete those rows from the table:
diff --git a/docs/en_US/pg/tutorial-fk.html b/docs/en_US/pg/tutorial-fk.html
index c224fe106c..280f101a73 100644
--- a/docs/en_US/pg/tutorial-fk.html
+++ b/docs/en_US/pg/tutorial-fk.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 3.3. Foreign Keys
      
-
          Recall the weather and
+
          Recall the weather and
     cities tables from Chapter 2, The SQL Language.  Consider the following problem:  You
     want to make sure that no one can insert rows in the
     weather table that do not have a matching
diff --git a/docs/en_US/pg/tutorial-inheritance.html b/docs/en_US/pg/tutorial-inheritance.html
index 20f4fdd20d..ef842f8369 100644
--- a/docs/en_US/pg/tutorial-inheritance.html
+++ b/docs/en_US/pg/tutorial-inheritance.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 3.5. Inheritance
      
-
          Inheritance is a concept from object-oriented databases.  It opens
+
          Inheritance is a concept from object-oriented databases.  It opens
     up interesting new possibilities of database design.
    
      
 
          Let's create two tables:  A table cities
diff --git a/docs/en_US/pg/tutorial-join.html b/docs/en_US/pg/tutorial-join.html
index 85ec37497b..5a7d3d5f94 100644
--- a/docs/en_US/pg/tutorial-join.html
+++ b/docs/en_US/pg/tutorial-join.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 2.6. Joins Between Tables
      
-
          Thus far, our queries have only accessed one table at a time.
+
          Thus far, our queries have only accessed one table at a time.
     Queries can access multiple tables at once, or access the same
     table in such a way that multiple rows of the table are being
     processed at the same time.  A query that accesses multiple rows
@@ -108,7 +108,7 @@ 
      Note
      
     This syntax is not as commonly used as the one above, but we show
     it here to help you understand the following topics.
    
      
-
          
+
          
 
     Now we will figure out how we can get the Hayward records back in.
     What we want the query to do is to scan the
@@ -143,8 +143,8 @@ 
      Note
      
 
      Exercise:      There are also right outer joins and full outer joins.  Try to
      find out what those do.
     
      
-
          
-    
+
          
+    
 
     We can also join a table against itself.  This is called a
     self join.  As an example, suppose we wish
diff --git a/docs/en_US/pg/tutorial-populate.html b/docs/en_US/pg/tutorial-populate.html
index d581f369e2..fd7384d5c9 100644
--- a/docs/en_US/pg/tutorial-populate.html
+++ b/docs/en_US/pg/tutorial-populate.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 2.4. Populating a Table With Rows
      
-
          The INSERT statement is used to populate a table  with
+
          The INSERT statement is used to populate a table  with
     rows:
 
 
      
@@ -54,7 +54,7 @@
 
          Please enter all the commands shown above so you have some data to
     work with in the following sections.
    
      
-
          
+
          
 
     You could also have used COPY to load large
     amounts of data from flat-text files.  This is usually faster
diff --git a/docs/en_US/pg/tutorial-select.html b/docs/en_US/pg/tutorial-select.html
index 9a54f8e7f9..187fd508ff 100644
--- a/docs/en_US/pg/tutorial-select.html
+++ b/docs/en_US/pg/tutorial-select.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,8 +14,8 @@
 
      
 
      
 2.5. Querying a Table
      
-
          
-    
+
          
+    
 
     To retrieve data from a table, the table is
     queried.  An SQL
@@ -30,7 +30,7 @@
 
      SELECT * FROM weather;
      
 
      
     Here * is a shorthand for “all columns”.
-     [2]
+     [2]
     So the same result would be had with:
 
      
 
      SELECT city, temp_lo, temp_hi, prcp, date FROM weather;
      
@@ -85,7 +85,7 @@
 (1 row)
      • 
 
      
    
      
-
          
+
          
 
     You can request that the results of a query
     be returned in sorted order:
@@ -112,8 +112,8 @@
     ORDER BY city, temp_lo;
 
      
    
      
-
          
-    
+
          
+    
 
     You can request that duplicate rows be removed from the result of
     a query:
@@ -134,7 +134,7 @@
     Here again, the result row ordering might vary.
     You can ensure consistent results by using DISTINCT and
     ORDER BY together:
-     [3]
+     [3]
 
 
      
 
      SELECT DISTINCT city
@@ -144,11 +144,11 @@
    
      
 
      
 
      
-
      [2]        While SELECT * is useful for off-the-cuff
+
      [2]        While SELECT * is useful for off-the-cuff
        queries, it is widely considered bad style in production code,
        since adding a column to the table would change the results.
       
      
-
      [3]        In some database systems, including older versions of
+
      [3]        In some database systems, including older versions of
        PostgreSQL, the implementation of
        DISTINCT automatically orders the rows and
        so ORDER BY is unnecessary.  But this is not
diff --git a/docs/en_US/pg/tutorial-sql.html b/docs/en_US/pg/tutorial-sql.html
index fb49de80b9..d6e02b0177 100644
--- a/docs/en_US/pg/tutorial-sql.html
+++ b/docs/en_US/pg/tutorial-sql.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/tutorial-start.html b/docs/en_US/pg/tutorial-start.html
index bb80f90e4e..7edb89b03d 100644
--- a/docs/en_US/pg/tutorial-start.html
+++ b/docs/en_US/pg/tutorial-start.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/tutorial-table.html b/docs/en_US/pg/tutorial-table.html
index 8ca3f34036..cd433aa0e9 100644
--- a/docs/en_US/pg/tutorial-table.html
+++ b/docs/en_US/pg/tutorial-table.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 2.3. Creating a New Table
      
-
          You  can  create  a  new  table by specifying the table
+
          You  can  create  a  new  table by specifying the table
     name, along with all column names and their types:
 
 
      
@@ -72,7 +72,7 @@
     The point type is an example of a
     PostgreSQL-specific data type.
    
      
-
          
+
          
 
     Finally, it should be mentioned that if you don't need a table any
     longer or want to recreate it differently you can remove it using
diff --git a/docs/en_US/pg/tutorial-transactions.html b/docs/en_US/pg/tutorial-transactions.html
index e0322ab9b0..ea6b65a13f 100644
--- a/docs/en_US/pg/tutorial-transactions.html
+++ b/docs/en_US/pg/tutorial-transactions.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 3.4. Transactions
      
-
          Transactions are a fundamental concept of all database
+
          Transactions are a fundamental concept of all database
     systems.  The essential point of a transaction is that it bundles
     multiple steps into a single, all-or-nothing operation.  The intermediate
     states between the steps are not visible to other concurrent transactions,
diff --git a/docs/en_US/pg/tutorial-update.html b/docs/en_US/pg/tutorial-update.html
index e25974349d..ba8e7e5693 100644
--- a/docs/en_US/pg/tutorial-update.html
+++ b/docs/en_US/pg/tutorial-update.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 2.8. Updates
      
-
          You can update existing rows using the
+
          You can update existing rows using the
     UPDATE command. 
     Suppose you discover the temperature readings are
     all off by 2 degrees after November 28.  You may correct the
diff --git a/docs/en_US/pg/tutorial-views.html b/docs/en_US/pg/tutorial-views.html
index 6cec7e1f5f..e48776ac87 100644
--- a/docs/en_US/pg/tutorial-views.html
+++ b/docs/en_US/pg/tutorial-views.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 3.2. Views
      
-
          Refer back to the queries in Section 2.6, “Joins Between Tables”.
+
          Refer back to the queries in Section 2.6, “Joins Between Tables”.
     Suppose the combined listing of weather records and city location
     is of particular interest to your application, but you do not want
     to type the query each time you need it.  You can create a
diff --git a/docs/en_US/pg/tutorial.html b/docs/en_US/pg/tutorial.html
index 1b65c73b78..03afa413db 100644
--- a/docs/en_US/pg/tutorial.html
+++ b/docs/en_US/pg/tutorial.html
@@ -5,8 +5,8 @@
 
 
 
-
-
+
+
 
 
 
@@ -14,7 +14,7 @@
 
      
 
      
 Part I. Tutorial
      
-
      
+
      
 
      
 
          Welcome to the PostgreSQL Tutorial.  The
     following few chapters are intended to give a simple introduction
diff --git a/docs/en_US/pg/typeconv-func.html b/docs/en_US/pg/typeconv-func.html
index 40db685d16..79dd61aaa0 100644
--- a/docs/en_US/pg/typeconv-func.html
+++ b/docs/en_US/pg/typeconv-func.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,11 +14,11 @@
 
      
 
      
 10.3. Functions
      
-
         The specific function to be used in a function invocation is determined
+
         The specific function to be used in a function invocation is determined
    according to the following steps.
   
      
 
      
-
      Function Type Resolution
      
+
      Function Type Resolution
      
 
        
 
      1. 
 
        Select the functions to be considered from the
@@ -86,7 +86,7 @@
 function type resolution.
 Some examples follow.
        
 
        
-
        Example 10.4. Rounding Function Argument Type Resolution
        
+
        Example 10.4. Rounding Function Argument Type Resolution
        
 
        
 
        There is only one round function with two
 arguments.  (The first is numeric, the second is
@@ -114,7 +114,7 @@
 
        
 
        
 
        
-
        Example 10.5. Substring Function Type Resolution
        
+
        Example 10.5. Substring Function Type Resolution
        
 
        
 
        There are several substr functions, one of which
 takes types text and integer.  If called
diff --git a/docs/en_US/pg/typeconv-oper.html b/docs/en_US/pg/typeconv-oper.html
index 8b56b21db2..fc6cfe1f2e 100644
--- a/docs/en_US/pg/typeconv-oper.html
+++ b/docs/en_US/pg/typeconv-oper.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,13 +14,13 @@
 
        
 
        
 10.2. Operators
        
-
           The specific operator to be used in an operator invocation is determined
+
           The specific operator to be used in an operator invocation is determined
    by following
    the procedure below.  Note that this procedure is indirectly affected
    by the precedence of the involved operators.  See Section 4.1.6, “Lexical Precedence” for more information.
   
        
 
        
-
        Operator Type Resolution
        
+
        Operator Type Resolution
        
 
          
 
        1. 
 
          Select the operators to be considered from the
@@ -82,7 +82,7 @@
 
        
 
        Some examples follow.
        
 
        
-
        Example 10.1. Exponentiation Operator Type Resolution
        
+
        Example 10.1. Exponentiation Operator Type Resolution
        
 
        
 
        There is only one exponentiation
 operator defined in the catalog, and it takes arguments of type 
@@ -106,7 +106,7 @@
 
        
 
        
 
        
-
        Example 10.2. String Concatenation Operator Type Resolution
        
+
        Example 10.2. String Concatenation Operator Type Resolution
        
 
        
 
        A string-like syntax is used for working with string types as well as for
 working with complex extension types.
@@ -140,7 +140,7 @@
 
        
 
        
 
        
-
        Example 10.3. Absolute-Value and Negation Operator Type Resolution
        
+
        Example 10.3. Absolute-Value and Negation Operator Type Resolution
        
 
        
 
        The PostgreSQL operator catalog has several
 entries for the prefix operator @, all of which implement
diff --git a/docs/en_US/pg/typeconv-query.html b/docs/en_US/pg/typeconv-query.html
index 1233f54b15..0fe504c6aa 100644
--- a/docs/en_US/pg/typeconv-query.html
+++ b/docs/en_US/pg/typeconv-query.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -19,7 +19,7 @@
    following steps.
   
        
 
        
-
        Value Storage Type Conversion
        
+
        Value Storage Type Conversion
        
 
          
 
        1. Check for an exact match with the target.
          2. 
 
        2. Otherwise, try to convert the expression to the target type.  This will succeed
@@ -40,7 +40,7 @@
 
        
 
        
 
        
-
        Example 10.6. character Storage Type Conversion
        
+
        Example 10.6. character Storage Type Conversion
        
 
        
 
        For a target column declared as character(20) the following statement
 ensures that the stored value is sized correctly:
diff --git a/docs/en_US/pg/typeconv-union-case.html b/docs/en_US/pg/typeconv-union-case.html
index 64abbca0e2..1425726171 100644
--- a/docs/en_US/pg/typeconv-union-case.html
+++ b/docs/en_US/pg/typeconv-union-case.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
        
 
        
 10.5. UNION, CASE, and Related Constructs
        
-
        SQL UNION constructs must match up possibly dissimilar
+
        SQL UNION constructs must match up possibly dissimilar
 types to become a single result set.  The resolution algorithm is
 applied separately to each output column of a union query.  The
 INTERSECT and EXCEPT constructs resolve
@@ -24,7 +24,7 @@
 algorithm to match up their component expressions and select a result
 data type.
        
 
        
-
        Type Resolution for UNION, CASE,
+
        Type Resolution for UNION, CASE,
 and Related Constructs
        
 
          
 
        1. If all inputs are of type unknown, resolve as type
@@ -39,7 +39,7 @@
 
        
 
        Some examples follow.
        
 
        
-
        Example 10.7. Type Resolution with Underspecified Types in a Union
        
+
        Example 10.7. Type Resolution with Underspecified Types in a Union
        
 
        
 
        SELECT text 'a' AS "text" UNION SELECT 'b';
 
@@ -53,7 +53,7 @@
 
        
 
        
 
        
-
        Example 10.8. Type Resolution in a Simple Union
        
+
        Example 10.8. Type Resolution in a Simple Union
        
 
        
 
        SELECT 1.2 AS "numeric" UNION SELECT 1;
 
@@ -69,7 +69,7 @@
 
        
 
        
 
        
-
        Example 10.9. Type Resolution in a Transposed Union
        
+
        Example 10.9. Type Resolution in a Transposed Union
        
 
        
 
        SELECT 1 AS "real" UNION SELECT CAST('2.2' AS REAL);
 
diff --git a/docs/en_US/pg/typeconv.html b/docs/en_US/pg/typeconv.html
index 54aa782e2d..8c4aa4d168 100644
--- a/docs/en_US/pg/typeconv.html
+++ b/docs/en_US/pg/typeconv.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -24,7 +24,7 @@
 
        10.5. UNION, CASE, and Related Constructs
        
 
 
        
-
        SQL statements can, intentionally or not, require
+
        SQL statements can, intentionally or not, require
 mixing of different data types in the same expression. 
 PostgreSQL has extensive facilities for
 evaluating mixed-type expressions.
        
@@ -109,7 +109,7 @@
 done in conjunction with defining new data types.  The set of casts
 between the built-in types has been carefully crafted and is best not
 altered.)
        
-
        An additional heuristic is provided in the parser to allow better guesses
+
        An additional heuristic is provided in the parser to allow better guesses
 at proper behavior for SQL standard types. There are
 several basic type categories defined: boolean,
 numeric, string, bitstring, datetime, timespan, geometric, network,
diff --git a/docs/en_US/pg/unsupported-features-sql-standard.html b/docs/en_US/pg/unsupported-features-sql-standard.html
index 25293938c4..196b125c4d 100644
--- a/docs/en_US/pg/unsupported-features-sql-standard.html
+++ b/docs/en_US/pg/unsupported-features-sql-standard.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/user-manag.html b/docs/en_US/pg/user-manag.html
index 897d364523..291e23ddd2 100644
--- a/docs/en_US/pg/user-manag.html
+++ b/docs/en_US/pg/user-manag.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -47,7 +47,7 @@
 
        
 
        
 18.1. Database Roles
        
-
           Database roles are conceptually completely separate from
+
           Database roles are conceptually completely separate from
    operating system users. In practice it might be convenient to
    maintain a correspondence, but this is not required. Database roles
    are global across a database cluster installation (and not
@@ -65,7 +65,7 @@
 
        DROP ROLE name;
        
 
        
   
        
-
           For convenience, the programs createuser
+
           For convenience, the programs createuser
    and dropuser are provided as wrappers
    around these SQL commands that can be called from the shell command
    line:
diff --git a/docs/en_US/pg/view-pg-cursors.html b/docs/en_US/pg/view-pg-cursors.html
index 695083e7e8..9b3feb3c66 100644
--- a/docs/en_US/pg/view-pg-cursors.html
+++ b/docs/en_US/pg/view-pg-cursors.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
        
 
        
 43.36. pg_cursors
        
-
           The pg_cursors view lists the cursors that
+
           The pg_cursors view lists the cursors that
    are currently available. Cursors can be defined in several ways:
    
        
 
          
@@ -49,7 +49,7 @@ 
          Note
          
 
          
   
          
 
          
-
          Table 43.36. pg_cursors Columns
          
+
          Table 43.36. pg_cursors Columns
          
 
          diff --git a/docs/en_US/pg/view-pg-group.html b/docs/en_US/pg/view-pg-group.html
index 32d5c9fc59..d518ca81ab 100644
--- a/docs/en_US/pg/view-pg-group.html
+++ b/docs/en_US/pg/view-pg-group.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.37. pg_group
          
-
             The view pg_group exists for backwards
+
             The view pg_group exists for backwards
    compatibility: it emulates a catalog that existed in
    PostgreSQL before version 8.1.
    It shows the names and members of all roles that are marked as not
@@ -22,7 +22,7 @@
    of roles that are being used as groups.
   
          
 
          
-
          Table 43.37. pg_group Columns
          
+
          Table 43.37. pg_group Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-indexes.html b/docs/en_US/pg/view-pg-indexes.html
index f0a2f00d5e..bf8cf506df 100644
--- a/docs/en_US/pg/view-pg-indexes.html
+++ b/docs/en_US/pg/view-pg-indexes.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,11 +14,11 @@
 
          
 
          
 43.38. pg_indexes
          
-
             The view pg_indexes provides access to
+
             The view pg_indexes provides access to
    useful information about each index in the database.
   
          
 
          
-
          Table 43.38. pg_indexes Columns
          
+
          Table 43.38. pg_indexes Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-locks.html b/docs/en_US/pg/view-pg-locks.html
index 0f286ed295..db91864e6c 100644
--- a/docs/en_US/pg/view-pg-locks.html
+++ b/docs/en_US/pg/view-pg-locks.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.39. pg_locks
          
-
             The view pg_locks provides access to
+
             The view pg_locks provides access to
    information about the locks held by open transactions within the
    database server.  See Chapter 12, Concurrency Control for more discussion
    of locking.
@@ -36,7 +36,7 @@
    relation is represented as a separate lockable object.
   
          
 
          
-
          Table 43.39. pg_locks Columns
          
+
          Table 43.39. pg_locks Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-prepared-statements.html b/docs/en_US/pg/view-pg-prepared-statements.html
index 95dd18d10a..019f7f1f72 100644
--- a/docs/en_US/pg/view-pg-prepared-statements.html
+++ b/docs/en_US/pg/view-pg-prepared-statements.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.40. pg_prepared_statements
          
-
             The pg_prepared_statements view displays
+
             The pg_prepared_statements view displays
    all the prepared statements that are available in the current
    session. See PREPARE for more information about prepared
    statements.
@@ -25,7 +25,7 @@
    is released (for example, via the DEALLOCATE command).
   
          
 
          
-
          Table 43.40. pg_prepared_statements Columns
          
+
          Table 43.40. pg_prepared_statements Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-prepared-xacts.html b/docs/en_US/pg/view-pg-prepared-xacts.html
index 8aeac33505..65ae66ab50 100644
--- a/docs/en_US/pg/view-pg-prepared-xacts.html
+++ b/docs/en_US/pg/view-pg-prepared-xacts.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.41. pg_prepared_xacts
          
-
             The view pg_prepared_xacts displays
+
             The view pg_prepared_xacts displays
    information about transactions that are currently prepared for two-phase
    commit (see PREPARE TRANSACTION for details).
   
          
@@ -23,7 +23,7 @@
    rolled back.
   
          
 
          
-
          Table 43.41. pg_prepared_xacts Columns
          
+
          Table 43.41. pg_prepared_xacts Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-roles.html b/docs/en_US/pg/view-pg-roles.html
index fd64d34c81..3bee3e0bb6 100644
--- a/docs/en_US/pg/view-pg-roles.html
+++ b/docs/en_US/pg/view-pg-roles.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.42. pg_roles
          
-
             The view pg_roles provides access to
+
             The view pg_roles provides access to
    information about database roles.  This is simply a publicly
    readable view of 
    pg_authid
@@ -24,7 +24,7 @@
    since that is needed to do joins to other catalogs.
   
          
 
          
-
          Table 43.42. pg_roles Columns
          
+
          Table 43.42. pg_roles Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-rules.html b/docs/en_US/pg/view-pg-rules.html
index c27a35640e..256eb7ac5f 100644
--- a/docs/en_US/pg/view-pg-rules.html
+++ b/docs/en_US/pg/view-pg-rules.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,11 +14,11 @@
 
          
 
          
 43.43. pg_rules
          
-
             The view pg_rules provides access to
+
             The view pg_rules provides access to
    useful information about query rewrite rules.
   
          
 
          
-
          Table 43.43. pg_rules Columns
          
+
          Table 43.43. pg_rules Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-settings.html b/docs/en_US/pg/view-pg-settings.html
index 351f2b2e2e..90ee2a18c3 100644
--- a/docs/en_US/pg/view-pg-settings.html
+++ b/docs/en_US/pg/view-pg-settings.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.44. pg_settings
          
-
             The view pg_settings provides access to
+
             The view pg_settings provides access to
    run-time parameters of the server.  It is essentially an alternative
    interface to the SHOW and SET commands.
    It also provides access to some facts about each parameter that are
@@ -22,7 +22,7 @@
    maximum values.
   
          
 
          
-
          Table 43.44. pg_settings Columns
          
+
          Table 43.44. pg_settings Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-shadow.html b/docs/en_US/pg/view-pg-shadow.html
index a96f6bfbfa..80de09e96d 100644
--- a/docs/en_US/pg/view-pg-shadow.html
+++ b/docs/en_US/pg/view-pg-shadow.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.45. pg_shadow
          
-
             The view pg_shadow exists for backwards
+
             The view pg_shadow exists for backwards
    compatibility: it emulates a catalog that existed in
    PostgreSQL before version 8.1.
    It shows properties of all roles that are marked as
@@ -27,7 +27,7 @@
    pg_shadow that blanks out the password field.
   
          
 
          
-
          Table 43.45. pg_shadow Columns
          
+
          Table 43.45. pg_shadow Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-stats.html b/docs/en_US/pg/view-pg-stats.html
index b70b533550..7b51edc961 100644
--- a/docs/en_US/pg/view-pg-stats.html
+++ b/docs/en_US/pg/view-pg-stats.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.46. pg_stats
          
-
             The view pg_stats provides access to
+
             The view pg_stats provides access to
    the information stored in the pg_statistic
    catalog.  This view allows access only to rows of
    pg_statistic that correspond to tables the
@@ -27,7 +27,7 @@
    are defined for pg_statistic.
   
          
 
          
-
          Table 43.46. pg_stats Columns
          
+
          Table 43.46. pg_stats Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-tables.html b/docs/en_US/pg/view-pg-tables.html
index 789b176e4b..6a436de471 100644
--- a/docs/en_US/pg/view-pg-tables.html
+++ b/docs/en_US/pg/view-pg-tables.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,11 +14,11 @@
 
          
 
          
 43.47. pg_tables
          
-
             The view pg_tables provides access to
+
             The view pg_tables provides access to
    useful information about each table in the database.
   
          
 
          
-
          Table 43.47. pg_tables Columns
          
+
          Table 43.47. pg_tables Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-timezone-abbrevs.html b/docs/en_US/pg/view-pg-timezone-abbrevs.html
index 99733b4234..2d40b2eb5e 100644
--- a/docs/en_US/pg/view-pg-timezone-abbrevs.html
+++ b/docs/en_US/pg/view-pg-timezone-abbrevs.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,13 +14,13 @@
 
          
 
          
 43.48. pg_timezone_abbrevs
          
-
             The view pg_timezone_abbrevs provides a list
+
             The view pg_timezone_abbrevs provides a list
    of time zone abbreviations that are currently recognized by the datetime
    input routines.  The contents of this view change when the
    timezone_abbreviations run-time parameter is modified.
   
          
 
          
-
          Table 43.48. pg_timezone_abbrevs Columns
          
+
          Table 43.48. pg_timezone_abbrevs Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-timezone-names.html b/docs/en_US/pg/view-pg-timezone-names.html
index db94392677..4e6e3f2f95 100644
--- a/docs/en_US/pg/view-pg-timezone-names.html
+++ b/docs/en_US/pg/view-pg-timezone-names.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,7 +14,7 @@
 
          
 
          
 43.49. pg_timezone_names
          
-
             The view pg_timezone_names provides a list
+
             The view pg_timezone_names provides a list
    of time zone names that are recognized by SET TIMEZONE,
    along with their associated abbreviations, UTC offsets,
    and daylight-savings status.
@@ -24,7 +24,7 @@
    value of CURRENT_TIMESTAMP.
   
          
 
          
-
          Table 43.49. pg_timezone_names Columns
          
+
          Table 43.49. pg_timezone_names Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-user.html b/docs/en_US/pg/view-pg-user.html
index b6acd40174..3ba51bf7f3 100644
--- a/docs/en_US/pg/view-pg-user.html
+++ b/docs/en_US/pg/view-pg-user.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,14 +14,14 @@
 
          
 
          
 43.50. pg_user
          
-
             The view pg_user provides access to
+
             The view pg_user provides access to
    information about database users.  This is simply a publicly
    readable view of 
    pg_shadow
    that blanks out the password field.
   
          
 
          
-
          Table 43.50. pg_user Columns
          
+
          Table 43.50. pg_user Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/view-pg-views.html b/docs/en_US/pg/view-pg-views.html
index bdeed13638..7fecdc80f9 100644
--- a/docs/en_US/pg/view-pg-views.html
+++ b/docs/en_US/pg/view-pg-views.html
@@ -5,7 +5,7 @@
 
-
+
@@ -14,11 +14,11 @@
 
          
 
          
 43.51. pg_views
          
-
             The view pg_views provides access to
+
             The view pg_views provides access to
    useful information about each view in the database.
   
          
 
          
-
          Table 43.51. pg_views Columns
          
+
          Table 43.51. pg_views Columns
          
 
          
 
 

 
 
 
 
 
          diff --git a/docs/en_US/pg/views-overview.html b/docs/en_US/pg/views-overview.html
index 7d3c15ab2e..3f085f6993 100644
--- a/docs/en_US/pg/views-overview.html
+++ b/docs/en_US/pg/views-overview.html
@@ -5,7 +5,7 @@
 
-
+
diff --git a/docs/en_US/pg/wal-configuration.html b/docs/en_US/pg/wal-configuration.html
index cc2dbb444a..d7bbbf0099 100644
--- a/docs/en_US/pg/wal-configuration.html
+++ b/docs/en_US/pg/wal-configuration.html
@@ -5,7 +5,7 @@
 
-
+
@@ -19,7 +19,7 @@
    Consult Chapter 17, Server Configuration for general information about
    setting server configuration parameters.
   
          
-
             Checkpoints
+
             Checkpoints
    are points in the sequence of transactions at which it is guaranteed
    that the data files have been updated with all information written before
    the checkpoint.  At checkpoint time, all dirty data pages are flushed to
diff --git a/docs/en_US/pg/wal-internals.html b/docs/en_US/pg/wal-internals.html
index 74eebb5d23..f1e32f157f 100644
--- a/docs/en_US/pg/wal-internals.html
+++ b/docs/en_US/pg/wal-internals.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -38,7 +38,7 @@
   
             The aim of WAL, to ensure that the log is
    written before database records are altered, may be subverted by
-   disk drives that falsely report a
+   disk drives that falsely report a
    successful write to the kernel, 
    when in fact they have only cached the data and not yet stored it
    on the disk.  A power failure in such a situation may still lead to
diff --git a/docs/en_US/pg/wal-intro.html b/docs/en_US/pg/wal-intro.html
index 6d002ae29a..550f4360c2 100644
--- a/docs/en_US/pg/wal-intro.html
+++ b/docs/en_US/pg/wal-intro.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 27.2. Write-Ahead Logging (WAL)
          
-
              Write-Ahead Logging (WAL)
+
              Write-Ahead Logging (WAL)
     is a standard approach to transaction logging.  Its detailed
     description may be found in most (if not all) books about
     transaction processing. Briefly, WAL's central
diff --git a/docs/en_US/pg/wal.html b/docs/en_US/pg/wal.html
index ca7933ffeb..b5b2b3328c 100644
--- a/docs/en_US/pg/wal.html
+++ b/docs/en_US/pg/wal.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/warm-standby.html b/docs/en_US/pg/warm-standby.html
index 486caa0791..bbe3d10dbf 100644
--- a/docs/en_US/pg/warm-standby.html
+++ b/docs/en_US/pg/warm-standby.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 23.4. Warm Standby Servers for High Availability
          
-
             Continuous archiving can be used to create a high
+
             Continuous archiving can be used to create a high
    availability (HA) cluster configuration with one or more
    standby servers ready to take 
    over operations if the primary server fails. This
@@ -263,7 +263,7 @@
 
          
 
          
 23.4.5. Incrementally Updated Backups
          
-
              In a warm standby configuration, it is possible to offload the expense of
+
              In a warm standby configuration, it is possible to offload the expense of
     taking periodic base backups from the primary server; instead base backups
     can be made by backing
     up a standby server's files.  This concept is generally known as 
diff --git a/docs/en_US/pg/xaggr.html b/docs/en_US/pg/xaggr.html
index 9ef3a92a8a..7f815db12b 100644
--- a/docs/en_US/pg/xaggr.html
+++ b/docs/en_US/pg/xaggr.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.10. User-Defined Aggregates
          
-
             Aggregate functions  in PostgreSQL 
+
             Aggregate functions  in PostgreSQL 
    are expressed in terms of state values
    and state transition functions.
    That is, an aggregate operates using a state value that is updated
diff --git a/docs/en_US/pg/xfunc-c.html b/docs/en_US/pg/xfunc-c.html
index 0c3117bcf5..6b968ede58 100644
--- a/docs/en_US/pg/xfunc-c.html
+++ b/docs/en_US/pg/xfunc-c.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.9. C-Language Functions
          
-
              User-defined functions can be written in C (or a language that can
+
              User-defined functions can be written in C (or a language that can
     be made compatible with C, such as C++).  Such functions are
     compiled into dynamically loadable objects (also called shared
     libraries) and are loaded by the server on demand.  The dynamic
@@ -36,7 +36,7 @@
 
          
 
          
 33.9.1. Dynamic Loading
          
-
              The first time a user-defined function in a particular
+
              The first time a user-defined function in a particular
     loadable object file is called in a session,
     the dynamic loader loads that object file into memory so that the
     function can be called.  The CREATE FUNCTION
@@ -57,11 +57,11 @@
 
        •        If the name starts with the string $libdir,
        that part is replaced by the PostgreSQL package
         library directory
-       name, which is determined at build time.
+       name, which is determined at build time.
       
          • 
 
        •        If the name does not contain a directory part, the file is
        searched for in the path specified by the configuration variable
-       dynamic_library_path.
+       dynamic_library_path.
       
          • 
 
        •        Otherwise (the file was not found in the path, or it contains a
        non-absolute directory part), the dynamic loader will try to
@@ -103,7 +103,7 @@ 
          Note
          
      information.
     
          
 
          • 
-
              To ensure that a dynamically loaded object file is not loaded into an
+
              To ensure that a dynamically loaded object file is not loaded into an
     incompatible server, PostgreSQL checks that the
     file contains a “magic block” with the appropriate contents.
     This allows the server to detect obvious incompatibilities, such as code
@@ -130,7 +130,7 @@ 
          Note
          
     file, for example after recompiling it, use the LOAD command or begin a
     fresh session.
    
          
-
              Optionally, a dynamically loaded file can contain initialization and
+
              Optionally, a dynamically loaded file can contain initialization and
     finalization functions.  If the file includes a function named
     _PG_init, that function will be called immediately after
     loading the file.  The function receives no parameters and should
@@ -146,7 +146,7 @@ 
          Note
          
 
          
 
          
 33.9.2. Base Types in C-Language Functions
          
-
               To know how to write C-language functions, you need to know how
+
               To know how to write C-language functions, you need to know how
      PostgreSQL internally represents base
      data types and how they can be passed to and from functions.
      Internally, PostgreSQL regards a base
@@ -461,7 +461,7 @@ 
          Warning
          
 
          
 
          
 
          
-33.9.3. Version 0 Calling Conventions
          
+33.9.3. Version 0 Calling Conventions
          
 
               We present the “old style” calling convention first — although
      this approach is now deprecated, it's easier to get a handle on
      initially.  In the version-0 method, the arguments and result
@@ -597,7 +597,7 @@ 
          Warning
          
 
          
 
          
 
          
-33.9.4. Version 1 Calling Conventions
          
+33.9.4. Version 1 Calling Conventions
               The version-1 calling convention relies on macros to suppress most
      of the complexity of passing arguments and results.  The C declaration
      of a version-1 function is always
@@ -778,7 +778,7 @@ 
          Warning
          
 
          
-33.9.5. Writing Code
          
+33.9.5. Writing Code
               Before we turn to the more advanced topics, we should discuss
      some coding rules for PostgreSQL
      C-language functions.  While it may be possible to load functions
@@ -796,7 +796,7 @@ 
          Warning
            
 
          •         Use pg_config
-        --includedir-server
+        --includedir-server
         to find out where the PostgreSQL server header
         files are installed on your system (or the system that your
         users will be running on).
@@ -812,7 +812,7 @@ 
            Warning
            
        
            • 
 
          •         When allocating memory, use the
         PostgreSQL functions
-        palloc and pfree
+        palloc and pfree
         instead of the corresponding C library functions
         malloc and free.
         The memory allocated by palloc will be
@@ -857,7 +857,7 @@ 
            Warning
            
   C, they must be compiled and linked in a special way to produce a
   file that can be dynamically loaded by the server.  To be precise, a
   shared library needs to be
-  created.
+  created.
 
  
            
 
              For information beyond what is contained in this section
@@ -874,7 +874,7 @@ 
            Warning
            
   executables: first the source files are compiled into object files,
   then the object files are linked together.  The object files need to
   be created as position-independent code
-  (PIC), which
+  (PIC), which
   conceptually means that they can be placed at an arbitrary location
   in memory when they are loaded by the executable.  (Object files
   intended for executables are usually not compiled that way.)  The
@@ -1071,7 +1071,7 @@ 
            Tip
            
 
            
 
            
 33.9.7. Extension Building Infrastructure
            
-
                If you are thinking about distributing your
+
                If you are thinking about distributing your
     PostgreSQL extension modules, setting up a
     portable build system for them can be fairly difficult.  Therefore
     the PostgreSQL installation provides a build
@@ -1207,7 +1207,7 @@ 
            Tip
            
 
            
 
            
 
            
-33.9.8. Composite-Type Arguments
            
+33.9.8. Composite-Type Arguments
               Composite types do not have a fixed layout like C structures.
      Instances of a composite type may contain null fields.  In
      addition, composite types that are part of an inheritance
@@ -1302,7 +1302,7 @@ 
          Tip
          
 
          
-33.9.9. Returning Rows (Composite Types)
          
+33.9.9. Returning Rows (Composite Types)
               To return a row or composite-type value from a C-language
      function, you can use a special API that provides macros and
      functions to hide most of the complexity of building composite
@@ -1725,7 +1725,7 @@ 
          Note
          
 
          
-33.9.11. Polymorphic Arguments and Return Types
          
+33.9.11. Polymorphic Arguments and Return Types
               C-language functions may be declared to accept and
      return the polymorphic types
      anyelement and anyarray.
@@ -1804,11 +1804,11 @@ 
          Note
          
 
          
-33.9.12. Shared Memory and LWLocks
          
+33.9.12. Shared Memory and LWLocks
               Add-ins may reserve LWLocks and an allocation of shared memory on server
      startup.  The add-in's shared library must be preloaded by specifying
      it in 
-     shared_preload_libraries.
+     shared_preload_libraries.
      Shared memory is reserved by calling:
 
          void RequestAddinShmemSpace(int size)
          
diff --git a/docs/en_US/pg/xfunc-internal.html b/docs/en_US/pg/xfunc-internal.html
index 590293b87f..a165db8d83 100644
--- a/docs/en_US/pg/xfunc-internal.html
+++ b/docs/en_US/pg/xfunc-internal.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.8. Internal Functions
          
-
              Internal functions are functions written in C that have been statically
+
              Internal functions are functions written in C that have been statically
     linked into the PostgreSQL server.
     The “body” of the function definition
     specifies the C-language name of the function, which need not be the
diff --git a/docs/en_US/pg/xfunc-overload.html b/docs/en_US/pg/xfunc-overload.html
index cf66d17c01..656fdd04d1 100644
--- a/docs/en_US/pg/xfunc-overload.html
+++ b/docs/en_US/pg/xfunc-overload.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.5. Function Overloading
          
-
              More than one function may be defined with the same SQL name, so long
+
              More than one function may be defined with the same SQL name, so long
     as the arguments they take are different.  In other words,
     function names can be overloaded.  When a
     query is executed, the server will determine which function to
diff --git a/docs/en_US/pg/xfunc-pl.html b/docs/en_US/pg/xfunc-pl.html
index f2d0566984..6eb0512f42 100644
--- a/docs/en_US/pg/xfunc-pl.html
+++ b/docs/en_US/pg/xfunc-pl.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/en_US/pg/xfunc-sql.html b/docs/en_US/pg/xfunc-sql.html
index e36ed4c647..43cd43426e 100644
--- a/docs/en_US/pg/xfunc-sql.html
+++ b/docs/en_US/pg/xfunc-sql.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.4. Query Language (SQL) Functions
          
-
              SQL functions execute an arbitrary list of SQL statements, returning
+
              SQL functions execute an arbitrary list of SQL statements, returning
     the result of the last query in the list.
     In the simple (non-set)
     case, the first row of the last query's result will be returned.
@@ -23,7 +23,7 @@
     If the last query happens
     to return no rows at all, the null value will be returned.
    
          
-
               Alternatively,
+
               Alternatively,
     an SQL function may be declared to return a set, by specifying the
     function's return type as SETOF
     sometype.  In this case all rows of the
@@ -170,7 +170,7 @@
 
          
 
          
 
          
-33.4.2. SQL Functions on Composite Types
          
+33.4.2. SQL Functions on Composite Types
          
 
               When writing  functions with arguments of composite
      types, we must  not  only  specify  which
      argument  we  want (as we did above with $1 and $2) but
@@ -346,8 +346,8 @@ 
          Tip
          
 
                The equivalence between functional notation and attribute notation
       makes it possible to use functions on composite types to emulate
       “computed fields”.
-      
-      
+      
+      
       For example, using the previous definition
       for double_salary(emp), we can write
 
@@ -382,7 +382,7 @@ 
          Tip
          
 
          
 
          
 33.4.3. Functions with Output Parameters
          
-
               An alternative way of describing a function's results is to define it
+
               An alternative way of describing a function's results is to define it
      with output parameters, as in this example:
 
 
          
@@ -487,7 +487,7 @@ 
          Tip
          
 
          
 
          
 
          
-33.4.5. SQL Functions Returning Sets
          
+33.4.5. SQL Functions Returning Sets
          
 
               When an SQL function is declared as returning SETOF
      sometype, the function's final
      SELECT query is executed to completion, and each row it
@@ -566,7 +566,7 @@ 
          Tip
          
 
 
          
 
          
-33.4.6. Polymorphic SQL Functions
          
+33.4.6. Polymorphic SQL Functions
          
 
               SQL functions may be declared to accept and
      return the polymorphic types anyelement and
      anyarray.  See Section 33.2.5, “Polymorphic Types” for a more detailed
diff --git a/docs/en_US/pg/xfunc-volatility.html b/docs/en_US/pg/xfunc-volatility.html
index 02e0883cfe..77d17ca958 100644
--- a/docs/en_US/pg/xfunc-volatility.html
+++ b/docs/en_US/pg/xfunc-volatility.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.6. Function Volatility Categories
          
-
              Every function has a volatility classification, with
+
              Every function has a volatility classification, with
     the possibilities being VOLATILE, STABLE, or
     IMMUTABLE.  VOLATILE is the default if the
     CREATE FUNCTION
diff --git a/docs/en_US/pg/xfunc.html b/docs/en_US/pg/xfunc.html
index 3e70b09d0b..f0354e97e5 100644
--- a/docs/en_US/pg/xfunc.html
+++ b/docs/en_US/pg/xfunc.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.3. User-Defined Functions
          
-
             PostgreSQL provides four kinds of
+
             PostgreSQL provides four kinds of
    functions:
 
    
          
diff --git a/docs/en_US/pg/xindex.html b/docs/en_US/pg/xindex.html
index c1f5a261fd..faa899062f 100644
--- a/docs/en_US/pg/xindex.html
+++ b/docs/en_US/pg/xindex.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.14. Interfacing Extensions To Indexes
          
-
             The procedures described thus far let you define new types, new
+
             The procedures described thus far let you define new types, new
    functions, and new operators. However, we cannot yet define an
    index on a column of a new data type.  To do this, we must define an
    operator class for the new data type.  Later in this
@@ -49,7 +49,7 @@ 
          Note
          
 
             The routines for an index method do not directly know anything
    about the data types that the index method will operate on.
    Instead, an operator
-   class
+   class
    identifies the set of operations that the index method needs to use
    to work with a particular data type.  Operator classes are so
    called because one thing they specify is the set of
@@ -655,7 +655,7 @@ 
          Note
          
 
          
 
          
 33.14.6. System Dependencies on Operator Classes
          
-
             PostgreSQL uses operator classes to infer the
+
             PostgreSQL uses operator classes to infer the
    properties of operators in more ways than just whether they can be used
    with indexes.  Therefore, you might want to create operator classes
    even if you have no intention of indexing any columns of your data type.
diff --git a/docs/en_US/pg/xoper-optimization.html b/docs/en_US/pg/xoper-optimization.html
index fe28747140..ef948ee476 100644
--- a/docs/en_US/pg/xoper-optimization.html
+++ b/docs/en_US/pg/xoper-optimization.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -27,11 +27,11 @@
    
          
 
              Additional optimization clauses might be added in future versions of
     PostgreSQL.  The ones described here are all
-    the ones that release 8.2.0 understands.
+    the ones that release 8.2.1 understands.
    
          
 
          
 
          
-33.13.1. COMMUTATOR
          
+33.13.1. COMMUTATOR
          
 
               The COMMUTATOR clause, if provided, names an operator that is the
      commutator of the operator being defined.  We say that operator A is the
      commutator of operator B if (x A y) equals (y B x) for all possible input
@@ -95,7 +95,7 @@
 
          
 
          
 
          
-33.13.2. NEGATOR
          
+33.13.2. NEGATOR
               The NEGATOR clause, if provided, names an operator that is the
      negator of the operator being defined.  We say that operator A
      is the negator of operator B if both return Boolean results and
@@ -123,7 +123,7 @@
 
 
          
 
          
-33.13.3. RESTRICT
          
+33.13.3. RESTRICT
              The RESTRICT clause, if provided, names a restriction selectivity
     estimation function for the operator.  (Note that this is a function
     name, not an operator name.)  RESTRICT clauses only make sense for
@@ -195,7 +195,7 @@
 
 
          
 
          
-33.13.4. JOIN
          
+33.13.4. JOIN
               The JOIN clause, if provided, names a join selectivity
      estimation function for the operator.  (Note that this is a function
      name, not an operator name.)  JOIN clauses only make sense for
@@ -238,7 +238,7 @@
 
 
          
 
          
-33.13.5. HASHES
          
+33.13.5. HASHES
               The HASHES clause, if present, tells the system that
      it is permissible to use the hash join method for a join based on this
      operator.  HASHES only makes sense for a binary operator that
@@ -297,7 +297,7 @@ 
          Note
          
 
          
-33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
          
+33.13.6. MERGES (SORT1, SORT2, LTCMP, GTCMP)
               The MERGES clause, if present, tells the system that
      it is permissible to use the merge-join method for a join based on this
      operator.  MERGES only makes sense for a binary operator that
diff --git a/docs/en_US/pg/xoper.html b/docs/en_US/pg/xoper.html
index c8bebe7812..a976113945 100644
--- a/docs/en_US/pg/xoper.html
+++ b/docs/en_US/pg/xoper.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.12. User-Defined Operators
          
-
             Every operator is “syntactic sugar” for a call to an
+
             Every operator is “syntactic sugar” for a call to an
    underlying function that does the real work; so you must
    first create the underlying function before you can create
    the operator.  However, an operator is not merely
@@ -25,7 +25,7 @@
   
          
 
             PostgreSQL supports left unary, right
    unary, and binary operators.  Operators can be
-   overloaded;
+   overloaded;
    that is, the same operator name can be used for different operators
    that have different numbers and types of operands.  When a query is
    executed, the system determines the operator to call from the
diff --git a/docs/en_US/pg/xplang.html b/docs/en_US/pg/xplang.html
index 413d62cebe..4172e66c7e 100644
--- a/docs/en_US/pg/xplang.html
+++ b/docs/en_US/pg/xplang.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -18,7 +18,7 @@
 
          Table of Contents
          
 
          36.1. Installing Procedural Languages
          
 
          
-
             PostgreSQL allows user-defined functions
+
             PostgreSQL allows user-defined functions
    to be written in other languages besides SQL and C.  These other
    languages are generically called procedural
    languages (PLs).  For a function
@@ -72,7 +72,7 @@
     does not know about.
    
          
-
               Manual Procedural Language Installation
+
               Manual Procedural Language Installation
     
          
 
               A procedural language is installed in a database in four steps,
      which must be carried out by a database superuser.  (For languages
diff --git a/docs/en_US/pg/xtypes.html b/docs/en_US/pg/xtypes.html
index 00294b3384..17f1ee5472 100644
--- a/docs/en_US/pg/xtypes.html
+++ b/docs/en_US/pg/xtypes.html
@@ -5,7 +5,7 @@
 
 
 
-
+
 
 
 
@@ -14,7 +14,7 @@
 
          
 
          
 33.11. User-Defined Types
          
-
             As described in Section 33.2, “The PostgreSQL Type System”,
+
             As described in Section 33.2, “The PostgreSQL Type System”,
    PostgreSQL can be extended to support new
    data types.  This section describes how to define new base types,
    which are data types defined below the level of the SQL
@@ -27,10 +27,10 @@
    See the README file in that directory for instructions
    about running the examples.
   
          
-
            
-  
+
            
+  
   A user-defined type must always have input and output
-  functions.
+  functions.
   These functions determine how the type appears in strings (for input
   by the user and output to the user) and how the type is organized in
   memory.  The input function takes a null-terminated character string
@@ -197,7 +197,7 @@
 
            When you define a new base type,
   PostgreSQL automatically provides support
   for arrays of that
-  type. For historical reasons, the array type
+  type. For historical reasons, the array type
   has the same name as the base type with the underscore character
   (_) prepended.
  
          
@@ -207,7 +207,7 @@
   created to support indexing of the data type.  These additional
   layers are discussed in following sections.
  
          
-
             
+
             
   If the values of your data type might exceed a few hundred bytes in
   size (in internal form), you should make the data type
   TOAST-able (see Section 52.2, “TOAST”).
diff --git a/docs/en_US/pgadmin3.hhc b/docs/en_US/pgadmin3.hhc
index 09627b107f..969cbf3278 100644
--- a/docs/en_US/pgadmin3.hhc
+++ b/docs/en_US/pgadmin3.hhc
@@ -216,7 +216,7 @@
 		
 	
 	
        •  
-		
+		
 		
 		
 	
            
@@ -244,7 +244,7 @@
 					
 				
          •  
 					
-					
+					
 					
 			
          
 			
        •  
@@ -262,15 +262,15 @@
 			
            
 				
          •  
 					
-					
+					
 					
 				
          •  
 					
-					
+					
 					
 				
          •  
 					
-					
+					
 					
 			
          
 		
@@ -412,7 +412,7 @@
 							          
 						
        •  
 							
-							
+							
 							
 						
        •  
 							
@@ -425,7 +425,7 @@
 						
 					
        •  
 						
-						
+						
 						
 					
        •  
 						
@@ -443,27 +443,27 @@
 				
            
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
-						
+						
 						
 					
          •  
 						
@@ -511,19 +511,19 @@
 				
              
 					
            •  
 						
-						
+						
 						
 					
            •  
 						
-						
+						
 						
 					
            •  
 						
-						
+						
 						
 					
            •  
 						
-						
+						
 						
 					
            •  
 						
@@ -541,35 +541,35 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -804,23 +804,23 @@
 					
                
 						
              •  
 							
-							
+							
 							
 						
              •  
 							
-							
+							
 							
 						
              •  
 							
-							
+							
 							
 						
              •  
 							
-							
+							
 							
 						
              •  
 							
-							
+							
 							
 					
              
 					
            •  
@@ -847,27 +847,27 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -903,27 +903,27 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -933,23 +933,23 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -1091,19 +1091,19 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -1121,27 +1121,27 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
              
 				
            •  
@@ -1151,19 +1151,19 @@
 				
                
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
@@ -1405,11 +1405,11 @@
 				
                  
 					
                •  
 						
-						
+						
 						
 					
                •  
 						
-						
+						
 						
 				
                
 				
              •  
@@ -1459,11 +1459,11 @@
 						
 					
              •  
 						
-						
+						
 						
 					
              •  
 						
-						
+						
 						
 				
 				
              •  
@@ -1754,11 +1754,11 @@
 					
                  
 						
                •  
 							
-							
+							
 							
 						
                •  
 							
-							
+							
 							
 						
                •  
 							
@@ -1791,15 +1791,15 @@
 				
                    
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 				
                  
 				
                •  
@@ -1813,15 +1813,15 @@
 						
 					
                •  
 						
-						
+						
 						
 					
                •  
 						
-						
+						
 						
 					
                •  
 						
-						
+						
 						
 				
 			
@@ -1988,7 +1988,7 @@
 					
                  • 
 				
                    
 					
                  •  
-						
+						
 						
 						
 					
                  •  
@@ -2057,31 +2057,31 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2233,43 +2233,43 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2313,23 +2313,23 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2343,31 +2343,31 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2377,15 +2377,15 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2399,15 +2399,15 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2417,15 +2417,15 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2657,19 +2657,19 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
@@ -2691,7 +2691,7 @@
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
@@ -2703,11 +2703,11 @@
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2741,15 +2741,15 @@
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
@@ -2761,11 +2761,11 @@
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
@@ -2773,11 +2773,11 @@
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 				
 				
                  •  
@@ -2799,27 +2799,27 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 					
                    •  
 						
-						
+						
 						
 				
                    
 				
                  •  
@@ -2899,11 +2899,11 @@
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
-						
+						
 						
 					
                  •  
 						
@@ -2917,12 +2917,12 @@
 				
                      
 					
                    •  
 						
-						
+						
 						
 					
                        
 						
                      •  
 							
-							
+							
 							
 					
                      
 					
                    •  
@@ -3058,11 +3058,11 @@
 					
                        
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 					
                      
 					
                    •  
@@ -3072,23 +3072,23 @@
 					
                        
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 					
                      
 					
                    •  
@@ -3098,23 +3098,23 @@
 					
                        
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 					
                      
 					
                    •  
@@ -3142,15 +3142,15 @@
 					
                        
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 					
                      
 					
                    •  
@@ -3160,15 +3160,15 @@
 					
                        
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
-							
+							
 							
 					
                      
 				
@@ -3187,7 +3187,7 @@
 				
                        
 					
                      •  
 						
-						
+						
 						
 					
                      •  
 						
@@ -3200,7 +3200,7 @@
 							
 						
                      •  
 							
-							
+							
 							
 						
                      •  
 							
@@ -4061,11 +4061,11 @@
 				
                          
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 				
                        
 				
                      •  
@@ -4079,7 +4079,7 @@
 				
                          
 					
                        •  
 						
-						
+						
 						
 				
                        
 				
                      •  
@@ -4327,11 +4327,11 @@
 				
                          
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
@@ -4339,7 +4339,7 @@
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
@@ -4351,15 +4351,15 @@
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 				
                        
 				
                      •  
@@ -4409,19 +4409,19 @@
 				
                          
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 					
                        •  
 						
-						
+						
 						
 				
                        
 				
                      •  
@@ -4624,7 +4624,7 @@
 			
                          
 				
                        •  
 					
-					
+					
 					
 				
                        •  
 					
@@ -4662,94 +4662,122 @@
 				
 				
 			
                            
+				
                          •  
+					
+					
+					
+				
                              
+					
                            •  
+						
+						
+						
+					
                            •  
+						
+						
+						
+				
                            
 				
                          •  
 					
-					
+					
 					
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
+				
                          •  
+					
+					
+					
+				
                              
+					
                            •  
+						
+						
+						
+					
                            •  
+						
+						
+						
+				
                            
 				
                          •  
 					
 					
@@ -4757,11 +4785,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4771,11 +4799,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4785,11 +4813,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4799,11 +4827,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4813,11 +4841,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4827,79 +4855,93 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
+				
                          •  
+					
+					
+					
+				
                              
+					
                            •  
+						
+						
+						
+					
                            •  
+						
+						
+						
+				
                            
 				
                          •  
 					
 					
@@ -4907,11 +4949,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4921,11 +4963,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4935,11 +4977,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4949,11 +4991,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4963,11 +5005,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4977,11 +5019,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -4991,11 +5033,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5005,11 +5047,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5019,11 +5061,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5033,71 +5075,85 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
+				
                          •  
+					
+					
+					
+				
                              
+					
                            •  
+						
+						
+						
+					
                            •  
+						
+						
+						
+				
                            
 				
                          •  
 					
 					
@@ -5105,11 +5161,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5119,11 +5175,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5133,11 +5189,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5147,11 +5203,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5161,11 +5217,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5175,11 +5231,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5189,11 +5245,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5203,11 +5259,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5217,11 +5273,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5231,11 +5287,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5245,11 +5301,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5259,11 +5315,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5273,11 +5329,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5287,11 +5343,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5301,79 +5357,93 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
+				
                          •  
+					
+					
+					
+				
                              
+					
                            •  
+						
+						
+						
+					
                            •  
+						
+						
+						
+				
                            
 				
                          •  
 					
 					
@@ -5381,11 +5451,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5395,11 +5465,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5409,11 +5479,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5423,11 +5493,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5437,11 +5507,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5451,11 +5521,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5465,11 +5535,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5479,11 +5549,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5493,11 +5563,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5507,11 +5577,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5521,11 +5591,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5535,11 +5605,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5549,11 +5619,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5563,11 +5633,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5577,11 +5647,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5591,11 +5661,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5605,80 +5675,80 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
@@ -5689,11 +5759,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5703,11 +5773,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5717,11 +5787,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5731,11 +5801,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5745,11 +5815,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5759,11 +5829,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5773,11 +5843,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5787,11 +5857,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5801,108 +5871,108 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 				
                            
@@ -5913,11 +5983,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5927,11 +5997,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5941,11 +6011,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5955,11 +6025,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5969,11 +6039,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5983,11 +6053,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -5997,11 +6067,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6011,11 +6081,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6025,11 +6095,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6039,11 +6109,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6053,11 +6123,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6067,17 +6137,17 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 					
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6087,11 +6157,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6101,11 +6171,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6115,11 +6185,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6129,7 +6199,7 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6139,7 +6209,7 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6149,11 +6219,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6163,11 +6233,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6177,15 +6247,15 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6195,11 +6265,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6209,11 +6279,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6223,15 +6293,15 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6245,15 +6315,15 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6263,11 +6333,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6277,7 +6347,7 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6287,7 +6357,7 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6297,7 +6367,7 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 				
                            
 				
                          •  
@@ -6325,11 +6395,11 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 				
                            
 			
@@ -6349,36 +6419,36 @@
 				
                              
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                            •  
 						
-						
+						
 						
 					
                                
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 						
                              •  
 							
-							
+							
 							
 					
                              
 					
                            •  
@@ -6393,27 +6463,27 @@
 				
                                
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 				
                              
 				
                            •  
@@ -6423,11 +6493,11 @@
 				
                                
 					
                              •  
 						
-						
+						
 						
 					
                              •  
 						
-						
+						
 						
 				
                              
 				
                            •  
@@ -6437,7 +6507,7 @@
 				
                                
 					
                              •  
 						
-						
+						
 						
 				
                              
 			
@@ -6467,15 +6537,15 @@
 		
                                
 			
                              •  
 				
-				
+				
 				
 			
                              •  
 				
-				
+				
 				
 			
                              •  
 				
-				
+				
 				
 		
                              
 	
diff --git a/docs/en_US/pgadmin3.hhk b/docs/en_US/pgadmin3.hhk
index ca395245a5..cc8d2a859a 100644
--- a/docs/en_US/pgadmin3.hhk
+++ b/docs/en_US/pgadmin3.hhk
@@ -8,2015 +8,2015 @@
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
@@ -2040,933 +2040,933 @@
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
@@ -2975,1567 +2975,1567 @@
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 		
                                  
 			
                                •  
 				
 				
-				
+				
 				
 		
                                
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
@@ -4544,3532 +4544,3532 @@
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 		
                                  
 			
                                •  
 				
 				
-				
+				
 				
 		
                                
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 		
                                  
 			
                                •  
 				
 				
-				
+				
 				
 		
                                
 	
                              
@@ -8080,2778 +8080,2778 @@
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 		
                                  
 			
                                •  
 				
 				
-				
+				
 				
 		
                                
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                                
 		
                              •  
 			
 			
-			
+			
 			
 	
                              
 	
                            •  
 		
 		
-		
+		
 		
 	
                            •  
 		
diff --git a/docs/en_US/pgadmin3.hhp b/docs/en_US/pgadmin3.hhp
index ab858accb2..03cd6f1a5b 100644
--- a/docs/en_US/pgadmin3.hhp
+++ b/docs/en_US/pgadmin3.hhp
@@ -648,12 +648,15 @@ pg/sql-keywords-appendix.html
 pg/features.html
 pg/unsupported-features-sql-standard.html
 pg/release.html
+pg/release-8-2.html
+pg/release-8-1-6.html
 pg/release-8-1-5.html
 pg/release-8-1-4.html
 pg/release-8-1-3.html
 pg/release-8-1-2.html
 pg/release-8-1-1.html
 pg/release-8-1.html
+pg/release-8-0-10.html
 pg/release-8-0-9.html
 pg/release-8-0-8.html
 pg/release-8-0-7.html
@@ -664,6 +667,7 @@ pg/release-8-0-3.html
 pg/release-8-0-2.html
 pg/release-8-0-1.html
 pg/release-8-0.html
+pg/release-7-4-15.html
 pg/release-7-4-14.html
 pg/release-7-4-13.html
 pg/release-7-4-12.html
@@ -679,6 +683,7 @@ pg/release-7-4-3.html
 pg/release-7-4-2.html
 pg/release-7-4-1.html
 pg/release-7-4.html
+pg/release-7-3-17.html
 pg/release-7-3-16.html
 pg/release-7-3-15.html
 pg/release-7-3-14.html

          •