kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/postgresql92-docs/PLIST

1460 lines
62 KiB
Text
Raw Normal View History

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is now end-of-life. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime.
2016-10-29 21:41:53 +02:00
@comment $NetBSD: PLIST,v 1.19 2016/10/29 19:41:54 adam Exp $
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
man/man1/clusterdb.1
man/man1/createdb.1
man/man1/createlang.1
man/man1/createuser.1
man/man1/dropdb.1
man/man1/droplang.1
man/man1/dropuser.1
man/man1/ecpg.1
man/man1/initdb.1
man/man1/oid2name.1
man/man1/pg_archivecleanup.1
man/man1/pg_basebackup.1
man/man1/pg_config.1
man/man1/pg_controldata.1
man/man1/pg_ctl.1
man/man1/pg_dump.1
man/man1/pg_dumpall.1
man/man1/pg_receivexlog.1
man/man1/pg_resetxlog.1
man/man1/pg_restore.1
man/man1/pg_standby.1
man/man1/pg_test_fsync.1
man/man1/pg_test_timing.1
man/man1/pg_upgrade.1
man/man1/pgbench.1
man/man1/postgres.1
man/man1/postmaster.1
man/man1/psql.1
man/man1/reindexdb.1
man/man1/vacuumdb.1
man/man1/vacuumlo.1
man/man3/SPI_connect.3
man/man3/SPI_copytuple.3
man/man3/SPI_cursor_close.3
man/man3/SPI_cursor_fetch.3
man/man3/SPI_cursor_find.3
man/man3/SPI_cursor_move.3
man/man3/SPI_cursor_open.3
man/man3/SPI_cursor_open_with_args.3
man/man3/SPI_cursor_open_with_paramlist.3
man/man3/SPI_exec.3
man/man3/SPI_execp.3
man/man3/SPI_execute.3
man/man3/SPI_execute_plan.3
man/man3/SPI_execute_plan_with_paramlist.3
man/man3/SPI_execute_with_args.3
man/man3/SPI_finish.3
man/man3/SPI_fname.3
man/man3/SPI_fnumber.3
man/man3/SPI_freeplan.3
man/man3/SPI_freetuple.3
man/man3/SPI_freetuptable.3
man/man3/SPI_getargcount.3
man/man3/SPI_getargtypeid.3
man/man3/SPI_getbinval.3
man/man3/SPI_getnspname.3
man/man3/SPI_getrelname.3
man/man3/SPI_gettype.3
man/man3/SPI_gettypeid.3
man/man3/SPI_getvalue.3
man/man3/SPI_is_cursor_plan.3
man/man3/SPI_keepplan.3
man/man3/SPI_modifytuple.3
man/man3/SPI_palloc.3
man/man3/SPI_pfree.3
man/man3/SPI_pop.3
man/man3/SPI_prepare.3
man/man3/SPI_prepare_cursor.3
man/man3/SPI_prepare_params.3
man/man3/SPI_push.3
man/man3/SPI_repalloc.3
man/man3/SPI_returntuple.3
man/man3/SPI_saveplan.3
man/man3/SPI_scroll_cursor_fetch.3
man/man3/SPI_scroll_cursor_move.3
man/man3/dblink.3
man/man3/dblink_build_sql_delete.3
man/man3/dblink_build_sql_insert.3
man/man3/dblink_build_sql_update.3
man/man3/dblink_cancel_query.3
man/man3/dblink_close.3
man/man3/dblink_connect.3
man/man3/dblink_connect_u.3
man/man3/dblink_disconnect.3
man/man3/dblink_error_message.3
man/man3/dblink_exec.3
man/man3/dblink_fetch.3
man/man3/dblink_get_connections.3
man/man3/dblink_get_notify.3
man/man3/dblink_get_pkey.3
man/man3/dblink_get_result.3
man/man3/dblink_is_busy.3
man/man3/dblink_open.3
man/man3/dblink_send_query.3
man/man7/ABORT.7
man/man7/ALTER_AGGREGATE.7
man/man7/ALTER_COLLATION.7
man/man7/ALTER_CONVERSION.7
man/man7/ALTER_DATABASE.7
man/man7/ALTER_DEFAULT_PRIVILEGES.7
man/man7/ALTER_DOMAIN.7
man/man7/ALTER_EXTENSION.7
man/man7/ALTER_FOREIGN_DATA_WRAPPER.7
man/man7/ALTER_FOREIGN_TABLE.7
man/man7/ALTER_FUNCTION.7
man/man7/ALTER_GROUP.7
man/man7/ALTER_INDEX.7
man/man7/ALTER_LANGUAGE.7
man/man7/ALTER_LARGE_OBJECT.7
man/man7/ALTER_OPERATOR.7
man/man7/ALTER_OPERATOR_CLASS.7
man/man7/ALTER_OPERATOR_FAMILY.7
man/man7/ALTER_ROLE.7
man/man7/ALTER_SCHEMA.7
man/man7/ALTER_SEQUENCE.7
man/man7/ALTER_SERVER.7
man/man7/ALTER_TABLE.7
man/man7/ALTER_TABLESPACE.7
man/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7
man/man7/ALTER_TEXT_SEARCH_DICTIONARY.7
man/man7/ALTER_TEXT_SEARCH_PARSER.7
man/man7/ALTER_TEXT_SEARCH_TEMPLATE.7
man/man7/ALTER_TRIGGER.7
man/man7/ALTER_TYPE.7
man/man7/ALTER_USER.7
man/man7/ALTER_USER_MAPPING.7
man/man7/ALTER_VIEW.7
man/man7/ANALYZE.7
man/man7/BEGIN.7
man/man7/CHECKPOINT.7
man/man7/CLOSE.7
man/man7/CLUSTER.7
man/man7/COMMENT.7
man/man7/COMMIT.7
man/man7/COMMIT_PREPARED.7
man/man7/COPY.7
man/man7/CREATE_AGGREGATE.7
man/man7/CREATE_CAST.7
man/man7/CREATE_COLLATION.7
man/man7/CREATE_CONVERSION.7
man/man7/CREATE_DATABASE.7
man/man7/CREATE_DOMAIN.7
man/man7/CREATE_EXTENSION.7
man/man7/CREATE_FOREIGN_DATA_WRAPPER.7
man/man7/CREATE_FOREIGN_TABLE.7
man/man7/CREATE_FUNCTION.7
man/man7/CREATE_GROUP.7
man/man7/CREATE_INDEX.7
man/man7/CREATE_LANGUAGE.7
man/man7/CREATE_OPERATOR.7
man/man7/CREATE_OPERATOR_CLASS.7
man/man7/CREATE_OPERATOR_FAMILY.7
man/man7/CREATE_ROLE.7
man/man7/CREATE_RULE.7
man/man7/CREATE_SCHEMA.7
man/man7/CREATE_SEQUENCE.7
man/man7/CREATE_SERVER.7
man/man7/CREATE_TABLE.7
man/man7/CREATE_TABLESPACE.7
man/man7/CREATE_TABLE_AS.7
man/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7
man/man7/CREATE_TEXT_SEARCH_DICTIONARY.7
man/man7/CREATE_TEXT_SEARCH_PARSER.7
man/man7/CREATE_TEXT_SEARCH_TEMPLATE.7
man/man7/CREATE_TRIGGER.7
man/man7/CREATE_TYPE.7
man/man7/CREATE_USER.7
man/man7/CREATE_USER_MAPPING.7
man/man7/CREATE_VIEW.7
man/man7/DEALLOCATE.7
man/man7/DECLARE.7
man/man7/DELETE.7
man/man7/DISCARD.7
man/man7/DO.7
man/man7/DROP_AGGREGATE.7
man/man7/DROP_CAST.7
man/man7/DROP_COLLATION.7
man/man7/DROP_CONVERSION.7
man/man7/DROP_DATABASE.7
man/man7/DROP_DOMAIN.7
man/man7/DROP_EXTENSION.7
man/man7/DROP_FOREIGN_DATA_WRAPPER.7
man/man7/DROP_FOREIGN_TABLE.7
man/man7/DROP_FUNCTION.7
man/man7/DROP_GROUP.7
man/man7/DROP_INDEX.7
man/man7/DROP_LANGUAGE.7
man/man7/DROP_OPERATOR.7
man/man7/DROP_OPERATOR_CLASS.7
man/man7/DROP_OPERATOR_FAMILY.7
man/man7/DROP_OWNED.7
man/man7/DROP_ROLE.7
man/man7/DROP_RULE.7
man/man7/DROP_SCHEMA.7
man/man7/DROP_SEQUENCE.7
man/man7/DROP_SERVER.7
man/man7/DROP_TABLE.7
man/man7/DROP_TABLESPACE.7
man/man7/DROP_TEXT_SEARCH_CONFIGURATION.7
man/man7/DROP_TEXT_SEARCH_DICTIONARY.7
man/man7/DROP_TEXT_SEARCH_PARSER.7
man/man7/DROP_TEXT_SEARCH_TEMPLATE.7
man/man7/DROP_TRIGGER.7
man/man7/DROP_TYPE.7
man/man7/DROP_USER.7
man/man7/DROP_USER_MAPPING.7
man/man7/DROP_VIEW.7
man/man7/END.7
man/man7/EXECUTE.7
man/man7/EXPLAIN.7
man/man7/FETCH.7
man/man7/GRANT.7
man/man7/INSERT.7
man/man7/LISTEN.7
man/man7/LOAD.7
man/man7/LOCK.7
man/man7/MOVE.7
man/man7/NOTIFY.7
man/man7/PREPARE.7
man/man7/PREPARE_TRANSACTION.7
man/man7/REASSIGN_OWNED.7
man/man7/REINDEX.7
man/man7/RELEASE_SAVEPOINT.7
man/man7/RESET.7
man/man7/REVOKE.7
man/man7/ROLLBACK.7
man/man7/ROLLBACK_PREPARED.7
man/man7/ROLLBACK_TO_SAVEPOINT.7
man/man7/SAVEPOINT.7
man/man7/SECURITY_LABEL.7
man/man7/SELECT.7
man/man7/SELECT_INTO.7
man/man7/SET.7
man/man7/SET_CONSTRAINTS.7
man/man7/SET_ROLE.7
man/man7/SET_SESSION_AUTHORIZATION.7
man/man7/SET_TRANSACTION.7
man/man7/SHOW.7
man/man7/START_TRANSACTION.7
man/man7/TABLE.7
man/man7/TRUNCATE.7
man/man7/UNLISTEN.7
man/man7/UPDATE.7
man/man7/VACUUM.7
man/man7/VALUES.7
man/man7/WITH.7
share/doc/postgresql/html/LEGALNOTICE.html
share/doc/postgresql/html/acronyms.html
share/doc/postgresql/html/admin.html
share/doc/postgresql/html/adminpack.html
share/doc/postgresql/html/app-clusterdb.html
share/doc/postgresql/html/app-createdb.html
share/doc/postgresql/html/app-createlang.html
share/doc/postgresql/html/app-createuser.html
share/doc/postgresql/html/app-dropdb.html
share/doc/postgresql/html/app-droplang.html
share/doc/postgresql/html/app-dropuser.html
share/doc/postgresql/html/app-ecpg.html
share/doc/postgresql/html/app-initdb.html
share/doc/postgresql/html/app-pg-ctl.html
share/doc/postgresql/html/app-pg-dumpall.html
share/doc/postgresql/html/app-pgbasebackup.html
share/doc/postgresql/html/app-pgconfig.html
share/doc/postgresql/html/app-pgcontroldata.html
share/doc/postgresql/html/app-pgdump.html
share/doc/postgresql/html/app-pgreceivexlog.html
share/doc/postgresql/html/app-pgresetxlog.html
share/doc/postgresql/html/app-pgrestore.html
share/doc/postgresql/html/app-postgres.html
share/doc/postgresql/html/app-postmaster.html
share/doc/postgresql/html/app-psql.html
share/doc/postgresql/html/app-reindexdb.html
share/doc/postgresql/html/app-vacuumdb.html
share/doc/postgresql/html/appendixes.html
share/doc/postgresql/html/applevel-consistency.html
share/doc/postgresql/html/archive-recovery-settings.html
share/doc/postgresql/html/arrays.html
share/doc/postgresql/html/auth-delay.html
share/doc/postgresql/html/auth-methods.html
share/doc/postgresql/html/auth-pg-hba-conf.html
share/doc/postgresql/html/auth-username-maps.html
share/doc/postgresql/html/auto-explain.html
share/doc/postgresql/html/backup-dump.html
share/doc/postgresql/html/backup-file.html
share/doc/postgresql/html/backup.html
share/doc/postgresql/html/biblio.html
share/doc/postgresql/html/bki-commands.html
share/doc/postgresql/html/bki-example.html
share/doc/postgresql/html/bki-format.html
share/doc/postgresql/html/bki-structure.html
share/doc/postgresql/html/bki.html
share/doc/postgresql/html/bookindex.html
share/doc/postgresql/html/btree-gin.html
share/doc/postgresql/html/btree-gist.html
share/doc/postgresql/html/bug-reporting.html
share/doc/postgresql/html/catalog-pg-aggregate.html
share/doc/postgresql/html/catalog-pg-am.html
share/doc/postgresql/html/catalog-pg-amop.html
share/doc/postgresql/html/catalog-pg-amproc.html
share/doc/postgresql/html/catalog-pg-attrdef.html
share/doc/postgresql/html/catalog-pg-attribute.html
share/doc/postgresql/html/catalog-pg-auth-members.html
share/doc/postgresql/html/catalog-pg-authid.html
share/doc/postgresql/html/catalog-pg-cast.html
share/doc/postgresql/html/catalog-pg-class.html
share/doc/postgresql/html/catalog-pg-collation.html
share/doc/postgresql/html/catalog-pg-constraint.html
share/doc/postgresql/html/catalog-pg-conversion.html
share/doc/postgresql/html/catalog-pg-database.html
share/doc/postgresql/html/catalog-pg-db-role-setting.html
share/doc/postgresql/html/catalog-pg-default-acl.html
share/doc/postgresql/html/catalog-pg-depend.html
share/doc/postgresql/html/catalog-pg-description.html
share/doc/postgresql/html/catalog-pg-enum.html
share/doc/postgresql/html/catalog-pg-extension.html
share/doc/postgresql/html/catalog-pg-foreign-data-wrapper.html
share/doc/postgresql/html/catalog-pg-foreign-server.html
share/doc/postgresql/html/catalog-pg-foreign-table.html
share/doc/postgresql/html/catalog-pg-index.html
share/doc/postgresql/html/catalog-pg-inherits.html
share/doc/postgresql/html/catalog-pg-language.html
share/doc/postgresql/html/catalog-pg-largeobject-metadata.html
share/doc/postgresql/html/catalog-pg-largeobject.html
share/doc/postgresql/html/catalog-pg-namespace.html
share/doc/postgresql/html/catalog-pg-opclass.html
share/doc/postgresql/html/catalog-pg-operator.html
share/doc/postgresql/html/catalog-pg-opfamily.html
share/doc/postgresql/html/catalog-pg-pltemplate.html
share/doc/postgresql/html/catalog-pg-proc.html
share/doc/postgresql/html/catalog-pg-range.html
share/doc/postgresql/html/catalog-pg-rewrite.html
share/doc/postgresql/html/catalog-pg-seclabel.html
share/doc/postgresql/html/catalog-pg-shdepend.html
share/doc/postgresql/html/catalog-pg-shdescription.html
share/doc/postgresql/html/catalog-pg-shseclabel.html
share/doc/postgresql/html/catalog-pg-statistic.html
share/doc/postgresql/html/catalog-pg-tablespace.html
share/doc/postgresql/html/catalog-pg-trigger.html
share/doc/postgresql/html/catalog-pg-ts-config-map.html
share/doc/postgresql/html/catalog-pg-ts-config.html
share/doc/postgresql/html/catalog-pg-ts-dict.html
share/doc/postgresql/html/catalog-pg-ts-parser.html
share/doc/postgresql/html/catalog-pg-ts-template.html
share/doc/postgresql/html/catalog-pg-type.html
share/doc/postgresql/html/catalog-pg-user-mapping.html
share/doc/postgresql/html/catalogs-overview.html
share/doc/postgresql/html/catalogs.html
share/doc/postgresql/html/charset.html
share/doc/postgresql/html/chkpass.html
share/doc/postgresql/html/citext.html
share/doc/postgresql/html/client-authentication-problems.html
share/doc/postgresql/html/client-authentication.html
share/doc/postgresql/html/client-interfaces.html
share/doc/postgresql/html/collation.html
share/doc/postgresql/html/config-setting.html
share/doc/postgresql/html/connect-estab.html
share/doc/postgresql/html/continuous-archiving.html
share/doc/postgresql/html/contrib-dblink-build-sql-delete.html
share/doc/postgresql/html/contrib-dblink-build-sql-insert.html
share/doc/postgresql/html/contrib-dblink-build-sql-update.html
share/doc/postgresql/html/contrib-dblink-cancel-query.html
share/doc/postgresql/html/contrib-dblink-close.html
share/doc/postgresql/html/contrib-dblink-connect-u.html
share/doc/postgresql/html/contrib-dblink-connect.html
share/doc/postgresql/html/contrib-dblink-disconnect.html
share/doc/postgresql/html/contrib-dblink-error-message.html
share/doc/postgresql/html/contrib-dblink-exec.html
share/doc/postgresql/html/contrib-dblink-fetch.html
share/doc/postgresql/html/contrib-dblink-function.html
share/doc/postgresql/html/contrib-dblink-get-connections.html
share/doc/postgresql/html/contrib-dblink-get-notify.html
share/doc/postgresql/html/contrib-dblink-get-pkey.html
share/doc/postgresql/html/contrib-dblink-get-result.html
share/doc/postgresql/html/contrib-dblink-is-busy.html
share/doc/postgresql/html/contrib-dblink-open.html
share/doc/postgresql/html/contrib-dblink-send-query.html
share/doc/postgresql/html/contrib-prog-client.html
share/doc/postgresql/html/contrib-prog-server.html
share/doc/postgresql/html/contrib-prog.html
share/doc/postgresql/html/contrib-spi.html
share/doc/postgresql/html/contrib.html
share/doc/postgresql/html/creating-cluster.html
share/doc/postgresql/html/cube.html
share/doc/postgresql/html/database-roles.html
share/doc/postgresql/html/datatype-binary.html
share/doc/postgresql/html/datatype-bit.html
share/doc/postgresql/html/datatype-boolean.html
share/doc/postgresql/html/datatype-character.html
share/doc/postgresql/html/datatype-datetime.html
share/doc/postgresql/html/datatype-enum.html
share/doc/postgresql/html/datatype-geometric.html
share/doc/postgresql/html/datatype-json.html
share/doc/postgresql/html/datatype-money.html
share/doc/postgresql/html/datatype-net-types.html
share/doc/postgresql/html/datatype-numeric.html
share/doc/postgresql/html/datatype-oid.html
share/doc/postgresql/html/datatype-pseudo.html
share/doc/postgresql/html/datatype-textsearch.html
share/doc/postgresql/html/datatype-uuid.html
share/doc/postgresql/html/datatype-xml.html
share/doc/postgresql/html/datatype.html
share/doc/postgresql/html/datetime-appendix.html
share/doc/postgresql/html/datetime-config-files.html
share/doc/postgresql/html/datetime-input-rules.html
share/doc/postgresql/html/datetime-keywords.html
share/doc/postgresql/html/datetime-units-history.html
share/doc/postgresql/html/dblink.html
share/doc/postgresql/html/ddl-alter.html
share/doc/postgresql/html/ddl-basics.html
share/doc/postgresql/html/ddl-constraints.html
share/doc/postgresql/html/ddl-default.html
share/doc/postgresql/html/ddl-depend.html
share/doc/postgresql/html/ddl-foreign-data.html
share/doc/postgresql/html/ddl-inherit.html
share/doc/postgresql/html/ddl-others.html
share/doc/postgresql/html/ddl-partitioning.html
share/doc/postgresql/html/ddl-priv.html
share/doc/postgresql/html/ddl-schemas.html
share/doc/postgresql/html/ddl-system-columns.html
share/doc/postgresql/html/ddl.html
share/doc/postgresql/html/dict-int.html
share/doc/postgresql/html/dict-xsyn.html
share/doc/postgresql/html/different-replication-solutions.html
share/doc/postgresql/html/disk-full.html
share/doc/postgresql/html/disk-usage.html
share/doc/postgresql/html/diskusage.html
share/doc/postgresql/html/dml-delete.html
share/doc/postgresql/html/dml-insert.html
share/doc/postgresql/html/dml-update.html
share/doc/postgresql/html/dml.html
share/doc/postgresql/html/docguide-authoring.html
share/doc/postgresql/html/docguide-build.html
share/doc/postgresql/html/docguide-docbook.html
share/doc/postgresql/html/docguide-style.html
share/doc/postgresql/html/docguide-toolsets.html
share/doc/postgresql/html/docguide.html
share/doc/postgresql/html/dummy-seclabel.html
share/doc/postgresql/html/dynamic-trace.html
share/doc/postgresql/html/earthdistance.html
share/doc/postgresql/html/ecpg-commands.html
share/doc/postgresql/html/ecpg-concept.html
share/doc/postgresql/html/ecpg-connect.html
share/doc/postgresql/html/ecpg-cpp.html
share/doc/postgresql/html/ecpg-descriptors.html
share/doc/postgresql/html/ecpg-develop.html
share/doc/postgresql/html/ecpg-dynamic.html
share/doc/postgresql/html/ecpg-errors.html
share/doc/postgresql/html/ecpg-informix-compat.html
share/doc/postgresql/html/ecpg-library.html
share/doc/postgresql/html/ecpg-lo.html
share/doc/postgresql/html/ecpg-pgtypes.html
share/doc/postgresql/html/ecpg-preproc.html
share/doc/postgresql/html/ecpg-process.html
share/doc/postgresql/html/ecpg-sql-allocate-descriptor.html
share/doc/postgresql/html/ecpg-sql-commands.html
share/doc/postgresql/html/ecpg-sql-connect.html
share/doc/postgresql/html/ecpg-sql-deallocate-descriptor.html
share/doc/postgresql/html/ecpg-sql-declare.html
share/doc/postgresql/html/ecpg-sql-describe.html
share/doc/postgresql/html/ecpg-sql-disconnect.html
share/doc/postgresql/html/ecpg-sql-execute-immediate.html
share/doc/postgresql/html/ecpg-sql-get-descriptor.html
share/doc/postgresql/html/ecpg-sql-open.html
share/doc/postgresql/html/ecpg-sql-prepare.html
share/doc/postgresql/html/ecpg-sql-set-autocommit.html
share/doc/postgresql/html/ecpg-sql-set-connection.html
share/doc/postgresql/html/ecpg-sql-set-descriptor.html
share/doc/postgresql/html/ecpg-sql-type.html
share/doc/postgresql/html/ecpg-sql-var.html
share/doc/postgresql/html/ecpg-sql-whenever.html
share/doc/postgresql/html/ecpg-variables.html
share/doc/postgresql/html/ecpg.html
share/doc/postgresql/html/encryption-options.html
share/doc/postgresql/html/errcodes-appendix.html
share/doc/postgresql/html/error-message-reporting.html
share/doc/postgresql/html/error-style-guide.html
share/doc/postgresql/html/event-log-registration.html
share/doc/postgresql/html/executor.html
share/doc/postgresql/html/explicit-joins.html
share/doc/postgresql/html/explicit-locking.html
share/doc/postgresql/html/extend-extensions.html
share/doc/postgresql/html/extend-how.html
share/doc/postgresql/html/extend-pgxs.html
share/doc/postgresql/html/extend-type-system.html
share/doc/postgresql/html/extend.html
share/doc/postgresql/html/external-admin-tools.html
share/doc/postgresql/html/external-extensions.html
share/doc/postgresql/html/external-interfaces.html
share/doc/postgresql/html/external-pl.html
share/doc/postgresql/html/external-projects.html
share/doc/postgresql/html/fdw-callbacks.html
share/doc/postgresql/html/fdw-functions.html
share/doc/postgresql/html/fdw-helpers.html
share/doc/postgresql/html/fdw-planning.html
share/doc/postgresql/html/fdwhandler.html
share/doc/postgresql/html/features-sql-standard.html
share/doc/postgresql/html/features.html
share/doc/postgresql/html/file-fdw.html
share/doc/postgresql/html/functions-admin.html
share/doc/postgresql/html/functions-aggregate.html
share/doc/postgresql/html/functions-array.html
share/doc/postgresql/html/functions-binarystring.html
share/doc/postgresql/html/functions-bitstring.html
share/doc/postgresql/html/functions-comparison.html
share/doc/postgresql/html/functions-comparisons.html
share/doc/postgresql/html/functions-conditional.html
share/doc/postgresql/html/functions-datetime.html
share/doc/postgresql/html/functions-enum.html
share/doc/postgresql/html/functions-formatting.html
share/doc/postgresql/html/functions-geometry.html
share/doc/postgresql/html/functions-info.html
share/doc/postgresql/html/functions-json.html
share/doc/postgresql/html/functions-logical.html
share/doc/postgresql/html/functions-matching.html
share/doc/postgresql/html/functions-math.html
share/doc/postgresql/html/functions-net.html
share/doc/postgresql/html/functions-range.html
share/doc/postgresql/html/functions-sequence.html
share/doc/postgresql/html/functions-srf.html
share/doc/postgresql/html/functions-string.html
share/doc/postgresql/html/functions-subquery.html
share/doc/postgresql/html/functions-textsearch.html
share/doc/postgresql/html/functions-trigger.html
share/doc/postgresql/html/functions-window.html
share/doc/postgresql/html/functions-xml.html
share/doc/postgresql/html/functions.html
share/doc/postgresql/html/fuzzystrmatch.html
share/doc/postgresql/html/geqo-biblio.html
share/doc/postgresql/html/geqo-intro.html
share/doc/postgresql/html/geqo-intro2.html
share/doc/postgresql/html/geqo-pg-intro.html
share/doc/postgresql/html/geqo.html
share/doc/postgresql/html/gin-examples.html
share/doc/postgresql/html/gin-extensibility.html
share/doc/postgresql/html/gin-implementation.html
share/doc/postgresql/html/gin-intro.html
share/doc/postgresql/html/gin-limit.html
share/doc/postgresql/html/gin-tips.html
share/doc/postgresql/html/gin.html
share/doc/postgresql/html/gist-examples.html
share/doc/postgresql/html/gist-extensibility.html
share/doc/postgresql/html/gist-implementation.html
share/doc/postgresql/html/gist-intro.html
share/doc/postgresql/html/gist.html
share/doc/postgresql/html/git.html
share/doc/postgresql/html/high-availability.html
share/doc/postgresql/html/history.html
share/doc/postgresql/html/hot-standby.html
share/doc/postgresql/html/hstore.html
share/doc/postgresql/html/index-catalog.html
share/doc/postgresql/html/index-cost-estimation.html
share/doc/postgresql/html/index-functions.html
share/doc/postgresql/html/index-locking.html
share/doc/postgresql/html/index-scanning.html
share/doc/postgresql/html/index-unique-checks.html
share/doc/postgresql/html/index.html
share/doc/postgresql/html/indexam.html
share/doc/postgresql/html/indexes-bitmap-scans.html
share/doc/postgresql/html/indexes-collations.html
share/doc/postgresql/html/indexes-examine.html
share/doc/postgresql/html/indexes-expressional.html
share/doc/postgresql/html/indexes-intro.html
share/doc/postgresql/html/indexes-multicolumn.html
share/doc/postgresql/html/indexes-opclass.html
share/doc/postgresql/html/indexes-ordering.html
share/doc/postgresql/html/indexes-partial.html
share/doc/postgresql/html/indexes-types.html
share/doc/postgresql/html/indexes-unique.html
share/doc/postgresql/html/indexes.html
share/doc/postgresql/html/information-schema.html
share/doc/postgresql/html/infoschema-administrable-role-authorizations.html
share/doc/postgresql/html/infoschema-applicable-roles.html
share/doc/postgresql/html/infoschema-attributes.html
share/doc/postgresql/html/infoschema-character-sets.html
share/doc/postgresql/html/infoschema-check-constraint-routine-usage.html
share/doc/postgresql/html/infoschema-check-constraints.html
share/doc/postgresql/html/infoschema-collation-character-set-applicab.html
share/doc/postgresql/html/infoschema-collations.html
share/doc/postgresql/html/infoschema-column-domain-usage.html
share/doc/postgresql/html/infoschema-column-options.html
share/doc/postgresql/html/infoschema-column-privileges.html
share/doc/postgresql/html/infoschema-column-udt-usage.html
share/doc/postgresql/html/infoschema-columns.html
share/doc/postgresql/html/infoschema-constraint-column-usage.html
share/doc/postgresql/html/infoschema-constraint-table-usage.html
share/doc/postgresql/html/infoschema-data-type-privileges.html
share/doc/postgresql/html/infoschema-datatypes.html
share/doc/postgresql/html/infoschema-domain-constraints.html
share/doc/postgresql/html/infoschema-domain-udt-usage.html
share/doc/postgresql/html/infoschema-domains.html
share/doc/postgresql/html/infoschema-element-types.html
share/doc/postgresql/html/infoschema-enabled-roles.html
share/doc/postgresql/html/infoschema-foreign-data-wrapper-options.html
share/doc/postgresql/html/infoschema-foreign-data-wrappers.html
share/doc/postgresql/html/infoschema-foreign-server-options.html
share/doc/postgresql/html/infoschema-foreign-servers.html
share/doc/postgresql/html/infoschema-foreign-table-options.html
share/doc/postgresql/html/infoschema-foreign-tables.html
share/doc/postgresql/html/infoschema-information-schema-catalog-name.html
share/doc/postgresql/html/infoschema-key-column-usage.html
share/doc/postgresql/html/infoschema-parameters.html
share/doc/postgresql/html/infoschema-referential-constraints.html
share/doc/postgresql/html/infoschema-role-column-grants.html
share/doc/postgresql/html/infoschema-role-routine-grants.html
share/doc/postgresql/html/infoschema-role-table-grants.html
share/doc/postgresql/html/infoschema-role-udt-grants.html
share/doc/postgresql/html/infoschema-role-usage-grants.html
share/doc/postgresql/html/infoschema-routine-privileges.html
share/doc/postgresql/html/infoschema-routines.html
share/doc/postgresql/html/infoschema-schema.html
share/doc/postgresql/html/infoschema-schemata.html
share/doc/postgresql/html/infoschema-sequences.html
share/doc/postgresql/html/infoschema-sql-features.html
share/doc/postgresql/html/infoschema-sql-implementation-info.html
share/doc/postgresql/html/infoschema-sql-languages.html
share/doc/postgresql/html/infoschema-sql-packages.html
share/doc/postgresql/html/infoschema-sql-parts.html
share/doc/postgresql/html/infoschema-sql-sizing-profiles.html
share/doc/postgresql/html/infoschema-sql-sizing.html
share/doc/postgresql/html/infoschema-table-constraints.html
share/doc/postgresql/html/infoschema-table-privileges.html
share/doc/postgresql/html/infoschema-tables.html
share/doc/postgresql/html/infoschema-triggered-update-columns.html
share/doc/postgresql/html/infoschema-triggers.html
share/doc/postgresql/html/infoschema-udt-privileges.html
share/doc/postgresql/html/infoschema-usage-privileges.html
share/doc/postgresql/html/infoschema-user-defined-types.html
share/doc/postgresql/html/infoschema-user-mapping-options.html
share/doc/postgresql/html/infoschema-user-mappings.html
share/doc/postgresql/html/infoschema-view-column-usage.html
share/doc/postgresql/html/infoschema-view-routine-usage.html
share/doc/postgresql/html/infoschema-view-table-usage.html
share/doc/postgresql/html/infoschema-views.html
share/doc/postgresql/html/install-getsource.html
share/doc/postgresql/html/install-post.html
share/doc/postgresql/html/install-procedure.html
share/doc/postgresql/html/install-requirements.html
share/doc/postgresql/html/install-short.html
share/doc/postgresql/html/install-windows-full.html
share/doc/postgresql/html/install-windows-libpq.html
share/doc/postgresql/html/install-windows.html
share/doc/postgresql/html/installation-platform-notes.html
share/doc/postgresql/html/installation.html
share/doc/postgresql/html/intagg.html
share/doc/postgresql/html/intarray.html
share/doc/postgresql/html/internals.html
share/doc/postgresql/html/intro-whatis.html
share/doc/postgresql/html/isn.html
share/doc/postgresql/html/kernel-resources.html
share/doc/postgresql/html/largeobjects.html
share/doc/postgresql/html/libpq-async.html
share/doc/postgresql/html/libpq-build.html
share/doc/postgresql/html/libpq-cancel.html
share/doc/postgresql/html/libpq-connect.html
share/doc/postgresql/html/libpq-control.html
share/doc/postgresql/html/libpq-copy.html
share/doc/postgresql/html/libpq-envars.html
share/doc/postgresql/html/libpq-events.html
share/doc/postgresql/html/libpq-example.html
share/doc/postgresql/html/libpq-exec.html
share/doc/postgresql/html/libpq-fastpath.html
share/doc/postgresql/html/libpq-ldap.html
share/doc/postgresql/html/libpq-misc.html
share/doc/postgresql/html/libpq-notice-processing.html
share/doc/postgresql/html/libpq-notify.html
share/doc/postgresql/html/libpq-pgpass.html
share/doc/postgresql/html/libpq-pgservice.html
share/doc/postgresql/html/libpq-single-row-mode.html
share/doc/postgresql/html/libpq-ssl.html
share/doc/postgresql/html/libpq-status.html
share/doc/postgresql/html/libpq-threading.html
share/doc/postgresql/html/libpq.html
share/doc/postgresql/html/lo-examplesect.html
share/doc/postgresql/html/lo-funcs.html
share/doc/postgresql/html/lo-implementation.html
share/doc/postgresql/html/lo-interfaces.html
share/doc/postgresql/html/lo-intro.html
share/doc/postgresql/html/lo.html
share/doc/postgresql/html/locale.html
share/doc/postgresql/html/locking-indexes.html
share/doc/postgresql/html/log-shipping-alternative.html
share/doc/postgresql/html/logfile-maintenance.html
share/doc/postgresql/html/ltree.html
share/doc/postgresql/html/maintenance.html
share/doc/postgresql/html/manage-ag-config.html
share/doc/postgresql/html/manage-ag-createdb.html
share/doc/postgresql/html/manage-ag-dropdb.html
share/doc/postgresql/html/manage-ag-overview.html
share/doc/postgresql/html/manage-ag-tablespaces.html
share/doc/postgresql/html/manage-ag-templatedbs.html
share/doc/postgresql/html/managing-databases.html
share/doc/postgresql/html/monitoring-locks.html
share/doc/postgresql/html/monitoring-ps.html
share/doc/postgresql/html/monitoring-stats.html
share/doc/postgresql/html/monitoring.html
share/doc/postgresql/html/multibyte.html
Changes 9.2.14: Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
2015-10-11 12:59:20 +02:00
share/doc/postgresql/html/mvcc-caveats.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/mvcc-intro.html
share/doc/postgresql/html/mvcc.html
share/doc/postgresql/html/nls-programmer.html
share/doc/postgresql/html/nls-translator.html
share/doc/postgresql/html/nls.html
share/doc/postgresql/html/non-durability.html
share/doc/postgresql/html/notation.html
share/doc/postgresql/html/oid2name.html
share/doc/postgresql/html/overview.html
share/doc/postgresql/html/pageinspect.html
share/doc/postgresql/html/parser-stage.html
share/doc/postgresql/html/passwordcheck.html
share/doc/postgresql/html/performance-tips.html
share/doc/postgresql/html/perm-functions.html
share/doc/postgresql/html/pgarchivecleanup.html
share/doc/postgresql/html/pgbench.html
share/doc/postgresql/html/pgbuffercache.html
share/doc/postgresql/html/pgcrypto.html
share/doc/postgresql/html/pgfreespacemap.html
share/doc/postgresql/html/pgrowlocks.html
share/doc/postgresql/html/pgstandby.html
share/doc/postgresql/html/pgstatstatements.html
share/doc/postgresql/html/pgstattuple.html
share/doc/postgresql/html/pgtestfsync.html
share/doc/postgresql/html/pgtesttiming.html
share/doc/postgresql/html/pgtrgm.html
share/doc/postgresql/html/pgupgrade.html
share/doc/postgresql/html/planner-optimizer.html
share/doc/postgresql/html/planner-stats-details.html
share/doc/postgresql/html/planner-stats.html
share/doc/postgresql/html/plhandler.html
share/doc/postgresql/html/plperl-builtins.html
share/doc/postgresql/html/plperl-data.html
share/doc/postgresql/html/plperl-funcs.html
share/doc/postgresql/html/plperl-global.html
share/doc/postgresql/html/plperl-triggers.html
share/doc/postgresql/html/plperl-trusted.html
share/doc/postgresql/html/plperl-under-the-hood.html
share/doc/postgresql/html/plperl.html
share/doc/postgresql/html/plpgsql-control-structures.html
share/doc/postgresql/html/plpgsql-cursors.html
share/doc/postgresql/html/plpgsql-declarations.html
share/doc/postgresql/html/plpgsql-development-tips.html
share/doc/postgresql/html/plpgsql-errors-and-messages.html
share/doc/postgresql/html/plpgsql-expressions.html
share/doc/postgresql/html/plpgsql-implementation.html
share/doc/postgresql/html/plpgsql-overview.html
share/doc/postgresql/html/plpgsql-porting.html
share/doc/postgresql/html/plpgsql-statements.html
share/doc/postgresql/html/plpgsql-structure.html
share/doc/postgresql/html/plpgsql-trigger.html
share/doc/postgresql/html/plpgsql.html
share/doc/postgresql/html/plpython-data.html
share/doc/postgresql/html/plpython-database.html
share/doc/postgresql/html/plpython-do.html
share/doc/postgresql/html/plpython-envar.html
share/doc/postgresql/html/plpython-funcs.html
share/doc/postgresql/html/plpython-python23.html
share/doc/postgresql/html/plpython-sharing.html
share/doc/postgresql/html/plpython-subtransaction.html
share/doc/postgresql/html/plpython-trigger.html
share/doc/postgresql/html/plpython-util.html
share/doc/postgresql/html/plpython.html
share/doc/postgresql/html/pltcl-data.html
share/doc/postgresql/html/pltcl-dbaccess.html
share/doc/postgresql/html/pltcl-functions.html
share/doc/postgresql/html/pltcl-global.html
share/doc/postgresql/html/pltcl-overview.html
share/doc/postgresql/html/pltcl-procnames.html
share/doc/postgresql/html/pltcl-trigger.html
share/doc/postgresql/html/pltcl-unknown.html
share/doc/postgresql/html/pltcl.html
share/doc/postgresql/html/populate.html
share/doc/postgresql/html/postgres-user.html
share/doc/postgresql/html/preface.html
share/doc/postgresql/html/preventing-server-spoofing.html
share/doc/postgresql/html/protocol-changes.html
share/doc/postgresql/html/protocol-error-fields.html
share/doc/postgresql/html/protocol-flow.html
share/doc/postgresql/html/protocol-message-formats.html
share/doc/postgresql/html/protocol-message-types.html
share/doc/postgresql/html/protocol-overview.html
share/doc/postgresql/html/protocol-replication.html
share/doc/postgresql/html/protocol.html
share/doc/postgresql/html/queries-limit.html
share/doc/postgresql/html/queries-order.html
share/doc/postgresql/html/queries-overview.html
share/doc/postgresql/html/queries-select-lists.html
share/doc/postgresql/html/queries-table-expressions.html
share/doc/postgresql/html/queries-union.html
share/doc/postgresql/html/queries-values.html
share/doc/postgresql/html/queries-with.html
share/doc/postgresql/html/queries.html
share/doc/postgresql/html/query-path.html
share/doc/postgresql/html/querytree.html
share/doc/postgresql/html/rangetypes.html
share/doc/postgresql/html/recovery-config.html
share/doc/postgresql/html/recovery-target-settings.html
share/doc/postgresql/html/reference-client.html
share/doc/postgresql/html/reference-server.html
share/doc/postgresql/html/reference.html
share/doc/postgresql/html/regress-coverage.html
share/doc/postgresql/html/regress-evaluation.html
share/doc/postgresql/html/regress-run.html
share/doc/postgresql/html/regress-variant.html
share/doc/postgresql/html/regress.html
share/doc/postgresql/html/release-0-01.html
share/doc/postgresql/html/release-0-02.html
share/doc/postgresql/html/release-0-03.html
share/doc/postgresql/html/release-1-0.html
share/doc/postgresql/html/release-1-01.html
share/doc/postgresql/html/release-1-02.html
share/doc/postgresql/html/release-1-09.html
share/doc/postgresql/html/release-6-0.html
share/doc/postgresql/html/release-6-1-1.html
share/doc/postgresql/html/release-6-1.html
share/doc/postgresql/html/release-6-2-1.html
share/doc/postgresql/html/release-6-2.html
share/doc/postgresql/html/release-6-3-1.html
share/doc/postgresql/html/release-6-3-2.html
share/doc/postgresql/html/release-6-3.html
share/doc/postgresql/html/release-6-4-1.html
share/doc/postgresql/html/release-6-4-2.html
share/doc/postgresql/html/release-6-4.html
share/doc/postgresql/html/release-6-5-1.html
share/doc/postgresql/html/release-6-5-2.html
share/doc/postgresql/html/release-6-5-3.html
share/doc/postgresql/html/release-6-5.html
share/doc/postgresql/html/release-7-0-1.html
share/doc/postgresql/html/release-7-0-2.html
share/doc/postgresql/html/release-7-0-3.html
share/doc/postgresql/html/release-7-0.html
share/doc/postgresql/html/release-7-1-1.html
share/doc/postgresql/html/release-7-1-2.html
share/doc/postgresql/html/release-7-1-3.html
share/doc/postgresql/html/release-7-1.html
share/doc/postgresql/html/release-7-2-1.html
share/doc/postgresql/html/release-7-2-2.html
share/doc/postgresql/html/release-7-2-3.html
share/doc/postgresql/html/release-7-2-4.html
share/doc/postgresql/html/release-7-2-5.html
share/doc/postgresql/html/release-7-2-6.html
share/doc/postgresql/html/release-7-2-7.html
share/doc/postgresql/html/release-7-2-8.html
share/doc/postgresql/html/release-7-2.html
share/doc/postgresql/html/release-7-3-1.html
share/doc/postgresql/html/release-7-3-10.html
share/doc/postgresql/html/release-7-3-11.html
share/doc/postgresql/html/release-7-3-12.html
share/doc/postgresql/html/release-7-3-13.html
share/doc/postgresql/html/release-7-3-14.html
share/doc/postgresql/html/release-7-3-15.html
share/doc/postgresql/html/release-7-3-16.html
share/doc/postgresql/html/release-7-3-17.html
share/doc/postgresql/html/release-7-3-18.html
share/doc/postgresql/html/release-7-3-19.html
share/doc/postgresql/html/release-7-3-2.html
share/doc/postgresql/html/release-7-3-20.html
share/doc/postgresql/html/release-7-3-21.html
share/doc/postgresql/html/release-7-3-3.html
share/doc/postgresql/html/release-7-3-4.html
share/doc/postgresql/html/release-7-3-5.html
share/doc/postgresql/html/release-7-3-6.html
share/doc/postgresql/html/release-7-3-7.html
share/doc/postgresql/html/release-7-3-8.html
share/doc/postgresql/html/release-7-3-9.html
share/doc/postgresql/html/release-7-3.html
share/doc/postgresql/html/release-7-4-1.html
share/doc/postgresql/html/release-7-4-10.html
share/doc/postgresql/html/release-7-4-11.html
share/doc/postgresql/html/release-7-4-12.html
share/doc/postgresql/html/release-7-4-13.html
share/doc/postgresql/html/release-7-4-14.html
share/doc/postgresql/html/release-7-4-15.html
share/doc/postgresql/html/release-7-4-16.html
share/doc/postgresql/html/release-7-4-17.html
share/doc/postgresql/html/release-7-4-18.html
share/doc/postgresql/html/release-7-4-19.html
share/doc/postgresql/html/release-7-4-2.html
share/doc/postgresql/html/release-7-4-20.html
share/doc/postgresql/html/release-7-4-21.html
share/doc/postgresql/html/release-7-4-22.html
share/doc/postgresql/html/release-7-4-23.html
share/doc/postgresql/html/release-7-4-24.html
share/doc/postgresql/html/release-7-4-25.html
share/doc/postgresql/html/release-7-4-26.html
share/doc/postgresql/html/release-7-4-27.html
share/doc/postgresql/html/release-7-4-28.html
share/doc/postgresql/html/release-7-4-29.html
share/doc/postgresql/html/release-7-4-3.html
share/doc/postgresql/html/release-7-4-30.html
share/doc/postgresql/html/release-7-4-4.html
share/doc/postgresql/html/release-7-4-5.html
share/doc/postgresql/html/release-7-4-6.html
share/doc/postgresql/html/release-7-4-7.html
share/doc/postgresql/html/release-7-4-8.html
share/doc/postgresql/html/release-7-4-9.html
share/doc/postgresql/html/release-7-4.html
share/doc/postgresql/html/release-8-0-1.html
share/doc/postgresql/html/release-8-0-10.html
share/doc/postgresql/html/release-8-0-11.html
share/doc/postgresql/html/release-8-0-12.html
share/doc/postgresql/html/release-8-0-13.html
share/doc/postgresql/html/release-8-0-14.html
share/doc/postgresql/html/release-8-0-15.html
share/doc/postgresql/html/release-8-0-16.html
share/doc/postgresql/html/release-8-0-17.html
share/doc/postgresql/html/release-8-0-18.html
share/doc/postgresql/html/release-8-0-19.html
share/doc/postgresql/html/release-8-0-2.html
share/doc/postgresql/html/release-8-0-20.html
share/doc/postgresql/html/release-8-0-21.html
share/doc/postgresql/html/release-8-0-22.html
share/doc/postgresql/html/release-8-0-23.html
share/doc/postgresql/html/release-8-0-24.html
share/doc/postgresql/html/release-8-0-25.html
share/doc/postgresql/html/release-8-0-26.html
share/doc/postgresql/html/release-8-0-3.html
share/doc/postgresql/html/release-8-0-4.html
share/doc/postgresql/html/release-8-0-5.html
share/doc/postgresql/html/release-8-0-6.html
share/doc/postgresql/html/release-8-0-7.html
share/doc/postgresql/html/release-8-0-8.html
share/doc/postgresql/html/release-8-0-9.html
share/doc/postgresql/html/release-8-0.html
share/doc/postgresql/html/release-8-1-1.html
share/doc/postgresql/html/release-8-1-10.html
share/doc/postgresql/html/release-8-1-11.html
share/doc/postgresql/html/release-8-1-12.html
share/doc/postgresql/html/release-8-1-13.html
share/doc/postgresql/html/release-8-1-14.html
share/doc/postgresql/html/release-8-1-15.html
share/doc/postgresql/html/release-8-1-16.html
share/doc/postgresql/html/release-8-1-17.html
share/doc/postgresql/html/release-8-1-18.html
share/doc/postgresql/html/release-8-1-19.html
share/doc/postgresql/html/release-8-1-2.html
share/doc/postgresql/html/release-8-1-20.html
share/doc/postgresql/html/release-8-1-21.html
share/doc/postgresql/html/release-8-1-22.html
share/doc/postgresql/html/release-8-1-23.html
share/doc/postgresql/html/release-8-1-3.html
share/doc/postgresql/html/release-8-1-4.html
share/doc/postgresql/html/release-8-1-5.html
share/doc/postgresql/html/release-8-1-6.html
share/doc/postgresql/html/release-8-1-7.html
share/doc/postgresql/html/release-8-1-8.html
share/doc/postgresql/html/release-8-1-9.html
share/doc/postgresql/html/release-8-1.html
share/doc/postgresql/html/release-8-2-1.html
share/doc/postgresql/html/release-8-2-10.html
share/doc/postgresql/html/release-8-2-11.html
share/doc/postgresql/html/release-8-2-12.html
share/doc/postgresql/html/release-8-2-13.html
share/doc/postgresql/html/release-8-2-14.html
share/doc/postgresql/html/release-8-2-15.html
share/doc/postgresql/html/release-8-2-16.html
share/doc/postgresql/html/release-8-2-17.html
share/doc/postgresql/html/release-8-2-18.html
share/doc/postgresql/html/release-8-2-19.html
share/doc/postgresql/html/release-8-2-2.html
share/doc/postgresql/html/release-8-2-20.html
share/doc/postgresql/html/release-8-2-21.html
share/doc/postgresql/html/release-8-2-22.html
share/doc/postgresql/html/release-8-2-23.html
share/doc/postgresql/html/release-8-2-3.html
share/doc/postgresql/html/release-8-2-4.html
share/doc/postgresql/html/release-8-2-5.html
share/doc/postgresql/html/release-8-2-6.html
share/doc/postgresql/html/release-8-2-7.html
share/doc/postgresql/html/release-8-2-8.html
share/doc/postgresql/html/release-8-2-9.html
share/doc/postgresql/html/release-8-2.html
share/doc/postgresql/html/release-8-3-1.html
share/doc/postgresql/html/release-8-3-10.html
share/doc/postgresql/html/release-8-3-11.html
share/doc/postgresql/html/release-8-3-12.html
share/doc/postgresql/html/release-8-3-13.html
share/doc/postgresql/html/release-8-3-14.html
share/doc/postgresql/html/release-8-3-15.html
share/doc/postgresql/html/release-8-3-16.html
share/doc/postgresql/html/release-8-3-17.html
share/doc/postgresql/html/release-8-3-18.html
share/doc/postgresql/html/release-8-3-19.html
share/doc/postgresql/html/release-8-3-2.html
share/doc/postgresql/html/release-8-3-20.html
share/doc/postgresql/html/release-8-3-21.html
This release fixes a significant page ordering issue with Hot Standby which could cause index corruption on the standby under some circumstances. In addition, this update patches timing issues with checkpoint and transaction ID wraparound which could cause data corruption in some cases. Today's update also fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. Users who use this feature may want to REINDEX or recreate affected indexes (see below). This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last month, including several fixes which are specific to version 9.2. These include: * Prevent psql crash due to incorrectly encoded input data * Fix pg_regress gmake build issues * Make sure correct directory is created for extensions * Fix some issues with buffer locks and VACUUM * Multiple fixes and improvements for pg_upgrade * Fix bugs with end-of-recovery when failing over to a standby * Avoid bogus "out-of-sequence timeline ID" errors in standby-mode * Don't launch new child processes during shutdown * Improve the ability of JOINs to use partial indexes * Fix assorted integer overflow errors * Eliminate memory leaks in record_out() and record_send() * Skip searching for subtransaction logs at COMMIT * Fix WaitLatch() timing issues * Fix handling of inherited check constraints in ALTER COLUMN TYPE * Make ALTER EXTENSION SET SCHEMA behave as documented * Have SEQUENCE SET statements in the "data" section of sectional dumps * Prevent parser from believing that VIEWs have system columns * Fix --clean mode for pg_dump * Prevent hash table corruption on out-of-memory * Various query planner and executor fixes and improvements * Multiple documentation updates * DST updates for seven timezones
2012-12-07 22:19:50 +01:00
share/doc/postgresql/html/release-8-3-22.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
2013-02-09 12:19:08 +01:00
share/doc/postgresql/html/release-8-3-23.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-8-3-3.html
share/doc/postgresql/html/release-8-3-4.html
share/doc/postgresql/html/release-8-3-5.html
share/doc/postgresql/html/release-8-3-6.html
share/doc/postgresql/html/release-8-3-7.html
share/doc/postgresql/html/release-8-3-8.html
share/doc/postgresql/html/release-8-3-9.html
share/doc/postgresql/html/release-8-3.html
share/doc/postgresql/html/release-8-4-1.html
share/doc/postgresql/html/release-8-4-10.html
share/doc/postgresql/html/release-8-4-11.html
share/doc/postgresql/html/release-8-4-12.html
share/doc/postgresql/html/release-8-4-13.html
share/doc/postgresql/html/release-8-4-14.html
This release fixes a significant page ordering issue with Hot Standby which could cause index corruption on the standby under some circumstances. In addition, this update patches timing issues with checkpoint and transaction ID wraparound which could cause data corruption in some cases. Today's update also fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. Users who use this feature may want to REINDEX or recreate affected indexes (see below). This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last month, including several fixes which are specific to version 9.2. These include: * Prevent psql crash due to incorrectly encoded input data * Fix pg_regress gmake build issues * Make sure correct directory is created for extensions * Fix some issues with buffer locks and VACUUM * Multiple fixes and improvements for pg_upgrade * Fix bugs with end-of-recovery when failing over to a standby * Avoid bogus "out-of-sequence timeline ID" errors in standby-mode * Don't launch new child processes during shutdown * Improve the ability of JOINs to use partial indexes * Fix assorted integer overflow errors * Eliminate memory leaks in record_out() and record_send() * Skip searching for subtransaction logs at COMMIT * Fix WaitLatch() timing issues * Fix handling of inherited check constraints in ALTER COLUMN TYPE * Make ALTER EXTENSION SET SCHEMA behave as documented * Have SEQUENCE SET statements in the "data" section of sectional dumps * Prevent parser from believing that VIEWs have system columns * Fix --clean mode for pg_dump * Prevent hash table corruption on out-of-memory * Various query planner and executor fixes and improvements * Multiple documentation updates * DST updates for seven timezones
2012-12-07 22:19:50 +01:00
share/doc/postgresql/html/release-8-4-15.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
2013-02-09 12:19:08 +01:00
share/doc/postgresql/html/release-8-4-16.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately. A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request. Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2013-04-04 23:08:25 +02:00
share/doc/postgresql/html/release-8-4-17.html
Changes 9.2.5: Guarantee transmission of all WAL files before replica failover Prevent downcasing of non-ASCII identifiers Fix several minor memory leaks Correct overcommit behavior when using more than 24GB of work memory Improve planner cost estimates for choosing generic plans Fix estimates of NULL rows in boolean columns Make UNION ALL and inheritance query plans recheck parameterized paths Correct pg_dump bugs for foreign tables, views, and extensions Prevent a parallel pg_restore failure on certain indexes Make REINDEX revalidate constraints Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY Prevent GiST index lookup crash Fix several regular expression failures Allow ALTER DEFAULT PRIVILEGES to work on all schemas Loosen restrictions on keywords Allow various spellings of infinity Expand ability to compare rows to records and arrays Prevent psql client crash on bad PSQLRC file Add spinlock support for ARM64
2013-10-12 09:04:22 +02:00
share/doc/postgresql/html/release-8-4-18.html
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
2013-12-10 23:32:56 +01:00
share/doc/postgresql/html/release-8-4-19.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-8-4-2.html
Changes: This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases. In addition to the above, the following issues are fixed in this release: Fix WAL logging of visibility map change Make sure that GIN indexes log all insertions Get pause_at_recovery_target to pause at correct time Ensure walreceiver sends hot-standby feedback messages on time Prevent timeout interrupts from taking control away from mainline code Eliminate several race conditions Fix some broken HINTs in error messages Prevent server lockup on SSL connection loss Fix two Unicode handling issues Prevent crash on certain subselect syntax Prevent crash on select from zero column table Fix two bugs with LATERAL Fix issue with UNION ALL, partitioning, and updates Ensure that ANALYZE understands domains over ranges Eliminate permissions check when using default tablespace Fix memory leakage in JSON functions Allow extensions with event triggers Distinguish numbers correctly in JSON output Fix permissions for pg_start_backup() and pg_stop_backup() Accept SHIFT_JIS as locale name Fix .* expansion for SQL function variables Prevent infinite loop on some COPY connection failures Several fixes for client issues on Windows Enable building PostgreSQL with Visual Studio 2013 Update time zone files for recent changes
2014-02-23 12:25:50 +01:00
share/doc/postgresql/html/release-8-4-20.html
This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update. Other PostgreSQL 9.3-only fixes in this update include: Make sure that statistics files for dropped databases get deleted Allow materialized views to be referenced in UPDATE and DELETE queries Add read-only data_checksum parameter Prevent erroneous operator push-down in postgres_fdw This release resolves some other issues in all versions of PostgreSQL, including: Fix timing consistency issue with NOTIFY Allow regular expression execution to be cancelled Improve performance of index checks for newly added rows Prevent premature walsender disconnection Prevent memory errors on newer Windows versions Update timezone files
2014-03-27 21:57:54 +01:00
share/doc/postgresql/html/release-8-4-21.html
The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22. This minor release fixes a number of issues discovered and reported by users over the last four months, including some data corruption issues, and is the last update of version 8.4. Users of version 9.3 will want to update at the earliest opportunity; users of version 8.4 will want to schedule an upgrade to a supported PostgreSQL version.
2014-07-26 00:14:55 +02:00
share/doc/postgresql/html/release-8-4-22.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-8-4-3.html
share/doc/postgresql/html/release-8-4-4.html
share/doc/postgresql/html/release-8-4-5.html
share/doc/postgresql/html/release-8-4-6.html
share/doc/postgresql/html/release-8-4-7.html
share/doc/postgresql/html/release-8-4-8.html
share/doc/postgresql/html/release-8-4-9.html
share/doc/postgresql/html/release-8-4.html
share/doc/postgresql/html/release-9-0-1.html
share/doc/postgresql/html/release-9-0-10.html
This release fixes a significant page ordering issue with Hot Standby which could cause index corruption on the standby under some circumstances. In addition, this update patches timing issues with checkpoint and transaction ID wraparound which could cause data corruption in some cases. Today's update also fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. Users who use this feature may want to REINDEX or recreate affected indexes (see below). This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last month, including several fixes which are specific to version 9.2. These include: * Prevent psql crash due to incorrectly encoded input data * Fix pg_regress gmake build issues * Make sure correct directory is created for extensions * Fix some issues with buffer locks and VACUUM * Multiple fixes and improvements for pg_upgrade * Fix bugs with end-of-recovery when failing over to a standby * Avoid bogus "out-of-sequence timeline ID" errors in standby-mode * Don't launch new child processes during shutdown * Improve the ability of JOINs to use partial indexes * Fix assorted integer overflow errors * Eliminate memory leaks in record_out() and record_send() * Skip searching for subtransaction logs at COMMIT * Fix WaitLatch() timing issues * Fix handling of inherited check constraints in ALTER COLUMN TYPE * Make ALTER EXTENSION SET SCHEMA behave as documented * Have SEQUENCE SET statements in the "data" section of sectional dumps * Prevent parser from believing that VIEWs have system columns * Fix --clean mode for pg_dump * Prevent hash table corruption on out-of-memory * Various query planner and executor fixes and improvements * Multiple documentation updates * DST updates for seven timezones
2012-12-07 22:19:50 +01:00
share/doc/postgresql/html/release-9-0-11.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
2013-02-09 12:19:08 +01:00
share/doc/postgresql/html/release-9-0-12.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately. A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request. Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2013-04-04 23:08:25 +02:00
share/doc/postgresql/html/release-9-0-13.html
Changes 9.2.5: Guarantee transmission of all WAL files before replica failover Prevent downcasing of non-ASCII identifiers Fix several minor memory leaks Correct overcommit behavior when using more than 24GB of work memory Improve planner cost estimates for choosing generic plans Fix estimates of NULL rows in boolean columns Make UNION ALL and inheritance query plans recheck parameterized paths Correct pg_dump bugs for foreign tables, views, and extensions Prevent a parallel pg_restore failure on certain indexes Make REINDEX revalidate constraints Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY Prevent GiST index lookup crash Fix several regular expression failures Allow ALTER DEFAULT PRIVILEGES to work on all schemas Loosen restrictions on keywords Allow various spellings of infinity Expand ability to compare rows to records and arrays Prevent psql client crash on bad PSQLRC file Add spinlock support for ARM64
2013-10-12 09:04:22 +02:00
share/doc/postgresql/html/release-9-0-14.html
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
2013-12-10 23:32:56 +01:00
share/doc/postgresql/html/release-9-0-15.html
Changes: This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases. In addition to the above, the following issues are fixed in this release: Fix WAL logging of visibility map change Make sure that GIN indexes log all insertions Get pause_at_recovery_target to pause at correct time Ensure walreceiver sends hot-standby feedback messages on time Prevent timeout interrupts from taking control away from mainline code Eliminate several race conditions Fix some broken HINTs in error messages Prevent server lockup on SSL connection loss Fix two Unicode handling issues Prevent crash on certain subselect syntax Prevent crash on select from zero column table Fix two bugs with LATERAL Fix issue with UNION ALL, partitioning, and updates Ensure that ANALYZE understands domains over ranges Eliminate permissions check when using default tablespace Fix memory leakage in JSON functions Allow extensions with event triggers Distinguish numbers correctly in JSON output Fix permissions for pg_start_backup() and pg_stop_backup() Accept SHIFT_JIS as locale name Fix .* expansion for SQL function variables Prevent infinite loop on some COPY connection failures Several fixes for client issues on Windows Enable building PostgreSQL with Visual Studio 2013 Update time zone files for recent changes
2014-02-23 12:25:50 +01:00
share/doc/postgresql/html/release-9-0-16.html
This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update. Other PostgreSQL 9.3-only fixes in this update include: Make sure that statistics files for dropped databases get deleted Allow materialized views to be referenced in UPDATE and DELETE queries Add read-only data_checksum parameter Prevent erroneous operator push-down in postgres_fdw This release resolves some other issues in all versions of PostgreSQL, including: Fix timing consistency issue with NOTIFY Allow regular expression execution to be cancelled Improve performance of index checks for newly added rows Prevent premature walsender disconnection Prevent memory errors on newer Windows versions Update timezone files
2014-03-27 21:57:54 +01:00
share/doc/postgresql/html/release-9-0-17.html
The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22. This minor release fixes a number of issues discovered and reported by users over the last four months, including some data corruption issues, and is the last update of version 8.4. Users of version 9.3 will want to update at the earliest opportunity; users of version 8.4 will want to schedule an upgrade to a supported PostgreSQL version.
2014-07-26 00:14:55 +02:00
share/doc/postgresql/html/release-9-0-18.html
Changes 9.2.10: Security Fixes * CVE-2015-0241 Buffer overruns in "to_char" functions. * CVE-2015-0242 Buffer overrun in replacement printf family of functions. * CVE-2015-0243 Memory errors in functions in the pgcrypto extension. * CVE-2015-0244 An error in extended protocol message reading. * CVE-2014-8161 Constraint violation errors can cause display of values in columns which the user would not normally have rights to see. JSON and JSONB Unicode Escapes Other Fixes and Improvements * Cope with the non-ASCII Norwegian Windows locale name. * Avoid data corruption when databases are moved to new tablespaces and back again. * Ensure that UNLOGGED tables are correctly copied during ALTER DATABASE operations. * Avoid deadlocks when locking recently modified rows. * Fix two SELECT FOR UPDATE query issues. * Prevent false negative for shortest-first regular expression matches. * Fix false positives and negatives in tsquery contains operator. * Fix namespace handling in xpath(). * Prevent row-producing functions from creating empty column names. * Make autovacuum use per-table cost_limit and cost_delay settings. * When autovacuum=off, limit autovacuum work to wraparound prevention only. * Multiple fixes for logical decoding in 9.4. * Fix transient errors on hot standby queries due to page replacement. * Prevent duplicate WAL file archiving at end of recovery or standby promotion. * Prevent deadlock in parallel restore of schema-only dump.
2015-02-14 08:57:40 +01:00
share/doc/postgresql/html/release-9-0-19.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-0-2.html
The PostgreSQL Global Development Group has released an update with multiple functionality and security fixes to all supported versions of the PostgreSQL database system, which includes minor versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20. The update contains a critical fix for a potential data corruption issue in PostgreSQL 9.3 and 9.4; users of those versions should update their servers at the next possible opportunity.
2015-05-27 15:27:27 +02:00
share/doc/postgresql/html/release-9-0-20.html
Changes: * File Permissions Fix * Have pg_get_functiondef() show the LEAKPROOF property * Make pushJsonbValue() function push jbvBinary type * Allow building with threaded Python on OpenBSD
2015-06-08 14:52:07 +02:00
share/doc/postgresql/html/release-9-0-21.html
Changes: This release primarily fixes issues not successfully fixed in prior releases. It should be applied as soon as possible all users of major versions 9.3 and 9.4. Other users should apply at the next available downtime. Crash Recovery Fixes: Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 with "multixact wraparound", but failed to account for issues doing multixact cleanup during crash recovery. This could cause servers to be unable to restart after a crash. As such, all users of 9.3 and 9.4 should apply this update as soon as possible.
2015-06-18 16:46:13 +02:00
share/doc/postgresql/html/release-9-0-22.html
Changes 9.2.14: Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
2015-10-11 12:59:20 +02:00
share/doc/postgresql/html/release-9-0-23.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-0-3.html
share/doc/postgresql/html/release-9-0-4.html
share/doc/postgresql/html/release-9-0-5.html
share/doc/postgresql/html/release-9-0-6.html
share/doc/postgresql/html/release-9-0-7.html
share/doc/postgresql/html/release-9-0-8.html
share/doc/postgresql/html/release-9-0-9.html
share/doc/postgresql/html/release-9-0.html
share/doc/postgresql/html/release-9-1-1.html
Changes 9.2.5: Guarantee transmission of all WAL files before replica failover Prevent downcasing of non-ASCII identifiers Fix several minor memory leaks Correct overcommit behavior when using more than 24GB of work memory Improve planner cost estimates for choosing generic plans Fix estimates of NULL rows in boolean columns Make UNION ALL and inheritance query plans recheck parameterized paths Correct pg_dump bugs for foreign tables, views, and extensions Prevent a parallel pg_restore failure on certain indexes Make REINDEX revalidate constraints Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY Prevent GiST index lookup crash Fix several regular expression failures Allow ALTER DEFAULT PRIVILEGES to work on all schemas Loosen restrictions on keywords Allow various spellings of infinity Expand ability to compare rows to records and arrays Prevent psql client crash on bad PSQLRC file Add spinlock support for ARM64
2013-10-12 09:04:22 +02:00
share/doc/postgresql/html/release-9-1-10.html
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
2013-12-10 23:32:56 +01:00
share/doc/postgresql/html/release-9-1-11.html
Changes: This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases. In addition to the above, the following issues are fixed in this release: Fix WAL logging of visibility map change Make sure that GIN indexes log all insertions Get pause_at_recovery_target to pause at correct time Ensure walreceiver sends hot-standby feedback messages on time Prevent timeout interrupts from taking control away from mainline code Eliminate several race conditions Fix some broken HINTs in error messages Prevent server lockup on SSL connection loss Fix two Unicode handling issues Prevent crash on certain subselect syntax Prevent crash on select from zero column table Fix two bugs with LATERAL Fix issue with UNION ALL, partitioning, and updates Ensure that ANALYZE understands domains over ranges Eliminate permissions check when using default tablespace Fix memory leakage in JSON functions Allow extensions with event triggers Distinguish numbers correctly in JSON output Fix permissions for pg_start_backup() and pg_stop_backup() Accept SHIFT_JIS as locale name Fix .* expansion for SQL function variables Prevent infinite loop on some COPY connection failures Several fixes for client issues on Windows Enable building PostgreSQL with Visual Studio 2013 Update time zone files for recent changes
2014-02-23 12:25:50 +01:00
share/doc/postgresql/html/release-9-1-12.html
This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update. Other PostgreSQL 9.3-only fixes in this update include: Make sure that statistics files for dropped databases get deleted Allow materialized views to be referenced in UPDATE and DELETE queries Add read-only data_checksum parameter Prevent erroneous operator push-down in postgres_fdw This release resolves some other issues in all versions of PostgreSQL, including: Fix timing consistency issue with NOTIFY Allow regular expression execution to be cancelled Improve performance of index checks for newly added rows Prevent premature walsender disconnection Prevent memory errors on newer Windows versions Update timezone files
2014-03-27 21:57:54 +01:00
share/doc/postgresql/html/release-9-1-13.html
The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22. This minor release fixes a number of issues discovered and reported by users over the last four months, including some data corruption issues, and is the last update of version 8.4. Users of version 9.3 will want to update at the earliest opportunity; users of version 8.4 will want to schedule an upgrade to a supported PostgreSQL version.
2014-07-26 00:14:55 +02:00
share/doc/postgresql/html/release-9-1-14.html
Changes 9.2.10: Security Fixes * CVE-2015-0241 Buffer overruns in "to_char" functions. * CVE-2015-0242 Buffer overrun in replacement printf family of functions. * CVE-2015-0243 Memory errors in functions in the pgcrypto extension. * CVE-2015-0244 An error in extended protocol message reading. * CVE-2014-8161 Constraint violation errors can cause display of values in columns which the user would not normally have rights to see. JSON and JSONB Unicode Escapes Other Fixes and Improvements * Cope with the non-ASCII Norwegian Windows locale name. * Avoid data corruption when databases are moved to new tablespaces and back again. * Ensure that UNLOGGED tables are correctly copied during ALTER DATABASE operations. * Avoid deadlocks when locking recently modified rows. * Fix two SELECT FOR UPDATE query issues. * Prevent false negative for shortest-first regular expression matches. * Fix false positives and negatives in tsquery contains operator. * Fix namespace handling in xpath(). * Prevent row-producing functions from creating empty column names. * Make autovacuum use per-table cost_limit and cost_delay settings. * When autovacuum=off, limit autovacuum work to wraparound prevention only. * Multiple fixes for logical decoding in 9.4. * Fix transient errors on hot standby queries due to page replacement. * Prevent duplicate WAL file archiving at end of recovery or standby promotion. * Prevent deadlock in parallel restore of schema-only dump.
2015-02-14 08:57:40 +01:00
share/doc/postgresql/html/release-9-1-15.html
The PostgreSQL Global Development Group has released an update with multiple functionality and security fixes to all supported versions of the PostgreSQL database system, which includes minor versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20. The update contains a critical fix for a potential data corruption issue in PostgreSQL 9.3 and 9.4; users of those versions should update their servers at the next possible opportunity.
2015-05-27 15:27:27 +02:00
share/doc/postgresql/html/release-9-1-16.html
Changes: * File Permissions Fix * Have pg_get_functiondef() show the LEAKPROOF property * Make pushJsonbValue() function push jbvBinary type * Allow building with threaded Python on OpenBSD
2015-06-08 14:52:07 +02:00
share/doc/postgresql/html/release-9-1-17.html
Changes: This release primarily fixes issues not successfully fixed in prior releases. It should be applied as soon as possible all users of major versions 9.3 and 9.4. Other users should apply at the next available downtime. Crash Recovery Fixes: Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 with "multixact wraparound", but failed to account for issues doing multixact cleanup during crash recovery. This could cause servers to be unable to restart after a crash. As such, all users of 9.3 and 9.4 should apply this update as soon as possible.
2015-06-18 16:46:13 +02:00
share/doc/postgresql/html/release-9-1-18.html
Changes 9.2.14: Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
2015-10-11 12:59:20 +02:00
share/doc/postgresql/html/release-9-1-19.html
Update to PostgreSQL 9.2.15 (2016-02-11) This release fixes two security issues, as well as several bugs found over the last four months. CVE-2016-0773 Unicode regular expression buffer overflow CVE-2016-0766 PL/Java privilege escalation
2016-02-25 01:41:54 +01:00
share/doc/postgresql/html/release-9-1-20.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-1-2.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible. This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query. The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.
2016-04-09 14:51:44 +02:00
share/doc/postgresql/html/release-9-1-21.html
This release fixes a number of issues reported by users over the last two months. Most database administrators should plan to upgrade at the next available downtime, unless they have been affected directly by the fixed issues.
2016-05-23 16:27:34 +02:00
share/doc/postgresql/html/release-9-1-22.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.4, 9.4.9, 9.3.14, 9.2.18 and 9.1.23. This release fixes two security issues. It also patches a number of other bugs reported over the last three months. Users who rely on security isolation between database users should update as soon as possible. Other users should plan to update at the next convenient downtime. Security Issues --------------- Two security holes have been closed by this release: CVE-2016-5423: certain nested CASE expressions can cause the server to crash. CVE-2016-5424: database and role names with embedded special characters can allow code injection during administrative operations like pg_dumpall. The fix for the second issue also adds an option, -reuse-previous, to psql's \connect command. pg_dumpall will also refuse to handle database and role names containing line breaks after the update. For more information on these issues and how they affect backwards-compatibility, see the Release Notes. Bug Fixes and Improvements -------------------------- This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 9.5, but many affect all supported versions: Fix misbehaviors of IS NULL/IS NOT NULL with composite values Fix three areas where INSERT ... ON CONFLICT failed to work properly with other SQL features. Make INET and CIDR data types properly reject bad IPv6 values Prevent crash in "point ## lseg" operator for NaN input Avoid possible crash in pg_get_expr() Fix several one-byte buffer over-reads in to_number() Don't needlessly plan query if WITH NO DATA is specified Avoid crash-unsafe state in expensive heap_update() paths Fix hint bit update during WAL replay of row locking operations Avoid unnecessary "could not serialize access" with FOR KEY SHARE Avoid crash in postgres -C when the specified variable is a null string Fix two issues with logical decoding and subtransactions Ensure that backends see up-to-date statistics for shared catalogs Prevent possible failure when vacuuming multixact IDs in an upgraded database When a manual ANALYZE specifies columns, don't reset changes_since_analyze Fix ANALYZE's overestimation of n_distinct for columns with nulls Fix bug in b-tree mark/restore processing Fix building of large (bigger than shared_buffers) hash indexes Prevent infinite loop in GiST index build with NaN values Fix possible crash during a nearest-neighbor indexscan Fix "PANIC: failed to add BRIN tuple" error Prevent possible crash during background worker shutdown Many fixes for issues in parallel pg_dump and pg_restore Make pg_basebackup accept -Z 0 as no compression Make regression tests safe for Danish and Welsh locales
2016-08-23 08:28:15 +02:00
share/doc/postgresql/html/release-9-1-23.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is now end-of-life. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime.
2016-10-29 21:41:53 +02:00
share/doc/postgresql/html/release-9-1-24.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-1-3.html
share/doc/postgresql/html/release-9-1-4.html
share/doc/postgresql/html/release-9-1-5.html
share/doc/postgresql/html/release-9-1-6.html
This release fixes a significant page ordering issue with Hot Standby which could cause index corruption on the standby under some circumstances. In addition, this update patches timing issues with checkpoint and transaction ID wraparound which could cause data corruption in some cases. Today's update also fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. Users who use this feature may want to REINDEX or recreate affected indexes (see below). This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last month, including several fixes which are specific to version 9.2. These include: * Prevent psql crash due to incorrectly encoded input data * Fix pg_regress gmake build issues * Make sure correct directory is created for extensions * Fix some issues with buffer locks and VACUUM * Multiple fixes and improvements for pg_upgrade * Fix bugs with end-of-recovery when failing over to a standby * Avoid bogus "out-of-sequence timeline ID" errors in standby-mode * Don't launch new child processes during shutdown * Improve the ability of JOINs to use partial indexes * Fix assorted integer overflow errors * Eliminate memory leaks in record_out() and record_send() * Skip searching for subtransaction logs at COMMIT * Fix WaitLatch() timing issues * Fix handling of inherited check constraints in ALTER COLUMN TYPE * Make ALTER EXTENSION SET SCHEMA behave as documented * Have SEQUENCE SET statements in the "data" section of sectional dumps * Prevent parser from believing that VIEWs have system columns * Fix --clean mode for pg_dump * Prevent hash table corruption on out-of-memory * Various query planner and executor fixes and improvements * Multiple documentation updates * DST updates for seven timezones
2012-12-07 22:19:50 +01:00
share/doc/postgresql/html/release-9-1-7.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
2013-02-09 12:19:08 +01:00
share/doc/postgresql/html/release-9-1-8.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately. A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request. Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2013-04-04 23:08:25 +02:00
share/doc/postgresql/html/release-9-1-9.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-1.html
share/doc/postgresql/html/release-9-2-1.html
Changes 9.2.10: Security Fixes * CVE-2015-0241 Buffer overruns in "to_char" functions. * CVE-2015-0242 Buffer overrun in replacement printf family of functions. * CVE-2015-0243 Memory errors in functions in the pgcrypto extension. * CVE-2015-0244 An error in extended protocol message reading. * CVE-2014-8161 Constraint violation errors can cause display of values in columns which the user would not normally have rights to see. JSON and JSONB Unicode Escapes Other Fixes and Improvements * Cope with the non-ASCII Norwegian Windows locale name. * Avoid data corruption when databases are moved to new tablespaces and back again. * Ensure that UNLOGGED tables are correctly copied during ALTER DATABASE operations. * Avoid deadlocks when locking recently modified rows. * Fix two SELECT FOR UPDATE query issues. * Prevent false negative for shortest-first regular expression matches. * Fix false positives and negatives in tsquery contains operator. * Fix namespace handling in xpath(). * Prevent row-producing functions from creating empty column names. * Make autovacuum use per-table cost_limit and cost_delay settings. * When autovacuum=off, limit autovacuum work to wraparound prevention only. * Multiple fixes for logical decoding in 9.4. * Fix transient errors on hot standby queries due to page replacement. * Prevent duplicate WAL file archiving at end of recovery or standby promotion. * Prevent deadlock in parallel restore of schema-only dump.
2015-02-14 08:57:40 +01:00
share/doc/postgresql/html/release-9-2-10.html
The PostgreSQL Global Development Group has released an update with multiple functionality and security fixes to all supported versions of the PostgreSQL database system, which includes minor versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20. The update contains a critical fix for a potential data corruption issue in PostgreSQL 9.3 and 9.4; users of those versions should update their servers at the next possible opportunity.
2015-05-27 15:27:27 +02:00
share/doc/postgresql/html/release-9-2-11.html
Changes: * File Permissions Fix * Have pg_get_functiondef() show the LEAKPROOF property * Make pushJsonbValue() function push jbvBinary type * Allow building with threaded Python on OpenBSD
2015-06-08 14:52:07 +02:00
share/doc/postgresql/html/release-9-2-12.html
Changes: This release primarily fixes issues not successfully fixed in prior releases. It should be applied as soon as possible all users of major versions 9.3 and 9.4. Other users should apply at the next available downtime. Crash Recovery Fixes: Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 with "multixact wraparound", but failed to account for issues doing multixact cleanup during crash recovery. This could cause servers to be unable to restart after a crash. As such, all users of 9.3 and 9.4 should apply this update as soon as possible.
2015-06-18 16:46:13 +02:00
share/doc/postgresql/html/release-9-2-13.html
Changes 9.2.14: Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
2015-10-11 12:59:20 +02:00
share/doc/postgresql/html/release-9-2-14.html
Update to PostgreSQL 9.2.15 (2016-02-11) This release fixes two security issues, as well as several bugs found over the last four months. CVE-2016-0773 Unicode regular expression buffer overflow CVE-2016-0766 PL/Java privilege escalation
2016-02-25 01:41:54 +01:00
share/doc/postgresql/html/release-9-2-15.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible. This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query. The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.
2016-04-09 14:51:44 +02:00
share/doc/postgresql/html/release-9-2-16.html
This release fixes a number of issues reported by users over the last two months. Most database administrators should plan to upgrade at the next available downtime, unless they have been affected directly by the fixed issues.
2016-05-23 16:27:34 +02:00
share/doc/postgresql/html/release-9-2-17.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.4, 9.4.9, 9.3.14, 9.2.18 and 9.1.23. This release fixes two security issues. It also patches a number of other bugs reported over the last three months. Users who rely on security isolation between database users should update as soon as possible. Other users should plan to update at the next convenient downtime. Security Issues --------------- Two security holes have been closed by this release: CVE-2016-5423: certain nested CASE expressions can cause the server to crash. CVE-2016-5424: database and role names with embedded special characters can allow code injection during administrative operations like pg_dumpall. The fix for the second issue also adds an option, -reuse-previous, to psql's \connect command. pg_dumpall will also refuse to handle database and role names containing line breaks after the update. For more information on these issues and how they affect backwards-compatibility, see the Release Notes. Bug Fixes and Improvements -------------------------- This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 9.5, but many affect all supported versions: Fix misbehaviors of IS NULL/IS NOT NULL with composite values Fix three areas where INSERT ... ON CONFLICT failed to work properly with other SQL features. Make INET and CIDR data types properly reject bad IPv6 values Prevent crash in "point ## lseg" operator for NaN input Avoid possible crash in pg_get_expr() Fix several one-byte buffer over-reads in to_number() Don't needlessly plan query if WITH NO DATA is specified Avoid crash-unsafe state in expensive heap_update() paths Fix hint bit update during WAL replay of row locking operations Avoid unnecessary "could not serialize access" with FOR KEY SHARE Avoid crash in postgres -C when the specified variable is a null string Fix two issues with logical decoding and subtransactions Ensure that backends see up-to-date statistics for shared catalogs Prevent possible failure when vacuuming multixact IDs in an upgraded database When a manual ANALYZE specifies columns, don't reset changes_since_analyze Fix ANALYZE's overestimation of n_distinct for columns with nulls Fix bug in b-tree mark/restore processing Fix building of large (bigger than shared_buffers) hash indexes Prevent infinite loop in GiST index build with NaN values Fix possible crash during a nearest-neighbor indexscan Fix "PANIC: failed to add BRIN tuple" error Prevent possible crash during background worker shutdown Many fixes for issues in parallel pg_dump and pg_restore Make pg_basebackup accept -Z 0 as no compression Make regression tests safe for Danish and Welsh locales
2016-08-23 08:28:15 +02:00
share/doc/postgresql/html/release-9-2-18.html
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is now end-of-life. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime.
2016-10-29 21:41:53 +02:00
share/doc/postgresql/html/release-9-2-19.html
This release fixes a significant page ordering issue with Hot Standby which could cause index corruption on the standby under some circumstances. In addition, this update patches timing issues with checkpoint and transaction ID wraparound which could cause data corruption in some cases. Today's update also fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. Users who use this feature may want to REINDEX or recreate affected indexes (see below). This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last month, including several fixes which are specific to version 9.2. These include: * Prevent psql crash due to incorrectly encoded input data * Fix pg_regress gmake build issues * Make sure correct directory is created for extensions * Fix some issues with buffer locks and VACUUM * Multiple fixes and improvements for pg_upgrade * Fix bugs with end-of-recovery when failing over to a standby * Avoid bogus "out-of-sequence timeline ID" errors in standby-mode * Don't launch new child processes during shutdown * Improve the ability of JOINs to use partial indexes * Fix assorted integer overflow errors * Eliminate memory leaks in record_out() and record_send() * Skip searching for subtransaction logs at COMMIT * Fix WaitLatch() timing issues * Fix handling of inherited check constraints in ALTER COLUMN TYPE * Make ALTER EXTENSION SET SCHEMA behave as documented * Have SEQUENCE SET statements in the "data" section of sectional dumps * Prevent parser from believing that VIEWs have system columns * Fix --clean mode for pg_dump * Prevent hash table corruption on out-of-memory * Various query planner and executor fixes and improvements * Multiple documentation updates * DST updates for seven timezones
2012-12-07 22:19:50 +01:00
share/doc/postgresql/html/release-9-2-2.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
2013-02-09 12:19:08 +01:00
share/doc/postgresql/html/release-9-2-3.html
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately. A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request. Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2013-04-04 23:08:25 +02:00
share/doc/postgresql/html/release-9-2-4.html
Changes 9.2.5: Guarantee transmission of all WAL files before replica failover Prevent downcasing of non-ASCII identifiers Fix several minor memory leaks Correct overcommit behavior when using more than 24GB of work memory Improve planner cost estimates for choosing generic plans Fix estimates of NULL rows in boolean columns Make UNION ALL and inheritance query plans recheck parameterized paths Correct pg_dump bugs for foreign tables, views, and extensions Prevent a parallel pg_restore failure on certain indexes Make REINDEX revalidate constraints Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY Prevent GiST index lookup crash Fix several regular expression failures Allow ALTER DEFAULT PRIVILEGES to work on all schemas Loosen restrictions on keywords Allow various spellings of infinity Expand ability to compare rows to records and arrays Prevent psql client crash on bad PSQLRC file Add spinlock support for ARM64
2013-10-12 09:04:22 +02:00
share/doc/postgresql/html/release-9-2-5.html
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
2013-12-10 23:32:56 +01:00
share/doc/postgresql/html/release-9-2-6.html
Changes: This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases. In addition to the above, the following issues are fixed in this release: Fix WAL logging of visibility map change Make sure that GIN indexes log all insertions Get pause_at_recovery_target to pause at correct time Ensure walreceiver sends hot-standby feedback messages on time Prevent timeout interrupts from taking control away from mainline code Eliminate several race conditions Fix some broken HINTs in error messages Prevent server lockup on SSL connection loss Fix two Unicode handling issues Prevent crash on certain subselect syntax Prevent crash on select from zero column table Fix two bugs with LATERAL Fix issue with UNION ALL, partitioning, and updates Ensure that ANALYZE understands domains over ranges Eliminate permissions check when using default tablespace Fix memory leakage in JSON functions Allow extensions with event triggers Distinguish numbers correctly in JSON output Fix permissions for pg_start_backup() and pg_stop_backup() Accept SHIFT_JIS as locale name Fix .* expansion for SQL function variables Prevent infinite loop on some COPY connection failures Several fixes for client issues on Windows Enable building PostgreSQL with Visual Studio 2013 Update time zone files for recent changes
2014-02-23 12:25:50 +01:00
share/doc/postgresql/html/release-9-2-7.html
This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update. Other PostgreSQL 9.3-only fixes in this update include: Make sure that statistics files for dropped databases get deleted Allow materialized views to be referenced in UPDATE and DELETE queries Add read-only data_checksum parameter Prevent erroneous operator push-down in postgres_fdw This release resolves some other issues in all versions of PostgreSQL, including: Fix timing consistency issue with NOTIFY Allow regular expression execution to be cancelled Improve performance of index checks for newly added rows Prevent premature walsender disconnection Prevent memory errors on newer Windows versions Update timezone files
2014-03-27 21:57:54 +01:00
share/doc/postgresql/html/release-9-2-8.html
The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22. This minor release fixes a number of issues discovered and reported by users over the last four months, including some data corruption issues, and is the last update of version 8.4. Users of version 9.3 will want to update at the earliest opportunity; users of version 8.4 will want to schedule an upgrade to a supported PostgreSQL version.
2014-07-26 00:14:55 +02:00
share/doc/postgresql/html/release-9-2-9.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/release-9-2.html
share/doc/postgresql/html/release.html
share/doc/postgresql/html/resources.html
share/doc/postgresql/html/role-attributes.html
share/doc/postgresql/html/role-membership.html
Update to PostgreSQL 9.2.15 (2016-02-11) This release fixes two security issues, as well as several bugs found over the last four months. CVE-2016-0773 Unicode regular expression buffer overflow CVE-2016-0766 PL/Java privilege escalation
2016-02-25 01:41:54 +01:00
share/doc/postgresql/html/role-removal.html
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.
2012-10-05 23:03:10 +02:00
share/doc/postgresql/html/routine-reindex.html
share/doc/postgresql/html/routine-vacuuming.html
share/doc/postgresql/html/row-estimation-examples.html
share/doc/postgresql/html/rowtypes.html
share/doc/postgresql/html/rule-system.html
share/doc/postgresql/html/rules-privileges.html
share/doc/postgresql/html/rules-status.html
share/doc/postgresql/html/rules-triggers.html
share/doc/postgresql/html/rules-update.html
share/doc/postgresql/html/rules-views.html
share/doc/postgresql/html/rules.html
share/doc/postgresql/html/runtime-config-autovacuum.html
share/doc/postgresql/html/runtime-config-client.html
share/doc/postgresql/html/runtime-config-compatible.html
share/doc/postgresql/html/runtime-config-connection.html
share/doc/postgresql/html/runtime-config-custom.html
share/doc/postgresql/html/runtime-config-developer.html
share/doc/postgresql/html/runtime-config-error-handling.html
share/doc/postgresql/html/runtime-config-file-locations.html
share/doc/postgresql/html/runtime-config-locks.html
share/doc/postgresql/html/runtime-config-logging.html
share/doc/postgresql/html/runtime-config-preset.html
share/doc/postgresql/html/runtime-config-query.html
share/doc/postgresql/html/runtime-config-replication.html
share/doc/postgresql/html/runtime-config-resource.html
share/doc/postgresql/html/runtime-config-short.html
share/doc/postgresql/html/runtime-config-statistics.html
share/doc/postgresql/html/runtime-config-wal.html
share/doc/postgresql/html/runtime-config.html
share/doc/postgresql/html/runtime.html
share/doc/postgresql/html/seg.html
share/doc/postgresql/html/sepgsql.html
share/doc/postgresql/html/server-programming.html
share/doc/postgresql/html/server-shutdown.html
share/doc/postgresql/html/server-start.html
share/doc/postgresql/html/source-format.html
share/doc/postgresql/html/source.html
share/doc/postgresql/html/sourcerepo.html
share/doc/postgresql/html/spgist-examples.html
share/doc/postgresql/html/spgist-extensibility.html
share/doc/postgresql/html/spgist-implementation.html
share/doc/postgresql/html/spgist-intro.html
share/doc/postgresql/html/spgist.html
share/doc/postgresql/html/spi-examples.html
share/doc/postgresql/html/spi-interface-support.html
share/doc/postgresql/html/spi-interface.html
share/doc/postgresql/html/spi-memory.html
share/doc/postgresql/html/spi-realloc.html
share/doc/postgresql/html/spi-spi-connect.html
share/doc/postgresql/html/spi-spi-copytuple.html
share/doc/postgresql/html/spi-spi-cursor-close.html
share/doc/postgresql/html/spi-spi-cursor-fetch.html
share/doc/postgresql/html/spi-spi-cursor-find.html
share/doc/postgresql/html/spi-spi-cursor-move.html
share/doc/postgresql/html/spi-spi-cursor-open-with-args.html
share/doc/postgresql/html/spi-spi-cursor-open-with-paramlist.html
share/doc/postgresql/html/spi-spi-cursor-open.html
share/doc/postgresql/html/spi-spi-exec.html
share/doc/postgresql/html/spi-spi-execp.html
share/doc/postgresql/html/spi-spi-execute-plan-with-paramlist.html
share/doc/postgresql/html/spi-spi-execute-plan.html
share/doc/postgresql/html/spi-spi-execute-with-args.html
share/doc/postgresql/html/spi-spi-execute.html
share/doc/postgresql/html/spi-spi-finish.html
share/doc/postgresql/html/spi-spi-fname.html
share/doc/postgresql/html/spi-spi-fnumber.html
share/doc/postgresql/html/spi-spi-freeplan.html
share/doc/postgresql/html/spi-spi-freetuple.html
share/doc/postgresql/html/spi-spi-freetupletable.html
share/doc/postgresql/html/spi-spi-getargcount.html
share/doc/postgresql/html/spi-spi-getargtypeid.html
share/doc/postgresql/html/spi-spi-getbinval.html
share/doc/postgresql/html/spi-spi-getnspname.html
share/doc/postgresql/html/spi-spi-getrelname.html
share/doc/postgresql/html/spi-spi-gettype.html
share/doc/postgresql/html/spi-spi-gettypeid.html
share/doc/postgresql/html/spi-spi-getvalue.html
share/doc/postgresql/html/spi-spi-is-cursor-plan.html
share/doc/postgresql/html/spi-spi-keepplan.html
share/doc/postgresql/html/spi-spi-modifytuple.html
share/doc/postgresql/html/spi-spi-palloc.html
share/doc/postgresql/html/spi-spi-pfree.html
share/doc/postgresql/html/spi-spi-pop.html
share/doc/postgresql/html/spi-spi-prepare-cursor.html
share/doc/postgresql/html/spi-spi-prepare-params.html
share/doc/postgresql/html/spi-spi-prepare.html
share/doc/postgresql/html/spi-spi-push.html
share/doc/postgresql/html/spi-spi-returntuple.html
share/doc/postgresql/html/spi-spi-saveplan.html
share/doc/postgresql/html/spi-spi-scroll-cursor-fetch.html
share/doc/postgresql/html/spi-spi-scroll-cursor-move.html
share/doc/postgresql/html/spi-visibility.html
share/doc/postgresql/html/spi.html
share/doc/postgresql/html/sql-abort.html
share/doc/postgresql/html/sql-alteraggregate.html
share/doc/postgresql/html/sql-altercollation.html
share/doc/postgresql/html/sql-alterconversion.html
share/doc/postgresql/html/sql-alterdatabase.html
share/doc/postgresql/html/sql-alterdefaultprivileges.html
share/doc/postgresql/html/sql-alterdomain.html
share/doc/postgresql/html/sql-alterextension.html
share/doc/postgresql/html/sql-alterforeigndatawrapper.html
share/doc/postgresql/html/sql-alterforeigntable.html
share/doc/postgresql/html/sql-alterfunction.html
share/doc/postgresql/html/sql-altergroup.html
share/doc/postgresql/html/sql-alterindex.html
share/doc/postgresql/html/sql-alterlanguage.html
share/doc/postgresql/html/sql-alterlargeobject.html
share/doc/postgresql/html/sql-alteropclass.html
share/doc/postgresql/html/sql-alteroperator.html
share/doc/postgresql/html/sql-alteropfamily.html
share/doc/postgresql/html/sql-alterrole.html
share/doc/postgresql/html/sql-alterschema.html
share/doc/postgresql/html/sql-altersequence.html
share/doc/postgresql/html/sql-alterserver.html
share/doc/postgresql/html/sql-altertable.html
share/doc/postgresql/html/sql-altertablespace.html
share/doc/postgresql/html/sql-altertrigger.html
share/doc/postgresql/html/sql-altertsconfig.html
share/doc/postgresql/html/sql-altertsdictionary.html
share/doc/postgresql/html/sql-altertsparser.html
share/doc/postgresql/html/sql-altertstemplate.html
share/doc/postgresql/html/sql-altertype.html
share/doc/postgresql/html/sql-alteruser.html
share/doc/postgresql/html/sql-alterusermapping.html
share/doc/postgresql/html/sql-alterview.html
share/doc/postgresql/html/sql-analyze.html
share/doc/postgresql/html/sql-begin.html
share/doc/postgresql/html/sql-checkpoint.html
share/doc/postgresql/html/sql-close.html
share/doc/postgresql/html/sql-cluster.html
share/doc/postgresql/html/sql-commands.html
share/doc/postgresql/html/sql-comment.html
share/doc/postgresql/html/sql-commit-prepared.html
share/doc/postgresql/html/sql-commit.html
share/doc/postgresql/html/sql-copy.html
share/doc/postgresql/html/sql-createaggregate.html
share/doc/postgresql/html/sql-createcast.html
share/doc/postgresql/html/sql-createcollation.html
share/doc/postgresql/html/sql-createconversion.html
share/doc/postgresql/html/sql-createdatabase.html
share/doc/postgresql/html/sql-createdomain.html
share/doc/postgresql/html/sql-createextension.html
share/doc/postgresql/html/sql-createforeigndatawrapper.html
share/doc/postgresql/html/sql-createforeigntable.html
share/doc/postgresql/html/sql-createfunction.html
share/doc/postgresql/html/sql-creategroup.html
share/doc/postgresql/html/sql-createindex.html
share/doc/postgresql/html/sql-createlanguage.html
share/doc/postgresql/html/sql-createopclass.html
share/doc/postgresql/html/sql-createoperator.html
share/doc/postgresql/html/sql-createopfamily.html
share/doc/postgresql/html/sql-createrole.html
share/doc/postgresql/html/sql-createrule.html
share/doc/postgresql/html/sql-createschema.html
share/doc/postgresql/html/sql-createsequence.html
share/doc/postgresql/html/sql-createserver.html
share/doc/postgresql/html/sql-createtable.html
share/doc/postgresql/html/sql-createtableas.html
share/doc/postgresql/html/sql-createtablespace.html
share/doc/postgresql/html/sql-createtrigger.html
share/doc/postgresql/html/sql-createtsconfig.html
share/doc/postgresql/html/sql-createtsdictionary.html
share/doc/postgresql/html/sql-createtsparser.html
share/doc/postgresql/html/sql-createtstemplate.html
share/doc/postgresql/html/sql-createtype.html
share/doc/postgresql/html/sql-createuser.html
share/doc/postgresql/html/sql-createusermapping.html
share/doc/postgresql/html/sql-createview.html
share/doc/postgresql/html/sql-deallocate.html
share/doc/postgresql/html/sql-declare.html
share/doc/postgresql/html/sql-delete.html
share/doc/postgresql/html/sql-discard.html
share/doc/postgresql/html/sql-do.html
share/doc/postgresql/html/sql-drop-owned.html
share/doc/postgresql/html/sql-dropaggregate.html
share/doc/postgresql/html/sql-dropcast.html
share/doc/postgresql/html/sql-dropcollation.html
share/doc/postgresql/html/sql-dropconversion.html
share/doc/postgresql/html/sql-dropdatabase.html
share/doc/postgresql/html/sql-dropdomain.html
share/doc/postgresql/html/sql-dropextension.html
share/doc/postgresql/html/sql-dropforeigndatawrapper.html
share/doc/postgresql/html/sql-dropforeigntable.html
share/doc/postgresql/html/sql-dropfunction.html
share/doc/postgresql/html/sql-dropgroup.html
share/doc/postgresql/html/sql-dropindex.html
share/doc/postgresql/html/sql-droplanguage.html
share/doc/postgresql/html/sql-dropopclass.html
share/doc/postgresql/html/sql-dropoperator.html
share/doc/postgresql/html/sql-dropopfamily.html
share/doc/postgresql/html/sql-droprole.html
share/doc/postgresql/html/sql-droprule.html
share/doc/postgresql/html/sql-dropschema.html
share/doc/postgresql/html/sql-dropsequence.html
share/doc/postgresql/html/sql-dropserver.html
share/doc/postgresql/html/sql-droptable.html
share/doc/postgresql/html/sql-droptablespace.html
share/doc/postgresql/html/sql-droptrigger.html
share/doc/postgresql/html/sql-droptsconfig.html
share/doc/postgresql/html/sql-droptsdictionary.html
share/doc/postgresql/html/sql-droptsparser.html
share/doc/postgresql/html/sql-droptstemplate.html
share/doc/postgresql/html/sql-droptype.html
share/doc/postgresql/html/sql-dropuser.html
share/doc/postgresql/html/sql-dropusermapping.html
share/doc/postgresql/html/sql-dropview.html
share/doc/postgresql/html/sql-end.html
share/doc/postgresql/html/sql-execute.html
share/doc/postgresql/html/sql-explain.html
share/doc/postgresql/html/sql-expressions.html
share/doc/postgresql/html/sql-fetch.html
share/doc/postgresql/html/sql-grant.html
share/doc/postgresql/html/sql-insert.html
share/doc/postgresql/html/sql-keywords-appendix.html
share/doc/postgresql/html/sql-listen.html
share/doc/postgresql/html/sql-load.html
share/doc/postgresql/html/sql-lock.html
share/doc/postgresql/html/sql-move.html
share/doc/postgresql/html/sql-notify.html
share/doc/postgresql/html/sql-prepare-transaction.html
share/doc/postgresql/html/sql-prepare.html
share/doc/postgresql/html/sql-reassign-owned.html
share/doc/postgresql/html/sql-reindex.html
share/doc/postgresql/html/sql-release-savepoint.html
share/doc/postgresql/html/sql-reset.html
share/doc/postgresql/html/sql-revoke.html
share/doc/postgresql/html/sql-rollback-prepared.html
share/doc/postgresql/html/sql-rollback-to.html
share/doc/postgresql/html/sql-rollback.html
share/doc/postgresql/html/sql-savepoint.html
share/doc/postgresql/html/sql-security-label.html
share/doc/postgresql/html/sql-select.html
share/doc/postgresql/html/sql-selectinto.html
share/doc/postgresql/html/sql-set-constraints.html
share/doc/postgresql/html/sql-set-role.html
share/doc/postgresql/html/sql-set-session-authorization.html
share/doc/postgresql/html/sql-set-transaction.html
share/doc/postgresql/html/sql-set.html
share/doc/postgresql/html/sql-show.html
share/doc/postgresql/html/sql-start-transaction.html
share/doc/postgresql/html/sql-syntax-calling-funcs.html
share/doc/postgresql/html/sql-syntax-lexical.html
share/doc/postgresql/html/sql-syntax.html
share/doc/postgresql/html/sql-truncate.html
share/doc/postgresql/html/sql-unlisten.html
share/doc/postgresql/html/sql-update.html
share/doc/postgresql/html/sql-vacuum.html
share/doc/postgresql/html/sql-values.html
share/doc/postgresql/html/sql.html
share/doc/postgresql/html/ssh-tunnels.html
share/doc/postgresql/html/ssl-tcp.html
share/doc/postgresql/html/sslinfo.html
share/doc/postgresql/html/standby-settings.html
share/doc/postgresql/html/storage-file-layout.html
share/doc/postgresql/html/storage-fsm.html
share/doc/postgresql/html/storage-init.html
share/doc/postgresql/html/storage-page-layout.html
share/doc/postgresql/html/storage-toast.html
share/doc/postgresql/html/storage-vm.html
share/doc/postgresql/html/storage.html
share/doc/postgresql/html/stylesheet.css
share/doc/postgresql/html/supported-platforms.html
share/doc/postgresql/html/tablefunc.html
share/doc/postgresql/html/tcn.html
share/doc/postgresql/html/test-parser.html
share/doc/postgresql/html/textsearch-configuration.html
share/doc/postgresql/html/textsearch-controls.html
share/doc/postgresql/html/textsearch-debugging.html
share/doc/postgresql/html/textsearch-dictionaries.html
share/doc/postgresql/html/textsearch-features.html
share/doc/postgresql/html/textsearch-indexes.html
share/doc/postgresql/html/textsearch-intro.html
share/doc/postgresql/html/textsearch-limitations.html
share/doc/postgresql/html/textsearch-migration.html
share/doc/postgresql/html/textsearch-parsers.html
share/doc/postgresql/html/textsearch-psql.html
share/doc/postgresql/html/textsearch-tables.html
share/doc/postgresql/html/textsearch.html
share/doc/postgresql/html/transaction-iso.html
share/doc/postgresql/html/trigger-datachanges.html
share/doc/postgresql/html/trigger-definition.html
share/doc/postgresql/html/trigger-example.html
share/doc/postgresql/html/trigger-interface.html
share/doc/postgresql/html/triggers.html
share/doc/postgresql/html/tsearch2.html
share/doc/postgresql/html/tutorial-accessdb.html
share/doc/postgresql/html/tutorial-advanced-intro.html
share/doc/postgresql/html/tutorial-advanced.html
share/doc/postgresql/html/tutorial-agg.html
share/doc/postgresql/html/tutorial-arch.html
share/doc/postgresql/html/tutorial-concepts.html
share/doc/postgresql/html/tutorial-conclusion.html
share/doc/postgresql/html/tutorial-createdb.html
share/doc/postgresql/html/tutorial-delete.html
share/doc/postgresql/html/tutorial-fk.html
share/doc/postgresql/html/tutorial-inheritance.html
share/doc/postgresql/html/tutorial-install.html
share/doc/postgresql/html/tutorial-join.html
share/doc/postgresql/html/tutorial-populate.html
share/doc/postgresql/html/tutorial-select.html
share/doc/postgresql/html/tutorial-sql-intro.html
share/doc/postgresql/html/tutorial-sql.html
share/doc/postgresql/html/tutorial-start.html
share/doc/postgresql/html/tutorial-table.html
share/doc/postgresql/html/tutorial-transactions.html
share/doc/postgresql/html/tutorial-update.html
share/doc/postgresql/html/tutorial-views.html
share/doc/postgresql/html/tutorial-window.html
share/doc/postgresql/html/tutorial.html
share/doc/postgresql/html/typeconv-func.html
share/doc/postgresql/html/typeconv-oper.html
share/doc/postgresql/html/typeconv-overview.html
share/doc/postgresql/html/typeconv-query.html
share/doc/postgresql/html/typeconv-union-case.html
share/doc/postgresql/html/typeconv.html
share/doc/postgresql/html/unaccent.html
share/doc/postgresql/html/unsupported-features-sql-standard.html
share/doc/postgresql/html/upgrading.html
share/doc/postgresql/html/user-manag.html
share/doc/postgresql/html/using-explain.html
share/doc/postgresql/html/uuid-ossp.html
share/doc/postgresql/html/vacuumlo.html
share/doc/postgresql/html/view-pg-available-extension-versions.html
share/doc/postgresql/html/view-pg-available-extensions.html
share/doc/postgresql/html/view-pg-cursors.html
share/doc/postgresql/html/view-pg-group.html
share/doc/postgresql/html/view-pg-indexes.html
share/doc/postgresql/html/view-pg-locks.html
share/doc/postgresql/html/view-pg-prepared-statements.html
share/doc/postgresql/html/view-pg-prepared-xacts.html
share/doc/postgresql/html/view-pg-roles.html
share/doc/postgresql/html/view-pg-rules.html
share/doc/postgresql/html/view-pg-seclabels.html
share/doc/postgresql/html/view-pg-settings.html
share/doc/postgresql/html/view-pg-shadow.html
share/doc/postgresql/html/view-pg-stats.html
share/doc/postgresql/html/view-pg-tables.html
share/doc/postgresql/html/view-pg-timezone-abbrevs.html
share/doc/postgresql/html/view-pg-timezone-names.html
share/doc/postgresql/html/view-pg-user-mappings.html
share/doc/postgresql/html/view-pg-user.html
share/doc/postgresql/html/view-pg-views.html
share/doc/postgresql/html/views-overview.html
share/doc/postgresql/html/wal-async-commit.html
share/doc/postgresql/html/wal-configuration.html
share/doc/postgresql/html/wal-internals.html
share/doc/postgresql/html/wal-intro.html
share/doc/postgresql/html/wal-reliability.html
share/doc/postgresql/html/wal.html
share/doc/postgresql/html/warm-standby-failover.html
share/doc/postgresql/html/warm-standby.html
share/doc/postgresql/html/xaggr.html
share/doc/postgresql/html/xfunc-c.html
share/doc/postgresql/html/xfunc-internal.html
share/doc/postgresql/html/xfunc-overload.html
share/doc/postgresql/html/xfunc-pl.html
share/doc/postgresql/html/xfunc-sql.html
share/doc/postgresql/html/xfunc-volatility.html
share/doc/postgresql/html/xfunc.html
share/doc/postgresql/html/xindex.html
share/doc/postgresql/html/xml2.html
share/doc/postgresql/html/xoper-optimization.html
share/doc/postgresql/html/xoper.html
share/doc/postgresql/html/xplang-install.html
share/doc/postgresql/html/xplang.html
share/doc/postgresql/html/xtypes.html
Reference in a new issue Copy permalink