Version in base suite: 13.10-0+deb11u1 Version in overlay suite: 13.11-0+deb11u1 Base version: postgresql-13_13.11-0+deb11u1 Target version: postgresql-13_13.12-0+deb11u1 Base file: /srv/ftp-master.debian.org/ftp/pool/main/p/postgresql-13/postgresql-13_13.11-0+deb11u1.dsc Target file: /srv/ftp-master.debian.org/policy/pool/main/p/postgresql-13/postgresql-13_13.12-0+deb11u1.dsc .gitrevision | 2 configure | 24 configure.in | 5 contrib/fuzzystrmatch/expected/fuzzystrmatch.out | 6 contrib/fuzzystrmatch/fuzzystrmatch.c | 15 contrib/fuzzystrmatch/sql/fuzzystrmatch.sql | 1 contrib/hstore/Makefile | 2 contrib/hstore/expected/hstore_utf8.out | 36 contrib/hstore/expected/hstore_utf8_1.out | 8 contrib/hstore/hstore_io.c | 9 contrib/hstore/sql/hstore_utf8.sql | 19 contrib/intarray/_int_gist.c | 12 contrib/intarray/_intbig_gist.c | 3 contrib/intarray/expected/_int.out | 2 contrib/intarray/sql/_int.sql | 2 contrib/postgres_fdw/expected/postgres_fdw.out | 26 contrib/postgres_fdw/sql/postgres_fdw.sql | 3 debian/changelog | 23 doc/src/sgml/catalogs.sgml | 3 doc/src/sgml/custom-scan.sgml | 19 doc/src/sgml/func.sgml | 30 doc/src/sgml/history.sgml | 2 doc/src/sgml/html/acronyms.html | 6 doc/src/sgml/html/admin.html | 4 doc/src/sgml/html/adminpack.html | 4 doc/src/sgml/html/amcheck.html | 4 doc/src/sgml/html/app-clusterdb.html | 4 doc/src/sgml/html/app-createdb.html | 4 doc/src/sgml/html/app-createuser.html | 4 doc/src/sgml/html/app-dropdb.html | 4 doc/src/sgml/html/app-dropuser.html | 4 doc/src/sgml/html/app-ecpg.html | 4 doc/src/sgml/html/app-initdb.html | 4 doc/src/sgml/html/app-pg-ctl.html | 4 doc/src/sgml/html/app-pg-dumpall.html | 4 doc/src/sgml/html/app-pg-isready.html | 4 doc/src/sgml/html/app-pgbasebackup.html | 4 doc/src/sgml/html/app-pgchecksums.html | 4 doc/src/sgml/html/app-pgconfig.html | 4 doc/src/sgml/html/app-pgcontroldata.html | 4 doc/src/sgml/html/app-pgdump.html | 4 doc/src/sgml/html/app-pgreceivewal.html | 4 doc/src/sgml/html/app-pgreceivexlog.html | 6 doc/src/sgml/html/app-pgrecvlogical.html | 4 doc/src/sgml/html/app-pgresetwal.html | 4 doc/src/sgml/html/app-pgresetxlog.html | 6 doc/src/sgml/html/app-pgrestore.html | 4 doc/src/sgml/html/app-pgrewind.html | 4 doc/src/sgml/html/app-pgverifybackup.html | 4 doc/src/sgml/html/app-postgres.html | 4 doc/src/sgml/html/app-postmaster.html | 4 doc/src/sgml/html/app-psql.html | 6 doc/src/sgml/html/app-reindexdb.html | 4 doc/src/sgml/html/app-vacuumdb.html | 4 doc/src/sgml/html/appendix-obsolete.html | 4 doc/src/sgml/html/appendixes.html | 2 doc/src/sgml/html/applevel-consistency.html | 4 doc/src/sgml/html/arrays.html | 4 doc/src/sgml/html/auth-bsd.html | 4 doc/src/sgml/html/auth-cert.html | 4 doc/src/sgml/html/auth-delay.html | 4 doc/src/sgml/html/auth-ident.html | 4 doc/src/sgml/html/auth-ldap.html | 4 doc/src/sgml/html/auth-methods.html | 4 doc/src/sgml/html/auth-pam.html | 4 doc/src/sgml/html/auth-password.html | 4 doc/src/sgml/html/auth-peer.html | 4 doc/src/sgml/html/auth-pg-hba-conf.html | 4 doc/src/sgml/html/auth-radius.html | 4 doc/src/sgml/html/auth-trust.html | 4 doc/src/sgml/html/auth-username-maps.html | 4 doc/src/sgml/html/auto-explain.html | 4 doc/src/sgml/html/backup-dump.html | 4 doc/src/sgml/html/backup-file.html | 4 doc/src/sgml/html/backup-manifest-files.html | 4 doc/src/sgml/html/backup-manifest-format.html | 4 doc/src/sgml/html/backup-manifest-toplevel.html | 4 doc/src/sgml/html/backup-manifest-wal-ranges.html | 4 doc/src/sgml/html/backup.html | 4 doc/src/sgml/html/bgworker.html | 4 doc/src/sgml/html/biblio.html | 4 doc/src/sgml/html/bki-commands.html | 4 doc/src/sgml/html/bki-example.html | 4 doc/src/sgml/html/bki-format.html | 4 doc/src/sgml/html/bki-structure.html | 4 doc/src/sgml/html/bki.html | 4 doc/src/sgml/html/bloom.html | 4 doc/src/sgml/html/bookindex.html | 24 doc/src/sgml/html/brin-builtin-opclasses.html | 4 doc/src/sgml/html/brin-extensibility.html | 4 doc/src/sgml/html/brin-intro.html | 4 doc/src/sgml/html/brin.html | 2 doc/src/sgml/html/btree-behavior.html | 4 doc/src/sgml/html/btree-gin.html | 4 doc/src/sgml/html/btree-gist.html | 4 doc/src/sgml/html/btree-implementation.html | 4 doc/src/sgml/html/btree-intro.html | 4 doc/src/sgml/html/btree-support-funcs.html | 4 doc/src/sgml/html/btree.html | 2 doc/src/sgml/html/bug-reporting.html | 6 doc/src/sgml/html/catalog-pg-aggregate.html | 4 doc/src/sgml/html/catalog-pg-am.html | 4 doc/src/sgml/html/catalog-pg-amop.html | 4 doc/src/sgml/html/catalog-pg-amproc.html | 4 doc/src/sgml/html/catalog-pg-attrdef.html | 4 doc/src/sgml/html/catalog-pg-attribute.html | 4 doc/src/sgml/html/catalog-pg-auth-members.html | 4 doc/src/sgml/html/catalog-pg-authid.html | 4 doc/src/sgml/html/catalog-pg-cast.html | 4 doc/src/sgml/html/catalog-pg-class.html | 4 doc/src/sgml/html/catalog-pg-collation.html | 4 doc/src/sgml/html/catalog-pg-constraint.html | 4 doc/src/sgml/html/catalog-pg-conversion.html | 4 doc/src/sgml/html/catalog-pg-database.html | 7 doc/src/sgml/html/catalog-pg-db-role-setting.html | 4 doc/src/sgml/html/catalog-pg-default-acl.html | 4 doc/src/sgml/html/catalog-pg-depend.html | 4 doc/src/sgml/html/catalog-pg-description.html | 4 doc/src/sgml/html/catalog-pg-enum.html | 4 doc/src/sgml/html/catalog-pg-event-trigger.html | 4 doc/src/sgml/html/catalog-pg-extension.html | 4 doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html | 4 doc/src/sgml/html/catalog-pg-foreign-server.html | 4 doc/src/sgml/html/catalog-pg-foreign-table.html | 4 doc/src/sgml/html/catalog-pg-index.html | 4 doc/src/sgml/html/catalog-pg-inherits.html | 4 doc/src/sgml/html/catalog-pg-init-privs.html | 4 doc/src/sgml/html/catalog-pg-language.html | 4 doc/src/sgml/html/catalog-pg-largeobject-metadata.html | 4 doc/src/sgml/html/catalog-pg-largeobject.html | 4 doc/src/sgml/html/catalog-pg-namespace.html | 4 doc/src/sgml/html/catalog-pg-opclass.html | 4 doc/src/sgml/html/catalog-pg-operator.html | 4 doc/src/sgml/html/catalog-pg-opfamily.html | 4 doc/src/sgml/html/catalog-pg-partitioned-table.html | 4 doc/src/sgml/html/catalog-pg-policy.html | 4 doc/src/sgml/html/catalog-pg-proc.html | 4 doc/src/sgml/html/catalog-pg-publication-rel.html | 4 doc/src/sgml/html/catalog-pg-publication.html | 4 doc/src/sgml/html/catalog-pg-range.html | 4 doc/src/sgml/html/catalog-pg-replication-origin.html | 4 doc/src/sgml/html/catalog-pg-rewrite.html | 4 doc/src/sgml/html/catalog-pg-seclabel.html | 4 doc/src/sgml/html/catalog-pg-sequence.html | 4 doc/src/sgml/html/catalog-pg-shdepend.html | 4 doc/src/sgml/html/catalog-pg-shdescription.html | 4 doc/src/sgml/html/catalog-pg-shseclabel.html | 4 doc/src/sgml/html/catalog-pg-statistic-ext-data.html | 4 doc/src/sgml/html/catalog-pg-statistic-ext.html | 4 doc/src/sgml/html/catalog-pg-statistic.html | 4 doc/src/sgml/html/catalog-pg-subscription-rel.html | 4 doc/src/sgml/html/catalog-pg-subscription.html | 4 doc/src/sgml/html/catalog-pg-tablespace.html | 4 doc/src/sgml/html/catalog-pg-transform.html | 4 doc/src/sgml/html/catalog-pg-trigger.html | 4 doc/src/sgml/html/catalog-pg-ts-config-map.html | 4 doc/src/sgml/html/catalog-pg-ts-config.html | 4 doc/src/sgml/html/catalog-pg-ts-dict.html | 4 doc/src/sgml/html/catalog-pg-ts-parser.html | 4 doc/src/sgml/html/catalog-pg-ts-template.html | 4 doc/src/sgml/html/catalog-pg-type.html | 4 doc/src/sgml/html/catalog-pg-user-mapping.html | 4 doc/src/sgml/html/catalogs-overview.html | 4 doc/src/sgml/html/catalogs.html | 4 doc/src/sgml/html/charset.html | 4 doc/src/sgml/html/citext.html | 4 doc/src/sgml/html/client-authentication-problems.html | 4 doc/src/sgml/html/client-authentication.html | 4 doc/src/sgml/html/client-interfaces.html | 4 doc/src/sgml/html/collation.html | 4 doc/src/sgml/html/color-when.html | 4 doc/src/sgml/html/color-which.html | 4 doc/src/sgml/html/color.html | 4 doc/src/sgml/html/config-setting.html | 4 doc/src/sgml/html/connect-estab.html | 4 doc/src/sgml/html/continuous-archiving.html | 4 doc/src/sgml/html/contrib-dblink-build-sql-delete.html | 4 doc/src/sgml/html/contrib-dblink-build-sql-insert.html | 4 doc/src/sgml/html/contrib-dblink-build-sql-update.html | 4 doc/src/sgml/html/contrib-dblink-cancel-query.html | 4 doc/src/sgml/html/contrib-dblink-close.html | 4 doc/src/sgml/html/contrib-dblink-connect-u.html | 4 doc/src/sgml/html/contrib-dblink-connect.html | 4 doc/src/sgml/html/contrib-dblink-disconnect.html | 4 doc/src/sgml/html/contrib-dblink-error-message.html | 4 doc/src/sgml/html/contrib-dblink-exec.html | 4 doc/src/sgml/html/contrib-dblink-fetch.html | 4 doc/src/sgml/html/contrib-dblink-function.html | 4 doc/src/sgml/html/contrib-dblink-get-connections.html | 4 doc/src/sgml/html/contrib-dblink-get-notify.html | 4 doc/src/sgml/html/contrib-dblink-get-pkey.html | 4 doc/src/sgml/html/contrib-dblink-get-result.html | 4 doc/src/sgml/html/contrib-dblink-is-busy.html | 4 doc/src/sgml/html/contrib-dblink-open.html | 4 doc/src/sgml/html/contrib-dblink-send-query.html | 4 doc/src/sgml/html/contrib-prog-client.html | 4 doc/src/sgml/html/contrib-prog-server.html | 4 doc/src/sgml/html/contrib-prog.html | 4 doc/src/sgml/html/contrib-spi.html | 4 doc/src/sgml/html/contrib.html | 4 doc/src/sgml/html/creating-cluster.html | 4 doc/src/sgml/html/cube.html | 4 doc/src/sgml/html/custom-scan-execution.html | 4 doc/src/sgml/html/custom-scan-path.html | 21 doc/src/sgml/html/custom-scan-plan.html | 4 doc/src/sgml/html/custom-scan.html | 4 doc/src/sgml/html/database-roles.html | 4 doc/src/sgml/html/datatype-binary.html | 4 doc/src/sgml/html/datatype-bit.html | 4 doc/src/sgml/html/datatype-boolean.html | 4 doc/src/sgml/html/datatype-character.html | 4 doc/src/sgml/html/datatype-datetime.html | 4 doc/src/sgml/html/datatype-enum.html | 4 doc/src/sgml/html/datatype-geometric.html | 4 doc/src/sgml/html/datatype-json.html | 4 doc/src/sgml/html/datatype-money.html | 4 doc/src/sgml/html/datatype-net-types.html | 4 doc/src/sgml/html/datatype-numeric.html | 4 doc/src/sgml/html/datatype-oid.html | 4 doc/src/sgml/html/datatype-pg-lsn.html | 4 doc/src/sgml/html/datatype-pseudo.html | 4 doc/src/sgml/html/datatype-textsearch.html | 4 doc/src/sgml/html/datatype-uuid.html | 4 doc/src/sgml/html/datatype-xml.html | 4 doc/src/sgml/html/datatype.html | 4 doc/src/sgml/html/datetime-appendix.html | 4 doc/src/sgml/html/datetime-config-files.html | 4 doc/src/sgml/html/datetime-input-rules.html | 4 doc/src/sgml/html/datetime-invalid-input.html | 4 doc/src/sgml/html/datetime-julian-dates.html | 4 doc/src/sgml/html/datetime-keywords.html | 4 doc/src/sgml/html/datetime-posix-timezone-specs.html | 4 doc/src/sgml/html/datetime-units-history.html | 4 doc/src/sgml/html/dblink.html | 4 doc/src/sgml/html/ddl-alter.html | 4 doc/src/sgml/html/ddl-basics.html | 4 doc/src/sgml/html/ddl-constraints.html | 4 doc/src/sgml/html/ddl-default.html | 4 doc/src/sgml/html/ddl-depend.html | 4 doc/src/sgml/html/ddl-foreign-data.html | 4 doc/src/sgml/html/ddl-generated-columns.html | 4 doc/src/sgml/html/ddl-inherit.html | 4 doc/src/sgml/html/ddl-others.html | 4 doc/src/sgml/html/ddl-partitioning.html | 4 doc/src/sgml/html/ddl-priv.html | 4 doc/src/sgml/html/ddl-rowsecurity.html | 4 doc/src/sgml/html/ddl-schemas.html | 4 doc/src/sgml/html/ddl-system-columns.html | 4 doc/src/sgml/html/ddl.html | 4 doc/src/sgml/html/default-roles.html | 4 doc/src/sgml/html/dict-int.html | 4 doc/src/sgml/html/dict-xsyn.html | 4 doc/src/sgml/html/different-replication-solutions.html | 4 doc/src/sgml/html/disk-full.html | 4 doc/src/sgml/html/disk-usage.html | 4 doc/src/sgml/html/diskusage.html | 4 doc/src/sgml/html/dml-delete.html | 4 doc/src/sgml/html/dml-insert.html | 4 doc/src/sgml/html/dml-returning.html | 4 doc/src/sgml/html/dml-update.html | 4 doc/src/sgml/html/dml.html | 4 doc/src/sgml/html/docguide-authoring.html | 4 doc/src/sgml/html/docguide-build.html | 4 doc/src/sgml/html/docguide-docbook.html | 4 doc/src/sgml/html/docguide-style.html | 4 doc/src/sgml/html/docguide-toolsets.html | 4 doc/src/sgml/html/docguide.html | 4 doc/src/sgml/html/domains.html | 4 doc/src/sgml/html/dynamic-trace.html | 4 doc/src/sgml/html/earthdistance.html | 4 doc/src/sgml/html/ecpg-commands.html | 4 doc/src/sgml/html/ecpg-concept.html | 4 doc/src/sgml/html/ecpg-connect.html | 4 doc/src/sgml/html/ecpg-cpp.html | 4 doc/src/sgml/html/ecpg-descriptors.html | 4 doc/src/sgml/html/ecpg-develop.html | 4 doc/src/sgml/html/ecpg-dynamic.html | 4 doc/src/sgml/html/ecpg-errors.html | 4 doc/src/sgml/html/ecpg-informix-compat.html | 4 doc/src/sgml/html/ecpg-library.html | 4 doc/src/sgml/html/ecpg-lo.html | 4 doc/src/sgml/html/ecpg-oracle-compat.html | 4 doc/src/sgml/html/ecpg-pgtypes.html | 4 doc/src/sgml/html/ecpg-preproc.html | 4 doc/src/sgml/html/ecpg-process.html | 4 doc/src/sgml/html/ecpg-sql-allocate-descriptor.html | 4 doc/src/sgml/html/ecpg-sql-commands.html | 4 doc/src/sgml/html/ecpg-sql-connect.html | 4 doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html | 4 doc/src/sgml/html/ecpg-sql-declare.html | 4 doc/src/sgml/html/ecpg-sql-describe.html | 4 doc/src/sgml/html/ecpg-sql-disconnect.html | 4 doc/src/sgml/html/ecpg-sql-execute-immediate.html | 4 doc/src/sgml/html/ecpg-sql-get-descriptor.html | 4 doc/src/sgml/html/ecpg-sql-open.html | 4 doc/src/sgml/html/ecpg-sql-prepare.html | 4 doc/src/sgml/html/ecpg-sql-set-autocommit.html | 4 doc/src/sgml/html/ecpg-sql-set-connection.html | 4 doc/src/sgml/html/ecpg-sql-set-descriptor.html | 4 doc/src/sgml/html/ecpg-sql-type.html | 4 doc/src/sgml/html/ecpg-sql-var.html | 4 doc/src/sgml/html/ecpg-sql-whenever.html | 4 doc/src/sgml/html/ecpg-variables.html | 4 doc/src/sgml/html/ecpg.html | 4 doc/src/sgml/html/encryption-options.html | 4 doc/src/sgml/html/errcodes-appendix.html | 6 doc/src/sgml/html/error-message-reporting.html | 4 doc/src/sgml/html/error-style-guide.html | 4 doc/src/sgml/html/event-log-registration.html | 4 doc/src/sgml/html/event-trigger-definition.html | 4 doc/src/sgml/html/event-trigger-example.html | 4 doc/src/sgml/html/event-trigger-interface.html | 4 doc/src/sgml/html/event-trigger-matrix.html | 4 doc/src/sgml/html/event-trigger-table-rewrite-example.html | 4 doc/src/sgml/html/event-triggers.html | 4 doc/src/sgml/html/executor.html | 4 doc/src/sgml/html/explicit-joins.html | 4 doc/src/sgml/html/explicit-locking.html | 4 doc/src/sgml/html/extend-extensions.html | 4 doc/src/sgml/html/extend-how.html | 4 doc/src/sgml/html/extend-pgxs.html | 4 doc/src/sgml/html/extend-type-system.html | 4 doc/src/sgml/html/extend.html | 4 doc/src/sgml/html/external-admin-tools.html | 4 doc/src/sgml/html/external-extensions.html | 4 doc/src/sgml/html/external-interfaces.html | 4 doc/src/sgml/html/external-pl.html | 4 doc/src/sgml/html/external-projects.html | 4 doc/src/sgml/html/fdw-callbacks.html | 4 doc/src/sgml/html/fdw-functions.html | 4 doc/src/sgml/html/fdw-helpers.html | 4 doc/src/sgml/html/fdw-planning.html | 4 doc/src/sgml/html/fdw-row-locking.html | 4 doc/src/sgml/html/fdwhandler.html | 4 doc/src/sgml/html/features-sql-standard.html | 4 doc/src/sgml/html/features.html | 4 doc/src/sgml/html/file-fdw.html | 4 doc/src/sgml/html/functions-admin.html | 4 doc/src/sgml/html/functions-aggregate.html | 4 doc/src/sgml/html/functions-array.html | 4 doc/src/sgml/html/functions-binarystring.html | 4 doc/src/sgml/html/functions-bitstring.html | 4 doc/src/sgml/html/functions-comparison.html | 4 doc/src/sgml/html/functions-comparisons.html | 32 doc/src/sgml/html/functions-conditional.html | 4 doc/src/sgml/html/functions-datetime.html | 4 doc/src/sgml/html/functions-enum.html | 4 doc/src/sgml/html/functions-event-triggers.html | 4 doc/src/sgml/html/functions-formatting.html | 4 doc/src/sgml/html/functions-geometry.html | 4 doc/src/sgml/html/functions-info.html | 4 doc/src/sgml/html/functions-json.html | 4 doc/src/sgml/html/functions-logical.html | 4 doc/src/sgml/html/functions-matching.html | 4 doc/src/sgml/html/functions-math.html | 4 doc/src/sgml/html/functions-net.html | 4 doc/src/sgml/html/functions-range.html | 4 doc/src/sgml/html/functions-sequence.html | 4 doc/src/sgml/html/functions-srf.html | 4 doc/src/sgml/html/functions-statistics.html | 4 doc/src/sgml/html/functions-string.html | 4 doc/src/sgml/html/functions-subquery.html | 4 doc/src/sgml/html/functions-textsearch.html | 4 doc/src/sgml/html/functions-trigger.html | 4 doc/src/sgml/html/functions-uuid.html | 4 doc/src/sgml/html/functions-window.html | 4 doc/src/sgml/html/functions-xml.html | 4 doc/src/sgml/html/functions.html | 4 doc/src/sgml/html/fuzzystrmatch.html | 4 doc/src/sgml/html/generic-wal.html | 4 doc/src/sgml/html/geqo-biblio.html | 4 doc/src/sgml/html/geqo-intro.html | 4 doc/src/sgml/html/geqo-intro2.html | 4 doc/src/sgml/html/geqo-pg-intro.html | 4 doc/src/sgml/html/geqo.html | 4 doc/src/sgml/html/gin-builtin-opclasses.html | 4 doc/src/sgml/html/gin-examples.html | 4 doc/src/sgml/html/gin-extensibility.html | 4 doc/src/sgml/html/gin-implementation.html | 4 doc/src/sgml/html/gin-intro.html | 4 doc/src/sgml/html/gin-limit.html | 4 doc/src/sgml/html/gin-tips.html | 4 doc/src/sgml/html/gin.html | 2 doc/src/sgml/html/gist-builtin-opclasses.html | 4 doc/src/sgml/html/gist-examples.html | 4 doc/src/sgml/html/gist-extensibility.html | 4 doc/src/sgml/html/gist-implementation.html | 4 doc/src/sgml/html/gist-intro.html | 4 doc/src/sgml/html/gist.html | 2 doc/src/sgml/html/git.html | 4 doc/src/sgml/html/glossary.html | 4 doc/src/sgml/html/gssapi-auth.html | 4 doc/src/sgml/html/gssapi-enc.html | 4 doc/src/sgml/html/hash-implementation.html | 4 doc/src/sgml/html/hash-index.html | 2 doc/src/sgml/html/hash-intro.html | 4 doc/src/sgml/html/high-availability.html | 4 doc/src/sgml/html/history.html | 6 doc/src/sgml/html/hot-standby.html | 4 doc/src/sgml/html/how-parallel-query-works.html | 4 doc/src/sgml/html/hstore.html | 4 doc/src/sgml/html/index-api.html | 4 doc/src/sgml/html/index-cost-estimation.html | 4 doc/src/sgml/html/index-functions.html | 4 doc/src/sgml/html/index-locking.html | 4 doc/src/sgml/html/index-scanning.html | 4 doc/src/sgml/html/index-unique-checks.html | 4 doc/src/sgml/html/index.html | 2 doc/src/sgml/html/indexam.html | 4 doc/src/sgml/html/indexes-bitmap-scans.html | 4 doc/src/sgml/html/indexes-collations.html | 4 doc/src/sgml/html/indexes-examine.html | 4 doc/src/sgml/html/indexes-expressional.html | 4 doc/src/sgml/html/indexes-index-only-scans.html | 4 doc/src/sgml/html/indexes-intro.html | 4 doc/src/sgml/html/indexes-multicolumn.html | 4 doc/src/sgml/html/indexes-opclass.html | 4 doc/src/sgml/html/indexes-ordering.html | 4 doc/src/sgml/html/indexes-partial.html | 4 doc/src/sgml/html/indexes-types.html | 4 doc/src/sgml/html/indexes-unique.html | 4 doc/src/sgml/html/indexes.html | 4 doc/src/sgml/html/information-schema.html | 4 doc/src/sgml/html/infoschema-administrable-role-authorizations.html | 4 doc/src/sgml/html/infoschema-applicable-roles.html | 4 doc/src/sgml/html/infoschema-attributes.html | 4 doc/src/sgml/html/infoschema-character-sets.html | 4 doc/src/sgml/html/infoschema-check-constraint-routine-usage.html | 4 doc/src/sgml/html/infoschema-check-constraints.html | 4 doc/src/sgml/html/infoschema-collation-character-set-applicab.html | 4 doc/src/sgml/html/infoschema-collations.html | 4 doc/src/sgml/html/infoschema-column-column-usage.html | 4 doc/src/sgml/html/infoschema-column-domain-usage.html | 4 doc/src/sgml/html/infoschema-column-options.html | 4 doc/src/sgml/html/infoschema-column-privileges.html | 4 doc/src/sgml/html/infoschema-column-udt-usage.html | 4 doc/src/sgml/html/infoschema-columns.html | 4 doc/src/sgml/html/infoschema-constraint-column-usage.html | 4 doc/src/sgml/html/infoschema-constraint-table-usage.html | 4 doc/src/sgml/html/infoschema-data-type-privileges.html | 4 doc/src/sgml/html/infoschema-datatypes.html | 4 doc/src/sgml/html/infoschema-domain-constraints.html | 4 doc/src/sgml/html/infoschema-domain-udt-usage.html | 4 doc/src/sgml/html/infoschema-domains.html | 4 doc/src/sgml/html/infoschema-element-types.html | 4 doc/src/sgml/html/infoschema-enabled-roles.html | 4 doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html | 4 doc/src/sgml/html/infoschema-foreign-data-wrappers.html | 4 doc/src/sgml/html/infoschema-foreign-server-options.html | 4 doc/src/sgml/html/infoschema-foreign-servers.html | 4 doc/src/sgml/html/infoschema-foreign-table-options.html | 4 doc/src/sgml/html/infoschema-foreign-tables.html | 4 doc/src/sgml/html/infoschema-information-schema-catalog-name.html | 4 doc/src/sgml/html/infoschema-key-column-usage.html | 4 doc/src/sgml/html/infoschema-parameters.html | 4 doc/src/sgml/html/infoschema-referential-constraints.html | 4 doc/src/sgml/html/infoschema-role-column-grants.html | 4 doc/src/sgml/html/infoschema-role-routine-grants.html | 4 doc/src/sgml/html/infoschema-role-table-grants.html | 4 doc/src/sgml/html/infoschema-role-udt-grants.html | 4 doc/src/sgml/html/infoschema-role-usage-grants.html | 4 doc/src/sgml/html/infoschema-routine-privileges.html | 4 doc/src/sgml/html/infoschema-routines.html | 4 doc/src/sgml/html/infoschema-schema.html | 4 doc/src/sgml/html/infoschema-schemata.html | 4 doc/src/sgml/html/infoschema-sequences.html | 4 doc/src/sgml/html/infoschema-sql-features.html | 4 doc/src/sgml/html/infoschema-sql-implementation-info.html | 4 doc/src/sgml/html/infoschema-sql-parts.html | 4 doc/src/sgml/html/infoschema-sql-sizing.html | 4 doc/src/sgml/html/infoschema-table-constraints.html | 4 doc/src/sgml/html/infoschema-table-privileges.html | 4 doc/src/sgml/html/infoschema-tables.html | 4 doc/src/sgml/html/infoschema-transforms.html | 4 doc/src/sgml/html/infoschema-triggered-update-columns.html | 4 doc/src/sgml/html/infoschema-triggers.html | 4 doc/src/sgml/html/infoschema-udt-privileges.html | 4 doc/src/sgml/html/infoschema-usage-privileges.html | 4 doc/src/sgml/html/infoschema-user-defined-types.html | 4 doc/src/sgml/html/infoschema-user-mapping-options.html | 4 doc/src/sgml/html/infoschema-user-mappings.html | 4 doc/src/sgml/html/infoschema-view-column-usage.html | 4 doc/src/sgml/html/infoschema-view-routine-usage.html | 4 doc/src/sgml/html/infoschema-view-table-usage.html | 4 doc/src/sgml/html/infoschema-views.html | 4 doc/src/sgml/html/install-getsource.html | 16 doc/src/sgml/html/install-post.html | 4 doc/src/sgml/html/install-procedure.html | 4 doc/src/sgml/html/install-requirements.html | 4 doc/src/sgml/html/install-short.html | 4 doc/src/sgml/html/install-windows-full.html | 4 doc/src/sgml/html/install-windows.html | 4 doc/src/sgml/html/installation-platform-notes.html | 4 doc/src/sgml/html/installation.html | 4 doc/src/sgml/html/intagg.html | 4 doc/src/sgml/html/intarray.html | 4 doc/src/sgml/html/internals.html | 4 doc/src/sgml/html/intro-whatis.html | 4 doc/src/sgml/html/isn.html | 4 doc/src/sgml/html/jit-configuration.html | 4 doc/src/sgml/html/jit-decision.html | 4 doc/src/sgml/html/jit-extensibility.html | 4 doc/src/sgml/html/jit-reason.html | 4 doc/src/sgml/html/jit.html | 4 doc/src/sgml/html/kernel-resources.html | 4 doc/src/sgml/html/largeobjects.html | 4 doc/src/sgml/html/libpq-async.html | 4 doc/src/sgml/html/libpq-build.html | 4 doc/src/sgml/html/libpq-cancel.html | 4 doc/src/sgml/html/libpq-connect.html | 4 doc/src/sgml/html/libpq-control.html | 4 doc/src/sgml/html/libpq-copy.html | 4 doc/src/sgml/html/libpq-envars.html | 4 doc/src/sgml/html/libpq-events.html | 4 doc/src/sgml/html/libpq-example.html | 4 doc/src/sgml/html/libpq-exec.html | 4 doc/src/sgml/html/libpq-fastpath.html | 4 doc/src/sgml/html/libpq-ldap.html | 4 doc/src/sgml/html/libpq-misc.html | 4 doc/src/sgml/html/libpq-notice-processing.html | 4 doc/src/sgml/html/libpq-notify.html | 4 doc/src/sgml/html/libpq-pgpass.html | 4 doc/src/sgml/html/libpq-pgservice.html | 4 doc/src/sgml/html/libpq-single-row-mode.html | 4 doc/src/sgml/html/libpq-ssl.html | 4 doc/src/sgml/html/libpq-status.html | 4 doc/src/sgml/html/libpq-threading.html | 4 doc/src/sgml/html/libpq.html | 4 doc/src/sgml/html/limits.html | 4 doc/src/sgml/html/lo-examplesect.html | 4 doc/src/sgml/html/lo-funcs.html | 4 doc/src/sgml/html/lo-implementation.html | 4 doc/src/sgml/html/lo-interfaces.html | 4 doc/src/sgml/html/lo-intro.html | 4 doc/src/sgml/html/lo.html | 4 doc/src/sgml/html/locale.html | 4 doc/src/sgml/html/locking-indexes.html | 4 doc/src/sgml/html/log-shipping-alternative.html | 4 doc/src/sgml/html/logfile-maintenance.html | 4 doc/src/sgml/html/logical-replication-architecture.html | 14 doc/src/sgml/html/logical-replication-config.html | 4 doc/src/sgml/html/logical-replication-conflicts.html | 4 doc/src/sgml/html/logical-replication-monitoring.html | 4 doc/src/sgml/html/logical-replication-publication.html | 4 doc/src/sgml/html/logical-replication-quick-setup.html | 4 doc/src/sgml/html/logical-replication-restrictions.html | 4 doc/src/sgml/html/logical-replication-security.html | 4 doc/src/sgml/html/logical-replication-subscription.html | 4 doc/src/sgml/html/logical-replication.html | 4 doc/src/sgml/html/logicaldecoding-catalogs.html | 4 doc/src/sgml/html/logicaldecoding-example.html | 4 doc/src/sgml/html/logicaldecoding-explanation.html | 4 doc/src/sgml/html/logicaldecoding-output-plugin.html | 4 doc/src/sgml/html/logicaldecoding-sql.html | 4 doc/src/sgml/html/logicaldecoding-synchronous.html | 4 doc/src/sgml/html/logicaldecoding-walsender.html | 4 doc/src/sgml/html/logicaldecoding-writer.html | 4 doc/src/sgml/html/logicaldecoding.html | 4 doc/src/sgml/html/ltree.html | 4 doc/src/sgml/html/maintenance.html | 4 doc/src/sgml/html/manage-ag-config.html | 4 doc/src/sgml/html/manage-ag-createdb.html | 4 doc/src/sgml/html/manage-ag-dropdb.html | 4 doc/src/sgml/html/manage-ag-overview.html | 4 doc/src/sgml/html/manage-ag-tablespaces.html | 4 doc/src/sgml/html/manage-ag-templatedbs.html | 4 doc/src/sgml/html/managing-databases.html | 4 doc/src/sgml/html/monitoring-locks.html | 4 doc/src/sgml/html/monitoring-ps.html | 4 doc/src/sgml/html/monitoring-stats.html | 4 doc/src/sgml/html/monitoring.html | 4 doc/src/sgml/html/multibyte.html | 4 doc/src/sgml/html/multivariate-statistics-examples.html | 4 doc/src/sgml/html/mvcc-caveats.html | 4 doc/src/sgml/html/mvcc-intro.html | 4 doc/src/sgml/html/mvcc.html | 4 doc/src/sgml/html/nls-programmer.html | 4 doc/src/sgml/html/nls-translator.html | 4 doc/src/sgml/html/nls.html | 2 doc/src/sgml/html/non-durability.html | 4 doc/src/sgml/html/notation.html | 4 doc/src/sgml/html/oid2name.html | 4 doc/src/sgml/html/overview.html | 4 doc/src/sgml/html/pageinspect.html | 4 doc/src/sgml/html/parallel-plans.html | 4 doc/src/sgml/html/parallel-query.html | 4 doc/src/sgml/html/parallel-safety.html | 4 doc/src/sgml/html/parser-stage.html | 4 doc/src/sgml/html/passwordcheck.html | 4 doc/src/sgml/html/performance-tips.html | 4 doc/src/sgml/html/perm-functions.html | 4 doc/src/sgml/html/pgarchivecleanup.html | 4 doc/src/sgml/html/pgbench.html | 4 doc/src/sgml/html/pgbuffercache.html | 4 doc/src/sgml/html/pgcrypto.html | 4 doc/src/sgml/html/pgfreespacemap.html | 4 doc/src/sgml/html/pgprewarm.html | 4 doc/src/sgml/html/pgrowlocks.html | 4 doc/src/sgml/html/pgstandby.html | 4 doc/src/sgml/html/pgstatstatements.html | 4 doc/src/sgml/html/pgstattuple.html | 4 doc/src/sgml/html/pgtestfsync.html | 4 doc/src/sgml/html/pgtesttiming.html | 4 doc/src/sgml/html/pgtrgm.html | 4 doc/src/sgml/html/pgupgrade.html | 4 doc/src/sgml/html/pgvisibility.html | 4 doc/src/sgml/html/pgwaldump.html | 4 doc/src/sgml/html/pgxlogdump.html | 6 doc/src/sgml/html/planner-optimizer.html | 4 doc/src/sgml/html/planner-stats-details.html | 4 doc/src/sgml/html/planner-stats-security.html | 4 doc/src/sgml/html/planner-stats.html | 4 doc/src/sgml/html/plhandler.html | 4 doc/src/sgml/html/plperl-builtins.html | 4 doc/src/sgml/html/plperl-data.html | 4 doc/src/sgml/html/plperl-event-triggers.html | 4 doc/src/sgml/html/plperl-funcs.html | 4 doc/src/sgml/html/plperl-global.html | 4 doc/src/sgml/html/plperl-triggers.html | 4 doc/src/sgml/html/plperl-trusted.html | 4 doc/src/sgml/html/plperl-under-the-hood.html | 4 doc/src/sgml/html/plperl.html | 4 doc/src/sgml/html/plpgsql-control-structures.html | 4 doc/src/sgml/html/plpgsql-cursors.html | 4 doc/src/sgml/html/plpgsql-declarations.html | 4 doc/src/sgml/html/plpgsql-development-tips.html | 4 doc/src/sgml/html/plpgsql-errors-and-messages.html | 4 doc/src/sgml/html/plpgsql-expressions.html | 4 doc/src/sgml/html/plpgsql-implementation.html | 4 doc/src/sgml/html/plpgsql-overview.html | 4 doc/src/sgml/html/plpgsql-porting.html | 4 doc/src/sgml/html/plpgsql-statements.html | 4 doc/src/sgml/html/plpgsql-structure.html | 4 doc/src/sgml/html/plpgsql-transactions.html | 4 doc/src/sgml/html/plpgsql-trigger.html | 4 doc/src/sgml/html/plpgsql.html | 2 doc/src/sgml/html/plpython-data.html | 4 doc/src/sgml/html/plpython-database.html | 4 doc/src/sgml/html/plpython-do.html | 4 doc/src/sgml/html/plpython-envar.html | 4 doc/src/sgml/html/plpython-funcs.html | 4 doc/src/sgml/html/plpython-python23.html | 4 doc/src/sgml/html/plpython-sharing.html | 4 doc/src/sgml/html/plpython-subtransaction.html | 4 doc/src/sgml/html/plpython-transactions.html | 4 doc/src/sgml/html/plpython-trigger.html | 4 doc/src/sgml/html/plpython-util.html | 4 doc/src/sgml/html/plpython.html | 4 doc/src/sgml/html/pltcl-config.html | 4 doc/src/sgml/html/pltcl-data.html | 4 doc/src/sgml/html/pltcl-dbaccess.html | 4 doc/src/sgml/html/pltcl-error-handling.html | 4 doc/src/sgml/html/pltcl-event-trigger.html | 4 doc/src/sgml/html/pltcl-functions.html | 4 doc/src/sgml/html/pltcl-global.html | 4 doc/src/sgml/html/pltcl-overview.html | 4 doc/src/sgml/html/pltcl-procnames.html | 4 doc/src/sgml/html/pltcl-subtransactions.html | 4 doc/src/sgml/html/pltcl-transactions.html | 4 doc/src/sgml/html/pltcl-trigger.html | 4 doc/src/sgml/html/pltcl.html | 4 doc/src/sgml/html/populate.html | 4 doc/src/sgml/html/postgres-fdw.html | 4 doc/src/sgml/html/postgres-user.html | 4 doc/src/sgml/html/preface.html | 4 doc/src/sgml/html/preventing-server-spoofing.html | 4 doc/src/sgml/html/progress-reporting.html | 4 doc/src/sgml/html/protocol-changes.html | 4 doc/src/sgml/html/protocol-error-fields.html | 4 doc/src/sgml/html/protocol-flow.html | 4 doc/src/sgml/html/protocol-logical-replication.html | 4 doc/src/sgml/html/protocol-logicalrep-message-formats.html | 4 doc/src/sgml/html/protocol-message-formats.html | 4 doc/src/sgml/html/protocol-message-types.html | 4 doc/src/sgml/html/protocol-overview.html | 4 doc/src/sgml/html/protocol-replication.html | 4 doc/src/sgml/html/protocol.html | 4 doc/src/sgml/html/queries-limit.html | 4 doc/src/sgml/html/queries-order.html | 4 doc/src/sgml/html/queries-overview.html | 4 doc/src/sgml/html/queries-select-lists.html | 4 doc/src/sgml/html/queries-table-expressions.html | 6 doc/src/sgml/html/queries-union.html | 4 doc/src/sgml/html/queries-values.html | 4 doc/src/sgml/html/queries-with.html | 4 doc/src/sgml/html/queries.html | 4 doc/src/sgml/html/query-path.html | 4 doc/src/sgml/html/querytree.html | 4 doc/src/sgml/html/rangetypes.html | 4 doc/src/sgml/html/recovery-config.html | 6 doc/src/sgml/html/reference-client.html | 4 doc/src/sgml/html/reference-server.html | 4 doc/src/sgml/html/reference.html | 4 doc/src/sgml/html/regress-coverage.html | 4 doc/src/sgml/html/regress-evaluation.html | 4 doc/src/sgml/html/regress-run.html | 4 doc/src/sgml/html/regress-tap.html | 4 doc/src/sgml/html/regress-variant.html | 4 doc/src/sgml/html/regress.html | 4 doc/src/sgml/html/release-13-1.html | 10 doc/src/sgml/html/release-13-10.html | 12 doc/src/sgml/html/release-13-11.html | 12 doc/src/sgml/html/release-13-12.html | 267 ++ doc/src/sgml/html/release-13-2.html | 10 doc/src/sgml/html/release-13-3.html | 12 doc/src/sgml/html/release-13-4.html | 12 doc/src/sgml/html/release-13-5.html | 12 doc/src/sgml/html/release-13-6.html | 12 doc/src/sgml/html/release-13-7.html | 12 doc/src/sgml/html/release-13-8.html | 12 doc/src/sgml/html/release-13-9.html | 12 doc/src/sgml/html/release-13.html | 52 doc/src/sgml/html/release-prior.html | 4 doc/src/sgml/html/release.html | 4 doc/src/sgml/html/replication-origins.html | 4 doc/src/sgml/html/resources.html | 4 doc/src/sgml/html/role-attributes.html | 4 doc/src/sgml/html/role-membership.html | 4 doc/src/sgml/html/role-removal.html | 4 doc/src/sgml/html/routine-reindex.html | 4 doc/src/sgml/html/routine-vacuuming.html | 4 doc/src/sgml/html/row-estimation-examples.html | 4 doc/src/sgml/html/rowtypes.html | 4 doc/src/sgml/html/rule-system.html | 4 doc/src/sgml/html/rules-materializedviews.html | 4 doc/src/sgml/html/rules-privileges.html | 4 doc/src/sgml/html/rules-status.html | 4 doc/src/sgml/html/rules-triggers.html | 4 doc/src/sgml/html/rules-update.html | 4 doc/src/sgml/html/rules-views.html | 4 doc/src/sgml/html/rules.html | 4 doc/src/sgml/html/runtime-config-autovacuum.html | 4 doc/src/sgml/html/runtime-config-client.html | 4 doc/src/sgml/html/runtime-config-compatible.html | 4 doc/src/sgml/html/runtime-config-connection.html | 4 doc/src/sgml/html/runtime-config-custom.html | 4 doc/src/sgml/html/runtime-config-developer.html | 4 doc/src/sgml/html/runtime-config-error-handling.html | 4 doc/src/sgml/html/runtime-config-file-locations.html | 4 doc/src/sgml/html/runtime-config-locks.html | 4 doc/src/sgml/html/runtime-config-logging.html | 4 doc/src/sgml/html/runtime-config-preset.html | 4 doc/src/sgml/html/runtime-config-query.html | 4 doc/src/sgml/html/runtime-config-replication.html | 4 doc/src/sgml/html/runtime-config-resource.html | 4 doc/src/sgml/html/runtime-config-short.html | 4 doc/src/sgml/html/runtime-config-statistics.html | 4 doc/src/sgml/html/runtime-config-wal.html | 4 doc/src/sgml/html/runtime-config.html | 4 doc/src/sgml/html/runtime.html | 4 doc/src/sgml/html/sasl-authentication.html | 4 doc/src/sgml/html/seg.html | 4 doc/src/sgml/html/sepgsql.html | 4 doc/src/sgml/html/server-programming.html | 4 doc/src/sgml/html/server-shutdown.html | 4 doc/src/sgml/html/server-start.html | 4 doc/src/sgml/html/source-conventions.html | 4 doc/src/sgml/html/source-format.html | 4 doc/src/sgml/html/source.html | 2 doc/src/sgml/html/sourcerepo.html | 4 doc/src/sgml/html/spgist-builtin-opclasses.html | 4 doc/src/sgml/html/spgist-examples.html | 4 doc/src/sgml/html/spgist-extensibility.html | 4 doc/src/sgml/html/spgist-implementation.html | 4 doc/src/sgml/html/spgist-intro.html | 4 doc/src/sgml/html/spgist.html | 2 doc/src/sgml/html/spi-examples.html | 52 doc/src/sgml/html/spi-interface-support.html | 4 doc/src/sgml/html/spi-interface.html | 4 doc/src/sgml/html/spi-memory.html | 4 doc/src/sgml/html/spi-realloc.html | 4 doc/src/sgml/html/spi-spi-commit.html | 4 doc/src/sgml/html/spi-spi-connect.html | 4 doc/src/sgml/html/spi-spi-copytuple.html | 4 doc/src/sgml/html/spi-spi-cursor-close.html | 4 doc/src/sgml/html/spi-spi-cursor-fetch.html | 4 doc/src/sgml/html/spi-spi-cursor-find.html | 4 doc/src/sgml/html/spi-spi-cursor-move.html | 4 doc/src/sgml/html/spi-spi-cursor-open-with-args.html | 4 doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html | 4 doc/src/sgml/html/spi-spi-cursor-open.html | 4 doc/src/sgml/html/spi-spi-exec.html | 4 doc/src/sgml/html/spi-spi-execp.html | 4 doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html | 4 doc/src/sgml/html/spi-spi-execute-plan.html | 4 doc/src/sgml/html/spi-spi-execute-with-args.html | 4 doc/src/sgml/html/spi-spi-execute.html | 4 doc/src/sgml/html/spi-spi-finish.html | 4 doc/src/sgml/html/spi-spi-fname.html | 4 doc/src/sgml/html/spi-spi-fnumber.html | 4 doc/src/sgml/html/spi-spi-freeplan.html | 4 doc/src/sgml/html/spi-spi-freetuple.html | 4 doc/src/sgml/html/spi-spi-freetupletable.html | 4 doc/src/sgml/html/spi-spi-getargcount.html | 4 doc/src/sgml/html/spi-spi-getargtypeid.html | 4 doc/src/sgml/html/spi-spi-getbinval.html | 4 doc/src/sgml/html/spi-spi-getnspname.html | 4 doc/src/sgml/html/spi-spi-getrelname.html | 4 doc/src/sgml/html/spi-spi-gettype.html | 4 doc/src/sgml/html/spi-spi-gettypeid.html | 4 doc/src/sgml/html/spi-spi-getvalue.html | 4 doc/src/sgml/html/spi-spi-is-cursor-plan.html | 4 doc/src/sgml/html/spi-spi-keepplan.html | 4 doc/src/sgml/html/spi-spi-modifytuple.html | 4 doc/src/sgml/html/spi-spi-palloc.html | 4 doc/src/sgml/html/spi-spi-pfree.html | 4 doc/src/sgml/html/spi-spi-prepare-cursor.html | 4 doc/src/sgml/html/spi-spi-prepare-params.html | 4 doc/src/sgml/html/spi-spi-prepare.html | 4 doc/src/sgml/html/spi-spi-register-relation.html | 4 doc/src/sgml/html/spi-spi-register-trigger-data.html | 4 doc/src/sgml/html/spi-spi-result-code-string.html | 4 doc/src/sgml/html/spi-spi-returntuple.html | 4 doc/src/sgml/html/spi-spi-rollback.html | 4 doc/src/sgml/html/spi-spi-saveplan.html | 4 doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html | 4 doc/src/sgml/html/spi-spi-scroll-cursor-move.html | 4 doc/src/sgml/html/spi-spi-start-transaction.html | 4 doc/src/sgml/html/spi-spi-unregister-relation.html | 4 doc/src/sgml/html/spi-transaction.html | 4 doc/src/sgml/html/spi-visibility.html | 4 doc/src/sgml/html/spi.html | 4 doc/src/sgml/html/sql-abort.html | 4 doc/src/sgml/html/sql-alteraggregate.html | 4 doc/src/sgml/html/sql-altercollation.html | 4 doc/src/sgml/html/sql-alterconversion.html | 4 doc/src/sgml/html/sql-alterdatabase.html | 4 doc/src/sgml/html/sql-alterdefaultprivileges.html | 4 doc/src/sgml/html/sql-alterdomain.html | 4 doc/src/sgml/html/sql-altereventtrigger.html | 4 doc/src/sgml/html/sql-alterextension.html | 4 doc/src/sgml/html/sql-alterforeigndatawrapper.html | 4 doc/src/sgml/html/sql-alterforeigntable.html | 6 doc/src/sgml/html/sql-alterfunction.html | 4 doc/src/sgml/html/sql-altergroup.html | 4 doc/src/sgml/html/sql-alterindex.html | 4 doc/src/sgml/html/sql-alterlanguage.html | 4 doc/src/sgml/html/sql-alterlargeobject.html | 4 doc/src/sgml/html/sql-altermaterializedview.html | 4 doc/src/sgml/html/sql-alteropclass.html | 4 doc/src/sgml/html/sql-alteroperator.html | 4 doc/src/sgml/html/sql-alteropfamily.html | 4 doc/src/sgml/html/sql-alterpolicy.html | 4 doc/src/sgml/html/sql-alterprocedure.html | 4 doc/src/sgml/html/sql-alterpublication.html | 4 doc/src/sgml/html/sql-alterrole.html | 4 doc/src/sgml/html/sql-alterroutine.html | 4 doc/src/sgml/html/sql-alterrule.html | 4 doc/src/sgml/html/sql-alterschema.html | 4 doc/src/sgml/html/sql-altersequence.html | 4 doc/src/sgml/html/sql-alterserver.html | 4 doc/src/sgml/html/sql-alterstatistics.html | 4 doc/src/sgml/html/sql-altersubscription.html | 4 doc/src/sgml/html/sql-altersystem.html | 4 doc/src/sgml/html/sql-altertable.html | 4 doc/src/sgml/html/sql-altertablespace.html | 4 doc/src/sgml/html/sql-altertrigger.html | 4 doc/src/sgml/html/sql-altertsconfig.html | 4 doc/src/sgml/html/sql-altertsdictionary.html | 4 doc/src/sgml/html/sql-altertsparser.html | 4 doc/src/sgml/html/sql-altertstemplate.html | 4 doc/src/sgml/html/sql-altertype.html | 4 doc/src/sgml/html/sql-alteruser.html | 4 doc/src/sgml/html/sql-alterusermapping.html | 4 doc/src/sgml/html/sql-alterview.html | 4 doc/src/sgml/html/sql-analyze.html | 4 doc/src/sgml/html/sql-begin.html | 4 doc/src/sgml/html/sql-call.html | 4 doc/src/sgml/html/sql-checkpoint.html | 4 doc/src/sgml/html/sql-close.html | 4 doc/src/sgml/html/sql-cluster.html | 4 doc/src/sgml/html/sql-commands.html | 4 doc/src/sgml/html/sql-comment.html | 4 doc/src/sgml/html/sql-commit-prepared.html | 4 doc/src/sgml/html/sql-commit.html | 4 doc/src/sgml/html/sql-copy.html | 4 doc/src/sgml/html/sql-create-access-method.html | 4 doc/src/sgml/html/sql-createaggregate.html | 4 doc/src/sgml/html/sql-createcast.html | 4 doc/src/sgml/html/sql-createcollation.html | 4 doc/src/sgml/html/sql-createconversion.html | 4 doc/src/sgml/html/sql-createdatabase.html | 4 doc/src/sgml/html/sql-createdomain.html | 4 doc/src/sgml/html/sql-createeventtrigger.html | 4 doc/src/sgml/html/sql-createextension.html | 4 doc/src/sgml/html/sql-createforeigndatawrapper.html | 4 doc/src/sgml/html/sql-createforeigntable.html | 4 doc/src/sgml/html/sql-createfunction.html | 4 doc/src/sgml/html/sql-creategroup.html | 4 doc/src/sgml/html/sql-createindex.html | 4 doc/src/sgml/html/sql-createlanguage.html | 4 doc/src/sgml/html/sql-creatematerializedview.html | 4 doc/src/sgml/html/sql-createopclass.html | 4 doc/src/sgml/html/sql-createoperator.html | 4 doc/src/sgml/html/sql-createopfamily.html | 4 doc/src/sgml/html/sql-createpolicy.html | 4 doc/src/sgml/html/sql-createprocedure.html | 4 doc/src/sgml/html/sql-createpublication.html | 4 doc/src/sgml/html/sql-createrole.html | 4 doc/src/sgml/html/sql-createrule.html | 4 doc/src/sgml/html/sql-createschema.html | 4 doc/src/sgml/html/sql-createsequence.html | 4 doc/src/sgml/html/sql-createserver.html | 4 doc/src/sgml/html/sql-createstatistics.html | 8 doc/src/sgml/html/sql-createsubscription.html | 4 doc/src/sgml/html/sql-createtable.html | 4 doc/src/sgml/html/sql-createtableas.html | 4 doc/src/sgml/html/sql-createtablespace.html | 4 doc/src/sgml/html/sql-createtransform.html | 4 doc/src/sgml/html/sql-createtrigger.html | 4 doc/src/sgml/html/sql-createtsconfig.html | 4 doc/src/sgml/html/sql-createtsdictionary.html | 4 doc/src/sgml/html/sql-createtsparser.html | 4 doc/src/sgml/html/sql-createtstemplate.html | 4 doc/src/sgml/html/sql-createtype.html | 4 doc/src/sgml/html/sql-createuser.html | 4 doc/src/sgml/html/sql-createusermapping.html | 4 doc/src/sgml/html/sql-createview.html | 4 doc/src/sgml/html/sql-deallocate.html | 4 doc/src/sgml/html/sql-declare.html | 4 doc/src/sgml/html/sql-delete.html | 4 doc/src/sgml/html/sql-discard.html | 4 doc/src/sgml/html/sql-do.html | 4 doc/src/sgml/html/sql-drop-access-method.html | 4 doc/src/sgml/html/sql-drop-owned.html | 4 doc/src/sgml/html/sql-dropaggregate.html | 4 doc/src/sgml/html/sql-dropcast.html | 4 doc/src/sgml/html/sql-dropcollation.html | 4 doc/src/sgml/html/sql-dropconversion.html | 4 doc/src/sgml/html/sql-dropdatabase.html | 4 doc/src/sgml/html/sql-dropdomain.html | 4 doc/src/sgml/html/sql-dropeventtrigger.html | 4 doc/src/sgml/html/sql-dropextension.html | 4 doc/src/sgml/html/sql-dropforeigndatawrapper.html | 4 doc/src/sgml/html/sql-dropforeigntable.html | 4 doc/src/sgml/html/sql-dropfunction.html | 4 doc/src/sgml/html/sql-dropgroup.html | 4 doc/src/sgml/html/sql-dropindex.html | 4 doc/src/sgml/html/sql-droplanguage.html | 4 doc/src/sgml/html/sql-dropmaterializedview.html | 4 doc/src/sgml/html/sql-dropopclass.html | 4 doc/src/sgml/html/sql-dropoperator.html | 4 doc/src/sgml/html/sql-dropopfamily.html | 4 doc/src/sgml/html/sql-droppolicy.html | 4 doc/src/sgml/html/sql-dropprocedure.html | 4 doc/src/sgml/html/sql-droppublication.html | 4 doc/src/sgml/html/sql-droprole.html | 4 doc/src/sgml/html/sql-droproutine.html | 4 doc/src/sgml/html/sql-droprule.html | 4 doc/src/sgml/html/sql-dropschema.html | 4 doc/src/sgml/html/sql-dropsequence.html | 4 doc/src/sgml/html/sql-dropserver.html | 4 doc/src/sgml/html/sql-dropstatistics.html | 4 doc/src/sgml/html/sql-dropsubscription.html | 12 doc/src/sgml/html/sql-droptable.html | 4 doc/src/sgml/html/sql-droptablespace.html | 4 doc/src/sgml/html/sql-droptransform.html | 4 doc/src/sgml/html/sql-droptrigger.html | 4 doc/src/sgml/html/sql-droptsconfig.html | 4 doc/src/sgml/html/sql-droptsdictionary.html | 4 doc/src/sgml/html/sql-droptsparser.html | 4 doc/src/sgml/html/sql-droptstemplate.html | 4 doc/src/sgml/html/sql-droptype.html | 4 doc/src/sgml/html/sql-dropuser.html | 4 doc/src/sgml/html/sql-dropusermapping.html | 4 doc/src/sgml/html/sql-dropview.html | 4 doc/src/sgml/html/sql-end.html | 4 doc/src/sgml/html/sql-execute.html | 4 doc/src/sgml/html/sql-explain.html | 4 doc/src/sgml/html/sql-expressions.html | 4 doc/src/sgml/html/sql-fetch.html | 4 doc/src/sgml/html/sql-grant.html | 4 doc/src/sgml/html/sql-importforeignschema.html | 4 doc/src/sgml/html/sql-insert.html | 4 doc/src/sgml/html/sql-keywords-appendix.html | 6 doc/src/sgml/html/sql-listen.html | 4 doc/src/sgml/html/sql-load.html | 4 doc/src/sgml/html/sql-lock.html | 4 doc/src/sgml/html/sql-move.html | 4 doc/src/sgml/html/sql-notify.html | 4 doc/src/sgml/html/sql-prepare-transaction.html | 4 doc/src/sgml/html/sql-prepare.html | 4 doc/src/sgml/html/sql-reassign-owned.html | 4 doc/src/sgml/html/sql-refreshmaterializedview.html | 4 doc/src/sgml/html/sql-reindex.html | 4 doc/src/sgml/html/sql-release-savepoint.html | 4 doc/src/sgml/html/sql-reset.html | 4 doc/src/sgml/html/sql-revoke.html | 4 doc/src/sgml/html/sql-rollback-prepared.html | 4 doc/src/sgml/html/sql-rollback-to.html | 4 doc/src/sgml/html/sql-rollback.html | 4 doc/src/sgml/html/sql-savepoint.html | 4 doc/src/sgml/html/sql-security-label.html | 4 doc/src/sgml/html/sql-select.html | 4 doc/src/sgml/html/sql-selectinto.html | 4 doc/src/sgml/html/sql-set-constraints.html | 4 doc/src/sgml/html/sql-set-role.html | 4 doc/src/sgml/html/sql-set-session-authorization.html | 4 doc/src/sgml/html/sql-set-transaction.html | 4 doc/src/sgml/html/sql-set.html | 4 doc/src/sgml/html/sql-show.html | 4 doc/src/sgml/html/sql-start-transaction.html | 4 doc/src/sgml/html/sql-syntax-calling-funcs.html | 4 doc/src/sgml/html/sql-syntax-lexical.html | 4 doc/src/sgml/html/sql-syntax.html | 4 doc/src/sgml/html/sql-truncate.html | 4 doc/src/sgml/html/sql-unlisten.html | 4 doc/src/sgml/html/sql-update.html | 4 doc/src/sgml/html/sql-vacuum.html | 4 doc/src/sgml/html/sql-values.html | 4 doc/src/sgml/html/sql.html | 4 doc/src/sgml/html/ssh-tunnels.html | 4 doc/src/sgml/html/ssl-tcp.html | 4 doc/src/sgml/html/sslinfo.html | 4 doc/src/sgml/html/sspi-auth.html | 4 doc/src/sgml/html/storage-file-layout.html | 4 doc/src/sgml/html/storage-fsm.html | 4 doc/src/sgml/html/storage-hot.html | 6 doc/src/sgml/html/storage-init.html | 4 doc/src/sgml/html/storage-page-layout.html | 4 doc/src/sgml/html/storage-toast.html | 4 doc/src/sgml/html/storage-vm.html | 4 doc/src/sgml/html/storage.html | 4 doc/src/sgml/html/supported-platforms.html | 4 doc/src/sgml/html/system-catalog-declarations.html | 4 doc/src/sgml/html/system-catalog-initial-data.html | 4 doc/src/sgml/html/tableam.html | 4 doc/src/sgml/html/tablefunc.html | 4 doc/src/sgml/html/tablesample-method.html | 4 doc/src/sgml/html/tablesample-support-functions.html | 4 doc/src/sgml/html/tcn.html | 4 doc/src/sgml/html/test-decoding.html | 4 doc/src/sgml/html/textsearch-configuration.html | 4 doc/src/sgml/html/textsearch-controls.html | 4 doc/src/sgml/html/textsearch-debugging.html | 4 doc/src/sgml/html/textsearch-dictionaries.html | 4 doc/src/sgml/html/textsearch-features.html | 4 doc/src/sgml/html/textsearch-indexes.html | 4 doc/src/sgml/html/textsearch-intro.html | 4 doc/src/sgml/html/textsearch-limitations.html | 4 doc/src/sgml/html/textsearch-parsers.html | 4 doc/src/sgml/html/textsearch-psql.html | 4 doc/src/sgml/html/textsearch-tables.html | 4 doc/src/sgml/html/textsearch.html | 2 doc/src/sgml/html/transaction-iso.html | 4 doc/src/sgml/html/trigger-datachanges.html | 4 doc/src/sgml/html/trigger-definition.html | 4 doc/src/sgml/html/trigger-example.html | 4 doc/src/sgml/html/trigger-interface.html | 4 doc/src/sgml/html/triggers.html | 4 doc/src/sgml/html/tsm-system-rows.html | 4 doc/src/sgml/html/tsm-system-time.html | 4 doc/src/sgml/html/tutorial-accessdb.html | 8 doc/src/sgml/html/tutorial-advanced-intro.html | 4 doc/src/sgml/html/tutorial-advanced.html | 2 doc/src/sgml/html/tutorial-agg.html | 4 doc/src/sgml/html/tutorial-arch.html | 4 doc/src/sgml/html/tutorial-concepts.html | 4 doc/src/sgml/html/tutorial-conclusion.html | 4 doc/src/sgml/html/tutorial-createdb.html | 4 doc/src/sgml/html/tutorial-delete.html | 4 doc/src/sgml/html/tutorial-fk.html | 4 doc/src/sgml/html/tutorial-inheritance.html | 4 doc/src/sgml/html/tutorial-install.html | 4 doc/src/sgml/html/tutorial-join.html | 4 doc/src/sgml/html/tutorial-populate.html | 4 doc/src/sgml/html/tutorial-select.html | 4 doc/src/sgml/html/tutorial-sql-intro.html | 4 doc/src/sgml/html/tutorial-sql.html | 2 doc/src/sgml/html/tutorial-start.html | 2 doc/src/sgml/html/tutorial-table.html | 4 doc/src/sgml/html/tutorial-transactions.html | 4 doc/src/sgml/html/tutorial-update.html | 4 doc/src/sgml/html/tutorial-views.html | 4 doc/src/sgml/html/tutorial-window.html | 4 doc/src/sgml/html/tutorial.html | 4 doc/src/sgml/html/typeconv-func.html | 4 doc/src/sgml/html/typeconv-oper.html | 4 doc/src/sgml/html/typeconv-overview.html | 4 doc/src/sgml/html/typeconv-query.html | 4 doc/src/sgml/html/typeconv-select.html | 4 doc/src/sgml/html/typeconv-union-case.html | 4 doc/src/sgml/html/typeconv.html | 4 doc/src/sgml/html/unaccent.html | 4 doc/src/sgml/html/unsupported-features-sql-standard.html | 4 doc/src/sgml/html/upgrading.html | 6 doc/src/sgml/html/user-manag.html | 4 doc/src/sgml/html/using-explain.html | 4 doc/src/sgml/html/uuid-ossp.html | 4 doc/src/sgml/html/vacuumlo.html | 4 doc/src/sgml/html/view-pg-available-extension-versions.html | 4 doc/src/sgml/html/view-pg-available-extensions.html | 4 doc/src/sgml/html/view-pg-config.html | 4 doc/src/sgml/html/view-pg-cursors.html | 4 doc/src/sgml/html/view-pg-file-settings.html | 4 doc/src/sgml/html/view-pg-group.html | 4 doc/src/sgml/html/view-pg-hba-file-rules.html | 4 doc/src/sgml/html/view-pg-indexes.html | 4 doc/src/sgml/html/view-pg-locks.html | 4 doc/src/sgml/html/view-pg-matviews.html | 4 doc/src/sgml/html/view-pg-policies.html | 4 doc/src/sgml/html/view-pg-prepared-statements.html | 4 doc/src/sgml/html/view-pg-prepared-xacts.html | 4 doc/src/sgml/html/view-pg-publication-tables.html | 4 doc/src/sgml/html/view-pg-replication-origin-status.html | 4 doc/src/sgml/html/view-pg-replication-slots.html | 4 doc/src/sgml/html/view-pg-roles.html | 4 doc/src/sgml/html/view-pg-rules.html | 4 doc/src/sgml/html/view-pg-seclabels.html | 4 doc/src/sgml/html/view-pg-sequences.html | 4 doc/src/sgml/html/view-pg-settings.html | 4 doc/src/sgml/html/view-pg-shadow.html | 4 doc/src/sgml/html/view-pg-shmem-allocations.html | 4 doc/src/sgml/html/view-pg-stats-ext.html | 4 doc/src/sgml/html/view-pg-stats.html | 4 doc/src/sgml/html/view-pg-tables.html | 4 doc/src/sgml/html/view-pg-timezone-abbrevs.html | 4 doc/src/sgml/html/view-pg-timezone-names.html | 4 doc/src/sgml/html/view-pg-user-mappings.html | 4 doc/src/sgml/html/view-pg-user.html | 4 doc/src/sgml/html/view-pg-views.html | 4 doc/src/sgml/html/views-overview.html | 4 doc/src/sgml/html/wal-async-commit.html | 4 doc/src/sgml/html/wal-configuration.html | 4 doc/src/sgml/html/wal-internals.html | 4 doc/src/sgml/html/wal-intro.html | 4 doc/src/sgml/html/wal-reliability.html | 4 doc/src/sgml/html/wal.html | 4 doc/src/sgml/html/warm-standby-failover.html | 4 doc/src/sgml/html/warm-standby.html | 4 doc/src/sgml/html/when-can-parallel-query-be-used.html | 4 doc/src/sgml/html/xaggr.html | 4 doc/src/sgml/html/xfunc-c.html | 4 doc/src/sgml/html/xfunc-internal.html | 4 doc/src/sgml/html/xfunc-optimization.html | 4 doc/src/sgml/html/xfunc-overload.html | 4 doc/src/sgml/html/xfunc-pl.html | 4 doc/src/sgml/html/xfunc-sql.html | 4 doc/src/sgml/html/xfunc-volatility.html | 4 doc/src/sgml/html/xfunc.html | 4 doc/src/sgml/html/xindex.html | 4 doc/src/sgml/html/xml-limits-conformance.html | 4 doc/src/sgml/html/xml2.html | 4 doc/src/sgml/html/xoper-optimization.html | 6 doc/src/sgml/html/xoper.html | 4 doc/src/sgml/html/xplang-install.html | 4 doc/src/sgml/html/xplang.html | 4 doc/src/sgml/html/xproc.html | 4 doc/src/sgml/html/xtypes.html | 4 doc/src/sgml/logical-replication.sgml | 10 doc/src/sgml/man1/clusterdb.1 | 6 doc/src/sgml/man1/createdb.1 | 6 doc/src/sgml/man1/createuser.1 | 6 doc/src/sgml/man1/dropdb.1 | 6 doc/src/sgml/man1/dropuser.1 | 6 doc/src/sgml/man1/ecpg.1 | 6 doc/src/sgml/man1/initdb.1 | 6 doc/src/sgml/man1/oid2name.1 | 6 doc/src/sgml/man1/pg_archivecleanup.1 | 6 doc/src/sgml/man1/pg_basebackup.1 | 6 doc/src/sgml/man1/pg_checksums.1 | 6 doc/src/sgml/man1/pg_config.1 | 6 doc/src/sgml/man1/pg_controldata.1 | 6 doc/src/sgml/man1/pg_ctl.1 | 6 doc/src/sgml/man1/pg_dump.1 | 6 doc/src/sgml/man1/pg_dumpall.1 | 6 doc/src/sgml/man1/pg_isready.1 | 6 doc/src/sgml/man1/pg_receivewal.1 | 6 doc/src/sgml/man1/pg_recvlogical.1 | 6 doc/src/sgml/man1/pg_resetwal.1 | 6 doc/src/sgml/man1/pg_restore.1 | 6 doc/src/sgml/man1/pg_rewind.1 | 6 doc/src/sgml/man1/pg_standby.1 | 6 doc/src/sgml/man1/pg_test_fsync.1 | 6 doc/src/sgml/man1/pg_test_timing.1 | 6 doc/src/sgml/man1/pg_upgrade.1 | 6 doc/src/sgml/man1/pg_verifybackup.1 | 6 doc/src/sgml/man1/pg_waldump.1 | 6 doc/src/sgml/man1/pgbench.1 | 6 doc/src/sgml/man1/postgres.1 | 6 doc/src/sgml/man1/postmaster.1 | 6 doc/src/sgml/man1/psql.1 | 8 doc/src/sgml/man1/reindexdb.1 | 6 doc/src/sgml/man1/vacuumdb.1 | 6 doc/src/sgml/man1/vacuumlo.1 | 6 doc/src/sgml/man3/SPI_commit.3 | 6 doc/src/sgml/man3/SPI_connect.3 | 6 doc/src/sgml/man3/SPI_copytuple.3 | 6 doc/src/sgml/man3/SPI_cursor_close.3 | 6 doc/src/sgml/man3/SPI_cursor_fetch.3 | 6 doc/src/sgml/man3/SPI_cursor_find.3 | 6 doc/src/sgml/man3/SPI_cursor_move.3 | 6 doc/src/sgml/man3/SPI_cursor_open.3 | 6 doc/src/sgml/man3/SPI_cursor_open_with_args.3 | 6 doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 | 6 doc/src/sgml/man3/SPI_exec.3 | 6 doc/src/sgml/man3/SPI_execp.3 | 6 doc/src/sgml/man3/SPI_execute.3 | 6 doc/src/sgml/man3/SPI_execute_plan.3 | 6 doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 | 6 doc/src/sgml/man3/SPI_execute_with_args.3 | 6 doc/src/sgml/man3/SPI_finish.3 | 6 doc/src/sgml/man3/SPI_fname.3 | 6 doc/src/sgml/man3/SPI_fnumber.3 | 6 doc/src/sgml/man3/SPI_freeplan.3 | 6 doc/src/sgml/man3/SPI_freetuple.3 | 6 doc/src/sgml/man3/SPI_freetuptable.3 | 6 doc/src/sgml/man3/SPI_getargcount.3 | 6 doc/src/sgml/man3/SPI_getargtypeid.3 | 6 doc/src/sgml/man3/SPI_getbinval.3 | 6 doc/src/sgml/man3/SPI_getnspname.3 | 6 doc/src/sgml/man3/SPI_getrelname.3 | 6 doc/src/sgml/man3/SPI_gettype.3 | 6 doc/src/sgml/man3/SPI_gettypeid.3 | 6 doc/src/sgml/man3/SPI_getvalue.3 | 6 doc/src/sgml/man3/SPI_is_cursor_plan.3 | 6 doc/src/sgml/man3/SPI_keepplan.3 | 6 doc/src/sgml/man3/SPI_modifytuple.3 | 6 doc/src/sgml/man3/SPI_palloc.3 | 6 doc/src/sgml/man3/SPI_pfree.3 | 6 doc/src/sgml/man3/SPI_prepare.3 | 6 doc/src/sgml/man3/SPI_prepare_cursor.3 | 6 doc/src/sgml/man3/SPI_prepare_params.3 | 6 doc/src/sgml/man3/SPI_register_relation.3 | 6 doc/src/sgml/man3/SPI_register_trigger_data.3 | 6 doc/src/sgml/man3/SPI_repalloc.3 | 6 doc/src/sgml/man3/SPI_result_code_string.3 | 6 doc/src/sgml/man3/SPI_returntuple.3 | 6 doc/src/sgml/man3/SPI_rollback.3 | 6 doc/src/sgml/man3/SPI_saveplan.3 | 6 doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 | 6 doc/src/sgml/man3/SPI_scroll_cursor_move.3 | 6 doc/src/sgml/man3/SPI_start_transaction.3 | 6 doc/src/sgml/man3/SPI_unregister_relation.3 | 6 doc/src/sgml/man3/dblink.3 | 6 doc/src/sgml/man3/dblink_build_sql_delete.3 | 6 doc/src/sgml/man3/dblink_build_sql_insert.3 | 6 doc/src/sgml/man3/dblink_build_sql_update.3 | 6 doc/src/sgml/man3/dblink_cancel_query.3 | 6 doc/src/sgml/man3/dblink_close.3 | 6 doc/src/sgml/man3/dblink_connect.3 | 6 doc/src/sgml/man3/dblink_connect_u.3 | 6 doc/src/sgml/man3/dblink_disconnect.3 | 6 doc/src/sgml/man3/dblink_error_message.3 | 6 doc/src/sgml/man3/dblink_exec.3 | 6 doc/src/sgml/man3/dblink_fetch.3 | 6 doc/src/sgml/man3/dblink_get_connections.3 | 6 doc/src/sgml/man3/dblink_get_notify.3 | 6 doc/src/sgml/man3/dblink_get_pkey.3 | 6 doc/src/sgml/man3/dblink_get_result.3 | 6 doc/src/sgml/man3/dblink_is_busy.3 | 6 doc/src/sgml/man3/dblink_open.3 | 6 doc/src/sgml/man3/dblink_send_query.3 | 6 doc/src/sgml/man7/ABORT.7 | 6 doc/src/sgml/man7/ALTER_AGGREGATE.7 | 6 doc/src/sgml/man7/ALTER_COLLATION.7 | 6 doc/src/sgml/man7/ALTER_CONVERSION.7 | 6 doc/src/sgml/man7/ALTER_DATABASE.7 | 6 doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 | 6 doc/src/sgml/man7/ALTER_DOMAIN.7 | 6 doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 | 6 doc/src/sgml/man7/ALTER_EXTENSION.7 | 6 doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 | 6 doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 | 8 doc/src/sgml/man7/ALTER_FUNCTION.7 | 6 doc/src/sgml/man7/ALTER_GROUP.7 | 6 doc/src/sgml/man7/ALTER_INDEX.7 | 6 doc/src/sgml/man7/ALTER_LANGUAGE.7 | 6 doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 | 6 doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 | 6 doc/src/sgml/man7/ALTER_OPERATOR.7 | 6 doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 | 6 doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 | 6 doc/src/sgml/man7/ALTER_POLICY.7 | 6 doc/src/sgml/man7/ALTER_PROCEDURE.7 | 6 doc/src/sgml/man7/ALTER_PUBLICATION.7 | 6 doc/src/sgml/man7/ALTER_ROLE.7 | 6 doc/src/sgml/man7/ALTER_ROUTINE.7 | 6 doc/src/sgml/man7/ALTER_RULE.7 | 6 doc/src/sgml/man7/ALTER_SCHEMA.7 | 6 doc/src/sgml/man7/ALTER_SEQUENCE.7 | 6 doc/src/sgml/man7/ALTER_SERVER.7 | 6 doc/src/sgml/man7/ALTER_STATISTICS.7 | 6 doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 | 6 doc/src/sgml/man7/ALTER_SYSTEM.7 | 6 doc/src/sgml/man7/ALTER_TABLE.7 | 6 doc/src/sgml/man7/ALTER_TABLESPACE.7 | 6 doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 | 6 doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 | 6 doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 | 6 doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 | 6 doc/src/sgml/man7/ALTER_TRIGGER.7 | 6 doc/src/sgml/man7/ALTER_TYPE.7 | 6 doc/src/sgml/man7/ALTER_USER.7 | 6 doc/src/sgml/man7/ALTER_USER_MAPPING.7 | 6 doc/src/sgml/man7/ALTER_VIEW.7 | 6 doc/src/sgml/man7/ANALYZE.7 | 6 doc/src/sgml/man7/BEGIN.7 | 6 doc/src/sgml/man7/CALL.7 | 6 doc/src/sgml/man7/CHECKPOINT.7 | 6 doc/src/sgml/man7/CLOSE.7 | 6 doc/src/sgml/man7/CLUSTER.7 | 6 doc/src/sgml/man7/COMMENT.7 | 6 doc/src/sgml/man7/COMMIT.7 | 6 doc/src/sgml/man7/COMMIT_PREPARED.7 | 6 doc/src/sgml/man7/COPY.7 | 6 doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 | 6 doc/src/sgml/man7/CREATE_AGGREGATE.7 | 6 doc/src/sgml/man7/CREATE_CAST.7 | 6 doc/src/sgml/man7/CREATE_COLLATION.7 | 6 doc/src/sgml/man7/CREATE_CONVERSION.7 | 6 doc/src/sgml/man7/CREATE_DATABASE.7 | 6 doc/src/sgml/man7/CREATE_DOMAIN.7 | 6 doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 | 6 doc/src/sgml/man7/CREATE_EXTENSION.7 | 6 doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 | 6 doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 | 6 doc/src/sgml/man7/CREATE_FUNCTION.7 | 6 doc/src/sgml/man7/CREATE_GROUP.7 | 6 doc/src/sgml/man7/CREATE_INDEX.7 | 6 doc/src/sgml/man7/CREATE_LANGUAGE.7 | 6 doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 | 6 doc/src/sgml/man7/CREATE_OPERATOR.7 | 6 doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 | 6 doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 | 6 doc/src/sgml/man7/CREATE_POLICY.7 | 6 doc/src/sgml/man7/CREATE_PROCEDURE.7 | 6 doc/src/sgml/man7/CREATE_PUBLICATION.7 | 6 doc/src/sgml/man7/CREATE_ROLE.7 | 6 doc/src/sgml/man7/CREATE_RULE.7 | 6 doc/src/sgml/man7/CREATE_SCHEMA.7 | 6 doc/src/sgml/man7/CREATE_SEQUENCE.7 | 6 doc/src/sgml/man7/CREATE_SERVER.7 | 6 doc/src/sgml/man7/CREATE_STATISTICS.7 | 9 doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 | 6 doc/src/sgml/man7/CREATE_TABLE.7 | 6 doc/src/sgml/man7/CREATE_TABLESPACE.7 | 6 doc/src/sgml/man7/CREATE_TABLE_AS.7 | 6 doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 | 6 doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 | 6 doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 | 6 doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 | 6 doc/src/sgml/man7/CREATE_TRANSFORM.7 | 6 doc/src/sgml/man7/CREATE_TRIGGER.7 | 6 doc/src/sgml/man7/CREATE_TYPE.7 | 6 doc/src/sgml/man7/CREATE_USER.7 | 6 doc/src/sgml/man7/CREATE_USER_MAPPING.7 | 6 doc/src/sgml/man7/CREATE_VIEW.7 | 6 doc/src/sgml/man7/DEALLOCATE.7 | 6 doc/src/sgml/man7/DECLARE.7 | 6 doc/src/sgml/man7/DELETE.7 | 6 doc/src/sgml/man7/DISCARD.7 | 6 doc/src/sgml/man7/DO.7 | 6 doc/src/sgml/man7/DROP_ACCESS_METHOD.7 | 6 doc/src/sgml/man7/DROP_AGGREGATE.7 | 6 doc/src/sgml/man7/DROP_CAST.7 | 6 doc/src/sgml/man7/DROP_COLLATION.7 | 6 doc/src/sgml/man7/DROP_CONVERSION.7 | 6 doc/src/sgml/man7/DROP_DATABASE.7 | 6 doc/src/sgml/man7/DROP_DOMAIN.7 | 6 doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 | 6 doc/src/sgml/man7/DROP_EXTENSION.7 | 6 doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 | 6 doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 | 6 doc/src/sgml/man7/DROP_FUNCTION.7 | 6 doc/src/sgml/man7/DROP_GROUP.7 | 6 doc/src/sgml/man7/DROP_INDEX.7 | 6 doc/src/sgml/man7/DROP_LANGUAGE.7 | 6 doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 | 6 doc/src/sgml/man7/DROP_OPERATOR.7 | 6 doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 | 6 doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 | 6 doc/src/sgml/man7/DROP_OWNED.7 | 6 doc/src/sgml/man7/DROP_POLICY.7 | 6 doc/src/sgml/man7/DROP_PROCEDURE.7 | 6 doc/src/sgml/man7/DROP_PUBLICATION.7 | 6 doc/src/sgml/man7/DROP_ROLE.7 | 6 doc/src/sgml/man7/DROP_ROUTINE.7 | 6 doc/src/sgml/man7/DROP_RULE.7 | 6 doc/src/sgml/man7/DROP_SCHEMA.7 | 6 doc/src/sgml/man7/DROP_SEQUENCE.7 | 6 doc/src/sgml/man7/DROP_SERVER.7 | 6 doc/src/sgml/man7/DROP_STATISTICS.7 | 6 doc/src/sgml/man7/DROP_SUBSCRIPTION.7 | 9 doc/src/sgml/man7/DROP_TABLE.7 | 6 doc/src/sgml/man7/DROP_TABLESPACE.7 | 6 doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 | 6 doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 | 6 doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 | 6 doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 | 6 doc/src/sgml/man7/DROP_TRANSFORM.7 | 6 doc/src/sgml/man7/DROP_TRIGGER.7 | 6 doc/src/sgml/man7/DROP_TYPE.7 | 6 doc/src/sgml/man7/DROP_USER.7 | 6 doc/src/sgml/man7/DROP_USER_MAPPING.7 | 6 doc/src/sgml/man7/DROP_VIEW.7 | 6 doc/src/sgml/man7/END.7 | 6 doc/src/sgml/man7/EXECUTE.7 | 6 doc/src/sgml/man7/EXPLAIN.7 | 6 doc/src/sgml/man7/FETCH.7 | 6 doc/src/sgml/man7/GRANT.7 | 6 doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 | 6 doc/src/sgml/man7/INSERT.7 | 6 doc/src/sgml/man7/LISTEN.7 | 6 doc/src/sgml/man7/LOAD.7 | 6 doc/src/sgml/man7/LOCK.7 | 6 doc/src/sgml/man7/MOVE.7 | 6 doc/src/sgml/man7/NOTIFY.7 | 6 doc/src/sgml/man7/PREPARE.7 | 6 doc/src/sgml/man7/PREPARE_TRANSACTION.7 | 6 doc/src/sgml/man7/REASSIGN_OWNED.7 | 6 doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 | 6 doc/src/sgml/man7/REINDEX.7 | 6 doc/src/sgml/man7/RELEASE_SAVEPOINT.7 | 6 doc/src/sgml/man7/RESET.7 | 6 doc/src/sgml/man7/REVOKE.7 | 6 doc/src/sgml/man7/ROLLBACK.7 | 6 doc/src/sgml/man7/ROLLBACK_PREPARED.7 | 6 doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 | 6 doc/src/sgml/man7/SAVEPOINT.7 | 6 doc/src/sgml/man7/SECURITY_LABEL.7 | 6 doc/src/sgml/man7/SELECT.7 | 6 doc/src/sgml/man7/SELECT_INTO.7 | 6 doc/src/sgml/man7/SET.7 | 6 doc/src/sgml/man7/SET_CONSTRAINTS.7 | 6 doc/src/sgml/man7/SET_ROLE.7 | 6 doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 | 6 doc/src/sgml/man7/SET_TRANSACTION.7 | 6 doc/src/sgml/man7/SHOW.7 | 6 doc/src/sgml/man7/START_TRANSACTION.7 | 6 doc/src/sgml/man7/TRUNCATE.7 | 6 doc/src/sgml/man7/UNLISTEN.7 | 6 doc/src/sgml/man7/UPDATE.7 | 6 doc/src/sgml/man7/VACUUM.7 | 6 doc/src/sgml/man7/VALUES.7 | 6 doc/src/sgml/queries.sgml | 2 doc/src/sgml/ref/alter_foreign_table.sgml | 2 doc/src/sgml/ref/create_statistics.sgml | 6 doc/src/sgml/ref/drop_subscription.sgml | 8 doc/src/sgml/release-13.sgml | 860 +++++++++ doc/src/sgml/spi.sgml | 48 doc/src/sgml/storage.sgml | 2 src/backend/access/brin/brin.c | 146 + src/backend/access/brin/brin_inclusion.c | 10 src/backend/access/brin/brin_minmax.c | 10 src/backend/access/brin/brin_tuple.c | 14 src/backend/access/gin/ginfast.c | 9 src/backend/access/gin/ginget.c | 4 src/backend/access/heap/heapam_handler.c | 6 src/backend/access/nbtree/nbtpage.c | 68 src/backend/access/nbtree/nbtree.c | 3 src/backend/access/nbtree/nbtsearch.c | 39 src/backend/access/transam/twophase.c | 33 src/backend/access/transam/xlog.c | 114 - src/backend/catalog/index.c | 2 src/backend/commands/dbcommands.c | 100 - src/backend/commands/extension.c | 32 src/backend/commands/indexcmds.c | 29 src/backend/commands/subscriptioncmds.c | 3 src/backend/commands/tablecmds.c | 23 src/backend/commands/trigger.c | 33 src/backend/commands/vacuum.c | 18 src/backend/executor/execExprInterp.c | 29 src/backend/executor/execUtils.c | 21 src/backend/executor/nodeIncrementalSort.c | 7 src/backend/jit/llvm/llvmjit.c | 2 src/backend/libpq/hba.c | 4 src/backend/optimizer/path/indxpath.c | 9 src/backend/optimizer/path/joinpath.c | 19 src/backend/optimizer/plan/analyzejoins.c | 9 src/backend/optimizer/plan/planner.c | 12 src/backend/optimizer/plan/subselect.c | 6 src/backend/optimizer/util/restrictinfo.c | 29 src/backend/po/de.po | 921 +++++---- src/backend/po/fr.po | 832 ++++---- src/backend/po/ja.po | 934 +++++----- src/backend/po/zh_CN.po | 2 src/backend/postmaster/autovacuum.c | 12 src/backend/rewrite/rewriteHandler.c | 6 src/backend/storage/ipc/procarray.c | 1 src/backend/storage/lmgr/README | 34 src/backend/storage/lmgr/deadlock.c | 9 src/backend/storage/lmgr/lock.c | 32 src/backend/storage/lmgr/proc.c | 18 src/backend/storage/smgr/md.c | 3 src/backend/tcop/postgres.c | 14 src/backend/tsearch/wparser_def.c | 15 src/backend/utils/adt/jsonpath.c | 3 src/backend/utils/adt/jsonpath_exec.c | 17 src/backend/utils/cache/plancache.c | 8 src/backend/utils/cache/relcache.c | 1 src/backend/utils/init/postinit.c | 10 src/backend/utils/mmgr/dsa.c | 65 src/bin/pg_basebackup/t/010_pg_basebackup.pl | 24 src/bin/pg_dump/pg_dumpall.c | 4 src/bin/pg_dump/t/002_pg_dump.pl | 21 src/bin/scripts/clusterdb.c | 4 src/bin/scripts/reindexdb.c | 4 src/bin/scripts/t/011_clusterdb_all.pl | 15 src/bin/scripts/t/050_dropdb.pl | 11 src/bin/scripts/t/091_reindexdb_all.pl | 15 src/bin/scripts/t/101_vacuumdb_all.pl | 15 src/bin/scripts/vacuumdb.c | 2 src/include/access/brin_tuple.h | 6 src/include/catalog/pg_database.h | 20 src/include/lib/simplehash.h | 4 src/include/nodes/pathnodes.h | 13 src/include/optimizer/restrictinfo.h | 2 src/include/pg_config.h.in | 4 src/test/isolation/expected/eval-plan-qual.out | 124 + src/test/isolation/specs/eval-plan-qual.spec | 20 src/test/kerberos/t/001_auth.pl | 9 src/test/ldap/t/001_auth.pl | 10 src/test/modules/brin/expected/summarization-and-inprogress-insertion.out | 8 src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec | 1 src/test/modules/test_extensions/Makefile | 2 src/test/modules/test_extensions/expected/test_extensions.out | 30 src/test/modules/test_extensions/sql/test_extensions.sql | 17 src/test/modules/test_extensions/test_ext_extschema--1.0.sql | 5 src/test/modules/test_extensions/test_ext_extschema.control | 3 src/test/perl/PostgresNode.pm | 15 src/test/perl/TestLib.pm | 7 src/test/recovery/t/019_replslot_limit.pl | 25 src/test/recovery/t/033_replay_tsp_drops.pl | 14 src/test/recovery/t/037_invalid_database.pl | 157 + src/test/regress/expected/indexing.out | 128 + src/test/regress/expected/join.out | 17 src/test/regress/expected/join_hash.out | 36 src/test/regress/expected/jsonb_jsonpath.out | 15 src/test/regress/expected/psql.out | 11 src/test/regress/expected/rowtypes.out | 9 src/test/regress/expected/transactions.out | 76 src/test/regress/expected/updatable_views.out | 32 src/test/regress/sql/indexing.sql | 91 src/test/regress/sql/join.sql | 9 src/test/regress/sql/join_hash.sql | 19 src/test/regress/sql/jsonb_jsonpath.sql | 3 src/test/regress/sql/psql.sql | 8 src/test/regress/sql/rowtypes.sql | 5 src/test/regress/sql/transactions.sql | 64 src/test/regress/sql/updatable_views.sql | 17 src/tools/msvc/Solution.pm | 10 1542 files changed, 7862 insertions(+), 5046 deletions(-) diff -Nru postgresql-13-13.11/.gitrevision postgresql-13-13.12/.gitrevision --- postgresql-13-13.11/.gitrevision 2023-05-08 21:32:52.000000000 +0000 +++ postgresql-13-13.12/.gitrevision 2023-08-07 20:31:14.000000000 +0000 @@ -1 +1 @@ -2faab87390b03929a8cbb5a9336a04faa45a27c5 +c9d50b21a72d2bbc092ea9d7de4d4c044d8f8275 diff -Nru postgresql-13-13.11/configure postgresql-13-13.12/configure --- postgresql-13-13.11/configure 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/configure 2023-08-07 20:11:34.000000000 +0000 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for PostgreSQL 13.11. +# Generated by GNU Autoconf 2.69 for PostgreSQL 13.12. # # Report bugs to . # @@ -582,8 +582,8 @@ # Identity of this package. PACKAGE_NAME='PostgreSQL' PACKAGE_TARNAME='postgresql' -PACKAGE_VERSION='13.11' -PACKAGE_STRING='PostgreSQL 13.11' +PACKAGE_VERSION='13.12' +PACKAGE_STRING='PostgreSQL 13.12' PACKAGE_BUGREPORT='pgsql-bugs@lists.postgresql.org' PACKAGE_URL='https://www.postgresql.org/' @@ -1436,7 +1436,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures PostgreSQL 13.11 to adapt to many kinds of systems. +\`configure' configures PostgreSQL 13.12 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1501,7 +1501,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of PostgreSQL 13.11:";; + short | recursive ) echo "Configuration of PostgreSQL 13.12:";; esac cat <<\_ACEOF @@ -1668,7 +1668,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -PostgreSQL configure 13.11 +PostgreSQL configure 13.12 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -2421,7 +2421,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by PostgreSQL $as_me 13.11, which was +It was created by PostgreSQL $as_me 13.12, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -12477,7 +12477,11 @@ fi if test "$with_openssl" = yes ; then - if test "$PORTNAME" != "win32"; then + # Minimum required OpenSSL version is 1.0.1 + +$as_echo "#define OPENSSL_API_COMPAT 0x10001000L" >>confdefs.h + + if test "$PORTNAME" != "win32"; then { $as_echo "$as_me:${as_lineno-$LINENO}: checking for CRYPTO_new_ex_data in -lcrypto" >&5 $as_echo_n "checking for CRYPTO_new_ex_data in -lcrypto... " >&6; } if ${ac_cv_lib_crypto_CRYPTO_new_ex_data+:} false; then : @@ -20031,7 +20035,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by PostgreSQL $as_me 13.11, which was +This file was extended by PostgreSQL $as_me 13.12, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -20102,7 +20106,7 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`" ac_cs_version="\\ -PostgreSQL config.status 13.11 +PostgreSQL config.status 13.12 configured by $0, generated by GNU Autoconf 2.69, with options \\"\$ac_cs_config\\" diff -Nru postgresql-13-13.11/configure.in postgresql-13-13.12/configure.in --- postgresql-13-13.11/configure.in 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/configure.in 2023-08-07 20:11:34.000000000 +0000 @@ -17,7 +17,7 @@ dnl m4_pattern_forbid(^PGAC_)dnl to catch undefined macros -AC_INIT([PostgreSQL], [13.11], [pgsql-bugs@lists.postgresql.org], [], [https://www.postgresql.org/]) +AC_INIT([PostgreSQL], [13.12], [pgsql-bugs@lists.postgresql.org], [], [https://www.postgresql.org/]) m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.69], [], [m4_fatal([Autoconf version 2.69 is required. Untested combinations of 'autoconf' and PostgreSQL versions are not @@ -1258,6 +1258,9 @@ if test "$with_openssl" = yes ; then dnl Order matters! + # Minimum required OpenSSL version is 1.0.1 + AC_DEFINE(OPENSSL_API_COMPAT, [0x10001000L], + [Define to the OpenSSL API version in use. This avoids deprecation warnings from newer OpenSSL versions.]) if test "$PORTNAME" != "win32"; then AC_CHECK_LIB(crypto, CRYPTO_new_ex_data, [], [AC_MSG_ERROR([library 'crypto' is required for OpenSSL])]) AC_CHECK_LIB(ssl, SSL_new, [], [AC_MSG_ERROR([library 'ssl' is required for OpenSSL])]) diff -Nru postgresql-13-13.11/contrib/fuzzystrmatch/expected/fuzzystrmatch.out postgresql-13-13.12/contrib/fuzzystrmatch/expected/fuzzystrmatch.out --- postgresql-13-13.11/contrib/fuzzystrmatch/expected/fuzzystrmatch.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/fuzzystrmatch/expected/fuzzystrmatch.out 2023-08-07 20:11:34.000000000 +0000 @@ -23,6 +23,12 @@ A500 | M626 | 0 (1 row) +SELECT soundex(''), difference('', ''); + soundex | difference +---------+------------ + | 4 +(1 row) + SELECT levenshtein('GUMBO', 'GAMBOL'); levenshtein ------------- diff -Nru postgresql-13-13.11/contrib/fuzzystrmatch/fuzzystrmatch.c postgresql-13-13.12/contrib/fuzzystrmatch/fuzzystrmatch.c --- postgresql-13-13.11/contrib/fuzzystrmatch/fuzzystrmatch.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/fuzzystrmatch/fuzzystrmatch.c 2023-08-07 20:11:34.000000000 +0000 @@ -727,16 +727,14 @@ AssertArg(instr); AssertArg(outstr); - outstr[SOUNDEX_LEN] = '\0'; - /* Skip leading non-alphabetic characters */ - while (!isalpha((unsigned char) instr[0]) && instr[0]) + while (*instr && !isalpha((unsigned char) *instr)) ++instr; - /* No string left */ - if (!instr[0]) + /* If no string left, return all-zeroes buffer */ + if (!*instr) { - outstr[0] = (char) 0; + memset(outstr, '\0', SOUNDEX_LEN + 1); return; } @@ -749,7 +747,7 @@ if (isalpha((unsigned char) *instr) && soundex_code(*instr) != soundex_code(*(instr - 1))) { - *outstr = soundex_code(instr[0]); + *outstr = soundex_code(*instr); if (*outstr != '0') { ++outstr; @@ -766,6 +764,9 @@ ++outstr; ++count; } + + /* And null-terminate */ + *outstr = '\0'; } PG_FUNCTION_INFO_V1(difference); diff -Nru postgresql-13-13.11/contrib/fuzzystrmatch/sql/fuzzystrmatch.sql postgresql-13-13.12/contrib/fuzzystrmatch/sql/fuzzystrmatch.sql --- postgresql-13-13.11/contrib/fuzzystrmatch/sql/fuzzystrmatch.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/fuzzystrmatch/sql/fuzzystrmatch.sql 2023-08-07 20:11:34.000000000 +0000 @@ -6,6 +6,7 @@ SELECT soundex('Anne'), soundex('Ann'), difference('Anne', 'Ann'); SELECT soundex('Anne'), soundex('Andrew'), difference('Anne', 'Andrew'); SELECT soundex('Anne'), soundex('Margaret'), difference('Anne', 'Margaret'); +SELECT soundex(''), difference('', ''); SELECT levenshtein('GUMBO', 'GAMBOL'); diff -Nru postgresql-13-13.11/contrib/hstore/Makefile postgresql-13-13.12/contrib/hstore/Makefile --- postgresql-13-13.11/contrib/hstore/Makefile 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/hstore/Makefile 2023-08-07 20:11:34.000000000 +0000 @@ -20,7 +20,7 @@ HEADERS = hstore.h -REGRESS = hstore +REGRESS = hstore hstore_utf8 ifdef USE_PGXS PG_CONFIG = pg_config diff -Nru postgresql-13-13.11/contrib/hstore/expected/hstore_utf8.out postgresql-13-13.12/contrib/hstore/expected/hstore_utf8.out --- postgresql-13-13.11/contrib/hstore/expected/hstore_utf8.out 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/contrib/hstore/expected/hstore_utf8.out 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,36 @@ +/* + * This test must be run in a database with UTF-8 encoding, + * because other encodings don't support all the characters used. + */ +SELECT getdatabaseencoding() <> 'UTF8' + AS skip_test \gset +\if :skip_test +\quit +\endif +SET client_encoding = utf8; +-- UTF-8 locale bug on macOS: isspace(0x85) returns true. \u0105 encodes +-- as 0xc4 0x85 in UTF-8; the 0x85 was interpreted here as a whitespace. +SELECT E'key\u0105=>value\u0105'::hstore; + hstore +------------------ + "keyą"=>"valueą" +(1 row) + +SELECT 'keyą=>valueą'::hstore; + hstore +------------------ + "keyą"=>"valueą" +(1 row) + +SELECT 'ą=>ą'::hstore; + hstore +---------- + "ą"=>"ą" +(1 row) + +SELECT 'keyąfoo=>valueą'::hstore; + hstore +--------------------- + "keyąfoo"=>"valueą" +(1 row) + diff -Nru postgresql-13-13.11/contrib/hstore/expected/hstore_utf8_1.out postgresql-13-13.12/contrib/hstore/expected/hstore_utf8_1.out --- postgresql-13-13.11/contrib/hstore/expected/hstore_utf8_1.out 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/contrib/hstore/expected/hstore_utf8_1.out 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,8 @@ +/* + * This test must be run in a database with UTF-8 encoding, + * because other encodings don't support all the characters used. + */ +SELECT getdatabaseencoding() <> 'UTF8' + AS skip_test \gset +\if :skip_test +\quit diff -Nru postgresql-13-13.11/contrib/hstore/hstore_io.c postgresql-13-13.12/contrib/hstore/hstore_io.c --- postgresql-13-13.11/contrib/hstore/hstore_io.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/hstore/hstore_io.c 2023-08-07 20:11:34.000000000 +0000 @@ -12,6 +12,7 @@ #include "hstore.h" #include "lib/stringinfo.h" #include "libpq/pqformat.h" +#include "parser/scansup.h" #include "utils/builtins.h" #include "utils/json.h" #include "utils/jsonb.h" @@ -86,7 +87,7 @@ { st = GV_WAITESCIN; } - else if (!isspace((unsigned char) *(state->ptr))) + else if (!scanner_isspace((unsigned char) *(state->ptr))) { *(state->cur) = *(state->ptr); state->cur++; @@ -109,7 +110,7 @@ state->ptr--; return true; } - else if (isspace((unsigned char) *(state->ptr))) + else if (scanner_isspace((unsigned char) *(state->ptr))) { return true; } @@ -217,7 +218,7 @@ { elog(ERROR, "Unexpected end of string"); } - else if (!isspace((unsigned char) *(state->ptr))) + else if (!scanner_isspace((unsigned char) *(state->ptr))) { elog(ERROR, "Syntax error near '%c' at position %d", *(state->ptr), (int32) (state->ptr - state->begin)); } @@ -265,7 +266,7 @@ { return; } - else if (!isspace((unsigned char) *(state->ptr))) + else if (!scanner_isspace((unsigned char) *(state->ptr))) { elog(ERROR, "Syntax error near '%c' at position %d", *(state->ptr), (int32) (state->ptr - state->begin)); } diff -Nru postgresql-13-13.11/contrib/hstore/sql/hstore_utf8.sql postgresql-13-13.12/contrib/hstore/sql/hstore_utf8.sql --- postgresql-13-13.11/contrib/hstore/sql/hstore_utf8.sql 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/contrib/hstore/sql/hstore_utf8.sql 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,19 @@ +/* + * This test must be run in a database with UTF-8 encoding, + * because other encodings don't support all the characters used. + */ + +SELECT getdatabaseencoding() <> 'UTF8' + AS skip_test \gset +\if :skip_test +\quit +\endif + +SET client_encoding = utf8; + +-- UTF-8 locale bug on macOS: isspace(0x85) returns true. \u0105 encodes +-- as 0xc4 0x85 in UTF-8; the 0x85 was interpreted here as a whitespace. +SELECT E'key\u0105=>value\u0105'::hstore; +SELECT 'keyą=>valueą'::hstore; +SELECT 'ą=>ą'::hstore; +SELECT 'keyąfoo=>valueą'::hstore; diff -Nru postgresql-13-13.11/contrib/intarray/_int_gist.c postgresql-13-13.12/contrib/intarray/_int_gist.c --- postgresql-13-13.11/contrib/intarray/_int_gist.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/intarray/_int_gist.c 2023-08-07 20:11:34.000000000 +0000 @@ -174,8 +174,10 @@ PREPAREARR(r); if (ARRNELEMS(r) >= 2 * num_ranges) - elog(NOTICE, "input array is too big (%d maximum allowed, %d current), use gist__intbig_ops opclass instead", - 2 * num_ranges - 1, ARRNELEMS(r)); + ereport(ERROR, + (errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED), + errmsg("input array is too big (%d maximum allowed, %d current), use gist__intbig_ops opclass instead", + 2 * num_ranges - 1, ARRNELEMS(r)))); retval = palloc(sizeof(GISTENTRY)); gistentryinit(*retval, PointerGetDatum(r), @@ -263,7 +265,8 @@ lenr = internal_size(dr, len); if (lenr < 0 || lenr > MAXNUMELTS) ereport(ERROR, - (errmsg("data is too sparse, recreate index using gist__intbig_ops opclass instead"))); + (errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED), + errmsg("data is too sparse, recreate index using gist__intbig_ops opclass instead"))); r = resize_intArrayType(r, len); retval = palloc(sizeof(GISTENTRY)); @@ -325,7 +328,8 @@ lenr = internal_size(din, lenin); if (lenr < 0 || lenr > MAXNUMELTS) ereport(ERROR, - (errmsg("compressed array is too big, recreate index using gist__intbig_ops opclass instead"))); + (errcode(ERRCODE_PROGRAM_LIMIT_EXCEEDED), + errmsg("compressed array is too big, recreate index using gist__intbig_ops opclass instead"))); r = new_intArrayType(lenr); dr = ARRPTR(r); diff -Nru postgresql-13-13.11/contrib/intarray/_intbig_gist.c postgresql-13-13.12/contrib/intarray/_intbig_gist.c --- postgresql-13-13.11/contrib/intarray/_intbig_gist.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/intarray/_intbig_gist.c 2023-08-07 20:11:34.000000000 +0000 @@ -174,9 +174,6 @@ entry->rel, entry->page, entry->offset, false); - if (in != DatumGetArrayTypeP(entry->key)) - pfree(in); - PG_RETURN_POINTER(retval); } else if (!ISALLTRUE(DatumGetPointer(entry->key))) diff -Nru postgresql-13-13.11/contrib/intarray/expected/_int.out postgresql-13-13.12/contrib/intarray/expected/_int.out --- postgresql-13-13.11/contrib/intarray/expected/_int.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/intarray/expected/_int.out 2023-08-07 20:11:34.000000000 +0000 @@ -547,6 +547,8 @@ 6343 (1 row) +INSERT INTO test__int SELECT array(SELECT x FROM generate_series(1, 1001) x); -- should fail +ERROR: input array is too big (199 maximum allowed, 1001 current), use gist__intbig_ops opclass instead DROP INDEX text_idx; CREATE INDEX text_idx on test__int using gist (a gist__int_ops(numranges = 0)); ERROR: value 0 out of bounds for option "numranges" diff -Nru postgresql-13-13.11/contrib/intarray/sql/_int.sql postgresql-13-13.12/contrib/intarray/sql/_int.sql --- postgresql-13-13.11/contrib/intarray/sql/_int.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/intarray/sql/_int.sql 2023-08-07 20:11:34.000000000 +0000 @@ -110,6 +110,8 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; SELECT count(*) from test__int WHERE a @@ '!20 & !21'; +INSERT INTO test__int SELECT array(SELECT x FROM generate_series(1, 1001) x); -- should fail + DROP INDEX text_idx; CREATE INDEX text_idx on test__int using gist (a gist__int_ops(numranges = 0)); CREATE INDEX text_idx on test__int using gist (a gist__int_ops(numranges = 253)); diff -Nru postgresql-13-13.11/contrib/postgres_fdw/expected/postgres_fdw.out postgresql-13-13.12/contrib/postgres_fdw/expected/postgres_fdw.out --- postgresql-13-13.11/contrib/postgres_fdw/expected/postgres_fdw.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/postgres_fdw/expected/postgres_fdw.out 2023-08-07 20:11:34.000000000 +0000 @@ -2188,6 +2188,32 @@ 1 (10 rows) +-- join with pseudoconstant quals, not pushed down. +EXPLAIN (VERBOSE, COSTS OFF) +SELECT t1.c1, t2.c1 FROM ft1 t1 JOIN ft2 t2 ON (t1.c1 = t2.c1 AND CURRENT_USER = SESSION_USER) ORDER BY t1.c3, t1.c1 OFFSET 100 LIMIT 10; + QUERY PLAN +------------------------------------------------------------------------------- + Limit + Output: t1.c1, t2.c1, t1.c3 + -> Sort + Output: t1.c1, t2.c1, t1.c3 + Sort Key: t1.c3, t1.c1 + -> Result + Output: t1.c1, t2.c1, t1.c3 + One-Time Filter: (CURRENT_USER = SESSION_USER) + -> Hash Join + Output: t1.c1, t1.c3, t2.c1 + Hash Cond: (t2.c1 = t1.c1) + -> Foreign Scan on public.ft2 t2 + Output: t2.c1 + Remote SQL: SELECT "C 1" FROM "S 1"."T 1" + -> Hash + Output: t1.c1, t1.c3 + -> Foreign Scan on public.ft1 t1 + Output: t1.c1, t1.c3 + Remote SQL: SELECT "C 1", c3 FROM "S 1"."T 1" +(19 rows) + -- non-Var items in targetlist of the nullable rel of a join preventing -- push-down in some cases -- unable to push {ft1, ft2} diff -Nru postgresql-13-13.11/contrib/postgres_fdw/sql/postgres_fdw.sql postgresql-13-13.12/contrib/postgres_fdw/sql/postgres_fdw.sql --- postgresql-13-13.11/contrib/postgres_fdw/sql/postgres_fdw.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/contrib/postgres_fdw/sql/postgres_fdw.sql 2023-08-07 20:11:34.000000000 +0000 @@ -583,6 +583,9 @@ EXPLAIN (VERBOSE, COSTS OFF) SELECT t1."C 1" FROM "S 1"."T 1" t1, LATERAL (SELECT DISTINCT t2.c1, t3.c1 FROM ft1 t2, ft2 t3 WHERE t2.c1 = t3.c1 AND t2.c2 = t1.c2) q ORDER BY t1."C 1" OFFSET 10 LIMIT 10; SELECT t1."C 1" FROM "S 1"."T 1" t1, LATERAL (SELECT DISTINCT t2.c1, t3.c1 FROM ft1 t2, ft2 t3 WHERE t2.c1 = t3.c1 AND t2.c2 = t1.c2) q ORDER BY t1."C 1" OFFSET 10 LIMIT 10; +-- join with pseudoconstant quals, not pushed down. +EXPLAIN (VERBOSE, COSTS OFF) +SELECT t1.c1, t2.c1 FROM ft1 t1 JOIN ft2 t2 ON (t1.c1 = t2.c1 AND CURRENT_USER = SESSION_USER) ORDER BY t1.c3, t1.c1 OFFSET 100 LIMIT 10; -- non-Var items in targetlist of the nullable rel of a join preventing -- push-down in some cases diff -Nru postgresql-13-13.11/debian/changelog postgresql-13-13.12/debian/changelog --- postgresql-13-13.11/debian/changelog 2023-05-10 18:35:39.000000000 +0000 +++ postgresql-13-13.12/debian/changelog 2023-10-01 19:59:50.000000000 +0000 @@ -1,3 +1,26 @@ +postgresql-13 (13.12-0+deb11u1) bullseye; urgency=medium + + * New upstream version. + + + Prevent CREATE SCHEMA from defeating changes in search_path + (Report and fix by Alexander Lakhin, CVE-2023-2454) + Within a CREATE SCHEMA command, objects in the prevailing search_path, + as well as those in the newly-created schema, would be visible even + within a called function or script that attempted to set a secure + search_path. This could allow any user having permission to create a + schema to hijack the privileges of a security definer function or + extension script. + + + Enforce row-level security policies correctly after inlining a + set-returning function (Report by Wolfgang Walther, CVE-2023-2455) + If a set-returning SQL-language function refers to a table having + row-level security policies, and it can be inlined into a calling query, + those RLS policies would not get enforced properly in some cases + involving re-using a cached plan under a different role. This could + allow a user to see or modify rows that should have been invisible. + + -- Christoph Berg Sun, 01 Oct 2023 21:59:50 +0200 + postgresql-13 (13.11-0+deb11u1) bullseye-security; urgency=medium * New upstream version. diff -Nru postgresql-13-13.11/doc/src/sgml/catalogs.sgml postgresql-13-13.12/doc/src/sgml/catalogs.sgml --- postgresql-13-13.11/doc/src/sgml/catalogs.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/catalogs.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -2951,7 +2951,8 @@ Sets maximum number of concurrent connections that can be made - to this database. -1 means no limit. + to this database. -1 means no limit, -2 indicates the database is + invalid. diff -Nru postgresql-13-13.11/doc/src/sgml/custom-scan.sgml postgresql-13-13.12/doc/src/sgml/custom-scan.sgml --- postgresql-13-13.11/doc/src/sgml/custom-scan.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/custom-scan.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -83,7 +83,7 @@ by nodeToString, so that debugging routines that attempt to print the custom path will work as designed. methods must point to a (usually statically allocated) object implementing the required - custom path methods, of which there is currently only one. + custom path methods, which are further detailed below. @@ -123,6 +123,23 @@ be a CustomScan object, which the callback must allocate and initialize. See for more details. + + + +List *(*ReparameterizeCustomPathByChild) (PlannerInfo *root, + List *custom_private, + RelOptInfo *child_rel); + + This callback is called while converting a path parameterized by the + top-most parent of the given child relation child_rel + to be parameterized by the child relation. The callback is used to + reparameterize any paths or translate any expression nodes saved in the + given custom_private member of a + CustomPath. The callback may use + reparameterize_path_by_child, + adjust_appendrel_attrs or + adjust_appendrel_attrs_multilevel as required. + diff -Nru postgresql-13-13.11/doc/src/sgml/func.sgml postgresql-13-13.12/doc/src/sgml/func.sgml --- postgresql-13-13.11/doc/src/sgml/func.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/func.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -20352,7 +20352,7 @@ The right-hand side is a parenthesized list - of scalar expressions. The result is true if the left-hand expression's + of expressions. The result is true if the left-hand expression's result is equal to any of the right-hand expressions. This is a shorthand notation for @@ -20383,7 +20383,7 @@ The right-hand side is a parenthesized list - of scalar expressions. The result is true if the left-hand expression's + of expressions. The result is true if the left-hand expression's result is unequal to all of the right-hand expressions. This is a shorthand notation for @@ -20494,26 +20494,24 @@ Each side is a row constructor, as described in . - The two row values must have the same number of fields. - Each side is evaluated and they are compared row-wise. Row constructor - comparisons are allowed when the operator is + The two row constructors must have the same number of fields. + The given operator is applied to each pair + of corresponding fields. (Since the fields could be of different + types, this means that a different specific operator could be selected + for each pair.) + All the selected operators must be members of some B-tree operator + class, or be the negator of an = member of a B-tree + operator class, meaning that row constructor comparison is only + possible when the operator is =, <>, <, <=, - > or - >=. - Every row element must be of a type which has a default B-tree operator - class or the attempted comparison may generate an error. + >, or + >=, + or has semantics similar to one of these. - - - Errors related to the number or types of elements might not occur if - the comparison is resolved using earlier columns. - - - The = and <> cases work slightly differently from the others. Two rows are considered diff -Nru postgresql-13-13.11/doc/src/sgml/history.sgml postgresql-13-13.12/doc/src/sgml/history.sgml --- postgresql-13-13.11/doc/src/sgml/history.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/history.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -12,7 +12,7 @@ The object-relational database management system now known as PostgreSQL is derived from the POSTGRES package written at the - University of California at Berkeley. With over two decades of + University of California at Berkeley. With decades of development behind it, PostgreSQL is now the most advanced open-source database available anywhere. diff -Nru postgresql-13-13.11/doc/src/sgml/html/acronyms.html postgresql-13-13.12/doc/src/sgml/html/acronyms.html --- postgresql-13-13.11/doc/src/sgml/html/acronyms.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/acronyms.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix L. Acronyms
Appendix L. Acronyms
Prev UpPart VIII. AppendixesHome Next

Appendix L. Acronyms

+Appendix L. Acronyms

Appendix L. Acronyms
Prev UpPart VIII. AppendixesHome Next

Appendix L. Acronyms

This is a list of acronyms commonly used in the PostgreSQL documentation and in discussions about PostgreSQL. @@ -134,7 +134,7 @@ Pluggable Authentication Modules

PGSQL

- PostgreSQL + PostgreSQL

PGXS

PostgreSQL Extension System

PID

@@ -209,4 +209,4 @@ Extensible Markup Language

-

Prev Up Next
Appendix K. PostgreSQL Limits Home Appendix M. Glossary
\ No newline at end of file +

Prev Up Next
Appendix K. PostgreSQL Limits Home Appendix M. Glossary
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/admin.html postgresql-13-13.12/doc/src/sgml/html/admin.html --- postgresql-13-13.11/doc/src/sgml/html/admin.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/admin.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Part III. Server Administration
Part III. Server Administration
Prev UpPostgreSQL 13.11 DocumentationHome Next

Part III. Server Administration

+Part III. Server Administration

Part III. Server Administration
Prev UpPostgreSQL 13.12 DocumentationHome Next

Part III. Server Administration

This part covers topics that are of interest to a PostgreSQL database administrator. This includes installation of the software, set up and configuration of the @@ -23,4 +23,4 @@ the PostgreSQL database system. Readers are encouraged to look at Part I and Part II for additional information.

Table of Contents

16. Installation from Source Code
16.1. Short Version
16.2. Requirements
16.3. Getting the Source
16.4. Installation Procedure
16.5. Post-Installation Setup
16.6. Supported Platforms
16.7. Platform-Specific Notes
17. Installation from Source Code on Windows
17.1. Building with Visual C++ or the - Microsoft Windows SDK
18. Server Setup and Operation
18.1. The PostgreSQL User Account
18.2. Creating a Database Cluster
18.3. Starting the Database Server
18.4. Managing Kernel Resources
18.5. Shutting Down the Server
18.6. Upgrading a PostgreSQL Cluster
18.7. Preventing Server Spoofing
18.8. Encryption Options
18.9. Secure TCP/IP Connections with SSL
18.10. Secure TCP/IP Connections with GSSAPI Encryption
18.11. Secure TCP/IP Connections with SSH Tunnels
18.12. Registering Event Log on Windows
19. Server Configuration
19.1. Setting Parameters
19.2. File Locations
19.3. Connections and Authentication
19.4. Resource Consumption
19.5. Write Ahead Log
19.6. Replication
19.7. Query Planning
19.8. Error Reporting and Logging
19.9. Run-time Statistics
19.10. Automatic Vacuuming
19.11. Client Connection Defaults
19.12. Lock Management
19.13. Version and Platform Compatibility
19.14. Error Handling
19.15. Preset Options
19.16. Customized Options
19.17. Developer Options
19.18. Short Options
20. Client Authentication
20.1. The pg_hba.conf File
20.2. User Name Maps
20.3. Authentication Methods
20.4. Trust Authentication
20.5. Password Authentication
20.6. GSSAPI Authentication
20.7. SSPI Authentication
20.8. Ident Authentication
20.9. Peer Authentication
20.10. LDAP Authentication
20.11. RADIUS Authentication
20.12. Certificate Authentication
20.13. PAM Authentication
20.14. BSD Authentication
20.15. Authentication Problems
21. Database Roles
21.1. Database Roles
21.2. Role Attributes
21.3. Role Membership
21.4. Dropping Roles
21.5. Default Roles
21.6. Function Security
22. Managing Databases
22.1. Overview
22.2. Creating a Database
22.3. Template Databases
22.4. Database Configuration
22.5. Destroying a Database
22.6. Tablespaces
23. Localization
23.1. Locale Support
23.2. Collation Support
23.3. Character Set Support
24. Routine Database Maintenance Tasks
24.1. Routine Vacuuming
24.2. Routine Reindexing
24.3. Log File Maintenance
25. Backup and Restore
25.1. SQL Dump
25.2. File System Level Backup
25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
26. High Availability, Load Balancing, and Replication
26.1. Comparison of Different Solutions
26.2. Log-Shipping Standby Servers
26.3. Failover
26.4. Alternative Method for Log Shipping
26.5. Hot Standby
27. Monitoring Database Activity
27.1. Standard Unix Tools
27.2. The Statistics Collector
27.3. Viewing Locks
27.4. Progress Reporting
27.5. Dynamic Tracing
28. Monitoring Disk Usage
28.1. Determining Disk Usage
28.2. Disk Full Failure
29. Reliability and the Write-Ahead Log
29.1. Reliability
29.2. Write-Ahead Logging (WAL)
29.3. Asynchronous Commit
29.4. WAL Configuration
29.5. WAL Internals
30. Logical Replication
30.1. Publication
30.2. Subscription
30.3. Conflicts
30.4. Restrictions
30.5. Architecture
30.6. Monitoring
30.7. Security
30.8. Configuration Settings
30.9. Quick Setup
31. Just-in-Time Compilation (JIT)
31.1. What Is JIT compilation?
31.2. When to JIT?
31.3. Configuration
31.4. Extensibility
32. Regression Tests
32.1. Running the Tests
32.2. Test Evaluation
32.3. Variant Comparison Files
32.4. TAP Tests
32.5. Test Coverage Examination
Prev Up Next
15.4. Parallel Safety Home Chapter 16. Installation from Source Code
\ No newline at end of file + Microsoft Windows SDK
18. Server Setup and Operation
18.1. The PostgreSQL User Account
18.2. Creating a Database Cluster
18.3. Starting the Database Server
18.4. Managing Kernel Resources
18.5. Shutting Down the Server
18.6. Upgrading a PostgreSQL Cluster
18.7. Preventing Server Spoofing
18.8. Encryption Options
18.9. Secure TCP/IP Connections with SSL
18.10. Secure TCP/IP Connections with GSSAPI Encryption
18.11. Secure TCP/IP Connections with SSH Tunnels
18.12. Registering Event Log on Windows
19. Server Configuration
19.1. Setting Parameters
19.2. File Locations
19.3. Connections and Authentication
19.4. Resource Consumption
19.5. Write Ahead Log
19.6. Replication
19.7. Query Planning
19.8. Error Reporting and Logging
19.9. Run-time Statistics
19.10. Automatic Vacuuming
19.11. Client Connection Defaults
19.12. Lock Management
19.13. Version and Platform Compatibility
19.14. Error Handling
19.15. Preset Options
19.16. Customized Options
19.17. Developer Options
19.18. Short Options
20. Client Authentication
20.1. The pg_hba.conf File
20.2. User Name Maps
20.3. Authentication Methods
20.4. Trust Authentication
20.5. Password Authentication
20.6. GSSAPI Authentication
20.7. SSPI Authentication
20.8. Ident Authentication
20.9. Peer Authentication
20.10. LDAP Authentication
20.11. RADIUS Authentication
20.12. Certificate Authentication
20.13. PAM Authentication
20.14. BSD Authentication
20.15. Authentication Problems
21. Database Roles
21.1. Database Roles
21.2. Role Attributes
21.3. Role Membership
21.4. Dropping Roles
21.5. Default Roles
21.6. Function Security
22. Managing Databases
22.1. Overview
22.2. Creating a Database
22.3. Template Databases
22.4. Database Configuration
22.5. Destroying a Database
22.6. Tablespaces
23. Localization
23.1. Locale Support
23.2. Collation Support
23.3. Character Set Support
24. Routine Database Maintenance Tasks
24.1. Routine Vacuuming
24.2. Routine Reindexing
24.3. Log File Maintenance
25. Backup and Restore
25.1. SQL Dump
25.2. File System Level Backup
25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
26. High Availability, Load Balancing, and Replication
26.1. Comparison of Different Solutions
26.2. Log-Shipping Standby Servers
26.3. Failover
26.4. Alternative Method for Log Shipping
26.5. Hot Standby
27. Monitoring Database Activity
27.1. Standard Unix Tools
27.2. The Statistics Collector
27.3. Viewing Locks
27.4. Progress Reporting
27.5. Dynamic Tracing
28. Monitoring Disk Usage
28.1. Determining Disk Usage
28.2. Disk Full Failure
29. Reliability and the Write-Ahead Log
29.1. Reliability
29.2. Write-Ahead Logging (WAL)
29.3. Asynchronous Commit
29.4. WAL Configuration
29.5. WAL Internals
30. Logical Replication
30.1. Publication
30.2. Subscription
30.3. Conflicts
30.4. Restrictions
30.5. Architecture
30.6. Monitoring
30.7. Security
30.8. Configuration Settings
30.9. Quick Setup
31. Just-in-Time Compilation (JIT)
31.1. What Is JIT compilation?
31.2. When to JIT?
31.3. Configuration
31.4. Extensibility
32. Regression Tests
32.1. Running the Tests
32.2. Test Evaluation
32.3. Variant Comparison Files
32.4. TAP Tests
32.5. Test Coverage Examination
Prev Up Next
15.4. Parallel Safety Home Chapter 16. Installation from Source Code
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/adminpack.html postgresql-13-13.12/doc/src/sgml/html/adminpack.html --- postgresql-13-13.11/doc/src/sgml/html/adminpack.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/adminpack.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.1. adminpack
F.1. adminpack
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.1. adminpack

+F.1. adminpack

F.1. adminpack
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.1. adminpack

adminpack provides a number of support functions which pgAdmin and other administration and management tools can use to provide additional functionality, such as remote management @@ -85,4 +85,4 @@ directory. The log_filename parameter must have its default setting (postgresql-%Y-%m-%d_%H%M%S.log) to use this function. -

Prev Up Next
Appendix F. Additional Supplied Modules Home F.2. amcheck
\ No newline at end of file +

Prev Up Next
Appendix F. Additional Supplied Modules Home F.2. amcheck
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/amcheck.html postgresql-13-13.12/doc/src/sgml/html/amcheck.html --- postgresql-13-13.11/doc/src/sgml/html/amcheck.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/amcheck.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.2. amcheck
F.2. amcheck
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.2. amcheck

F.2.1. Functions
F.2.2. Optional heapallindexed Verification
F.2.3. Using amcheck Effectively
F.2.4. Repairing Corruption

+F.2. amcheck

F.2. amcheck
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.2. amcheck

F.2.1. Functions
F.2.2. Optional heapallindexed Verification
F.2.3. Using amcheck Effectively
F.2.4. Repairing Corruption

The amcheck module provides functions that allow you to verify the logical consistency of the structure of relations. If the structure appears to be valid, no error is raised. @@ -264,4 +264,4 @@ an invariant violation should be sought. pageinspect may play a useful role in diagnosing corruption that amcheck detects. A REINDEX may not be effective in repairing corruption. -

Prev Up Next
F.1. adminpack Home F.3. auth_delay
\ No newline at end of file +

Prev Up Next
F.1. adminpack Home F.3. auth_delay
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-clusterdb.html postgresql-13-13.12/doc/src/sgml/html/app-clusterdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-clusterdb.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-clusterdb.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -clusterdb
clusterdb
Prev UpPostgreSQL Client ApplicationsHome Next

clusterdb

clusterdb — cluster a PostgreSQL database

Synopsis

clusterdb [connection-option...] [ --verbose | -v ] +clusterdb

clusterdb
Prev UpPostgreSQL Client ApplicationsHome Next

clusterdb

clusterdb — cluster a PostgreSQL database

Synopsis

clusterdb [connection-option...] [ --verbose | -v ] [ --table | -t table @@ -119,4 +119,4 @@ xyzzy: 

 $ clusterdb --table=foo xyzzy
-

See Also

CLUSTER
Prev Up Next
PostgreSQL Client Applications Home createdb
\ No newline at end of file +

See Also

CLUSTER
Prev Up Next
PostgreSQL Client Applications Home createdb
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-createdb.html postgresql-13-13.12/doc/src/sgml/html/app-createdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-createdb.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-createdb.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -createdb
createdb
Prev UpPostgreSQL Client ApplicationsHome Next

createdb

createdb — create a new PostgreSQL database

Synopsis

createdb [connection-option...] [option...] [dbname +createdb

createdb
Prev UpPostgreSQL Client ApplicationsHome Next

createdb

createdb — create a new PostgreSQL database

Synopsis

createdb [connection-option...] [option...] [dbname [description]]

Description

createdb creates a new PostgreSQL database. @@ -138,4 +138,4 @@ 

 $ createdb -p 5000 -h eden -T template0 -e demo
 CREATE DATABASE demo TEMPLATE template0;
-
Prev Up Next
clusterdb Home createuser
\ No newline at end of file +
Prev Up Next
clusterdb Home createuser
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-createuser.html postgresql-13-13.12/doc/src/sgml/html/app-createuser.html --- postgresql-13-13.11/doc/src/sgml/html/app-createuser.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-createuser.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -createuser
createuser
Prev UpPostgreSQL Client ApplicationsHome Next

createuser

createuser — define a new PostgreSQL user account

Synopsis

createuser [connection-option...] [option...] [username]

Description

+createuser

createuser
Prev UpPostgreSQL Client ApplicationsHome Next

createuser

createuser — define a new PostgreSQL user account

Synopsis

createuser [connection-option...] [option...] [username]

Description

createuser creates a new PostgreSQL user (or more precisely, a role). Only superusers and users with CREATEROLE privilege can create @@ -187,4 +187,4 @@ In the above example, the new password isn't actually echoed when typed, but we show what was typed for clarity. As you see, the password is encrypted before it is sent to the client. -

Prev Up Next
createdb Home dropdb
\ No newline at end of file +

Prev Up Next
createdb Home dropdb
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-dropdb.html postgresql-13-13.12/doc/src/sgml/html/app-dropdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-dropdb.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-dropdb.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -dropdb
dropdb
Prev UpPostgreSQL Client ApplicationsHome Next

dropdb

dropdb — remove a PostgreSQL database

Synopsis

dropdb [connection-option...] [option...] dbname

Description

+dropdb

dropdb
Prev UpPostgreSQL Client ApplicationsHome Next

dropdb

dropdb — remove a PostgreSQL database

Synopsis

dropdb [connection-option...] [option...] dbname

Description

dropdb destroys an existing PostgreSQL database. The user who executes this command must be a database @@ -108,4 +108,4 @@ Database "demo" will be permanently deleted. Are you sure? (y/n) y DROP DATABASE demo; -

Prev Up Next
createuser Home dropuser
\ No newline at end of file +
Prev Up Next
createuser Home dropuser
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-dropuser.html postgresql-13-13.12/doc/src/sgml/html/app-dropuser.html --- postgresql-13-13.11/doc/src/sgml/html/app-dropuser.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-dropuser.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -dropuser
dropuser
Prev UpPostgreSQL Client ApplicationsHome Next

dropuser

dropuser — remove a PostgreSQL user account

Synopsis

dropuser [connection-option...] [option...] [username]

Description

+dropuser

dropuser
Prev UpPostgreSQL Client ApplicationsHome Next

dropuser

dropuser — remove a PostgreSQL user account

Synopsis

dropuser [connection-option...] [option...] [username]

Description

dropuser removes an existing PostgreSQL user. Only superusers and users with the CREATEROLE privilege can @@ -100,4 +100,4 @@ Role "joe" will be permanently removed. Are you sure? (y/n) y DROP ROLE joe; -

Prev Up Next
dropdb Home ecpg
\ No newline at end of file +
Prev Up Next
dropdb Home ecpg
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-ecpg.html postgresql-13-13.12/doc/src/sgml/html/app-ecpg.html --- postgresql-13-13.11/doc/src/sgml/html/app-ecpg.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-ecpg.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -ecpg
ecpg
Prev UpPostgreSQL Client ApplicationsHome Next

ecpg

ecpg — embedded SQL C preprocessor

Synopsis

ecpg [option...] file...

Description

+ecpg

ecpg
Prev UpPostgreSQL Client ApplicationsHome Next

ecpg

ecpg — embedded SQL C preprocessor

Synopsis

ecpg [option...] file...

Description

ecpg is the embedded SQL preprocessor for C programs. It converts C programs with embedded SQL statements to normal C code by replacing the SQL invocations with special @@ -103,4 +103,4 @@ ecpg prog1.pgc cc -I/usr/local/pgsql/include -c prog1.c cc -o prog1 prog1.o -L/usr/local/pgsql/lib -lecpg -

Prev Up Next
dropuser Home pg_basebackup
\ No newline at end of file +
Prev Up Next
dropuser Home pg_basebackup
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-initdb.html postgresql-13-13.12/doc/src/sgml/html/app-initdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-initdb.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-initdb.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -initdb
initdb
Prev UpPostgreSQL Server ApplicationsHome Next

initdb

initdb — create a new PostgreSQL database cluster

Synopsis

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

Description

+initdb

initdb
Prev UpPostgreSQL Server ApplicationsHome Next

initdb

initdb — create a new PostgreSQL database cluster

Synopsis

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

Description

initdb creates a new PostgreSQL database cluster. A database cluster is a collection of databases that are managed by a single @@ -210,4 +210,4 @@

Notes

initdb can also be invoked via pg_ctl initdb. -

See Also

pg_ctl, postgres
Prev Up Next
PostgreSQL Server Applications Home pg_archivecleanup
\ No newline at end of file +

See Also

pg_ctl, postgres
Prev Up Next
PostgreSQL Server Applications Home pg_archivecleanup
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pg-ctl.html postgresql-13-13.12/doc/src/sgml/html/app-pg-ctl.html --- postgresql-13-13.11/doc/src/sgml/html/app-pg-ctl.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pg-ctl.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_ctl
pg_ctl
Prev UpPostgreSQL Server ApplicationsHome Next

pg_ctl

pg_ctl — initialize, start, stop, or control a PostgreSQL server

Synopsis

pg_ctl init[db] [-D datadir] [-s] [-o initdb-options]

pg_ctl start [-D datadir] [-l filename] [-W] [-t seconds] [-s] [-o options] [-p path] [-c]

pg_ctl stop [-D datadir] [-m +pg_ctl

pg_ctl
Prev UpPostgreSQL Server ApplicationsHome Next

pg_ctl

pg_ctl — initialize, start, stop, or control a PostgreSQL server

Synopsis

pg_ctl init[db] [-D datadir] [-s] [-o initdb-options]

pg_ctl start [-D datadir] [-l filename] [-W] [-t seconds] [-s] [-o options] [-p path] [-c]

pg_ctl stop [-D datadir] [-m s[mart] | f[ast] | i[mmediate] ] [-W] [-t seconds] [-s]

pg_ctl restart [-D datadir] [-m s[mart] | f[ast] | i[mmediate] @@ -285,4 +285,4 @@ /usr/local/pgsql/bin/postgres "-D" "/usr/local/pgsql/data" "-p" "5433" "-B" "128"

The second line is the command that would be invoked in restart mode. -

See Also

initdb, postgres
Prev Up Next
pg_controldata Home pg_resetwal
\ No newline at end of file +

See Also

initdb, postgres
Prev Up Next
pg_controldata Home pg_resetwal
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pg-dumpall.html postgresql-13-13.12/doc/src/sgml/html/app-pg-dumpall.html --- postgresql-13-13.11/doc/src/sgml/html/app-pg-dumpall.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pg-dumpall.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_dumpall
pg_dumpall
Prev UpPostgreSQL Client ApplicationsHome Next

pg_dumpall

pg_dumpall — extract a PostgreSQL database cluster into a script file

Synopsis

pg_dumpall [connection-option...] [option...]

Description

+pg_dumpall

pg_dumpall
Prev UpPostgreSQL Client ApplicationsHome Next

pg_dumpall

pg_dumpall — extract a PostgreSQL database cluster into a script file

Synopsis

pg_dumpall [connection-option...] [option...]

Description

pg_dumpall is a utility for writing out (“dumping”) all PostgreSQL databases of a cluster into one script file. The script file contains @@ -347,4 +347,4 @@

See Also

Check pg_dump for details on possible error conditions. -

Prev Up Next
pg_dump Home pg_isready
\ No newline at end of file +

Prev Up Next
pg_dump Home pg_isready
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pg-isready.html postgresql-13-13.12/doc/src/sgml/html/app-pg-isready.html --- postgresql-13-13.11/doc/src/sgml/html/app-pg-isready.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pg-isready.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_isready
pg_isready
Prev UpPostgreSQL Client ApplicationsHome Next

pg_isready

pg_isready — check the connection status of a PostgreSQL server

Synopsis

pg_isready [connection-option...] [option...]

Description

+pg_isready

pg_isready
Prev UpPostgreSQL Client ApplicationsHome Next

pg_isready

pg_isready — check the connection status of a PostgreSQL server

Synopsis

pg_isready [connection-option...] [option...]

Description

pg_isready is a utility for checking the connection status of a PostgreSQL database server. The exit status specifies the result of the connection check. @@ -76,4 +76,4 @@ $ echo $? 2

-

Prev Up Next
pg_dumpall Home pg_receivewal
\ No newline at end of file +

Prev Up Next
pg_dumpall Home pg_receivewal
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgbasebackup.html postgresql-13-13.12/doc/src/sgml/html/app-pgbasebackup.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgbasebackup.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgbasebackup.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -pg_basebackup
pg_basebackup
Prev UpPostgreSQL Client ApplicationsHome Next

pg_basebackup

pg_basebackup — take a base backup of a PostgreSQL cluster

Synopsis

pg_basebackup [option...]

Description

+pg_basebackup

pg_basebackup
Prev UpPostgreSQL Client ApplicationsHome Next

pg_basebackup

pg_basebackup — take a base backup of a PostgreSQL cluster

Synopsis

pg_basebackup [option...]

Description

pg_basebackup is used to take a base backup of a running PostgreSQL database cluster. The backup is taken without affecting other clients of the database, and can be used @@ -486,4 +486,4 @@ to ./backup/ts: 

 $ pg_basebackup -D backup/data -T /opt/ts=$(pwd)/backup/ts
-

See Also

pg_dump
Prev Up Next
ecpg Home pgbench
\ No newline at end of file +

See Also

pg_dump
Prev Up Next
ecpg Home pgbench
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgchecksums.html postgresql-13-13.12/doc/src/sgml/html/app-pgchecksums.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgchecksums.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgchecksums.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_checksums
pg_checksums
Prev UpPostgreSQL Server ApplicationsHome Next

pg_checksums

pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster

Synopsis

pg_checksums [option...] [[ -D | --pgdata ]datadir]

Description

+pg_checksums

pg_checksums
Prev UpPostgreSQL Server ApplicationsHome Next

pg_checksums

pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster

Synopsis

pg_checksums [option...] [[ -D | --pgdata ]datadir]

Description

pg_checksums checks, enables or disables data checksums in a PostgreSQL cluster. The server must be shut down cleanly before running @@ -71,4 +71,4 @@ enabling or disabling checksums, the cluster's data checksum configuration remains unchanged, and pg_checksums can be re-run to perform the same operation. -

Prev Up Next
pg_archivecleanup Home pg_controldata
\ No newline at end of file +

Prev Up Next
pg_archivecleanup Home pg_controldata
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgconfig.html postgresql-13-13.12/doc/src/sgml/html/app-pgconfig.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgconfig.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgconfig.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_config
pg_config
Prev UpPostgreSQL Client ApplicationsHome Next

pg_config

pg_config — retrieve information about the installed version of PostgreSQL

Synopsis

pg_config [option...]

Description

+pg_config

pg_config
Prev UpPostgreSQL Client ApplicationsHome Next

pg_config

pg_config — retrieve information about the installed version of PostgreSQL

Synopsis

pg_config [option...]

Description

The pg_config utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be used by software packages that want to interface @@ -107,4 +107,4 @@ shell quotation marks so arguments with spaces are represented correctly. Therefore, using eval is required for proper results. -

Prev Up Next
pgbench Home pg_dump
\ No newline at end of file +

Prev Up Next
pgbench Home pg_dump
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgcontroldata.html postgresql-13-13.12/doc/src/sgml/html/app-pgcontroldata.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgcontroldata.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgcontroldata.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_controldata
pg_controldata
Prev UpPostgreSQL Server ApplicationsHome Next

pg_controldata

pg_controldata — display control information of a PostgreSQL database cluster

Synopsis

pg_controldata [option] [[ -D | --pgdata ]datadir]

Description

+pg_controldata

pg_controldata
Prev UpPostgreSQL Server ApplicationsHome Next

pg_controldata

pg_controldata — display control information of a PostgreSQL database cluster

Synopsis

pg_controldata [option] [[ -D | --pgdata ]datadir]

Description

pg_controldata prints information initialized during initdb, such as the catalog version. It also shows information about write-ahead logging and checkpoint @@ -20,4 +20,4 @@ Specifies whether to use color in diagnostic messages. Possible values are always, auto and never. -

Prev Up Next
pg_checksums Home pg_ctl
\ No newline at end of file +

Prev Up Next
pg_checksums Home pg_ctl
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgdump.html postgresql-13-13.12/doc/src/sgml/html/app-pgdump.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgdump.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgdump.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_dump
pg_dump
Prev UpPostgreSQL Client ApplicationsHome Next

pg_dump

pg_dump — +pg_dump

pg_dump
Prev UpPostgreSQL Client ApplicationsHome Next

pg_dump

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

Synopsis

pg_dump [connection-option...] [option...] [dbname]

Description

pg_dump is a utility for backing up a @@ -795,4 +795,4 @@ 

 $ pg_dump -t "\"MixedCaseName\"" mydb > mytab.sql
-
Prev Up Next
pg_config Home pg_dumpall
\ No newline at end of file +
Prev Up Next
pg_config Home pg_dumpall
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgreceivewal.html postgresql-13-13.12/doc/src/sgml/html/app-pgreceivewal.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgreceivewal.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgreceivewal.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_receivewal
pg_receivewal
Prev UpPostgreSQL Client ApplicationsHome Next

pg_receivewal

pg_receivewal — stream write-ahead logs from a PostgreSQL server

Synopsis

pg_receivewal [option...]

Description

+pg_receivewal

pg_receivewal
Prev UpPostgreSQL Client ApplicationsHome Next

pg_receivewal

pg_receivewal — stream write-ahead logs from a PostgreSQL server

Synopsis

pg_receivewal [option...]

Description

pg_receivewal is used to stream the write-ahead log from a running PostgreSQL cluster. The write-ahead log is streamed using the streaming replication protocol, and is written @@ -219,4 +219,4 @@ /usr/local/pgsql/archive: 

 $ pg_receivewal -h mydbserver -D /usr/local/pgsql/archive
-
Prev Up Next
pg_isready Home pg_recvlogical
\ No newline at end of file +
Prev Up Next
pg_isready Home pg_recvlogical
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgreceivexlog.html postgresql-13-13.12/doc/src/sgml/html/app-pgreceivexlog.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgreceivexlog.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgreceivexlog.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,10 +1,10 @@ -O.4. pg_receivexlog renamed to pg_receivewal
O.4. pg_receivexlog renamed to pg_receivewal
Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

O.4. pg_receivexlog renamed to pg_receivewal

+O.4. pg_receivexlog renamed to pg_receivewal

O.4. pg_receivexlog renamed to pg_receivewal
Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

O.4. pg_receivexlog renamed to pg_receivewal

PostgreSQL 9.6 and below provided a command named pg_receivexlog to fetch write-ahead-log (WAL) files. This command was renamed to pg_receivewal, see pg_receivewal for documentation of pg_receivewal and see - the release notes for PostgreSQL 10 for details + the release notes for PostgreSQL 10 for details on this change. -

Prev Up Next
O.3. pg_resetxlog renamed to pg_resetwal Home Bibliography
\ No newline at end of file +

Prev Up Next
O.3. pg_resetxlog renamed to pg_resetwal Home Bibliography
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgrecvlogical.html postgresql-13-13.12/doc/src/sgml/html/app-pgrecvlogical.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgrecvlogical.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgrecvlogical.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_recvlogical
pg_recvlogical
Prev UpPostgreSQL Client ApplicationsHome Next

pg_recvlogical

pg_recvlogical — control PostgreSQL logical decoding streams

Synopsis

pg_recvlogical [option...]

Description

+pg_recvlogical

pg_recvlogical
Prev UpPostgreSQL Client ApplicationsHome Next

pg_recvlogical

pg_recvlogical — control PostgreSQL logical decoding streams

Synopsis

pg_recvlogical [option...]

Description

pg_recvlogical controls logical decoding replication slots and streams data from such replication slots.

@@ -168,4 +168,4 @@ cluster.

Examples

See Section 48.1 for an example. -

Prev Up Next
pg_receivewal Home pg_restore
\ No newline at end of file +

Prev Up Next
pg_receivewal Home pg_restore
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgresetwal.html postgresql-13-13.12/doc/src/sgml/html/app-pgresetwal.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgresetwal.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgresetwal.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_resetwal
pg_resetwal
Prev UpPostgreSQL Server ApplicationsHome Next

pg_resetwal

pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster

Synopsis

pg_resetwal [ -f | --force ] [ -n | --dry-run ] [option...] [ -D | --pgdata ]datadir

Description

+pg_resetwal

pg_resetwal
Prev UpPostgreSQL Server ApplicationsHome Next

pg_resetwal

pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster

Synopsis

pg_resetwal [ -f | --force ] [ -n | --dry-run ] [option...] [ -D | --pgdata ]datadir

Description

pg_resetwal clears the write-ahead log (WAL) and optionally resets some other control information stored in the pg_control file. This function is sometimes needed @@ -166,4 +166,4 @@

pg_resetwal works only with servers of the same major version. -

Prev Up Next
pg_ctl Home pg_rewind
\ No newline at end of file +

Prev Up Next
pg_ctl Home pg_rewind
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgresetxlog.html postgresql-13-13.12/doc/src/sgml/html/app-pgresetxlog.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgresetxlog.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgresetxlog.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,10 +1,10 @@ -O.3. pg_resetxlog renamed to pg_resetwal
O.3. pg_resetxlog renamed to pg_resetwal
Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

O.3. pg_resetxlog renamed to pg_resetwal

+O.3. pg_resetxlog renamed to pg_resetwal

O.3. pg_resetxlog renamed to pg_resetwal
Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

O.3. pg_resetxlog renamed to pg_resetwal

PostgreSQL 9.6 and below provided a command named pg_resetxlog to reset the write-ahead-log (WAL) files. This command was renamed to pg_resetwal, see pg_resetwal for documentation of pg_resetwal and see - the release notes for PostgreSQL 10 for details + the release notes for PostgreSQL 10 for details on this change. -

Prev Up Next
O.2. pg_xlogdump renamed to pg_waldump Home O.4. pg_receivexlog renamed to pg_receivewal
\ No newline at end of file +

Prev Up Next
O.2. pg_xlogdump renamed to pg_waldump Home O.4. pg_receivexlog renamed to pg_receivewal
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgrestore.html postgresql-13-13.12/doc/src/sgml/html/app-pgrestore.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgrestore.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgrestore.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_restore
pg_restore
Prev UpPostgreSQL Client ApplicationsHome Next

pg_restore

pg_restore — +pg_restore

pg_restore
Prev UpPostgreSQL Client ApplicationsHome Next

pg_restore

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

Synopsis

pg_restore [connection-option...] [option...] [filename]

Description

@@ -488,4 +488,4 @@ items 10 and 6, in that order: 

 $ pg_restore -L db.list db.dump
-
Prev Up Next
pg_recvlogical Home pg_verifybackup
\ No newline at end of file +
Prev Up Next
pg_recvlogical Home pg_verifybackup
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgrewind.html postgresql-13-13.12/doc/src/sgml/html/app-pgrewind.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgrewind.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgrewind.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_rewind
pg_rewind
Prev UpPostgreSQL Server ApplicationsHome Next

pg_rewind

pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it

Synopsis

pg_rewind [option...] { -D | --target-pgdata } directory { --source-pgdata=directory | --source-server=connstr }

Description

+pg_rewind

pg_rewind
Prev UpPostgreSQL Server ApplicationsHome Next

pg_rewind

pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it

Synopsis

pg_rewind [option...] { -D | --target-pgdata } directory { --source-pgdata=directory | --source-server=connstr }

Description

pg_rewind is a tool for synchronizing a PostgreSQL cluster with another copy of the same cluster, after the clusters' timelines have diverged. A typical scenario is to bring an old master server back online @@ -205,4 +205,4 @@ When starting the target, PostgreSQL replays all the required WAL, resulting in a data directory in a consistent state. -

Prev Up Next
pg_resetwal Home pg_test_fsync
\ No newline at end of file +

Prev Up Next
pg_resetwal Home pg_test_fsync
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-pgverifybackup.html postgresql-13-13.12/doc/src/sgml/html/app-pgverifybackup.html --- postgresql-13-13.11/doc/src/sgml/html/app-pgverifybackup.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-pgverifybackup.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pg_verifybackup
pg_verifybackup
Prev UpPostgreSQL Client ApplicationsHome Next

pg_verifybackup

pg_verifybackup — verify the integrity of a base backup of a +pg_verifybackup

pg_verifybackup
Prev UpPostgreSQL Client ApplicationsHome Next

pg_verifybackup

pg_verifybackup — verify the integrity of a base backup of a PostgreSQL cluster

Synopsis

pg_verifybackup [option...]

Description

pg_verifybackup is used to check the integrity of a database cluster backup taken using @@ -141,4 +141,4 @@ $ pg_basebackup -h mydbserver -D /usr/local/pgsql/data $ edit /usr/local/pgsql/data/note.to.self $ pg_verifybackup --ignore=note.to.self --skip-checksums /usr/local/pgsql/data -

Prev Up Next
pg_restore Home psql
\ No newline at end of file +
Prev Up Next
pg_restore Home psql
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-postgres.html postgresql-13-13.12/doc/src/sgml/html/app-postgres.html --- postgresql-13-13.11/doc/src/sgml/html/app-postgres.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-postgres.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -postgres
postgres
Prev UpPostgreSQL Server ApplicationsHome Next

postgres

postgres — PostgreSQL database server

Synopsis

postgres [option...]

Description

+postgres

postgres
Prev UpPostgreSQL Server ApplicationsHome Next

postgres

postgres — PostgreSQL database server

Synopsis

postgres [option...]

Description

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

See Also

initdb, pg_ctl -

Prev Up Next
pg_waldump Home postmaster
\ No newline at end of file +

Prev Up Next
pg_waldump Home postmaster
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-postmaster.html postgresql-13-13.12/doc/src/sgml/html/app-postmaster.html --- postgresql-13-13.11/doc/src/sgml/html/app-postmaster.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-postmaster.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,6 +1,6 @@ -postmaster
postmaster
Prev UpPostgreSQL Server ApplicationsHome Next

postmaster

postmaster — PostgreSQL database server

Synopsis

postmaster [option...]

Description

+postmaster

postmaster
Prev UpPostgreSQL Server ApplicationsHome Next

postmaster

postmaster — PostgreSQL database server

Synopsis

postmaster [option...]

Description

postmaster is a deprecated alias of postgres.

See Also

postgres -

Prev Up Next
postgres Home Part VII. Internals
\ No newline at end of file +

Prev Up Next
postgres Home Part VII. Internals
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-psql.html postgresql-13-13.12/doc/src/sgml/html/app-psql.html --- postgresql-13-13.11/doc/src/sgml/html/app-psql.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-psql.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -psql
psql
Prev UpPostgreSQL Client ApplicationsHome Next

psql

psql — +psql

psql
Prev UpPostgreSQL Client ApplicationsHome Next

psql

psql — PostgreSQL interactive terminal

Synopsis

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

Description

@@ -349,7 +349,7 @@ the string =>. For example: 

 $ psql testdb
-psql (13.11)
+psql (13.12)
 Type "help" for help.
 
 testdb=>
@@ -2815,4 +2815,4 @@
  2 | 202 | 204 | 206 | 208
  1 | 101 | 102 | 103 | 104
 (4 rows)
-
Prev Up Next
pg_verifybackup Home reindexdb
\ No newline at end of file +
Prev Up Next
pg_verifybackup Home reindexdb
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-reindexdb.html postgresql-13-13.12/doc/src/sgml/html/app-reindexdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-reindexdb.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-reindexdb.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -reindexdb
reindexdb
Prev UpPostgreSQL Client ApplicationsHome Next

reindexdb

reindexdb — reindex a PostgreSQL database

Synopsis

reindexdb [connection-option...] [option...] +reindexdb

reindexdb
Prev UpPostgreSQL Client ApplicationsHome Next

reindexdb

reindexdb — reindex a PostgreSQL database

Synopsis

reindexdb [connection-option...] [option...] [ -S | --schema schema @@ -158,4 +158,4 @@ bar in a database named abcd: 

 $ reindexdb --table=foo --index=bar abcd
-

See Also

REINDEX
Prev Up Next
psql Home vacuumdb
\ No newline at end of file +

See Also

REINDEX
Prev Up Next
psql Home vacuumdb
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/app-vacuumdb.html postgresql-13-13.12/doc/src/sgml/html/app-vacuumdb.html --- postgresql-13-13.11/doc/src/sgml/html/app-vacuumdb.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/app-vacuumdb.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -vacuumdb
vacuumdb
Prev UpPostgreSQL Client ApplicationsHome Next

vacuumdb

vacuumdb — garbage-collect and analyze a PostgreSQL database

Synopsis

vacuumdb [connection-option...] [option...] +vacuumdb

vacuumdb
Prev UpPostgreSQL Client ApplicationsHome Next

vacuumdb

vacuumdb — garbage-collect and analyze a PostgreSQL database

Synopsis

vacuumdb [connection-option...] [option...] [ -t | --table table @@ -217,4 +217,4 @@ bar of the table for the optimizer: 

 $ vacuumdb --analyze --verbose --table='foo(bar)' xyzzy
-

See Also

VACUUM
Prev Up Next
reindexdb Home PostgreSQL Server Applications
\ No newline at end of file +

See Also

VACUUM
Prev Up Next
reindexdb Home PostgreSQL Server Applications
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/appendix-obsolete.html postgresql-13-13.12/doc/src/sgml/html/appendix-obsolete.html --- postgresql-13-13.11/doc/src/sgml/html/appendix-obsolete.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/appendix-obsolete.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,8 +1,8 @@ -Appendix O. Obsolete or Renamed Features
Appendix O. Obsolete or Renamed Features
Prev UpPart VIII. AppendixesHome Next

Appendix O. Obsolete or Renamed Features

Table of Contents

O.1. recovery.conf file merged into postgresql.conf
O.2. pg_xlogdump renamed to pg_waldump
O.3. pg_resetxlog renamed to pg_resetwal
O.4. pg_receivexlog renamed to pg_receivewal

+Appendix O. Obsolete or Renamed Features

Appendix O. Obsolete or Renamed Features
Prev UpPart VIII. AppendixesHome Next

Appendix O. Obsolete or Renamed Features

Table of Contents

O.1. recovery.conf file merged into postgresql.conf
O.2. pg_xlogdump renamed to pg_waldump
O.3. pg_resetxlog renamed to pg_resetwal
O.4. pg_receivexlog renamed to pg_receivewal

Functionality is sometimes removed from PostgreSQL, feature, setting and file names sometimes change, or documentation moves to different places. This section directs users coming from old versions of the documentation or from external links to the appropriate new location for the information they need. -

Prev Up Next
N.2. Configuring the Colors Home O.1. recovery.conf file merged into postgresql.conf
\ No newline at end of file +

Prev Up Next
N.2. Configuring the Colors Home O.1. recovery.conf file merged into postgresql.conf
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/appendixes.html postgresql-13-13.12/doc/src/sgml/html/appendixes.html --- postgresql-13-13.11/doc/src/sgml/html/appendixes.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/appendixes.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,2 +1,2 @@ -Part VIII. Appendixes
Part VIII. Appendixes
Prev UpPostgreSQL 13.11 DocumentationHome Next

Part VIII. Appendixes

Table of Contents

A. PostgreSQL Error Codes
B. Date/Time Support
B.1. Date/Time Input Interpretation
B.2. Handling of Invalid or Ambiguous Timestamps
B.3. Date/Time Key Words
B.4. Date/Time Configuration Files
B.5. POSIX Time Zone Specifications
B.6. History of Units
B.7. Julian Dates
C. SQL Key Words
D. SQL Conformance
D.1. Supported Features
D.2. Unsupported Features
D.3. XML Limits and Conformance to SQL/XML
E. Release Notes
E.1. Release 13.11
E.2. Release 13.10
E.3. Release 13.9
E.4. Release 13.8
E.5. Release 13.7
E.6. Release 13.6
E.7. Release 13.5
E.8. Release 13.4
E.9. Release 13.3
E.10. Release 13.2
E.11. Release 13.1
E.12. Release 13
E.13. Prior Releases
F. Additional Supplied Modules
F.1. adminpack
F.2. amcheck
F.3. auth_delay
F.4. auto_explain
F.5. bloom
F.6. btree_gin
F.7. btree_gist
F.8. citext
F.9. cube
F.10. dblink
F.11. dict_int
F.12. dict_xsyn
F.13. earthdistance
F.14. file_fdw
F.15. fuzzystrmatch
F.16. hstore
F.17. intagg
F.18. intarray
F.19. isn
F.20. lo
F.21. ltree
F.22. pageinspect
F.23. passwordcheck
F.24. pg_buffercache
F.25. pgcrypto
F.26. pg_freespacemap
F.27. pg_prewarm
F.28. pgrowlocks
F.29. pg_stat_statements
F.30. pgstattuple
F.31. pg_trgm
F.32. pg_visibility
F.33. postgres_fdw
F.34. seg
F.35. sepgsql
F.36. spi
F.37. sslinfo
F.38. tablefunc
F.39. tcn
F.40. test_decoding
F.41. tsm_system_rows
F.42. tsm_system_time
F.43. unaccent
F.44. uuid-ossp
F.45. xml2
G. Additional Supplied Programs
G.1. Client Applications
G.2. Server Applications
H. External Projects
H.1. Client Interfaces
H.2. Administration Tools
H.3. Procedural Languages
H.4. Extensions
I. The Source Code Repository
I.1. Getting the Source via Git
J. Documentation
J.1. DocBook
J.2. Tool Sets
J.3. Building the Documentation
J.4. Documentation Authoring
J.5. Style Guide
K. PostgreSQL Limits
L. Acronyms
M. Glossary
N. Color Support
N.1. When Color is Used
N.2. Configuring the Colors
O. Obsolete or Renamed Features
O.1. recovery.conf file merged into postgresql.conf
O.2. pg_xlogdump renamed to pg_waldump
O.3. pg_resetxlog renamed to pg_resetwal
O.4. pg_receivexlog renamed to pg_receivewal
Prev Up Next
72.3. Backup Manifest WAL Range Object Home Appendix A. PostgreSQL Error Codes
\ No newline at end of file +Part VIII. Appendixes
Part VIII. Appendixes
Prev UpPostgreSQL 13.12 DocumentationHome Next

Part VIII. Appendixes

Table of Contents

A. PostgreSQL Error Codes
B. Date/Time Support
B.1. Date/Time Input Interpretation
B.2. Handling of Invalid or Ambiguous Timestamps
B.3. Date/Time Key Words
B.4. Date/Time Configuration Files
B.5. POSIX Time Zone Specifications
B.6. History of Units
B.7. Julian Dates
C. SQL Key Words
D. SQL Conformance
D.1. Supported Features
D.2. Unsupported Features
D.3. XML Limits and Conformance to SQL/XML
E. Release Notes
E.1. Release 13.12
E.2. Release 13.11
E.3. Release 13.10
E.4. Release 13.9
E.5. Release 13.8
E.6. Release 13.7
E.7. Release 13.6
E.8. Release 13.5
E.9. Release 13.4
E.10. Release 13.3
E.11. Release 13.2
E.12. Release 13.1
E.13. Release 13
E.14. Prior Releases
F. Additional Supplied Modules
F.1. adminpack
F.2. amcheck
F.3. auth_delay
F.4. auto_explain
F.5. bloom
F.6. btree_gin
F.7. btree_gist
F.8. citext
F.9. cube
F.10. dblink
F.11. dict_int
F.12. dict_xsyn
F.13. earthdistance
F.14. file_fdw
F.15. fuzzystrmatch
F.16. hstore
F.17. intagg
F.18. intarray
F.19. isn
F.20. lo
F.21. ltree
F.22. pageinspect
F.23. passwordcheck
F.24. pg_buffercache
F.25. pgcrypto
F.26. pg_freespacemap
F.27. pg_prewarm
F.28. pgrowlocks
F.29. pg_stat_statements
F.30. pgstattuple
F.31. pg_trgm
F.32. pg_visibility
F.33. postgres_fdw
F.34. seg
F.35. sepgsql
F.36. spi
F.37. sslinfo
F.38. tablefunc
F.39. tcn
F.40. test_decoding
F.41. tsm_system_rows
F.42. tsm_system_time
F.43. unaccent
F.44. uuid-ossp
F.45. xml2
G. Additional Supplied Programs
G.1. Client Applications
G.2. Server Applications
H. External Projects
H.1. Client Interfaces
H.2. Administration Tools
H.3. Procedural Languages
H.4. Extensions
I. The Source Code Repository
I.1. Getting the Source via Git
J. Documentation
J.1. DocBook
J.2. Tool Sets
J.3. Building the Documentation
J.4. Documentation Authoring
J.5. Style Guide
K. PostgreSQL Limits
L. Acronyms
M. Glossary
N. Color Support
N.1. When Color is Used
N.2. Configuring the Colors
O. Obsolete or Renamed Features
O.1. recovery.conf file merged into postgresql.conf
O.2. pg_xlogdump renamed to pg_waldump
O.3. pg_resetxlog renamed to pg_resetwal
O.4. pg_receivexlog renamed to pg_receivewal
Prev Up Next
72.3. Backup Manifest WAL Range Object Home Appendix A. PostgreSQL Error Codes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/applevel-consistency.html postgresql-13-13.12/doc/src/sgml/html/applevel-consistency.html --- postgresql-13-13.11/doc/src/sgml/html/applevel-consistency.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/applevel-consistency.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -13.4. Data Consistency Checks at the Application Level
13.4. Data Consistency Checks at the Application Level
Prev UpChapter 13. Concurrency ControlHome Next

13.4. Data Consistency Checks at the Application Level

13.4.1. Enforcing Consistency with Serializable Transactions
13.4.2. Enforcing Consistency with Explicit Blocking Locks

+13.4. Data Consistency Checks at the Application Level

13.4. Data Consistency Checks at the Application Level
Prev UpChapter 13. Concurrency ControlHome Next

13.4. Data Consistency Checks at the Application Level

13.4.1. Enforcing Consistency with Serializable Transactions
13.4.2. Enforcing Consistency with Explicit Blocking Locks

It is very difficult to enforce business rules regarding data integrity using Read Committed transactions because the view of the data is shifting with each statement, and even a single statement may not @@ -111,4 +111,4 @@ UPDATE, or DELETE), so it is possible to obtain locks explicitly before the snapshot is frozen. -

Prev Up Next
13.3. Explicit Locking Home 13.5. Caveats
\ No newline at end of file +

Prev Up Next
13.3. Explicit Locking Home 13.5. Caveats
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/arrays.html postgresql-13-13.12/doc/src/sgml/html/arrays.html --- postgresql-13-13.11/doc/src/sgml/html/arrays.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/arrays.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.15. Arrays
8.15. Arrays
Prev UpChapter 8. Data TypesHome Next

8.15. Arrays

8.15.1. Declaration of Array Types
8.15.2. Array Value Input
8.15.3. Accessing Arrays
8.15.4. Modifying Arrays
8.15.5. Searching in Arrays
8.15.6. Array Input and Output Syntax

+8.15. Arrays

8.15. Arrays
Prev UpChapter 8. Data TypesHome Next

8.15. Arrays

8.15.1. Declaration of Array Types
8.15.2. Array Value Input
8.15.3. Accessing Arrays
8.15.4. Modifying Arrays
8.15.5. Searching in Arrays
8.15.6. Array Input and Output Syntax

PostgreSQL allows columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type, enum type, composite type, range type, @@ -644,4 +644,4 @@ with than the array-literal syntax when writing array values in SQL commands. In ARRAY, individual element values are written the same way they would be written when not members of an array. -

Prev Up Next
8.14. JSON Types Home 8.16. Composite Types
\ No newline at end of file +

Prev Up Next
8.14. JSON Types Home 8.16. Composite Types
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-bsd.html postgresql-13-13.12/doc/src/sgml/html/auth-bsd.html --- postgresql-13-13.11/doc/src/sgml/html/auth-bsd.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-bsd.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.14. BSD Authentication
20.14. BSD Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.14. BSD Authentication

+20.14. BSD Authentication

20.14. BSD Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.14. BSD Authentication

This authentication method operates similarly to password except that it uses BSD Authentication to verify the password. BSD Authentication is used only @@ -18,4 +18,4 @@ operating system user running the server) must first be added to the auth group. The auth group exists by default on OpenBSD systems. -

Prev Up Next
20.13. PAM Authentication Home 20.15. Authentication Problems
\ No newline at end of file +

Prev Up Next
20.13. PAM Authentication Home 20.15. Authentication Problems
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-cert.html postgresql-13-13.12/doc/src/sgml/html/auth-cert.html --- postgresql-13-13.11/doc/src/sgml/html/auth-cert.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-cert.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.12. Certificate Authentication
20.12. Certificate Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.12. Certificate Authentication

+20.12. Certificate Authentication

20.12. Certificate Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.12. Certificate Authentication

This authentication method uses SSL client certificates to perform authentication. It is therefore only available for SSL connections. When using this authentication method, the server will require that @@ -21,4 +21,4 @@ cert authentication because cert authentication is effectively trust authentication with clientcert=verify-full. -

Prev Up Next
20.11. RADIUS Authentication Home 20.13. PAM Authentication
\ No newline at end of file +

Prev Up Next
20.11. RADIUS Authentication Home 20.13. PAM Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-delay.html postgresql-13-13.12/doc/src/sgml/html/auth-delay.html --- postgresql-13-13.11/doc/src/sgml/html/auth-delay.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-delay.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.3. auth_delay
F.3. auth_delay
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.3. auth_delay

F.3.1. Configuration Parameters
F.3.2. Author

+F.3. auth_delay

F.3. auth_delay
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.3. auth_delay

F.3.1. Configuration Parameters
F.3.2. Author

auth_delay causes the server to pause briefly before reporting authentication failure, to make brute-force attacks on database passwords more difficult. Note that it does nothing to prevent @@ -25,4 +25,4 @@ auth_delay.milliseconds = '500'

F.3.2. Author

KaiGai Kohei -

Prev Up Next
F.2. amcheck Home F.4. auto_explain
\ No newline at end of file +

Prev Up Next
F.2. amcheck Home F.4. auto_explain
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-ident.html postgresql-13-13.12/doc/src/sgml/html/auth-ident.html --- postgresql-13-13.11/doc/src/sgml/html/auth-ident.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-ident.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.8. Ident Authentication
20.8. Ident Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.8. Ident Authentication

+20.8. Ident Authentication

20.8. Ident Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.8. Ident Authentication

The ident authentication method works by obtaining the client's operating system user name from an ident server and using it as the allowed database user name (with an optional user name mapping). @@ -48,4 +48,4 @@ used when using the ident server with PostgreSQL, since PostgreSQL does not have any way to decrypt the returned string to determine the actual user name. -

Prev Up Next
20.7. SSPI Authentication Home 20.9. Peer Authentication
\ No newline at end of file +

Prev Up Next
20.7. SSPI Authentication Home 20.9. Peer Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-ldap.html postgresql-13-13.12/doc/src/sgml/html/auth-ldap.html --- postgresql-13-13.11/doc/src/sgml/html/auth-ldap.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-ldap.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.10. LDAP Authentication
20.10. LDAP Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.10. LDAP Authentication

+20.10. LDAP Authentication

20.10. LDAP Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.10. LDAP Authentication

This authentication method operates similarly to password except that it uses LDAP as the password verification method. LDAP is used only to validate @@ -185,4 +185,4 @@ Since LDAP often uses commas and spaces to separate the different parts of a DN, it is often necessary to use double-quoted parameter values when configuring LDAP options, as shown in the examples. -

Prev Up Next
20.9. Peer Authentication Home 20.11. RADIUS Authentication
\ No newline at end of file +

Prev Up Next
20.9. Peer Authentication Home 20.11. RADIUS Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-methods.html postgresql-13-13.12/doc/src/sgml/html/auth-methods.html --- postgresql-13-13.11/doc/src/sgml/html/auth-methods.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-methods.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.3. Authentication Methods
20.3. Authentication Methods
Prev UpChapter 20. Client AuthenticationHome Next

20.3. Authentication Methods

+20.3. Authentication Methods

20.3. Authentication Methods
Prev UpChapter 20. Client AuthenticationHome Next

20.3. Authentication Methods

PostgreSQL provides various methods for authenticating users: @@ -55,4 +55,4 @@

The following sections describe each of these authentication methods in more detail. -

Prev Up Next
20.2. User Name Maps Home 20.4. Trust Authentication
\ No newline at end of file +

Prev Up Next
20.2. User Name Maps Home 20.4. Trust Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-pam.html postgresql-13-13.12/doc/src/sgml/html/auth-pam.html --- postgresql-13-13.11/doc/src/sgml/html/auth-pam.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-pam.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.13. PAM Authentication
20.13. PAM Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.13. PAM Authentication

+20.13. PAM Authentication

20.13. PAM Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.13. PAM Authentication

This authentication method operates similarly to password except that it uses PAM (Pluggable Authentication Modules) as the authentication mechanism. The @@ -28,4 +28,4 @@ will fail because the PostgreSQL server is started by a non-root user. However, this is not an issue when PAM is configured to use LDAP or other authentication methods. -

Prev Up Next
20.12. Certificate Authentication Home 20.14. BSD Authentication
\ No newline at end of file +

Prev Up Next
20.12. Certificate Authentication Home 20.14. BSD Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-password.html postgresql-13-13.12/doc/src/sgml/html/auth-password.html --- postgresql-13-13.11/doc/src/sgml/html/auth-password.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-password.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.5. Password Authentication
20.5. Password Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.5. Password Authentication

+20.5. Password Authentication

20.5. Password Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.5. Password Authentication

There are several password-based authentication methods. These methods operate similarly but differ in how the users' passwords are stored on the server and how the password provided by a client is sent across the @@ -77,4 +77,4 @@ in postgresql.conf, make all users set new passwords, and change the authentication method specifications in pg_hba.conf to scram-sha-256. -

Prev Up Next
20.4. Trust Authentication Home 20.6. GSSAPI Authentication
\ No newline at end of file +

Prev Up Next
20.4. Trust Authentication Home 20.6. GSSAPI Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-peer.html postgresql-13-13.12/doc/src/sgml/html/auth-peer.html --- postgresql-13-13.11/doc/src/sgml/html/auth-peer.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-peer.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.9. Peer Authentication
20.9. Peer Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.9. Peer Authentication

+20.9. Peer Authentication

20.9. Peer Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.9. Peer Authentication

The peer authentication method works by obtaining the client's operating system user name from the kernel and using it as the allowed database user name (with optional user name mapping). This @@ -18,4 +18,4 @@ most flavors of BSD including macOS, and Solaris. -

Prev Up Next
20.8. Ident Authentication Home 20.10. LDAP Authentication
\ No newline at end of file +

Prev Up Next
20.8. Ident Authentication Home 20.10. LDAP Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-pg-hba-conf.html postgresql-13-13.12/doc/src/sgml/html/auth-pg-hba-conf.html --- postgresql-13-13.11/doc/src/sgml/html/auth-pg-hba-conf.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-pg-hba-conf.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.1. The pg_hba.conf File
20.1. The pg_hba.conf File
Prev UpChapter 20. Client AuthenticationHome Next

20.1. The pg_hba.conf File

+20.1. The pg_hba.conf File

20.1. The pg_hba.conf File
Prev UpChapter 20. Client AuthenticationHome Next

20.1. The pg_hba.conf File

Client authentication is controlled by a configuration file, which traditionally is named pg_hba.conf and is stored in the database @@ -464,4 +464,4 @@ # The database column can also use lists and file names: local db1,db2,@demodbs all md5 -


Prev Up Next
Chapter 20. Client Authentication Home 20.2. User Name Maps
\ No newline at end of file +
Prev Up Next
Chapter 20. Client Authentication Home 20.2. User Name Maps
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-radius.html postgresql-13-13.12/doc/src/sgml/html/auth-radius.html --- postgresql-13-13.11/doc/src/sgml/html/auth-radius.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-radius.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.11. RADIUS Authentication
20.11. RADIUS Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.11. RADIUS Authentication

+20.11. RADIUS Authentication

20.11. RADIUS Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.11. RADIUS Authentication

This authentication method operates similarly to password except that it uses RADIUS as the password verification method. RADIUS is used only to validate @@ -62,4 +62,4 @@ 

 host ... radius radiusservers="server1,server2" radiussecrets="""secret one"",""secret two"""

-

Prev Up Next
20.10. LDAP Authentication Home 20.12. Certificate Authentication
\ No newline at end of file +

Prev Up Next
20.10. LDAP Authentication Home 20.12. Certificate Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-trust.html postgresql-13-13.12/doc/src/sgml/html/auth-trust.html --- postgresql-13-13.11/doc/src/sgml/html/auth-trust.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-trust.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.4. Trust Authentication
20.4. Trust Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.4. Trust Authentication

+20.4. Trust Authentication

20.4. Trust Authentication
Prev UpChapter 20. Client AuthenticationHome Next

20.4. Trust Authentication

When trust authentication is specified, PostgreSQL assumes that anyone who can connect to the server is authorized to access the database with @@ -34,4 +34,4 @@ to the server by the pg_hba.conf lines that specify trust. It is seldom reasonable to use trust for any TCP/IP connections other than those from localhost (127.0.0.1). -

Prev Up Next
20.3. Authentication Methods Home 20.5. Password Authentication
\ No newline at end of file +

Prev Up Next
20.3. Authentication Methods Home 20.5. Password Authentication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auth-username-maps.html postgresql-13-13.12/doc/src/sgml/html/auth-username-maps.html --- postgresql-13-13.11/doc/src/sgml/html/auth-username-maps.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auth-username-maps.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.2. User Name Maps
20.2. User Name Maps
Prev UpChapter 20. Client AuthenticationHome Next

20.2. User Name Maps

+20.2. User Name Maps

20.2. User Name Maps
Prev UpChapter 20. Client AuthenticationHome Next

20.2. User Name Maps

When using an external authentication system such as Ident or GSSAPI, the name of the operating system user that initiated the connection might not be the same as the database user (role) that is to be used. @@ -91,4 +91,4 @@ omicron robert bob # bryanh can also connect as guest1 omicron bryanh guest1 -


Prev Up Next
20.1. The pg_hba.conf File Home 20.3. Authentication Methods
\ No newline at end of file +
Prev Up Next
20.1. The pg_hba.conf File Home 20.3. Authentication Methods
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/auto-explain.html postgresql-13-13.12/doc/src/sgml/html/auto-explain.html --- postgresql-13-13.11/doc/src/sgml/html/auto-explain.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/auto-explain.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.4. auto_explain
F.4. auto_explain
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.4. auto_explain

F.4.1. Configuration Parameters
F.4.2. Example
F.4.3. Author

+F.4. auto_explain

F.4. auto_explain
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.4. auto_explain

F.4.1. Configuration Parameters
F.4.2. Example
F.4.3. Author

The auto_explain module provides a means for logging execution plans of slow statements automatically, without having to run EXPLAIN @@ -186,4 +186,4 @@ Filter: indisunique

F.4.3. Author

Takahiro Itagaki -

Prev Up Next
F.3. auth_delay Home F.5. bloom
\ No newline at end of file +

Prev Up Next
F.3. auth_delay Home F.5. bloom
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-dump.html postgresql-13-13.12/doc/src/sgml/html/backup-dump.html --- postgresql-13-13.11/doc/src/sgml/html/backup-dump.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-dump.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -25.1. SQL Dump
25.1. SQL Dump
Prev UpChapter 25. Backup and RestoreHome Next

25.1. SQL Dump

25.1.1. Restoring the Dump
25.1.2. Using pg_dumpall
25.1.3. Handling Large Databases

+25.1. SQL Dump

25.1. SQL Dump
Prev UpChapter 25. Backup and RestoreHome Next

25.1. SQL Dump

25.1.1. Restoring the Dump
25.1.2. Using pg_dumpall
25.1.3. Handling Large Databases

The idea behind this dump method is to generate a file with SQL commands that, when fed back to the server, will recreate the database in the same state as it was at the time of the dump. @@ -244,4 +244,4 @@ You can use pg_restore -j to restore a dump in parallel. This will work for any archive of either the "custom" or the "directory" archive mode, whether or not it has been created with pg_dump -j. -

Prev Up Next
Chapter 25. Backup and Restore Home 25.2. File System Level Backup
\ No newline at end of file +

Prev Up Next
Chapter 25. Backup and Restore Home 25.2. File System Level Backup
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-file.html postgresql-13-13.12/doc/src/sgml/html/backup-file.html --- postgresql-13-13.11/doc/src/sgml/html/backup-file.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-file.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -25.2. File System Level Backup
25.2. File System Level Backup
Prev UpChapter 25. Backup and RestoreHome Next

25.2. File System Level Backup

+25.2. File System Level Backup

25.2. File System Level Backup
Prev UpChapter 25. Backup and RestoreHome Next

25.2. File System Level Backup

An alternative backup strategy is to directly copy the files that PostgreSQL uses to store the data in the database; Section 18.2 explains where these files @@ -88,4 +88,4 @@ than an SQL dump. (pg_dump does not need to dump the contents of indexes for example, just the commands to recreate them.) However, taking a file system backup might be faster. -

Prev Up Next
25.1. SQL Dump Home 25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
\ No newline at end of file +

Prev Up Next
25.1. SQL Dump Home 25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-manifest-files.html postgresql-13-13.12/doc/src/sgml/html/backup-manifest-files.html --- postgresql-13-13.11/doc/src/sgml/html/backup-manifest-files.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-manifest-files.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -72.2. Backup Manifest File Object
72.2. Backup Manifest File Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.2. Backup Manifest File Object

+72.2. Backup Manifest File Object

72.2. Backup Manifest File Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.2. Backup Manifest File Object

The object which describes a single file contains either a Path key or an Encoded-Path key. Normally, the Path key will be present. The @@ -36,4 +36,4 @@

Checksum

The checksum computed for this file, stored as a series of hexadecimal characters, two for each byte of the checksum. -

Prev Up Next
72.1. Backup Manifest Top-level Object Home 72.3. Backup Manifest WAL Range Object
\ No newline at end of file +

Prev Up Next
72.1. Backup Manifest Top-level Object Home 72.3. Backup Manifest WAL Range Object
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-manifest-format.html postgresql-13-13.12/doc/src/sgml/html/backup-manifest-format.html --- postgresql-13-13.11/doc/src/sgml/html/backup-manifest-format.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-manifest-format.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 72. Backup Manifest Format
Chapter 72. Backup Manifest Format
Prev UpPart VII. InternalsHome Next

Chapter 72. Backup Manifest Format

Table of Contents

72.1. Backup Manifest Top-level Object
72.2. Backup Manifest File Object
72.3. Backup Manifest WAL Range Object

+Chapter 72. Backup Manifest Format

Chapter 72. Backup Manifest Format
Prev UpPart VII. InternalsHome Next

Chapter 72. Backup Manifest Format

Table of Contents

72.1. Backup Manifest Top-level Object
72.2. Backup Manifest File Object
72.3. Backup Manifest WAL Range Object

The backup manifest generated by pg_basebackup is primarily intended to permit the backup to be verified using pg_verifybackup. However, it is @@ -13,4 +13,4 @@ supported server encoding. There is no similar exception for backup manifests.) The JSON document is always an object; the keys that are present in this object are described in the next section. -

Prev Up Next
71.3. Planner Statistics and Security Home 72.1. Backup Manifest Top-level Object
\ No newline at end of file +

Prev Up Next
71.3. Planner Statistics and Security Home 72.1. Backup Manifest Top-level Object
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-manifest-toplevel.html postgresql-13-13.12/doc/src/sgml/html/backup-manifest-toplevel.html --- postgresql-13-13.11/doc/src/sgml/html/backup-manifest-toplevel.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-manifest-toplevel.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -72.1. Backup Manifest Top-level Object
72.1. Backup Manifest Top-level Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.1. Backup Manifest Top-level Object

+72.1. Backup Manifest Top-level Object

72.1. Backup Manifest Top-level Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.1. Backup Manifest Top-level Object

The backup manifest JSON document contains the following keys.

PostgreSQL-Backup-Manifest-Version

The associated value is always the integer 1. @@ -22,4 +22,4 @@ is significantly more expensive than a CRC32C checksum, the manifest should normally be small enough that the extra computation won't matter very much. -

Prev Up Next
Chapter 72. Backup Manifest Format Home 72.2. Backup Manifest File Object
\ No newline at end of file +

Prev Up Next
Chapter 72. Backup Manifest Format Home 72.2. Backup Manifest File Object
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup-manifest-wal-ranges.html postgresql-13-13.12/doc/src/sgml/html/backup-manifest-wal-ranges.html --- postgresql-13-13.11/doc/src/sgml/html/backup-manifest-wal-ranges.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup-manifest-wal-ranges.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -72.3. Backup Manifest WAL Range Object
72.3. Backup Manifest WAL Range Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.3. Backup Manifest WAL Range Object

+72.3. Backup Manifest WAL Range Object

72.3. Backup Manifest WAL Range Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.3. Backup Manifest WAL Range Object

The object which describes a WAL range always has three keys:

Timeline

The timeline for this range of WAL records, as an integer. @@ -19,4 +19,4 @@ upstream promotion, it is possible for multiple ranges to be present, each with a different timeline. There will never be multiple WAL ranges present for the same timeline. -

Prev Up Next
72.2. Backup Manifest File Object Home Part VIII. Appendixes
\ No newline at end of file +

Prev Up Next
72.2. Backup Manifest File Object Home Part VIII. Appendixes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/backup.html postgresql-13-13.12/doc/src/sgml/html/backup.html --- postgresql-13-13.11/doc/src/sgml/html/backup.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/backup.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 25. Backup and Restore
Chapter 25. Backup and Restore
Prev UpPart III. Server AdministrationHome Next

Chapter 25. Backup and Restore

Table of Contents

25.1. SQL Dump
25.1.1. Restoring the Dump
25.1.2. Using pg_dumpall
25.1.3. Handling Large Databases
25.2. File System Level Backup
25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
25.3.1. Setting Up WAL Archiving
25.3.2. Making a Base Backup
25.3.3. Making a Base Backup Using the Low Level API
25.3.4. Recovering Using a Continuous Archive Backup
25.3.5. Timelines
25.3.6. Tips and Examples
25.3.7. Caveats

+Chapter 25. Backup and Restore

Chapter 25. Backup and Restore
Prev UpPart III. Server AdministrationHome Next

Chapter 25. Backup and Restore

Table of Contents

25.1. SQL Dump
25.1.1. Restoring the Dump
25.1.2. Using pg_dumpall
25.1.3. Handling Large Databases
25.2. File System Level Backup
25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
25.3.1. Setting Up WAL Archiving
25.3.2. Making a Base Backup
25.3.3. Making a Base Backup Using the Low Level API
25.3.4. Recovering Using a Continuous Archive Backup
25.3.5. Timelines
25.3.6. Tips and Examples
25.3.7. Caveats

As with everything that contains valuable data, PostgreSQL databases should be backed up regularly. While the procedure is essentially simple, it is important to have a clear understanding of @@ -10,4 +10,4 @@

  • SQL dump

  • File system level backup

  • Continuous archiving

Each has its own strengths and weaknesses; each is discussed in turn in the following sections. -

Prev Up Next
24.3. Log File Maintenance Home 25.1. SQL Dump
\ No newline at end of file +

Prev Up Next
24.3. Log File Maintenance Home 25.1. SQL Dump
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bgworker.html postgresql-13-13.12/doc/src/sgml/html/bgworker.html --- postgresql-13-13.11/doc/src/sgml/html/bgworker.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bgworker.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 47. Background Worker Processes
Chapter 47. Background Worker Processes
Prev UpPart V. Server ProgrammingHome Next

Chapter 47. Background Worker Processes

+Chapter 47. Background Worker Processes

Chapter 47. Background Worker Processes
Prev UpPart V. Server ProgrammingHome Next

Chapter 47. Background Worker Processes

PostgreSQL can be extended to run user-supplied code in separate processes. Such processes are started, stopped and monitored by postgres, which permits them to have a lifetime closely linked to the server's status. @@ -232,4 +232,4 @@

The maximum number of registered background workers is limited by max_worker_processes. -

Prev Up Next
SPI_start_transaction Home Chapter 48. Logical Decoding
\ No newline at end of file +

Prev Up Next
SPI_start_transaction Home Chapter 48. Logical Decoding
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/biblio.html postgresql-13-13.12/doc/src/sgml/html/biblio.html --- postgresql-13-13.11/doc/src/sgml/html/biblio.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/biblio.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Bibliography
Bibliography
Prev UpPostgreSQL 13.11 DocumentationHome Next

Bibliography

+Bibliography

Bibliography
Prev UpPostgreSQL 13.12 DocumentationHome Next

Bibliography

Selected references and readings for SQL and PostgreSQL.

@@ -20,4 +20,4 @@ system”. M. Stonebraker, M. Hearst, and S. Potamianos. SIGMOD Record 18(3). Sept. 1989.

[ston89b] “The case for partial indexes”. M. Stonebraker. SIGMOD Record 18(4). Dec. 1989. 4–11.

[ston90a] “The implementation of POSTGRES”. M. Stonebraker, L. A. Rowe, and M. Hirohama. Transactions on Knowledge and Data Engineering 2(1). IEEE. March 1990.

[ston90b] “On - Rules, Procedures, Caching and Views in Database Systems”. M. Stonebraker, A. Jhingran, J. Goh, and S. Potamianos. ACM-SIGMOD Conference on Management of Data, June 1990.

Prev Up Next
O.4. pg_receivexlog renamed to pg_receivewal Home Index
\ No newline at end of file + Rules, Procedures, Caching and Views in Database Systems”. M. Stonebraker, A. Jhingran, J. Goh, and S. Potamianos. ACM-SIGMOD Conference on Management of Data, June 1990.

Prev Up Next
O.4. pg_receivexlog renamed to pg_receivewal Home Index
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bki-commands.html postgresql-13-13.12/doc/src/sgml/html/bki-commands.html --- postgresql-13-13.11/doc/src/sgml/html/bki-commands.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bki-commands.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.4. BKI Commands
70.4. BKI Commands
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.4. BKI Commands

+70.4. BKI Commands
70.4. BKI Commands
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.4. BKI Commands

create tablename tableoid @@ -106,4 +106,4 @@ is postponed.

build indices

Fill in the indices that have previously been declared. -

Prev Up Next
70.3. BKI File Format Home 70.5. Structure of the Bootstrap BKI File
\ No newline at end of file +

Prev Up Next
70.3. BKI File Format Home 70.5. Structure of the Bootstrap BKI File
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bki-example.html postgresql-13-13.12/doc/src/sgml/html/bki-example.html --- postgresql-13-13.11/doc/src/sgml/html/bki-example.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bki-example.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.6. BKI Example
70.6. BKI Example
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.6. BKI Example

+70.6. BKI Example

70.6. BKI Example
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.6. BKI Example

The following sequence of commands will create the table test_table with OID 420, having three columns oid, cola and colb @@ -12,4 +12,4 @@ insert ( 422 2 _null_ ) close test_table

-

Prev Up Next
70.5. Structure of the Bootstrap BKI File Home Chapter 71. How the Planner Uses Statistics
\ No newline at end of file +

Prev Up Next
70.5. Structure of the Bootstrap BKI File Home Chapter 71. How the Planner Uses Statistics
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bki-format.html postgresql-13-13.12/doc/src/sgml/html/bki-format.html --- postgresql-13-13.11/doc/src/sgml/html/bki-format.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bki-format.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.3. BKI File Format
70.3. BKI File Format
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.3. BKI File Format

+70.3. BKI File Format

70.3. BKI File Format
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.3. BKI File Format

This section describes how the PostgreSQL backend interprets BKI files. This description will be easier to understand if the postgres.bki @@ -16,4 +16,4 @@ strings. Everything is case sensitive.

Lines starting with # are ignored. -

Prev Up Next
70.2. System Catalog Initial Data Home 70.4. BKI Commands
\ No newline at end of file +

Prev Up Next
70.2. System Catalog Initial Data Home 70.4. BKI Commands
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bki-structure.html postgresql-13-13.12/doc/src/sgml/html/bki-structure.html --- postgresql-13-13.11/doc/src/sgml/html/bki-structure.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bki-structure.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.5. Structure of the Bootstrap BKI File
70.5. Structure of the Bootstrap BKI File
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.5. Structure of the Bootstrap BKI File

+70.5. Structure of the Bootstrap BKI File

70.5. Structure of the Bootstrap BKI File
Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

70.5. Structure of the Bootstrap BKI File

The open command cannot be used until the tables it uses exist and have entries for the table that is to be opened. (These minimum tables are pg_class, @@ -39,4 +39,4 @@

There are doubtless other, undocumented ordering dependencies. -

Prev Up Next
70.4. BKI Commands Home 70.6. BKI Example
\ No newline at end of file +

Prev Up Next
70.4. BKI Commands Home 70.6. BKI Example
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bki.html postgresql-13-13.12/doc/src/sgml/html/bki.html --- postgresql-13-13.11/doc/src/sgml/html/bki.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bki.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 70. System Catalog Declarations and Initial Contents
Chapter 70. System Catalog Declarations and Initial Contents
Prev UpPart VII. InternalsHome Next

Chapter 70. System Catalog Declarations and Initial Contents

Table of Contents

70.1. System Catalog Declaration Rules
70.2. System Catalog Initial Data
70.2.1. Data File Format
70.2.2. OID Assignment
70.2.3. OID Reference Lookup
70.2.4. Automatic Creation of Array Types
70.2.5. Recipes for Editing Data Files
70.3. BKI File Format
70.4. BKI Commands
70.5. Structure of the Bootstrap BKI File
70.6. BKI Example

+Chapter 70. System Catalog Declarations and Initial Contents

Chapter 70. System Catalog Declarations and Initial Contents
Prev UpPart VII. InternalsHome Next

Chapter 70. System Catalog Declarations and Initial Contents

Table of Contents

70.1. System Catalog Declaration Rules
70.2. System Catalog Initial Data
70.2.1. Data File Format
70.2.2. OID Assignment
70.2.3. OID Reference Lookup
70.2.4. Automatic Creation of Array Types
70.2.5. Recipes for Editing Data Files
70.3. BKI File Format
70.4. BKI Commands
70.5. Structure of the Bootstrap BKI File
70.6. BKI Example

PostgreSQL uses many different system catalogs to keep track of the existence and properties of database objects, such as tables and functions. Physically there is no difference between a system @@ -57,4 +57,4 @@ and/or initial data files. The rest of this chapter gives some information about that, and for completeness describes the BKI file format. -

Prev Up Next
69.7. Heap-Only Tuples (HOT) Home 70.1. System Catalog Declaration Rules
\ No newline at end of file +

Prev Up Next
69.7. Heap-Only Tuples (HOT) Home 70.1. System Catalog Declaration Rules
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bloom.html postgresql-13-13.12/doc/src/sgml/html/bloom.html --- postgresql-13-13.11/doc/src/sgml/html/bloom.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bloom.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.5. bloom
F.5. bloom
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.5. bloom

F.5.1. Parameters
F.5.2. Examples
F.5.3. Operator Class Interface
F.5.4. Limitations
F.5.5. Authors

+F.5. bloom

F.5. bloom
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.5. bloom

F.5.1. Parameters
F.5.2. Examples
F.5.3. Operator Class Interface
F.5.4. Limitations
F.5.5. Authors

bloom provides an index access method based on Bloom filters.

@@ -187,4 +187,4 @@

Oleg Bartunov , Postgres Professional, Moscow, Russia -

Prev Up Next
F.4. auto_explain Home F.6. btree_gin
\ No newline at end of file +

Prev Up Next
F.4. auto_explain Home F.6. btree_gin
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bookindex.html postgresql-13-13.12/doc/src/sgml/html/bookindex.html --- postgresql-13-13.11/doc/src/sgml/html/bookindex.html 2023-05-08 21:34:19.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bookindex.html 2023-08-07 20:32:40.000000000 +0000 @@ -1,5 +1,5 @@ -Index
Index
Prev UpPostgreSQL 13.11 DocumentationHome 

Index

Symbols +Index

Index
Prev UpPostgreSQL 13.12 DocumentationHome 

Index

Symbols | A | @@ -51,19 +51,19 @@ | Y | - Z

A

abbrev, Network Address Functions and Operators
ABORT, ABORT
abs, Mathematical Functions and Operators
ACL, Privileges
aclcontains, System Information Functions and Operators
acldefault, System Information Functions and Operators
aclexplode, System Information Functions and Operators
aclitem, Privileges
aclitemeq, System Information Functions and Operators
acos, Mathematical Functions and Operators
acosd, Mathematical Functions and Operators
acosh, Mathematical Functions and Operators
administration tools
externally maintained, Administration Tools
adminpack, adminpack
advisory lock, Advisory Locks
age, Date/Time Functions and Operators
aggregate function, Aggregate Functions, Aggregate Expressions, Aggregate Functions, User-Defined Aggregates
built-in, Aggregate Functions
invocation, Aggregate Expressions
moving aggregate, Moving-Aggregate Mode
ordered set, Ordered-Set Aggregates
partial aggregation, Partial Aggregation
polymorphic, Polymorphic and Variadic Aggregates
support functions for, Support Functions for Aggregates
user-defined, User-Defined Aggregates
variadic, Polymorphic and Variadic Aggregates
AIX, AIX
installation on, AIX
IPC configuration, Shared Memory and Semaphores
akeys, hstore Operators and Functions
alias, Table and Column Aliases, Column Labels
for table name in query, Joins Between Tables
in the FROM clause, Table and Column Aliases
in the select list, Column Labels
ALL, Subquery Expressions, Row and Array Comparisons
allow_in_place_tablespaces configuration parameter, Developer Options
allow_system_table_mods configuration parameter, Developer Options
ALTER AGGREGATE, ALTER AGGREGATE
ALTER COLLATION, ALTER COLLATION
ALTER CONVERSION, ALTER CONVERSION
ALTER DATABASE, ALTER DATABASE
ALTER DEFAULT PRIVILEGES, ALTER DEFAULT PRIVILEGES
ALTER DOMAIN, ALTER DOMAIN
ALTER EVENT TRIGGER, ALTER EVENT TRIGGER
ALTER EXTENSION, ALTER EXTENSION
ALTER FOREIGN DATA WRAPPER, ALTER FOREIGN DATA WRAPPER
ALTER FOREIGN TABLE, ALTER FOREIGN TABLE
ALTER FUNCTION, ALTER FUNCTION
ALTER GROUP, ALTER GROUP
ALTER INDEX, ALTER INDEX
ALTER LANGUAGE, ALTER LANGUAGE
ALTER LARGE OBJECT, ALTER LARGE OBJECT
ALTER MATERIALIZED VIEW, ALTER MATERIALIZED VIEW
ALTER OPERATOR, ALTER OPERATOR
ALTER OPERATOR CLASS, ALTER OPERATOR CLASS
ALTER OPERATOR FAMILY, ALTER OPERATOR FAMILY
ALTER POLICY, ALTER POLICY
ALTER PROCEDURE, ALTER PROCEDURE
ALTER PUBLICATION, ALTER PUBLICATION
ALTER ROLE, Role Attributes, ALTER ROLE
ALTER ROUTINE, ALTER ROUTINE
ALTER RULE, ALTER RULE
ALTER SCHEMA, ALTER SCHEMA
ALTER SEQUENCE, ALTER SEQUENCE
ALTER SERVER, ALTER SERVER
ALTER STATISTICS, ALTER STATISTICS
ALTER SUBSCRIPTION, ALTER SUBSCRIPTION
ALTER SYSTEM, ALTER SYSTEM
ALTER TABLE, ALTER TABLE
ALTER TABLESPACE, ALTER TABLESPACE
ALTER TEXT SEARCH CONFIGURATION, ALTER TEXT SEARCH CONFIGURATION
ALTER TEXT SEARCH DICTIONARY, ALTER TEXT SEARCH DICTIONARY
ALTER TEXT SEARCH PARSER, ALTER TEXT SEARCH PARSER
ALTER TEXT SEARCH TEMPLATE, ALTER TEXT SEARCH TEMPLATE
ALTER TRIGGER, ALTER TRIGGER
ALTER TYPE, ALTER TYPE
ALTER USER, ALTER USER
ALTER USER MAPPING, ALTER USER MAPPING
ALTER VIEW, ALTER VIEW
amcheck, amcheck
ANALYZE, Updating Planner Statistics, ANALYZE
AND (operator), Logical Operators
anonymous code blocks, DO
any, Pseudo-Types
ANY, Aggregate Functions, Subquery Expressions, Row and Array Comparisons
anyarray, Pseudo-Types
anycompatible, Pseudo-Types
anycompatiblearray, Pseudo-Types
anycompatiblenonarray, Pseudo-Types
anycompatiblerange, Pseudo-Types
anyelement, Pseudo-Types
anyenum, Pseudo-Types
anynonarray, Pseudo-Types
anyrange, Pseudo-Types
applicable role, applicable_roles
application_name configuration parameter, What to Log
arbitrary precision numbers, Arbitrary Precision Numbers
archive_cleanup_command configuration parameter, Archive Recovery
archive_command configuration parameter, Archiving
archive_mode configuration parameter, Archiving
archive_timeout configuration parameter, Archiving
area, Geometric Functions and Operators
armor, armor(), dearmor()
array, Arrays
accessing, Accessing Arrays
constant, Array Value Input
constructor, Array Constructors
declaration, Declaration of Array Types
I/O, Array Input and Output Syntax
modifying, Modifying Arrays
of user-defined type, User-Defined Types
searching, Searching in Arrays
ARRAY, Array Constructors, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
array_agg, Aggregate Functions, Functions
array_append, Array Functions and Operators
array_cat, Array Functions and Operators
array_dims, Array Functions and Operators
array_fill, Array Functions and Operators
array_length, Array Functions and Operators
array_lower, Array Functions and Operators
array_ndims, Array Functions and Operators
array_nulls configuration parameter, Previous PostgreSQL Versions
array_position, Array Functions and Operators
array_positions, Array Functions and Operators
array_prepend, Array Functions and Operators
array_remove, Array Functions and Operators
array_replace, Array Functions and Operators
array_to_json, Processing and Creating JSON Data
array_to_string, Array Functions and Operators
array_to_tsvector, Text Search Functions and Operators
array_upper, Array Functions and Operators
ascii, String Functions and Operators
asin, Mathematical Functions and Operators
asind, Mathematical Functions and Operators
asinh, Mathematical Functions and Operators
ASSERT
in PL/pgSQL, Checking Assertions
assertions
in PL/pgSQL, Checking Assertions
asynchronous commit, Asynchronous Commit
AT TIME ZONE, AT TIME ZONE
atan, Mathematical Functions and Operators
atan2, Mathematical Functions and Operators
atan2d, Mathematical Functions and Operators
atand, Mathematical Functions and Operators
atanh, Mathematical Functions and Operators
authentication_timeout configuration parameter, Authentication
auth_delay, auth_delay
auth_delay.milliseconds configuration parameter, Configuration Parameters
auto-increment (see serial)
autocommit
bulk-loading data, Disable Autocommit
psql, Variables
autosummarize storage parameter, Index Storage Parameters
autovacuum
configuration parameters, Automatic Vacuuming
general information, The Autovacuum Daemon
autovacuum configuration parameter, Automatic Vacuuming
autovacuum_analyze_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_analyze_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_enabled storage parameter, Storage Parameters
autovacuum_freeze_max_age
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_freeze_min_age storage parameter, Storage Parameters
autovacuum_freeze_table_age storage parameter, Storage Parameters
autovacuum_max_workers configuration parameter, Automatic Vacuuming
autovacuum_multixact_freeze_max_age
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_multixact_freeze_min_age storage parameter, Storage Parameters
autovacuum_multixact_freeze_table_age storage parameter, Storage Parameters
autovacuum_naptime configuration parameter, Automatic Vacuuming
autovacuum_vacuum_cost_delay
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_cost_limit
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_insert_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_insert_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_work_mem configuration parameter, Memory
auto_explain, auto_explain
auto_explain.log_analyze configuration parameter, Configuration Parameters
auto_explain.log_buffers configuration parameter, Configuration Parameters
auto_explain.log_format configuration parameter, Configuration Parameters
auto_explain.log_level configuration parameter, Configuration Parameters
auto_explain.log_min_duration configuration parameter, Configuration Parameters
auto_explain.log_nested_statements configuration parameter, Configuration Parameters
auto_explain.log_settings configuration parameter, Configuration Parameters
auto_explain.log_timing configuration parameter, Configuration Parameters
auto_explain.log_triggers configuration parameter, Configuration Parameters
auto_explain.log_verbose configuration parameter, Configuration Parameters
auto_explain.log_wal configuration parameter, Configuration Parameters
auto_explain.sample_rate configuration parameter, Configuration Parameters
avals, hstore Operators and Functions
average, Aggregate Functions
avg, Aggregate Functions

B

B-tree (see index)
backend_flush_after configuration parameter, Asynchronous Behavior
Background workers, Background Worker Processes
backslash escapes, String Constants with C-Style Escapes
backslash_quote configuration parameter, Previous PostgreSQL Versions
backtrace_functions configuration parameter, Developer Options
backup, Backup Control Functions, Backup and Restore
Backup Manifest, Backup Manifest Format
base type, The PostgreSQL Type System
base64 format, Binary String Functions and Operators
BASE_BACKUP, Streaming Replication Protocol
BEGIN, BEGIN
BETWEEN, Comparison Functions and Operators
BETWEEN SYMMETRIC, Comparison Functions and Operators
BGWORKER_BACKEND_​DATABASE_CONNECTION, Background Worker Processes
BGWORKER_SHMEM_ACCESS, Background Worker Processes
bgwriter_delay configuration parameter, Background Writer
bgwriter_flush_after configuration parameter, Background Writer
bgwriter_lru_maxpages configuration parameter, Background Writer
bgwriter_lru_multiplier configuration parameter, Background Writer
bigint, Numeric Constants, Integer Types
bigserial, Serial Types
binary data, Binary Data Types, Binary String Functions and Operators
functions, Binary String Functions and Operators
binary string
concatenation, Binary String Functions and Operators
converting to character string, Binary String Functions and Operators
length, Binary String Functions and Operators
bison, Requirements
bit string, Bit-String Constants, Bit String Types
constant, Bit-String Constants
data type, Bit String Types
length, Bit String Functions and Operators
bit strings, Bit String Functions and Operators
functions, Bit String Functions and Operators
bitmap scan, Combining Multiple Indexes, Planner Method Configuration
bit_and, Aggregate Functions
bit_length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
bit_or, Aggregate Functions
BLOB (see large object)
block_size configuration parameter, Preset Options
bloom, bloom
bonjour configuration parameter, Connection Settings
bonjour_name configuration parameter, Connection Settings
Boolean, Boolean Type
data type, Boolean Type
operators (see operators, logical)
bool_and, Aggregate Functions
bool_or, Aggregate Functions
booting
starting the server during, Starting the Database Server
bound_box, Geometric Functions and Operators
box, Geometric Functions and Operators
box (data type), Boxes
BRIN (see index)
brin_desummarize_range, Index Maintenance Functions
brin_metapage_info, BRIN Functions
brin_page_items, BRIN Functions
brin_page_type, BRIN Functions
brin_revmap_data, BRIN Functions
brin_summarize_new_values, Index Maintenance Functions
brin_summarize_range, Index Maintenance Functions
broadcast, Network Address Functions and Operators
BSD Authentication, BSD Authentication
btree_gin, btree_gin
btree_gist, btree_gist
btrim, String Functions and Operators, Binary String Functions and Operators
bt_index_check, Functions
bt_index_parent_check, Functions
bt_metap, B-Tree Functions
bt_page_items, B-Tree Functions
bt_page_stats, B-Tree Functions
buffering storage parameter, Index Storage Parameters
bytea, Binary Data Types
bytea_output configuration parameter, Statement Behavior

C

C, libpq — C Library, ECPG — Embedded SQL in C
C++, Using C++ for Extensibility
CALL, CALL
canceling, Canceling Queries in Progress
SQL command, Canceling Queries in Progress
cardinality, Array Functions and Operators
CASCADE, Dependency Tracking
with DROP, Dependency Tracking
foreign key action, Foreign Keys
Cascading Replication, High Availability, Load Balancing, and Replication
CASE, Conditional Expressions, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
case sensitivity
of SQL commands, Identifiers and Key Words
cast, CREATE CAST
I/O conversion, CREATE CAST
cbrt, Mathematical Functions and Operators
ceil, Mathematical Functions and Operators
ceiling, Mathematical Functions and Operators
center, Geometric Functions and Operators
Certificate, Certificate Authentication
chained transactions, Transaction Management, Parameters, Parameters
in PL/pgSQL, Transaction Management
char, Character Types
character, Character Types
character set, Locale and Formatting, Preset Options, Character Set Support
character string, String Constants, Character Types
concatenation, String Functions and Operators
constant, String Constants
converting to binary string, Binary String Functions and Operators
data types, Character Types
length, String Functions and Operators
character varying, Character Types
character_length, String Functions and Operators
char_length, String Functions and Operators
check constraint, Check Constraints
CHECK OPTION, CREATE VIEW
checkpoint, WAL Configuration
CHECKPOINT, CHECKPOINT
checkpoint_completion_target configuration parameter, Checkpoints
checkpoint_flush_after configuration parameter, Checkpoints
checkpoint_timeout configuration parameter, Checkpoints
checkpoint_warning configuration parameter, Checkpoints
check_function_bodies configuration parameter, Statement Behavior
chr, String Functions and Operators
cid, Object Identifier Types
cidr, cidr
circle, Circles, Geometric Functions and Operators
citext, citext
client authentication, Client Authentication
timeout during, Authentication
client_encoding configuration parameter, Locale and Formatting
client_min_messages configuration parameter, Statement Behavior
clock_timestamp, Date/Time Functions and Operators
CLOSE, CLOSE
cluster
of databases (see database cluster)
CLUSTER, CLUSTER
clusterdb, clusterdb
clustering, High Availability, Load Balancing, and Replication
cluster_name configuration parameter, Process Title
cmax, System Columns
cmin, System Columns
COALESCE, COALESCE
COLLATE, Collation Expressions
collation, Collation Support
in PL/pgSQL, Collation of PL/pgSQL Variables
in SQL functions, SQL Functions with Collations
COLLATION FOR, System Information Functions and Operators
color, Color Support
column, Concepts, Table Basics
adding, Adding a Column
removing, Removing a Column
renaming, Renaming a Column
system column, System Columns
column data type
changing, Changing a Column's Data Type
column reference, Column References
col_description, System Information Functions and Operators
comment, Comments
about database objects, System Information Functions and Operators
in SQL, Comments
COMMENT, COMMENT
COMMIT, COMMIT
COMMIT PREPARED, COMMIT PREPARED
commit_delay configuration parameter, Settings
commit_siblings configuration parameter, Settings
common table expression (see WITH)
comparison, Comparison Functions and Operators, Subquery Expressions
composite type, Row and Array Comparisons
operators, Comparison Functions and Operators
row constructor, Row and Array Comparisons
subquery result row, Subquery Expressions
compiling, Building libpq Programs
libpq applications, Building libpq Programs
composite type, Composite Types, The PostgreSQL Type System
comparison, Row and Array Comparisons
constant, Constructing Composite Values
constructor, Row Constructors
computed field, Using Composite Types in Queries
concat, String Functions and Operators
concat_ws, String Functions and Operators
concurrency, Concurrency Control
conditional expression, Conditional Expressions
configuration
of recovery
of a standby server, Archive Recovery
of the server, Server Configuration
of the server
functions, Configuration Settings Functions
configure, Installation Procedure
configure environment variables, configure Environment Variables
configure options, configure Options
config_file configuration parameter, File Locations
conjunction, Logical Operators
connectby, Functions Provided, connectby
connection service file, The Connection Service File
conninfo, Connection Strings
constant, Constants
constraint, Constraints
adding, Adding a Constraint
check, Check Constraints
exclusion, Exclusion Constraints
foreign key, Foreign Keys
name, Check Constraints
NOT NULL, Not-Null Constraints
primary key, Primary Keys
removing, Removing a Constraint
unique, Unique Constraints
constraint exclusion, Partitioning and Constraint Exclusion, Other Planner Options
constraint_exclusion configuration parameter, Other Planner Options
container type, The PostgreSQL Type System
CONTINUE
in PL/pgSQL, CONTINUE
continuous archiving, Backup and Restore
in standby, Continuous Archiving in Standby
control file, Extension Files
convert, Binary String Functions and Operators
convert_from, Binary String Functions and Operators
convert_to, Binary String Functions and Operators
COPY, Populating a Table With Rows, Functions Associated with the COPY Command, COPY
with libpq, Functions Associated with the COPY Command
corr, Aggregate Functions
correlation, Aggregate Functions
in the query planner, Extended Statistics
cos, Mathematical Functions and Operators
cosd, Mathematical Functions and Operators
cosh, Mathematical Functions and Operators
cot, Mathematical Functions and Operators
cotd, Mathematical Functions and Operators
count, Aggregate Functions
covariance
population, Aggregate Functions
sample, Aggregate Functions
covar_pop, Aggregate Functions
covar_samp, Aggregate Functions
covering index, Index-Only Scans and Covering Indexes
cpu_index_tuple_cost configuration parameter, Planner Cost Constants
cpu_operator_cost configuration parameter, Planner Cost Constants
cpu_tuple_cost configuration parameter, Planner Cost Constants
CREATE ACCESS METHOD, CREATE ACCESS METHOD
CREATE AGGREGATE, CREATE AGGREGATE
CREATE CAST, CREATE CAST
CREATE COLLATION, CREATE COLLATION
CREATE CONVERSION, CREATE CONVERSION
CREATE DATABASE, Creating a Database, CREATE DATABASE
CREATE DOMAIN, CREATE DOMAIN
CREATE EVENT TRIGGER, CREATE EVENT TRIGGER
CREATE EXTENSION, CREATE EXTENSION
CREATE FOREIGN DATA WRAPPER, CREATE FOREIGN DATA WRAPPER
CREATE FOREIGN TABLE, CREATE FOREIGN TABLE
CREATE FUNCTION, CREATE FUNCTION
CREATE GROUP, CREATE GROUP
CREATE INDEX, CREATE INDEX
CREATE LANGUAGE, CREATE LANGUAGE
CREATE MATERIALIZED VIEW, CREATE MATERIALIZED VIEW
CREATE OPERATOR, CREATE OPERATOR
CREATE OPERATOR CLASS, CREATE OPERATOR CLASS
CREATE OPERATOR FAMILY, CREATE OPERATOR FAMILY
CREATE POLICY, CREATE POLICY
CREATE PROCEDURE, CREATE PROCEDURE
CREATE PUBLICATION, CREATE PUBLICATION
CREATE ROLE, Database Roles, CREATE ROLE
CREATE RULE, CREATE RULE
CREATE SCHEMA, CREATE SCHEMA
CREATE SEQUENCE, CREATE SEQUENCE
CREATE SERVER, CREATE SERVER
CREATE STATISTICS, CREATE STATISTICS
CREATE SUBSCRIPTION, CREATE SUBSCRIPTION
CREATE TABLE, Creating a New Table, CREATE TABLE
CREATE TABLE AS, CREATE TABLE AS
CREATE TABLESPACE, Tablespaces, CREATE TABLESPACE
CREATE TEXT SEARCH CONFIGURATION, CREATE TEXT SEARCH CONFIGURATION
CREATE TEXT SEARCH DICTIONARY, CREATE TEXT SEARCH DICTIONARY
CREATE TEXT SEARCH PARSER, CREATE TEXT SEARCH PARSER
CREATE TEXT SEARCH TEMPLATE, CREATE TEXT SEARCH TEMPLATE
CREATE TRANSFORM, CREATE TRANSFORM
CREATE TRIGGER, CREATE TRIGGER
CREATE TYPE, CREATE TYPE
CREATE USER, CREATE USER
CREATE USER MAPPING, CREATE USER MAPPING
CREATE VIEW, CREATE VIEW
createdb, Creating a Database, Creating a Database, createdb
createuser, Database Roles, createuser
CREATE_REPLICATION_SLOT, Streaming Replication Protocol
cross compilation, Build Process Details
cross join, Joined Tables
crosstab, crosstab(text), crosstabN(text), crosstab(text, text)
crypt, crypt()
cstring, Pseudo-Types
CSV (Comma-Separated Values) format
in psql, Meta-Commands
ctid, System Columns
CTID, View Rules in Non-SELECT Statements
CUBE, GROUPING SETS, CUBE, and ROLLUP
cube (extension), cube
cume_dist, Window Functions
hypothetical, Aggregate Functions
current_catalog, System Information Functions and Operators
current_database, System Information Functions and Operators
current_date, Date/Time Functions and Operators
current_logfiles
and the log_destination configuration parameter, Where to Log
and the pg_current_logfile function, System Information Functions and Operators
current_query, System Information Functions and Operators
current_role, System Information Functions and Operators
current_schema, System Information Functions and Operators
current_schemas, System Information Functions and Operators
current_setting, Configuration Settings Functions
current_time, Date/Time Functions and Operators
current_timestamp, Date/Time Functions and Operators
current_user, System Information Functions and Operators
currval, Sequence Manipulation Functions
cursor, Cursors, CLOSE, DECLARE, EXPLAIN, FETCH, MOVE
CLOSE, CLOSE
DECLARE, DECLARE
FETCH, FETCH
in PL/pgSQL, Cursors
MOVE, MOVE
showing the query plan, EXPLAIN
cursor_tuple_fraction configuration parameter, Other Planner Options
custom scan provider, Writing a Custom Scan Provider
handler for, Writing a Custom Scan Provider
Cygwin, Cygwin
installation on, Cygwin

D

data area (see database cluster)
data partitioning, High Availability, Load Balancing, and Replication
data type, Data Types, Numeric Types, Enumerated Types, Domain Types, Type Conversion, The PostgreSQL Type System, The PostgreSQL Type System, The PostgreSQL Type System, Polymorphic Types, Base Types in C-Language Functions, User-Defined Types
base, The PostgreSQL Type System
category, Overview
composite, The PostgreSQL Type System
constant, Constants of Other Types
container, The PostgreSQL Type System
conversion, Type Conversion
domain, Domain Types
enumerated (enum), Enumerated Types
internal organization, Base Types in C-Language Functions
numeric, Numeric Types
polymorphic, Polymorphic Types
type cast, Type Casts
user-defined, User-Defined Types
database, Creating a Database, Managing Databases
creating, Creating a Database
privilege to create, Role Attributes
database activity, Monitoring Database Activity
monitoring, Monitoring Database Activity
database cluster, Concepts, Creating a Database Cluster
data_checksums configuration parameter, Preset Options
data_directory configuration parameter, File Locations
data_directory_mode configuration parameter, Preset Options
data_sync_retry configuration parameter, Error Handling
date, Date/Time Types, Dates
constants, Special Values
current, Current Date/Time
output format, Date/Time Output
(see also formatting)
DateStyle configuration parameter, Locale and Formatting
date_part, Date/Time Functions and Operators, EXTRACT, date_part
date_trunc, Date/Time Functions and Operators, date_trunc
dblink, dblink, dblink
dblink_build_sql_delete, dblink_build_sql_delete
dblink_build_sql_insert, dblink_build_sql_insert
dblink_build_sql_update, dblink_build_sql_update
dblink_cancel_query, dblink_cancel_query
dblink_close, dblink_close
dblink_connect, dblink_connect
dblink_connect_u, dblink_connect_u
dblink_disconnect, dblink_disconnect
dblink_error_message, dblink_error_message
dblink_exec, dblink_exec
dblink_fetch, dblink_fetch
dblink_get_connections, dblink_get_connections
dblink_get_notify, dblink_get_notify
dblink_get_pkey, dblink_get_pkey
dblink_get_result, dblink_get_result
dblink_is_busy, dblink_is_busy
dblink_open, dblink_open
dblink_send_query, dblink_send_query
db_user_namespace configuration parameter, Authentication
deadlock, Deadlocks
timeout during, Lock Management
deadlock_timeout configuration parameter, Lock Management
DEALLOCATE, DEALLOCATE
dearmor, armor(), dearmor()
debug_assertions configuration parameter, Preset Options
debug_deadlocks configuration parameter, Developer Options
debug_pretty_print configuration parameter, What to Log
debug_print_parse configuration parameter, What to Log
debug_print_plan configuration parameter, What to Log
debug_print_rewritten configuration parameter, What to Log
decimal (see numeric)
DECLARE, DECLARE
decode, Binary String Functions and Operators
decode_bytea
in PL/Perl, Utility Functions in PL/Perl
decrypt, Raw Encryption Functions
decrypt_iv, Raw Encryption Functions
deduplicate_items storage parameter, Index Storage Parameters
default value, Default Values
changing, Changing a Column's Default Value
default_statistics_target configuration parameter, Other Planner Options
default_tablespace configuration parameter, Statement Behavior
default_table_access_method configuration parameter, Statement Behavior
default_text_search_config configuration parameter, Locale and Formatting
default_transaction_deferrable configuration parameter, Statement Behavior
default_transaction_isolation configuration parameter, Statement Behavior
default_transaction_read_only configuration parameter, Statement Behavior
deferrable transaction, Statement Behavior
setting, SET TRANSACTION
setting default, Statement Behavior
defined, hstore Operators and Functions
degrees, Mathematical Functions and Operators
delay, Delaying Execution
DELETE, Deletions, Deleting Data, Returning Data from Modified Rows, DELETE
RETURNING, Returning Data from Modified Rows
delete, hstore Operators and Functions
deleting, Deleting Data
dense_rank, Window Functions
hypothetical, Aggregate Functions
diagonal, Geometric Functions and Operators
diameter, Geometric Functions and Operators
dict_int, dict_int
dict_xsyn, dict_xsyn
difference, Soundex
digest, digest()
dirty read, Transaction Isolation
DISCARD, DISCARD
disjunction, Logical Operators
disk drive, WAL Internals
disk space, Recovering Disk Space
disk usage, Determining Disk Usage
DISTINCT, Querying a Table, DISTINCT
div, Mathematical Functions and Operators
dmetaphone, Double Metaphone
dmetaphone_alt, Double Metaphone
DO, DO
document, What Is a Document?
text search, What Is a Document?
dollar quoting, Dollar-Quoted String Constants
domain, Domain Types
double precision, Floating-Point Types
DROP ACCESS METHOD, DROP ACCESS METHOD
DROP AGGREGATE, DROP AGGREGATE
DROP CAST, DROP CAST
DROP COLLATION, DROP COLLATION
DROP CONVERSION, DROP CONVERSION
DROP DATABASE, Destroying a Database, DROP DATABASE
DROP DOMAIN, DROP DOMAIN
DROP EVENT TRIGGER, DROP EVENT TRIGGER
DROP EXTENSION, DROP EXTENSION
DROP FOREIGN DATA WRAPPER, DROP FOREIGN DATA WRAPPER
DROP FOREIGN TABLE, DROP FOREIGN TABLE
DROP FUNCTION, DROP FUNCTION
DROP GROUP, DROP GROUP
DROP INDEX, DROP INDEX
DROP LANGUAGE, DROP LANGUAGE
DROP MATERIALIZED VIEW, DROP MATERIALIZED VIEW
DROP OPERATOR, DROP OPERATOR
DROP OPERATOR CLASS, DROP OPERATOR CLASS
DROP OPERATOR FAMILY, DROP OPERATOR FAMILY
DROP OWNED, DROP OWNED
DROP POLICY, DROP POLICY
DROP PROCEDURE, DROP PROCEDURE
DROP PUBLICATION, DROP PUBLICATION
DROP ROLE, Database Roles, DROP ROLE
DROP ROUTINE, DROP ROUTINE
DROP RULE, DROP RULE
DROP SCHEMA, DROP SCHEMA
DROP SEQUENCE, DROP SEQUENCE
DROP SERVER, DROP SERVER
DROP STATISTICS, DROP STATISTICS
DROP SUBSCRIPTION, DROP SUBSCRIPTION
DROP TABLE, Creating a New Table, DROP TABLE
DROP TABLESPACE, DROP TABLESPACE
DROP TEXT SEARCH CONFIGURATION, DROP TEXT SEARCH CONFIGURATION
DROP TEXT SEARCH DICTIONARY, DROP TEXT SEARCH DICTIONARY
DROP TEXT SEARCH PARSER, DROP TEXT SEARCH PARSER
DROP TEXT SEARCH TEMPLATE, DROP TEXT SEARCH TEMPLATE
DROP TRANSFORM, DROP TRANSFORM
DROP TRIGGER, DROP TRIGGER
DROP TYPE, DROP TYPE
DROP USER, DROP USER
DROP USER MAPPING, DROP USER MAPPING
DROP VIEW, DROP VIEW
dropdb, Destroying a Database, dropdb
dropuser, Database Roles, dropuser
DROP_REPLICATION_SLOT, Streaming Replication Protocol
DTD, Creating XML Values
DTrace, Developer Options, Dynamic Tracing
duplicate, Querying a Table
duplicates, DISTINCT
dynamic loading, Other Defaults, Dynamic Loading
dynamic_library_path, Dynamic Loading
dynamic_library_path configuration parameter, Other Defaults
dynamic_shared_memory_type configuration parameter, Memory

E

each, hstore Operators and Functions
earth, Cube-Based Earth Distances
earthdistance, earthdistance
earth_box, Cube-Based Earth Distances
earth_distance, Cube-Based Earth Distances
ECPG, ECPG — Embedded SQL in C
ecpg, ecpg
effective_cache_size configuration parameter, Planner Cost Constants
effective_io_concurrency configuration parameter, Asynchronous Behavior
elog, Reporting Errors Within the Server
in PL/Perl, Utility Functions in PL/Perl
in PL/Python, Utility Functions
in PL/Tcl, Database Access from PL/Tcl
embedded SQL, ECPG — Embedded SQL in C
in C, ECPG — Embedded SQL in C
enabled role, enabled_roles
enable_bitmapscan configuration parameter, Planner Method Configuration
enable_gathermerge configuration parameter, Planner Method Configuration
enable_hashagg configuration parameter, Planner Method Configuration
enable_hashjoin configuration parameter, Planner Method Configuration
enable_incremental_sort configuration parameter, Planner Method Configuration
enable_indexonlyscan configuration parameter, Planner Method Configuration
enable_indexscan configuration parameter, Planner Method Configuration
enable_material configuration parameter, Planner Method Configuration
enable_mergejoin configuration parameter, Planner Method Configuration
enable_nestloop configuration parameter, Planner Method Configuration
enable_parallel_append configuration parameter, Planner Method Configuration
enable_parallel_hash configuration parameter, Planner Method Configuration
enable_partitionwise_aggregate configuration parameter, Planner Method Configuration
enable_partitionwise_join configuration parameter, Planner Method Configuration
enable_partition_pruning configuration parameter, Planner Method Configuration
enable_seqscan configuration parameter, Planner Method Configuration
enable_sort configuration parameter, Planner Method Configuration
enable_tidscan configuration parameter, Planner Method Configuration
encode, Binary String Functions and Operators
encode_array_constructor
in PL/Perl, Utility Functions in PL/Perl
encode_array_literal
in PL/Perl, Utility Functions in PL/Perl
encode_bytea
in PL/Perl, Utility Functions in PL/Perl
encode_typed_literal
in PL/Perl, Utility Functions in PL/Perl
encrypt, Raw Encryption Functions
encryption, Encryption Options, pgcrypto
for specific columns, pgcrypto
encrypt_iv, Raw Encryption Functions
END, END
enumerated types, Enumerated Types
enum_first, Enum Support Functions
enum_last, Enum Support Functions
enum_range, Enum Support Functions
environment variable, Environment Variables
ephemeral named relation
registering with SPI, SPI_register_relation, SPI_register_trigger_data
unregistering from SPI, SPI_unregister_relation
ereport, Reporting Errors Within the Server
error codes, PostgreSQL Error Codes
libpq, Main Functions
list of, PostgreSQL Error Codes
error message, Connection Status Functions
escape format, Binary String Functions and Operators
escape string syntax, String Constants with C-Style Escapes
escape_string_warning configuration parameter, Previous PostgreSQL Versions
escaping strings, Escaping Strings for Inclusion in SQL Commands
in libpq, Escaping Strings for Inclusion in SQL Commands
event log, Registering Event Log on Windows
event log, Registering Event Log on Windows
event trigger, Event Triggers, Writing Event Trigger Functions in C
in C, Writing Event Trigger Functions in C
in PL/Tcl, Event Trigger Functions in PL/Tcl
event_source configuration parameter, Where to Log
event_trigger, Pseudo-Types
every, Aggregate Functions
EXCEPT, Combining Queries
exceptions
in PL/pgSQL, Trapping Errors
in PL/Tcl, Error Handling in PL/Tcl
exclusion constraint, Exclusion Constraints
EXECUTE, EXECUTE
exist, hstore Operators and Functions
EXISTS, Subquery Expressions
EXIT
in PL/pgSQL, EXIT
exit_on_error configuration parameter, Error Handling
exp, Mathematical Functions and Operators
EXPLAIN, Using EXPLAIN, EXPLAIN
expression, Value Expressions
order of evaluation, Expression Evaluation Rules
syntax, Value Expressions
extending SQL, Extending SQL
extension, Packaging Related Objects into an Extension
externally maintained, Extensions
external_pid_file configuration parameter, File Locations
extract, Date/Time Functions and Operators, EXTRACT, date_part
extra_float_digits configuration parameter, Locale and Formatting

F

factorial, Mathematical Functions and Operators
failover, High Availability, Load Balancing, and Replication
false, Boolean Type
family, Network Address Functions and Operators
fast path, The Fast-Path Interface
fastupdate storage parameter, Index Storage Parameters
fdw_handler, Pseudo-Types
FETCH, FETCH
field
computed, Using Composite Types in Queries
field selection, Field Selection
file system mount points, Use of Secondary File Systems
file_fdw, file_fdw
fillfactor storage parameter, Index Storage Parameters, Storage Parameters
FILTER, Aggregate Expressions
first_value, Window Functions
flex, Requirements
float4 (see real)
float8 (see double precision)
floating point, Floating-Point Types
floating-point
display, Locale and Formatting
floor, Mathematical Functions and Operators
force_parallel_mode configuration parameter, Other Planner Options
foreign data, Foreign Data
foreign data wrapper, Writing a Foreign Data Wrapper
handler for, Writing a Foreign Data Wrapper
foreign key, Foreign Keys, Foreign Keys
self-referential, Foreign Keys
foreign table, Foreign Data
format, String Functions and Operators, format
use in PL/pgSQL, Executing Dynamic Commands
formatting, Data Type Formatting Functions
format_type, System Information Functions and Operators
Free Space Map, Free Space Map
FreeBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
from_collapse_limit configuration parameter, Other Planner Options
FSM (see Free Space Map)
fsm_page_contents, General Functions
fsync configuration parameter, Settings
full text search, Text Search Types, Text Search Types, Full Text Search
data types, Text Search Types
functions and operators, Text Search Types
full_page_writes configuration parameter, Settings
function, Table Functions, Functions and Operators, Statistics Information Functions, Functions, Polymorphic Types, User-Defined Functions, Query Language (SQL) Functions, Internal Functions, C-Language Functions
default values for arguments, SQL Functions with Default Values for Arguments
in the FROM clause, Table Functions
internal, Internal Functions
invocation, Function Calls
mixed notation, Using Mixed Notation
named argument, Arguments for SQL Functions
named notation, Using Named Notation
output parameter, SQL Functions with Output Parameters
polymorphic, Polymorphic Types
positional notation, Using Positional Notation
RETURNS TABLE, SQL Functions Returning TABLE
statistics, Statistics Information Functions
type resolution in an invocation, Functions
user-defined, User-Defined Functions, Query Language (SQL) Functions, C-Language Functions
in C, C-Language Functions
in SQL, Query Language (SQL) Functions
variadic, SQL Functions with Variable Numbers of Arguments
with SETOF, SQL Functions Returning Sets
functional dependency, The GROUP BY and HAVING Clauses
fuzzystrmatch, fuzzystrmatch

G

gcd, Mathematical Functions and Operators
gc_to_sec, Cube-Based Earth Distances
generated column, Generated Columns, Parameters, Parameters
in - triggers, Overview of Trigger Behavior
generate_series, Set Returning Functions
generate_subscripts, Set Returning Functions
genetic query optimization, Genetic Query Optimizer
gen_random_bytes, Random-Data Functions
gen_random_uuid, UUID Functions, Random-Data Functions
gen_salt, gen_salt()
GEQO (see genetic query optimization)
geqo configuration parameter, Genetic Query Optimizer
geqo_effort configuration parameter, Genetic Query Optimizer
geqo_generations configuration parameter, Genetic Query Optimizer
geqo_pool_size configuration parameter, Genetic Query Optimizer
geqo_seed configuration parameter, Genetic Query Optimizer
geqo_selection_bias configuration parameter, Genetic Query Optimizer
geqo_threshold configuration parameter, Genetic Query Optimizer
get_bit, Binary String Functions and Operators, Bit String Functions and Operators
get_byte, Binary String Functions and Operators
get_current_ts_config, Text Search Functions and Operators
get_raw_page, General Functions
GIN (see index)
gin_clean_pending_list, Index Maintenance Functions
gin_fuzzy_search_limit configuration parameter, Other Defaults
gin_leafpage_items, GIN Functions
gin_metapage_info, GIN Functions
gin_page_opaque_info, GIN Functions
gin_pending_list_limit
configuration parameter, Statement Behavior
storage parameter, Index Storage Parameters
GiST (see index)
global data, Global Data in PL/Tcl
in PL/Python, Sharing Data
in PL/Tcl, Global Data in PL/Tcl
GRANT, Privileges, GRANT
GREATEST, GREATEST and LEAST, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
Gregorian calendar, History of Units
GROUP BY, Aggregate Functions, The GROUP BY and HAVING Clauses
grouping, The GROUP BY and HAVING Clauses
GROUPING, Aggregate Functions
GROUPING SETS, GROUPING SETS, CUBE, and ROLLUP
gssapi, Secure TCP/IP Connections with GSSAPI Encryption
GSSAPI, GSSAPI Authentication
with - libpq, Parameter Key Words
GUID, UUID Type

H

hash (see index)
hash_bitmap_info, Hash Functions
hash_mem_multiplier configuration parameter, Memory
hash_metapage_info, Hash Functions
hash_page_items, Hash Functions
hash_page_stats, Hash Functions
hash_page_type, Hash Functions
has_any_column_privilege, System Information Functions and Operators
has_column_privilege, System Information Functions and Operators
has_database_privilege, System Information Functions and Operators
has_foreign_data_wrapper_privilege, System Information Functions and Operators
has_function_privilege, System Information Functions and Operators
has_language_privilege, System Information Functions and Operators
has_schema_privilege, System Information Functions and Operators
has_sequence_privilege, System Information Functions and Operators
has_server_privilege, System Information Functions and Operators
has_tablespace_privilege, System Information Functions and Operators
has_table_privilege, System Information Functions and Operators
has_type_privilege, System Information Functions and Operators
HAVING, Aggregate Functions, The GROUP BY and HAVING Clauses
hba_file configuration parameter, File Locations
heap_page_items, Heap Functions
heap_page_item_attrs, Heap Functions
heap_tuple_infomask_flags, Heap Functions
height, Geometric Functions and Operators
hex format, Binary String Functions and Operators
hierarchical database, Concepts
high availability, High Availability, Load Balancing, and Replication
history, A Brief History of PostgreSQL
of PostgreSQL, A Brief History of PostgreSQL
hmac, hmac()
host, Network Address Functions and Operators
host - name, Parameter Key Words
hostmask, Network Address Functions and Operators
Hot Standby, High Availability, Load Balancing, and Replication
hot_standby configuration parameter, Standby Servers
hot_standby_feedback configuration parameter, Standby Servers
HP-UX
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
hstore, hstore, hstore Operators and Functions
hstore_to_array, hstore Operators and Functions
hstore_to_json, hstore Operators and Functions
hstore_to_jsonb, hstore Operators and Functions
hstore_to_jsonb_loose, hstore Operators and Functions
hstore_to_json_loose, hstore Operators and Functions
hstore_to_matrix, hstore Operators and Functions
huge_pages configuration parameter, Memory
hypothetical-set aggregate
built-in, Aggregate Functions

I

icount, intarray Functions and Operators
ICU, PostgreSQL Features, Managing Collations, Parameters
ident, Ident Authentication
identifier, Identifiers and Key Words
length, Identifiers and Key Words
syntax of, Identifiers and Key Words
IDENTIFY_SYSTEM, Streaming Replication Protocol
ident_file configuration parameter, File Locations
idle_in_transaction_session_timeout configuration parameter, Statement Behavior
idx, intarray Functions and Operators
IFNULL, COALESCE
ignore_checksum_failure configuration parameter, Developer Options
ignore_invalid_pages configuration parameter, Developer Options
ignore_system_indexes configuration parameter, Developer Options
IMMUTABLE, Function Volatility Categories
IMPORT FOREIGN SCHEMA, IMPORT FOREIGN SCHEMA
IN, Subquery Expressions, Row and Array Comparisons
INCLUDE
in index definitions, Index-Only Scans and Covering Indexes
include
in configuration file, Managing Configuration File Contents
include_dir
in configuration file, Managing Configuration File Contents
include_if_exists
in configuration file, Managing Configuration File Contents
index, Indexes, Multicolumn Indexes, Indexes and ORDER BY, Combining Multiple Indexes, Unique Indexes, Indexes on Expressions, Partial Indexes, Index-Only Scans and Covering Indexes, Index-Only Scans and Covering Indexes, Examining Index Usage, Preferred Index Types for Text Search, Preferred Index Types for Text Search, Locking and Indexes, Interfacing Extensions to Indexes, Building Indexes Concurrently, Rebuilding Indexes Concurrently, Operators and Functions
and ORDER BY, Indexes and ORDER BY
B-tree, Index Types
B-Tree, B-Tree Indexes
BRIN, Index Types, BRIN Indexes
building concurrently, Building Indexes Concurrently
combining multiple indexes, Combining Multiple Indexes
covering, Index-Only Scans and Covering Indexes
examining usage, Examining Index Usage
on expressions, Indexes on Expressions
for user-defined data type, Interfacing Extensions to Indexes
GIN, Index Types, Preferred Index Types for Text Search, GIN Indexes
text search, Preferred Index Types for Text Search
GiST, Index Types, Preferred Index Types for Text Search, GiST Indexes
text search, Preferred Index Types for Text Search
hash, Index Types
Hash, Hash Indexes
index-only scans, Index-Only Scans and Covering Indexes
locks, Locking and Indexes
multicolumn, Multicolumn Indexes
partial, Partial Indexes
rebuilding concurrently, Rebuilding Indexes Concurrently
SP-GiST, Index Types, SP-GiST Indexes
unique, Unique Indexes
Index Access Method, Index Access Method Interface Definition
index scan, Planner Method Configuration
index-only scan, Index-Only Scans and Covering Indexes
indexam
Index Access Method, Index Access Method Interface Definition
index_am_handler, Pseudo-Types
inet (data type), inet
inet_client_addr, System Information Functions and Operators
inet_client_port, System Information Functions and Operators
inet_merge, Network Address Functions and Operators
inet_same_family, Network Address Functions and Operators
inet_server_addr, System Information Functions and Operators
inet_server_port, System Information Functions and Operators
information schema, The Information Schema
inheritance, Inheritance, Inheritance
initcap, String Functions and Operators
initdb, Creating a Database Cluster, initdb
Initialization Fork, The Initialization Fork
input function, User-Defined Types
INSERT, Populating a Table With Rows, Inserting Data, Returning Data from Modified Rows, INSERT
RETURNING, Returning Data from Modified Rows
inserting, Inserting Data
installation, Installation from Source Code
on Windows, Installation from Source Code on Windows
instr function, Appendix
int2 (see smallint)
int4 (see integer)
int8 (see bigint)
intagg, intagg
intarray, intarray
integer, Numeric Constants, Integer Types
integer_datetimes configuration parameter, Preset Options
interfaces
externally maintained, Client Interfaces
internal, Pseudo-Types
INTERSECT, Combining Queries
interval, Date/Time Types, Interval Input
output format, Interval Output
(see also formatting)
IntervalStyle configuration parameter, Locale and Formatting
intset, intarray Functions and Operators
int_array_aggregate, Functions
int_array_enum, Functions
inverse distribution, Aggregate Functions
in_range support functions, B-Tree Support Functions
IS DISTINCT FROM, Comparison Functions and Operators, Row and Array Comparisons
IS DOCUMENT, IS DOCUMENT
IS FALSE, Comparison Functions and Operators
IS NOT DISTINCT FROM, Comparison Functions and Operators, Row and Array Comparisons
IS NOT DOCUMENT, IS NOT DOCUMENT
IS NOT FALSE, Comparison Functions and Operators
IS NOT NULL, Comparison Functions and Operators
IS NOT TRUE, Comparison Functions and Operators
IS NOT UNKNOWN, Comparison Functions and Operators
IS NULL, Comparison Functions and Operators, Platform and Client Compatibility
IS TRUE, Comparison Functions and Operators
IS UNKNOWN, Comparison Functions and Operators
isclosed, Geometric Functions and Operators
isempty, Range Functions and Operators
isfinite, Date/Time Functions and Operators
isn, isn
ISNULL, Comparison Functions and Operators
isn_weak, Functions and Operators
isopen, Geometric Functions and Operators
is_array_ref
in PL/Perl, Utility Functions in PL/Perl
is_valid, Functions and Operators

J

JIT, Just-in-Time Compilation (JIT)
jit configuration parameter, Other Planner Options
jit_above_cost configuration parameter, Planner Cost Constants
jit_debugging_support configuration parameter, Developer Options
jit_dump_bitcode configuration parameter, Developer Options
jit_expressions configuration parameter, Developer Options
jit_inline_above_cost configuration parameter, Planner Cost Constants
jit_optimize_above_cost configuration parameter, Planner Cost Constants
jit_profiling_support configuration parameter, Developer Options
jit_provider configuration parameter, Shared Library Preloading
jit_tuple_deforming configuration parameter, Developer Options
join, Joins Between Tables, Joined Tables, Controlling the Planner with Explicit JOIN Clauses
controlling the order, Controlling the Planner with Explicit JOIN Clauses
cross, Joined Tables
left, Joined Tables
natural, Joined Tables
outer, Joins Between Tables, Joined Tables
right, Joined Tables
self, Joins Between Tables
join_collapse_limit configuration parameter, Other Planner Options
JSON, JSON Types, JSON Functions and Operators
functions and operators, JSON Functions and Operators
JSONB, JSON Types
jsonb
containment, jsonb Containment and Existence
existence, jsonb Containment and Existence
indexes on, jsonb Indexing
jsonb_agg, Aggregate Functions
jsonb_array_elements, Processing and Creating JSON Data
jsonb_array_elements_text, Processing and Creating JSON Data
jsonb_array_length, Processing and Creating JSON Data
jsonb_build_array, Processing and Creating JSON Data
jsonb_build_object, Processing and Creating JSON Data
jsonb_each, Processing and Creating JSON Data
jsonb_each_text, Processing and Creating JSON Data
jsonb_extract_path, Processing and Creating JSON Data
jsonb_extract_path_text, Processing and Creating JSON Data
jsonb_insert, Processing and Creating JSON Data
jsonb_object, Processing and Creating JSON Data
jsonb_object_agg, Aggregate Functions
jsonb_object_keys, Processing and Creating JSON Data
jsonb_path_exists, Processing and Creating JSON Data
jsonb_path_exists_tz, Processing and Creating JSON Data
jsonb_path_match, Processing and Creating JSON Data
jsonb_path_match_tz, Processing and Creating JSON Data
jsonb_path_query, Processing and Creating JSON Data
jsonb_path_query_array, Processing and Creating JSON Data
jsonb_path_query_array_tz, Processing and Creating JSON Data
jsonb_path_query_first, Processing and Creating JSON Data
jsonb_path_query_first_tz, Processing and Creating JSON Data
jsonb_path_query_tz, Processing and Creating JSON Data
jsonb_populate_record, Processing and Creating JSON Data
jsonb_populate_recordset, Processing and Creating JSON Data
jsonb_pretty, Processing and Creating JSON Data
jsonb_set, Processing and Creating JSON Data
jsonb_set_lax, Processing and Creating JSON Data
jsonb_strip_nulls, Processing and Creating JSON Data
jsonb_to_record, Processing and Creating JSON Data
jsonb_to_recordset, Processing and Creating JSON Data
jsonb_to_tsvector, Text Search Functions and Operators
jsonb_typeof, Processing and Creating JSON Data
jsonpath, jsonpath Type
json_agg, Aggregate Functions
json_array_elements, Processing and Creating JSON Data
json_array_elements_text, Processing and Creating JSON Data
json_array_length, Processing and Creating JSON Data
json_build_array, Processing and Creating JSON Data
json_build_object, Processing and Creating JSON Data
json_each, Processing and Creating JSON Data
json_each_text, Processing and Creating JSON Data
json_extract_path, Processing and Creating JSON Data
json_extract_path_text, Processing and Creating JSON Data
json_object, Processing and Creating JSON Data
json_object_agg, Aggregate Functions
json_object_keys, Processing and Creating JSON Data
json_populate_record, Processing and Creating JSON Data
json_populate_recordset, Processing and Creating JSON Data
json_strip_nulls, Processing and Creating JSON Data
json_to_record, Processing and Creating JSON Data
json_to_recordset, Processing and Creating JSON Data
json_to_tsvector, Text Search Functions and Operators
json_typeof, Processing and Creating JSON Data
Julian date, Julian Dates
Just-In-Time compilation (see JIT)
justify_days, Date/Time Functions and Operators
justify_hours, Date/Time Functions and Operators
justify_interval, Date/Time Functions and Operators

K

key word, Identifiers and Key Words, SQL Key Words
list of, SQL Key Words
syntax of, Identifiers and Key Words
krb_caseins_users configuration parameter, Authentication
krb_server_keyfile configuration parameter, Authentication

L

label (see alias)
lag, Window Functions
language_handler, Pseudo-Types
large object, Large Objects
lastval, Sequence Manipulation Functions
last_value, Window Functions
LATERAL, LATERAL Subqueries
in the FROM clause, LATERAL Subqueries
latitude, Cube-Based Earth Distances
lca, Operators and Functions
lcm, Mathematical Functions and Operators
lc_collate configuration parameter, Preset Options
lc_ctype configuration parameter, Preset Options
lc_messages configuration parameter, Locale and Formatting
lc_monetary configuration parameter, Locale and Formatting
lc_numeric configuration parameter, Locale and Formatting
lc_time configuration parameter, Locale and Formatting
LDAP, PostgreSQL Features, LDAP Authentication
LDAP connection parameter lookup, LDAP Lookup of Connection Parameters
ldconfig, Shared Libraries
lead, Window Functions
LEAST, GREATEST and LEAST, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
left, String Functions and Operators
left join, Joined Tables
length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators, Geometric Functions and Operators, Text Search Functions and Operators
of a binary string (see binary strings, length)
of a character string (see character string, length)
length(tsvector), Manipulating Documents
levenshtein, Levenshtein
levenshtein_less_equal, Levenshtein
lex, Requirements
libedit, Requirements
libperl, Requirements
libpq, libpq — C Library, Retrieving Query Results Row-by-Row
single-row mode, Retrieving Query Results Row-by-Row
libpq-fe.h, libpq — C Library, Connection Status Functions
libpq-int.h, Connection Status Functions
libpython, Requirements
library finalization function, Dynamic Loading
library initialization function, Dynamic Loading
LIKE, LIKE
and locales, Behavior
LIKE_REGEX, Differences from XQuery (LIKE_REGEX), SQL/JSON Regular Expressions
in SQL/JSON, SQL/JSON Regular Expressions
LIMIT, LIMIT and OFFSET
line, Lines, Geometric Functions and Operators
line segment, Line Segments
linear regression, Aggregate Functions
Linux
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
LISTEN, LISTEN
listen_addresses configuration parameter, Connection Settings
llvm-config, PostgreSQL Features
ll_to_earth, Cube-Based Earth Distances
ln, Mathematical Functions and Operators
lo, lo
LOAD, LOAD
load balancing, High Availability, Load Balancing, and Replication
locale, Creating a Database Cluster, Locale Support
localtime, Date/Time Functions and Operators
localtimestamp, Date/Time Functions and Operators
local_preload_libraries configuration parameter, Shared Library Preloading
lock, Explicit Locking, Advisory Locks, Viewing Locks
advisory, Advisory Locks
monitoring, Viewing Locks
LOCK, Table-Level Locks, LOCK
lock_timeout configuration parameter, Statement Behavior
log, Mathematical Functions and Operators
log shipping, High Availability, Load Balancing, and Replication
log10, Mathematical Functions and Operators
Logging
current_logfiles file and the pg_current_logfile - function, System Information Functions and Operators
pg_current_logfile function, System Information Functions and Operators
logging_collector configuration parameter, Where to Log
Logical Decoding, Logical Decoding, Logical Decoding
logical_decoding_work_mem configuration parameter, Memory
login privilege, Role Attributes
log_autovacuum_min_duration
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
log_btree_build_stats configuration parameter, Developer Options
log_checkpoints configuration parameter, What to Log
log_connections configuration parameter, What to Log
log_destination configuration parameter, Where to Log
log_directory configuration parameter, Where to Log
log_disconnections configuration parameter, What to Log
log_duration configuration parameter, What to Log
log_error_verbosity configuration parameter, What to Log
log_executor_stats configuration parameter, Statistics Monitoring
log_filename configuration parameter, Where to Log
log_file_mode configuration parameter, Where to Log
log_hostname configuration parameter, What to Log
log_line_prefix configuration parameter, What to Log
log_lock_waits configuration parameter, What to Log
log_min_duration_sample configuration parameter, When to Log
log_min_duration_statement configuration parameter, When to Log
log_min_error_statement configuration parameter, When to Log
log_min_messages configuration parameter, When to Log
log_parameter_max_length configuration parameter, What to Log
log_parameter_max_length_on_error configuration parameter, What to Log
log_parser_stats configuration parameter, Statistics Monitoring
log_planner_stats configuration parameter, Statistics Monitoring
log_replication_commands configuration parameter, What to Log
log_rotation_age configuration parameter, Where to Log
log_rotation_size configuration parameter, Where to Log
log_statement configuration parameter, What to Log
log_statement_sample_rate configuration parameter, When to Log
log_statement_stats configuration parameter, Statistics Monitoring
log_temp_files configuration parameter, What to Log
log_timezone configuration parameter, What to Log
log_transaction_sample_rate configuration parameter, When to Log
log_truncate_on_rotation configuration parameter, Where to Log
longitude, Cube-Based Earth Distances
looks_like_number
in PL/Perl, Utility Functions in PL/Perl
loop, Simple Loops
in PL/pgSQL, Simple Loops
lower, String Functions and Operators, Range Functions and Operators
and locales, Behavior
lower_inc, Range Functions and Operators
lower_inf, Range Functions and Operators
lo_close, Closing a Large Object Descriptor
lo_compat_privileges configuration parameter, Previous PostgreSQL Versions
lo_creat, Creating a Large Object, Server-Side Functions
lo_create, Creating a Large Object
lo_export, Exporting a Large Object, Server-Side Functions
lo_from_bytea, Server-Side Functions
lo_get, Server-Side Functions
lo_import, Importing a Large Object, Server-Side Functions
lo_import_with_oid, Importing a Large Object
lo_lseek, Seeking in a Large Object
lo_lseek64, Seeking in a Large Object
lo_open, Opening an Existing Large Object
lo_put, Server-Side Functions
lo_read, Reading Data from a Large Object
lo_tell, Obtaining the Seek Position of a Large Object
lo_tell64, Obtaining the Seek Position of a Large Object
lo_truncate, Truncating a Large Object
lo_truncate64, Truncating a Large Object
lo_unlink, Removing a Large Object, Server-Side Functions
lo_write, Writing Data to a Large Object
lpad, String Functions and Operators
lseg, Line Segments, Geometric Functions and Operators
LSN, WAL Internals
ltree, ltree
ltree2text, Operators and Functions
ltrim, String Functions and Operators

M

MAC address (see macaddr)
MAC address (EUI-64 format) (see macaddr)
macaddr (data type), macaddr
macaddr8 (data type), macaddr8
macaddr8_set7bit, Network Address Functions and Operators
macOS, macOS
installation on, macOS
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
magic block, Dynamic Loading
maintenance, Routine Database Maintenance Tasks
maintenance_io_concurrency configuration parameter, Asynchronous Behavior
maintenance_work_mem configuration parameter, Memory
make, Requirements
makeaclitem, System Information Functions and Operators
make_date, Date/Time Functions and Operators
make_interval, Date/Time Functions and Operators
make_time, Date/Time Functions and Operators
make_timestamp, Date/Time Functions and Operators
make_timestamptz, Date/Time Functions and Operators
make_valid, Functions and Operators
MANPATH, Environment Variables
masklen, Network Address Functions and Operators
materialized view, Materialized Views
implementation through rules, Materialized Views
materialized views, pg_matviews
max, Aggregate Functions
max_connections configuration parameter, Connection Settings
max_files_per_process configuration parameter, Kernel Resource Usage
max_function_args configuration parameter, Preset Options
max_identifier_length configuration parameter, Preset Options
max_index_keys configuration parameter, Preset Options
max_locks_per_transaction configuration parameter, Lock Management
max_logical_replication_workers configuration parameter, Subscribers
max_parallel_maintenance_workers configuration parameter, Asynchronous Behavior
max_parallel_workers configuration parameter, Asynchronous Behavior
max_parallel_workers_per_gather configuration parameter, Asynchronous Behavior
max_pred_locks_per_page configuration parameter, Lock Management
max_pred_locks_per_relation configuration parameter, Lock Management
max_pred_locks_per_transaction configuration parameter, Lock Management
max_prepared_transactions configuration parameter, Memory
max_replication_slots configuration parameter, Sending Servers
max_slot_wal_keep_size configuration parameter, Sending Servers
max_stack_depth configuration parameter, Memory
max_standby_archive_delay configuration parameter, Standby Servers
max_standby_streaming_delay configuration parameter, Standby Servers
max_sync_workers_per_subscription configuration parameter, Subscribers
max_wal_senders configuration parameter, Sending Servers
max_wal_size configuration parameter, Checkpoints
max_worker_processes configuration parameter, Asynchronous Behavior
md5, String Functions and Operators, Binary String Functions and Operators
MD5, Password Authentication
median, Aggregate Expressions
(see also percentile)
memory context
in SPI, Memory Management
memory overcommit, Linux Memory Overcommit
metaphone, Metaphone
min, Aggregate Functions
MinGW, MinGW/Native Windows
installation on, MinGW/Native Windows
min_parallel_index_scan_size configuration parameter, Planner Cost Constants
min_parallel_table_scan_size configuration parameter, Planner Cost Constants
min_scale, Mathematical Functions and Operators
min_wal_size configuration parameter, Checkpoints
mod, Mathematical Functions and Operators
mode
statistical, Aggregate Functions
monitoring, Monitoring Database Activity
database activity, Monitoring Database Activity
MOVE, MOVE
moving-aggregate mode, Moving-Aggregate Mode
Multiversion Concurrency Control, Introduction
MultiXactId, Multixacts and Wraparound
MVCC, Introduction

N

name, Identifiers and Key Words
qualified, Creating a Schema
syntax of, Identifiers and Key Words
unqualified, The Schema Search Path
NaN (see not a number)
natural join, Joined Tables
negation, Logical Operators
NetBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
netmask, Network Address Functions and Operators
network, Network Address Types, Network Address Functions and Operators
data types, Network Address Types
nextval, Sequence Manipulation Functions
NFS, NFS
nlevel, Operators and Functions
non-durable, Non-Durable Settings
nonblocking connection, Database Connection Control Functions, Asynchronous Command Processing
nonrepeatable read, Transaction Isolation
normalize, String Functions and Operators
normalized, String Functions and Operators
normal_rand, normal_rand
NOT (operator), Logical Operators
not a number
double precision, Floating-Point Types
numeric (data type), Arbitrary Precision Numbers
NOT IN, Subquery Expressions, Row and Array Comparisons
not-null constraint, Not-Null Constraints
notation, Calling Functions
functions, Calling Functions
notice processing, Notice Processing
in libpq, Notice Processing
notice processor, Notice Processing
notice receiver, Notice Processing
NOTIFY, Asynchronous Notification, NOTIFY
in libpq, Asynchronous Notification
NOTNULL, Comparison Functions and Operators
now, Date/Time Functions and Operators
npoints, Geometric Functions and Operators
nth_value, Window Functions
ntile, Window Functions
null value
with check constraints, Check Constraints
comparing, Comparison Functions and Operators
default value, Default Values
in DISTINCT, DISTINCT
in libpq, Retrieving Query Result Information
in PL/Perl, PL/Perl Functions and Arguments
in PL/Python, Null, None
with unique constraints, Unique Constraints
NULLIF, NULLIF
number
constant, Numeric Constants
numeric, Numeric Constants
numeric (data type), Arbitrary Precision Numbers
numnode, Text Search Functions and Operators, Manipulating Queries
num_nonnulls, Comparison Functions and Operators
num_nulls, Comparison Functions and Operators
NVL, COALESCE

O

object identifier, Object Identifier Types
data type, Object Identifier Types
object-oriented database, Concepts
obj_description, System Information Functions and Operators
octet_length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
OFFSET, LIMIT and OFFSET
oid, Object Identifier Types
OID
in libpq, Retrieving Other Result Information
oid2name, oid2name
old_snapshot_threshold configuration parameter, Asynchronous Behavior
ON CONFLICT, INSERT
ONLY, The FROM Clause
OOM, Linux Memory Overcommit
OpenBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
OpenSSL, PostgreSQL Features
(see also SSL)
operator, Operators, Operator Precedence, Functions and Operators, Logical Operators, Operators, User-Defined Operators
invocation, Operator Invocations
logical, Logical Operators
precedence, Operator Precedence
syntax, Operators
type resolution in an invocation, Operators
user-defined, User-Defined Operators
operator class, Operator Classes and Operator Families, Index Methods and Operator Classes
operator family, Operator Classes and Operator Families, Operator Classes and Operator Families
operator_precedence_warning configuration parameter, Previous PostgreSQL Versions
optimization information, Function Optimization Information, Operator Optimization Information
for functions, Function Optimization Information
for operators, Operator Optimization Information
OR (operator), Logical Operators
Oracle, Porting from Oracle PL/SQL
porting from PL/SQL to PL/pgSQL, Porting from Oracle PL/SQL
ORDER BY, Querying a Table, Sorting Rows
and locales, Behavior
ordered-set aggregate, Aggregate Expressions
built-in, Aggregate Functions
ordering operator, System Dependencies on Operator Classes
ordinality, Set Returning Functions
outer join, Joined Tables
output function, User-Defined Types
OVER clause, Window Function Calls
overcommit, Linux Memory Overcommit
OVERLAPS, Date/Time Functions and Operators
overlay, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
overloading, Function Overloading
functions, Function Overloading
operators, User-Defined Operators
owner, Privileges

P

pageinspect, pageinspect
pages_per_range storage parameter, Index Storage Parameters
page_checksum, General Functions
page_header, General Functions
palloc, Writing Code
PAM, PostgreSQL Features, PAM Authentication
parallel query, Parallel Query
+ Z

A

abbrev, Network Address Functions and Operators
ABORT, ABORT
abs, Mathematical Functions and Operators
ACL, Privileges
aclcontains, System Information Functions and Operators
acldefault, System Information Functions and Operators
aclexplode, System Information Functions and Operators
aclitem, Privileges
aclitemeq, System Information Functions and Operators
acos, Mathematical Functions and Operators
acosd, Mathematical Functions and Operators
acosh, Mathematical Functions and Operators
administration tools
externally maintained, Administration Tools
adminpack, adminpack
advisory lock, Advisory Locks
age, Date/Time Functions and Operators
aggregate function, Aggregate Functions, Aggregate Expressions, Aggregate Functions, User-Defined Aggregates
built-in, Aggregate Functions
invocation, Aggregate Expressions
moving aggregate, Moving-Aggregate Mode
ordered set, Ordered-Set Aggregates
partial aggregation, Partial Aggregation
polymorphic, Polymorphic and Variadic Aggregates
support functions for, Support Functions for Aggregates
user-defined, User-Defined Aggregates
variadic, Polymorphic and Variadic Aggregates
AIX, AIX
installation on, AIX
IPC configuration, Shared Memory and Semaphores
akeys, hstore Operators and Functions
alias, Table and Column Aliases, Column Labels
for table name in query, Joins Between Tables
in the FROM clause, Table and Column Aliases
in the select list, Column Labels
ALL, Subquery Expressions, Row and Array Comparisons
allow_in_place_tablespaces configuration parameter, Developer Options
allow_system_table_mods configuration parameter, Developer Options
ALTER AGGREGATE, ALTER AGGREGATE
ALTER COLLATION, ALTER COLLATION
ALTER CONVERSION, ALTER CONVERSION
ALTER DATABASE, ALTER DATABASE
ALTER DEFAULT PRIVILEGES, ALTER DEFAULT PRIVILEGES
ALTER DOMAIN, ALTER DOMAIN
ALTER EVENT TRIGGER, ALTER EVENT TRIGGER
ALTER EXTENSION, ALTER EXTENSION
ALTER FOREIGN DATA WRAPPER, ALTER FOREIGN DATA WRAPPER
ALTER FOREIGN TABLE, ALTER FOREIGN TABLE
ALTER FUNCTION, ALTER FUNCTION
ALTER GROUP, ALTER GROUP
ALTER INDEX, ALTER INDEX
ALTER LANGUAGE, ALTER LANGUAGE
ALTER LARGE OBJECT, ALTER LARGE OBJECT
ALTER MATERIALIZED VIEW, ALTER MATERIALIZED VIEW
ALTER OPERATOR, ALTER OPERATOR
ALTER OPERATOR CLASS, ALTER OPERATOR CLASS
ALTER OPERATOR FAMILY, ALTER OPERATOR FAMILY
ALTER POLICY, ALTER POLICY
ALTER PROCEDURE, ALTER PROCEDURE
ALTER PUBLICATION, ALTER PUBLICATION
ALTER ROLE, Role Attributes, ALTER ROLE
ALTER ROUTINE, ALTER ROUTINE
ALTER RULE, ALTER RULE
ALTER SCHEMA, ALTER SCHEMA
ALTER SEQUENCE, ALTER SEQUENCE
ALTER SERVER, ALTER SERVER
ALTER STATISTICS, ALTER STATISTICS
ALTER SUBSCRIPTION, ALTER SUBSCRIPTION
ALTER SYSTEM, ALTER SYSTEM
ALTER TABLE, ALTER TABLE
ALTER TABLESPACE, ALTER TABLESPACE
ALTER TEXT SEARCH CONFIGURATION, ALTER TEXT SEARCH CONFIGURATION
ALTER TEXT SEARCH DICTIONARY, ALTER TEXT SEARCH DICTIONARY
ALTER TEXT SEARCH PARSER, ALTER TEXT SEARCH PARSER
ALTER TEXT SEARCH TEMPLATE, ALTER TEXT SEARCH TEMPLATE
ALTER TRIGGER, ALTER TRIGGER
ALTER TYPE, ALTER TYPE
ALTER USER, ALTER USER
ALTER USER MAPPING, ALTER USER MAPPING
ALTER VIEW, ALTER VIEW
amcheck, amcheck
ANALYZE, Updating Planner Statistics, ANALYZE
AND (operator), Logical Operators
anonymous code blocks, DO
any, Pseudo-Types
ANY, Aggregate Functions, Subquery Expressions, Row and Array Comparisons
anyarray, Pseudo-Types
anycompatible, Pseudo-Types
anycompatiblearray, Pseudo-Types
anycompatiblenonarray, Pseudo-Types
anycompatiblerange, Pseudo-Types
anyelement, Pseudo-Types
anyenum, Pseudo-Types
anynonarray, Pseudo-Types
anyrange, Pseudo-Types
applicable role, applicable_roles
application_name configuration parameter, What to Log
arbitrary precision numbers, Arbitrary Precision Numbers
archive_cleanup_command configuration parameter, Archive Recovery
archive_command configuration parameter, Archiving
archive_mode configuration parameter, Archiving
archive_timeout configuration parameter, Archiving
area, Geometric Functions and Operators
armor, armor(), dearmor()
array, Arrays
accessing, Accessing Arrays
constant, Array Value Input
constructor, Array Constructors
declaration, Declaration of Array Types
I/O, Array Input and Output Syntax
modifying, Modifying Arrays
of user-defined type, User-Defined Types
searching, Searching in Arrays
ARRAY, Array Constructors, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
array_agg, Aggregate Functions, Functions
array_append, Array Functions and Operators
array_cat, Array Functions and Operators
array_dims, Array Functions and Operators
array_fill, Array Functions and Operators
array_length, Array Functions and Operators
array_lower, Array Functions and Operators
array_ndims, Array Functions and Operators
array_nulls configuration parameter, Previous PostgreSQL Versions
array_position, Array Functions and Operators
array_positions, Array Functions and Operators
array_prepend, Array Functions and Operators
array_remove, Array Functions and Operators
array_replace, Array Functions and Operators
array_to_json, Processing and Creating JSON Data
array_to_string, Array Functions and Operators
array_to_tsvector, Text Search Functions and Operators
array_upper, Array Functions and Operators
ascii, String Functions and Operators
asin, Mathematical Functions and Operators
asind, Mathematical Functions and Operators
asinh, Mathematical Functions and Operators
ASSERT
in PL/pgSQL, Checking Assertions
assertions
in PL/pgSQL, Checking Assertions
asynchronous commit, Asynchronous Commit
AT TIME ZONE, AT TIME ZONE
atan, Mathematical Functions and Operators
atan2, Mathematical Functions and Operators
atan2d, Mathematical Functions and Operators
atand, Mathematical Functions and Operators
atanh, Mathematical Functions and Operators
authentication_timeout configuration parameter, Authentication
auth_delay, auth_delay
auth_delay.milliseconds configuration parameter, Configuration Parameters
auto-increment (see serial)
autocommit
bulk-loading data, Disable Autocommit
psql, Variables
autosummarize storage parameter, Index Storage Parameters
autovacuum
configuration parameters, Automatic Vacuuming
general information, The Autovacuum Daemon
autovacuum configuration parameter, Automatic Vacuuming
autovacuum_analyze_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_analyze_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_enabled storage parameter, Storage Parameters
autovacuum_freeze_max_age
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_freeze_min_age storage parameter, Storage Parameters
autovacuum_freeze_table_age storage parameter, Storage Parameters
autovacuum_max_workers configuration parameter, Automatic Vacuuming
autovacuum_multixact_freeze_max_age
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_multixact_freeze_min_age storage parameter, Storage Parameters
autovacuum_multixact_freeze_table_age storage parameter, Storage Parameters
autovacuum_naptime configuration parameter, Automatic Vacuuming
autovacuum_vacuum_cost_delay
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_cost_limit
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_insert_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_insert_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_scale_factor
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_vacuum_threshold
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
autovacuum_work_mem configuration parameter, Memory
auto_explain, auto_explain
auto_explain.log_analyze configuration parameter, Configuration Parameters
auto_explain.log_buffers configuration parameter, Configuration Parameters
auto_explain.log_format configuration parameter, Configuration Parameters
auto_explain.log_level configuration parameter, Configuration Parameters
auto_explain.log_min_duration configuration parameter, Configuration Parameters
auto_explain.log_nested_statements configuration parameter, Configuration Parameters
auto_explain.log_settings configuration parameter, Configuration Parameters
auto_explain.log_timing configuration parameter, Configuration Parameters
auto_explain.log_triggers configuration parameter, Configuration Parameters
auto_explain.log_verbose configuration parameter, Configuration Parameters
auto_explain.log_wal configuration parameter, Configuration Parameters
auto_explain.sample_rate configuration parameter, Configuration Parameters
avals, hstore Operators and Functions
average, Aggregate Functions
avg, Aggregate Functions

B

B-tree (see index)
backend_flush_after configuration parameter, Asynchronous Behavior
Background workers, Background Worker Processes
backslash escapes, String Constants with C-Style Escapes
backslash_quote configuration parameter, Previous PostgreSQL Versions
backtrace_functions configuration parameter, Developer Options
backup, Backup Control Functions, Backup and Restore
Backup Manifest, Backup Manifest Format
base type, The PostgreSQL Type System
base64 format, Binary String Functions and Operators
BASE_BACKUP, Streaming Replication Protocol
BEGIN, BEGIN
BETWEEN, Comparison Functions and Operators
BETWEEN SYMMETRIC, Comparison Functions and Operators
BGWORKER_BACKEND_​DATABASE_CONNECTION, Background Worker Processes
BGWORKER_SHMEM_ACCESS, Background Worker Processes
bgwriter_delay configuration parameter, Background Writer
bgwriter_flush_after configuration parameter, Background Writer
bgwriter_lru_maxpages configuration parameter, Background Writer
bgwriter_lru_multiplier configuration parameter, Background Writer
bigint, Numeric Constants, Integer Types
bigserial, Serial Types
binary data, Binary Data Types, Binary String Functions and Operators
functions, Binary String Functions and Operators
binary string
concatenation, Binary String Functions and Operators
converting to character string, Binary String Functions and Operators
length, Binary String Functions and Operators
bison, Requirements
bit string, Bit-String Constants, Bit String Types
constant, Bit-String Constants
data type, Bit String Types
length, Bit String Functions and Operators
bit strings, Bit String Functions and Operators
functions, Bit String Functions and Operators
bitmap scan, Combining Multiple Indexes, Planner Method Configuration
bit_and, Aggregate Functions
bit_length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
bit_or, Aggregate Functions
BLOB (see large object)
block_size configuration parameter, Preset Options
bloom, bloom
bonjour configuration parameter, Connection Settings
bonjour_name configuration parameter, Connection Settings
Boolean, Boolean Type
data type, Boolean Type
operators (see operators, logical)
bool_and, Aggregate Functions
bool_or, Aggregate Functions
booting
starting the server during, Starting the Database Server
bound_box, Geometric Functions and Operators
box, Geometric Functions and Operators
box (data type), Boxes
BRIN (see index)
brin_desummarize_range, Index Maintenance Functions
brin_metapage_info, BRIN Functions
brin_page_items, BRIN Functions
brin_page_type, BRIN Functions
brin_revmap_data, BRIN Functions
brin_summarize_new_values, Index Maintenance Functions
brin_summarize_range, Index Maintenance Functions
broadcast, Network Address Functions and Operators
BSD Authentication, BSD Authentication
btree_gin, btree_gin
btree_gist, btree_gist
btrim, String Functions and Operators, Binary String Functions and Operators
bt_index_check, Functions
bt_index_parent_check, Functions
bt_metap, B-Tree Functions
bt_page_items, B-Tree Functions
bt_page_stats, B-Tree Functions
buffering storage parameter, Index Storage Parameters
bytea, Binary Data Types
bytea_output configuration parameter, Statement Behavior

C

C, libpq — C Library, ECPG — Embedded SQL in C
C++, Using C++ for Extensibility
CALL, CALL
canceling, Canceling Queries in Progress
SQL command, Canceling Queries in Progress
cardinality, Array Functions and Operators
CASCADE, Dependency Tracking
with DROP, Dependency Tracking
foreign key action, Foreign Keys
Cascading Replication, High Availability, Load Balancing, and Replication
CASE, Conditional Expressions, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
case sensitivity
of SQL commands, Identifiers and Key Words
cast, CREATE CAST
I/O conversion, CREATE CAST
cbrt, Mathematical Functions and Operators
ceil, Mathematical Functions and Operators
ceiling, Mathematical Functions and Operators
center, Geometric Functions and Operators
Certificate, Certificate Authentication
chained transactions, Transaction Management, Parameters, Parameters
in PL/pgSQL, Transaction Management
char, Character Types
character, Character Types
character set, Locale and Formatting, Preset Options, Character Set Support
character string, String Constants, Character Types
concatenation, String Functions and Operators
constant, String Constants
converting to binary string, Binary String Functions and Operators
data types, Character Types
length, String Functions and Operators
character varying, Character Types
character_length, String Functions and Operators
char_length, String Functions and Operators
check constraint, Check Constraints
CHECK OPTION, CREATE VIEW
checkpoint, WAL Configuration
CHECKPOINT, CHECKPOINT
checkpoint_completion_target configuration parameter, Checkpoints
checkpoint_flush_after configuration parameter, Checkpoints
checkpoint_timeout configuration parameter, Checkpoints
checkpoint_warning configuration parameter, Checkpoints
check_function_bodies configuration parameter, Statement Behavior
chr, String Functions and Operators
cid, Object Identifier Types
cidr, cidr
circle, Circles, Geometric Functions and Operators
citext, citext
client authentication, Client Authentication
timeout during, Authentication
client_encoding configuration parameter, Locale and Formatting
client_min_messages configuration parameter, Statement Behavior
clock_timestamp, Date/Time Functions and Operators
CLOSE, CLOSE
cluster
of databases (see database cluster)
CLUSTER, CLUSTER
clusterdb, clusterdb
clustering, High Availability, Load Balancing, and Replication
cluster_name configuration parameter, Process Title
cmax, System Columns
cmin, System Columns
COALESCE, COALESCE
COLLATE, Collation Expressions
collation, Collation Support
in PL/pgSQL, Collation of PL/pgSQL Variables
in SQL functions, SQL Functions with Collations
COLLATION FOR, System Information Functions and Operators
color, Color Support
column, Concepts, Table Basics
adding, Adding a Column
removing, Removing a Column
renaming, Renaming a Column
system column, System Columns
column data type
changing, Changing a Column's Data Type
column reference, Column References
col_description, System Information Functions and Operators
comment, Comments
about database objects, System Information Functions and Operators
in SQL, Comments
COMMENT, COMMENT
COMMIT, COMMIT
COMMIT PREPARED, COMMIT PREPARED
commit_delay configuration parameter, Settings
commit_siblings configuration parameter, Settings
common table expression (see WITH)
comparison, Comparison Functions and Operators, Subquery Expressions
composite type, Row and Array Comparisons
operators, Comparison Functions and Operators
row constructor, Row and Array Comparisons
subquery result row, Subquery Expressions
compiling, Building libpq Programs
libpq applications, Building libpq Programs
composite type, Composite Types, The PostgreSQL Type System
comparison, Row and Array Comparisons
constant, Constructing Composite Values
constructor, Row Constructors
computed field, Using Composite Types in Queries
concat, String Functions and Operators
concat_ws, String Functions and Operators
concurrency, Concurrency Control
conditional expression, Conditional Expressions
configuration
of recovery
of a standby server, Archive Recovery
of the server, Server Configuration
of the server
functions, Configuration Settings Functions
configure, Installation Procedure
configure environment variables, configure Environment Variables
configure options, configure Options
config_file configuration parameter, File Locations
conjunction, Logical Operators
connectby, Functions Provided, connectby
connection service file, The Connection Service File
conninfo, Connection Strings
constant, Constants
constraint, Constraints
adding, Adding a Constraint
check, Check Constraints
exclusion, Exclusion Constraints
foreign key, Foreign Keys
name, Check Constraints
NOT NULL, Not-Null Constraints
primary key, Primary Keys
removing, Removing a Constraint
unique, Unique Constraints
constraint exclusion, Partitioning and Constraint Exclusion, Other Planner Options
constraint_exclusion configuration parameter, Other Planner Options
container type, The PostgreSQL Type System
CONTINUE
in PL/pgSQL, CONTINUE
continuous archiving, Backup and Restore
in standby, Continuous Archiving in Standby
control file, Extension Files
convert, Binary String Functions and Operators
convert_from, Binary String Functions and Operators
convert_to, Binary String Functions and Operators
COPY, Populating a Table With Rows, Functions Associated with the COPY Command, COPY
with libpq, Functions Associated with the COPY Command
corr, Aggregate Functions
correlation, Aggregate Functions
in the query planner, Extended Statistics
cos, Mathematical Functions and Operators
cosd, Mathematical Functions and Operators
cosh, Mathematical Functions and Operators
cot, Mathematical Functions and Operators
cotd, Mathematical Functions and Operators
count, Aggregate Functions
covariance
population, Aggregate Functions
sample, Aggregate Functions
covar_pop, Aggregate Functions
covar_samp, Aggregate Functions
covering index, Index-Only Scans and Covering Indexes
cpu_index_tuple_cost configuration parameter, Planner Cost Constants
cpu_operator_cost configuration parameter, Planner Cost Constants
cpu_tuple_cost configuration parameter, Planner Cost Constants
CREATE ACCESS METHOD, CREATE ACCESS METHOD
CREATE AGGREGATE, CREATE AGGREGATE
CREATE CAST, CREATE CAST
CREATE COLLATION, CREATE COLLATION
CREATE CONVERSION, CREATE CONVERSION
CREATE DATABASE, Creating a Database, CREATE DATABASE
CREATE DOMAIN, CREATE DOMAIN
CREATE EVENT TRIGGER, CREATE EVENT TRIGGER
CREATE EXTENSION, CREATE EXTENSION
CREATE FOREIGN DATA WRAPPER, CREATE FOREIGN DATA WRAPPER
CREATE FOREIGN TABLE, CREATE FOREIGN TABLE
CREATE FUNCTION, CREATE FUNCTION
CREATE GROUP, CREATE GROUP
CREATE INDEX, CREATE INDEX
CREATE LANGUAGE, CREATE LANGUAGE
CREATE MATERIALIZED VIEW, CREATE MATERIALIZED VIEW
CREATE OPERATOR, CREATE OPERATOR
CREATE OPERATOR CLASS, CREATE OPERATOR CLASS
CREATE OPERATOR FAMILY, CREATE OPERATOR FAMILY
CREATE POLICY, CREATE POLICY
CREATE PROCEDURE, CREATE PROCEDURE
CREATE PUBLICATION, CREATE PUBLICATION
CREATE ROLE, Database Roles, CREATE ROLE
CREATE RULE, CREATE RULE
CREATE SCHEMA, CREATE SCHEMA
CREATE SEQUENCE, CREATE SEQUENCE
CREATE SERVER, CREATE SERVER
CREATE STATISTICS, CREATE STATISTICS
CREATE SUBSCRIPTION, CREATE SUBSCRIPTION
CREATE TABLE, Creating a New Table, CREATE TABLE
CREATE TABLE AS, CREATE TABLE AS
CREATE TABLESPACE, Tablespaces, CREATE TABLESPACE
CREATE TEXT SEARCH CONFIGURATION, CREATE TEXT SEARCH CONFIGURATION
CREATE TEXT SEARCH DICTIONARY, CREATE TEXT SEARCH DICTIONARY
CREATE TEXT SEARCH PARSER, CREATE TEXT SEARCH PARSER
CREATE TEXT SEARCH TEMPLATE, CREATE TEXT SEARCH TEMPLATE
CREATE TRANSFORM, CREATE TRANSFORM
CREATE TRIGGER, CREATE TRIGGER
CREATE TYPE, CREATE TYPE
CREATE USER, CREATE USER
CREATE USER MAPPING, CREATE USER MAPPING
CREATE VIEW, CREATE VIEW
createdb, Creating a Database, Creating a Database, createdb
createuser, Database Roles, createuser
CREATE_REPLICATION_SLOT, Streaming Replication Protocol
cross compilation, Build Process Details
cross join, Joined Tables
crosstab, crosstab(text), crosstabN(text), crosstab(text, text)
crypt, crypt()
cstring, Pseudo-Types
CSV (Comma-Separated Values) format
in psql, Meta-Commands
ctid, System Columns
CTID, View Rules in Non-SELECT Statements
CUBE, GROUPING SETS, CUBE, and ROLLUP
cube (extension), cube
cume_dist, Window Functions
hypothetical, Aggregate Functions
current_catalog, System Information Functions and Operators
current_database, System Information Functions and Operators
current_date, Date/Time Functions and Operators
current_logfiles
and the log_destination configuration parameter, Where to Log
and the pg_current_logfile function, System Information Functions and Operators
current_query, System Information Functions and Operators
current_role, System Information Functions and Operators
current_schema, System Information Functions and Operators
current_schemas, System Information Functions and Operators
current_setting, Configuration Settings Functions
current_time, Date/Time Functions and Operators
current_timestamp, Date/Time Functions and Operators
current_user, System Information Functions and Operators
currval, Sequence Manipulation Functions
cursor, Cursors, CLOSE, DECLARE, EXPLAIN, FETCH, MOVE
CLOSE, CLOSE
DECLARE, DECLARE
FETCH, FETCH
in PL/pgSQL, Cursors
MOVE, MOVE
showing the query plan, EXPLAIN
cursor_tuple_fraction configuration parameter, Other Planner Options
custom scan provider, Writing a Custom Scan Provider
handler for, Writing a Custom Scan Provider
Cygwin, Cygwin
installation on, Cygwin

D

data area (see database cluster)
data partitioning, High Availability, Load Balancing, and Replication
data type, Data Types, Numeric Types, Enumerated Types, Domain Types, Type Conversion, The PostgreSQL Type System, The PostgreSQL Type System, The PostgreSQL Type System, Polymorphic Types, Base Types in C-Language Functions, User-Defined Types
base, The PostgreSQL Type System
category, Overview
composite, The PostgreSQL Type System
constant, Constants of Other Types
container, The PostgreSQL Type System
conversion, Type Conversion
domain, Domain Types
enumerated (enum), Enumerated Types
internal organization, Base Types in C-Language Functions
numeric, Numeric Types
polymorphic, Polymorphic Types
type cast, Type Casts
user-defined, User-Defined Types
database, Creating a Database, Managing Databases
creating, Creating a Database
privilege to create, Role Attributes
database activity, Monitoring Database Activity
monitoring, Monitoring Database Activity
database cluster, Concepts, Creating a Database Cluster
data_checksums configuration parameter, Preset Options
data_directory configuration parameter, File Locations
data_directory_mode configuration parameter, Preset Options
data_sync_retry configuration parameter, Error Handling
date, Date/Time Types, Dates
constants, Special Values
current, Current Date/Time
output format, Date/Time Output
(see also formatting)
DateStyle configuration parameter, Locale and Formatting
date_part, Date/Time Functions and Operators, EXTRACT, date_part
date_trunc, Date/Time Functions and Operators, date_trunc
dblink, dblink, dblink
dblink_build_sql_delete, dblink_build_sql_delete
dblink_build_sql_insert, dblink_build_sql_insert
dblink_build_sql_update, dblink_build_sql_update
dblink_cancel_query, dblink_cancel_query
dblink_close, dblink_close
dblink_connect, dblink_connect
dblink_connect_u, dblink_connect_u
dblink_disconnect, dblink_disconnect
dblink_error_message, dblink_error_message
dblink_exec, dblink_exec
dblink_fetch, dblink_fetch
dblink_get_connections, dblink_get_connections
dblink_get_notify, dblink_get_notify
dblink_get_pkey, dblink_get_pkey
dblink_get_result, dblink_get_result
dblink_is_busy, dblink_is_busy
dblink_open, dblink_open
dblink_send_query, dblink_send_query
db_user_namespace configuration parameter, Authentication
deadlock, Deadlocks
timeout during, Lock Management
deadlock_timeout configuration parameter, Lock Management
DEALLOCATE, DEALLOCATE
dearmor, armor(), dearmor()
debug_assertions configuration parameter, Preset Options
debug_deadlocks configuration parameter, Developer Options
debug_pretty_print configuration parameter, What to Log
debug_print_parse configuration parameter, What to Log
debug_print_plan configuration parameter, What to Log
debug_print_rewritten configuration parameter, What to Log
decimal (see numeric)
DECLARE, DECLARE
decode, Binary String Functions and Operators
decode_bytea
in PL/Perl, Utility Functions in PL/Perl
decrypt, Raw Encryption Functions
decrypt_iv, Raw Encryption Functions
deduplicate_items storage parameter, Index Storage Parameters
default value, Default Values
changing, Changing a Column's Default Value
default_statistics_target configuration parameter, Other Planner Options
default_tablespace configuration parameter, Statement Behavior
default_table_access_method configuration parameter, Statement Behavior
default_text_search_config configuration parameter, Locale and Formatting
default_transaction_deferrable configuration parameter, Statement Behavior
default_transaction_isolation configuration parameter, Statement Behavior
default_transaction_read_only configuration parameter, Statement Behavior
deferrable transaction, Statement Behavior
setting, SET TRANSACTION
setting default, Statement Behavior
defined, hstore Operators and Functions
degrees, Mathematical Functions and Operators
delay, Delaying Execution
DELETE, Deletions, Deleting Data, Returning Data from Modified Rows, DELETE
RETURNING, Returning Data from Modified Rows
delete, hstore Operators and Functions
deleting, Deleting Data
dense_rank, Window Functions
hypothetical, Aggregate Functions
diagonal, Geometric Functions and Operators
diameter, Geometric Functions and Operators
dict_int, dict_int
dict_xsyn, dict_xsyn
difference, Soundex
digest, digest()
dirty read, Transaction Isolation
DISCARD, DISCARD
disjunction, Logical Operators
disk drive, WAL Internals
disk space, Recovering Disk Space
disk usage, Determining Disk Usage
DISTINCT, Querying a Table, DISTINCT
div, Mathematical Functions and Operators
dmetaphone, Double Metaphone
dmetaphone_alt, Double Metaphone
DO, DO
document, What Is a Document?
text search, What Is a Document?
dollar quoting, Dollar-Quoted String Constants
domain, Domain Types
double precision, Floating-Point Types
DROP ACCESS METHOD, DROP ACCESS METHOD
DROP AGGREGATE, DROP AGGREGATE
DROP CAST, DROP CAST
DROP COLLATION, DROP COLLATION
DROP CONVERSION, DROP CONVERSION
DROP DATABASE, Destroying a Database, DROP DATABASE
DROP DOMAIN, DROP DOMAIN
DROP EVENT TRIGGER, DROP EVENT TRIGGER
DROP EXTENSION, DROP EXTENSION
DROP FOREIGN DATA WRAPPER, DROP FOREIGN DATA WRAPPER
DROP FOREIGN TABLE, DROP FOREIGN TABLE
DROP FUNCTION, DROP FUNCTION
DROP GROUP, DROP GROUP
DROP INDEX, DROP INDEX
DROP LANGUAGE, DROP LANGUAGE
DROP MATERIALIZED VIEW, DROP MATERIALIZED VIEW
DROP OPERATOR, DROP OPERATOR
DROP OPERATOR CLASS, DROP OPERATOR CLASS
DROP OPERATOR FAMILY, DROP OPERATOR FAMILY
DROP OWNED, DROP OWNED
DROP POLICY, DROP POLICY
DROP PROCEDURE, DROP PROCEDURE
DROP PUBLICATION, DROP PUBLICATION
DROP ROLE, Database Roles, DROP ROLE
DROP ROUTINE, DROP ROUTINE
DROP RULE, DROP RULE
DROP SCHEMA, DROP SCHEMA
DROP SEQUENCE, DROP SEQUENCE
DROP SERVER, DROP SERVER
DROP STATISTICS, DROP STATISTICS
DROP SUBSCRIPTION, DROP SUBSCRIPTION
DROP TABLE, Creating a New Table, DROP TABLE
DROP TABLESPACE, DROP TABLESPACE
DROP TEXT SEARCH CONFIGURATION, DROP TEXT SEARCH CONFIGURATION
DROP TEXT SEARCH DICTIONARY, DROP TEXT SEARCH DICTIONARY
DROP TEXT SEARCH PARSER, DROP TEXT SEARCH PARSER
DROP TEXT SEARCH TEMPLATE, DROP TEXT SEARCH TEMPLATE
DROP TRANSFORM, DROP TRANSFORM
DROP TRIGGER, DROP TRIGGER
DROP TYPE, DROP TYPE
DROP USER, DROP USER
DROP USER MAPPING, DROP USER MAPPING
DROP VIEW, DROP VIEW
dropdb, Destroying a Database, dropdb
dropuser, Database Roles, dropuser
DROP_REPLICATION_SLOT, Streaming Replication Protocol
DTD, Creating XML Values
DTrace, Developer Options, Dynamic Tracing
duplicate, Querying a Table
duplicates, DISTINCT
dynamic loading, Other Defaults, Dynamic Loading
dynamic_library_path, Dynamic Loading
dynamic_library_path configuration parameter, Other Defaults
dynamic_shared_memory_type configuration parameter, Memory

E

each, hstore Operators and Functions
earth, Cube-Based Earth Distances
earthdistance, earthdistance
earth_box, Cube-Based Earth Distances
earth_distance, Cube-Based Earth Distances
ECPG, ECPG — Embedded SQL in C
ecpg, ecpg
effective_cache_size configuration parameter, Planner Cost Constants
effective_io_concurrency configuration parameter, Asynchronous Behavior
elog, Reporting Errors Within the Server
in PL/Perl, Utility Functions in PL/Perl
in PL/Python, Utility Functions
in PL/Tcl, Database Access from PL/Tcl
embedded SQL, ECPG — Embedded SQL in C
in C, ECPG — Embedded SQL in C
enabled role, enabled_roles
enable_bitmapscan configuration parameter, Planner Method Configuration
enable_gathermerge configuration parameter, Planner Method Configuration
enable_hashagg configuration parameter, Planner Method Configuration
enable_hashjoin configuration parameter, Planner Method Configuration
enable_incremental_sort configuration parameter, Planner Method Configuration
enable_indexonlyscan configuration parameter, Planner Method Configuration
enable_indexscan configuration parameter, Planner Method Configuration
enable_material configuration parameter, Planner Method Configuration
enable_mergejoin configuration parameter, Planner Method Configuration
enable_nestloop configuration parameter, Planner Method Configuration
enable_parallel_append configuration parameter, Planner Method Configuration
enable_parallel_hash configuration parameter, Planner Method Configuration
enable_partitionwise_aggregate configuration parameter, Planner Method Configuration
enable_partitionwise_join configuration parameter, Planner Method Configuration
enable_partition_pruning configuration parameter, Planner Method Configuration
enable_seqscan configuration parameter, Planner Method Configuration
enable_sort configuration parameter, Planner Method Configuration
enable_tidscan configuration parameter, Planner Method Configuration
encode, Binary String Functions and Operators
encode_array_constructor
in PL/Perl, Utility Functions in PL/Perl
encode_array_literal
in PL/Perl, Utility Functions in PL/Perl
encode_bytea
in PL/Perl, Utility Functions in PL/Perl
encode_typed_literal
in PL/Perl, Utility Functions in PL/Perl
encrypt, Raw Encryption Functions
encryption, Encryption Options, pgcrypto
for specific columns, pgcrypto
encrypt_iv, Raw Encryption Functions
END, END
enumerated types, Enumerated Types
enum_first, Enum Support Functions
enum_last, Enum Support Functions
enum_range, Enum Support Functions
environment variable, Environment Variables
ephemeral named relation
registering with SPI, SPI_register_relation, SPI_register_trigger_data
unregistering from SPI, SPI_unregister_relation
ereport, Reporting Errors Within the Server
error codes, PostgreSQL Error Codes
libpq, Main Functions
list of, PostgreSQL Error Codes
error message, Connection Status Functions
escape format, Binary String Functions and Operators
escape string syntax, String Constants with C-Style Escapes
escape_string_warning configuration parameter, Previous PostgreSQL Versions
escaping strings, Escaping Strings for Inclusion in SQL Commands
in libpq, Escaping Strings for Inclusion in SQL Commands
event log, Registering Event Log on Windows
event log, Registering Event Log on Windows
event trigger, Event Triggers, Writing Event Trigger Functions in C
in C, Writing Event Trigger Functions in C
in PL/Tcl, Event Trigger Functions in PL/Tcl
event_source configuration parameter, Where to Log
event_trigger, Pseudo-Types
every, Aggregate Functions
EXCEPT, Combining Queries
exceptions
in PL/pgSQL, Trapping Errors
in PL/Tcl, Error Handling in PL/Tcl
exclusion constraint, Exclusion Constraints
EXECUTE, EXECUTE
exist, hstore Operators and Functions
EXISTS, Subquery Expressions
EXIT
in PL/pgSQL, EXIT
exit_on_error configuration parameter, Error Handling
exp, Mathematical Functions and Operators
EXPLAIN, Using EXPLAIN, EXPLAIN
expression, Value Expressions
order of evaluation, Expression Evaluation Rules
syntax, Value Expressions
extending SQL, Extending SQL
extension, Packaging Related Objects into an Extension
externally maintained, Extensions
external_pid_file configuration parameter, File Locations
extract, Date/Time Functions and Operators, EXTRACT, date_part
extra_float_digits configuration parameter, Locale and Formatting

F

factorial, Mathematical Functions and Operators
failover, High Availability, Load Balancing, and Replication
false, Boolean Type
family, Network Address Functions and Operators
fast path, The Fast-Path Interface
fastupdate storage parameter, Index Storage Parameters
fdw_handler, Pseudo-Types
FETCH, FETCH
field
computed, Using Composite Types in Queries
field selection, Field Selection
file system mount points, Use of Secondary File Systems
file_fdw, file_fdw
fillfactor storage parameter, Index Storage Parameters, Storage Parameters
FILTER, Aggregate Expressions
first_value, Window Functions
flex, Requirements
float4 (see real)
float8 (see double precision)
floating point, Floating-Point Types
floating-point
display, Locale and Formatting
floor, Mathematical Functions and Operators
force_parallel_mode configuration parameter, Other Planner Options
foreign data, Foreign Data
foreign data wrapper, Writing a Foreign Data Wrapper
handler for, Writing a Foreign Data Wrapper
foreign key, Foreign Keys, Foreign Keys
self-referential, Foreign Keys
foreign table, Foreign Data
format, String Functions and Operators, format
use in PL/pgSQL, Executing Dynamic Commands
formatting, Data Type Formatting Functions
format_type, System Information Functions and Operators
Free Space Map, Free Space Map
FreeBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
from_collapse_limit configuration parameter, Other Planner Options
FSM (see Free Space Map)
fsm_page_contents, General Functions
fsync configuration parameter, Settings
full text search, Text Search Types, Text Search Types, Full Text Search
data types, Text Search Types
functions and operators, Text Search Types
full_page_writes configuration parameter, Settings
function, Table Functions, Functions and Operators, Statistics Information Functions, Functions, Polymorphic Types, User-Defined Functions, Query Language (SQL) Functions, Internal Functions, C-Language Functions
default values for arguments, SQL Functions with Default Values for Arguments
in the FROM clause, Table Functions
internal, Internal Functions
invocation, Function Calls
mixed notation, Using Mixed Notation
named argument, Arguments for SQL Functions
named notation, Using Named Notation
output parameter, SQL Functions with Output Parameters
polymorphic, Polymorphic Types
positional notation, Using Positional Notation
RETURNS TABLE, SQL Functions Returning TABLE
statistics, Statistics Information Functions
type resolution in an invocation, Functions
user-defined, User-Defined Functions, Query Language (SQL) Functions, C-Language Functions
in C, C-Language Functions
in SQL, Query Language (SQL) Functions
variadic, SQL Functions with Variable Numbers of Arguments
with SETOF, SQL Functions Returning Sets
functional dependency, The GROUP BY and HAVING Clauses
fuzzystrmatch, fuzzystrmatch

G

gcd, Mathematical Functions and Operators
gc_to_sec, Cube-Based Earth Distances
generated column, Generated Columns, Parameters, Parameters
in + triggers, Overview of Trigger Behavior
generate_series, Set Returning Functions
generate_subscripts, Set Returning Functions
genetic query optimization, Genetic Query Optimizer
gen_random_bytes, Random-Data Functions
gen_random_uuid, UUID Functions, Random-Data Functions
gen_salt, gen_salt()
GEQO (see genetic query optimization)
geqo configuration parameter, Genetic Query Optimizer
geqo_effort configuration parameter, Genetic Query Optimizer
geqo_generations configuration parameter, Genetic Query Optimizer
geqo_pool_size configuration parameter, Genetic Query Optimizer
geqo_seed configuration parameter, Genetic Query Optimizer
geqo_selection_bias configuration parameter, Genetic Query Optimizer
geqo_threshold configuration parameter, Genetic Query Optimizer
get_bit, Binary String Functions and Operators, Bit String Functions and Operators
get_byte, Binary String Functions and Operators
get_current_ts_config, Text Search Functions and Operators
get_raw_page, General Functions
GIN (see index)
gin_clean_pending_list, Index Maintenance Functions
gin_fuzzy_search_limit configuration parameter, Other Defaults
gin_leafpage_items, GIN Functions
gin_metapage_info, GIN Functions
gin_page_opaque_info, GIN Functions
gin_pending_list_limit
configuration parameter, Statement Behavior
storage parameter, Index Storage Parameters
GiST (see index)
global data, Global Data in PL/Tcl
in PL/Python, Sharing Data
in PL/Tcl, Global Data in PL/Tcl
GRANT, Privileges, GRANT
GREATEST, GREATEST and LEAST, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
Gregorian calendar, History of Units
GROUP BY, Aggregate Functions, The GROUP BY and HAVING Clauses
grouping, The GROUP BY and HAVING Clauses
GROUPING, Aggregate Functions
GROUPING SETS, GROUPING SETS, CUBE, and ROLLUP
gssapi, Secure TCP/IP Connections with GSSAPI Encryption
GSSAPI, GSSAPI Authentication
with + libpq, Parameter Key Words
GUID, UUID Type

H

hash (see index)
hash_bitmap_info, Hash Functions
hash_mem_multiplier configuration parameter, Memory
hash_metapage_info, Hash Functions
hash_page_items, Hash Functions
hash_page_stats, Hash Functions
hash_page_type, Hash Functions
has_any_column_privilege, System Information Functions and Operators
has_column_privilege, System Information Functions and Operators
has_database_privilege, System Information Functions and Operators
has_foreign_data_wrapper_privilege, System Information Functions and Operators
has_function_privilege, System Information Functions and Operators
has_language_privilege, System Information Functions and Operators
has_schema_privilege, System Information Functions and Operators
has_sequence_privilege, System Information Functions and Operators
has_server_privilege, System Information Functions and Operators
has_tablespace_privilege, System Information Functions and Operators
has_table_privilege, System Information Functions and Operators
has_type_privilege, System Information Functions and Operators
HAVING, Aggregate Functions, The GROUP BY and HAVING Clauses
hba_file configuration parameter, File Locations
heap_page_items, Heap Functions
heap_page_item_attrs, Heap Functions
heap_tuple_infomask_flags, Heap Functions
height, Geometric Functions and Operators
hex format, Binary String Functions and Operators
hierarchical database, Concepts
high availability, High Availability, Load Balancing, and Replication
history, A Brief History of PostgreSQL
of PostgreSQL, A Brief History of PostgreSQL
hmac, hmac()
host, Network Address Functions and Operators
host + name, Parameter Key Words
hostmask, Network Address Functions and Operators
Hot Standby, High Availability, Load Balancing, and Replication
hot_standby configuration parameter, Standby Servers
hot_standby_feedback configuration parameter, Standby Servers
HP-UX
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
hstore, hstore, hstore Operators and Functions
hstore_to_array, hstore Operators and Functions
hstore_to_json, hstore Operators and Functions
hstore_to_jsonb, hstore Operators and Functions
hstore_to_jsonb_loose, hstore Operators and Functions
hstore_to_json_loose, hstore Operators and Functions
hstore_to_matrix, hstore Operators and Functions
huge_pages configuration parameter, Memory
hypothetical-set aggregate
built-in, Aggregate Functions

I

icount, intarray Functions and Operators
ICU, PostgreSQL Features, Managing Collations, Parameters
ident, Ident Authentication
identifier, Identifiers and Key Words
length, Identifiers and Key Words
syntax of, Identifiers and Key Words
IDENTIFY_SYSTEM, Streaming Replication Protocol
ident_file configuration parameter, File Locations
idle_in_transaction_session_timeout configuration parameter, Statement Behavior
idx, intarray Functions and Operators
IFNULL, COALESCE
ignore_checksum_failure configuration parameter, Developer Options
ignore_invalid_pages configuration parameter, Developer Options
ignore_system_indexes configuration parameter, Developer Options
IMMUTABLE, Function Volatility Categories
IMPORT FOREIGN SCHEMA, IMPORT FOREIGN SCHEMA
IN, Subquery Expressions, Row and Array Comparisons
INCLUDE
in index definitions, Index-Only Scans and Covering Indexes
include
in configuration file, Managing Configuration File Contents
include_dir
in configuration file, Managing Configuration File Contents
include_if_exists
in configuration file, Managing Configuration File Contents
index, Indexes, Multicolumn Indexes, Indexes and ORDER BY, Combining Multiple Indexes, Unique Indexes, Indexes on Expressions, Partial Indexes, Index-Only Scans and Covering Indexes, Index-Only Scans and Covering Indexes, Examining Index Usage, Preferred Index Types for Text Search, Preferred Index Types for Text Search, Locking and Indexes, Interfacing Extensions to Indexes, Building Indexes Concurrently, Rebuilding Indexes Concurrently, Operators and Functions
and ORDER BY, Indexes and ORDER BY
B-tree, Index Types
B-Tree, B-Tree Indexes
BRIN, Index Types, BRIN Indexes
building concurrently, Building Indexes Concurrently
combining multiple indexes, Combining Multiple Indexes
covering, Index-Only Scans and Covering Indexes
examining usage, Examining Index Usage
on expressions, Indexes on Expressions
for user-defined data type, Interfacing Extensions to Indexes
GIN, Index Types, Preferred Index Types for Text Search, GIN Indexes
text search, Preferred Index Types for Text Search
GiST, Index Types, Preferred Index Types for Text Search, GiST Indexes
text search, Preferred Index Types for Text Search
hash, Index Types
Hash, Hash Indexes
index-only scans, Index-Only Scans and Covering Indexes
locks, Locking and Indexes
multicolumn, Multicolumn Indexes
partial, Partial Indexes
rebuilding concurrently, Rebuilding Indexes Concurrently
SP-GiST, Index Types, SP-GiST Indexes
unique, Unique Indexes
Index Access Method, Index Access Method Interface Definition
index scan, Planner Method Configuration
index-only scan, Index-Only Scans and Covering Indexes
indexam
Index Access Method, Index Access Method Interface Definition
index_am_handler, Pseudo-Types
inet (data type), inet
inet_client_addr, System Information Functions and Operators
inet_client_port, System Information Functions and Operators
inet_merge, Network Address Functions and Operators
inet_same_family, Network Address Functions and Operators
inet_server_addr, System Information Functions and Operators
inet_server_port, System Information Functions and Operators
information schema, The Information Schema
inheritance, Inheritance, Inheritance
initcap, String Functions and Operators
initdb, Creating a Database Cluster, initdb
Initialization Fork, The Initialization Fork
input function, User-Defined Types
INSERT, Populating a Table With Rows, Inserting Data, Returning Data from Modified Rows, INSERT
RETURNING, Returning Data from Modified Rows
inserting, Inserting Data
installation, Installation from Source Code
on Windows, Installation from Source Code on Windows
instr function, Appendix
int2 (see smallint)
int4 (see integer)
int8 (see bigint)
intagg, intagg
intarray, intarray
integer, Numeric Constants, Integer Types
integer_datetimes configuration parameter, Preset Options
interfaces
externally maintained, Client Interfaces
internal, Pseudo-Types
INTERSECT, Combining Queries
interval, Date/Time Types, Interval Input
output format, Interval Output
(see also formatting)
IntervalStyle configuration parameter, Locale and Formatting
intset, intarray Functions and Operators
int_array_aggregate, Functions
int_array_enum, Functions
inverse distribution, Aggregate Functions
in_range support functions, B-Tree Support Functions
IS DISTINCT FROM, Comparison Functions and Operators, Row and Array Comparisons
IS DOCUMENT, IS DOCUMENT
IS FALSE, Comparison Functions and Operators
IS NOT DISTINCT FROM, Comparison Functions and Operators, Row and Array Comparisons
IS NOT DOCUMENT, IS NOT DOCUMENT
IS NOT FALSE, Comparison Functions and Operators
IS NOT NULL, Comparison Functions and Operators
IS NOT TRUE, Comparison Functions and Operators
IS NOT UNKNOWN, Comparison Functions and Operators
IS NULL, Comparison Functions and Operators, Platform and Client Compatibility
IS TRUE, Comparison Functions and Operators
IS UNKNOWN, Comparison Functions and Operators
isclosed, Geometric Functions and Operators
isempty, Range Functions and Operators
isfinite, Date/Time Functions and Operators
isn, isn
ISNULL, Comparison Functions and Operators
isn_weak, Functions and Operators
isopen, Geometric Functions and Operators
is_array_ref
in PL/Perl, Utility Functions in PL/Perl
is_valid, Functions and Operators

J

JIT, Just-in-Time Compilation (JIT)
jit configuration parameter, Other Planner Options
jit_above_cost configuration parameter, Planner Cost Constants
jit_debugging_support configuration parameter, Developer Options
jit_dump_bitcode configuration parameter, Developer Options
jit_expressions configuration parameter, Developer Options
jit_inline_above_cost configuration parameter, Planner Cost Constants
jit_optimize_above_cost configuration parameter, Planner Cost Constants
jit_profiling_support configuration parameter, Developer Options
jit_provider configuration parameter, Shared Library Preloading
jit_tuple_deforming configuration parameter, Developer Options
join, Joins Between Tables, Joined Tables, Controlling the Planner with Explicit JOIN Clauses
controlling the order, Controlling the Planner with Explicit JOIN Clauses
cross, Joined Tables
left, Joined Tables
natural, Joined Tables
outer, Joins Between Tables, Joined Tables
right, Joined Tables
self, Joins Between Tables
join_collapse_limit configuration parameter, Other Planner Options
JSON, JSON Types, JSON Functions and Operators
functions and operators, JSON Functions and Operators
JSONB, JSON Types
jsonb
containment, jsonb Containment and Existence
existence, jsonb Containment and Existence
indexes on, jsonb Indexing
jsonb_agg, Aggregate Functions
jsonb_array_elements, Processing and Creating JSON Data
jsonb_array_elements_text, Processing and Creating JSON Data
jsonb_array_length, Processing and Creating JSON Data
jsonb_build_array, Processing and Creating JSON Data
jsonb_build_object, Processing and Creating JSON Data
jsonb_each, Processing and Creating JSON Data
jsonb_each_text, Processing and Creating JSON Data
jsonb_extract_path, Processing and Creating JSON Data
jsonb_extract_path_text, Processing and Creating JSON Data
jsonb_insert, Processing and Creating JSON Data
jsonb_object, Processing and Creating JSON Data
jsonb_object_agg, Aggregate Functions
jsonb_object_keys, Processing and Creating JSON Data
jsonb_path_exists, Processing and Creating JSON Data
jsonb_path_exists_tz, Processing and Creating JSON Data
jsonb_path_match, Processing and Creating JSON Data
jsonb_path_match_tz, Processing and Creating JSON Data
jsonb_path_query, Processing and Creating JSON Data
jsonb_path_query_array, Processing and Creating JSON Data
jsonb_path_query_array_tz, Processing and Creating JSON Data
jsonb_path_query_first, Processing and Creating JSON Data
jsonb_path_query_first_tz, Processing and Creating JSON Data
jsonb_path_query_tz, Processing and Creating JSON Data
jsonb_populate_record, Processing and Creating JSON Data
jsonb_populate_recordset, Processing and Creating JSON Data
jsonb_pretty, Processing and Creating JSON Data
jsonb_set, Processing and Creating JSON Data
jsonb_set_lax, Processing and Creating JSON Data
jsonb_strip_nulls, Processing and Creating JSON Data
jsonb_to_record, Processing and Creating JSON Data
jsonb_to_recordset, Processing and Creating JSON Data
jsonb_to_tsvector, Text Search Functions and Operators
jsonb_typeof, Processing and Creating JSON Data
jsonpath, jsonpath Type
json_agg, Aggregate Functions
json_array_elements, Processing and Creating JSON Data
json_array_elements_text, Processing and Creating JSON Data
json_array_length, Processing and Creating JSON Data
json_build_array, Processing and Creating JSON Data
json_build_object, Processing and Creating JSON Data
json_each, Processing and Creating JSON Data
json_each_text, Processing and Creating JSON Data
json_extract_path, Processing and Creating JSON Data
json_extract_path_text, Processing and Creating JSON Data
json_object, Processing and Creating JSON Data
json_object_agg, Aggregate Functions
json_object_keys, Processing and Creating JSON Data
json_populate_record, Processing and Creating JSON Data
json_populate_recordset, Processing and Creating JSON Data
json_strip_nulls, Processing and Creating JSON Data
json_to_record, Processing and Creating JSON Data
json_to_recordset, Processing and Creating JSON Data
json_to_tsvector, Text Search Functions and Operators
json_typeof, Processing and Creating JSON Data
Julian date, Julian Dates
Just-In-Time compilation (see JIT)
justify_days, Date/Time Functions and Operators
justify_hours, Date/Time Functions and Operators
justify_interval, Date/Time Functions and Operators

K

key word, Identifiers and Key Words, SQL Key Words
list of, SQL Key Words
syntax of, Identifiers and Key Words
krb_caseins_users configuration parameter, Authentication
krb_server_keyfile configuration parameter, Authentication

L

label (see alias)
lag, Window Functions
language_handler, Pseudo-Types
large object, Large Objects
lastval, Sequence Manipulation Functions
last_value, Window Functions
LATERAL, LATERAL Subqueries
in the FROM clause, LATERAL Subqueries
latitude, Cube-Based Earth Distances
lca, Operators and Functions
lcm, Mathematical Functions and Operators
lc_collate configuration parameter, Preset Options
lc_ctype configuration parameter, Preset Options
lc_messages configuration parameter, Locale and Formatting
lc_monetary configuration parameter, Locale and Formatting
lc_numeric configuration parameter, Locale and Formatting
lc_time configuration parameter, Locale and Formatting
LDAP, PostgreSQL Features, LDAP Authentication
LDAP connection parameter lookup, LDAP Lookup of Connection Parameters
ldconfig, Shared Libraries
lead, Window Functions
LEAST, GREATEST and LEAST, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
left, String Functions and Operators
left join, Joined Tables
length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators, Geometric Functions and Operators, Text Search Functions and Operators
of a binary string (see binary strings, length)
of a character string (see character string, length)
length(tsvector), Manipulating Documents
levenshtein, Levenshtein
levenshtein_less_equal, Levenshtein
lex, Requirements
libedit, Requirements
libperl, Requirements
libpq, libpq — C Library, Retrieving Query Results Row-by-Row
single-row mode, Retrieving Query Results Row-by-Row
libpq-fe.h, libpq — C Library, Connection Status Functions
libpq-int.h, Connection Status Functions
libpython, Requirements
library finalization function, Dynamic Loading
library initialization function, Dynamic Loading
LIKE, LIKE
and locales, Behavior
LIKE_REGEX, Differences from XQuery (LIKE_REGEX), SQL/JSON Regular Expressions
in SQL/JSON, SQL/JSON Regular Expressions
LIMIT, LIMIT and OFFSET
line, Lines, Geometric Functions and Operators
line segment, Line Segments
linear regression, Aggregate Functions
Linux
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
LISTEN, LISTEN
listen_addresses configuration parameter, Connection Settings
llvm-config, PostgreSQL Features
ll_to_earth, Cube-Based Earth Distances
ln, Mathematical Functions and Operators
lo, lo
LOAD, LOAD
load balancing, High Availability, Load Balancing, and Replication
locale, Creating a Database Cluster, Locale Support
localtime, Date/Time Functions and Operators
localtimestamp, Date/Time Functions and Operators
local_preload_libraries configuration parameter, Shared Library Preloading
lock, Explicit Locking, Advisory Locks, Viewing Locks
advisory, Advisory Locks
monitoring, Viewing Locks
LOCK, Table-Level Locks, LOCK
lock_timeout configuration parameter, Statement Behavior
log, Mathematical Functions and Operators
log shipping, High Availability, Load Balancing, and Replication
log10, Mathematical Functions and Operators
Logging
current_logfiles file and the pg_current_logfile + function, System Information Functions and Operators
pg_current_logfile function, System Information Functions and Operators
logging_collector configuration parameter, Where to Log
Logical Decoding, Logical Decoding, Logical Decoding
logical_decoding_work_mem configuration parameter, Memory
login privilege, Role Attributes
log_autovacuum_min_duration
configuration parameter, Automatic Vacuuming
storage parameter, Storage Parameters
log_btree_build_stats configuration parameter, Developer Options
log_checkpoints configuration parameter, What to Log
log_connections configuration parameter, What to Log
log_destination configuration parameter, Where to Log
log_directory configuration parameter, Where to Log
log_disconnections configuration parameter, What to Log
log_duration configuration parameter, What to Log
log_error_verbosity configuration parameter, What to Log
log_executor_stats configuration parameter, Statistics Monitoring
log_filename configuration parameter, Where to Log
log_file_mode configuration parameter, Where to Log
log_hostname configuration parameter, What to Log
log_line_prefix configuration parameter, What to Log
log_lock_waits configuration parameter, What to Log
log_min_duration_sample configuration parameter, When to Log
log_min_duration_statement configuration parameter, When to Log
log_min_error_statement configuration parameter, When to Log
log_min_messages configuration parameter, When to Log
log_parameter_max_length configuration parameter, What to Log
log_parameter_max_length_on_error configuration parameter, What to Log
log_parser_stats configuration parameter, Statistics Monitoring
log_planner_stats configuration parameter, Statistics Monitoring
log_replication_commands configuration parameter, What to Log
log_rotation_age configuration parameter, Where to Log
log_rotation_size configuration parameter, Where to Log
log_statement configuration parameter, What to Log
log_statement_sample_rate configuration parameter, When to Log
log_statement_stats configuration parameter, Statistics Monitoring
log_temp_files configuration parameter, What to Log
log_timezone configuration parameter, What to Log
log_transaction_sample_rate configuration parameter, When to Log
log_truncate_on_rotation configuration parameter, Where to Log
longitude, Cube-Based Earth Distances
looks_like_number
in PL/Perl, Utility Functions in PL/Perl
loop, Simple Loops
in PL/pgSQL, Simple Loops
lower, String Functions and Operators, Range Functions and Operators
and locales, Behavior
lower_inc, Range Functions and Operators
lower_inf, Range Functions and Operators
lo_close, Closing a Large Object Descriptor
lo_compat_privileges configuration parameter, Previous PostgreSQL Versions
lo_creat, Creating a Large Object, Server-Side Functions
lo_create, Creating a Large Object
lo_export, Exporting a Large Object, Server-Side Functions
lo_from_bytea, Server-Side Functions
lo_get, Server-Side Functions
lo_import, Importing a Large Object, Server-Side Functions
lo_import_with_oid, Importing a Large Object
lo_lseek, Seeking in a Large Object
lo_lseek64, Seeking in a Large Object
lo_open, Opening an Existing Large Object
lo_put, Server-Side Functions
lo_read, Reading Data from a Large Object
lo_tell, Obtaining the Seek Position of a Large Object
lo_tell64, Obtaining the Seek Position of a Large Object
lo_truncate, Truncating a Large Object
lo_truncate64, Truncating a Large Object
lo_unlink, Removing a Large Object, Server-Side Functions
lo_write, Writing Data to a Large Object
lpad, String Functions and Operators
lseg, Line Segments, Geometric Functions and Operators
LSN, WAL Internals
ltree, ltree
ltree2text, Operators and Functions
ltrim, String Functions and Operators

M

MAC address (see macaddr)
MAC address (EUI-64 format) (see macaddr)
macaddr (data type), macaddr
macaddr8 (data type), macaddr8
macaddr8_set7bit, Network Address Functions and Operators
macOS, macOS
installation on, macOS
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
magic block, Dynamic Loading
maintenance, Routine Database Maintenance Tasks
maintenance_io_concurrency configuration parameter, Asynchronous Behavior
maintenance_work_mem configuration parameter, Memory
make, Requirements
makeaclitem, System Information Functions and Operators
make_date, Date/Time Functions and Operators
make_interval, Date/Time Functions and Operators
make_time, Date/Time Functions and Operators
make_timestamp, Date/Time Functions and Operators
make_timestamptz, Date/Time Functions and Operators
make_valid, Functions and Operators
MANPATH, Environment Variables
masklen, Network Address Functions and Operators
materialized view, Materialized Views
implementation through rules, Materialized Views
materialized views, pg_matviews
max, Aggregate Functions
max_connections configuration parameter, Connection Settings
max_files_per_process configuration parameter, Kernel Resource Usage
max_function_args configuration parameter, Preset Options
max_identifier_length configuration parameter, Preset Options
max_index_keys configuration parameter, Preset Options
max_locks_per_transaction configuration parameter, Lock Management
max_logical_replication_workers configuration parameter, Subscribers
max_parallel_maintenance_workers configuration parameter, Asynchronous Behavior
max_parallel_workers configuration parameter, Asynchronous Behavior
max_parallel_workers_per_gather configuration parameter, Asynchronous Behavior
max_pred_locks_per_page configuration parameter, Lock Management
max_pred_locks_per_relation configuration parameter, Lock Management
max_pred_locks_per_transaction configuration parameter, Lock Management
max_prepared_transactions configuration parameter, Memory
max_replication_slots configuration parameter, Sending Servers
max_slot_wal_keep_size configuration parameter, Sending Servers
max_stack_depth configuration parameter, Memory
max_standby_archive_delay configuration parameter, Standby Servers
max_standby_streaming_delay configuration parameter, Standby Servers
max_sync_workers_per_subscription configuration parameter, Subscribers
max_wal_senders configuration parameter, Sending Servers
max_wal_size configuration parameter, Checkpoints
max_worker_processes configuration parameter, Asynchronous Behavior
md5, String Functions and Operators, Binary String Functions and Operators
MD5, Password Authentication
median, Aggregate Expressions
(see also percentile)
memory context
in SPI, Memory Management
memory overcommit, Linux Memory Overcommit
metaphone, Metaphone
min, Aggregate Functions
MinGW, MinGW/Native Windows
installation on, MinGW/Native Windows
min_parallel_index_scan_size configuration parameter, Planner Cost Constants
min_parallel_table_scan_size configuration parameter, Planner Cost Constants
min_scale, Mathematical Functions and Operators
min_wal_size configuration parameter, Checkpoints
mod, Mathematical Functions and Operators
mode
statistical, Aggregate Functions
monitoring, Monitoring Database Activity
database activity, Monitoring Database Activity
MOVE, MOVE
moving-aggregate mode, Moving-Aggregate Mode
Multiversion Concurrency Control, Introduction
MultiXactId, Multixacts and Wraparound
MVCC, Introduction

N

name, Identifiers and Key Words
qualified, Creating a Schema
syntax of, Identifiers and Key Words
unqualified, The Schema Search Path
NaN (see not a number)
natural join, Joined Tables
negation, Logical Operators
NetBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
netmask, Network Address Functions and Operators
network, Network Address Types, Network Address Functions and Operators
data types, Network Address Types
nextval, Sequence Manipulation Functions
NFS, NFS
nlevel, Operators and Functions
non-durable, Non-Durable Settings
nonblocking connection, Database Connection Control Functions, Asynchronous Command Processing
nonrepeatable read, Transaction Isolation
normalize, String Functions and Operators
normalized, String Functions and Operators
normal_rand, normal_rand
NOT (operator), Logical Operators
not a number
double precision, Floating-Point Types
numeric (data type), Arbitrary Precision Numbers
NOT IN, Subquery Expressions, Row and Array Comparisons
not-null constraint, Not-Null Constraints
notation, Calling Functions
functions, Calling Functions
notice processing, Notice Processing
in libpq, Notice Processing
notice processor, Notice Processing
notice receiver, Notice Processing
NOTIFY, Asynchronous Notification, NOTIFY
in libpq, Asynchronous Notification
NOTNULL, Comparison Functions and Operators
now, Date/Time Functions and Operators
npoints, Geometric Functions and Operators
nth_value, Window Functions
ntile, Window Functions
null value
with check constraints, Check Constraints
comparing, Comparison Functions and Operators
default value, Default Values
in DISTINCT, DISTINCT
in libpq, Retrieving Query Result Information
in PL/Perl, PL/Perl Functions and Arguments
in PL/Python, Null, None
with unique constraints, Unique Constraints
NULLIF, NULLIF
number
constant, Numeric Constants
numeric, Numeric Constants
numeric (data type), Arbitrary Precision Numbers
numnode, Text Search Functions and Operators, Manipulating Queries
num_nonnulls, Comparison Functions and Operators
num_nulls, Comparison Functions and Operators
NVL, COALESCE

O

object identifier, Object Identifier Types
data type, Object Identifier Types
object-oriented database, Concepts
obj_description, System Information Functions and Operators
octet_length, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
OFFSET, LIMIT and OFFSET
oid, Object Identifier Types
OID
in libpq, Retrieving Other Result Information
oid2name, oid2name
old_snapshot_threshold configuration parameter, Asynchronous Behavior
ON CONFLICT, INSERT
ONLY, The FROM Clause
OOM, Linux Memory Overcommit
OpenBSD
IPC configuration, Shared Memory and Semaphores
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
OpenSSL, PostgreSQL Features
(see also SSL)
operator, Operators, Operator Precedence, Functions and Operators, Logical Operators, Operators, User-Defined Operators
invocation, Operator Invocations
logical, Logical Operators
precedence, Operator Precedence
syntax, Operators
type resolution in an invocation, Operators
user-defined, User-Defined Operators
operator class, Operator Classes and Operator Families, Index Methods and Operator Classes
operator family, Operator Classes and Operator Families, Operator Classes and Operator Families
operator_precedence_warning configuration parameter, Previous PostgreSQL Versions
optimization information, Function Optimization Information, Operator Optimization Information
for functions, Function Optimization Information
for operators, Operator Optimization Information
OR (operator), Logical Operators
Oracle, Porting from Oracle PL/SQL
porting from PL/SQL to PL/pgSQL, Porting from Oracle PL/SQL
ORDER BY, Querying a Table, Sorting Rows
and locales, Behavior
ordered-set aggregate, Aggregate Expressions
built-in, Aggregate Functions
ordering operator, System Dependencies on Operator Classes
ordinality, Set Returning Functions
outer join, Joined Tables
output function, User-Defined Types
OVER clause, Window Function Calls
overcommit, Linux Memory Overcommit
OVERLAPS, Date/Time Functions and Operators
overlay, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
overloading, Function Overloading
functions, Function Overloading
operators, User-Defined Operators
owner, Privileges

P

pageinspect, pageinspect
pages_per_range storage parameter, Index Storage Parameters
page_checksum, General Functions
page_header, General Functions
palloc, Writing Code
PAM, PostgreSQL Features, PAM Authentication
parallel query, Parallel Query
parallel_leader_participation configuration parameter - , Other Planner Options
parallel_setup_cost configuration parameter, Planner Cost Constants
parallel_tuple_cost configuration parameter, Planner Cost Constants
parallel_workers storage parameter, Storage Parameters
parameter
syntax, Positional Parameters
parenthesis, Value Expressions
parse_ident, String Functions and Operators
partition pruning, Partition Pruning
partitioned table, Table Partitioning
partitioning, Table Partitioning
password, Role Attributes
authentication, Password Authentication
of the superuser, Creating a Database Cluster
password file, The Password File
passwordcheck, passwordcheck
password_encryption configuration parameter, Authentication
path, Geometric Functions and Operators
for schemas, Statement Behavior
PATH, Environment Variables
path (data type), Paths
pattern matching, Pattern Matching
patterns
in psql and pg_dump, Patterns
pclose, Geometric Functions and Operators
peer, Peer Authentication
percentile
continuous, Aggregate Functions
discrete, Aggregate Functions
percent_rank, Window Functions
hypothetical, Aggregate Functions
performance, Performance Tips
perl, Requirements
Perl, PL/Perl — Perl Procedural Language
permission (see privilege)
pfree, Writing Code
PGAPPNAME, Environment Variables
pgbench, pgbench
PGcancel, Canceling Queries in Progress
PGCHANNELBINDING, Environment Variables
PGCLIENTENCODING, Environment Variables
PGconn, Database Connection Control Functions
PGCONNECT_TIMEOUT, Environment Variables
pgcrypto, pgcrypto
PGDATA, Creating a Database Cluster
PGDATABASE, Environment Variables
PGDATESTYLE, Environment Variables
PGEventProc, Event Callback Procedure
PGGEQO, Environment Variables
PGGSSENCMODE, Environment Variables
PGGSSLIB, Environment Variables
PGHOST, Environment Variables
PGHOSTADDR, Environment Variables
PGKRBSRVNAME, Environment Variables
PGLOCALEDIR, Environment Variables
PGOPTIONS, Environment Variables
PGPASSFILE, Environment Variables
PGPASSWORD, Environment Variables
PGPORT, Environment Variables
pgp_armor_headers, pgp_armor_headers
pgp_key_id, pgp_key_id()
pgp_pub_decrypt, pgp_pub_decrypt()
pgp_pub_decrypt_bytea, pgp_pub_decrypt()
pgp_pub_encrypt, pgp_pub_encrypt()
pgp_pub_encrypt_bytea, pgp_pub_encrypt()
pgp_sym_decrypt, pgp_sym_decrypt()
pgp_sym_decrypt_bytea, pgp_sym_decrypt()
pgp_sym_encrypt, pgp_sym_encrypt()
pgp_sym_encrypt_bytea, pgp_sym_encrypt()
PGREQUIREPEER, Environment Variables
PGREQUIRESSL, Environment Variables
PGresult, Main Functions
pgrowlocks, pgrowlocks, Overview
PGSERVICE, Environment Variables
PGSERVICEFILE, Environment Variables
PGSSLCERT, Environment Variables
PGSSLCOMPRESSION, Environment Variables
PGSSLCRL, Environment Variables
PGSSLKEY, Environment Variables
PGSSLMAXPROTOCOLVERSION, Environment Variables
PGSSLMINPROTOCOLVERSION, Environment Variables
PGSSLMODE, Environment Variables
PGSSLROOTCERT, Environment Variables
pgstatginindex, Functions
pgstathashindex, Functions
pgstatindex, Functions
pgstattuple, pgstattuple, Functions
pgstattuple_approx, Functions
PGSYSCONFDIR, Environment Variables
PGTARGETSESSIONATTRS, Environment Variables
PGTZ, Environment Variables
PGUSER, Environment Variables
pgxs, Extension Building Infrastructure
pg_advisory_lock, Advisory Lock Functions
pg_advisory_lock_shared, Advisory Lock Functions
pg_advisory_unlock, Advisory Lock Functions
pg_advisory_unlock_all, Advisory Lock Functions
pg_advisory_unlock_shared, Advisory Lock Functions
pg_advisory_xact_lock, Advisory Lock Functions
pg_advisory_xact_lock_shared, Advisory Lock Functions
pg_aggregate, pg_aggregate
pg_am, pg_am
pg_amop, pg_amop
pg_amproc, pg_amproc
pg_archivecleanup, pg_archivecleanup
pg_attrdef, pg_attrdef
pg_attribute, pg_attribute
pg_authid, pg_authid
pg_auth_members, pg_auth_members
pg_available_extensions, pg_available_extensions
pg_available_extension_versions, pg_available_extension_versions
pg_backend_pid, System Information Functions and Operators
pg_backup_start_time, Backup Control Functions
pg_basebackup, pg_basebackup
pg_blocking_pids, System Information Functions and Operators
pg_buffercache, pg_buffercache
pg_buffercache_pages, pg_buffercache
pg_cancel_backend, Server Signaling Functions
pg_cast, pg_cast
pg_checksums, pg_checksums
pg_class, pg_class
pg_client_encoding, String Functions and Operators
pg_collation, pg_collation
pg_collation_actual_version, Database Object Management Functions
pg_collation_is_visible, System Information Functions and Operators
PG_COLOR, When Color is Used
PG_COLORS, Configuring the Colors
pg_column_size, Database Object Management Functions
pg_config, pg_config, pg_config
with - ecpg, Processing Embedded SQL Programs
with libpq, Building libpq Programs
with user-defined C functions, Writing Code
pg_conf_load_time, System Information Functions and Operators
pg_constraint, pg_constraint
pg_controldata, pg_controldata
pg_control_checkpoint, System Information Functions and Operators
pg_control_init, System Information Functions and Operators
pg_control_recovery, System Information Functions and Operators
pg_control_system, System Information Functions and Operators
pg_conversion, pg_conversion
pg_conversion_is_visible, System Information Functions and Operators
pg_copy_logical_replication_slot, Replication Management Functions
pg_copy_physical_replication_slot, Replication Management Functions
pg_create_logical_replication_slot, Replication Management Functions
pg_create_physical_replication_slot, Replication Management Functions
pg_create_restore_point, Backup Control Functions
pg_ctl, Creating a Database Cluster, Starting the Database Server, pg_ctl
pg_current_logfile, System Information Functions and Operators
pg_current_snapshot, System Information Functions and Operators
pg_current_wal_flush_lsn, Backup Control Functions
pg_current_wal_insert_lsn, Backup Control Functions
pg_current_wal_lsn, Backup Control Functions
pg_current_xact_id, System Information Functions and Operators
pg_current_xact_id_if_assigned, System Information Functions and Operators
pg_cursors, pg_cursors
pg_database, Template Databases, pg_database
pg_database_size, Database Object Management Functions
pg_db_role_setting, pg_db_role_setting
pg_ddl_command, Pseudo-Types
pg_default_acl, pg_default_acl
pg_depend, pg_depend
pg_describe_object, System Information Functions and Operators
pg_description, pg_description
pg_drop_replication_slot, Replication Management Functions
pg_dump, pg_dump
pg_dumpall, pg_dumpall
use during upgrade, Upgrading Data via pg_dumpall
pg_enum, pg_enum
pg_event_trigger, pg_event_trigger
pg_event_trigger_ddl_commands, Capturing Changes at Command End
pg_event_trigger_dropped_objects, Processing Objects Dropped by a DDL Command
pg_event_trigger_table_rewrite_oid, Handling a Table Rewrite Event
pg_event_trigger_table_rewrite_reason, Handling a Table Rewrite Event
pg_export_snapshot, Snapshot Synchronization Functions
pg_extension, pg_extension
pg_extension_config_dump, Extension Configuration Tables
pg_filenode_relation, Database Object Management Functions
pg_file_rename, adminpack
pg_file_settings, pg_file_settings
pg_file_sync, adminpack
pg_file_unlink, adminpack
pg_file_write, adminpack
pg_foreign_data_wrapper, pg_foreign_data_wrapper
pg_foreign_server, pg_foreign_server
pg_foreign_table, pg_foreign_table
pg_freespace, Functions
pg_freespacemap, pg_freespacemap
pg_function_is_visible, System Information Functions and Operators
pg_get_constraintdef, System Information Functions and Operators
pg_get_expr, System Information Functions and Operators
pg_get_functiondef, System Information Functions and Operators
pg_get_function_arguments, System Information Functions and Operators
pg_get_function_identity_arguments, System Information Functions and Operators
pg_get_function_result, System Information Functions and Operators
pg_get_indexdef, System Information Functions and Operators
pg_get_keywords, System Information Functions and Operators
pg_get_object_address, System Information Functions and Operators
pg_get_ruledef, System Information Functions and Operators
pg_get_serial_sequence, System Information Functions and Operators
pg_get_statisticsobjdef, System Information Functions and Operators
pg_get_triggerdef, System Information Functions and Operators
pg_get_userbyid, System Information Functions and Operators
pg_get_viewdef, System Information Functions and Operators
pg_group, pg_group
pg_has_role, System Information Functions and Operators
pg_hba.conf, The pg_hba.conf File
pg_hba_file_rules, pg_hba_file_rules
pg_ident.conf, User Name Maps
pg_identify_object, System Information Functions and Operators
pg_identify_object_as_address, System Information Functions and Operators
pg_import_system_collations, Database Object Management Functions
pg_index, pg_index
pg_indexam_has_property, System Information Functions and Operators
pg_indexes, pg_indexes
pg_indexes_size, Database Object Management Functions
pg_index_column_has_property, System Information Functions and Operators
pg_index_has_property, System Information Functions and Operators
pg_inherits, pg_inherits
pg_init_privs, pg_init_privs
pg_isready, pg_isready
pg_is_in_backup, Backup Control Functions
pg_is_in_recovery, Recovery Control Functions
pg_is_other_temp_schema, System Information Functions and Operators
pg_is_wal_replay_paused, Recovery Control Functions
pg_jit_available, System Information Functions and Operators
pg_language, pg_language
pg_largeobject, pg_largeobject
pg_largeobject_metadata, pg_largeobject_metadata
pg_last_committed_xact, System Information Functions and Operators
pg_last_wal_receive_lsn, Recovery Control Functions
pg_last_wal_replay_lsn, Recovery Control Functions
pg_last_xact_replay_timestamp, Recovery Control Functions
pg_listening_channels, System Information Functions and Operators
pg_locks, pg_locks
pg_logdir_ls, adminpack
pg_logical_emit_message, Replication Management Functions
pg_logical_slot_get_binary_changes, Replication Management Functions
pg_logical_slot_get_changes, Replication Management Functions
pg_logical_slot_peek_binary_changes, Replication Management Functions
pg_logical_slot_peek_changes, Replication Management Functions
pg_lsn, pg_lsn Type
pg_ls_archive_statusdir, Generic File Access Functions
pg_ls_dir, Generic File Access Functions
pg_ls_logdir, Generic File Access Functions
pg_ls_tmpdir, Generic File Access Functions
pg_ls_waldir, Generic File Access Functions
pg_matviews, pg_matviews
pg_mcv_list_items, Inspecting MCV Lists
pg_my_temp_schema, System Information Functions and Operators
pg_namespace, pg_namespace
pg_notification_queue_usage, System Information Functions and Operators
pg_notify, pg_notify
pg_opclass, pg_opclass
pg_opclass_is_visible, System Information Functions and Operators
pg_operator, pg_operator
pg_operator_is_visible, System Information Functions and Operators
pg_opfamily, pg_opfamily
pg_opfamily_is_visible, System Information Functions and Operators
pg_options_to_table, System Information Functions and Operators
pg_partitioned_table, pg_partitioned_table
pg_partition_ancestors, Database Object Management Functions
pg_partition_root, Database Object Management Functions
pg_partition_tree, Database Object Management Functions
pg_policies, pg_policies
pg_policy, pg_policy
pg_postmaster_start_time, System Information Functions and Operators
pg_prepared_statements, pg_prepared_statements
pg_prepared_xacts, pg_prepared_xacts
pg_prewarm, pg_prewarm
pg_prewarm.autoprewarm configuration parameter, Configuration Parameters
pg_prewarm.autoprewarm_interval configuration parameter, Configuration Parameters
pg_proc, pg_proc
pg_promote, Recovery Control Functions
pg_publication, pg_publication
pg_publication_rel, pg_publication_rel
pg_publication_tables, pg_publication_tables
pg_range, pg_range
pg_read_binary_file, Generic File Access Functions
pg_read_file, Generic File Access Functions
pg_receivewal, pg_receivewal
pg_receivexlog, pg_receivexlog renamed to pg_receivewal (see pg_receivewal)
pg_recvlogical, pg_recvlogical
pg_relation_filenode, Database Object Management Functions
pg_relation_filepath, Database Object Management Functions
pg_relation_size, Database Object Management Functions
pg_reload_conf, Server Signaling Functions
pg_relpages, Functions
pg_replication_origin, pg_replication_origin
pg_replication_origin_advance, Replication Management Functions
pg_replication_origin_create, Replication Management Functions
pg_replication_origin_drop, Replication Management Functions
pg_replication_origin_oid, Replication Management Functions
pg_replication_origin_progress, Replication Management Functions
pg_replication_origin_session_is_setup, Replication Management Functions
pg_replication_origin_session_progress, Replication Management Functions
pg_replication_origin_session_reset, Replication Management Functions
pg_replication_origin_session_setup, Replication Management Functions
pg_replication_origin_status, pg_replication_origin_status
pg_replication_origin_xact_reset, Replication Management Functions
pg_replication_origin_xact_setup, Replication Management Functions
pg_replication_slots, pg_replication_slots
pg_replication_slot_advance, Replication Management Functions
pg_resetwal, pg_resetwal
pg_resetxlog, pg_resetxlog renamed to pg_resetwal (see pg_resetwal)
pg_restore, pg_restore
pg_rewind, pg_rewind
pg_rewrite, pg_rewrite
pg_roles, pg_roles
pg_rotate_logfile, Server Signaling Functions
pg_rules, pg_rules
pg_safe_snapshot_blocking_pids, System Information Functions and Operators
pg_seclabel, pg_seclabel
pg_seclabels, pg_seclabels
pg_sequence, pg_sequence
pg_sequences, pg_sequences
pg_service.conf, The Connection Service File
pg_settings, pg_settings
pg_shadow, pg_shadow
pg_shdepend, pg_shdepend
pg_shdescription, pg_shdescription
pg_shmem_allocations, pg_shmem_allocations
pg_shseclabel, pg_shseclabel
pg_size_bytes, Database Object Management Functions
pg_size_pretty, Database Object Management Functions
pg_sleep, Delaying Execution
pg_sleep_for, Delaying Execution
pg_sleep_until, Delaying Execution
pg_snapshot_xip, System Information Functions and Operators
pg_snapshot_xmax, System Information Functions and Operators
pg_snapshot_xmin, System Information Functions and Operators
pg_standby, pg_standby
pg_start_backup, Backup Control Functions
pg_statio_all_indexes, Viewing Statistics, pg_statio_all_indexes
pg_statio_all_sequences, Viewing Statistics, pg_statio_all_sequences
pg_statio_all_tables, Viewing Statistics, pg_statio_all_tables
pg_statio_sys_indexes, Viewing Statistics
pg_statio_sys_sequences, Viewing Statistics
pg_statio_sys_tables, Viewing Statistics
pg_statio_user_indexes, Viewing Statistics
pg_statio_user_sequences, Viewing Statistics
pg_statio_user_tables, Viewing Statistics
pg_statistic, Single-Column Statistics, pg_statistic
pg_statistics_obj_is_visible, System Information Functions and Operators
pg_statistic_ext, Extended Statistics, pg_statistic_ext
pg_statistic_ext_data, Extended Statistics, pg_statistic_ext
pg_stats, Single-Column Statistics, pg_stats
pg_stats_ext, pg_stats_ext
pg_stat_activity, Viewing Statistics, pg_stat_activity
pg_stat_all_indexes, Viewing Statistics, pg_stat_all_indexes
pg_stat_all_tables, Viewing Statistics, pg_stat_all_tables
pg_stat_archiver, Viewing Statistics, pg_stat_archiver
pg_stat_bgwriter, Viewing Statistics, pg_stat_bgwriter
pg_stat_clear_snapshot, Statistics Functions
pg_stat_database, Viewing Statistics, pg_stat_database
pg_stat_database_conflicts, Viewing Statistics, pg_stat_database_conflicts
pg_stat_file, Generic File Access Functions
pg_stat_get_activity, Statistics Functions
pg_stat_get_backend_activity, Statistics Functions
pg_stat_get_backend_activity_start, Statistics Functions
pg_stat_get_backend_client_addr, Statistics Functions
pg_stat_get_backend_client_port, Statistics Functions
pg_stat_get_backend_dbid, Statistics Functions
pg_stat_get_backend_idset, Statistics Functions
pg_stat_get_backend_pid, Statistics Functions
pg_stat_get_backend_start, Statistics Functions
pg_stat_get_backend_userid, Statistics Functions
pg_stat_get_backend_wait_event, Statistics Functions
pg_stat_get_backend_wait_event_type, Statistics Functions
pg_stat_get_backend_xact_start, Statistics Functions
pg_stat_get_snapshot_timestamp, Statistics Functions
pg_stat_get_xact_blocks_fetched, Statistics Functions
pg_stat_get_xact_blocks_hit, Statistics Functions
pg_stat_gssapi, Viewing Statistics, pg_stat_gssapi
pg_stat_progress_analyze, Viewing Statistics
pg_stat_progress_basebackup, Viewing Statistics
pg_stat_progress_cluster, Viewing Statistics
pg_stat_progress_create_index, Viewing Statistics
pg_stat_progress_vacuum, Viewing Statistics
pg_stat_replication, Viewing Statistics, pg_stat_replication
pg_stat_reset, Statistics Functions
pg_stat_reset_shared, Statistics Functions
pg_stat_reset_single_function_counters, Statistics Functions
pg_stat_reset_single_table_counters, Statistics Functions
pg_stat_reset_slru, Statistics Functions
pg_stat_slru, Viewing Statistics, pg_stat_slru
pg_stat_ssl, Viewing Statistics, pg_stat_ssl
pg_stat_statements, pg_stat_statements
function, Functions
pg_stat_statements_reset, Functions
pg_stat_subscription, Viewing Statistics, pg_stat_subscription
pg_stat_sys_indexes, Viewing Statistics
pg_stat_sys_tables, Viewing Statistics
pg_stat_user_functions, Viewing Statistics, pg_stat_user_functions
pg_stat_user_indexes, Viewing Statistics
pg_stat_user_tables, Viewing Statistics
pg_stat_wal_receiver, Viewing Statistics, pg_stat_wal_receiver
pg_stat_xact_all_tables, Viewing Statistics
pg_stat_xact_sys_tables, Viewing Statistics
pg_stat_xact_user_functions, Viewing Statistics
pg_stat_xact_user_tables, Viewing Statistics
pg_stop_backup, Backup Control Functions
pg_subscription, pg_subscription
pg_subscription_rel, pg_subscription_rel
pg_switch_wal, Backup Control Functions
pg_tables, pg_tables
pg_tablespace, pg_tablespace
pg_tablespace_databases, System Information Functions and Operators
pg_tablespace_location, System Information Functions and Operators
pg_tablespace_size, Database Object Management Functions
pg_table_is_visible, System Information Functions and Operators
pg_table_size, Database Object Management Functions
pg_temp, Statement Behavior
securing functions, Writing SECURITY DEFINER Functions Safely
pg_terminate_backend, Server Signaling Functions
pg_test_fsync, pg_test_fsync
pg_test_timing, pg_test_timing
pg_timezone_abbrevs, pg_timezone_abbrevs
pg_timezone_names, pg_timezone_names
pg_total_relation_size, Database Object Management Functions
pg_transform, pg_transform
pg_trgm, pg_trgm
pg_trgm.similarity_threshold configuration parameter, GUC Parameters
+ , Other Planner Options
parallel_setup_cost configuration parameter, Planner Cost Constants
parallel_tuple_cost configuration parameter, Planner Cost Constants
parallel_workers storage parameter, Storage Parameters
parameter
syntax, Positional Parameters
parenthesis, Value Expressions
parse_ident, String Functions and Operators
partition pruning, Partition Pruning
partitioned table, Table Partitioning
partitioning, Table Partitioning
password, Role Attributes
authentication, Password Authentication
of the superuser, Creating a Database Cluster
password file, The Password File
passwordcheck, passwordcheck
password_encryption configuration parameter, Authentication
path, Geometric Functions and Operators
for schemas, Statement Behavior
PATH, Environment Variables
path (data type), Paths
pattern matching, Pattern Matching
patterns
in psql and pg_dump, Patterns
pclose, Geometric Functions and Operators
peer, Peer Authentication
percentile
continuous, Aggregate Functions
discrete, Aggregate Functions
percent_rank, Window Functions
hypothetical, Aggregate Functions
performance, Performance Tips
perl, Requirements
Perl, PL/Perl — Perl Procedural Language
permission (see privilege)
pfree, Writing Code
PGAPPNAME, Environment Variables
pgbench, pgbench
PGcancel, Canceling Queries in Progress
PGCHANNELBINDING, Environment Variables
PGCLIENTENCODING, Environment Variables
PGconn, Database Connection Control Functions
PGCONNECT_TIMEOUT, Environment Variables
pgcrypto, pgcrypto
PGDATA, Creating a Database Cluster
PGDATABASE, Environment Variables
PGDATESTYLE, Environment Variables
PGEventProc, Event Callback Procedure
PGGEQO, Environment Variables
PGGSSENCMODE, Environment Variables
PGGSSLIB, Environment Variables
PGHOST, Environment Variables
PGHOSTADDR, Environment Variables
PGKRBSRVNAME, Environment Variables
PGLOCALEDIR, Environment Variables
PGOPTIONS, Environment Variables
PGPASSFILE, Environment Variables
PGPASSWORD, Environment Variables
PGPORT, Environment Variables
pgp_armor_headers, pgp_armor_headers
pgp_key_id, pgp_key_id()
pgp_pub_decrypt, pgp_pub_decrypt()
pgp_pub_decrypt_bytea, pgp_pub_decrypt()
pgp_pub_encrypt, pgp_pub_encrypt()
pgp_pub_encrypt_bytea, pgp_pub_encrypt()
pgp_sym_decrypt, pgp_sym_decrypt()
pgp_sym_decrypt_bytea, pgp_sym_decrypt()
pgp_sym_encrypt, pgp_sym_encrypt()
pgp_sym_encrypt_bytea, pgp_sym_encrypt()
PGREQUIREPEER, Environment Variables
PGREQUIRESSL, Environment Variables
PGresult, Main Functions
pgrowlocks, pgrowlocks, Overview
PGSERVICE, Environment Variables
PGSERVICEFILE, Environment Variables
PGSSLCERT, Environment Variables
PGSSLCOMPRESSION, Environment Variables
PGSSLCRL, Environment Variables
PGSSLKEY, Environment Variables
PGSSLMAXPROTOCOLVERSION, Environment Variables
PGSSLMINPROTOCOLVERSION, Environment Variables
PGSSLMODE, Environment Variables
PGSSLROOTCERT, Environment Variables
pgstatginindex, Functions
pgstathashindex, Functions
pgstatindex, Functions
pgstattuple, pgstattuple, Functions
pgstattuple_approx, Functions
PGSYSCONFDIR, Environment Variables
PGTARGETSESSIONATTRS, Environment Variables
PGTZ, Environment Variables
PGUSER, Environment Variables
pgxs, Extension Building Infrastructure
pg_advisory_lock, Advisory Lock Functions
pg_advisory_lock_shared, Advisory Lock Functions
pg_advisory_unlock, Advisory Lock Functions
pg_advisory_unlock_all, Advisory Lock Functions
pg_advisory_unlock_shared, Advisory Lock Functions
pg_advisory_xact_lock, Advisory Lock Functions
pg_advisory_xact_lock_shared, Advisory Lock Functions
pg_aggregate, pg_aggregate
pg_am, pg_am
pg_amop, pg_amop
pg_amproc, pg_amproc
pg_archivecleanup, pg_archivecleanup
pg_attrdef, pg_attrdef
pg_attribute, pg_attribute
pg_authid, pg_authid
pg_auth_members, pg_auth_members
pg_available_extensions, pg_available_extensions
pg_available_extension_versions, pg_available_extension_versions
pg_backend_pid, System Information Functions and Operators
pg_backup_start_time, Backup Control Functions
pg_basebackup, pg_basebackup
pg_blocking_pids, System Information Functions and Operators
pg_buffercache, pg_buffercache
pg_buffercache_pages, pg_buffercache
pg_cancel_backend, Server Signaling Functions
pg_cast, pg_cast
pg_checksums, pg_checksums
pg_class, pg_class
pg_client_encoding, String Functions and Operators
pg_collation, pg_collation
pg_collation_actual_version, Database Object Management Functions
pg_collation_is_visible, System Information Functions and Operators
PG_COLOR, When Color is Used
PG_COLORS, Configuring the Colors
pg_column_size, Database Object Management Functions
pg_config, pg_config, pg_config
with + ecpg, Processing Embedded SQL Programs
with libpq, Building libpq Programs
with user-defined C functions, Writing Code
pg_conf_load_time, System Information Functions and Operators
pg_constraint, pg_constraint
pg_controldata, pg_controldata
pg_control_checkpoint, System Information Functions and Operators
pg_control_init, System Information Functions and Operators
pg_control_recovery, System Information Functions and Operators
pg_control_system, System Information Functions and Operators
pg_conversion, pg_conversion
pg_conversion_is_visible, System Information Functions and Operators
pg_copy_logical_replication_slot, Replication Management Functions
pg_copy_physical_replication_slot, Replication Management Functions
pg_create_logical_replication_slot, Replication Management Functions
pg_create_physical_replication_slot, Replication Management Functions
pg_create_restore_point, Backup Control Functions
pg_ctl, Creating a Database Cluster, Starting the Database Server, pg_ctl
pg_current_logfile, System Information Functions and Operators
pg_current_snapshot, System Information Functions and Operators
pg_current_wal_flush_lsn, Backup Control Functions
pg_current_wal_insert_lsn, Backup Control Functions
pg_current_wal_lsn, Backup Control Functions
pg_current_xact_id, System Information Functions and Operators
pg_current_xact_id_if_assigned, System Information Functions and Operators
pg_cursors, pg_cursors
pg_database, Template Databases, pg_database
pg_database_size, Database Object Management Functions
pg_db_role_setting, pg_db_role_setting
pg_ddl_command, Pseudo-Types
pg_default_acl, pg_default_acl
pg_depend, pg_depend
pg_describe_object, System Information Functions and Operators
pg_description, pg_description
pg_drop_replication_slot, Replication Management Functions
pg_dump, pg_dump
pg_dumpall, pg_dumpall
use during upgrade, Upgrading Data via pg_dumpall
pg_enum, pg_enum
pg_event_trigger, pg_event_trigger
pg_event_trigger_ddl_commands, Capturing Changes at Command End
pg_event_trigger_dropped_objects, Processing Objects Dropped by a DDL Command
pg_event_trigger_table_rewrite_oid, Handling a Table Rewrite Event
pg_event_trigger_table_rewrite_reason, Handling a Table Rewrite Event
pg_export_snapshot, Snapshot Synchronization Functions
pg_extension, pg_extension
pg_extension_config_dump, Extension Configuration Tables
pg_filenode_relation, Database Object Management Functions
pg_file_rename, adminpack
pg_file_settings, pg_file_settings
pg_file_sync, adminpack
pg_file_unlink, adminpack
pg_file_write, adminpack
pg_foreign_data_wrapper, pg_foreign_data_wrapper
pg_foreign_server, pg_foreign_server
pg_foreign_table, pg_foreign_table
pg_freespace, Functions
pg_freespacemap, pg_freespacemap
pg_function_is_visible, System Information Functions and Operators
pg_get_constraintdef, System Information Functions and Operators
pg_get_expr, System Information Functions and Operators
pg_get_functiondef, System Information Functions and Operators
pg_get_function_arguments, System Information Functions and Operators
pg_get_function_identity_arguments, System Information Functions and Operators
pg_get_function_result, System Information Functions and Operators
pg_get_indexdef, System Information Functions and Operators
pg_get_keywords, System Information Functions and Operators
pg_get_object_address, System Information Functions and Operators
pg_get_ruledef, System Information Functions and Operators
pg_get_serial_sequence, System Information Functions and Operators
pg_get_statisticsobjdef, System Information Functions and Operators
pg_get_triggerdef, System Information Functions and Operators
pg_get_userbyid, System Information Functions and Operators
pg_get_viewdef, System Information Functions and Operators
pg_group, pg_group
pg_has_role, System Information Functions and Operators
pg_hba.conf, The pg_hba.conf File
pg_hba_file_rules, pg_hba_file_rules
pg_ident.conf, User Name Maps
pg_identify_object, System Information Functions and Operators
pg_identify_object_as_address, System Information Functions and Operators
pg_import_system_collations, Database Object Management Functions
pg_index, pg_index
pg_indexam_has_property, System Information Functions and Operators
pg_indexes, pg_indexes
pg_indexes_size, Database Object Management Functions
pg_index_column_has_property, System Information Functions and Operators
pg_index_has_property, System Information Functions and Operators
pg_inherits, pg_inherits
pg_init_privs, pg_init_privs
pg_isready, pg_isready
pg_is_in_backup, Backup Control Functions
pg_is_in_recovery, Recovery Control Functions
pg_is_other_temp_schema, System Information Functions and Operators
pg_is_wal_replay_paused, Recovery Control Functions
pg_jit_available, System Information Functions and Operators
pg_language, pg_language
pg_largeobject, pg_largeobject
pg_largeobject_metadata, pg_largeobject_metadata
pg_last_committed_xact, System Information Functions and Operators
pg_last_wal_receive_lsn, Recovery Control Functions
pg_last_wal_replay_lsn, Recovery Control Functions
pg_last_xact_replay_timestamp, Recovery Control Functions
pg_listening_channels, System Information Functions and Operators
pg_locks, pg_locks
pg_logdir_ls, adminpack
pg_logical_emit_message, Replication Management Functions
pg_logical_slot_get_binary_changes, Replication Management Functions
pg_logical_slot_get_changes, Replication Management Functions
pg_logical_slot_peek_binary_changes, Replication Management Functions
pg_logical_slot_peek_changes, Replication Management Functions
pg_lsn, pg_lsn Type
pg_ls_archive_statusdir, Generic File Access Functions
pg_ls_dir, Generic File Access Functions
pg_ls_logdir, Generic File Access Functions
pg_ls_tmpdir, Generic File Access Functions
pg_ls_waldir, Generic File Access Functions
pg_matviews, pg_matviews
pg_mcv_list_items, Inspecting MCV Lists
pg_my_temp_schema, System Information Functions and Operators
pg_namespace, pg_namespace
pg_notification_queue_usage, System Information Functions and Operators
pg_notify, pg_notify
pg_opclass, pg_opclass
pg_opclass_is_visible, System Information Functions and Operators
pg_operator, pg_operator
pg_operator_is_visible, System Information Functions and Operators
pg_opfamily, pg_opfamily
pg_opfamily_is_visible, System Information Functions and Operators
pg_options_to_table, System Information Functions and Operators
pg_partitioned_table, pg_partitioned_table
pg_partition_ancestors, Database Object Management Functions
pg_partition_root, Database Object Management Functions
pg_partition_tree, Database Object Management Functions
pg_policies, pg_policies
pg_policy, pg_policy
pg_postmaster_start_time, System Information Functions and Operators
pg_prepared_statements, pg_prepared_statements
pg_prepared_xacts, pg_prepared_xacts
pg_prewarm, pg_prewarm
pg_prewarm.autoprewarm configuration parameter, Configuration Parameters
pg_prewarm.autoprewarm_interval configuration parameter, Configuration Parameters
pg_proc, pg_proc
pg_promote, Recovery Control Functions
pg_publication, pg_publication
pg_publication_rel, pg_publication_rel
pg_publication_tables, pg_publication_tables
pg_range, pg_range
pg_read_binary_file, Generic File Access Functions
pg_read_file, Generic File Access Functions
pg_receivewal, pg_receivewal
pg_receivexlog, pg_receivexlog renamed to pg_receivewal (see pg_receivewal)
pg_recvlogical, pg_recvlogical
pg_relation_filenode, Database Object Management Functions
pg_relation_filepath, Database Object Management Functions
pg_relation_size, Database Object Management Functions
pg_reload_conf, Server Signaling Functions
pg_relpages, Functions
pg_replication_origin, pg_replication_origin
pg_replication_origin_advance, Replication Management Functions
pg_replication_origin_create, Replication Management Functions
pg_replication_origin_drop, Replication Management Functions
pg_replication_origin_oid, Replication Management Functions
pg_replication_origin_progress, Replication Management Functions
pg_replication_origin_session_is_setup, Replication Management Functions
pg_replication_origin_session_progress, Replication Management Functions
pg_replication_origin_session_reset, Replication Management Functions
pg_replication_origin_session_setup, Replication Management Functions
pg_replication_origin_status, pg_replication_origin_status
pg_replication_origin_xact_reset, Replication Management Functions
pg_replication_origin_xact_setup, Replication Management Functions
pg_replication_slots, pg_replication_slots
pg_replication_slot_advance, Replication Management Functions
pg_resetwal, pg_resetwal
pg_resetxlog, pg_resetxlog renamed to pg_resetwal (see pg_resetwal)
pg_restore, pg_restore
pg_rewind, pg_rewind
pg_rewrite, pg_rewrite
pg_roles, pg_roles
pg_rotate_logfile, Server Signaling Functions
pg_rules, pg_rules
pg_safe_snapshot_blocking_pids, System Information Functions and Operators
pg_seclabel, pg_seclabel
pg_seclabels, pg_seclabels
pg_sequence, pg_sequence
pg_sequences, pg_sequences
pg_service.conf, The Connection Service File
pg_settings, pg_settings
pg_shadow, pg_shadow
pg_shdepend, pg_shdepend
pg_shdescription, pg_shdescription
pg_shmem_allocations, pg_shmem_allocations
pg_shseclabel, pg_shseclabel
pg_size_bytes, Database Object Management Functions
pg_size_pretty, Database Object Management Functions
pg_sleep, Delaying Execution
pg_sleep_for, Delaying Execution
pg_sleep_until, Delaying Execution
pg_snapshot_xip, System Information Functions and Operators
pg_snapshot_xmax, System Information Functions and Operators
pg_snapshot_xmin, System Information Functions and Operators
pg_standby, pg_standby
pg_start_backup, Backup Control Functions
pg_statio_all_indexes, Viewing Statistics, pg_statio_all_indexes
pg_statio_all_sequences, Viewing Statistics, pg_statio_all_sequences
pg_statio_all_tables, Viewing Statistics, pg_statio_all_tables
pg_statio_sys_indexes, Viewing Statistics
pg_statio_sys_sequences, Viewing Statistics
pg_statio_sys_tables, Viewing Statistics
pg_statio_user_indexes, Viewing Statistics
pg_statio_user_sequences, Viewing Statistics
pg_statio_user_tables, Viewing Statistics
pg_statistic, Single-Column Statistics, pg_statistic
pg_statistics_obj_is_visible, System Information Functions and Operators
pg_statistic_ext, Extended Statistics, pg_statistic_ext
pg_statistic_ext_data, Extended Statistics, pg_statistic_ext
pg_stats, Single-Column Statistics, pg_stats
pg_stats_ext, pg_stats_ext
pg_stat_activity, Viewing Statistics, pg_stat_activity
pg_stat_all_indexes, Viewing Statistics, pg_stat_all_indexes
pg_stat_all_tables, Viewing Statistics, pg_stat_all_tables
pg_stat_archiver, Viewing Statistics, pg_stat_archiver
pg_stat_bgwriter, Viewing Statistics, pg_stat_bgwriter
pg_stat_clear_snapshot, Statistics Functions
pg_stat_database, Viewing Statistics, pg_stat_database
pg_stat_database_conflicts, Viewing Statistics, pg_stat_database_conflicts
pg_stat_file, Generic File Access Functions
pg_stat_get_activity, Statistics Functions
pg_stat_get_backend_activity, Statistics Functions
pg_stat_get_backend_activity_start, Statistics Functions
pg_stat_get_backend_client_addr, Statistics Functions
pg_stat_get_backend_client_port, Statistics Functions
pg_stat_get_backend_dbid, Statistics Functions
pg_stat_get_backend_idset, Statistics Functions
pg_stat_get_backend_pid, Statistics Functions
pg_stat_get_backend_start, Statistics Functions
pg_stat_get_backend_userid, Statistics Functions
pg_stat_get_backend_wait_event, Statistics Functions
pg_stat_get_backend_wait_event_type, Statistics Functions
pg_stat_get_backend_xact_start, Statistics Functions
pg_stat_get_snapshot_timestamp, Statistics Functions
pg_stat_get_xact_blocks_fetched, Statistics Functions
pg_stat_get_xact_blocks_hit, Statistics Functions
pg_stat_gssapi, Viewing Statistics, pg_stat_gssapi
pg_stat_progress_analyze, Viewing Statistics
pg_stat_progress_basebackup, Viewing Statistics
pg_stat_progress_cluster, Viewing Statistics
pg_stat_progress_create_index, Viewing Statistics
pg_stat_progress_vacuum, Viewing Statistics
pg_stat_replication, Viewing Statistics, pg_stat_replication
pg_stat_reset, Statistics Functions
pg_stat_reset_shared, Statistics Functions
pg_stat_reset_single_function_counters, Statistics Functions
pg_stat_reset_single_table_counters, Statistics Functions
pg_stat_reset_slru, Statistics Functions
pg_stat_slru, Viewing Statistics, pg_stat_slru
pg_stat_ssl, Viewing Statistics, pg_stat_ssl
pg_stat_statements, pg_stat_statements
function, Functions
pg_stat_statements_reset, Functions
pg_stat_subscription, Viewing Statistics, pg_stat_subscription
pg_stat_sys_indexes, Viewing Statistics
pg_stat_sys_tables, Viewing Statistics
pg_stat_user_functions, Viewing Statistics, pg_stat_user_functions
pg_stat_user_indexes, Viewing Statistics
pg_stat_user_tables, Viewing Statistics
pg_stat_wal_receiver, Viewing Statistics, pg_stat_wal_receiver
pg_stat_xact_all_tables, Viewing Statistics
pg_stat_xact_sys_tables, Viewing Statistics
pg_stat_xact_user_functions, Viewing Statistics
pg_stat_xact_user_tables, Viewing Statistics
pg_stop_backup, Backup Control Functions
pg_subscription, pg_subscription
pg_subscription_rel, pg_subscription_rel
pg_switch_wal, Backup Control Functions
pg_tables, pg_tables
pg_tablespace, pg_tablespace
pg_tablespace_databases, System Information Functions and Operators
pg_tablespace_location, System Information Functions and Operators
pg_tablespace_size, Database Object Management Functions
pg_table_is_visible, System Information Functions and Operators
pg_table_size, Database Object Management Functions
pg_temp, Statement Behavior
securing functions, Writing SECURITY DEFINER Functions Safely
pg_terminate_backend, Server Signaling Functions
pg_test_fsync, pg_test_fsync
pg_test_timing, pg_test_timing
pg_timezone_abbrevs, pg_timezone_abbrevs
pg_timezone_names, pg_timezone_names
pg_total_relation_size, Database Object Management Functions
pg_transform, pg_transform
pg_trgm, pg_trgm
pg_trgm.similarity_threshold configuration parameter, GUC Parameters
pg_trgm.strict_word_similarity_threshold configuration parameter - , GUC Parameters
+ , GUC Parameters
pg_trgm.word_similarity_threshold configuration parameter - , GUC Parameters
pg_trigger, pg_trigger
pg_trigger_depth, System Information Functions and Operators
pg_try_advisory_lock, Advisory Lock Functions
pg_try_advisory_lock_shared, Advisory Lock Functions
pg_try_advisory_xact_lock, Advisory Lock Functions
pg_try_advisory_xact_lock_shared, Advisory Lock Functions
pg_ts_config, pg_ts_config
pg_ts_config_is_visible, System Information Functions and Operators
pg_ts_config_map, pg_ts_config_map
pg_ts_dict, pg_ts_dict
pg_ts_dict_is_visible, System Information Functions and Operators
pg_ts_parser, pg_ts_parser
pg_ts_parser_is_visible, System Information Functions and Operators
pg_ts_template, pg_ts_template
pg_ts_template_is_visible, System Information Functions and Operators
pg_type, pg_type
pg_typeof, System Information Functions and Operators
pg_type_is_visible, System Information Functions and Operators
pg_upgrade, pg_upgrade
pg_user, pg_user
pg_user_mapping, pg_user_mapping
pg_user_mappings, pg_user_mappings
pg_verifybackup, pg_verifybackup
pg_views, pg_views
pg_visibility, pg_visibility
pg_visible_in_snapshot, System Information Functions and Operators
pg_waldump, pg_waldump
pg_walfile_name, Backup Control Functions
pg_walfile_name_offset, Backup Control Functions
pg_wal_lsn_diff, Backup Control Functions
pg_wal_replay_pause, Recovery Control Functions
pg_wal_replay_resume, Recovery Control Functions
pg_xact_commit_timestamp, System Information Functions and Operators
pg_xact_status, System Information Functions and Operators
pg_xlogdump, pg_xlogdump renamed to pg_waldump (see pg_waldump)
phantom read, Transaction Isolation
phraseto_tsquery, Text Search Functions and Operators, Parsing Queries
pi, Mathematical Functions and Operators
PIC, Compiling and Linking Dynamically-Loaded Functions
PID
determining PID of server process
in libpq, Connection Status Functions
pipelining, Pipelining
protocol specification, Pipelining
PITR, Backup and Restore
PITR standby, High Availability, Load Balancing, and Replication
pkg-config, PostgreSQL Features
with + , GUC Parameters
pg_trigger, pg_trigger
pg_trigger_depth, System Information Functions and Operators
pg_try_advisory_lock, Advisory Lock Functions
pg_try_advisory_lock_shared, Advisory Lock Functions
pg_try_advisory_xact_lock, Advisory Lock Functions
pg_try_advisory_xact_lock_shared, Advisory Lock Functions
pg_ts_config, pg_ts_config
pg_ts_config_is_visible, System Information Functions and Operators
pg_ts_config_map, pg_ts_config_map
pg_ts_dict, pg_ts_dict
pg_ts_dict_is_visible, System Information Functions and Operators
pg_ts_parser, pg_ts_parser
pg_ts_parser_is_visible, System Information Functions and Operators
pg_ts_template, pg_ts_template
pg_ts_template_is_visible, System Information Functions and Operators
pg_type, pg_type
pg_typeof, System Information Functions and Operators
pg_type_is_visible, System Information Functions and Operators
pg_upgrade, pg_upgrade
pg_user, pg_user
pg_user_mapping, pg_user_mapping
pg_user_mappings, pg_user_mappings
pg_verifybackup, pg_verifybackup
pg_views, pg_views
pg_visibility, pg_visibility
pg_visible_in_snapshot, System Information Functions and Operators
pg_waldump, pg_waldump
pg_walfile_name, Backup Control Functions
pg_walfile_name_offset, Backup Control Functions
pg_wal_lsn_diff, Backup Control Functions
pg_wal_replay_pause, Recovery Control Functions
pg_wal_replay_resume, Recovery Control Functions
pg_xact_commit_timestamp, System Information Functions and Operators
pg_xact_status, System Information Functions and Operators
pg_xlogdump, pg_xlogdump renamed to pg_waldump (see pg_waldump)
phantom read, Transaction Isolation
phraseto_tsquery, Text Search Functions and Operators, Parsing Queries
pi, Mathematical Functions and Operators
PIC, Compiling and Linking Dynamically-Loaded Functions
PID
determining PID of server process
in libpq, Connection Status Functions
pipelining, Pipelining
protocol specification, Pipelining
PITR, Backup and Restore
PITR standby, High Availability, Load Balancing, and Replication
pkg-config, PostgreSQL Features
with ecpg, Processing Embedded SQL Programs
with - libpq, Building libpq Programs
PL/Perl, PL/Perl — Perl Procedural Language
PL/PerlU, Trusted and Untrusted PL/Perl
PL/pgSQL, PL/pgSQL — SQL Procedural Language
PL/Python, PL/Python — Python Procedural Language
PL/SQL (Oracle), Porting from Oracle PL/SQL
porting to PL/pgSQL, Porting from Oracle PL/SQL
PL/Tcl, PL/Tcl — Tcl Procedural Language
plainto_tsquery, Text Search Functions and Operators, Parsing Queries
plan_cache_mode configuration parameter, Other Planner Options
plperl.on_init configuration parameter, Configuration
plperl.on_plperlu_init configuration parameter, Configuration
plperl.on_plperl_init configuration parameter, Configuration
plperl.use_strict configuration parameter, Configuration
plpgsql.check_asserts configuration parameter, Checking Assertions
plpgsql.variable_conflict configuration parameter, Variable Substitution
pltcl.start_proc configuration parameter, PL/Tcl Configuration
pltclu.start_proc configuration parameter, PL/Tcl Configuration
point, Points, Geometric Functions and Operators
point-in-time recovery, Backup and Restore
policy, Row Security Policies
polygon, Polygons, Geometric Functions and Operators
polymorphic function, Polymorphic Types
polymorphic type, Polymorphic Types
popen, Geometric Functions and Operators
populate_record, hstore Operators and Functions
port, Parameter Key Words
port configuration parameter, Connection Settings
position, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
POSTGRES, The Berkeley POSTGRES Project
postgres, Architectural Fundamentals, Starting the Database Server, Creating a Database, postgres
postgres user, The PostgreSQL User Account
Postgres95, Postgres95
postgresql.auto.conf, Parameter Interaction via the Configuration File
postgresql.conf, Parameter Interaction via the Configuration File
postgres_fdw, postgres_fdw
postmaster, postmaster
post_auth_delay configuration parameter, Developer Options
power, Mathematical Functions and Operators
PQbackendPID, Connection Status Functions
PQbinaryTuples, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQcancel, Canceling Queries in Progress
PQclear, Main Functions
PQclientEncoding, Control Functions
PQcmdStatus, Retrieving Other Result Information
PQcmdTuples, Retrieving Other Result Information
PQconndefaults, Database Connection Control Functions
PQconnectdb, Database Connection Control Functions
PQconnectdbParams, Database Connection Control Functions
PQconnectionNeedsPassword, Connection Status Functions
PQconnectionUsedPassword, Connection Status Functions
PQconnectPoll, Database Connection Control Functions
PQconnectStart, Database Connection Control Functions
PQconnectStartParams, Database Connection Control Functions
PQconninfo, Database Connection Control Functions
PQconninfoFree, Miscellaneous Functions
PQconninfoParse, Database Connection Control Functions
PQconsumeInput, Asynchronous Command Processing
PQcopyResult, Miscellaneous Functions
PQdb, Connection Status Functions
PQdescribePortal, Main Functions
PQdescribePrepared, Main Functions
PQencryptPassword, Miscellaneous Functions
PQencryptPasswordConn, Miscellaneous Functions
PQendcopy, Obsolete Functions for COPY
PQerrorMessage, Connection Status Functions
PQescapeBytea, Escaping Strings for Inclusion in SQL Commands
PQescapeByteaConn, Escaping Strings for Inclusion in SQL Commands
PQescapeIdentifier, Escaping Strings for Inclusion in SQL Commands
PQescapeLiteral, Escaping Strings for Inclusion in SQL Commands
PQescapeString, Escaping Strings for Inclusion in SQL Commands
PQescapeStringConn, Escaping Strings for Inclusion in SQL Commands
PQexec, Main Functions
PQexecParams, Main Functions
PQexecPrepared, Main Functions
PQfformat, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQfinish, Database Connection Control Functions
PQfireResultCreateEvents, Miscellaneous Functions
PQflush, Asynchronous Command Processing
PQfmod, Retrieving Query Result Information
PQfn, The Fast-Path Interface
PQfname, Retrieving Query Result Information
PQfnumber, Retrieving Query Result Information
PQfreeCancel, Canceling Queries in Progress
PQfreemem, Miscellaneous Functions
PQfsize, Retrieving Query Result Information
PQftable, Retrieving Query Result Information
PQftablecol, Retrieving Query Result Information
PQftype, Retrieving Query Result Information
PQgetCancel, Canceling Queries in Progress
PQgetCopyData, Functions for Receiving COPY Data
PQgetisnull, Retrieving Query Result Information
PQgetlength, Retrieving Query Result Information
PQgetline, Obsolete Functions for COPY
PQgetlineAsync, Obsolete Functions for COPY
PQgetResult, Asynchronous Command Processing
PQgetssl, Connection Status Functions
PQgetSSLKeyPassHook_OpenSSL, Database Connection Control Functions
PQgetvalue, Retrieving Query Result Information
PQhost, Connection Status Functions
PQhostaddr, Connection Status Functions
PQinitOpenSSL, SSL Library Initialization
PQinitSSL, SSL Library Initialization
PQinstanceData, Event Support Functions
PQisBusy, Asynchronous Command Processing
PQisnonblocking, Asynchronous Command Processing
PQisthreadsafe, Behavior in Threaded Programs
PQlibVersion, Miscellaneous Functions
(see also PQserverVersion)
PQmakeEmptyPGresult, Miscellaneous Functions
PQnfields, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQnotifies, Asynchronous Notification
PQnparams, Retrieving Query Result Information
PQntuples, Retrieving Query Result Information
PQoidStatus, Retrieving Other Result Information
PQoidValue, Retrieving Other Result Information
PQoptions, Connection Status Functions
PQparameterStatus, Connection Status Functions
PQparamtype, Retrieving Query Result Information
PQpass, Connection Status Functions
PQping, Database Connection Control Functions
PQpingParams, Database Connection Control Functions
PQport, Connection Status Functions
PQprepare, Main Functions
PQprint, Retrieving Query Result Information
PQprotocolVersion, Connection Status Functions
PQputCopyData, Functions for Sending COPY Data
PQputCopyEnd, Functions for Sending COPY Data
PQputline, Obsolete Functions for COPY
PQputnbytes, Obsolete Functions for COPY
PQregisterEventProc, Event Support Functions
PQrequestCancel, Canceling Queries in Progress
PQreset, Database Connection Control Functions
PQresetPoll, Database Connection Control Functions
PQresetStart, Database Connection Control Functions
PQresStatus, Main Functions
PQresultAlloc, Miscellaneous Functions
PQresultErrorField, Main Functions
PQresultErrorMessage, Main Functions
PQresultInstanceData, Event Support Functions
PQresultMemorySize, Miscellaneous Functions
PQresultSetInstanceData, Event Support Functions
PQresultStatus, Main Functions
PQresultVerboseErrorMessage, Main Functions
PQsendDescribePortal, Asynchronous Command Processing
PQsendDescribePrepared, Asynchronous Command Processing
PQsendPrepare, Asynchronous Command Processing
PQsendQuery, Asynchronous Command Processing
PQsendQueryParams, Asynchronous Command Processing
PQsendQueryPrepared, Asynchronous Command Processing
PQserverVersion, Connection Status Functions
PQsetClientEncoding, Control Functions
PQsetdb, Database Connection Control Functions
PQsetdbLogin, Database Connection Control Functions
PQsetErrorContextVisibility, Control Functions
PQsetErrorVerbosity, Control Functions
PQsetInstanceData, Event Support Functions
PQsetnonblocking, Asynchronous Command Processing
PQsetNoticeProcessor, Notice Processing
PQsetNoticeReceiver, Notice Processing
PQsetResultAttrs, Miscellaneous Functions
PQsetSingleRowMode, Retrieving Query Results Row-by-Row
PQsetSSLKeyPassHook_OpenSSL, Database Connection Control Functions
PQsetvalue, Miscellaneous Functions
PQsocket, Connection Status Functions
PQsslAttribute, Connection Status Functions
PQsslAttributeNames, Connection Status Functions
PQsslInUse, Connection Status Functions
PQsslStruct, Connection Status Functions
PQstatus, Connection Status Functions
PQtrace, Control Functions
PQtransactionStatus, Connection Status Functions
PQtty, Connection Status Functions
PQunescapeBytea, Escaping Strings for Inclusion in SQL Commands
PQuntrace, Control Functions
PQuser, Connection Status Functions
predicate locking, Serializable Isolation Level
PREPARE, PREPARE
PREPARE TRANSACTION, PREPARE TRANSACTION
prepared statements, DEALLOCATE, EXECUTE, EXPLAIN, PREPARE
creating, PREPARE
executing, EXECUTE
removing, DEALLOCATE
showing the query plan, EXPLAIN
preparing a query
in PL/pgSQL, Plan Caching
in PL/Python, Database Access Functions
in PL/Tcl, Database Access from PL/Tcl
pre_auth_delay configuration parameter, Developer Options
primary key, Primary Keys
primary_conninfo configuration parameter, Standby Servers
primary_slot_name configuration parameter, Standby Servers
privilege, Privileges, Schemas and Privileges, Rules and Privileges, Rules and Privileges
querying, System Information Functions and Operators
with rules, Rules and Privileges
for schemas, Schemas and Privileges
with views, Rules and Privileges
procedural language, Procedural Languages, Writing a Procedural Language Handler
externally maintained, Procedural Languages
handler for, Writing a Procedural Language Handler
procedure, User-Defined Procedures
user-defined, User-Defined Procedures
promote_trigger_file configuration parameter, Standby Servers
protocol, Frontend/Backend Protocol
frontend-backend, Frontend/Backend Protocol
ps, Standard Unix Tools
to monitor activity, Standard Unix Tools
psql, Accessing a Database, psql
Python, PL/Python — Python Procedural Language

R

radians, Mathematical Functions and Operators
radius, Geometric Functions and Operators
RADIUS, RADIUS Authentication
RAISE
in PL/pgSQL, Reporting Errors and Messages
random, Mathematical Functions and Operators
random_page_cost configuration parameter, Planner Cost Constants
range table, The Query Tree
range type, Range Types
exclude, Constraints on Ranges
indexes on, Indexing
range_merge, Range Functions and Operators
rank, Window Functions
hypothetical, Aggregate Functions
read committed, Read Committed Isolation Level
read-only transaction, Statement Behavior
setting, SET TRANSACTION
setting default, Statement Behavior
readline, Requirements
real, Floating-Point Types
REASSIGN OWNED, REASSIGN OWNED
record, Pseudo-Types
recovery.conf, recovery.conf file merged into postgresql.conf
recovery.signal, Archive Recovery
recovery_end_command configuration parameter, Archive Recovery
recovery_min_apply_delay configuration parameter, Standby Servers
recovery_target configuration parameter, Recovery Target
recovery_target_action configuration parameter, Recovery Target
recovery_target_inclusive configuration parameter, Recovery Target
recovery_target_lsn configuration parameter, Recovery Target
recovery_target_name configuration parameter, Recovery Target
recovery_target_time configuration parameter, Recovery Target
recovery_target_timeline configuration parameter, Recovery Target
recovery_target_xid configuration parameter, Recovery Target
rectangle, Boxes
RECURSIVE, CREATE VIEW
in common table expressions, SELECT in WITH
in views, CREATE VIEW
referential integrity, Foreign Keys, Foreign Keys
REFRESH MATERIALIZED VIEW, REFRESH MATERIALIZED VIEW
regclass, Object Identifier Types
regcollation, Object Identifier Types
regconfig, Object Identifier Types
regdictionary, Object Identifier Types
regexp_match, String Functions and Operators, POSIX Regular Expressions
regexp_matches, String Functions and Operators, POSIX Regular Expressions
regexp_replace, String Functions and Operators, POSIX Regular Expressions
regexp_split_to_array, String Functions and Operators, POSIX Regular Expressions
regexp_split_to_table, String Functions and Operators, POSIX Regular Expressions
regnamespace, Object Identifier Types
regoper, Object Identifier Types
regoperator, Object Identifier Types
regproc, Object Identifier Types
regprocedure, Object Identifier Types
regression intercept, Aggregate Functions
regression slope, Aggregate Functions
regression test, Installation Procedure
regression tests, Regression Tests
regrole, Object Identifier Types
regr_avgx, Aggregate Functions
regr_avgy, Aggregate Functions
regr_count, Aggregate Functions
regr_intercept, Aggregate Functions
regr_r2, Aggregate Functions
regr_slope, Aggregate Functions
regr_sxx, Aggregate Functions
regr_sxy, Aggregate Functions
regr_syy, Aggregate Functions
regtype, Object Identifier Types
regular expression, SIMILAR TO Regular Expressions, POSIX Regular Expressions
(see also pattern matching)
regular expressions
and locales, Behavior
reindex, Routine Reindexing
REINDEX, REINDEX
reindexdb, reindexdb
relation, Concepts
relational database, Concepts
RELEASE SAVEPOINT, RELEASE SAVEPOINT
repeat, String Functions and Operators
repeatable read, Repeatable Read Isolation Level
replace, String Functions and Operators
replication, High Availability, Load Balancing, and Replication
Replication Origins, Replication Progress Tracking
Replication Progress Tracking, Replication Progress Tracking
replication slot
logical replication, Replication Slots
streaming replication, Replication Slots
reporting errors
in PL/pgSQL, Reporting Errors and Messages
RESET, RESET
restartpoint, WAL Configuration
restart_after_crash configuration parameter, Error Handling
restore_command configuration parameter, Archive Recovery
RESTRICT, Dependency Tracking
with DROP, Dependency Tracking
foreign key action, Foreign Keys
RETURN NEXT
in PL/pgSQL, RETURN NEXT and RETURN QUERY
RETURN QUERY
in PL/pgSQL, RETURN NEXT and RETURN QUERY
RETURNING, Returning Data from Modified Rows
RETURNING INTO, Executing a Query with a Single-Row Result
in PL/pgSQL, Executing a Query with a Single-Row Result
reverse, String Functions and Operators
REVOKE, Privileges, REVOKE
right, String Functions and Operators
right join, Joined Tables
role, Database Roles, Role Membership, Default Roles
applicable, applicable_roles
enabled, enabled_roles
membership in, Role Membership
privilege to bypass, Role Attributes
privilege to create, Role Attributes
privilege to inherit, Role Attributes
privilege to initiate replication, Role Attributes
privilege to limit connection, Role Attributes
ROLLBACK, ROLLBACK
rollback
psql, Variables
ROLLBACK PREPARED, ROLLBACK PREPARED
ROLLBACK TO SAVEPOINT, ROLLBACK TO SAVEPOINT
ROLLUP, GROUPING SETS, CUBE, and ROLLUP
round, Mathematical Functions and Operators
routine, User-Defined Procedures
routine maintenance, Routine Database Maintenance Tasks
row, Concepts, Table Basics
ROW, Row Constructors
row estimation, Row Estimation Examples
multivariate, Multivariate Statistics Examples
planner, Row Estimation Examples
row type, Composite Types
constructor, Row Constructors
row-level security, Row Security Policies
row-wise comparison, Row and Array Comparisons
row_number, Window Functions
row_security configuration parameter, Statement Behavior
row_security_active, System Information Functions and Operators
row_to_json, Processing and Creating JSON Data
rpad, String Functions and Operators
rtrim, String Functions and Operators
rule, The Rule System, Views and the Rule System, How SELECT Rules Work, Materialized Views, Rules on INSERT, UPDATE, and DELETE, Rules on INSERT, UPDATE, and DELETE, Rules on INSERT, UPDATE, and DELETE, Rules Versus Triggers
and materialized views, Materialized Views
and views, Views and the Rule System
for DELETE, Rules on INSERT, UPDATE, and DELETE
for INSERT, Rules on INSERT, UPDATE, and DELETE
for SELECT, How SELECT Rules Work
compared with triggers, Rules Versus Triggers
for UPDATE, Rules on INSERT, UPDATE, and DELETE

S

SAVEPOINT, SAVEPOINT
savepoints, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT, SAVEPOINT
defining, SAVEPOINT
releasing, RELEASE SAVEPOINT
rolling back, ROLLBACK TO SAVEPOINT
scalar (see expression)
scale, Mathematical Functions and Operators
schema, Schemas, Creating a Schema, The Public Schema, Overview
creating, Creating a Schema
current, The Schema Search Path, System Information Functions and Operators
public, The Public Schema
removing, Creating a Schema
SCRAM, Password Authentication
search path, The Schema Search Path
current, System Information Functions and Operators
object visibility, System Information Functions and Operators
search_path configuration parameter, The Schema Search Path, Statement Behavior
use in securing functions, Writing SECURITY DEFINER Functions Safely
SECURITY LABEL, SECURITY LABEL
sec_to_gc, Cube-Based Earth Distances
seg, seg
segment_size configuration parameter, Preset Options
SELECT, Querying a Table, Queries, SELECT Output Columns, SELECT
determination of result type, SELECT Output Columns
select list, Select Lists
SELECT INTO, Executing a Query with a Single-Row Result, SELECT INTO
in PL/pgSQL, Executing a Query with a Single-Row Result
semaphores, Shared Memory and Semaphores
sepgsql, sepgsql
sepgsql.debug_audit configuration parameter, GUC Parameters
sepgsql.permissive configuration parameter, GUC Parameters
sequence, Sequence Manipulation Functions
and serial type, Serial Types
sequential scan, Planner Method Configuration
seq_page_cost configuration parameter, Planner Cost Constants
serial, Serial Types
serial2, Serial Types
serial4, Serial Types
serial8, Serial Types
serializable, Serializable Isolation Level
Serializable Snapshot Isolation, Introduction
serialization anomaly, Transaction Isolation, Serializable Isolation Level
server log, Error Reporting and Logging, Log File Maintenance
log file maintenance, Log File Maintenance
server spoofing, Preventing Server Spoofing
server_encoding configuration parameter, Preset Options
server_version configuration parameter, Preset Options
server_version_num configuration parameter, Preset Options
session_preload_libraries configuration parameter, Shared Library Preloading
session_replication_role configuration parameter, Statement Behavior
session_user, System Information Functions and Operators
SET, Configuration Settings Functions, SET
SET CONSTRAINTS, SET CONSTRAINTS
set difference, Combining Queries
set intersection, Combining Queries
set operation, Combining Queries
set returning functions, Set Returning Functions
functions, Set Returning Functions
SET ROLE, SET ROLE
SET SESSION AUTHORIZATION, SET SESSION AUTHORIZATION
SET TRANSACTION, SET TRANSACTION
set union, Combining Queries
SET XML OPTION, Statement Behavior
setseed, Mathematical Functions and Operators
setval, Sequence Manipulation Functions
setweight, Text Search Functions and Operators, Manipulating Documents
setweight for specific lexeme(s), Text Search Functions and Operators
set_bit, Binary String Functions and Operators, Bit String Functions and Operators
set_byte, Binary String Functions and Operators
set_config, Configuration Settings Functions
set_limit, Functions and Operators
set_masklen, Network Address Functions and Operators
sha224, Binary String Functions and Operators
sha256, Binary String Functions and Operators
sha384, Binary String Functions and Operators
sha512, Binary String Functions and Operators
shared library, Shared Libraries, Compiling and Linking Dynamically-Loaded Functions
shared memory, Shared Memory and Semaphores
shared_buffers configuration parameter, Memory
shared_memory_type configuration parameter, Memory
shared_preload_libraries, Shared Memory and LWLocks
shared_preload_libraries configuration parameter, Shared Library Preloading
shobj_description, System Information Functions and Operators
SHOW, Configuration Settings Functions, SHOW, Streaming Replication Protocol
show_limit, Functions and Operators
show_trgm, Functions and Operators
shutdown, Shutting Down the Server
SIGHUP, Parameter Interaction via the Configuration File, The pg_hba.conf File, User Name Maps
SIGINT, Shutting Down the Server
sign, Mathematical Functions and Operators
signal
backend processes, Server Signaling Functions
significant digits, Locale and Formatting
SIGQUIT, Shutting Down the Server
SIGTERM, Shutting Down the Server
SIMILAR TO, SIMILAR TO Regular Expressions
similarity, Functions and Operators
sin, Mathematical Functions and Operators
sind, Mathematical Functions and Operators
single-user mode, Options for Single-User Mode
sinh, Mathematical Functions and Operators
skeys, hstore Operators and Functions
sleep, Delaying Execution
slice, hstore Operators and Functions
sliced bread (see TOAST)
slope, Geometric Functions and Operators
SLRU, pg_stat_slru
smallint, Integer Types
smallserial, Serial Types
Solaris, Solaris
installation on, Solaris
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
SOME, Aggregate Functions, Subquery Expressions, Row and Array Comparisons
sort, intarray Functions and Operators
sorting, Sorting Rows
sort_asc, intarray Functions and Operators
sort_desc, intarray Functions and Operators
soundex, Soundex
SP-GiST (see index)
SPI, Server Programming Interface, spi
examples, spi
spi_commit
in PL/Perl, Database Access from PL/Perl
SPI_commit, SPI_commit
SPI_commit_and_chain, SPI_commit
SPI_connect, SPI_connect
SPI_connect_ext, SPI_connect
SPI_copytuple, SPI_copytuple
spi_cursor_close
in PL/Perl, Database Access from PL/Perl
SPI_cursor_close, SPI_cursor_close
SPI_cursor_fetch, SPI_cursor_fetch
SPI_cursor_find, SPI_cursor_find
SPI_cursor_move, SPI_cursor_move
SPI_cursor_open, SPI_cursor_open
SPI_cursor_open_with_args, SPI_cursor_open_with_args
SPI_cursor_open_with_paramlist, SPI_cursor_open_with_paramlist
SPI_exec, SPI_exec
SPI_execp, SPI_execp
SPI_execute, SPI_execute
SPI_execute_plan, SPI_execute_plan
SPI_execute_plan_with_paramlist, SPI_execute_plan_with_paramlist
SPI_execute_with_args, SPI_execute_with_args
spi_exec_prepared
in PL/Perl, Database Access from PL/Perl
spi_exec_query
in PL/Perl, Database Access from PL/Perl
spi_fetchrow
in PL/Perl, Database Access from PL/Perl
SPI_finish, SPI_finish
SPI_fname, SPI_fname
SPI_fnumber, SPI_fnumber
spi_freeplan
in PL/Perl, Database Access from PL/Perl
SPI_freeplan, SPI_freeplan
SPI_freetuple, SPI_freetuple
SPI_freetuptable, SPI_freetuptable
SPI_getargcount, SPI_getargcount
SPI_getargtypeid, SPI_getargtypeid
SPI_getbinval, SPI_getbinval
SPI_getnspname, SPI_getnspname
SPI_getrelname, SPI_getrelname
SPI_gettype, SPI_gettype
SPI_gettypeid, SPI_gettypeid
SPI_getvalue, SPI_getvalue
SPI_is_cursor_plan, SPI_is_cursor_plan
SPI_keepplan, SPI_keepplan
SPI_modifytuple, SPI_modifytuple
SPI_palloc, SPI_palloc
SPI_pfree, SPI_pfree
spi_prepare
in PL/Perl, Database Access from PL/Perl
SPI_prepare, SPI_prepare
SPI_prepare_cursor, SPI_prepare_cursor
SPI_prepare_params, SPI_prepare_params
spi_query
in PL/Perl, Database Access from PL/Perl
spi_query_prepared
in PL/Perl, Database Access from PL/Perl
SPI_register_relation, SPI_register_relation
SPI_register_trigger_data, SPI_register_trigger_data
SPI_repalloc, SPI_repalloc
SPI_result_code_string, SPI_result_code_string
SPI_returntuple, SPI_returntuple
spi_rollback
in PL/Perl, Database Access from PL/Perl
SPI_rollback, SPI_rollback
SPI_rollback_and_chain, SPI_rollback
SPI_saveplan, SPI_saveplan
SPI_scroll_cursor_fetch, SPI_scroll_cursor_fetch
SPI_scroll_cursor_move, SPI_scroll_cursor_move
SPI_start_transaction, SPI_start_transaction
SPI_unregister_relation, SPI_unregister_relation
split_part, String Functions and Operators
SQL/CLI, SQL Conformance
SQL/Foundation, SQL Conformance
SQL/Framework, SQL Conformance
SQL/JRT, SQL Conformance
SQL/JSON path language, The SQL/JSON Path Language
SQL/MDA, SQL Conformance
SQL/MED, SQL Conformance
SQL/OLB, SQL Conformance
SQL/PSM, SQL Conformance
SQL/Schemata, SQL Conformance
SQL/XML, SQL Conformance
limits and conformance, XML Limits and Conformance to SQL/XML
sqrt, Mathematical Functions and Operators
ssh, Secure TCP/IP Connections with SSH Tunnels
SSI, Introduction
SSL, Secure TCP/IP Connections with SSL, SSL Support
in libpq, Connection Status Functions
with libpq, Parameter Key Words
ssl configuration parameter, SSL
sslinfo, sslinfo
ssl_ca_file configuration parameter, SSL
ssl_cert_file configuration parameter, SSL
ssl_cipher, Functions Provided
ssl_ciphers configuration parameter, SSL
ssl_client_cert_present, Functions Provided
ssl_client_dn, Functions Provided
ssl_client_dn_field, Functions Provided
ssl_client_serial, Functions Provided
ssl_crl_file configuration parameter, SSL
ssl_dh_params_file configuration parameter, SSL
ssl_ecdh_curve configuration parameter, SSL
ssl_extension_info, Functions Provided
ssl_issuer_dn, Functions Provided
ssl_issuer_field, Functions Provided
ssl_is_used, Functions Provided
ssl_key_file configuration parameter, SSL
ssl_library configuration parameter, Preset Options
ssl_max_protocol_version configuration parameter, SSL
ssl_min_protocol_version configuration parameter, SSL
ssl_passphrase_command configuration parameter, SSL
ssl_passphrase_command_supports_reload configuration parameter, SSL
ssl_prefer_server_ciphers configuration parameter, SSL
ssl_version, Functions Provided
SSPI, SSPI Authentication
STABLE, Function Volatility Categories
standard deviation, Aggregate Functions
population, Aggregate Functions
sample, Aggregate Functions
standard_conforming_strings configuration parameter, Previous PostgreSQL Versions
standby server, High Availability, Load Balancing, and Replication
standby.signal, Archive Recovery, Standby Server Operation, Setting Up a Standby Server
for hot standby, Administrator's Overview
pg_basebackup --write-recovery-conf, Options
standby_mode (see standby.signal)
START TRANSACTION, START TRANSACTION
starts_with, String Functions and Operators
START_REPLICATION, Streaming Replication Protocol
statement_timeout configuration parameter, Statement Behavior
statement_timestamp, Date/Time Functions and Operators
statistics, Aggregate Functions, Statistics Used by the Planner, Extended Statistics, Updating Planner Statistics, The Statistics Collector
of the planner, Statistics Used by the Planner, Extended Statistics, Updating Planner Statistics
stats_temp_directory configuration parameter, Query and Index Statistics Collector
stddev, Aggregate Functions
stddev_pop, Aggregate Functions
stddev_samp, Aggregate Functions
STONITH, High Availability, Load Balancing, and Replication
storage parameters, Storage Parameters
Streaming Replication, High Availability, Load Balancing, and Replication
strict_word_similarity, Functions and Operators
string (see character string)
strings
backslash quotes, Previous PostgreSQL Versions
escape warning, Previous PostgreSQL Versions
standard conforming, Previous PostgreSQL Versions
string_agg, Aggregate Functions
string_to_array, Array Functions and Operators
strip, Text Search Functions and Operators, Manipulating Documents
strpos, String Functions and Operators
subarray, intarray Functions and Operators
subltree, Operators and Functions
subpath, Operators and Functions
subquery, Aggregate Functions, Scalar Subqueries, Subqueries, Subquery Expressions
subscript, Subscripts
substr, String Functions and Operators, Binary String Functions and Operators
substring, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators, SIMILAR TO Regular Expressions, POSIX Regular Expressions
subtransactions
in PL/Tcl, Explicit Subtransactions in PL/Tcl
sum, Aggregate Functions
superuser, Accessing a Database, Role Attributes
superuser_reserved_connections configuration parameter, Connection Settings
support functions
in_range, B-Tree Support Functions
suppress_redundant_updates_trigger, Trigger Functions
svals, hstore Operators and Functions
synchronize_seqscans configuration parameter, Previous PostgreSQL Versions
synchronous commit, Asynchronous Commit
Synchronous Replication, High Availability, Load Balancing, and Replication
synchronous_commit configuration parameter, Settings
synchronous_standby_names configuration parameter, Master Server
syntax, SQL Syntax
SQL, SQL Syntax
syslog_facility configuration parameter, Where to Log
syslog_ident configuration parameter, Where to Log
syslog_sequence_numbers configuration parameter, Where to Log
syslog_split_messages configuration parameter, Where to Log
system catalog, The System Catalog Schema
schema, The System Catalog Schema
systemd, PostgreSQL Features, Starting the Database Server
RemoveIPC, systemd RemoveIPC

T

table, Concepts, Table Basics, Modifying Tables
creating, Table Basics
inheritance, Inheritance
modifying, Modifying Tables
partitioning, Table Partitioning
removing, Table Basics
renaming, Renaming a Table
Table Access Method, Table Access Method Interface Definition
TABLE command, SELECT
table expression, Table Expressions
table function, Table Functions, xmltable
XMLTABLE, xmltable
table sampling method, Writing a Table Sampling Method
tableam
Table Access Method, Table Access Method Interface Definition
tablefunc, tablefunc
tableoid, System Columns
TABLESAMPLE method, Writing a Table Sampling Method
tablespace, Tablespaces
default, Statement Behavior
temporary, Statement Behavior
table_am_handler, Pseudo-Types
tan, Mathematical Functions and Operators
tand, Mathematical Functions and Operators
tanh, Mathematical Functions and Operators
target list, The Query Tree
Tcl, PL/Tcl — Tcl Procedural Language
tcn, tcn
tcp_keepalives_count configuration parameter, Connection Settings
tcp_keepalives_idle configuration parameter, Connection Settings
tcp_keepalives_interval configuration parameter, Connection Settings
tcp_user_timeout configuration parameter, Connection Settings
template0, Template Databases
template1, Creating a Database, Template Databases
temp_buffers configuration parameter, Memory
temp_file_limit configuration parameter, Disk
temp_tablespaces configuration parameter, Statement Behavior
test, Regression Tests
test_decoding, test_decoding
text, Character Types, Network Address Functions and Operators
text search, Text Search Types, Text Search Types, Full Text Search, Preferred Index Types for Text Search
data types, Text Search Types
functions and operators, Text Search Types
indexes, Preferred Index Types for Text Search
text2ltree, Operators and Functions
threads, Behavior in Threaded Programs
with libpq, Behavior in Threaded Programs
tid, Object Identifier Types
time, Date/Time Types, Times
constants, Special Values
current, Current Date/Time
output format, Date/Time Output
(see also formatting)
time span, Date/Time Types
time with time zone, Date/Time Types, Times
time without time zone, Date/Time Types, Times
time zone, Time Zones, Locale and Formatting, POSIX Time Zone Specifications
conversion, AT TIME ZONE
input abbreviations, Date/Time Configuration Files
POSIX-style specification, POSIX Time Zone Specifications
time zone data, Build Process Details
time zone names, Locale and Formatting
timelines, Backup and Restore
TIMELINE_HISTORY, Streaming Replication Protocol
timeofday, Date/Time Functions and Operators
timeout
client authentication, Authentication
deadlock, Lock Management
timestamp, Date/Time Types, Time Stamps
timestamp with time zone, Date/Time Types, Time Stamps
timestamp without time zone, Date/Time Types, Time Stamps
timestamptz, Date/Time Types
TimeZone configuration parameter, Locale and Formatting
timezone_abbreviations configuration parameter, Locale and Formatting
TOAST, TOAST
and user-defined types, TOAST Considerations
per-column storage settings, Description
per-type storage settings, Description
versus large objects, Introduction
toast_tuple_target storage parameter, Storage Parameters
token, Lexical Structure
to_ascii, String Functions and Operators
to_char, Data Type Formatting Functions
and locales, Behavior
to_date, Data Type Formatting Functions
to_hex, String Functions and Operators
to_json, Processing and Creating JSON Data
to_jsonb, Processing and Creating JSON Data
to_number, Data Type Formatting Functions
to_regclass, System Information Functions and Operators
to_regcollation, System Information Functions and Operators
to_regnamespace, System Information Functions and Operators
to_regoper, System Information Functions and Operators
to_regoperator, System Information Functions and Operators
to_regproc, System Information Functions and Operators
to_regprocedure, System Information Functions and Operators
to_regrole, System Information Functions and Operators
to_regtype, System Information Functions and Operators
to_timestamp, Data Type Formatting Functions, Date/Time Functions and Operators
to_tsquery, Text Search Functions and Operators, Parsing Queries
to_tsvector, Text Search Functions and Operators, Parsing Documents
trace_locks configuration parameter, Developer Options
trace_lock_oidmin configuration parameter, Developer Options
trace_lock_table configuration parameter, Developer Options
trace_lwlocks configuration parameter, Developer Options
trace_notify configuration parameter, Developer Options
trace_recovery_messages configuration parameter, Developer Options
trace_sort configuration parameter, Developer Options
trace_userlocks configuration parameter, Developer Options
track_activities configuration parameter, Query and Index Statistics Collector
track_activity_query_size configuration parameter, Query and Index Statistics Collector
track_commit_timestamp configuration parameter, Sending Servers
track_counts configuration parameter, Query and Index Statistics Collector
track_functions configuration parameter, Query and Index Statistics Collector
track_io_timing configuration parameter, Query and Index Statistics Collector
transaction, Transactions
transaction ID, Preventing Transaction ID Wraparound Failures
wraparound, Preventing Transaction ID Wraparound Failures
transaction isolation, Transaction Isolation
transaction isolation level, Transaction Isolation, Statement Behavior
read committed, Read Committed Isolation Level
repeatable read, Repeatable Read Isolation Level
serializable, Serializable Isolation Level
setting, SET TRANSACTION
setting default, Statement Behavior
transaction log (see WAL)
transaction_deferrable configuration parameter, Statement Behavior
transaction_isolation configuration parameter, Statement Behavior
transaction_read_only configuration parameter, Statement Behavior
transaction_timestamp, Date/Time Functions and Operators
transform_null_equals configuration parameter, Platform and Client Compatibility
transition tables, CREATE TRIGGER
(see also ephemeral named relation)
implementation in PLs, SPI_register_trigger_data
referencing from C trigger, Writing Trigger Functions in C
translate, String Functions and Operators
transparent - huge pages, Memory
trigger, Pseudo-Types, Triggers, Writing Trigger Functions in C, Rules Versus Triggers, Trigger Functions, Trigger Functions
arguments for trigger functions, Overview of Trigger Behavior
for updating a derived tsvector column, Triggers for Automatic Updates
in C, Writing Trigger Functions in C
in PL/pgSQL, Trigger Functions
in PL/Python, Trigger Functions
in PL/Tcl, Trigger Functions in PL/Tcl
compared with rules, Rules Versus Triggers
triggered_change_notification, tcn
trigger_file (see promote_trigger_file)
trim, String Functions and Operators, Binary String Functions and Operators
trim_scale, Mathematical Functions and Operators
true, Boolean Type
trunc, Mathematical Functions and Operators, Network Address Functions and Operators
TRUNCATE, TRUNCATE
trusted, Trusted and Untrusted PL/Perl
PL/Perl, Trusted and Untrusted PL/Perl
tsm_handler, Pseudo-Types
tsm_system_rows, tsm_system_rows
tsm_system_time, tsm_system_time
tsquery (data type), tsquery
tsquery_phrase, Text Search Functions and Operators, Manipulating Queries
tsvector (data type), tsvector
tsvector concatenation, Manipulating Documents
tsvector_to_array, Text Search Functions and Operators
tsvector_update_trigger, Trigger Functions
tsvector_update_trigger_column, Trigger Functions
ts_debug, Text Search Functions and Operators, Configuration Testing
ts_delete, Text Search Functions and Operators
ts_filter, Text Search Functions and Operators
ts_headline, Text Search Functions and Operators, Highlighting Results
ts_lexize, Text Search Functions and Operators, Dictionary Testing
ts_parse, Text Search Functions and Operators, Parser Testing
ts_rank, Text Search Functions and Operators, Ranking Search Results
ts_rank_cd, Text Search Functions and Operators, Ranking Search Results
ts_rewrite, Text Search Functions and Operators, Query Rewriting
ts_stat, Text Search Functions and Operators, Gathering Document Statistics
ts_token_type, Text Search Functions and Operators, Parser Testing
tuple_data_split, Heap Functions
txid_current, System Information Functions and Operators
txid_current_if_assigned, System Information Functions and Operators
txid_current_snapshot, System Information Functions and Operators
txid_snapshot_xip, System Information Functions and Operators
txid_snapshot_xmax, System Information Functions and Operators
txid_snapshot_xmin, System Information Functions and Operators
txid_status, System Information Functions and Operators
txid_visible_in_snapshot, System Information Functions and Operators
type (see data type)
type cast, Numeric Constants, Type Casts

U

UESCAPE, Identifiers and Key Words, String Constants with Unicode Escapes
unaccent, unaccent, Functions
Unicode escape, String Constants with Unicode Escapes
in identifiers, Identifiers and Key Words
in string constants, String Constants with Unicode Escapes
Unicode normalization, String Functions and Operators
UNION, Combining Queries, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
uniq, intarray Functions and Operators
unique constraint, Unique Constraints
Unix domain socket, Parameter Key Words
unix_socket_directories configuration parameter, Connection Settings
unix_socket_group configuration parameter, Connection Settings
unix_socket_permissions configuration parameter, Connection Settings
unknown, Pseudo-Types
UNLISTEN, UNLISTEN
unnest, Array Functions and Operators
for tsvector, Text Search Functions and Operators
unqualified name, The Schema Search Path
updatable views, Updatable Views
UPDATE, Updates, Updating Data, Returning Data from Modified Rows, UPDATE
RETURNING, Returning Data from Modified Rows
update_process_title configuration parameter, Process Title
updating, Updating Data
upgrading, Upgrading a PostgreSQL Cluster
upper, String Functions and Operators, Range Functions and Operators
and locales, Behavior
upper_inc, Range Functions and Operators
upper_inf, Range Functions and Operators
UPSERT, INSERT
URI, Connection Strings
user, System Information Functions and Operators, Database Roles
current, System Information Functions and Operators
user mapping, Foreign Data
User name maps, User Name Maps
user_catalog_table storage parameter, Storage Parameters
UUID, UUID Type, UUID Type, PostgreSQL Features
generating, UUID Type
uuid-ossp, uuid-ossp
uuid_generate_v1, uuid-ossp Functions
uuid_generate_v1mc, uuid-ossp Functions
uuid_generate_v3, uuid-ossp Functions

V

vacuum, Routine Vacuuming
VACUUM, VACUUM
vacuumdb, vacuumdb
vacuumlo, vacuumlo
vacuum_cost_delay configuration parameter, Cost-based Vacuum Delay
vacuum_cost_limit configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_dirty configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_hit configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_miss configuration parameter, Cost-based Vacuum Delay
vacuum_defer_cleanup_age configuration parameter, Master Server
vacuum_freeze_min_age configuration parameter, Statement Behavior
vacuum_freeze_table_age configuration parameter, Statement Behavior
vacuum_index_cleanup storage parameter, Storage Parameters
vacuum_multixact_freeze_min_age configuration parameter, Statement Behavior
vacuum_multixact_freeze_table_age configuration parameter, Statement Behavior
vacuum_truncate storage parameter, Storage Parameters
value expression, Value Expressions
VALUES, VALUES Lists, UNION, CASE, and Related Constructs, VALUES
determination of result type, UNION, CASE, and Related Constructs
varchar, Character Types
variadic function, SQL Functions with Variable Numbers of Arguments
variance, Aggregate Functions
population, Aggregate Functions
sample, Aggregate Functions
var_pop, Aggregate Functions
var_samp, Aggregate Functions
version, Accessing a Database, System Information Functions and Operators, Upgrading a PostgreSQL Cluster
compatibility, Upgrading a PostgreSQL Cluster
view, Views, Views and the Rule System, Materialized Views, Cooperation with Views
implementation through rules, Views and the Rule System
materialized, Materialized Views
updating, Cooperation with Views
Visibility Map, Visibility Map
VM (see Visibility Map)
void, Pseudo-Types
VOLATILE, Function Volatility Categories
volatility, Function Volatility Categories
functions, Function Volatility Categories
VPATH, Installation Procedure, Extension Building Infrastructure

W

WAL, Reliability and the Write-Ahead Log
wal_block_size configuration parameter, Preset Options
wal_buffers configuration parameter, Settings
wal_compression configuration parameter, Settings
wal_consistency_checking configuration parameter, Developer Options
wal_debug configuration parameter, Developer Options
wal_init_zero configuration parameter, Settings
wal_keep_size configuration parameter, Sending Servers
wal_level configuration parameter, Settings
wal_log_hints configuration parameter, Settings
wal_receiver_create_temp_slot configuration parameter, Standby Servers
wal_receiver_status_interval configuration parameter, Standby Servers
wal_receiver_timeout configuration parameter, Standby Servers
wal_recycle configuration parameter, Settings
wal_retrieve_retry_interval configuration parameter, Standby Servers
wal_segment_size configuration parameter, Preset Options
wal_sender_timeout configuration parameter, Sending Servers
wal_skip_threshold configuration parameter, Settings
wal_sync_method configuration parameter, Settings
wal_writer_delay configuration parameter, Settings
wal_writer_flush_after configuration parameter, Settings
warm standby, High Availability, Load Balancing, and Replication
websearch_to_tsquery, Text Search Functions and Operators
WHERE, The WHERE Clause
where to log, Where to Log
WHILE
in PL/pgSQL, WHILE
width, Geometric Functions and Operators
width_bucket, Mathematical Functions and Operators
window function, Window Functions, Window Function Calls, Window Function Processing, Window Functions
built-in, Window Functions
invocation, Window Function Calls
order of execution, Window Function Processing
WITH, WITH Queries (Common Table Expressions), SELECT
in SELECT, WITH Queries (Common Table Expressions), SELECT
WITH CHECK OPTION, CREATE VIEW
WITHIN GROUP, Aggregate Expressions
witness server, High Availability, Load Balancing, and Replication
word_similarity, Functions and Operators
work_mem configuration parameter, Memory
wraparound
of multixact IDs, Multixacts and Wraparound
of transaction IDs, Preventing Transaction ID Wraparound Failures

X

xid, Object Identifier Types
xid8, Object Identifier Types
xmax, System Columns
xmin, System Columns
XML, XML Type
XML export, Mapping Tables to XML
XML Functions, XML Functions
XML option, Creating XML Values, Statement Behavior
xml2, xml2
xmlagg, xmlagg, Aggregate Functions
xmlbinary configuration parameter, Statement Behavior
xmlcomment, xmlcomment
xmlconcat, xmlconcat
xmlelement, xmlelement
XMLEXISTS, XMLEXISTS
xmlforest, xmlforest
xmloption configuration parameter, Statement Behavior
xmlparse, Creating XML Values
xmlpi, xmlpi
xmlroot, xmlroot
xmlserialize, Creating XML Values
xmltable, xmltable
xml_is_well_formed, xml_is_well_formed
xml_is_well_formed_content, xml_is_well_formed
xml_is_well_formed_document, xml_is_well_formed
XPath, xpath
xpath_exists, xpath_exists
xpath_table, xpath_table
XQuery regular expressions, Differences from XQuery (LIKE_REGEX)
xslt_process, xslt_process

Z

zero_damaged_pages configuration parameter, Developer Options
zlib, Requirements, Anti-Features
Prev Up 
Bibliography Home 
\ No newline at end of file + libpq, Building libpq Programs
PL/Perl, PL/Perl — Perl Procedural Language
PL/PerlU, Trusted and Untrusted PL/Perl
PL/pgSQL, PL/pgSQL — SQL Procedural Language
PL/Python, PL/Python — Python Procedural Language
PL/SQL (Oracle), Porting from Oracle PL/SQL
porting to PL/pgSQL, Porting from Oracle PL/SQL
PL/Tcl, PL/Tcl — Tcl Procedural Language
plainto_tsquery, Text Search Functions and Operators, Parsing Queries
plan_cache_mode configuration parameter, Other Planner Options
plperl.on_init configuration parameter, Configuration
plperl.on_plperlu_init configuration parameter, Configuration
plperl.on_plperl_init configuration parameter, Configuration
plperl.use_strict configuration parameter, Configuration
plpgsql.check_asserts configuration parameter, Checking Assertions
plpgsql.variable_conflict configuration parameter, Variable Substitution
pltcl.start_proc configuration parameter, PL/Tcl Configuration
pltclu.start_proc configuration parameter, PL/Tcl Configuration
point, Points, Geometric Functions and Operators
point-in-time recovery, Backup and Restore
policy, Row Security Policies
polygon, Polygons, Geometric Functions and Operators
polymorphic function, Polymorphic Types
polymorphic type, Polymorphic Types
popen, Geometric Functions and Operators
populate_record, hstore Operators and Functions
port, Parameter Key Words
port configuration parameter, Connection Settings
position, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators
POSTGRES, The Berkeley POSTGRES Project
postgres, Architectural Fundamentals, Starting the Database Server, Creating a Database, postgres
postgres user, The PostgreSQL User Account
Postgres95, Postgres95
postgresql.auto.conf, Parameter Interaction via the Configuration File
postgresql.conf, Parameter Interaction via the Configuration File
postgres_fdw, postgres_fdw
postmaster, postmaster
post_auth_delay configuration parameter, Developer Options
power, Mathematical Functions and Operators
PQbackendPID, Connection Status Functions
PQbinaryTuples, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQcancel, Canceling Queries in Progress
PQclear, Main Functions
PQclientEncoding, Control Functions
PQcmdStatus, Retrieving Other Result Information
PQcmdTuples, Retrieving Other Result Information
PQconndefaults, Database Connection Control Functions
PQconnectdb, Database Connection Control Functions
PQconnectdbParams, Database Connection Control Functions
PQconnectionNeedsPassword, Connection Status Functions
PQconnectionUsedPassword, Connection Status Functions
PQconnectPoll, Database Connection Control Functions
PQconnectStart, Database Connection Control Functions
PQconnectStartParams, Database Connection Control Functions
PQconninfo, Database Connection Control Functions
PQconninfoFree, Miscellaneous Functions
PQconninfoParse, Database Connection Control Functions
PQconsumeInput, Asynchronous Command Processing
PQcopyResult, Miscellaneous Functions
PQdb, Connection Status Functions
PQdescribePortal, Main Functions
PQdescribePrepared, Main Functions
PQencryptPassword, Miscellaneous Functions
PQencryptPasswordConn, Miscellaneous Functions
PQendcopy, Obsolete Functions for COPY
PQerrorMessage, Connection Status Functions
PQescapeBytea, Escaping Strings for Inclusion in SQL Commands
PQescapeByteaConn, Escaping Strings for Inclusion in SQL Commands
PQescapeIdentifier, Escaping Strings for Inclusion in SQL Commands
PQescapeLiteral, Escaping Strings for Inclusion in SQL Commands
PQescapeString, Escaping Strings for Inclusion in SQL Commands
PQescapeStringConn, Escaping Strings for Inclusion in SQL Commands
PQexec, Main Functions
PQexecParams, Main Functions
PQexecPrepared, Main Functions
PQfformat, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQfinish, Database Connection Control Functions
PQfireResultCreateEvents, Miscellaneous Functions
PQflush, Asynchronous Command Processing
PQfmod, Retrieving Query Result Information
PQfn, The Fast-Path Interface
PQfname, Retrieving Query Result Information
PQfnumber, Retrieving Query Result Information
PQfreeCancel, Canceling Queries in Progress
PQfreemem, Miscellaneous Functions
PQfsize, Retrieving Query Result Information
PQftable, Retrieving Query Result Information
PQftablecol, Retrieving Query Result Information
PQftype, Retrieving Query Result Information
PQgetCancel, Canceling Queries in Progress
PQgetCopyData, Functions for Receiving COPY Data
PQgetisnull, Retrieving Query Result Information
PQgetlength, Retrieving Query Result Information
PQgetline, Obsolete Functions for COPY
PQgetlineAsync, Obsolete Functions for COPY
PQgetResult, Asynchronous Command Processing
PQgetssl, Connection Status Functions
PQgetSSLKeyPassHook_OpenSSL, Database Connection Control Functions
PQgetvalue, Retrieving Query Result Information
PQhost, Connection Status Functions
PQhostaddr, Connection Status Functions
PQinitOpenSSL, SSL Library Initialization
PQinitSSL, SSL Library Initialization
PQinstanceData, Event Support Functions
PQisBusy, Asynchronous Command Processing
PQisnonblocking, Asynchronous Command Processing
PQisthreadsafe, Behavior in Threaded Programs
PQlibVersion, Miscellaneous Functions
(see also PQserverVersion)
PQmakeEmptyPGresult, Miscellaneous Functions
PQnfields, Retrieving Query Result Information
with COPY, Functions Associated with the COPY Command
PQnotifies, Asynchronous Notification
PQnparams, Retrieving Query Result Information
PQntuples, Retrieving Query Result Information
PQoidStatus, Retrieving Other Result Information
PQoidValue, Retrieving Other Result Information
PQoptions, Connection Status Functions
PQparameterStatus, Connection Status Functions
PQparamtype, Retrieving Query Result Information
PQpass, Connection Status Functions
PQping, Database Connection Control Functions
PQpingParams, Database Connection Control Functions
PQport, Connection Status Functions
PQprepare, Main Functions
PQprint, Retrieving Query Result Information
PQprotocolVersion, Connection Status Functions
PQputCopyData, Functions for Sending COPY Data
PQputCopyEnd, Functions for Sending COPY Data
PQputline, Obsolete Functions for COPY
PQputnbytes, Obsolete Functions for COPY
PQregisterEventProc, Event Support Functions
PQrequestCancel, Canceling Queries in Progress
PQreset, Database Connection Control Functions
PQresetPoll, Database Connection Control Functions
PQresetStart, Database Connection Control Functions
PQresStatus, Main Functions
PQresultAlloc, Miscellaneous Functions
PQresultErrorField, Main Functions
PQresultErrorMessage, Main Functions
PQresultInstanceData, Event Support Functions
PQresultMemorySize, Miscellaneous Functions
PQresultSetInstanceData, Event Support Functions
PQresultStatus, Main Functions
PQresultVerboseErrorMessage, Main Functions
PQsendDescribePortal, Asynchronous Command Processing
PQsendDescribePrepared, Asynchronous Command Processing
PQsendPrepare, Asynchronous Command Processing
PQsendQuery, Asynchronous Command Processing
PQsendQueryParams, Asynchronous Command Processing
PQsendQueryPrepared, Asynchronous Command Processing
PQserverVersion, Connection Status Functions
PQsetClientEncoding, Control Functions
PQsetdb, Database Connection Control Functions
PQsetdbLogin, Database Connection Control Functions
PQsetErrorContextVisibility, Control Functions
PQsetErrorVerbosity, Control Functions
PQsetInstanceData, Event Support Functions
PQsetnonblocking, Asynchronous Command Processing
PQsetNoticeProcessor, Notice Processing
PQsetNoticeReceiver, Notice Processing
PQsetResultAttrs, Miscellaneous Functions
PQsetSingleRowMode, Retrieving Query Results Row-by-Row
PQsetSSLKeyPassHook_OpenSSL, Database Connection Control Functions
PQsetvalue, Miscellaneous Functions
PQsocket, Connection Status Functions
PQsslAttribute, Connection Status Functions
PQsslAttributeNames, Connection Status Functions
PQsslInUse, Connection Status Functions
PQsslStruct, Connection Status Functions
PQstatus, Connection Status Functions
PQtrace, Control Functions
PQtransactionStatus, Connection Status Functions
PQtty, Connection Status Functions
PQunescapeBytea, Escaping Strings for Inclusion in SQL Commands
PQuntrace, Control Functions
PQuser, Connection Status Functions
predicate locking, Serializable Isolation Level
PREPARE, PREPARE
PREPARE TRANSACTION, PREPARE TRANSACTION
prepared statements, DEALLOCATE, EXECUTE, EXPLAIN, PREPARE
creating, PREPARE
executing, EXECUTE
removing, DEALLOCATE
showing the query plan, EXPLAIN
preparing a query
in PL/pgSQL, Plan Caching
in PL/Python, Database Access Functions
in PL/Tcl, Database Access from PL/Tcl
pre_auth_delay configuration parameter, Developer Options
primary key, Primary Keys
primary_conninfo configuration parameter, Standby Servers
primary_slot_name configuration parameter, Standby Servers
privilege, Privileges, Schemas and Privileges, Rules and Privileges, Rules and Privileges
querying, System Information Functions and Operators
with rules, Rules and Privileges
for schemas, Schemas and Privileges
with views, Rules and Privileges
procedural language, Procedural Languages, Writing a Procedural Language Handler
externally maintained, Procedural Languages
handler for, Writing a Procedural Language Handler
procedure, User-Defined Procedures
user-defined, User-Defined Procedures
promote_trigger_file configuration parameter, Standby Servers
protocol, Frontend/Backend Protocol
frontend-backend, Frontend/Backend Protocol
ps, Standard Unix Tools
to monitor activity, Standard Unix Tools
psql, Accessing a Database, psql
Python, PL/Python — Python Procedural Language

R

radians, Mathematical Functions and Operators
radius, Geometric Functions and Operators
RADIUS, RADIUS Authentication
RAISE
in PL/pgSQL, Reporting Errors and Messages
random, Mathematical Functions and Operators
random_page_cost configuration parameter, Planner Cost Constants
range table, The Query Tree
range type, Range Types
exclude, Constraints on Ranges
indexes on, Indexing
range_merge, Range Functions and Operators
rank, Window Functions
hypothetical, Aggregate Functions
read committed, Read Committed Isolation Level
read-only transaction, Statement Behavior
setting, SET TRANSACTION
setting default, Statement Behavior
readline, Requirements
real, Floating-Point Types
REASSIGN OWNED, REASSIGN OWNED
record, Pseudo-Types
recovery.conf, recovery.conf file merged into postgresql.conf
recovery.signal, Archive Recovery
recovery_end_command configuration parameter, Archive Recovery
recovery_min_apply_delay configuration parameter, Standby Servers
recovery_target configuration parameter, Recovery Target
recovery_target_action configuration parameter, Recovery Target
recovery_target_inclusive configuration parameter, Recovery Target
recovery_target_lsn configuration parameter, Recovery Target
recovery_target_name configuration parameter, Recovery Target
recovery_target_time configuration parameter, Recovery Target
recovery_target_timeline configuration parameter, Recovery Target
recovery_target_xid configuration parameter, Recovery Target
rectangle, Boxes
RECURSIVE, CREATE VIEW
in common table expressions, SELECT in WITH
in views, CREATE VIEW
referential integrity, Foreign Keys, Foreign Keys
REFRESH MATERIALIZED VIEW, REFRESH MATERIALIZED VIEW
regclass, Object Identifier Types
regcollation, Object Identifier Types
regconfig, Object Identifier Types
regdictionary, Object Identifier Types
regexp_match, String Functions and Operators, POSIX Regular Expressions
regexp_matches, String Functions and Operators, POSIX Regular Expressions
regexp_replace, String Functions and Operators, POSIX Regular Expressions
regexp_split_to_array, String Functions and Operators, POSIX Regular Expressions
regexp_split_to_table, String Functions and Operators, POSIX Regular Expressions
regnamespace, Object Identifier Types
regoper, Object Identifier Types
regoperator, Object Identifier Types
regproc, Object Identifier Types
regprocedure, Object Identifier Types
regression intercept, Aggregate Functions
regression slope, Aggregate Functions
regression test, Installation Procedure
regression tests, Regression Tests
regrole, Object Identifier Types
regr_avgx, Aggregate Functions
regr_avgy, Aggregate Functions
regr_count, Aggregate Functions
regr_intercept, Aggregate Functions
regr_r2, Aggregate Functions
regr_slope, Aggregate Functions
regr_sxx, Aggregate Functions
regr_sxy, Aggregate Functions
regr_syy, Aggregate Functions
regtype, Object Identifier Types
regular expression, SIMILAR TO Regular Expressions, POSIX Regular Expressions
(see also pattern matching)
regular expressions
and locales, Behavior
reindex, Routine Reindexing
REINDEX, REINDEX
reindexdb, reindexdb
relation, Concepts
relational database, Concepts
RELEASE SAVEPOINT, RELEASE SAVEPOINT
repeat, String Functions and Operators
repeatable read, Repeatable Read Isolation Level
replace, String Functions and Operators
replication, High Availability, Load Balancing, and Replication
Replication Origins, Replication Progress Tracking
Replication Progress Tracking, Replication Progress Tracking
replication slot
logical replication, Replication Slots
streaming replication, Replication Slots
reporting errors
in PL/pgSQL, Reporting Errors and Messages
RESET, RESET
restartpoint, WAL Configuration
restart_after_crash configuration parameter, Error Handling
restore_command configuration parameter, Archive Recovery
RESTRICT, Dependency Tracking
with DROP, Dependency Tracking
foreign key action, Foreign Keys
RETURN NEXT
in PL/pgSQL, RETURN NEXT and RETURN QUERY
RETURN QUERY
in PL/pgSQL, RETURN NEXT and RETURN QUERY
RETURNING, Returning Data from Modified Rows
RETURNING INTO, Executing a Query with a Single-Row Result
in PL/pgSQL, Executing a Query with a Single-Row Result
reverse, String Functions and Operators
REVOKE, Privileges, REVOKE
right, String Functions and Operators
right join, Joined Tables
role, Database Roles, Role Membership, Default Roles
applicable, applicable_roles
enabled, enabled_roles
membership in, Role Membership
privilege to bypass, Role Attributes
privilege to create, Role Attributes
privilege to inherit, Role Attributes
privilege to initiate replication, Role Attributes
privilege to limit connection, Role Attributes
ROLLBACK, ROLLBACK
rollback
psql, Variables
ROLLBACK PREPARED, ROLLBACK PREPARED
ROLLBACK TO SAVEPOINT, ROLLBACK TO SAVEPOINT
ROLLUP, GROUPING SETS, CUBE, and ROLLUP
round, Mathematical Functions and Operators
routine, User-Defined Procedures
routine maintenance, Routine Database Maintenance Tasks
row, Concepts, Table Basics
ROW, Row Constructors
row estimation, Row Estimation Examples
multivariate, Multivariate Statistics Examples
planner, Row Estimation Examples
row type, Composite Types
constructor, Row Constructors
row-level security, Row Security Policies
row-wise comparison, Row and Array Comparisons
row_number, Window Functions
row_security configuration parameter, Statement Behavior
row_security_active, System Information Functions and Operators
row_to_json, Processing and Creating JSON Data
rpad, String Functions and Operators
rtrim, String Functions and Operators
rule, The Rule System, Views and the Rule System, How SELECT Rules Work, Materialized Views, Rules on INSERT, UPDATE, and DELETE, Rules on INSERT, UPDATE, and DELETE, Rules on INSERT, UPDATE, and DELETE, Rules Versus Triggers
and materialized views, Materialized Views
and views, Views and the Rule System
for DELETE, Rules on INSERT, UPDATE, and DELETE
for INSERT, Rules on INSERT, UPDATE, and DELETE
for SELECT, How SELECT Rules Work
compared with triggers, Rules Versus Triggers
for UPDATE, Rules on INSERT, UPDATE, and DELETE

S

SAVEPOINT, SAVEPOINT
savepoints, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT, SAVEPOINT
defining, SAVEPOINT
releasing, RELEASE SAVEPOINT
rolling back, ROLLBACK TO SAVEPOINT
scalar (see expression)
scale, Mathematical Functions and Operators
schema, Schemas, Creating a Schema, The Public Schema, Overview
creating, Creating a Schema
current, The Schema Search Path, System Information Functions and Operators
public, The Public Schema
removing, Creating a Schema
SCRAM, Password Authentication
search path, The Schema Search Path
current, System Information Functions and Operators
object visibility, System Information Functions and Operators
search_path configuration parameter, The Schema Search Path, Statement Behavior
use in securing functions, Writing SECURITY DEFINER Functions Safely
SECURITY LABEL, SECURITY LABEL
sec_to_gc, Cube-Based Earth Distances
seg, seg
segment_size configuration parameter, Preset Options
SELECT, Querying a Table, Queries, SELECT Output Columns, SELECT
determination of result type, SELECT Output Columns
select list, Select Lists
SELECT INTO, Executing a Query with a Single-Row Result, SELECT INTO
in PL/pgSQL, Executing a Query with a Single-Row Result
semaphores, Shared Memory and Semaphores
sepgsql, sepgsql
sepgsql.debug_audit configuration parameter, GUC Parameters
sepgsql.permissive configuration parameter, GUC Parameters
sequence, Sequence Manipulation Functions
and serial type, Serial Types
sequential scan, Planner Method Configuration
seq_page_cost configuration parameter, Planner Cost Constants
serial, Serial Types
serial2, Serial Types
serial4, Serial Types
serial8, Serial Types
serializable, Serializable Isolation Level
Serializable Snapshot Isolation, Introduction
serialization anomaly, Transaction Isolation, Serializable Isolation Level
server log, Error Reporting and Logging, Log File Maintenance
log file maintenance, Log File Maintenance
server spoofing, Preventing Server Spoofing
server_encoding configuration parameter, Preset Options
server_version configuration parameter, Preset Options
server_version_num configuration parameter, Preset Options
session_preload_libraries configuration parameter, Shared Library Preloading
session_replication_role configuration parameter, Statement Behavior
session_user, System Information Functions and Operators
SET, Configuration Settings Functions, SET
SET CONSTRAINTS, SET CONSTRAINTS
set difference, Combining Queries
set intersection, Combining Queries
set operation, Combining Queries
set returning functions, Set Returning Functions
functions, Set Returning Functions
SET ROLE, SET ROLE
SET SESSION AUTHORIZATION, SET SESSION AUTHORIZATION
SET TRANSACTION, SET TRANSACTION
set union, Combining Queries
SET XML OPTION, Statement Behavior
setseed, Mathematical Functions and Operators
setval, Sequence Manipulation Functions
setweight, Text Search Functions and Operators, Manipulating Documents
setweight for specific lexeme(s), Text Search Functions and Operators
set_bit, Binary String Functions and Operators, Bit String Functions and Operators
set_byte, Binary String Functions and Operators
set_config, Configuration Settings Functions
set_limit, Functions and Operators
set_masklen, Network Address Functions and Operators
sha224, Binary String Functions and Operators
sha256, Binary String Functions and Operators
sha384, Binary String Functions and Operators
sha512, Binary String Functions and Operators
shared library, Shared Libraries, Compiling and Linking Dynamically-Loaded Functions
shared memory, Shared Memory and Semaphores
shared_buffers configuration parameter, Memory
shared_memory_type configuration parameter, Memory
shared_preload_libraries, Shared Memory and LWLocks
shared_preload_libraries configuration parameter, Shared Library Preloading
shobj_description, System Information Functions and Operators
SHOW, Configuration Settings Functions, SHOW, Streaming Replication Protocol
show_limit, Functions and Operators
show_trgm, Functions and Operators
shutdown, Shutting Down the Server
SIGHUP, Parameter Interaction via the Configuration File, The pg_hba.conf File, User Name Maps
SIGINT, Shutting Down the Server
sign, Mathematical Functions and Operators
signal
backend processes, Server Signaling Functions
significant digits, Locale and Formatting
SIGQUIT, Shutting Down the Server
SIGTERM, Shutting Down the Server
SIMILAR TO, SIMILAR TO Regular Expressions
similarity, Functions and Operators
sin, Mathematical Functions and Operators
sind, Mathematical Functions and Operators
single-user mode, Options for Single-User Mode
sinh, Mathematical Functions and Operators
skeys, hstore Operators and Functions
sleep, Delaying Execution
slice, hstore Operators and Functions
sliced bread (see TOAST)
slope, Geometric Functions and Operators
SLRU, pg_stat_slru
smallint, Integer Types
smallserial, Serial Types
Solaris, Solaris
installation on, Solaris
shared library, Compiling and Linking Dynamically-Loaded Functions
start script, Starting the Database Server
SOME, Aggregate Functions, Subquery Expressions, Row and Array Comparisons
sort, intarray Functions and Operators
sorting, Sorting Rows
sort_asc, intarray Functions and Operators
sort_desc, intarray Functions and Operators
soundex, Soundex
SP-GiST (see index)
SPI, Server Programming Interface, spi
examples, spi
spi_commit
in PL/Perl, Database Access from PL/Perl
SPI_commit, SPI_commit
SPI_commit_and_chain, SPI_commit
SPI_connect, SPI_connect
SPI_connect_ext, SPI_connect
SPI_copytuple, SPI_copytuple
spi_cursor_close
in PL/Perl, Database Access from PL/Perl
SPI_cursor_close, SPI_cursor_close
SPI_cursor_fetch, SPI_cursor_fetch
SPI_cursor_find, SPI_cursor_find
SPI_cursor_move, SPI_cursor_move
SPI_cursor_open, SPI_cursor_open
SPI_cursor_open_with_args, SPI_cursor_open_with_args
SPI_cursor_open_with_paramlist, SPI_cursor_open_with_paramlist
SPI_exec, SPI_exec
SPI_execp, SPI_execp
SPI_execute, SPI_execute
SPI_execute_plan, SPI_execute_plan
SPI_execute_plan_with_paramlist, SPI_execute_plan_with_paramlist
SPI_execute_with_args, SPI_execute_with_args
spi_exec_prepared
in PL/Perl, Database Access from PL/Perl
spi_exec_query
in PL/Perl, Database Access from PL/Perl
spi_fetchrow
in PL/Perl, Database Access from PL/Perl
SPI_finish, SPI_finish
SPI_fname, SPI_fname
SPI_fnumber, SPI_fnumber
spi_freeplan
in PL/Perl, Database Access from PL/Perl
SPI_freeplan, SPI_freeplan
SPI_freetuple, SPI_freetuple
SPI_freetuptable, SPI_freetuptable
SPI_getargcount, SPI_getargcount
SPI_getargtypeid, SPI_getargtypeid
SPI_getbinval, SPI_getbinval
SPI_getnspname, SPI_getnspname
SPI_getrelname, SPI_getrelname
SPI_gettype, SPI_gettype
SPI_gettypeid, SPI_gettypeid
SPI_getvalue, SPI_getvalue
SPI_is_cursor_plan, SPI_is_cursor_plan
SPI_keepplan, SPI_keepplan
SPI_modifytuple, SPI_modifytuple
SPI_palloc, SPI_palloc
SPI_pfree, SPI_pfree
spi_prepare
in PL/Perl, Database Access from PL/Perl
SPI_prepare, SPI_prepare
SPI_prepare_cursor, SPI_prepare_cursor
SPI_prepare_params, SPI_prepare_params
spi_query
in PL/Perl, Database Access from PL/Perl
spi_query_prepared
in PL/Perl, Database Access from PL/Perl
SPI_register_relation, SPI_register_relation
SPI_register_trigger_data, SPI_register_trigger_data
SPI_repalloc, SPI_repalloc
SPI_result_code_string, SPI_result_code_string
SPI_returntuple, SPI_returntuple
spi_rollback
in PL/Perl, Database Access from PL/Perl
SPI_rollback, SPI_rollback
SPI_rollback_and_chain, SPI_rollback
SPI_saveplan, SPI_saveplan
SPI_scroll_cursor_fetch, SPI_scroll_cursor_fetch
SPI_scroll_cursor_move, SPI_scroll_cursor_move
SPI_start_transaction, SPI_start_transaction
SPI_unregister_relation, SPI_unregister_relation
split_part, String Functions and Operators
SQL/CLI, SQL Conformance
SQL/Foundation, SQL Conformance
SQL/Framework, SQL Conformance
SQL/JRT, SQL Conformance
SQL/JSON path language, The SQL/JSON Path Language
SQL/MDA, SQL Conformance
SQL/MED, SQL Conformance
SQL/OLB, SQL Conformance
SQL/PSM, SQL Conformance
SQL/Schemata, SQL Conformance
SQL/XML, SQL Conformance
limits and conformance, XML Limits and Conformance to SQL/XML
sqrt, Mathematical Functions and Operators
ssh, Secure TCP/IP Connections with SSH Tunnels
SSI, Introduction
SSL, Secure TCP/IP Connections with SSL, SSL Support
in libpq, Connection Status Functions
with libpq, Parameter Key Words
ssl configuration parameter, SSL
sslinfo, sslinfo
ssl_ca_file configuration parameter, SSL
ssl_cert_file configuration parameter, SSL
ssl_cipher, Functions Provided
ssl_ciphers configuration parameter, SSL
ssl_client_cert_present, Functions Provided
ssl_client_dn, Functions Provided
ssl_client_dn_field, Functions Provided
ssl_client_serial, Functions Provided
ssl_crl_file configuration parameter, SSL
ssl_dh_params_file configuration parameter, SSL
ssl_ecdh_curve configuration parameter, SSL
ssl_extension_info, Functions Provided
ssl_issuer_dn, Functions Provided
ssl_issuer_field, Functions Provided
ssl_is_used, Functions Provided
ssl_key_file configuration parameter, SSL
ssl_library configuration parameter, Preset Options
ssl_max_protocol_version configuration parameter, SSL
ssl_min_protocol_version configuration parameter, SSL
ssl_passphrase_command configuration parameter, SSL
ssl_passphrase_command_supports_reload configuration parameter, SSL
ssl_prefer_server_ciphers configuration parameter, SSL
ssl_version, Functions Provided
SSPI, SSPI Authentication
STABLE, Function Volatility Categories
standard deviation, Aggregate Functions
population, Aggregate Functions
sample, Aggregate Functions
standard_conforming_strings configuration parameter, Previous PostgreSQL Versions
standby server, High Availability, Load Balancing, and Replication
standby.signal, Archive Recovery, Standby Server Operation, Setting Up a Standby Server
for hot standby, Administrator's Overview
pg_basebackup --write-recovery-conf, Options
standby_mode (see standby.signal)
START TRANSACTION, START TRANSACTION
starts_with, String Functions and Operators
START_REPLICATION, Streaming Replication Protocol
statement_timeout configuration parameter, Statement Behavior
statement_timestamp, Date/Time Functions and Operators
statistics, Aggregate Functions, Statistics Used by the Planner, Extended Statistics, Updating Planner Statistics, The Statistics Collector
of the planner, Statistics Used by the Planner, Extended Statistics, Updating Planner Statistics
stats_temp_directory configuration parameter, Query and Index Statistics Collector
stddev, Aggregate Functions
stddev_pop, Aggregate Functions
stddev_samp, Aggregate Functions
STONITH, High Availability, Load Balancing, and Replication
storage parameters, Storage Parameters
Streaming Replication, High Availability, Load Balancing, and Replication
strict_word_similarity, Functions and Operators
string (see character string)
strings
backslash quotes, Previous PostgreSQL Versions
escape warning, Previous PostgreSQL Versions
standard conforming, Previous PostgreSQL Versions
string_agg, Aggregate Functions
string_to_array, Array Functions and Operators
strip, Text Search Functions and Operators, Manipulating Documents
strpos, String Functions and Operators
subarray, intarray Functions and Operators
subltree, Operators and Functions
subpath, Operators and Functions
subquery, Aggregate Functions, Scalar Subqueries, Subqueries, Subquery Expressions
subscript, Subscripts
substr, String Functions and Operators, Binary String Functions and Operators
substring, String Functions and Operators, Binary String Functions and Operators, Bit String Functions and Operators, SIMILAR TO Regular Expressions, POSIX Regular Expressions
subtransactions
in PL/Tcl, Explicit Subtransactions in PL/Tcl
sum, Aggregate Functions
superuser, Accessing a Database, Role Attributes
superuser_reserved_connections configuration parameter, Connection Settings
support functions
in_range, B-Tree Support Functions
suppress_redundant_updates_trigger, Trigger Functions
svals, hstore Operators and Functions
synchronize_seqscans configuration parameter, Previous PostgreSQL Versions
synchronous commit, Asynchronous Commit
Synchronous Replication, High Availability, Load Balancing, and Replication
synchronous_commit configuration parameter, Settings
synchronous_standby_names configuration parameter, Master Server
syntax, SQL Syntax
SQL, SQL Syntax
syslog_facility configuration parameter, Where to Log
syslog_ident configuration parameter, Where to Log
syslog_sequence_numbers configuration parameter, Where to Log
syslog_split_messages configuration parameter, Where to Log
system catalog, The System Catalog Schema
schema, The System Catalog Schema
systemd, PostgreSQL Features, Starting the Database Server
RemoveIPC, systemd RemoveIPC

T

table, Concepts, Table Basics, Modifying Tables
creating, Table Basics
inheritance, Inheritance
modifying, Modifying Tables
partitioning, Table Partitioning
removing, Table Basics
renaming, Renaming a Table
Table Access Method, Table Access Method Interface Definition
TABLE command, SELECT
table expression, Table Expressions
table function, Table Functions, xmltable
XMLTABLE, xmltable
table sampling method, Writing a Table Sampling Method
tableam
Table Access Method, Table Access Method Interface Definition
tablefunc, tablefunc
tableoid, System Columns
TABLESAMPLE method, Writing a Table Sampling Method
tablespace, Tablespaces
default, Statement Behavior
temporary, Statement Behavior
table_am_handler, Pseudo-Types
tan, Mathematical Functions and Operators
tand, Mathematical Functions and Operators
tanh, Mathematical Functions and Operators
target list, The Query Tree
Tcl, PL/Tcl — Tcl Procedural Language
tcn, tcn
tcp_keepalives_count configuration parameter, Connection Settings
tcp_keepalives_idle configuration parameter, Connection Settings
tcp_keepalives_interval configuration parameter, Connection Settings
tcp_user_timeout configuration parameter, Connection Settings
template0, Template Databases
template1, Creating a Database, Template Databases
temp_buffers configuration parameter, Memory
temp_file_limit configuration parameter, Disk
temp_tablespaces configuration parameter, Statement Behavior
test, Regression Tests
test_decoding, test_decoding
text, Character Types, Network Address Functions and Operators
text search, Text Search Types, Text Search Types, Full Text Search, Preferred Index Types for Text Search
data types, Text Search Types
functions and operators, Text Search Types
indexes, Preferred Index Types for Text Search
text2ltree, Operators and Functions
threads, Behavior in Threaded Programs
with libpq, Behavior in Threaded Programs
tid, Object Identifier Types
time, Date/Time Types, Times
constants, Special Values
current, Current Date/Time
output format, Date/Time Output
(see also formatting)
time span, Date/Time Types
time with time zone, Date/Time Types, Times
time without time zone, Date/Time Types, Times
time zone, Time Zones, Locale and Formatting, POSIX Time Zone Specifications
conversion, AT TIME ZONE
input abbreviations, Date/Time Configuration Files
POSIX-style specification, POSIX Time Zone Specifications
time zone data, Build Process Details
time zone names, Locale and Formatting
timelines, Backup and Restore
TIMELINE_HISTORY, Streaming Replication Protocol
timeofday, Date/Time Functions and Operators
timeout
client authentication, Authentication
deadlock, Lock Management
timestamp, Date/Time Types, Time Stamps
timestamp with time zone, Date/Time Types, Time Stamps
timestamp without time zone, Date/Time Types, Time Stamps
timestamptz, Date/Time Types
TimeZone configuration parameter, Locale and Formatting
timezone_abbreviations configuration parameter, Locale and Formatting
TOAST, TOAST
and user-defined types, TOAST Considerations
per-column storage settings, Description
per-type storage settings, Description
versus large objects, Introduction
toast_tuple_target storage parameter, Storage Parameters
token, Lexical Structure
to_ascii, String Functions and Operators
to_char, Data Type Formatting Functions
and locales, Behavior
to_date, Data Type Formatting Functions
to_hex, String Functions and Operators
to_json, Processing and Creating JSON Data
to_jsonb, Processing and Creating JSON Data
to_number, Data Type Formatting Functions
to_regclass, System Information Functions and Operators
to_regcollation, System Information Functions and Operators
to_regnamespace, System Information Functions and Operators
to_regoper, System Information Functions and Operators
to_regoperator, System Information Functions and Operators
to_regproc, System Information Functions and Operators
to_regprocedure, System Information Functions and Operators
to_regrole, System Information Functions and Operators
to_regtype, System Information Functions and Operators
to_timestamp, Data Type Formatting Functions, Date/Time Functions and Operators
to_tsquery, Text Search Functions and Operators, Parsing Queries
to_tsvector, Text Search Functions and Operators, Parsing Documents
trace_locks configuration parameter, Developer Options
trace_lock_oidmin configuration parameter, Developer Options
trace_lock_table configuration parameter, Developer Options
trace_lwlocks configuration parameter, Developer Options
trace_notify configuration parameter, Developer Options
trace_recovery_messages configuration parameter, Developer Options
trace_sort configuration parameter, Developer Options
trace_userlocks configuration parameter, Developer Options
track_activities configuration parameter, Query and Index Statistics Collector
track_activity_query_size configuration parameter, Query and Index Statistics Collector
track_commit_timestamp configuration parameter, Sending Servers
track_counts configuration parameter, Query and Index Statistics Collector
track_functions configuration parameter, Query and Index Statistics Collector
track_io_timing configuration parameter, Query and Index Statistics Collector
transaction, Transactions
transaction ID, Preventing Transaction ID Wraparound Failures
wraparound, Preventing Transaction ID Wraparound Failures
transaction isolation, Transaction Isolation
transaction isolation level, Transaction Isolation, Statement Behavior
read committed, Read Committed Isolation Level
repeatable read, Repeatable Read Isolation Level
serializable, Serializable Isolation Level
setting, SET TRANSACTION
setting default, Statement Behavior
transaction log (see WAL)
transaction_deferrable configuration parameter, Statement Behavior
transaction_isolation configuration parameter, Statement Behavior
transaction_read_only configuration parameter, Statement Behavior
transaction_timestamp, Date/Time Functions and Operators
transform_null_equals configuration parameter, Platform and Client Compatibility
transition tables, CREATE TRIGGER
(see also ephemeral named relation)
implementation in PLs, SPI_register_trigger_data
referencing from C trigger, Writing Trigger Functions in C
translate, String Functions and Operators
transparent + huge pages, Memory
trigger, Pseudo-Types, Triggers, Writing Trigger Functions in C, Rules Versus Triggers, Trigger Functions, Trigger Functions
arguments for trigger functions, Overview of Trigger Behavior
for updating a derived tsvector column, Triggers for Automatic Updates
in C, Writing Trigger Functions in C
in PL/pgSQL, Trigger Functions
in PL/Python, Trigger Functions
in PL/Tcl, Trigger Functions in PL/Tcl
compared with rules, Rules Versus Triggers
triggered_change_notification, tcn
trigger_file (see promote_trigger_file)
trim, String Functions and Operators, Binary String Functions and Operators
trim_scale, Mathematical Functions and Operators
true, Boolean Type
trunc, Mathematical Functions and Operators, Network Address Functions and Operators
TRUNCATE, TRUNCATE
trusted, Trusted and Untrusted PL/Perl
PL/Perl, Trusted and Untrusted PL/Perl
tsm_handler, Pseudo-Types
tsm_system_rows, tsm_system_rows
tsm_system_time, tsm_system_time
tsquery (data type), tsquery
tsquery_phrase, Text Search Functions and Operators, Manipulating Queries
tsvector (data type), tsvector
tsvector concatenation, Manipulating Documents
tsvector_to_array, Text Search Functions and Operators
tsvector_update_trigger, Trigger Functions
tsvector_update_trigger_column, Trigger Functions
ts_debug, Text Search Functions and Operators, Configuration Testing
ts_delete, Text Search Functions and Operators
ts_filter, Text Search Functions and Operators
ts_headline, Text Search Functions and Operators, Highlighting Results
ts_lexize, Text Search Functions and Operators, Dictionary Testing
ts_parse, Text Search Functions and Operators, Parser Testing
ts_rank, Text Search Functions and Operators, Ranking Search Results
ts_rank_cd, Text Search Functions and Operators, Ranking Search Results
ts_rewrite, Text Search Functions and Operators, Query Rewriting
ts_stat, Text Search Functions and Operators, Gathering Document Statistics
ts_token_type, Text Search Functions and Operators, Parser Testing
tuple_data_split, Heap Functions
txid_current, System Information Functions and Operators
txid_current_if_assigned, System Information Functions and Operators
txid_current_snapshot, System Information Functions and Operators
txid_snapshot_xip, System Information Functions and Operators
txid_snapshot_xmax, System Information Functions and Operators
txid_snapshot_xmin, System Information Functions and Operators
txid_status, System Information Functions and Operators
txid_visible_in_snapshot, System Information Functions and Operators
type (see data type)
type cast, Numeric Constants, Type Casts

U

UESCAPE, Identifiers and Key Words, String Constants with Unicode Escapes
unaccent, unaccent, Functions
Unicode escape, String Constants with Unicode Escapes
in identifiers, Identifiers and Key Words
in string constants, String Constants with Unicode Escapes
Unicode normalization, String Functions and Operators
UNION, Combining Queries, UNION, CASE, and Related Constructs
determination of result type, UNION, CASE, and Related Constructs
uniq, intarray Functions and Operators
unique constraint, Unique Constraints
Unix domain socket, Parameter Key Words
unix_socket_directories configuration parameter, Connection Settings
unix_socket_group configuration parameter, Connection Settings
unix_socket_permissions configuration parameter, Connection Settings
unknown, Pseudo-Types
UNLISTEN, UNLISTEN
unnest, Array Functions and Operators
for tsvector, Text Search Functions and Operators
unqualified name, The Schema Search Path
updatable views, Updatable Views
UPDATE, Updates, Updating Data, Returning Data from Modified Rows, UPDATE
RETURNING, Returning Data from Modified Rows
update_process_title configuration parameter, Process Title
updating, Updating Data
upgrading, Upgrading a PostgreSQL Cluster
upper, String Functions and Operators, Range Functions and Operators
and locales, Behavior
upper_inc, Range Functions and Operators
upper_inf, Range Functions and Operators
UPSERT, INSERT
URI, Connection Strings
user, System Information Functions and Operators, Database Roles
current, System Information Functions and Operators
user mapping, Foreign Data
User name maps, User Name Maps
user_catalog_table storage parameter, Storage Parameters
UUID, UUID Type, UUID Type, PostgreSQL Features
generating, UUID Type
uuid-ossp, uuid-ossp
uuid_generate_v1, uuid-ossp Functions
uuid_generate_v1mc, uuid-ossp Functions
uuid_generate_v3, uuid-ossp Functions

V

vacuum, Routine Vacuuming
VACUUM, VACUUM
vacuumdb, vacuumdb
vacuumlo, vacuumlo
vacuum_cost_delay configuration parameter, Cost-based Vacuum Delay
vacuum_cost_limit configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_dirty configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_hit configuration parameter, Cost-based Vacuum Delay
vacuum_cost_page_miss configuration parameter, Cost-based Vacuum Delay
vacuum_defer_cleanup_age configuration parameter, Master Server
vacuum_freeze_min_age configuration parameter, Statement Behavior
vacuum_freeze_table_age configuration parameter, Statement Behavior
vacuum_index_cleanup storage parameter, Storage Parameters
vacuum_multixact_freeze_min_age configuration parameter, Statement Behavior
vacuum_multixact_freeze_table_age configuration parameter, Statement Behavior
vacuum_truncate storage parameter, Storage Parameters
value expression, Value Expressions
VALUES, VALUES Lists, UNION, CASE, and Related Constructs, VALUES
determination of result type, UNION, CASE, and Related Constructs
varchar, Character Types
variadic function, SQL Functions with Variable Numbers of Arguments
variance, Aggregate Functions
population, Aggregate Functions
sample, Aggregate Functions
var_pop, Aggregate Functions
var_samp, Aggregate Functions
version, Accessing a Database, System Information Functions and Operators, Upgrading a PostgreSQL Cluster
compatibility, Upgrading a PostgreSQL Cluster
view, Views, Views and the Rule System, Materialized Views, Cooperation with Views
implementation through rules, Views and the Rule System
materialized, Materialized Views
updating, Cooperation with Views
Visibility Map, Visibility Map
VM (see Visibility Map)
void, Pseudo-Types
VOLATILE, Function Volatility Categories
volatility, Function Volatility Categories
functions, Function Volatility Categories
VPATH, Installation Procedure, Extension Building Infrastructure

W

WAL, Reliability and the Write-Ahead Log
wal_block_size configuration parameter, Preset Options
wal_buffers configuration parameter, Settings
wal_compression configuration parameter, Settings
wal_consistency_checking configuration parameter, Developer Options
wal_debug configuration parameter, Developer Options
wal_init_zero configuration parameter, Settings
wal_keep_size configuration parameter, Sending Servers
wal_level configuration parameter, Settings
wal_log_hints configuration parameter, Settings
wal_receiver_create_temp_slot configuration parameter, Standby Servers
wal_receiver_status_interval configuration parameter, Standby Servers
wal_receiver_timeout configuration parameter, Standby Servers
wal_recycle configuration parameter, Settings
wal_retrieve_retry_interval configuration parameter, Standby Servers
wal_segment_size configuration parameter, Preset Options
wal_sender_timeout configuration parameter, Sending Servers
wal_skip_threshold configuration parameter, Settings
wal_sync_method configuration parameter, Settings
wal_writer_delay configuration parameter, Settings
wal_writer_flush_after configuration parameter, Settings
warm standby, High Availability, Load Balancing, and Replication
websearch_to_tsquery, Text Search Functions and Operators
WHERE, The WHERE Clause
where to log, Where to Log
WHILE
in PL/pgSQL, WHILE
width, Geometric Functions and Operators
width_bucket, Mathematical Functions and Operators
window function, Window Functions, Window Function Calls, Window Function Processing, Window Functions
built-in, Window Functions
invocation, Window Function Calls
order of execution, Window Function Processing
WITH, WITH Queries (Common Table Expressions), SELECT
in SELECT, WITH Queries (Common Table Expressions), SELECT
WITH CHECK OPTION, CREATE VIEW
WITHIN GROUP, Aggregate Expressions
witness server, High Availability, Load Balancing, and Replication
word_similarity, Functions and Operators
work_mem configuration parameter, Memory
wraparound
of multixact IDs, Multixacts and Wraparound
of transaction IDs, Preventing Transaction ID Wraparound Failures

X

xid, Object Identifier Types
xid8, Object Identifier Types
xmax, System Columns
xmin, System Columns
XML, XML Type
XML export, Mapping Tables to XML
XML Functions, XML Functions
XML option, Creating XML Values, Statement Behavior
xml2, xml2
xmlagg, xmlagg, Aggregate Functions
xmlbinary configuration parameter, Statement Behavior
xmlcomment, xmlcomment
xmlconcat, xmlconcat
xmlelement, xmlelement
XMLEXISTS, XMLEXISTS
xmlforest, xmlforest
xmloption configuration parameter, Statement Behavior
xmlparse, Creating XML Values
xmlpi, xmlpi
xmlroot, xmlroot
xmlserialize, Creating XML Values
xmltable, xmltable
xml_is_well_formed, xml_is_well_formed
xml_is_well_formed_content, xml_is_well_formed
xml_is_well_formed_document, xml_is_well_formed
XPath, xpath
xpath_exists, xpath_exists
xpath_table, xpath_table
XQuery regular expressions, Differences from XQuery (LIKE_REGEX)
xslt_process, xslt_process

Z

zero_damaged_pages configuration parameter, Developer Options
zlib, Requirements, Anti-Features
Prev Up 
Bibliography Home 
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/brin-builtin-opclasses.html postgresql-13-13.12/doc/src/sgml/html/brin-builtin-opclasses.html --- postgresql-13-13.11/doc/src/sgml/html/brin-builtin-opclasses.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/brin-builtin-opclasses.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -67.2. Built-in Operator Classes
67.2. Built-in Operator Classes
Prev UpChapter 67. BRIN IndexesHome Next

67.2. Built-in Operator Classes

+67.2. Built-in Operator Classes

67.2. Built-in Operator Classes
Prev UpChapter 67. BRIN IndexesHome Next

67.2. Built-in Operator Classes

The core PostgreSQL distribution includes the BRIN operator classes shown in Table 67.1. @@ -200,4 +200,4 @@ = >= > -


Prev Up Next
67.1. Introduction Home 67.3. Extensibility
\ No newline at end of file +
Prev Up Next
67.1. Introduction Home 67.3. Extensibility
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/brin-extensibility.html postgresql-13-13.12/doc/src/sgml/html/brin-extensibility.html --- postgresql-13-13.11/doc/src/sgml/html/brin-extensibility.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/brin-extensibility.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -67.3. Extensibility
67.3. Extensibility
Prev UpChapter 67. BRIN IndexesHome Next

67.3. Extensibility

+67.3. Extensibility

67.3. Extensibility
Prev UpChapter 67. BRIN IndexesHome Next

67.3. Extensibility

The BRIN interface has a high level of abstraction, requiring the access method implementer only to implement the semantics of the data type being accessed. The BRIN layer @@ -134,4 +134,4 @@ right-hand-side argument of the supported operator. See float4_minmax_ops as an example of minmax, and box_inclusion_ops as an example of inclusion. -

Prev Up Next
67.2. Built-in Operator Classes Home Chapter 68. Hash Indexes
\ No newline at end of file +

Prev Up Next
67.2. Built-in Operator Classes Home Chapter 68. Hash Indexes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/brin-intro.html postgresql-13-13.12/doc/src/sgml/html/brin-intro.html --- postgresql-13-13.11/doc/src/sgml/html/brin-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/brin-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -67.1. Introduction
67.1. Introduction
Prev UpChapter 67. BRIN IndexesHome Next

67.1. Introduction

67.1.1. Index Maintenance

+67.1. Introduction

67.1. Introduction
Prev UpChapter 67. BRIN IndexesHome Next

67.1. Introduction

67.1.1. Index Maintenance

BRIN stands for Block Range Index. BRIN is designed for handling very large tables in which certain columns have some natural correlation with their @@ -96,4 +96,4 @@ which is useful when the index tuple is no longer a very good representation because the existing values have changed. See Section 9.27.8 for details. -

Prev Up Next
Chapter 67. BRIN Indexes Home 67.2. Built-in Operator Classes
\ No newline at end of file +

Prev Up Next
Chapter 67. BRIN Indexes Home 67.2. Built-in Operator Classes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/brin.html postgresql-13-13.12/doc/src/sgml/html/brin.html --- postgresql-13-13.11/doc/src/sgml/html/brin.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/brin.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 67. BRIN Indexes
Chapter 67. BRIN Indexes
Prev UpPart VII. InternalsHome Next
Prev Up Next
66.7. Examples Home 67.1. Introduction
\ No newline at end of file +Chapter 67. BRIN Indexes
Chapter 67. BRIN Indexes
Prev UpPart VII. InternalsHome Next
Prev Up Next
66.7. Examples Home 67.1. Introduction
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-behavior.html postgresql-13-13.12/doc/src/sgml/html/btree-behavior.html --- postgresql-13-13.11/doc/src/sgml/html/btree-behavior.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-behavior.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -63.2. Behavior of B-Tree Operator Classes
63.2. Behavior of B-Tree Operator Classes
Prev UpChapter 63. B-Tree IndexesHome Next

63.2. Behavior of B-Tree Operator Classes

+63.2. Behavior of B-Tree Operator Classes

63.2. Behavior of B-Tree Operator Classes
Prev UpChapter 63. B-Tree IndexesHome Next

63.2. Behavior of B-Tree Operator Classes

As shown in Table 37.3, a btree operator class must provide five comparison operators, <, @@ -115,4 +115,4 @@ data types. The extensions to three or more data types within a family are not strictly required by the btree index mechanism itself, but the planner relies on them for optimization purposes. -

Prev Up Next
63.1. Introduction Home 63.3. B-Tree Support Functions
\ No newline at end of file +

Prev Up Next
63.1. Introduction Home 63.3. B-Tree Support Functions
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-gin.html postgresql-13-13.12/doc/src/sgml/html/btree-gin.html --- postgresql-13-13.11/doc/src/sgml/html/btree-gin.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-gin.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.6. btree_gin
F.6. btree_gin
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.6. btree_gin

F.6.1. Example Usage
F.6.2. Authors

+F.6. btree_gin

F.6. btree_gin
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.6. btree_gin

F.6.1. Example Usage
F.6.2. Authors

btree_gin provides sample GIN operator classes that implement B-tree equivalent behavior for the data types int2, int4, int8, float4, @@ -35,4 +35,4 @@ Oleg Bartunov (). See http://www.sai.msu.su/~megera/oddmuse/index.cgi/Gin for additional information. -

Prev Up Next
F.5. bloom Home F.7. btree_gist
\ No newline at end of file +

Prev Up Next
F.5. bloom Home F.7. btree_gist
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-gist.html postgresql-13-13.12/doc/src/sgml/html/btree-gist.html --- postgresql-13-13.11/doc/src/sgml/html/btree-gist.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-gist.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.7. btree_gist
F.7. btree_gist
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.7. btree_gist

F.7.1. Example Usage
F.7.2. Authors

+F.7. btree_gist

F.7. btree_gist
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.7. btree_gist

F.7.1. Example Usage
F.7.2. Authors

btree_gist provides GiST index operator classes that implement B-tree equivalent behavior for the data types int2, int4, int8, float4, @@ -77,4 +77,4 @@ Paul Jungwirth (). See http://www.sai.msu.su/~megera/postgres/gist/ for additional information. -

Prev Up Next
F.6. btree_gin Home F.8. citext
\ No newline at end of file +

Prev Up Next
F.6. btree_gin Home F.8. citext
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-implementation.html postgresql-13-13.12/doc/src/sgml/html/btree-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/btree-implementation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-implementation.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -63.4. Implementation
63.4. Implementation
Prev UpChapter 63. B-Tree IndexesHome Next

63.4. Implementation

63.4.1. B-Tree Structure
63.4.2. Deduplication

+63.4. Implementation

63.4. Implementation
Prev UpChapter 63. B-Tree IndexesHome Next

63.4. Implementation

63.4.1. B-Tree Structure
63.4.2. Deduplication

This section covers B-Tree index implementation details that may be of use to advanced users. See src/backend/access/nbtree/README in the source @@ -167,4 +167,4 @@

  • INCLUDE indexes can never use deduplication.

-

Prev Up Next
63.3. B-Tree Support Functions Home Chapter 64. GiST Indexes
\ No newline at end of file +

Prev Up Next
63.3. B-Tree Support Functions Home Chapter 64. GiST Indexes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-intro.html postgresql-13-13.12/doc/src/sgml/html/btree-intro.html --- postgresql-13-13.11/doc/src/sgml/html/btree-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -63.1. Introduction
63.1. Introduction
Prev UpChapter 63. B-Tree IndexesHome Next

63.1. Introduction

+63.1. Introduction

63.1. Introduction
Prev UpChapter 63. B-Tree IndexesHome Next

63.1. Introduction

PostgreSQL includes an implementation of the standard btree (multi-way balanced tree) index data structure. Any data type that can be sorted into a well-defined linear @@ -14,4 +14,4 @@ some features that go beyond what would be needed just to support btree indexes, and parts of the system that are quite distant from the btree AM make use of them. -

Prev Up Next
Chapter 63. B-Tree Indexes Home 63.2. Behavior of B-Tree Operator Classes
\ No newline at end of file +

Prev Up Next
Chapter 63. B-Tree Indexes Home 63.2. Behavior of B-Tree Operator Classes
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree-support-funcs.html postgresql-13-13.12/doc/src/sgml/html/btree-support-funcs.html --- postgresql-13-13.11/doc/src/sgml/html/btree-support-funcs.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree-support-funcs.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -63.3. B-Tree Support Functions
63.3. B-Tree Support Functions
Prev UpChapter 63. B-Tree IndexesHome Next

63.3. B-Tree Support Functions

+63.3. B-Tree Support Functions

63.3. B-Tree Support Functions
Prev UpChapter 63. B-Tree IndexesHome Next

63.3. B-Tree Support Functions

As shown in Table 37.9, btree defines one required and four optional support functions. The five user-defined methods are: @@ -288,4 +288,4 @@ access method. Nevertheless, this support function was added to B-tree for uniformity, and will probably find uses during further evolution of B-tree in PostgreSQL. -

Prev Up Next
63.2. Behavior of B-Tree Operator Classes Home 63.4. Implementation
\ No newline at end of file +

Prev Up Next
63.2. Behavior of B-Tree Operator Classes Home 63.4. Implementation
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/btree.html postgresql-13-13.12/doc/src/sgml/html/btree.html --- postgresql-13-13.11/doc/src/sgml/html/btree.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/btree.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 63. B-Tree Indexes
Chapter 63. B-Tree Indexes
Prev UpPart VII. InternalsHome Next
Prev Up Next
Chapter 62. Generic WAL Records Home 63.1. Introduction
\ No newline at end of file +Chapter 63. B-Tree Indexes
Chapter 63. B-Tree Indexes
Prev UpPart VII. InternalsHome Next
Prev Up Next
Chapter 62. Generic WAL Records Home 63.1. Introduction
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/bug-reporting.html postgresql-13-13.12/doc/src/sgml/html/bug-reporting.html --- postgresql-13-13.11/doc/src/sgml/html/bug-reporting.html 2023-05-08 21:33:47.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/bug-reporting.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -5. Bug Reporting Guidelines
5. Bug Reporting Guidelines
Prev UpPrefaceHome Next

5. Bug Reporting Guidelines

5.1. Identifying Bugs
5.2. What to Report
5.3. Where to Report Bugs

+5. Bug Reporting Guidelines

5. Bug Reporting Guidelines
Prev UpPrefaceHome Next

5. Bug Reporting Guidelines

5.1. Identifying Bugs
5.2. What to Report
5.3. Where to Report Bugs

When you find a bug in PostgreSQL we want to hear about it. Your bug reports play an important part in making PostgreSQL more reliable because even the utmost @@ -154,7 +154,7 @@ subversion the package might have. If you are talking about a Git snapshot, mention that, including the commit hash.

- If your version is older than 13.11 we will almost certainly + If your version is older than 13.12 we will almost certainly tell you to upgrade. There are many bug fixes and improvements in each new release, so it is quite possible that a bug you have encountered in an older release of PostgreSQL @@ -245,4 +245,4 @@ will be some delay before the email is delivered. If you wish to subscribe to the lists, please visit https://lists.postgresql.org/ for instructions. -

Prev Up Next
4. Further Information Home Part I. Tutorial
\ No newline at end of file +

Prev Up Next
4. Further Information Home Part I. Tutorial
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-aggregate.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-aggregate.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-aggregate.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-aggregate.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.2. pg_aggregate
51.2. pg_aggregate
Prev UpChapter 51. System CatalogsHome Next

51.2. pg_aggregate

+51.2. pg_aggregate

51.2. pg_aggregate
Prev UpChapter 51. System CatalogsHome Next

51.2. pg_aggregate

The catalog pg_aggregate stores information about aggregate functions. An aggregate function is a function that operates on a set of values (typically one column from each row @@ -166,4 +166,4 @@ command. See Section 37.12 for more information about writing aggregate functions and the meaning of the transition functions, etc. -

Prev Up Next
51.1. Overview Home 51.3. pg_am
\ No newline at end of file +

Prev Up Next
51.1. Overview Home 51.3. pg_am
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-am.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-am.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-am.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-am.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.3. pg_am
51.3. pg_am
Prev UpChapter 51. System CatalogsHome Next

51.3. pg_am

+51.3. pg_am

51.3. pg_am
Prev UpChapter 51. System CatalogsHome Next

51.3. pg_am

The catalog pg_am stores information about relation access methods. There is one row for each access method supported by the system. @@ -41,4 +41,4 @@ However, pg_index_column_has_property() and related functions have been added to allow SQL queries to inspect index access method properties; see Table 9.68. -

Prev Up Next
51.2. pg_aggregate Home 51.4. pg_amop
\ No newline at end of file +

Prev Up Next
51.2. pg_aggregate Home 51.4. pg_amop
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-amop.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-amop.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-amop.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-amop.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.4. pg_amop
51.4. pg_amop
Prev UpChapter 51. System CatalogsHome Next

51.4. pg_amop

+51.4. pg_amop

51.4. pg_amop
Prev UpChapter 51. System CatalogsHome Next

51.4. pg_amop

The catalog pg_amop stores information about operators associated with access method operator families. There is one row for each operator that is a member of an operator family. A family @@ -101,4 +101,4 @@ amoplefttype and amoprighttype must match the oprleft and oprright fields of the referenced pg_operator entry. -

Prev Up Next
51.3. pg_am Home 51.5. pg_amproc
\ No newline at end of file +

Prev Up Next
51.3. pg_am Home 51.5. pg_amproc
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-amproc.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-amproc.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-amproc.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-amproc.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.5. pg_amproc
51.5. pg_amproc
Prev UpChapter 51. System CatalogsHome Next

51.5. pg_amproc

+51.5. pg_amproc

51.5. pg_amproc
Prev UpChapter 51. System CatalogsHome Next

51.5. pg_amproc

The catalog pg_amproc stores information about support functions associated with access method operator families. There is one row for each support function belonging to an operator family. @@ -52,4 +52,4 @@ an index, which are those with amproclefttype and amprocrighttype both equal to the index operator class's opcintype. -

Prev Up Next
51.4. pg_amop Home 51.6. pg_attrdef
\ No newline at end of file +

Prev Up Next
51.4. pg_amop Home 51.6. pg_attrdef
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-attrdef.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-attrdef.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-attrdef.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-attrdef.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.6. pg_attrdef
51.6. pg_attrdef
Prev UpChapter 51. System CatalogsHome Next

51.6. pg_attrdef

+51.6. pg_attrdef

51.6. pg_attrdef
Prev UpChapter 51. System CatalogsHome Next

51.6. pg_attrdef

The catalog pg_attrdef stores column default values. The main information about columns is stored in pg_attribute. @@ -34,4 +34,4 @@ The column default value, in nodeToString() representation. Use pg_get_expr(adbin, adrelid) to convert it to an SQL expression. -


Prev Up Next
51.5. pg_amproc Home 51.7. pg_attribute
\ No newline at end of file +


Prev Up Next
51.5. pg_amproc Home 51.7. pg_attribute
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-attribute.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-attribute.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-attribute.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-attribute.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.7. pg_attribute
51.7. pg_attribute
Prev UpChapter 51. System CatalogsHome Next

51.7. pg_attribute

+51.7. pg_attribute

51.7. pg_attribute
Prev UpChapter 51. System CatalogsHome Next

51.7. pg_attribute

The catalog pg_attribute stores information about table columns. There will be exactly one pg_attribute row for every column in every @@ -195,4 +195,4 @@ later dropped, and so there is no pg_type row anymore. attlen and the other fields can be used to interpret the contents of a row of the table. -

Prev Up Next
51.6. pg_attrdef Home 51.8. pg_authid
\ No newline at end of file +

Prev Up Next
51.6. pg_attrdef Home 51.8. pg_authid
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-auth-members.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-auth-members.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-auth-members.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-auth-members.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.9. pg_auth_members
51.9. pg_auth_members
Prev UpChapter 51. System CatalogsHome Next

51.9. pg_auth_members

+51.9. pg_auth_members

51.9. pg_auth_members
Prev UpChapter 51. System CatalogsHome Next

51.9. pg_auth_members

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

@@ -37,4 +37,4 @@

True if member can grant membership in roleid to others -


Prev Up Next
51.8. pg_authid Home 51.10. pg_cast
\ No newline at end of file +


Prev Up Next
51.8. pg_authid Home 51.10. pg_cast
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-authid.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-authid.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-authid.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-authid.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.8. pg_authid
51.8. pg_authid
Prev UpChapter 51. System CatalogsHome Next

51.8. pg_authid

+51.8. pg_authid

51.8. pg_authid
Prev UpChapter 51. System CatalogsHome Next

51.8. pg_authid

The catalog pg_authid contains information about database authorization identifiers (roles). A role subsumes the concepts of “users” and “groups”. A user is essentially just a @@ -110,4 +110,4 @@

A password that does not follow either of those formats is assumed to be unencrypted. -

Prev Up Next
51.7. pg_attribute Home 51.9. pg_auth_members
\ No newline at end of file +

Prev Up Next
51.7. pg_attribute Home 51.9. pg_auth_members
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-cast.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-cast.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-cast.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-cast.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.10. pg_cast
51.10. pg_cast
Prev UpChapter 51. System CatalogsHome Next

51.10. pg_cast

+51.10. pg_cast

51.10. pg_cast
Prev UpChapter 51. System CatalogsHome Next

51.10. pg_cast

The catalog pg_cast stores data type conversion paths, both built-in and user-defined.

@@ -83,4 +83,4 @@ coercion in a single step. When no such entry is available, coercion to a type that uses a type modifier involves two steps, one to convert between data types and a second to apply the modifier. -

Prev Up Next
51.9. pg_auth_members Home 51.11. pg_class
\ No newline at end of file +

Prev Up Next
51.9. pg_auth_members Home 51.11. pg_class
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-class.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-class.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-class.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-class.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.11. pg_class
51.11. pg_class
Prev UpChapter 51. System CatalogsHome Next

51.11. pg_class

+51.11. pg_class

51.11. pg_class
Prev UpChapter 51. System CatalogsHome Next

51.11. pg_class

The catalog pg_class catalogs tables and most everything else that has columns or is otherwise similar to a table. This includes indexes (but see also @@ -255,4 +255,4 @@ DROP INDEX. Instead, VACUUM clears relhasindex if it finds the table has no indexes. This arrangement avoids race conditions and improves concurrency. -

Prev Up Next
51.10. pg_cast Home 51.12. pg_collation
\ No newline at end of file +

Prev Up Next
51.10. pg_cast Home 51.12. pg_collation
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-collation.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-collation.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-collation.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-collation.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.12. pg_collation
51.12. pg_collation
Prev UpChapter 51. System CatalogsHome Next

51.12. pg_collation

+51.12. pg_collation

51.12. pg_collation
Prev UpChapter 51. System CatalogsHome Next

51.12. pg_collation

The catalog pg_collation describes the available collations, which are essentially mappings from an SQL name to operating system locale categories. @@ -85,4 +85,4 @@ collations whose encoding does not match the database encoding, since they could match the encodings of databases later cloned from template0. This would currently have to be done manually. -

Prev Up Next
51.11. pg_class Home 51.13. pg_constraint
\ No newline at end of file +

Prev Up Next
51.11. pg_class Home 51.13. pg_constraint
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-constraint.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-constraint.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-constraint.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-constraint.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.13. pg_constraint
51.13. pg_constraint
Prev UpChapter 51. System CatalogsHome Next

51.13. pg_constraint

+51.13. pg_constraint

51.13. pg_constraint
Prev UpChapter 51. System CatalogsHome Next

51.13. pg_constraint

The catalog pg_constraint stores check, primary key, unique, foreign key, and exclusion constraints on tables. (Column constraints are not treated specially. Every column constraint is @@ -194,4 +194,4 @@ pg_class.relchecks needs to agree with the number of check-constraint entries found in this table for each relation. -

Prev Up Next
51.12. pg_collation Home 51.14. pg_conversion
\ No newline at end of file +

Prev Up Next
51.12. pg_collation Home 51.14. pg_conversion
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-conversion.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-conversion.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-conversion.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-conversion.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.14. pg_conversion
51.14. pg_conversion
Prev UpChapter 51. System CatalogsHome Next

51.14. pg_conversion

+51.14. pg_conversion

51.14. pg_conversion
Prev UpChapter 51. System CatalogsHome Next

51.14. pg_conversion

The catalog pg_conversion describes encoding conversion functions. See CREATE CONVERSION for more information. @@ -51,4 +51,4 @@

True if this is the default conversion -


Prev Up Next
51.13. pg_constraint Home 51.15. pg_database
\ No newline at end of file +


Prev Up Next
51.13. pg_constraint Home 51.15. pg_database
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-database.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-database.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-database.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-database.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.15. pg_database
51.15. pg_database
Prev UpChapter 51. System CatalogsHome Next

51.15. pg_database

+51.15. pg_database

51.15. pg_database
Prev UpChapter 51. System CatalogsHome Next

51.15. pg_database

The catalog pg_database stores information about the available databases. Databases are created with the CREATE DATABASE command. Consult Chapter 22 for details about the meaning @@ -66,7 +66,8 @@

Sets maximum number of concurrent connections that can be made - to this database. -1 means no limit. + to this database. -1 means no limit, -2 indicates the database is + invalid.

datlastsysoid oid

@@ -108,4 +109,4 @@

Access privileges; see Section 5.7 for details -


Prev Up Next
51.14. pg_conversion Home 51.16. pg_db_role_setting
\ No newline at end of file +


Prev Up Next
51.14. pg_conversion Home 51.16. pg_db_role_setting
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-db-role-setting.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-db-role-setting.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-db-role-setting.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-db-role-setting.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.16. pg_db_role_setting
51.16. pg_db_role_setting
Prev UpChapter 51. System CatalogsHome Next

51.16. pg_db_role_setting

+51.16. pg_db_role_setting

51.16. pg_db_role_setting
Prev UpChapter 51. System CatalogsHome Next

51.16. pg_db_role_setting

The catalog pg_db_role_setting records the default values that have been set for run-time configuration variables, for each role and database combination. @@ -30,4 +30,4 @@

Defaults for run-time configuration variables -


Prev Up Next
51.15. pg_database Home 51.17. pg_default_acl
\ No newline at end of file +


Prev Up Next
51.15. pg_database Home 51.17. pg_default_acl
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-default-acl.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-default-acl.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-default-acl.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-default-acl.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.17. pg_default_acl
51.17. pg_default_acl
Prev UpChapter 51. System CatalogsHome Next

51.17. pg_default_acl

+51.17. pg_default_acl

51.17. pg_default_acl
Prev UpChapter 51. System CatalogsHome Next

51.17. pg_default_acl

The catalog pg_default_acl stores initial privileges to be assigned to newly created objects.

Table 51.17. pg_default_acl Columns

@@ -55,4 +55,4 @@ not whatever might be in pg_default_acl at the moment. pg_default_acl is only consulted during object creation. -

Prev Up Next
51.16. pg_db_role_setting Home 51.18. pg_depend
\ No newline at end of file +

Prev Up Next
51.16. pg_db_role_setting Home 51.18. pg_depend
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-depend.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-depend.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-depend.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-depend.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.18. pg_depend
51.18. pg_depend
Prev UpChapter 51. System CatalogsHome Next

51.18. pg_depend

+51.18. pg_depend

51.18. pg_depend
Prev UpChapter 51. System CatalogsHome Next

51.18. pg_depend

The catalog pg_depend records the dependency relationships between database objects. This information allows DROP commands to find which other objects must be dropped @@ -167,4 +167,4 @@ its condition for automatic dropping. Conversely, all the dependencies' restrictions about which objects must be dropped together must be satisfied. -

Prev Up Next
51.17. pg_default_acl Home 51.19. pg_description
\ No newline at end of file +

Prev Up Next
51.17. pg_default_acl Home 51.19. pg_description
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-description.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-description.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-description.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-description.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.19. pg_description
51.19. pg_description
Prev UpChapter 51. System CatalogsHome Next

51.19. pg_description

+51.19. pg_description

51.19. pg_description
Prev UpChapter 51. System CatalogsHome Next

51.19. pg_description

The catalog pg_description stores optional descriptions (comments) for each database object. Descriptions can be manipulated with the COMMENT command and viewed with @@ -40,4 +40,4 @@

Arbitrary text that serves as the description of this object -


Prev Up Next
51.18. pg_depend Home 51.20. pg_enum
\ No newline at end of file +


Prev Up Next
51.18. pg_depend Home 51.20. pg_enum
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-enum.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-enum.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-enum.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-enum.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.20. pg_enum
51.20. pg_enum
Prev UpChapter 51. System CatalogsHome Next

51.20. pg_enum

+51.20. pg_enum

51.20. pg_enum
Prev UpChapter 51. System CatalogsHome Next

51.20. pg_enum

The pg_enum catalog contains entries showing the values and labels for each enum type. The internal representation of a given enum value is actually the OID @@ -46,4 +46,4 @@ negative or fractional values of enumsortorder. The only requirement on these values is that they be correctly ordered and unique within each enum type. -

Prev Up Next
51.19. pg_description Home 51.21. pg_event_trigger
\ No newline at end of file +

Prev Up Next
51.19. pg_description Home 51.21. pg_event_trigger
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-event-trigger.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-event-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-event-trigger.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-event-trigger.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.21. pg_event_trigger
51.21. pg_event_trigger
Prev UpChapter 51. System CatalogsHome Next

51.21. pg_event_trigger

+51.21. pg_event_trigger

51.21. pg_event_trigger
Prev UpChapter 51. System CatalogsHome Next

51.21. pg_event_trigger

The catalog pg_event_trigger stores event triggers. See Chapter 39 for more information.

Table 51.21. pg_event_trigger Columns

@@ -50,4 +50,4 @@

Command tags for which this trigger will fire. If NULL, the firing of this trigger is not restricted on the basis of the command tag. -


Prev Up Next
51.20. pg_enum Home 51.22. pg_extension
\ No newline at end of file +


Prev Up Next
51.20. pg_enum Home 51.22. pg_extension
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-extension.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-extension.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-extension.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-extension.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.22. pg_extension
51.22. pg_extension
Prev UpChapter 51. System CatalogsHome Next

51.22. pg_extension

+51.22. pg_extension

51.22. pg_extension
Prev UpChapter 51. System CatalogsHome Next

51.22. pg_extension

The catalog pg_extension stores information about the installed extensions. See Section 37.17 for details about extensions. @@ -62,4 +62,4 @@ objects. If extrelocatable is true, then this schema must in fact contain all schema-qualifiable objects belonging to the extension. -

Prev Up Next
51.21. pg_event_trigger Home 51.23. pg_foreign_data_wrapper
\ No newline at end of file +

Prev Up Next
51.21. pg_event_trigger Home 51.23. pg_foreign_data_wrapper
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.23. pg_foreign_data_wrapper
51.23. pg_foreign_data_wrapper
Prev UpChapter 51. System CatalogsHome Next

51.23. pg_foreign_data_wrapper

+51.23. pg_foreign_data_wrapper

51.23. pg_foreign_data_wrapper
Prev UpChapter 51. System CatalogsHome Next

51.23. pg_foreign_data_wrapper

The catalog pg_foreign_data_wrapper stores foreign-data wrapper definitions. A foreign-data wrapper is the mechanism by which external data, residing on foreign servers, is @@ -53,4 +53,4 @@

Foreign-data wrapper specific options, as “keyword=value” strings -


Prev Up Next
51.22. pg_extension Home 51.24. pg_foreign_server
\ No newline at end of file +


Prev Up Next
51.22. pg_extension Home 51.24. pg_foreign_server
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-server.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-server.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-server.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-server.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.24. pg_foreign_server
51.24. pg_foreign_server
Prev UpChapter 51. System CatalogsHome Next

51.24. pg_foreign_server

+51.24. pg_foreign_server

51.24. pg_foreign_server
Prev UpChapter 51. System CatalogsHome Next

51.24. pg_foreign_server

The catalog pg_foreign_server stores foreign server definitions. A foreign server describes a source of external data, such as a remote server. Foreign @@ -51,4 +51,4 @@

Foreign server specific options, as “keyword=value” strings -


Prev Up Next
51.23. pg_foreign_data_wrapper Home 51.25. pg_foreign_table
\ No newline at end of file +


Prev Up Next
51.23. pg_foreign_data_wrapper Home 51.25. pg_foreign_table
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-table.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-table.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-foreign-table.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-foreign-table.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.25. pg_foreign_table
51.25. pg_foreign_table
Prev UpChapter 51. System CatalogsHome Next

51.25. pg_foreign_table

+51.25. pg_foreign_table

51.25. pg_foreign_table
Prev UpChapter 51. System CatalogsHome Next

51.25. pg_foreign_table

The catalog pg_foreign_table contains auxiliary information about foreign tables. A foreign table is primarily represented by a pg_class entry, @@ -28,4 +28,4 @@

Foreign table options, as “keyword=value” strings -


Prev Up Next
51.24. pg_foreign_server Home 51.26. pg_index
\ No newline at end of file +


Prev Up Next
51.24. pg_foreign_server Home 51.26. pg_index
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-index.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-index.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-index.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-index.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.26. pg_index
51.26. pg_index
Prev UpChapter 51. System CatalogsHome Next

51.26. pg_index

+51.26. pg_index

51.26. pg_index
Prev UpChapter 51. System CatalogsHome Next

51.26. pg_index

The catalog pg_index contains part of the information about indexes. The rest is mostly in pg_class. @@ -151,4 +151,4 @@ Expression tree (in nodeToString() representation) for partial index predicate. Null if not a partial index. -


Prev Up Next
51.25. pg_foreign_table Home 51.27. pg_inherits
\ No newline at end of file +


Prev Up Next
51.25. pg_foreign_table Home 51.27. pg_inherits
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-inherits.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-inherits.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-inherits.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-inherits.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.27. pg_inherits
51.27. pg_inherits
Prev UpChapter 51. System CatalogsHome Next

51.27. pg_inherits

+51.27. pg_inherits

51.27. pg_inherits
Prev UpChapter 51. System CatalogsHome Next

51.27. pg_inherits

The catalog pg_inherits records information about table and index inheritance hierarchies. There is one entry for each direct parent-child table or index relationship in the database. (Indirect @@ -32,4 +32,4 @@

Indexes cannot have multiple inheritance, since they can only inherit when using declarative partitioning. -


Prev Up Next
51.26. pg_index Home 51.28. pg_init_privs
\ No newline at end of file +


Prev Up Next
51.26. pg_index Home 51.28. pg_init_privs
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-init-privs.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-init-privs.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-init-privs.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-init-privs.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.28. pg_init_privs
51.28. pg_init_privs
Prev UpChapter 51. System CatalogsHome Next

51.28. pg_init_privs

+51.28. pg_init_privs

51.28. pg_init_privs
Prev UpChapter 51. System CatalogsHome Next

51.28. pg_init_privs

The catalog pg_init_privs records information about the initial privileges of objects in the system. There is one entry for each object in the database which has a non-default (non-NULL) @@ -58,4 +58,4 @@

The initial access privileges; see Section 5.7 for details -


Prev Up Next
51.27. pg_inherits Home 51.29. pg_language
\ No newline at end of file +


Prev Up Next
51.27. pg_inherits Home 51.29. pg_language
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-language.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-language.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-language.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-language.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.29. pg_language
51.29. pg_language
Prev UpChapter 51. System CatalogsHome Next

51.29. pg_language

+51.29. pg_language

51.29. pg_language
Prev UpChapter 51. System CatalogsHome Next

51.29. pg_language

The catalog pg_language registers languages in which you can write functions or stored procedures. See CREATE LANGUAGE @@ -73,4 +73,4 @@

Access privileges; see Section 5.7 for details -


Prev Up Next
51.28. pg_init_privs Home 51.30. pg_largeobject
\ No newline at end of file +


Prev Up Next
51.28. pg_init_privs Home 51.30. pg_largeobject
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-largeobject-metadata.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-largeobject-metadata.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.31. pg_largeobject_metadata
51.31. pg_largeobject_metadata
Prev UpChapter 51. System CatalogsHome Next

51.31. pg_largeobject_metadata

+51.31. pg_largeobject_metadata

51.31. pg_largeobject_metadata
Prev UpChapter 51. System CatalogsHome Next

51.31. pg_largeobject_metadata

The catalog pg_largeobject_metadata holds metadata associated with large objects. The actual large object data is stored in @@ -25,4 +25,4 @@

Access privileges; see Section 5.7 for details -


Prev Up Next
51.30. pg_largeobject Home 51.32. pg_namespace
\ No newline at end of file +


Prev Up Next
51.30. pg_largeobject Home 51.32. pg_namespace
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-largeobject.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-largeobject.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-largeobject.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-largeobject.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.30. pg_largeobject
51.30. pg_largeobject
Prev UpChapter 51. System CatalogsHome Next

51.30. pg_largeobject

+51.30. pg_largeobject

51.30. pg_largeobject
Prev UpChapter 51. System CatalogsHome Next

51.30. pg_largeobject

The catalog pg_largeobject holds the data making up “large objects”. A large object is identified by an OID assigned when it is created. Each large object is broken into @@ -45,4 +45,4 @@ allows sparse storage: pages might be missing, and might be shorter than LOBLKSIZE bytes even if they are not the last page of the object. Missing regions within a large object read as zeroes. -

Prev Up Next
51.29. pg_language Home 51.31. pg_largeobject_metadata
\ No newline at end of file +

Prev Up Next
51.29. pg_language Home 51.31. pg_largeobject_metadata
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-namespace.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-namespace.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-namespace.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-namespace.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.32. pg_namespace
51.32. pg_namespace
Prev UpChapter 51. System CatalogsHome Next

51.32. pg_namespace

+51.32. pg_namespace

51.32. pg_namespace
Prev UpChapter 51. System CatalogsHome Next

51.32. pg_namespace

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

Access privileges; see Section 5.7 for details -


Prev Up Next
51.31. pg_largeobject_metadata Home 51.33. pg_opclass
\ No newline at end of file +


Prev Up Next
51.31. pg_largeobject_metadata Home 51.33. pg_opclass
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-opclass.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-opclass.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-opclass.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-opclass.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.33. pg_opclass
51.33. pg_opclass
Prev UpChapter 51. System CatalogsHome Next

51.33. pg_opclass

+51.33. pg_opclass

51.33. pg_opclass
Prev UpChapter 51. System CatalogsHome Next

51.33. pg_opclass

The catalog pg_opclass defines index access method operator classes. Each operator class defines semantics for index columns of a particular data type and a particular @@ -72,4 +72,4 @@ Also, there must be no more than one pg_opclass row having opcdefault true for any given combination of opcmethod and opcintype. -

Prev Up Next
51.32. pg_namespace Home 51.34. pg_operator
\ No newline at end of file +

Prev Up Next
51.32. pg_namespace Home 51.34. pg_operator
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-operator.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-operator.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-operator.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-operator.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.34. pg_operator
51.34. pg_operator
Prev UpChapter 51. System CatalogsHome Next

51.34. pg_operator

+51.34. pg_operator

51.34. pg_operator
Prev UpChapter 51. System CatalogsHome Next

51.34. pg_operator

The catalog pg_operator stores information about operators. See CREATE OPERATOR and Section 37.14 for more information. @@ -97,4 +97,4 @@


Unused columns contain zeroes. For example, oprleft is zero for a prefix operator. -

Prev Up Next
51.33. pg_opclass Home 51.35. pg_opfamily
\ No newline at end of file +

Prev Up Next
51.33. pg_opclass Home 51.35. pg_opfamily
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-opfamily.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-opfamily.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-opfamily.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-opfamily.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.35. pg_opfamily
51.35. pg_opfamily
Prev UpChapter 51. System CatalogsHome Next

51.35. pg_opfamily

+51.35. pg_opfamily

51.35. pg_opfamily
Prev UpChapter 51. System CatalogsHome Next

51.35. pg_opfamily

The catalog pg_opfamily defines operator families. Each operator family is a collection of operators and associated support routines that implement the semantics specified for a particular @@ -50,4 +50,4 @@ pg_amproc, and pg_opclass. -

Prev Up Next
51.34. pg_operator Home 51.36. pg_partitioned_table
\ No newline at end of file +

Prev Up Next
51.34. pg_operator Home 51.36. pg_partitioned_table
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-partitioned-table.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-partitioned-table.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-partitioned-table.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-partitioned-table.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.36. pg_partitioned_table
51.36. pg_partitioned_table
Prev UpChapter 51. System CatalogsHome Next

51.36. pg_partitioned_table

+51.36. pg_partitioned_table

51.36. pg_partitioned_table
Prev UpChapter 51. System CatalogsHome Next

51.36. pg_partitioned_table

The catalog pg_partitioned_table stores information about how tables are partitioned.

Table 51.36. pg_partitioned_table Columns

@@ -68,4 +68,4 @@ references. This is a list with one element for each zero entry in partattrs. Null if all partition key columns are simple references. -


Prev Up Next
51.35. pg_opfamily Home 51.37. pg_policy
\ No newline at end of file +


Prev Up Next
51.35. pg_opfamily Home 51.37. pg_policy
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-policy.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-policy.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-policy.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-policy.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.37. pg_policy
51.37. pg_policy
Prev UpChapter 51. System CatalogsHome Next

51.37. pg_policy

+51.37. pg_policy

51.37. pg_policy
Prev UpChapter 51. System CatalogsHome Next

51.37. pg_policy

The catalog pg_policy stores row level security policies for tables. A policy includes the kind of command that it applies to (possibly all commands), the roles that it @@ -63,4 +63,4 @@ Policies stored in pg_policy are applied only when pg_class.relrowsecurity is set for their table. -

Prev Up Next
51.36. pg_partitioned_table Home 51.38. pg_proc
\ No newline at end of file +

Prev Up Next
51.36. pg_partitioned_table Home 51.38. pg_proc
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-proc.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-proc.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-proc.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-proc.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.38. pg_proc
51.38. pg_proc
Prev UpChapter 51. System CatalogsHome Next

51.38. pg_proc

+51.38. pg_proc

51.38. pg_proc
Prev UpChapter 51. System CatalogsHome Next

51.38. pg_proc

The catalog pg_proc stores information about functions, procedures, aggregate functions, and window functions (collectively also known as routines). See CREATE FUNCTION, CREATE PROCEDURE, and @@ -239,4 +239,4 @@ text. probin is unused except for dynamically-loaded C functions, for which it gives the name of the shared library file containing the function. -

Prev Up Next
51.37. pg_policy Home 51.39. pg_publication
\ No newline at end of file +

Prev Up Next
51.37. pg_policy Home 51.39. pg_publication
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-publication-rel.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-publication-rel.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-publication-rel.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-publication-rel.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.40. pg_publication_rel
51.40. pg_publication_rel
Prev UpChapter 51. System CatalogsHome Next

51.40. pg_publication_rel

+51.40. pg_publication_rel

51.40. pg_publication_rel
Prev UpChapter 51. System CatalogsHome Next

51.40. pg_publication_rel

The catalog pg_publication_rel contains the mapping between relations and publications in the database. This is a many-to-many mapping. See also Section 51.78 @@ -26,4 +26,4 @@

Reference to relation -


Prev Up Next
51.39. pg_publication Home 51.41. pg_range
\ No newline at end of file +


Prev Up Next
51.39. pg_publication Home 51.41. pg_range
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-publication.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-publication.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-publication.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-publication.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.39. pg_publication
51.39. pg_publication
Prev UpChapter 51. System CatalogsHome Next

51.39. pg_publication

+51.39. pg_publication

51.39. pg_publication
Prev UpChapter 51. System CatalogsHome Next

51.39. pg_publication

The catalog pg_publication contains all publications created in the database. For more on publications see Section 30.1. @@ -61,4 +61,4 @@ If true, operations on a leaf partition are replicated using the identity and schema of its topmost partitioned ancestor mentioned in the publication instead of its own. -


Prev Up Next
51.38. pg_proc Home 51.40. pg_publication_rel
\ No newline at end of file +


Prev Up Next
51.38. pg_proc Home 51.40. pg_publication_rel
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-range.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-range.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-range.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-range.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.41. pg_range
51.41. pg_range
Prev UpChapter 51. System CatalogsHome Next

51.41. pg_range

+51.41. pg_range

51.41. pg_range
Prev UpChapter 51. System CatalogsHome Next

51.41. pg_range

The catalog pg_range stores information about range types. This is in addition to the types' entries in pg_type. @@ -52,4 +52,4 @@ type. rngcanonical is used when the element type is discrete. rngsubdiff is optional but should be supplied to improve performance of GiST indexes on the range type. -

Prev Up Next
51.40. pg_publication_rel Home 51.42. pg_replication_origin
\ No newline at end of file +

Prev Up Next
51.40. pg_publication_rel Home 51.42. pg_replication_origin
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-replication-origin.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-replication-origin.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-replication-origin.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-replication-origin.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.42. pg_replication_origin
51.42. pg_replication_origin
Prev UpChapter 51. System CatalogsHome Next

51.42. pg_replication_origin

+51.42. pg_replication_origin

51.42. pg_replication_origin
Prev UpChapter 51. System CatalogsHome Next

51.42. pg_replication_origin

The pg_replication_origin catalog contains all replication origins created. For more on replication origins see Chapter 49. @@ -25,4 +25,4 @@

The external, user defined, name of a replication origin. -


Prev Up Next
51.41. pg_range Home 51.43. pg_rewrite
\ No newline at end of file +


Prev Up Next
51.41. pg_range Home 51.43. pg_rewrite
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-rewrite.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-rewrite.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-rewrite.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-rewrite.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.43. pg_rewrite
51.43. pg_rewrite
Prev UpChapter 51. System CatalogsHome Next

51.43. pg_rewrite

+51.43. pg_rewrite

51.43. pg_rewrite
Prev UpChapter 51. System CatalogsHome Next

51.43. pg_rewrite

The catalog pg_rewrite stores rewrite rules for tables and views.

Table 51.43. pg_rewrite Columns

Column Type @@ -61,4 +61,4 @@


Note

pg_class.relhasrules must be true if a table has any rules in this catalog. -

Prev Up Next
51.42. pg_replication_origin Home 51.44. pg_seclabel
\ No newline at end of file +

Prev Up Next
51.42. pg_replication_origin Home 51.44. pg_seclabel
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-seclabel.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-seclabel.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-seclabel.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-seclabel.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.44. pg_seclabel
51.44. pg_seclabel
Prev UpChapter 51. System CatalogsHome Next

51.44. pg_seclabel

+51.44. pg_seclabel

51.44. pg_seclabel
Prev UpChapter 51. System CatalogsHome Next

51.44. pg_seclabel

The catalog pg_seclabel stores security labels on database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier @@ -43,4 +43,4 @@

The security label applied to this object. -


Prev Up Next
51.43. pg_rewrite Home 51.45. pg_sequence
\ No newline at end of file +


Prev Up Next
51.43. pg_rewrite Home 51.45. pg_sequence
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-sequence.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-sequence.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-sequence.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-sequence.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.45. pg_sequence
51.45. pg_sequence
Prev UpChapter 51. System CatalogsHome Next

51.45. pg_sequence

+51.45. pg_sequence

51.45. pg_sequence
Prev UpChapter 51. System CatalogsHome Next

51.45. pg_sequence

The catalog pg_sequence contains information about sequences. Some of the information about sequences, such as the name and the schema, is in pg_class. @@ -50,4 +50,4 @@

Whether the sequence cycles -


Prev Up Next
51.44. pg_seclabel Home 51.46. pg_shdepend
\ No newline at end of file +


Prev Up Next
51.44. pg_seclabel Home 51.46. pg_shdepend
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shdepend.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shdepend.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shdepend.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shdepend.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.46. pg_shdepend
51.46. pg_shdepend
Prev UpChapter 51. System CatalogsHome Next

51.46. pg_shdepend

+51.46. pg_shdepend

51.46. pg_shdepend
Prev UpChapter 51. System CatalogsHome Next

51.46. pg_shdepend

The catalog pg_shdepend records the dependency relationships between database objects and shared objects, such as roles. This information allows @@ -95,4 +95,4 @@ Other dependency flavors might be needed in future. Note in particular that the current definition only supports roles and tablespaces as referenced objects. -

Prev Up Next
51.45. pg_sequence Home 51.47. pg_shdescription
\ No newline at end of file +

Prev Up Next
51.45. pg_sequence Home 51.47. pg_shdescription
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shdescription.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shdescription.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shdescription.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shdescription.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.47. pg_shdescription
51.47. pg_shdescription
Prev UpChapter 51. System CatalogsHome Next

51.47. pg_shdescription

+51.47. pg_shdescription

51.47. pg_shdescription
Prev UpChapter 51. System CatalogsHome Next

51.47. pg_shdescription

The catalog pg_shdescription stores optional descriptions (comments) for shared database objects. Descriptions can be manipulated with the COMMENT command and viewed with @@ -35,4 +35,4 @@

Arbitrary text that serves as the description of this object -


Prev Up Next
51.46. pg_shdepend Home 51.48. pg_shseclabel
\ No newline at end of file +


Prev Up Next
51.46. pg_shdepend Home 51.48. pg_shseclabel
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shseclabel.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shseclabel.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-shseclabel.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-shseclabel.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.48. pg_shseclabel
51.48. pg_shseclabel
Prev UpChapter 51. System CatalogsHome Next

51.48. pg_shseclabel

+51.48. pg_shseclabel

51.48. pg_shseclabel
Prev UpChapter 51. System CatalogsHome Next

51.48. pg_shseclabel

The catalog pg_shseclabel stores security labels on shared database objects. Security labels can be manipulated with the SECURITY LABEL command. For an easier @@ -40,4 +40,4 @@

The security label applied to this object. -


Prev Up Next
51.47. pg_shdescription Home 51.49. pg_statistic
\ No newline at end of file +


Prev Up Next
51.47. pg_shdescription Home 51.49. pg_statistic
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic-ext-data.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic-ext-data.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.51. pg_statistic_ext_data
51.51. pg_statistic_ext_data
Prev UpChapter 51. System CatalogsHome Next

51.51. pg_statistic_ext_data

+51.51. pg_statistic_ext_data

51.51. pg_statistic_ext_data
Prev UpChapter 51. System CatalogsHome Next

51.51. pg_statistic_ext_data

The catalog pg_statistic_ext_data holds data for extended planner statistics defined in pg_statistic_ext. Each row in this catalog corresponds to a statistics object @@ -44,4 +44,4 @@

MCV (most-common values) list statistics, serialized as pg_mcv_list type -


Prev Up Next
51.50. pg_statistic_ext Home 51.52. pg_subscription
\ No newline at end of file +


Prev Up Next
51.50. pg_statistic_ext Home 51.52. pg_subscription
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic-ext.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic-ext.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic-ext.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic-ext.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.50. pg_statistic_ext
51.50. pg_statistic_ext
Prev UpChapter 51. System CatalogsHome Next

51.50. pg_statistic_ext

+51.50. pg_statistic_ext

51.50. pg_statistic_ext
Prev UpChapter 51. System CatalogsHome Next

51.50. pg_statistic_ext

The catalog pg_statistic_ext holds definitions of extended planner statistics. Each row in this catalog corresponds to a statistics object @@ -76,4 +76,4 @@ and populate an entry in the pg_statistic_ext_data catalog. -

Prev Up Next
51.49. pg_statistic Home 51.51. pg_statistic_ext_data
\ No newline at end of file +

Prev Up Next
51.49. pg_statistic Home 51.51. pg_statistic_ext_data
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-statistic.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-statistic.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.49. pg_statistic
51.49. pg_statistic
Prev UpChapter 51. System CatalogsHome Next

51.49. pg_statistic

+51.49. pg_statistic

51.49. pg_statistic
Prev UpChapter 51. System CatalogsHome Next

51.49. pg_statistic

The catalog pg_statistic stores statistical data about the contents of the database. Entries are created by ANALYZE @@ -130,4 +130,4 @@ values are actually of the specific column's data type, or a related type such as an array's element type, so there is no way to define these columns' type more specifically than anyarray. -


Prev Up Next
51.48. pg_shseclabel Home 51.50. pg_statistic_ext
\ No newline at end of file +


Prev Up Next
51.48. pg_shseclabel Home 51.50. pg_statistic_ext
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-subscription-rel.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-subscription-rel.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-subscription-rel.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-subscription-rel.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.53. pg_subscription_rel
51.53. pg_subscription_rel
Prev UpChapter 51. System CatalogsHome Next

51.53. pg_subscription_rel

+51.53. pg_subscription_rel

51.53. pg_subscription_rel
Prev UpChapter 51. System CatalogsHome Next

51.53. pg_subscription_rel

The catalog pg_subscription_rel contains the state for each replicated relation in each subscription. This is a many-to-many mapping. @@ -40,4 +40,4 @@ Remote LSN of the state change used for synchronization coordination when in s or r states, otherwise null -


Prev Up Next
51.52. pg_subscription Home 51.54. pg_tablespace
\ No newline at end of file +


Prev Up Next
51.52. pg_subscription Home 51.54. pg_tablespace
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-subscription.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-subscription.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-subscription.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-subscription.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.52. pg_subscription
51.52. pg_subscription
Prev UpChapter 51. System CatalogsHome Next

51.52. pg_subscription

+51.52. pg_subscription

51.52. pg_subscription
Prev UpChapter 51. System CatalogsHome Next

51.52. pg_subscription

The catalog pg_subscription contains all existing logical replication subscriptions. For more information about logical replication see Chapter 30. @@ -68,4 +68,4 @@ Array of subscribed publication names. These reference the publications on the publisher server. For more on publications see Section 30.1. -


Prev Up Next
51.51. pg_statistic_ext_data Home 51.53. pg_subscription_rel
\ No newline at end of file +


Prev Up Next
51.51. pg_statistic_ext_data Home 51.53. pg_subscription_rel
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-tablespace.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-tablespace.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-tablespace.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-tablespace.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.54. pg_tablespace
51.54. pg_tablespace
Prev UpChapter 51. System CatalogsHome Next

51.54. pg_tablespace

+51.54. pg_tablespace

51.54. pg_tablespace
Prev UpChapter 51. System CatalogsHome Next

51.54. pg_tablespace

The catalog pg_tablespace stores information about the available tablespaces. Tables can be placed in particular tablespaces to aid administration of disk layout. @@ -39,4 +39,4 @@

Tablespace-level options, as “keyword=value” strings -


Prev Up Next
51.53. pg_subscription_rel Home 51.55. pg_transform
\ No newline at end of file +


Prev Up Next
51.53. pg_subscription_rel Home 51.55. pg_transform
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-transform.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-transform.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-transform.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-transform.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.55. pg_transform
51.55. pg_transform
Prev UpChapter 51. System CatalogsHome Next

51.55. pg_transform

+51.55. pg_transform

51.55. pg_transform
Prev UpChapter 51. System CatalogsHome Next

51.55. pg_transform

The catalog pg_transform stores information about transforms, which are a mechanism to adapt data types to procedural languages. See CREATE TRANSFORM for more information. @@ -41,4 +41,4 @@ The OID of the function to use when converting output from the procedural language (e.g., return values) to the data type. Zero is stored if this operation is not supported. -


Prev Up Next
51.54. pg_tablespace Home 51.56. pg_trigger
\ No newline at end of file +


Prev Up Next
51.54. pg_tablespace Home 51.56. pg_trigger
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-trigger.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-trigger.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-trigger.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.56. pg_trigger
51.56. pg_trigger
Prev UpChapter 51. System CatalogsHome Next

51.56. pg_trigger

+51.56. pg_trigger

51.56. pg_trigger
Prev UpChapter 51. System CatalogsHome Next

51.56. pg_trigger

The catalog pg_trigger stores triggers on tables and views. See CREATE TRIGGER @@ -142,4 +142,4 @@

Note

pg_class.relhastriggers must be true if a relation has any triggers in this catalog. -

Prev Up Next
51.55. pg_transform Home 51.57. pg_ts_config
\ No newline at end of file +

Prev Up Next
51.55. pg_transform Home 51.57. pg_ts_config
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-config-map.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-config-map.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-config-map.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-config-map.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.58. pg_ts_config_map
51.58. pg_ts_config_map
Prev UpChapter 51. System CatalogsHome Next

51.58. pg_ts_config_map

+51.58. pg_ts_config_map

51.58. pg_ts_config_map
Prev UpChapter 51. System CatalogsHome Next

51.58. pg_ts_config_map

The pg_ts_config_map catalog contains entries showing which text search dictionaries should be consulted, and in what order, for each output token type of each text search configuration's @@ -35,4 +35,4 @@

The OID of the text search dictionary to consult -


Prev Up Next
51.57. pg_ts_config Home 51.59. pg_ts_dict
\ No newline at end of file +


Prev Up Next
51.57. pg_ts_config Home 51.59. pg_ts_dict
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-config.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-config.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-config.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-config.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.57. pg_ts_config
51.57. pg_ts_config
Prev UpChapter 51. System CatalogsHome Next

51.57. pg_ts_config

+51.57. pg_ts_config

51.57. pg_ts_config
Prev UpChapter 51. System CatalogsHome Next

51.57. pg_ts_config

The pg_ts_config catalog contains entries representing text search configurations. A configuration specifies a particular text search parser and a list of dictionaries to use @@ -42,4 +42,4 @@

The OID of the text search parser for this configuration -


Prev Up Next
51.56. pg_trigger Home 51.58. pg_ts_config_map
\ No newline at end of file +


Prev Up Next
51.56. pg_trigger Home 51.58. pg_ts_config_map
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-dict.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-dict.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-dict.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-dict.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.59. pg_ts_dict
51.59. pg_ts_dict
Prev UpChapter 51. System CatalogsHome Next

51.59. pg_ts_dict

+51.59. pg_ts_dict

51.59. pg_ts_dict
Prev UpChapter 51. System CatalogsHome Next

51.59. pg_ts_dict

The pg_ts_dict catalog contains entries defining text search dictionaries. A dictionary depends on a text search template, which specifies all the implementation functions @@ -49,4 +49,4 @@

Initialization option string for the template -


Prev Up Next
51.58. pg_ts_config_map Home 51.60. pg_ts_parser
\ No newline at end of file +


Prev Up Next
51.58. pg_ts_config_map Home 51.60. pg_ts_parser
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-parser.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-parser.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-parser.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-parser.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.60. pg_ts_parser
51.60. pg_ts_parser
Prev UpChapter 51. System CatalogsHome Next

51.60. pg_ts_parser

+51.60. pg_ts_parser

51.60. pg_ts_parser
Prev UpChapter 51. System CatalogsHome Next

51.60. pg_ts_parser

The pg_ts_parser catalog contains entries defining text search parsers. A parser is responsible for splitting input text into lexemes and assigning a token type to each lexeme. @@ -59,4 +59,4 @@

OID of the parser's lextype function -


Prev Up Next
51.59. pg_ts_dict Home 51.61. pg_ts_template
\ No newline at end of file +


Prev Up Next
51.59. pg_ts_dict Home 51.61. pg_ts_template
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-template.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-template.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-ts-template.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-ts-template.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.61. pg_ts_template
51.61. pg_ts_template
Prev UpChapter 51. System CatalogsHome Next

51.61. pg_ts_template

+51.61. pg_ts_template

51.61. pg_ts_template
Prev UpChapter 51. System CatalogsHome Next

51.61. pg_ts_template

The pg_ts_template catalog contains entries defining text search templates. A template is the implementation skeleton for a class of text search dictionaries. @@ -41,4 +41,4 @@

OID of the template's lexize function -


Prev Up Next
51.60. pg_ts_parser Home 51.62. pg_type
\ No newline at end of file +


Prev Up Next
51.60. pg_ts_parser Home 51.62. pg_type
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-type.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-type.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-type.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-type.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.62. pg_type
51.62. pg_type
Prev UpChapter 51. System CatalogsHome Next

51.62. pg_type

+51.62. pg_type

51.62. pg_type
Prev UpChapter 51. System CatalogsHome Next

51.62. pg_type

The catalog pg_type stores information about data types. Base types and enum types (scalar types) are created with CREATE TYPE, and @@ -297,4 +297,4 @@ of typcategory. Any future additions to this list will also be upper-case ASCII letters. All other ASCII characters are reserved for user-defined categories. -

Table 51.63. typcategory Codes

CodeCategory
AArray types
BBoolean types
CComposite types
DDate/time types
EEnum types
GGeometric types
INetwork address types
NNumeric types
PPseudo-types
RRange types
SString types
TTimespan types
UUser-defined types
VBit-string types
Xunknown type

Prev Up Next
51.61. pg_ts_template Home 51.63. pg_user_mapping
\ No newline at end of file +

Table 51.63. typcategory Codes

CodeCategory
AArray types
BBoolean types
CComposite types
DDate/time types
EEnum types
GGeometric types
INetwork address types
NNumeric types
PPseudo-types
RRange types
SString types
TTimespan types
UUser-defined types
VBit-string types
Xunknown type

Prev Up Next
51.61. pg_ts_template Home 51.63. pg_user_mapping
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalog-pg-user-mapping.html postgresql-13-13.12/doc/src/sgml/html/catalog-pg-user-mapping.html --- postgresql-13-13.11/doc/src/sgml/html/catalog-pg-user-mapping.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalog-pg-user-mapping.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.63. pg_user_mapping
51.63. pg_user_mapping
Prev UpChapter 51. System CatalogsHome Next

51.63. pg_user_mapping

+51.63. pg_user_mapping

51.63. pg_user_mapping
Prev UpChapter 51. System CatalogsHome Next

51.63. pg_user_mapping

The catalog pg_user_mapping stores the mappings from local user to remote. Access to this catalog is restricted from normal users, use the view @@ -32,4 +32,4 @@

User mapping specific options, as “keyword=value” strings -


Prev Up Next
51.62. pg_type Home 51.64. System Views
\ No newline at end of file +


Prev Up Next
51.62. pg_type Home 51.64. System Views
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalogs-overview.html postgresql-13-13.12/doc/src/sgml/html/catalogs-overview.html --- postgresql-13-13.11/doc/src/sgml/html/catalogs-overview.html 2023-05-08 21:34:10.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalogs-overview.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -51.1. Overview
51.1. Overview
Prev UpChapter 51. System CatalogsHome Next

51.1. Overview

+51.1. Overview

51.1. Overview
Prev UpChapter 51. System CatalogsHome Next

51.1. Overview

Table 51.1 lists the system catalogs. More detailed documentation of each catalog follows below.

@@ -7,4 +7,4 @@ database creation and are thereafter database-specific. A few catalogs are physically shared across all databases in a cluster; these are noted in the descriptions of the individual catalogs. -

Table 51.1. System Catalogs

Catalog NamePurpose
pg_aggregateaggregate functions
pg_amrelation access methods
pg_amopaccess method operators
pg_amprocaccess method support functions
pg_attrdefcolumn default values
pg_attributetable columns (“attributes”)
pg_authidauthorization identifiers (roles)
pg_auth_membersauthorization identifier membership relationships
pg_castcasts (data type conversions)
pg_classtables, indexes, sequences, views (“relations”)
pg_collationcollations (locale information)
pg_constraintcheck constraints, unique constraints, primary key constraints, foreign key constraints
pg_conversionencoding conversion information
pg_databasedatabases within this database cluster
pg_db_role_settingper-role and per-database settings
pg_default_acldefault privileges for object types
pg_dependdependencies between database objects
pg_descriptiondescriptions or comments on database objects
pg_enumenum label and value definitions
pg_event_triggerevent triggers
pg_extensioninstalled extensions
pg_foreign_data_wrapperforeign-data wrapper definitions
pg_foreign_serverforeign server definitions
pg_foreign_tableadditional foreign table information
pg_indexadditional index information
pg_inheritstable inheritance hierarchy
pg_init_privsobject initial privileges
pg_languagelanguages for writing functions
pg_largeobjectdata pages for large objects
pg_largeobject_metadatametadata for large objects
pg_namespaceschemas
pg_opclassaccess method operator classes
pg_operatoroperators
pg_opfamilyaccess method operator families
pg_partitioned_tableinformation about partition key of tables
pg_policyrow-security policies
pg_procfunctions and procedures
pg_publicationpublications for logical replication
pg_publication_relrelation to publication mapping
pg_rangeinformation about range types
pg_replication_originregistered replication origins
pg_rewritequery rewrite rules
pg_seclabelsecurity labels on database objects
pg_sequenceinformation about sequences
pg_shdependdependencies on shared objects
pg_shdescriptioncomments on shared objects
pg_shseclabelsecurity labels on shared database objects
pg_statisticplanner statistics
pg_statistic_extextended planner statistics (definition)
pg_statistic_ext_dataextended planner statistics (built statistics)
pg_subscriptionlogical replication subscriptions
pg_subscription_relrelation state for subscriptions
pg_tablespacetablespaces within this database cluster
pg_transformtransforms (data type to procedural language conversions)
pg_triggertriggers
pg_ts_configtext search configurations
pg_ts_config_maptext search configurations' token mappings
pg_ts_dicttext search dictionaries
pg_ts_parsertext search parsers
pg_ts_templatetext search templates
pg_typedata types
pg_user_mappingmappings of users to foreign servers

Prev Up Next
Chapter 51. System Catalogs Home 51.2. pg_aggregate
\ No newline at end of file +

Table 51.1. System Catalogs

Catalog NamePurpose
pg_aggregateaggregate functions
pg_amrelation access methods
pg_amopaccess method operators
pg_amprocaccess method support functions
pg_attrdefcolumn default values
pg_attributetable columns (“attributes”)
pg_authidauthorization identifiers (roles)
pg_auth_membersauthorization identifier membership relationships
pg_castcasts (data type conversions)
pg_classtables, indexes, sequences, views (“relations”)
pg_collationcollations (locale information)
pg_constraintcheck constraints, unique constraints, primary key constraints, foreign key constraints
pg_conversionencoding conversion information
pg_databasedatabases within this database cluster
pg_db_role_settingper-role and per-database settings
pg_default_acldefault privileges for object types
pg_dependdependencies between database objects
pg_descriptiondescriptions or comments on database objects
pg_enumenum label and value definitions
pg_event_triggerevent triggers
pg_extensioninstalled extensions
pg_foreign_data_wrapperforeign-data wrapper definitions
pg_foreign_serverforeign server definitions
pg_foreign_tableadditional foreign table information
pg_indexadditional index information
pg_inheritstable inheritance hierarchy
pg_init_privsobject initial privileges
pg_languagelanguages for writing functions
pg_largeobjectdata pages for large objects
pg_largeobject_metadatametadata for large objects
pg_namespaceschemas
pg_opclassaccess method operator classes
pg_operatoroperators
pg_opfamilyaccess method operator families
pg_partitioned_tableinformation about partition key of tables
pg_policyrow-security policies
pg_procfunctions and procedures
pg_publicationpublications for logical replication
pg_publication_relrelation to publication mapping
pg_rangeinformation about range types
pg_replication_originregistered replication origins
pg_rewritequery rewrite rules
pg_seclabelsecurity labels on database objects
pg_sequenceinformation about sequences
pg_shdependdependencies on shared objects
pg_shdescriptioncomments on shared objects
pg_shseclabelsecurity labels on shared database objects
pg_statisticplanner statistics
pg_statistic_extextended planner statistics (definition)
pg_statistic_ext_dataextended planner statistics (built statistics)
pg_subscriptionlogical replication subscriptions
pg_subscription_relrelation state for subscriptions
pg_tablespacetablespaces within this database cluster
pg_transformtransforms (data type to procedural language conversions)
pg_triggertriggers
pg_ts_configtext search configurations
pg_ts_config_maptext search configurations' token mappings
pg_ts_dicttext search dictionaries
pg_ts_parsertext search parsers
pg_ts_templatetext search templates
pg_typedata types
pg_user_mappingmappings of users to foreign servers

Prev Up Next
Chapter 51. System Catalogs Home 51.2. pg_aggregate
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/catalogs.html postgresql-13-13.12/doc/src/sgml/html/catalogs.html --- postgresql-13-13.11/doc/src/sgml/html/catalogs.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/catalogs.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 51. System Catalogs
Chapter 51. System Catalogs
Prev UpPart VII. InternalsHome Next

Chapter 51. System Catalogs

Table of Contents

51.1. Overview
51.2. pg_aggregate
51.3. pg_am
51.4. pg_amop
51.5. pg_amproc
51.6. pg_attrdef
51.7. pg_attribute
51.8. pg_authid
51.9. pg_auth_members
51.10. pg_cast
51.11. pg_class
51.12. pg_collation
51.13. pg_constraint
51.14. pg_conversion
51.15. pg_database
51.16. pg_db_role_setting
51.17. pg_default_acl
51.18. pg_depend
51.19. pg_description
51.20. pg_enum
51.21. pg_event_trigger
51.22. pg_extension
51.23. pg_foreign_data_wrapper
51.24. pg_foreign_server
51.25. pg_foreign_table
51.26. pg_index
51.27. pg_inherits
51.28. pg_init_privs
51.29. pg_language
51.30. pg_largeobject
51.31. pg_largeobject_metadata
51.32. pg_namespace
51.33. pg_opclass
51.34. pg_operator
51.35. pg_opfamily
51.36. pg_partitioned_table
51.37. pg_policy
51.38. pg_proc
51.39. pg_publication
51.40. pg_publication_rel
51.41. pg_range
51.42. pg_replication_origin
51.43. pg_rewrite
51.44. pg_seclabel
51.45. pg_sequence
51.46. pg_shdepend
51.47. pg_shdescription
51.48. pg_shseclabel
51.49. pg_statistic
51.50. pg_statistic_ext
51.51. pg_statistic_ext_data
51.52. pg_subscription
51.53. pg_subscription_rel
51.54. pg_tablespace
51.55. pg_transform
51.56. pg_trigger
51.57. pg_ts_config
51.58. pg_ts_config_map
51.59. pg_ts_dict
51.60. pg_ts_parser
51.61. pg_ts_template
51.62. pg_type
51.63. pg_user_mapping
51.64. System Views
51.65. pg_available_extensions
51.66. pg_available_extension_versions
51.67. pg_config
51.68. pg_cursors
51.69. pg_file_settings
51.70. pg_group
51.71. pg_hba_file_rules
51.72. pg_indexes
51.73. pg_locks
51.74. pg_matviews
51.75. pg_policies
51.76. pg_prepared_statements
51.77. pg_prepared_xacts
51.78. pg_publication_tables
51.79. pg_replication_origin_status
51.80. pg_replication_slots
51.81. pg_roles
51.82. pg_rules
51.83. pg_seclabels
51.84. pg_sequences
51.85. pg_settings
51.86. pg_shadow
51.87. pg_shmem_allocations
51.88. pg_stats
51.89. pg_stats_ext
51.90. pg_tables
51.91. pg_timezone_abbrevs
51.92. pg_timezone_names
51.93. pg_user
51.94. pg_user_mappings
51.95. pg_views

+Chapter 51. System Catalogs

Chapter 51. System Catalogs
Prev UpPart VII. InternalsHome Next

Chapter 51. System Catalogs

Table of Contents

51.1. Overview
51.2. pg_aggregate
51.3. pg_am
51.4. pg_amop
51.5. pg_amproc
51.6. pg_attrdef
51.7. pg_attribute
51.8. pg_authid
51.9. pg_auth_members
51.10. pg_cast
51.11. pg_class
51.12. pg_collation
51.13. pg_constraint
51.14. pg_conversion
51.15. pg_database
51.16. pg_db_role_setting
51.17. pg_default_acl
51.18. pg_depend
51.19. pg_description
51.20. pg_enum
51.21. pg_event_trigger
51.22. pg_extension
51.23. pg_foreign_data_wrapper
51.24. pg_foreign_server
51.25. pg_foreign_table
51.26. pg_index
51.27. pg_inherits
51.28. pg_init_privs
51.29. pg_language
51.30. pg_largeobject
51.31. pg_largeobject_metadata
51.32. pg_namespace
51.33. pg_opclass
51.34. pg_operator
51.35. pg_opfamily
51.36. pg_partitioned_table
51.37. pg_policy
51.38. pg_proc
51.39. pg_publication
51.40. pg_publication_rel
51.41. pg_range
51.42. pg_replication_origin
51.43. pg_rewrite
51.44. pg_seclabel
51.45. pg_sequence
51.46. pg_shdepend
51.47. pg_shdescription
51.48. pg_shseclabel
51.49. pg_statistic
51.50. pg_statistic_ext
51.51. pg_statistic_ext_data
51.52. pg_subscription
51.53. pg_subscription_rel
51.54. pg_tablespace
51.55. pg_transform
51.56. pg_trigger
51.57. pg_ts_config
51.58. pg_ts_config_map
51.59. pg_ts_dict
51.60. pg_ts_parser
51.61. pg_ts_template
51.62. pg_type
51.63. pg_user_mapping
51.64. System Views
51.65. pg_available_extensions
51.66. pg_available_extension_versions
51.67. pg_config
51.68. pg_cursors
51.69. pg_file_settings
51.70. pg_group
51.71. pg_hba_file_rules
51.72. pg_indexes
51.73. pg_locks
51.74. pg_matviews
51.75. pg_policies
51.76. pg_prepared_statements
51.77. pg_prepared_xacts
51.78. pg_publication_tables
51.79. pg_replication_origin_status
51.80. pg_replication_slots
51.81. pg_roles
51.82. pg_rules
51.83. pg_seclabels
51.84. pg_sequences
51.85. pg_settings
51.86. pg_shadow
51.87. pg_shmem_allocations
51.88. pg_stats
51.89. pg_stats_ext
51.90. pg_tables
51.91. pg_timezone_abbrevs
51.92. pg_timezone_names
51.93. pg_user
51.94. pg_user_mappings
51.95. pg_views

The system catalogs are the place where a relational database management system stores schema metadata, such as information about tables and columns, and internal bookkeeping information. @@ -14,4 +14,4 @@ particularly esoteric operations, but many of those have been made available as SQL commands over time, and so the need for direct manipulation of the system catalogs is ever decreasing. -

Prev Up Next
50.6. Executor Home 51.1. Overview
\ No newline at end of file +

Prev Up Next
50.6. Executor Home 51.1. Overview
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/charset.html postgresql-13-13.12/doc/src/sgml/html/charset.html --- postgresql-13-13.11/doc/src/sgml/html/charset.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/charset.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 23. Localization
Chapter 23. Localization
Prev UpPart III. Server AdministrationHome Next
Prev Up Next
22.6. Tablespaces Home 23.1. Locale Support
\ No newline at end of file +

Prev Up Next
22.6. Tablespaces Home 23.1. Locale Support
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/citext.html postgresql-13-13.12/doc/src/sgml/html/citext.html --- postgresql-13-13.11/doc/src/sgml/html/citext.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/citext.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.8. citext
F.8. citext
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.8. citext

F.8.1. Rationale
F.8.2. How to Use It
F.8.3. String Comparison Behavior
F.8.4. Limitations
F.8.5. Author

+F.8. citext

F.8. citext
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.8. citext

F.8.1. Rationale
F.8.2. How to Use It
F.8.3. String Comparison Behavior
F.8.4. Limitations
F.8.5. Author

The citext module provides a case-insensitive character string type, citext. Essentially, it internally calls lower when comparing values. Otherwise, it behaves almost @@ -163,4 +163,4 @@ David E. Wheeler

Inspired by the original citext module by Donald Fraser. -

Prev Up Next
F.7. btree_gist Home F.9. cube
\ No newline at end of file +

Prev Up Next
F.7. btree_gist Home F.9. cube
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/client-authentication-problems.html postgresql-13-13.12/doc/src/sgml/html/client-authentication-problems.html --- postgresql-13-13.11/doc/src/sgml/html/client-authentication-problems.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/client-authentication-problems.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.15. Authentication Problems
20.15. Authentication Problems
Prev UpChapter 20. Client AuthenticationHome Next

20.15. Authentication Problems

+20.15. Authentication Problems

20.15. Authentication Problems
Prev UpChapter 20. Client AuthenticationHome Next

20.15. Authentication Problems

Authentication failures and related problems generally manifest themselves through error messages like the following:

@@ -37,4 +37,4 @@ The server log might contain more information about an authentication failure than is reported to the client. If you are confused about the reason for a failure, check the server log. -

Prev Up Next
20.14. BSD Authentication Home Chapter 21. Database Roles
\ No newline at end of file +

Prev Up Next
20.14. BSD Authentication Home Chapter 21. Database Roles
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/client-authentication.html postgresql-13-13.12/doc/src/sgml/html/client-authentication.html --- postgresql-13-13.11/doc/src/sgml/html/client-authentication.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/client-authentication.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 20. Client Authentication
Chapter 20. Client Authentication
Prev UpPart III. Server AdministrationHome Next

Chapter 20. Client Authentication

Table of Contents

20.1. The pg_hba.conf File
20.2. User Name Maps
20.3. Authentication Methods
20.4. Trust Authentication
20.5. Password Authentication
20.6. GSSAPI Authentication
20.7. SSPI Authentication
20.8. Ident Authentication
20.9. Peer Authentication
20.10. LDAP Authentication
20.11. RADIUS Authentication
20.12. Certificate Authentication
20.13. PAM Authentication
20.14. BSD Authentication
20.15. Authentication Problems

+Chapter 20. Client Authentication

Chapter 20. Client Authentication
Prev UpPart III. Server AdministrationHome Next

Chapter 20. Client Authentication

Table of Contents

20.1. The pg_hba.conf File
20.2. User Name Maps
20.3. Authentication Methods
20.4. Trust Authentication
20.5. Password Authentication
20.6. GSSAPI Authentication
20.7. SSPI Authentication
20.8. Ident Authentication
20.9. Peer Authentication
20.10. LDAP Authentication
20.11. RADIUS Authentication
20.12. Certificate Authentication
20.13. PAM Authentication
20.14. BSD Authentication
20.15. Authentication Problems

When a client application connects to the database server, it specifies which PostgreSQL database user name it wants to connect as, much the same way one logs into a Unix computer @@ -34,4 +34,4 @@ operating system account, and in such cases there need be no connection between database user names and OS user names. -

Prev Up Next
19.18. Short Options Home 20.1. The pg_hba.conf File
\ No newline at end of file +

Prev Up Next
19.18. Short Options Home 20.1. The pg_hba.conf File
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/client-interfaces.html postgresql-13-13.12/doc/src/sgml/html/client-interfaces.html --- postgresql-13-13.11/doc/src/sgml/html/client-interfaces.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/client-interfaces.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -Part IV. Client Interfaces
Part IV. Client Interfaces
Prev UpPostgreSQL 13.11 DocumentationHome Next

Part IV. Client Interfaces

+Part IV. Client Interfaces

Part IV. Client Interfaces
Prev UpPostgreSQL 13.12 DocumentationHome Next

Part IV. Client Interfaces

This part describes the client programming interfaces distributed with PostgreSQL. Each of these chapters can be read independently. Note that there are many other programming @@ -9,4 +9,4 @@ familiar with using SQL commands to manipulate and query the database (see Part II) and of course with the programming language that the interface uses. -

Table of Contents

33. libpq — C Library
33.1. Database Connection Control Functions
33.2. Connection Status Functions
33.3. Command Execution Functions
33.4. Asynchronous Command Processing
33.5. Retrieving Query Results Row-by-Row
33.6. Canceling Queries in Progress
33.7. The Fast-Path Interface
33.8. Asynchronous Notification
33.9. Functions Associated with the COPY Command
33.10. Control Functions
33.11. Miscellaneous Functions
33.12. Notice Processing
33.13. Event System
33.14. Environment Variables
33.15. The Password File
33.16. The Connection Service File
33.17. LDAP Lookup of Connection Parameters
33.18. SSL Support
33.19. Behavior in Threaded Programs
33.20. Building libpq Programs
33.21. Example Programs
34. Large Objects
34.1. Introduction
34.2. Implementation Features
34.3. Client Interfaces
34.4. Server-Side Functions
34.5. Example Program
35. ECPG — Embedded SQL in C
35.1. The Concept
35.2. Managing Database Connections
35.3. Running SQL Commands
35.4. Using Host Variables
35.5. Dynamic SQL
35.6. pgtypes Library
35.7. Using Descriptor Areas
35.8. Error Handling
35.9. Preprocessor Directives
35.10. Processing Embedded SQL Programs
35.11. Library Functions
35.12. Large Objects
35.13. C++ Applications
35.14. Embedded SQL Commands
35.15. Informix Compatibility Mode
35.16. Oracle Compatibility Mode
35.17. Internals
36. The Information Schema
36.1. The Schema
36.2. Data Types
36.3. information_schema_catalog_name
36.4. administrable_role_​authorizations
36.5. applicable_roles
36.6. attributes
36.7. character_sets
36.8. check_constraint_routine_usage
36.9. check_constraints
36.10. collations
36.11. collation_character_set_​applicability
36.12. column_column_usage
36.13. column_domain_usage
36.14. column_options
36.15. column_privileges
36.16. column_udt_usage
36.17. columns
36.18. constraint_column_usage
36.19. constraint_table_usage
36.20. data_type_privileges
36.21. domain_constraints
36.22. domain_udt_usage
36.23. domains
36.24. element_types
36.25. enabled_roles
36.26. foreign_data_wrapper_options
36.27. foreign_data_wrappers
36.28. foreign_server_options
36.29. foreign_servers
36.30. foreign_table_options
36.31. foreign_tables
36.32. key_column_usage
36.33. parameters
36.34. referential_constraints
36.35. role_column_grants
36.36. role_routine_grants
36.37. role_table_grants
36.38. role_udt_grants
36.39. role_usage_grants
36.40. routine_privileges
36.41. routines
36.42. schemata
36.43. sequences
36.44. sql_features
36.45. sql_implementation_info
36.46. sql_parts
36.47. sql_sizing
36.48. table_constraints
36.49. table_privileges
36.50. tables
36.51. transforms
36.52. triggered_update_columns
36.53. triggers
36.54. udt_privileges
36.55. usage_privileges
36.56. user_defined_types
36.57. user_mapping_options
36.58. user_mappings
36.59. view_column_usage
36.60. view_routine_usage
36.61. view_table_usage
36.62. views
Prev Up Next
32.5. Test Coverage Examination Home Chapter 33. libpq — C Library
\ No newline at end of file +

Table of Contents

33. libpq — C Library
33.1. Database Connection Control Functions
33.2. Connection Status Functions
33.3. Command Execution Functions
33.4. Asynchronous Command Processing
33.5. Retrieving Query Results Row-by-Row
33.6. Canceling Queries in Progress
33.7. The Fast-Path Interface
33.8. Asynchronous Notification
33.9. Functions Associated with the COPY Command
33.10. Control Functions
33.11. Miscellaneous Functions
33.12. Notice Processing
33.13. Event System
33.14. Environment Variables
33.15. The Password File
33.16. The Connection Service File
33.17. LDAP Lookup of Connection Parameters
33.18. SSL Support
33.19. Behavior in Threaded Programs
33.20. Building libpq Programs
33.21. Example Programs
34. Large Objects
34.1. Introduction
34.2. Implementation Features
34.3. Client Interfaces
34.4. Server-Side Functions
34.5. Example Program
35. ECPG — Embedded SQL in C
35.1. The Concept
35.2. Managing Database Connections
35.3. Running SQL Commands
35.4. Using Host Variables
35.5. Dynamic SQL
35.6. pgtypes Library
35.7. Using Descriptor Areas
35.8. Error Handling
35.9. Preprocessor Directives
35.10. Processing Embedded SQL Programs
35.11. Library Functions
35.12. Large Objects
35.13. C++ Applications
35.14. Embedded SQL Commands
35.15. Informix Compatibility Mode
35.16. Oracle Compatibility Mode
35.17. Internals
36. The Information Schema
36.1. The Schema
36.2. Data Types
36.3. information_schema_catalog_name
36.4. administrable_role_​authorizations
36.5. applicable_roles
36.6. attributes
36.7. character_sets
36.8. check_constraint_routine_usage
36.9. check_constraints
36.10. collations
36.11. collation_character_set_​applicability
36.12. column_column_usage
36.13. column_domain_usage
36.14. column_options
36.15. column_privileges
36.16. column_udt_usage
36.17. columns
36.18. constraint_column_usage
36.19. constraint_table_usage
36.20. data_type_privileges
36.21. domain_constraints
36.22. domain_udt_usage
36.23. domains
36.24. element_types
36.25. enabled_roles
36.26. foreign_data_wrapper_options
36.27. foreign_data_wrappers
36.28. foreign_server_options
36.29. foreign_servers
36.30. foreign_table_options
36.31. foreign_tables
36.32. key_column_usage
36.33. parameters
36.34. referential_constraints
36.35. role_column_grants
36.36. role_routine_grants
36.37. role_table_grants
36.38. role_udt_grants
36.39. role_usage_grants
36.40. routine_privileges
36.41. routines
36.42. schemata
36.43. sequences
36.44. sql_features
36.45. sql_implementation_info
36.46. sql_parts
36.47. sql_sizing
36.48. table_constraints
36.49. table_privileges
36.50. tables
36.51. transforms
36.52. triggered_update_columns
36.53. triggers
36.54. udt_privileges
36.55. usage_privileges
36.56. user_defined_types
36.57. user_mapping_options
36.58. user_mappings
36.59. view_column_usage
36.60. view_routine_usage
36.61. view_table_usage
36.62. views
Prev Up Next
32.5. Test Coverage Examination Home Chapter 33. libpq — C Library
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/collation.html postgresql-13-13.12/doc/src/sgml/html/collation.html --- postgresql-13-13.11/doc/src/sgml/html/collation.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/collation.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -23.2. Collation Support
23.2. Collation Support
Prev UpChapter 23. LocalizationHome Next

23.2. Collation Support

23.2.1. Concepts
23.2.2. Managing Collations

+23.2. Collation Support

23.2. Collation Support
Prev UpChapter 23. LocalizationHome Next

23.2. Collation Support

23.2.1. Concepts
23.2.2. Managing Collations

The collation feature allows specifying the sort order and character classification behavior of data per-column, or even per-operation. This alleviates the restriction that the @@ -413,4 +413,4 @@ normalize and is normalized to preprocess or check the strings, instead of using nondeterministic collations. There are different trade-offs for each approach. -

Prev Up Next
23.1. Locale Support Home 23.3. Character Set Support
\ No newline at end of file +

Prev Up Next
23.1. Locale Support Home 23.3. Character Set Support
\ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/color-when.html postgresql-13-13.12/doc/src/sgml/html/color-when.html --- postgresql-13-13.11/doc/src/sgml/html/color-when.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/color-when.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -N.1. When Color is Used
N.1. When Color is Used
Prev UpAppendix N. Color SupportHome Next

N.1. When Color is Used

+N.1. When Color is Used

N.1. When Color is Used
Prev UpAppendix N. Color SupportHome Next

N.1. When Color is Used

To use colorized output, set the environment variable PG_COLOR as follows: @@ -12,4 +12,4 @@

  • Otherwise, color is not used.

    • -

    Prev Up Next
    Appendix N. Color Support Home N.2. Configuring the Colors
    \ No newline at end of file +

    Prev Up Next
    Appendix N. Color Support Home N.2. Configuring the Colors
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/color-which.html postgresql-13-13.12/doc/src/sgml/html/color-which.html --- postgresql-13-13.11/doc/src/sgml/html/color-which.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/color-which.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -N.2. Configuring the Colors
    N.2. Configuring the Colors
    Prev UpAppendix N. Color SupportHome Next

    N.2. Configuring the Colors

    +N.2. Configuring the Colors

    N.2. Configuring the Colors
    Prev UpAppendix N. Color SupportHome Next

    N.2. Configuring the Colors

    The actual colors to be used are configured using the environment variable PG_COLORS (note plural). The value is a colon-separated list of @@ -20,4 +20,4 @@ This color specification format is also used by other software packages such as GCC, GNU coreutils, and GNU grep. -

    Prev Up Next
    N.1. When Color is Used Home Appendix O. Obsolete or Renamed Features
    \ No newline at end of file +

    Prev Up Next
    N.1. When Color is Used Home Appendix O. Obsolete or Renamed Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/color.html postgresql-13-13.12/doc/src/sgml/html/color.html --- postgresql-13-13.11/doc/src/sgml/html/color.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/color.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix N. Color Support
    Appendix N. Color Support
    Prev UpPart VIII. AppendixesHome Next

    Appendix N. Color Support

    Table of Contents

    N.1. When Color is Used
    N.2. Configuring the Colors

    +Appendix N. Color Support

    Appendix N. Color Support
    Prev UpPart VIII. AppendixesHome Next

    Appendix N. Color Support

    Table of Contents

    N.1. When Color is Used
    N.2. Configuring the Colors

    Most programs in the PostgreSQL package can produce colorized console output. This appendix describes how that is configured. -

    Prev Up Next
    Appendix M. Glossary Home N.1. When Color is Used
    \ No newline at end of file +

    Prev Up Next
    Appendix M. Glossary Home N.1. When Color is Used
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/config-setting.html postgresql-13-13.12/doc/src/sgml/html/config-setting.html --- postgresql-13-13.11/doc/src/sgml/html/config-setting.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/config-setting.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.1. Setting Parameters
    19.1. Setting Parameters
    Prev UpChapter 19. Server ConfigurationHome Next

    19.1. Setting Parameters

    19.1.1. Parameter Names and Values
    19.1.2. Parameter Interaction via the Configuration File
    19.1.3. Parameter Interaction via SQL
    19.1.4. Parameter Interaction via the Shell
    19.1.5. Managing Configuration File Contents

    19.1.1. Parameter Names and Values

    +19.1. Setting Parameters

    19.1. Setting Parameters
    Prev UpChapter 19. Server ConfigurationHome Next

    19.1. Setting Parameters

    19.1.1. Parameter Names and Values
    19.1.2. Parameter Interaction via the Configuration File
    19.1.3. Parameter Interaction via SQL
    19.1.4. Parameter Interaction via the Shell
    19.1.5. Managing Configuration File Contents

    19.1.1. Parameter Names and Values

    All parameter names are case-insensitive. Every parameter takes a value of one of five types: boolean, string, integer, floating point, or enumerated (enum). The type determines the syntax for setting the @@ -330,4 +330,4 @@ their configurations all stored in one place, such as in a version control repository. (Storing database configuration files under version control is another good practice to consider.) -

    Prev Up Next
    Chapter 19. Server Configuration Home 19.2. File Locations
    \ No newline at end of file +

    Prev Up Next
    Chapter 19. Server Configuration Home 19.2. File Locations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/connect-estab.html postgresql-13-13.12/doc/src/sgml/html/connect-estab.html --- postgresql-13-13.11/doc/src/sgml/html/connect-estab.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/connect-estab.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.2. How Connections Are Established
    50.2. How Connections Are Established
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.2. How Connections Are Established

    +50.2. How Connections Are Established

    50.2. How Connections Are Established
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.2. How Connections Are Established

    PostgreSQL is implemented using a simple “process per user” client/server model. In this model there is one client process connected to @@ -28,4 +28,4 @@ server parses the query, creates an execution plan, executes the plan and returns the retrieved rows to the client by transmitting them over the established connection. -

    Prev Up Next
    50.1. The Path of a Query Home 50.3. The Parser Stage
    \ No newline at end of file +

    Prev Up Next
    50.1. The Path of a Query Home 50.3. The Parser Stage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/continuous-archiving.html postgresql-13-13.12/doc/src/sgml/html/continuous-archiving.html --- postgresql-13-13.11/doc/src/sgml/html/continuous-archiving.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/continuous-archiving.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
    25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
    Prev UpChapter 25. Backup and RestoreHome Next

    25.3. Continuous Archiving and Point-in-Time Recovery (PITR)

    25.3.1. Setting Up WAL Archiving
    25.3.2. Making a Base Backup
    25.3.3. Making a Base Backup Using the Low Level API
    25.3.4. Recovering Using a Continuous Archive Backup
    25.3.5. Timelines
    25.3.6. Tips and Examples
    25.3.7. Caveats

    +25.3. Continuous Archiving and Point-in-Time Recovery (PITR)

    25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
    Prev UpChapter 25. Backup and RestoreHome Next

    25.3. Continuous Archiving and Point-in-Time Recovery (PITR)

    25.3.1. Setting Up WAL Archiving
    25.3.2. Making a Base Backup
    25.3.3. Making a Base Backup Using the Low Level API
    25.3.4. Recovering Using a Continuous Archive Backup
    25.3.5. Timelines
    25.3.6. Tips and Examples
    25.3.7. Caveats

    At all times, PostgreSQL maintains a write ahead log (WAL) in the pg_wal/ subdirectory of the cluster's data directory. The log records @@ -880,4 +880,4 @@ on. In the meantime, administrators might wish to reduce the number of page snapshots included in WAL by increasing the checkpoint interval parameters as much as feasible. -

    Prev Up Next
    25.2. File System Level Backup Home Chapter 26. High Availability, Load Balancing, and Replication
    \ No newline at end of file +

    Prev Up Next
    25.2. File System Level Backup Home Chapter 26. High Availability, Load Balancing, and Replication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-delete.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-delete.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_build_sql_delete
    dblink_build_sql_delete
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_build_sql_insert Home dblink_build_sql_update
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-insert.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-insert.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-insert.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-insert.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_build_sql_insert
    dblink_build_sql_insert
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_get_pkey Home dblink_build_sql_delete
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-update.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-update.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-build-sql-update.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-build-sql-update.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_build_sql_update
    dblink_build_sql_update
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_build_sql_delete Home F.11. dict_int
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-cancel-query.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-cancel-query.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-cancel-query.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-cancel-query.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_cancel_query
    dblink_cancel_query
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_get_result Home dblink_get_pkey
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-close.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-close.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-close.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-close.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_close
    dblink_close
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_fetch Home dblink_get_connections
    \ No newline at end of file +
    Prev Up Next
    dblink_fetch Home dblink_get_connections
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-connect-u.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-connect-u.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-connect-u.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-connect-u.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_connect_u
    dblink_connect_u
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_connect Home dblink_disconnect
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-connect.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-connect.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-connect.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-connect.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_connect
    dblink_connect
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    F.10. dblink Home dblink_connect_u
    \ No newline at end of file +
    Prev Up Next
    F.10. dblink Home dblink_connect_u
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-disconnect.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-disconnect.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-disconnect.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-disconnect.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_disconnect
    dblink_disconnect
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_connect_u Home dblink
    \ No newline at end of file +
    Prev Up Next
    dblink_connect_u Home dblink
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-error-message.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-error-message.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-error-message.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-error-message.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_error_message
    dblink_error_message
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_get_connections Home dblink_send_query
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-exec.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-exec.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-exec.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-exec.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_exec
    dblink_exec
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink Home dblink_open
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-fetch.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-fetch.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-fetch.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-fetch.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_fetch
    dblink_fetch
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_open Home dblink_close
    \ No newline at end of file +
    Prev Up Next
    dblink_open Home dblink_close
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-function.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-function.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-function.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-function.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink
    dblink
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_disconnect Home dblink_exec
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-connections.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-connections.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-connections.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-connections.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,9 +1,9 @@ -dblink_get_connections
    dblink_get_connections
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_close Home dblink_error_message
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-notify.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-notify.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-notify.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-notify.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_get_notify
    dblink_get_notify
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_is_busy Home dblink_get_result
    \ No newline at end of file +
    Prev Up Next
    dblink_is_busy Home dblink_get_result
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-pkey.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-pkey.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-pkey.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-pkey.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_get_pkey
    dblink_get_pkey
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_cancel_query Home dblink_build_sql_insert
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-result.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-result.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-get-result.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-get-result.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_get_result
    dblink_get_result
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_get_notify Home dblink_cancel_query
    \ No newline at end of file +
    Prev Up Next
    dblink_get_notify Home dblink_cancel_query
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-is-busy.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-is-busy.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-is-busy.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-is-busy.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_is_busy
    dblink_is_busy
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_send_query Home dblink_get_notify
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-open.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-open.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-open.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-open.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_open
    dblink_open
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_exec Home dblink_fetch
    \ No newline at end of file +
    Prev Up Next
    dblink_exec Home dblink_fetch
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-send-query.html postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-send-query.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-dblink-send-query.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-dblink-send-query.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -dblink_send_query
    dblink_send_query
    Prev UpF.10. dblinkHome Next
    Prev Up Next
    dblink_error_message Home dblink_is_busy
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-prog-client.html postgresql-13-13.12/doc/src/sgml/html/contrib-prog-client.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-prog-client.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-prog-client.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,9 +1,9 @@ -G.1. Client Applications
    G.1. Client Applications
    Prev UpAppendix G. Additional Supplied ProgramsHome Next

    G.1. Client Applications

    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
    vacuumlo — remove orphaned large objects from a PostgreSQL database

    +G.1. Client Applications

    G.1. Client Applications
    Prev UpAppendix G. Additional Supplied ProgramsHome Next

    G.1. Client Applications

    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
    vacuumlo — remove orphaned large objects from a PostgreSQL database

    This section covers PostgreSQL client applications in contrib. They can be run from anywhere, independent of where the database server resides. See also PostgreSQL Client Applications for information about client applications that are part of the core PostgreSQL distribution. -

    Prev Up Next
    Appendix G. Additional Supplied Programs Home oid2name
    \ No newline at end of file +

    Prev Up Next
    Appendix G. Additional Supplied Programs Home oid2name
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-prog-server.html postgresql-13-13.12/doc/src/sgml/html/contrib-prog-server.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-prog-server.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-prog-server.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,7 +1,7 @@ -G.2. Server Applications
    G.2. Server Applications
    Prev UpAppendix G. Additional Supplied ProgramsHome Next

    G.2. Server Applications

    pg_standby — supports the creation of a PostgreSQL warm standby server

    +G.2. Server Applications

    G.2. Server Applications
    Prev UpAppendix G. Additional Supplied ProgramsHome Next

    G.2. Server Applications

    pg_standby — supports the creation of a PostgreSQL warm standby server

    This section covers PostgreSQL server-related applications in contrib. They are typically run on the host where the database server resides. See also PostgreSQL Server Applications for information about server applications that are part of the core PostgreSQL distribution. -

    Prev Up Next
    vacuumlo Home pg_standby
    \ No newline at end of file +

    Prev Up Next
    vacuumlo Home pg_standby
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-prog.html postgresql-13-13.12/doc/src/sgml/html/contrib-prog.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-prog.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-prog.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix G. Additional Supplied Programs
    Appendix G. Additional Supplied Programs
    Prev UpPart VIII. AppendixesHome Next

    Appendix G. Additional Supplied Programs

    Table of Contents

    G.1. Client Applications
    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
    vacuumlo — remove orphaned large objects from a PostgreSQL database
    G.2. Server Applications
    pg_standby — supports the creation of a PostgreSQL warm standby server

    +Appendix G. Additional Supplied Programs

    Appendix G. Additional Supplied Programs
    Prev UpPart VIII. AppendixesHome Next

    Appendix G. Additional Supplied Programs

    Table of Contents

    G.1. Client Applications
    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory
    vacuumlo — remove orphaned large objects from a PostgreSQL database
    G.2. Server Applications
    pg_standby — supports the creation of a PostgreSQL warm standby server

    This appendix and the previous one contain information regarding the modules that can be found in the contrib directory of the PostgreSQL distribution. See Appendix F for @@ -12,4 +12,4 @@ the bin directory of the PostgreSQL installation and can be used like any other program. -

    Prev Up Next
    F.45. xml2 Home G.1. Client Applications
    \ No newline at end of file +

    Prev Up Next
    F.45. xml2 Home G.1. Client Applications
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib-spi.html postgresql-13-13.12/doc/src/sgml/html/contrib-spi.html --- postgresql-13-13.11/doc/src/sgml/html/contrib-spi.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib-spi.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.36. spi
    F.36. spi
    Prev UpAppendix F. Additional Supplied ModulesHome Next
    Prev Up Next
    F.35. sepgsql Home F.37. sslinfo
    \ No newline at end of file +

    Prev Up Next
    F.35. sepgsql Home F.37. sslinfo
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/contrib.html postgresql-13-13.12/doc/src/sgml/html/contrib.html --- postgresql-13-13.11/doc/src/sgml/html/contrib.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/contrib.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix F. Additional Supplied Modules
    Appendix F. Additional Supplied Modules
    Prev UpPart VIII. AppendixesHome Next

    Appendix F. Additional Supplied Modules

    Table of Contents

    F.1. adminpack
    F.2. amcheck
    F.2.1. Functions
    F.2.2. Optional heapallindexed Verification
    F.2.3. Using amcheck Effectively
    F.2.4. Repairing Corruption
    F.3. auth_delay
    F.3.1. Configuration Parameters
    F.3.2. Author
    F.4. auto_explain
    F.4.1. Configuration Parameters
    F.4.2. Example
    F.4.3. Author
    F.5. bloom
    F.5.1. Parameters
    F.5.2. Examples
    F.5.3. Operator Class Interface
    F.5.4. Limitations
    F.5.5. Authors
    F.6. btree_gin
    F.6.1. Example Usage
    F.6.2. Authors
    F.7. btree_gist
    F.7.1. Example Usage
    F.7.2. Authors
    F.8. citext
    F.8.1. Rationale
    F.8.2. How to Use It
    F.8.3. String Comparison Behavior
    F.8.4. Limitations
    F.8.5. Author
    F.9. cube
    F.9.1. Syntax
    F.9.2. Precision
    F.9.3. Usage
    F.9.4. Defaults
    F.9.5. Notes
    F.9.6. Credits
    F.10. dblink
    dblink_connect — opens a persistent connection to a remote database
    dblink_connect_u — opens a persistent connection to a remote database, insecurely
    dblink_disconnect — closes a persistent connection to a remote database
    dblink — executes a query in a remote database
    dblink_exec — executes a command in a remote database
    dblink_open — opens a cursor in a remote database
    dblink_fetch — returns rows from an open cursor in a remote database
    dblink_close — closes a cursor in a remote database
    dblink_get_connections — returns the names of all open named dblink connections
    dblink_error_message — gets last error message on the named connection
    dblink_send_query — sends an async query to a remote database
    dblink_is_busy — checks if connection is busy with an async query
    dblink_get_notify — retrieve async notifications on a connection
    dblink_get_result — gets an async query result
    dblink_cancel_query — cancels any active query on the named connection
    dblink_get_pkey — returns the positions and field names of a relation's +Appendix F. Additional Supplied Modules
    Appendix F. Additional Supplied Modules
    Prev UpPart VIII. AppendixesHome Next

    Appendix F. Additional Supplied Modules

    Table of Contents

    F.1. adminpack
    F.2. amcheck
    F.2.1. Functions
    F.2.2. Optional heapallindexed Verification
    F.2.3. Using amcheck Effectively
    F.2.4. Repairing Corruption
    F.3. auth_delay
    F.3.1. Configuration Parameters
    F.3.2. Author
    F.4. auto_explain
    F.4.1. Configuration Parameters
    F.4.2. Example
    F.4.3. Author
    F.5. bloom
    F.5.1. Parameters
    F.5.2. Examples
    F.5.3. Operator Class Interface
    F.5.4. Limitations
    F.5.5. Authors
    F.6. btree_gin
    F.6.1. Example Usage
    F.6.2. Authors
    F.7. btree_gist
    F.7.1. Example Usage
    F.7.2. Authors
    F.8. citext
    F.8.1. Rationale
    F.8.2. How to Use It
    F.8.3. String Comparison Behavior
    F.8.4. Limitations
    F.8.5. Author
    F.9. cube
    F.9.1. Syntax
    F.9.2. Precision
    F.9.3. Usage
    F.9.4. Defaults
    F.9.5. Notes
    F.9.6. Credits
    F.10. dblink
    dblink_connect — opens a persistent connection to a remote database
    dblink_connect_u — opens a persistent connection to a remote database, insecurely
    dblink_disconnect — closes a persistent connection to a remote database
    dblink — executes a query in a remote database
    dblink_exec — executes a command in a remote database
    dblink_open — opens a cursor in a remote database
    dblink_fetch — returns rows from an open cursor in a remote database
    dblink_close — closes a cursor in a remote database
    dblink_get_connections — returns the names of all open named dblink connections
    dblink_error_message — gets last error message on the named connection
    dblink_send_query — sends an async query to a remote database
    dblink_is_busy — checks if connection is busy with an async query
    dblink_get_notify — retrieve async notifications on a connection
    dblink_get_result — gets an async query result
    dblink_cancel_query — cancels any active query on the named connection
    dblink_get_pkey — returns the positions and field names of a relation's primary key fields
    dblink_build_sql_insert — builds an INSERT statement using a local tuple, replacing the @@ -84,4 +84,4 @@ by way of shared_preload_libraries. See the documentation of each module for details. -

    Prev Up Next
    E.13. Prior Releases Home F.1. adminpack
    \ No newline at end of file +

    Prev Up Next
    E.14. Prior Releases Home F.1. adminpack
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/creating-cluster.html postgresql-13-13.12/doc/src/sgml/html/creating-cluster.html --- postgresql-13-13.11/doc/src/sgml/html/creating-cluster.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/creating-cluster.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.2. Creating a Database Cluster
    18.2. Creating a Database Cluster
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.2. Creating a Database Cluster

    18.2.1. Use of Secondary File Systems
    18.2.2. File Systems

    +18.2. Creating a Database Cluster

    18.2. Creating a Database Cluster
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.2. Creating a Database Cluster

    18.2.1. Use of Secondary File Systems
    18.2.2. File Systems

    Before you can do anything, you must initialize a database storage area on disk. We call this a database cluster. (The SQL standard uses the term catalog cluster.) A @@ -200,4 +200,4 @@ it. That approach might relieve the DBA from having to deal with some of the idiosyncrasies of NFS, but of course the complexity of managing remote storage then happens at other levels. -

    Prev Up Next
    18.1. The PostgreSQL User Account Home 18.3. Starting the Database Server
    \ No newline at end of file +

    Prev Up Next
    18.1. The PostgreSQL User Account Home 18.3. Starting the Database Server
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/cube.html postgresql-13-13.12/doc/src/sgml/html/cube.html --- postgresql-13-13.11/doc/src/sgml/html/cube.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/cube.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -F.9. cube
    F.9. cube
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.9. cube

    F.9.1. Syntax
    F.9.2. Precision
    F.9.3. Usage
    F.9.4. Defaults
    F.9.5. Notes
    F.9.6. Credits

    +F.9. cube

    F.9. cube
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.9. cube

    F.9.1. Syntax
    F.9.2. Precision
    F.9.3. Usage
    F.9.4. Defaults
    F.9.5. Notes
    F.9.6. Credits

    This module implements a data type cube for representing multidimensional cubes.

    @@ -394,4 +394,4 @@ July 2006. These include cube(float8[], float8[]) and cleaning up the code to use the V1 call protocol instead of the deprecated V0 protocol. -

    Prev Up Next
    F.8. citext Home F.10. dblink
    \ No newline at end of file +

    Prev Up Next
    F.8. citext Home F.10. dblink
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/custom-scan-execution.html postgresql-13-13.12/doc/src/sgml/html/custom-scan-execution.html --- postgresql-13-13.11/doc/src/sgml/html/custom-scan-execution.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/custom-scan-execution.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -58.3. Executing Custom Scans
    58.3. Executing Custom Scans
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.3. Executing Custom Scans

    58.3.1. Custom Scan Execution Callbacks

    +58.3. Executing Custom Scans

    58.3. Executing Custom Scans
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.3. Executing Custom Scans

    58.3.1. Custom Scan Execution Callbacks

    When a CustomScan is executed, its execution state is represented by a CustomScanState, which is declared as follows: @@ -136,4 +136,4 @@ ScanState, such as the target list and scan relation, will be shown even without this callback, but the callback allows the display of additional, private state. -

    Prev Up Next
    58.2. Creating Custom Scan Plans Home Chapter 59. Genetic Query Optimizer
    \ No newline at end of file +

    Prev Up Next
    58.2. Creating Custom Scan Plans Home Chapter 59. Genetic Query Optimizer
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/custom-scan-path.html postgresql-13-13.12/doc/src/sgml/html/custom-scan-path.html --- postgresql-13-13.11/doc/src/sgml/html/custom-scan-path.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/custom-scan-path.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -58.1. Creating Custom Scan Paths
    58.1. Creating Custom Scan Paths
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.1. Creating Custom Scan Paths

    58.1.1. Custom Scan Path Callbacks

    +58.1. Creating Custom Scan Paths

    58.1. Creating Custom Scan Paths
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.1. Creating Custom Scan Paths

    58.1.1. Custom Scan Path Callbacks

    A custom scan provider will typically add paths for a base relation by setting the following hook, which is called after the core code has generated all the access paths it can for the relation (except for @@ -44,7 +44,7 @@ by nodeToString, so that debugging routines that attempt to print the custom path will work as designed. methods must point to a (usually statically allocated) object implementing the required - custom path methods, of which there is currently only one. + custom path methods, which are further detailed below.

    A custom scan provider can also provide join paths. Just as for base relations, such a path must produce the same output as would normally be @@ -76,4 +76,19 @@ Convert a custom path to a finished plan. The return value will generally be a CustomScan object, which the callback must allocate and initialize. See Section 58.2 for more details. -

    Prev Up Next
    Chapter 58. Writing a Custom Scan Provider Home 58.2. Creating Custom Scan Plans
    \ No newline at end of file +

    +

    +List *(*ReparameterizeCustomPathByChild) (PlannerInfo *root,
+                                          List *custom_private,
+                                          RelOptInfo *child_rel);
+

    + This callback is called while converting a path parameterized by the + top-most parent of the given child relation child_rel + to be parameterized by the child relation. The callback is used to + reparameterize any paths or translate any expression nodes saved in the + given custom_private member of a + CustomPath. The callback may use + reparameterize_path_by_child, + adjust_appendrel_attrs or + adjust_appendrel_attrs_multilevel as required. +

    Prev Up Next
    Chapter 58. Writing a Custom Scan Provider Home 58.2. Creating Custom Scan Plans
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/custom-scan-plan.html postgresql-13-13.12/doc/src/sgml/html/custom-scan-plan.html --- postgresql-13-13.11/doc/src/sgml/html/custom-scan-plan.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/custom-scan-plan.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -58.2. Creating Custom Scan Plans
    58.2. Creating Custom Scan Plans
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.2. Creating Custom Scan Plans

    58.2.1. Custom Scan Plan Callbacks

    +58.2. Creating Custom Scan Plans

    58.2. Creating Custom Scan Plans
    Prev UpChapter 58. Writing a Custom Scan ProviderHome Next

    58.2. Creating Custom Scan Plans

    58.2.1. Custom Scan Plan Callbacks

    A custom scan is represented in a finished plan tree using the following structure: 

    @@ -64,4 +64,4 @@
     stage; after ExecInitCustomScan performs basic initialization,
     the BeginCustomScan callback will be invoked to give the
     custom scan provider a chance to do whatever else is needed.
-
    Prev Up Next
    58.1. Creating Custom Scan Paths Home 58.3. Executing Custom Scans
    \ No newline at end of file +

    Prev Up Next
    58.1. Creating Custom Scan Paths Home 58.3. Executing Custom Scans
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/custom-scan.html postgresql-13-13.12/doc/src/sgml/html/custom-scan.html --- postgresql-13-13.11/doc/src/sgml/html/custom-scan.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/custom-scan.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 58. Writing a Custom Scan Provider
    Chapter 58. Writing a Custom Scan Provider
    Prev UpPart VII. InternalsHome Next

    Chapter 58. Writing a Custom Scan Provider

    Table of Contents

    58.1. Creating Custom Scan Paths
    58.1.1. Custom Scan Path Callbacks
    58.2. Creating Custom Scan Plans
    58.2.1. Custom Scan Plan Callbacks
    58.3. Executing Custom Scans
    58.3.1. Custom Scan Execution Callbacks

    +Chapter 58. Writing a Custom Scan Provider

    Chapter 58. Writing a Custom Scan Provider
    Prev UpPart VII. InternalsHome Next

    Chapter 58. Writing a Custom Scan Provider

    Table of Contents

    58.1. Creating Custom Scan Paths
    58.1.1. Custom Scan Path Callbacks
    58.2. Creating Custom Scan Plans
    58.2.1. Custom Scan Plan Callbacks
    58.3. Executing Custom Scans
    58.3.1. Custom Scan Execution Callbacks

    PostgreSQL supports a set of experimental facilities which are intended to allow extension modules to add new scan types to the system. Unlike a foreign data wrapper, which is only @@ -18,4 +18,4 @@ Finally, it must be possible to execute the plan and generate the same results that would have been generated for any other access path targeting the same relation. -

    Prev Up Next
    57.1. Sampling Method Support Functions Home 58.1. Creating Custom Scan Paths
    \ No newline at end of file +

    Prev Up Next
    57.1. Sampling Method Support Functions Home 58.1. Creating Custom Scan Paths
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/database-roles.html postgresql-13-13.12/doc/src/sgml/html/database-roles.html --- postgresql-13-13.11/doc/src/sgml/html/database-roles.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/database-roles.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.1. Database Roles
    21.1. Database Roles
    Prev UpChapter 21. Database RolesHome Next

    21.1. Database Roles

    +21.1. Database Roles

    21.1. Database Roles
    Prev UpChapter 21. Database RolesHome Next

    21.1. Database Roles

    Database roles are conceptually completely separate from operating system users. In practice it might be convenient to maintain a correspondence, but this is not required. Database roles @@ -67,4 +67,4 @@ identity determines the set of privileges available to a connected client, it is important to carefully configure privileges when setting up a multiuser environment. -

    Prev Up Next
    Chapter 21. Database Roles Home 21.2. Role Attributes
    \ No newline at end of file +

    Prev Up Next
    Chapter 21. Database Roles Home 21.2. Role Attributes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-binary.html postgresql-13-13.12/doc/src/sgml/html/datatype-binary.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-binary.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-binary.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.4. Binary Data Types
    8.4. Binary Data Types
    Prev UpChapter 8. Data TypesHome Next

    8.4. Binary Data Types

    8.4.1. bytea Hex Format
    8.4.2. bytea Escape Format

    +8.4. Binary Data Types

    8.4. Binary Data Types
    Prev UpChapter 8. Data TypesHome Next

    8.4. Binary Data Types

    8.4.1. bytea Hex Format
    8.4.2. bytea Escape Format

    The bytea data type allows storage of binary strings; see Table 8.6.

    Table 8.6. Binary Data Types

    NameStorage SizeDescription
    bytea1 or 4 bytes plus the actual binary stringvariable-length binary string

    @@ -129,4 +129,4 @@ unescaping bytea strings. For example, you might also have to escape line feeds and carriage returns if your interface automatically translates these. -

    Prev Up Next
    8.3. Character Types Home 8.5. Date/Time Types
    \ No newline at end of file +

    Prev Up Next
    8.3. Character Types Home 8.5. Date/Time Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-bit.html postgresql-13-13.12/doc/src/sgml/html/datatype-bit.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-bit.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-bit.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.10. Bit String Types
    8.10. Bit String Types
    Prev UpChapter 8. Data TypesHome Next

    8.10. Bit String Types

    +8.10. Bit String Types

    8.10. Bit String Types
    Prev UpChapter 8. Data TypesHome Next

    8.10. Bit String Types

    Bit strings are strings of 1's and 0's. They can be used to store or visualize bit masks. There are two SQL bit types: bit(n) and bit @@ -46,4 +46,4 @@ 5 or 8 bytes overhead depending on the length of the string (but long values may be compressed or moved out-of-line, as explained in Section 8.3 for character strings). -

    Prev Up Next
    8.9. Network Address Types Home 8.11. Text Search Types
    \ No newline at end of file +

    Prev Up Next
    8.9. Network Address Types Home 8.11. Text Search Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-boolean.html postgresql-13-13.12/doc/src/sgml/html/datatype-boolean.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-boolean.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-boolean.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.6. Boolean Type
    8.6. Boolean Type
    Prev UpChapter 8. Data TypesHome Next

    8.6. Boolean Type

    +8.6. Boolean Type

    8.6. Boolean Type
    Prev UpChapter 8. Data TypesHome Next

    8.6. Boolean Type

    PostgreSQL provides the standard SQL type boolean; see Table 8.19. @@ -55,4 +55,4 @@ example NULL::boolean. Conversely, the cast can be omitted from a string-literal Boolean value in contexts where the parser can deduce that the literal must be of type boolean. -

    Prev Up Next
    8.5. Date/Time Types Home 8.7. Enumerated Types
    \ No newline at end of file +

    Prev Up Next
    8.5. Date/Time Types Home 8.7. Enumerated Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-character.html postgresql-13-13.12/doc/src/sgml/html/datatype-character.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-character.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-character.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.3. Character Types
    8.3. Character Types
    Prev UpChapter 8. Data TypesHome Next

    8.3. Character Types

    Table 8.4. Character Types

    NameDescription
    character varying(n), varchar(n)variable-length with limit
    character(n), char(n)fixed-length, blank padded
    textvariable unlimited length

    +8.3. Character Types

    8.3. Character Types
    Prev UpChapter 8. Data TypesHome Next

    8.3. Character Types

    Table 8.4. Character Types

    NameDescription
    character varying(n), varchar(n)variable-length with limit
    character(n), char(n)fixed-length, blank padded
    textvariable unlimited length

    Table 8.4 shows the general-purpose character types available in PostgreSQL. @@ -137,4 +137,4 @@ (note the quotes) is different from char(1) in that it only uses one byte of storage. It is internally used in the system catalogs as a simplistic enumeration type. -

    Table 8.5. Special Character Types

    NameStorage SizeDescription
    "char"1 bytesingle-byte internal type
    name64 bytesinternal type for object names

    Prev Up Next
    8.2. Monetary Types Home 8.4. Binary Data Types
    \ No newline at end of file +

    Table 8.5. Special Character Types

    NameStorage SizeDescription
    "char"1 bytesingle-byte internal type
    name64 bytesinternal type for object names

    Prev Up Next
    8.2. Monetary Types Home 8.4. Binary Data Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-datetime.html postgresql-13-13.12/doc/src/sgml/html/datatype-datetime.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-datetime.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-datetime.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.5. Date/Time Types
    8.5. Date/Time Types
    Prev UpChapter 8. Data TypesHome Next

    8.5. Date/Time Types

    8.5.1. Date/Time Input
    8.5.2. Date/Time Output
    8.5.3. Time Zones
    8.5.4. Interval Input
    8.5.5. Interval Output

    +8.5. Date/Time Types

    8.5. Date/Time Types
    Prev UpChapter 8. Data TypesHome Next

    8.5. Date/Time Types

    8.5.1. Date/Time Input
    8.5.2. Date/Time Output
    8.5.3. Time Zones
    8.5.4. Interval Input
    8.5.5. Interval Output

    PostgreSQL supports the full set of SQL date and time types, shown in Table 8.9. The operations available on these data types are described in @@ -545,4 +545,4 @@ The output of the iso_8601 style matches the “format with designators” described in section 4.4.3.2 of the ISO 8601 standard. -

    Table 8.18. Interval Output Style Examples

    Style SpecificationYear-Month IntervalDay-Time IntervalMixed Interval
    sql_standard1-23 4:05:06-1-2 +3 -4:05:06
    postgres1 year 2 mons3 days 04:05:06-1 year -2 mons +3 days -04:05:06
    postgres_verbose@ 1 year 2 mons@ 3 days 4 hours 5 mins 6 secs@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago
    iso_8601P1Y2MP3DT4H5M6SP-1Y-2M3D​T-4H-5M-6S

    Prev Up Next
    8.4. Binary Data Types Home 8.6. Boolean Type
    \ No newline at end of file +

    Table 8.18. Interval Output Style Examples

    Style SpecificationYear-Month IntervalDay-Time IntervalMixed Interval
    sql_standard1-23 4:05:06-1-2 +3 -4:05:06
    postgres1 year 2 mons3 days 04:05:06-1 year -2 mons +3 days -04:05:06
    postgres_verbose@ 1 year 2 mons@ 3 days 4 hours 5 mins 6 secs@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago
    iso_8601P1Y2MP3DT4H5M6SP-1Y-2M3D​T-4H-5M-6S

    Prev Up Next
    8.4. Binary Data Types Home 8.6. Boolean Type
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-enum.html postgresql-13-13.12/doc/src/sgml/html/datatype-enum.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-enum.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-enum.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.7. Enumerated Types
    8.7. Enumerated Types
    Prev UpChapter 8. Data TypesHome Next

    8.7. Enumerated Types

    8.7.1. Declaration of Enumerated Types
    8.7.2. Ordering
    8.7.3. Type Safety
    8.7.4. Implementation Details

    +8.7. Enumerated Types

    8.7. Enumerated Types
    Prev UpChapter 8. Data TypesHome Next

    8.7. Enumerated Types

    8.7.1. Declaration of Enumerated Types
    8.7.2. Ordering
    8.7.3. Type Safety
    8.7.4. Implementation Details

    Enumerated (enum) types are data types that comprise a static, ordered set of values. They are equivalent to the enum @@ -112,4 +112,4 @@ kept in the system catalog pg_enum. Querying this catalog directly can be useful. -

    Prev Up Next
    8.6. Boolean Type Home 8.8. Geometric Types
    \ No newline at end of file +

    Prev Up Next
    8.6. Boolean Type Home 8.8. Geometric Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-geometric.html postgresql-13-13.12/doc/src/sgml/html/datatype-geometric.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-geometric.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-geometric.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.8. Geometric Types
    8.8. Geometric Types
    Prev UpChapter 8. Data TypesHome Next

    8.8. Geometric Types

    8.8.1. Points
    8.8.2. Lines
    8.8.3. Line Segments
    8.8.4. Boxes
    8.8.5. Paths
    8.8.6. Polygons
    8.8.7. Circles

    +8.8. Geometric Types

    8.8. Geometric Types
    Prev UpChapter 8. Data TypesHome Next

    8.8. Geometric Types

    8.8.1. Points
    8.8.2. Lines
    8.8.3. Line Segments
    8.8.4. Boxes
    8.8.5. Paths
    8.8.6. Polygons
    8.8.7. Circles

    Geometric data types represent two-dimensional spatial objects. Table 8.20 shows the geometric types available in PostgreSQL. @@ -148,4 +148,4 @@ circle.

    Circles are output using the first syntax. -

    Prev Up Next
    8.7. Enumerated Types Home 8.9. Network Address Types
    \ No newline at end of file +

    Prev Up Next
    8.7. Enumerated Types Home 8.9. Network Address Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-json.html postgresql-13-13.12/doc/src/sgml/html/datatype-json.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-json.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-json.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.14. JSON Types
    8.14. JSON Types
    Prev UpChapter 8. Data TypesHome Next

    8.14. JSON Types

    8.14.1. JSON Input and Output Syntax
    8.14.2. Designing JSON Documents
    8.14.3. jsonb Containment and Existence
    8.14.4. jsonb Indexing
    8.14.5. Transforms
    8.14.6. jsonpath Type

    +8.14. JSON Types

    8.14. JSON Types
    Prev UpChapter 8. Data TypesHome Next

    8.14. JSON Types

    8.14.1. JSON Input and Output Syntax
    8.14.2. Designing JSON Documents
    8.14.3. jsonb Containment and Existence
    8.14.4. jsonb Indexing
    8.14.5. Transforms
    8.14.6. jsonpath Type

    JSON data types are for storing JSON (JavaScript Object Notation) data, as specified in RFC 7159. Such data can also be stored as text, but @@ -639,4 +639,4 @@ For this purpose, the term “value” includes array elements, though JSON terminology sometimes considers array elements distinct from values within objects. -

    Prev Up Next
    8.13. XML Type Home 8.15. Arrays
    \ No newline at end of file +

    Prev Up Next
    8.13. XML Type Home 8.15. Arrays
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-money.html postgresql-13-13.12/doc/src/sgml/html/datatype-money.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-money.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-money.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.2. Monetary Types
    8.2. Monetary Types
    Prev UpChapter 8. Data TypesHome Next

    8.2. Monetary Types

    +8.2. Monetary Types

    8.2. Monetary Types
    Prev UpChapter 8. Data TypesHome Next

    8.2. Monetary Types

    The money type stores a currency amount with a fixed fractional precision; see Table 8.3. The fractional precision is determined by the database's lc_monetary setting. @@ -41,4 +41,4 @@ When a money value is divided by another money value, the result is double precision (i.e., a pure number, not money); the currency units cancel each other out in the division. -

    Prev Up Next
    8.1. Numeric Types Home 8.3. Character Types
    \ No newline at end of file +

    Prev Up Next
    8.1. Numeric Types Home 8.3. Character Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-net-types.html postgresql-13-13.12/doc/src/sgml/html/datatype-net-types.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-net-types.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-net-types.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.9. Network Address Types
    8.9. Network Address Types
    Prev UpChapter 8. Data TypesHome Next

    8.9. Network Address Types

    8.9.1. inet
    8.9.2. cidr
    8.9.3. inet vs. cidr
    8.9.4. macaddr
    8.9.5. macaddr8

    +8.9. Network Address Types

    8.9. Network Address Types
    Prev UpChapter 8. Data TypesHome Next

    8.9. Network Address Types

    8.9.1. inet
    8.9.2. cidr
    8.9.3. inet vs. cidr
    8.9.4. macaddr
    8.9.5. macaddr8

    PostgreSQL offers data types to store IPv4, IPv6, and MAC addresses, as shown in Table 8.21. It is better to use these types instead of plain text types to store @@ -129,4 +129,4 @@

    -

    Prev Up Next
    8.8. Geometric Types Home 8.10. Bit String Types
    \ No newline at end of file +

    Prev Up Next
    8.8. Geometric Types Home 8.10. Bit String Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-numeric.html postgresql-13-13.12/doc/src/sgml/html/datatype-numeric.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-numeric.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-numeric.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.1. Numeric Types
    8.1. Numeric Types
    Prev UpChapter 8. Data TypesHome Next

    8.1. Numeric Types

    8.1.1. Integer Types
    8.1.2. Arbitrary Precision Numbers
    8.1.3. Floating-Point Types
    8.1.4. Serial Types

    +8.1. Numeric Types

    8.1. Numeric Types
    Prev UpChapter 8. Data TypesHome Next

    8.1. Numeric Types

    8.1.1. Integer Types
    8.1.2. Arbitrary Precision Numbers
    8.1.3. Floating-Point Types
    8.1.4. Serial Types

    Numeric types consist of two-, four-, and eight-byte integers, four- and eight-byte floating-point numbers, and selectable-precision decimals. Table 8.2 lists the @@ -303,4 +303,4 @@ automatically dropped when the owning column is dropped. You can drop the sequence without dropping the column, but this will force removal of the column default expression. -

    Prev Up Next
    Chapter 8. Data Types Home 8.2. Monetary Types
    \ No newline at end of file +

    Prev Up Next
    Chapter 8. Data Types Home 8.2. Monetary Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-oid.html postgresql-13-13.12/doc/src/sgml/html/datatype-oid.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-oid.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-oid.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.19. Object Identifier Types
    8.19. Object Identifier Types
    Prev UpChapter 8. Data TypesHome Next

    8.19. Object Identifier Types

    +8.19. Object Identifier Types

    8.19. Object Identifier Types
    Prev UpChapter 8. Data TypesHome Next

    8.19. Object Identifier Types

    Object identifiers (OIDs) are used internally by PostgreSQL as primary keys for various system tables. @@ -89,4 +89,4 @@ physical location of the row within its table.

    (The system columns are further explained in Section 5.5.) -

    Prev Up Next
    8.18. Domain Types Home 8.20. pg_lsn Type
    \ No newline at end of file +

    Prev Up Next
    8.18. Domain Types Home 8.20. pg_lsn Type
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-pg-lsn.html postgresql-13-13.12/doc/src/sgml/html/datatype-pg-lsn.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-pg-lsn.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-pg-lsn.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.20. pg_lsn Type
    8.20. pg_lsn Type
    Prev UpChapter 8. Data TypesHome Next

    8.20. pg_lsn Type

    +8.20. pg_lsn Type

    8.20. pg_lsn Type
    Prev UpChapter 8. Data TypesHome Next

    8.20. pg_lsn Type

    The pg_lsn data type can be used to store LSN (Log Sequence Number) data which is a pointer to a location in the WAL. This type is a representation of XLogRecPtr and an internal system type of @@ -13,4 +13,4 @@ >. Two LSNs can be subtracted using the - operator; the result is the number of bytes separating those write-ahead log locations. -

    Prev Up Next
    8.19. Object Identifier Types Home 8.21. Pseudo-Types
    \ No newline at end of file +

    Prev Up Next
    8.19. Object Identifier Types Home 8.21. Pseudo-Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-pseudo.html postgresql-13-13.12/doc/src/sgml/html/datatype-pseudo.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-pseudo.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-pseudo.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.21. Pseudo-Types
    8.21. Pseudo-Types
    Prev UpChapter 8. Data TypesHome Next

    8.21. Pseudo-Types

    +8.21. Pseudo-Types

    8.21. Pseudo-Types
    Prev UpChapter 8. Data TypesHome Next

    8.21. Pseudo-Types

    The PostgreSQL type system contains a number of special-purpose entries that are collectively called pseudo-types. A pseudo-type cannot be used as a @@ -51,4 +51,4 @@ follow this coding rule: do not create any function that is declared to return internal unless it has at least one internal argument. -

    Prev Up Next
    8.20. pg_lsn Type Home Chapter 9. Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    8.20. pg_lsn Type Home Chapter 9. Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-textsearch.html postgresql-13-13.12/doc/src/sgml/html/datatype-textsearch.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-textsearch.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-textsearch.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.11. Text Search Types
    8.11. Text Search Types
    Prev UpChapter 8. Data TypesHome Next

    8.11. Text Search Types

    8.11.1. tsvector
    8.11.2. tsquery

    +8.11. Text Search Types

    8.11. Text Search Types
    Prev UpChapter 8. Data TypesHome Next

    8.11. Text Search Types

    8.11.1. tsvector
    8.11.2. tsquery

    PostgreSQL provides two data types that are designed to support full text search, which is the activity of searching through a collection of natural-language documents @@ -193,4 +193,4 @@ 'postgradu':1 | 'postgr':*

    which will match the stemmed form of postgraduate. -

    Prev Up Next
    8.10. Bit String Types Home 8.12. UUID Type
    \ No newline at end of file +

    Prev Up Next
    8.10. Bit String Types Home 8.12. UUID Type
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-uuid.html postgresql-13-13.12/doc/src/sgml/html/datatype-uuid.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-uuid.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-uuid.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.12. UUID Type
    8.12. UUID Type
    Prev UpChapter 8. Data TypesHome Next

    8.12. UUID Type

    +8.12. UUID Type

    8.12. UUID Type
    Prev UpChapter 8. Data TypesHome Next

    8.12. UUID Type

    The data type uuid stores Universally Unique Identifiers (UUID) as defined by RFC 4122, ISO/IEC 9834-8:2005, and related standards. (Some systems refer to this data type as a globally unique identifier, or @@ -35,4 +35,4 @@

    See Section 9.14 for how to generate a UUID in PostgreSQL. -

    Prev Up Next
    8.11. Text Search Types Home 8.13. XML Type
    \ No newline at end of file +

    Prev Up Next
    8.11. Text Search Types Home 8.13. XML Type
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype-xml.html postgresql-13-13.12/doc/src/sgml/html/datatype-xml.html --- postgresql-13-13.11/doc/src/sgml/html/datatype-xml.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype-xml.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.13. XML Type
    8.13. XML Type
    Prev UpChapter 8. Data TypesHome Next

    8.13. XML Type

    8.13.1. Creating XML Values
    8.13.2. Encoding Handling
    8.13.3. Accessing XML Values

    +8.13. XML Type

    8.13. XML Type
    Prev UpChapter 8. Data TypesHome Next

    8.13. XML Type

    8.13.1. Creating XML Values
    8.13.2. Encoding Handling
    8.13.3. Accessing XML Values

    The xml data type can be used to store XML data. Its advantage over storing XML data in a text field is that it checks the input values for well-formedness, and there are support @@ -148,4 +148,4 @@ up full-document searches of XML data. The necessary preprocessing support is, however, not yet available in the PostgreSQL distribution. -

    Prev Up Next
    8.12. UUID Type Home 8.14. JSON Types
    \ No newline at end of file +

    Prev Up Next
    8.12. UUID Type Home 8.14. JSON Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datatype.html postgresql-13-13.12/doc/src/sgml/html/datatype.html --- postgresql-13-13.11/doc/src/sgml/html/datatype.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datatype.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 8. Data Types
    Chapter 8. Data Types
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 8. Data Types

    Table of Contents

    8.1. Numeric Types
    8.1.1. Integer Types
    8.1.2. Arbitrary Precision Numbers
    8.1.3. Floating-Point Types
    8.1.4. Serial Types
    8.2. Monetary Types
    8.3. Character Types
    8.4. Binary Data Types
    8.4.1. bytea Hex Format
    8.4.2. bytea Escape Format
    8.5. Date/Time Types
    8.5.1. Date/Time Input
    8.5.2. Date/Time Output
    8.5.3. Time Zones
    8.5.4. Interval Input
    8.5.5. Interval Output
    8.6. Boolean Type
    8.7. Enumerated Types
    8.7.1. Declaration of Enumerated Types
    8.7.2. Ordering
    8.7.3. Type Safety
    8.7.4. Implementation Details
    8.8. Geometric Types
    8.8.1. Points
    8.8.2. Lines
    8.8.3. Line Segments
    8.8.4. Boxes
    8.8.5. Paths
    8.8.6. Polygons
    8.8.7. Circles
    8.9. Network Address Types
    8.9.1. inet
    8.9.2. cidr
    8.9.3. inet vs. cidr
    8.9.4. macaddr
    8.9.5. macaddr8
    8.10. Bit String Types
    8.11. Text Search Types
    8.11.1. tsvector
    8.11.2. tsquery
    8.12. UUID Type
    8.13. XML Type
    8.13.1. Creating XML Values
    8.13.2. Encoding Handling
    8.13.3. Accessing XML Values
    8.14. JSON Types
    8.14.1. JSON Input and Output Syntax
    8.14.2. Designing JSON Documents
    8.14.3. jsonb Containment and Existence
    8.14.4. jsonb Indexing
    8.14.5. Transforms
    8.14.6. jsonpath Type
    8.15. Arrays
    8.15.1. Declaration of Array Types
    8.15.2. Array Value Input
    8.15.3. Accessing Arrays
    8.15.4. Modifying Arrays
    8.15.5. Searching in Arrays
    8.15.6. Array Input and Output Syntax
    8.16. Composite Types
    8.16.1. Declaration of Composite Types
    8.16.2. Constructing Composite Values
    8.16.3. Accessing Composite Types
    8.16.4. Modifying Composite Types
    8.16.5. Using Composite Types in Queries
    8.16.6. Composite Type Input and Output Syntax
    8.17. Range Types
    8.17.1. Built-in Range Types
    8.17.2. Examples
    8.17.3. Inclusive and Exclusive Bounds
    8.17.4. Infinite (Unbounded) Ranges
    8.17.5. Range Input/Output
    8.17.6. Constructing Ranges
    8.17.7. Discrete Range Types
    8.17.8. Defining New Range Types
    8.17.9. Indexing
    8.17.10. Constraints on Ranges
    8.18. Domain Types
    8.19. Object Identifier Types
    8.20. pg_lsn Type
    8.21. Pseudo-Types

    +Chapter 8. Data Types

    Chapter 8. Data Types
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 8. Data Types

    Table of Contents

    8.1. Numeric Types
    8.1.1. Integer Types
    8.1.2. Arbitrary Precision Numbers
    8.1.3. Floating-Point Types
    8.1.4. Serial Types
    8.2. Monetary Types
    8.3. Character Types
    8.4. Binary Data Types
    8.4.1. bytea Hex Format
    8.4.2. bytea Escape Format
    8.5. Date/Time Types
    8.5.1. Date/Time Input
    8.5.2. Date/Time Output
    8.5.3. Time Zones
    8.5.4. Interval Input
    8.5.5. Interval Output
    8.6. Boolean Type
    8.7. Enumerated Types
    8.7.1. Declaration of Enumerated Types
    8.7.2. Ordering
    8.7.3. Type Safety
    8.7.4. Implementation Details
    8.8. Geometric Types
    8.8.1. Points
    8.8.2. Lines
    8.8.3. Line Segments
    8.8.4. Boxes
    8.8.5. Paths
    8.8.6. Polygons
    8.8.7. Circles
    8.9. Network Address Types
    8.9.1. inet
    8.9.2. cidr
    8.9.3. inet vs. cidr
    8.9.4. macaddr
    8.9.5. macaddr8
    8.10. Bit String Types
    8.11. Text Search Types
    8.11.1. tsvector
    8.11.2. tsquery
    8.12. UUID Type
    8.13. XML Type
    8.13.1. Creating XML Values
    8.13.2. Encoding Handling
    8.13.3. Accessing XML Values
    8.14. JSON Types
    8.14.1. JSON Input and Output Syntax
    8.14.2. Designing JSON Documents
    8.14.3. jsonb Containment and Existence
    8.14.4. jsonb Indexing
    8.14.5. Transforms
    8.14.6. jsonpath Type
    8.15. Arrays
    8.15.1. Declaration of Array Types
    8.15.2. Array Value Input
    8.15.3. Accessing Arrays
    8.15.4. Modifying Arrays
    8.15.5. Searching in Arrays
    8.15.6. Array Input and Output Syntax
    8.16. Composite Types
    8.16.1. Declaration of Composite Types
    8.16.2. Constructing Composite Values
    8.16.3. Accessing Composite Types
    8.16.4. Modifying Composite Types
    8.16.5. Using Composite Types in Queries
    8.16.6. Composite Type Input and Output Syntax
    8.17. Range Types
    8.17.1. Built-in Range Types
    8.17.2. Examples
    8.17.3. Inclusive and Exclusive Bounds
    8.17.4. Infinite (Unbounded) Ranges
    8.17.5. Range Input/Output
    8.17.6. Constructing Ranges
    8.17.7. Discrete Range Types
    8.17.8. Defining New Range Types
    8.17.9. Indexing
    8.17.10. Constraints on Ranges
    8.18. Domain Types
    8.19. Object Identifier Types
    8.20. pg_lsn Type
    8.21. Pseudo-Types

    PostgreSQL has a rich set of native data types available to users. Users can add new types to PostgreSQL using the CREATE TYPE command. @@ -33,4 +33,4 @@ Some of the input and output functions are not invertible, i.e., the result of an output function might lose accuracy when compared to the original input. -

    Prev Up Next
    7.8. WITH Queries (Common Table Expressions) Home 8.1. Numeric Types
    \ No newline at end of file +

    Prev Up Next
    7.8. WITH Queries (Common Table Expressions) Home 8.1. Numeric Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-appendix.html postgresql-13-13.12/doc/src/sgml/html/datetime-appendix.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-appendix.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-appendix.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix B. Date/Time Support
    Appendix B. Date/Time Support
    Prev UpPart VIII. AppendixesHome Next

    Appendix B. Date/Time Support

    Table of Contents

    B.1. Date/Time Input Interpretation
    B.2. Handling of Invalid or Ambiguous Timestamps
    B.3. Date/Time Key Words
    B.4. Date/Time Configuration Files
    B.5. POSIX Time Zone Specifications
    B.6. History of Units
    B.7. Julian Dates

    +Appendix B. Date/Time Support

    Appendix B. Date/Time Support
    Prev UpPart VIII. AppendixesHome Next

    Appendix B. Date/Time Support

    Table of Contents

    B.1. Date/Time Input Interpretation
    B.2. Handling of Invalid or Ambiguous Timestamps
    B.3. Date/Time Key Words
    B.4. Date/Time Configuration Files
    B.5. POSIX Time Zone Specifications
    B.6. History of Units
    B.7. Julian Dates

    PostgreSQL uses an internal heuristic parser for all date/time input support. Dates and times are input as strings, and are broken up into distinct fields with a preliminary @@ -12,4 +12,4 @@ This appendix includes information on the content of these lookup tables and describes the steps used by the parser to decode dates and times. -

    Prev Up Next
    Appendix A. PostgreSQL Error Codes Home B.1. Date/Time Input Interpretation
    \ No newline at end of file +

    Prev Up Next
    Appendix A. PostgreSQL Error Codes Home B.1. Date/Time Input Interpretation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-config-files.html postgresql-13-13.12/doc/src/sgml/html/datetime-config-files.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-config-files.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-config-files.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.4. Date/Time Configuration Files
    B.4. Date/Time Configuration Files
    Prev UpAppendix B. Date/Time SupportHome Next

    B.4. Date/Time Configuration Files

    +B.4. Date/Time Configuration Files

    B.4. Date/Time Configuration Files
    Prev UpAppendix B. Date/Time SupportHome Next

    B.4. Date/Time Configuration Files

    Since timezone abbreviations are not well standardized, PostgreSQL provides a means to customize the set of abbreviations accepted by the server. The @@ -95,4 +95,4 @@ If you modify files in .../share/timezonesets/, it is up to you to make backups — a normal database dump will not include this directory. -

    Prev Up Next
    B.3. Date/Time Key Words Home B.5. POSIX Time Zone Specifications
    \ No newline at end of file +

    Prev Up Next
    B.3. Date/Time Key Words Home B.5. POSIX Time Zone Specifications
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-input-rules.html postgresql-13-13.12/doc/src/sgml/html/datetime-input-rules.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-input-rules.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-input-rules.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.1. Date/Time Input Interpretation
    B.1. Date/Time Input Interpretation
    Prev UpAppendix B. Date/Time SupportHome Next

    B.1. Date/Time Input Interpretation

    +B.1. Date/Time Input Interpretation

    B.1. Date/Time Input Interpretation
    Prev UpAppendix B. Date/Time SupportHome Next

    B.1. Date/Time Input Interpretation

    Date/time input strings are decoded using the following procedure.

    1. Break the input string into tokens and categorize each token as @@ -71,4 +71,4 @@ Gregorian years AD 1–99 can be entered by using 4 digits with leading zeros (e.g., 0099 is AD 99).

    -

    Prev Up Next
    Appendix B. Date/Time Support Home B.2. Handling of Invalid or Ambiguous Timestamps
    \ No newline at end of file +

    Prev Up Next
    Appendix B. Date/Time Support Home B.2. Handling of Invalid or Ambiguous Timestamps
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-invalid-input.html postgresql-13-13.12/doc/src/sgml/html/datetime-invalid-input.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-invalid-input.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-invalid-input.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.2. Handling of Invalid or Ambiguous Timestamps
    B.2. Handling of Invalid or Ambiguous Timestamps
    Prev UpAppendix B. Date/Time SupportHome Next

    B.2. Handling of Invalid or Ambiguous Timestamps

    +B.2. Handling of Invalid or Ambiguous Timestamps

    B.2. Handling of Invalid or Ambiguous Timestamps
    Prev UpAppendix B. Date/Time SupportHome Next

    B.2. Handling of Invalid or Ambiguous Timestamps

    Ordinarily, if a date/time string is syntactically valid but contains out-of-range field values, an error will be thrown. For example, input specifying the 31st of February will be rejected. @@ -59,4 +59,4 @@ abbreviation that corresponds to a fixed UTC offset. The rule just given applies only when it is necessary to infer a UTC offset for a time zone in which the offset varies. -

    Prev Up Next
    B.1. Date/Time Input Interpretation Home B.3. Date/Time Key Words
    \ No newline at end of file +

    Prev Up Next
    B.1. Date/Time Input Interpretation Home B.3. Date/Time Key Words
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-julian-dates.html postgresql-13-13.12/doc/src/sgml/html/datetime-julian-dates.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-julian-dates.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-julian-dates.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.7. Julian Dates
    B.7. Julian Dates
    Prev UpAppendix B. Date/Time SupportHome Next

    B.7. Julian Dates

    +B.7. Julian Dates

    B.7. Julian Dates
    Prev UpAppendix B. Date/Time SupportHome Next

    B.7. Julian Dates

    The Julian Date system is a method for numbering days. It is unrelated to the Julian calendar, though it is confusingly @@ -45,4 +45,4 @@ 2459389 (1 row)

    -

    Prev Up Next
    B.6. History of Units Home Appendix C. SQL Key Words
    \ No newline at end of file +

    Prev Up Next
    B.6. History of Units Home Appendix C. SQL Key Words
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-keywords.html postgresql-13-13.12/doc/src/sgml/html/datetime-keywords.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-keywords.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-keywords.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.3. Date/Time Key Words
    B.3. Date/Time Key Words
    Prev UpAppendix B. Date/Time SupportHome Next

    B.3. Date/Time Key Words

    +B.3. Date/Time Key Words

    B.3. Date/Time Key Words
    Prev UpAppendix B. Date/Time SupportHome Next

    B.3. Date/Time Key Words

    Table B.1 shows the tokens that are recognized as names of months.

    Table B.1. Month Names

    MonthAbbreviations
    JanuaryJan
    FebruaryFeb
    MarchMar
    AprilApr
    May 
    JuneJun
    JulyJul
    AugustAug
    SeptemberSep, Sept
    OctoberOct
    NovemberNov
    DecemberDec

    @@ -8,4 +8,4 @@

    Table B.2. Day of the Week Names

    DayAbbreviations
    SundaySun
    MondayMon
    TuesdayTue, Tues
    WednesdayWed, Weds
    ThursdayThu, Thur, Thurs
    FridayFri
    SaturdaySat

    Table B.3 shows the tokens that serve various modifier purposes. -

    Table B.3. Date/Time Field Modifiers

    IdentifierDescription
    AMTime is before 12:00
    ATIgnored
    JULIAN, JD, JNext field is Julian Date
    ONIgnored
    PMTime is on or after 12:00
    TNext field is time

    Prev Up Next
    B.2. Handling of Invalid or Ambiguous Timestamps Home B.4. Date/Time Configuration Files
    \ No newline at end of file +

    Table B.3. Date/Time Field Modifiers

    IdentifierDescription
    AMTime is before 12:00
    ATIgnored
    JULIAN, JD, JNext field is Julian Date
    ONIgnored
    PMTime is on or after 12:00
    TNext field is time

    Prev Up Next
    B.2. Handling of Invalid or Ambiguous Timestamps Home B.4. Date/Time Configuration Files
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-posix-timezone-specs.html postgresql-13-13.12/doc/src/sgml/html/datetime-posix-timezone-specs.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-posix-timezone-specs.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-posix-timezone-specs.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.5. POSIX Time Zone Specifications
    B.5. POSIX Time Zone Specifications
    Prev UpAppendix B. Date/Time SupportHome Next

    B.5. POSIX Time Zone Specifications

    +B.5. POSIX Time Zone Specifications

    B.5. POSIX Time Zone Specifications
    Prev UpAppendix B. Date/Time SupportHome Next

    B.5. POSIX Time Zone Specifications

    PostgreSQL can accept time zone specifications that are written according to the POSIX standard's rules for the TZ environment @@ -132,4 +132,4 @@ zone abbreviation(s). For example, SET TIMEZONE TO FOOBAR0 will work, leaving the system effectively using a rather peculiar abbreviation for UTC. -

    Prev Up Next
    B.4. Date/Time Configuration Files Home B.6. History of Units
    \ No newline at end of file +

    Prev Up Next
    B.4. Date/Time Configuration Files Home B.6. History of Units
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/datetime-units-history.html postgresql-13-13.12/doc/src/sgml/html/datetime-units-history.html --- postgresql-13-13.11/doc/src/sgml/html/datetime-units-history.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/datetime-units-history.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -B.6. History of Units
    B.6. History of Units
    Prev UpAppendix B. Date/Time SupportHome Next

    B.6. History of Units

    +B.6. History of Units

    B.6. History of Units
    Prev UpAppendix B. Date/Time SupportHome Next

    B.6. History of Units

    The SQL standard states that “Within the definition of a ‘datetime literal’, the ‘datetime values’ are constrained by the natural rules for dates and @@ -84,4 +84,4 @@ The People's Republic of China uses the Gregorian calendar for civil purposes. The Chinese calendar is used for determining festivals. -

    Prev Up Next
    B.5. POSIX Time Zone Specifications Home B.7. Julian Dates
    \ No newline at end of file +

    Prev Up Next
    B.5. POSIX Time Zone Specifications Home B.7. Julian Dates
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dblink.html postgresql-13-13.12/doc/src/sgml/html/dblink.html --- postgresql-13-13.11/doc/src/sgml/html/dblink.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dblink.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.10. dblink
    F.10. dblink
    Prev UpAppendix F. Additional Supplied ModulesHome Next
    Prev Up Next
    5.5. System Columns Home 5.7. Privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-basics.html postgresql-13-13.12/doc/src/sgml/html/ddl-basics.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-basics.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-basics.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.1. Table Basics
    5.1. Table Basics
    Prev UpChapter 5. Data DefinitionHome Next

    5.1. Table Basics

    +5.1. Table Basics

    5.1. Table Basics
    Prev UpChapter 5. Data DefinitionHome Next

    5.1. Table Basics

    A table in a relational database is much like a table on paper: It consists of rows and columns. The number and order of the columns is fixed, and each column has a name. The number of rows is @@ -98,4 +98,4 @@ security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter 6 and read the rest of this chapter later. -

    Prev Up Next
    Chapter 5. Data Definition Home 5.2. Default Values
    \ No newline at end of file +

    Prev Up Next
    Chapter 5. Data Definition Home 5.2. Default Values
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-constraints.html postgresql-13-13.12/doc/src/sgml/html/ddl-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-constraints.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-constraints.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.4. Constraints
    5.4. Constraints
    Prev UpChapter 5. Data DefinitionHome Next

    5.4. Constraints

    5.4.1. Check Constraints
    5.4.2. Not-Null Constraints
    5.4.3. Unique Constraints
    5.4.4. Primary Keys
    5.4.5. Foreign Keys
    5.4.6. Exclusion Constraints

    +5.4. Constraints

    5.4. Constraints
    Prev UpChapter 5. Data DefinitionHome Next

    5.4. Constraints

    5.4.1. Check Constraints
    5.4.2. Not-Null Constraints
    5.4.3. Unique Constraints
    5.4.4. Primary Keys
    5.4.5. Foreign Keys
    5.4.6. Exclusion Constraints

    Data types are a way to limit the kind of data that can be stored in a table. For many applications, however, the constraint they provide is too coarse. For example, a column containing a product @@ -537,4 +537,4 @@

    Adding an exclusion constraint will automatically create an index of the type specified in the constraint declaration. -

    Prev Up Next
    5.3. Generated Columns Home 5.5. System Columns
    \ No newline at end of file +

    Prev Up Next
    5.3. Generated Columns Home 5.5. System Columns
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-default.html postgresql-13-13.12/doc/src/sgml/html/ddl-default.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-default.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-default.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.2. Default Values
    5.2. Default Values
    Prev UpChapter 5. Data DefinitionHome Next

    5.2. Default Values

    +5.2. Default Values

    5.2. Default Values
    Prev UpChapter 5. Data DefinitionHome Next

    5.2. Default Values

    A column can be assigned a default value. When a new row is created and no values are specified for some of the columns, those columns will be filled with their respective default values. A @@ -46,4 +46,4 @@ );

    The SERIAL shorthand is discussed further in Section 8.1.4. -

    Prev Up Next
    5.1. Table Basics Home 5.3. Generated Columns
    \ No newline at end of file +

    Prev Up Next
    5.1. Table Basics Home 5.3. Generated Columns
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-depend.html postgresql-13-13.12/doc/src/sgml/html/ddl-depend.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-depend.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-depend.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.14. Dependency Tracking
    5.14. Dependency Tracking
    Prev UpChapter 5. Data DefinitionHome Next

    5.14. Dependency Tracking

    +5.14. Dependency Tracking

    5.14. Dependency Tracking
    Prev UpChapter 5. Data DefinitionHome Next

    5.14. Dependency Tracking

    When you create complex database structures involving many tables with foreign key constraints, views, triggers, functions, etc. you implicitly create a net of dependencies between the objects. @@ -80,4 +80,4 @@ there are also benefits. The function is still valid in some sense if the table is missing, though executing it would cause an error; creating a new table of the same name would allow the function to work again. -

    Prev Up Next
    5.13. Other Database Objects Home Chapter 6. Data Manipulation
    \ No newline at end of file +

    Prev Up Next
    5.13. Other Database Objects Home Chapter 6. Data Manipulation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-foreign-data.html postgresql-13-13.12/doc/src/sgml/html/ddl-foreign-data.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-foreign-data.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-foreign-data.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.12. Foreign Data
    5.12. Foreign Data
    Prev UpChapter 5. Data DefinitionHome Next

    5.12. Foreign Data

    +5.12. Foreign Data

    5.12. Foreign Data
    Prev UpChapter 5. Data DefinitionHome Next

    5.12. Foreign Data

    PostgreSQL implements portions of the SQL/MED specification, allowing you to access data that resides outside PostgreSQL using regular SQL queries. Such data is referred to as @@ -38,4 +38,4 @@ CREATE USER MAPPING, CREATE FOREIGN TABLE, and IMPORT FOREIGN SCHEMA. -

    Prev Up Next
    5.11. Table Partitioning Home 5.13. Other Database Objects
    \ No newline at end of file +

    Prev Up Next
    5.11. Table Partitioning Home 5.13. Other Database Objects
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-generated-columns.html postgresql-13-13.12/doc/src/sgml/html/ddl-generated-columns.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-generated-columns.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-generated-columns.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.3. Generated Columns
    5.3. Generated Columns
    Prev UpChapter 5. Data DefinitionHome Next

    5.3. Generated Columns

    +5.3. Generated Columns

    5.3. Generated Columns
    Prev UpChapter 5. Data DefinitionHome Next

    5.3. Generated Columns

    A generated column is a special column that is always computed from other columns. Thus, it is for columns what a view is for tables. There are two kinds of generated columns: stored and virtual. A stored generated column @@ -82,4 +82,4 @@ generated columns. But conversely, it is not allowed to access generated columns in BEFORE triggers.

    -

    Prev Up Next
    5.2. Default Values Home 5.4. Constraints
    \ No newline at end of file +

    Prev Up Next
    5.2. Default Values Home 5.4. Constraints
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-inherit.html postgresql-13-13.12/doc/src/sgml/html/ddl-inherit.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-inherit.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-inherit.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.10. Inheritance
    5.10. Inheritance
    Prev UpChapter 5. Data DefinitionHome Next

    5.10. Inheritance

    5.10.1. Caveats

    +5.10. Inheritance

    5.10. Inheritance
    Prev UpChapter 5. Data DefinitionHome Next

    5.10. Inheritance

    5.10.1. Caveats

    PostgreSQL implements table inheritance, which can be a useful tool for database designers. (SQL:1999 and later define a type inheritance feature, which differs in many @@ -286,4 +286,4 @@ implemented for declarative partitioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. -

    Prev Up Next
    5.9. Schemas Home 5.11. Table Partitioning
    \ No newline at end of file +

    Prev Up Next
    5.9. Schemas Home 5.11. Table Partitioning
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-others.html postgresql-13-13.12/doc/src/sgml/html/ddl-others.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-others.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-others.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.13. Other Database Objects
    5.13. Other Database Objects
    Prev UpChapter 5. Data DefinitionHome Next

    5.13. Other Database Objects

    +5.13. Other Database Objects

    5.13. Other Database Objects
    Prev UpChapter 5. Data DefinitionHome Next

    5.13. Other Database Objects

    Tables are the central objects in a relational database structure, because they hold your data. But they are not the only objects that exist in a database. Many other kinds of objects can be @@ -17,4 +17,4 @@

    Detailed information on these topics appears in Part V. -

    Prev Up Next
    5.12. Foreign Data Home 5.14. Dependency Tracking
    \ No newline at end of file +

    Prev Up Next
    5.12. Foreign Data Home 5.14. Dependency Tracking
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-partitioning.html postgresql-13-13.12/doc/src/sgml/html/ddl-partitioning.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-partitioning.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-partitioning.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.11. Table Partitioning
    5.11. Table Partitioning
    Prev UpChapter 5. Data DefinitionHome Next

    5.11. Table Partitioning

    5.11.1. Overview
    5.11.2. Declarative Partitioning
    5.11.3. Partitioning Using Inheritance
    5.11.4. Partition Pruning
    5.11.5. Partitioning and Constraint Exclusion
    5.11.6. Best Practices for Declarative Partitioning

    +5.11. Table Partitioning

    5.11. Table Partitioning
    Prev UpChapter 5. Data DefinitionHome Next

    5.11. Table Partitioning

    5.11.1. Overview
    5.11.2. Declarative Partitioning
    5.11.3. Partitioning Using Inheritance
    5.11.4. Partition Pruning
    5.11.5. Partitioning and Constraint Exclusion
    5.11.6. Best Practices for Declarative Partitioning

    PostgreSQL supports basic table partitioning. This section describes why and how to implement partitioning as part of your database design. @@ -993,4 +993,4 @@ painfully slow. Simulations of the intended workload are often beneficial for optimizing the partitioning strategy. Never just assume that more partitions are better than fewer partitions, nor vice-versa. -

    Prev Up Next
    5.10. Inheritance Home 5.12. Foreign Data
    \ No newline at end of file +

    Prev Up Next
    5.10. Inheritance Home 5.12. Foreign Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-priv.html postgresql-13-13.12/doc/src/sgml/html/ddl-priv.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-priv.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-priv.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.7. Privileges
    5.7. Privileges
    Prev UpChapter 5. Data DefinitionHome Next

    5.7. Privileges

    +5.7. Privileges

    5.7. Privileges
    Prev UpChapter 5. Data DefinitionHome Next

    5.7. Privileges

    When an object is created, it is assigned an owner. The owner is normally the role that executed the creation statement. For most kinds of objects, the initial state is that only the owner @@ -293,4 +293,4 @@ Notice that the owner's implicit grant options are not marked in the access privileges display. A * will appear only when grant options have been explicitly granted to someone. -

    Prev Up Next
    5.6. Modifying Tables Home 5.8. Row Security Policies
    \ No newline at end of file +

    Prev Up Next
    5.6. Modifying Tables Home 5.8. Row Security Policies
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-rowsecurity.html postgresql-13-13.12/doc/src/sgml/html/ddl-rowsecurity.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-rowsecurity.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-rowsecurity.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.8. Row Security Policies
    5.8. Row Security Policies
    Prev UpChapter 5. Data DefinitionHome Next

    5.8. Row Security Policies

    +5.8. Row Security Policies

    5.8. Row Security Policies
    Prev UpChapter 5. Data DefinitionHome Next

    5.8. Row Security Policies

    In addition to the SQL-standard privilege system available through GRANT, tables can have row security policies that restrict, @@ -385,4 +385,4 @@

    For additional details see CREATE POLICY and ALTER TABLE. -

    Prev Up Next
    5.7. Privileges Home 5.9. Schemas
    \ No newline at end of file +

    Prev Up Next
    5.7. Privileges Home 5.9. Schemas
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-schemas.html postgresql-13-13.12/doc/src/sgml/html/ddl-schemas.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-schemas.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-schemas.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.9. Schemas
    5.9. Schemas
    Prev UpChapter 5. Data DefinitionHome Next

    5.9. Schemas

    5.9.1. Creating a Schema
    5.9.2. The Public Schema
    5.9.3. The Schema Search Path
    5.9.4. Schemas and Privileges
    5.9.5. The System Catalog Schema
    5.9.6. Usage Patterns
    5.9.7. Portability

    +5.9. Schemas

    5.9. Schemas
    Prev UpChapter 5. Data DefinitionHome Next

    5.9. Schemas

    5.9.1. Creating a Schema
    5.9.2. The Public Schema
    5.9.3. The Schema Search Path
    5.9.4. Schemas and Privileges
    5.9.5. The System Catalog Schema
    5.9.6. Usage Patterns
    5.9.7. Portability

    A PostgreSQL database cluster contains one or more named databases. Roles and a few other object types are shared across the entire cluster. A client connection to the server @@ -317,4 +317,4 @@ limited) cross-database access. If you need to work with those systems, then maximum portability would be achieved by not using schemas at all. -

    Prev Up Next
    5.8. Row Security Policies Home 5.10. Inheritance
    \ No newline at end of file +

    Prev Up Next
    5.8. Row Security Policies Home 5.10. Inheritance
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl-system-columns.html postgresql-13-13.12/doc/src/sgml/html/ddl-system-columns.html --- postgresql-13-13.11/doc/src/sgml/html/ddl-system-columns.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl-system-columns.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -5.5. System Columns
    5.5. System Columns
    Prev UpChapter 5. Data DefinitionHome Next

    5.5. System Columns

    +5.5. System Columns

    5.5. System Columns
    Prev UpChapter 5. Data DefinitionHome Next

    5.5. System Columns

    Every table has several system columns that are implicitly defined by the system. Therefore, these names cannot be used as names of user-defined columns. (Note that these @@ -54,4 +54,4 @@ SQL commands, not the number of rows processed. Also, only commands that actually modify the database contents will consume a command identifier. -

    Prev Up Next
    5.4. Constraints Home 5.6. Modifying Tables
    \ No newline at end of file +

    Prev Up Next
    5.4. Constraints Home 5.6. Modifying Tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ddl.html postgresql-13-13.12/doc/src/sgml/html/ddl.html --- postgresql-13-13.11/doc/src/sgml/html/ddl.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ddl.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 5. Data Definition
    Chapter 5. Data Definition
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 5. Data Definition

    Table of Contents

    5.1. Table Basics
    5.2. Default Values
    5.3. Generated Columns
    5.4. Constraints
    5.4.1. Check Constraints
    5.4.2. Not-Null Constraints
    5.4.3. Unique Constraints
    5.4.4. Primary Keys
    5.4.5. Foreign Keys
    5.4.6. Exclusion Constraints
    5.5. System Columns
    5.6. Modifying Tables
    5.6.1. Adding a Column
    5.6.2. Removing a Column
    5.6.3. Adding a Constraint
    5.6.4. Removing a Constraint
    5.6.5. Changing a Column's Default Value
    5.6.6. Changing a Column's Data Type
    5.6.7. Renaming a Column
    5.6.8. Renaming a Table
    5.7. Privileges
    5.8. Row Security Policies
    5.9. Schemas
    5.9.1. Creating a Schema
    5.9.2. The Public Schema
    5.9.3. The Schema Search Path
    5.9.4. Schemas and Privileges
    5.9.5. The System Catalog Schema
    5.9.6. Usage Patterns
    5.9.7. Portability
    5.10. Inheritance
    5.10.1. Caveats
    5.11. Table Partitioning
    5.11.1. Overview
    5.11.2. Declarative Partitioning
    5.11.3. Partitioning Using Inheritance
    5.11.4. Partition Pruning
    5.11.5. Partitioning and Constraint Exclusion
    5.11.6. Best Practices for Declarative Partitioning
    5.12. Foreign Data
    5.13. Other Database Objects
    5.14. Dependency Tracking

    +Chapter 5. Data Definition

    Chapter 5. Data Definition
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    4.3. Calling Functions Home 5.1. Table Basics
    \ No newline at end of file +

    Prev Up Next
    4.3. Calling Functions Home 5.1. Table Basics
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/default-roles.html postgresql-13-13.12/doc/src/sgml/html/default-roles.html --- postgresql-13-13.11/doc/src/sgml/html/default-roles.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/default-roles.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.5. Default Roles
    21.5. Default Roles
    Prev UpChapter 21. Database RolesHome Next

    21.5. Default Roles

    +21.5. Default Roles

    21.5. Default Roles
    Prev UpChapter 21. Database RolesHome Next

    21.5. Default Roles

    PostgreSQL provides a set of default roles which provide access to certain, commonly needed, privileged capabilities and information. Administrators can GRANT these roles to users and/or @@ -52,4 +52,4 @@ 

     GRANT pg_signal_backend TO admin_user;

    -

    Prev Up Next
    21.4. Dropping Roles Home 21.6. Function Security
    \ No newline at end of file +

    Prev Up Next
    21.4. Dropping Roles Home 21.6. Function Security
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dict-int.html postgresql-13-13.12/doc/src/sgml/html/dict-int.html --- postgresql-13-13.11/doc/src/sgml/html/dict-int.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dict-int.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.11. dict_int
    F.11. dict_int
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.11. dict_int

    F.11.1. Configuration
    F.11.2. Usage

    +F.11. dict_int

    F.11. dict_int
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.11. dict_int

    F.11.1. Configuration
    F.11.2. Usage

    dict_int is an example of an add-on dictionary template for full-text search. The motivation for this example dictionary is to control the indexing of integers (signed and unsigned), allowing such @@ -59,4 +59,4 @@ ALTER MAPPING FOR int, uint WITH intdict;

    -

    Prev Up Next
    dblink_build_sql_update Home F.12. dict_xsyn
    \ No newline at end of file +

    Prev Up Next
    dblink_build_sql_update Home F.12. dict_xsyn
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dict-xsyn.html postgresql-13-13.12/doc/src/sgml/html/dict-xsyn.html --- postgresql-13-13.11/doc/src/sgml/html/dict-xsyn.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dict-xsyn.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.12. dict_xsyn
    F.12. dict_xsyn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.12. dict_xsyn

    F.12.1. Configuration
    F.12.2. Usage

    +F.12. dict_xsyn

    F.12. dict_xsyn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.12. dict_xsyn

    F.12.1. Configuration
    F.12.2. Usage

    dict_xsyn (Extended Synonym Dictionary) is an example of an add-on dictionary template for full-text search. This dictionary type replaces words with groups of their synonyms, and so makes it possible to @@ -94,4 +94,4 @@ ALTER MAPPING FOR word, asciiword WITH xsyn, english_stem;

    -

    Prev Up Next
    F.11. dict_int Home F.13. earthdistance
    \ No newline at end of file +

    Prev Up Next
    F.11. dict_int Home F.13. earthdistance
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/different-replication-solutions.html postgresql-13-13.12/doc/src/sgml/html/different-replication-solutions.html --- postgresql-13-13.11/doc/src/sgml/html/different-replication-solutions.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/different-replication-solutions.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -26.1. Comparison of Different Solutions
    26.1. Comparison of Different Solutions
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.1. Comparison of Different Solutions

    Shared Disk Failover

    +26.1. Comparison of Different Solutions

    26.1. Comparison of Different Solutions
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.1. Comparison of Different Solutions

    Shared Disk Failover

    Shared disk failover avoids synchronization overhead by having only one copy of the database. It uses a single disk array that is shared by multiple servers. If the main database server fails, the standby server @@ -136,4 +136,4 @@ taken PostgreSQL and created commercial closed-source solutions with unique failover, replication, and load balancing capabilities. These are not discussed here. -

    Prev Up Next
    Chapter 26. High Availability, Load Balancing, and Replication Home 26.2. Log-Shipping Standby Servers
    \ No newline at end of file +

    Prev Up Next
    Chapter 26. High Availability, Load Balancing, and Replication Home 26.2. Log-Shipping Standby Servers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/disk-full.html postgresql-13-13.12/doc/src/sgml/html/disk-full.html --- postgresql-13-13.11/doc/src/sgml/html/disk-full.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/disk-full.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -28.2. Disk Full Failure
    28.2. Disk Full Failure
    Prev UpChapter 28. Monitoring Disk UsageHome Next

    28.2. Disk Full Failure

    +28.2. Disk Full Failure

    28.2. Disk Full Failure
    Prev UpChapter 28. Monitoring Disk UsageHome Next

    28.2. Disk Full Failure

    The most important disk monitoring task of a database administrator is to make sure the disk doesn't become full. A filled data disk will not result in data corruption, but it might prevent useful activity @@ -17,4 +17,4 @@ will naturally be subject to whatever quota is placed on the user the server runs as. Exceeding the quota will have the same bad effects as running out of disk space entirely. -

    Prev Up Next
    28.1. Determining Disk Usage Home Chapter 29. Reliability and the Write-Ahead Log
    \ No newline at end of file +

    Prev Up Next
    28.1. Determining Disk Usage Home Chapter 29. Reliability and the Write-Ahead Log
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/disk-usage.html postgresql-13-13.12/doc/src/sgml/html/disk-usage.html --- postgresql-13-13.11/doc/src/sgml/html/disk-usage.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/disk-usage.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -28.1. Determining Disk Usage
    28.1. Determining Disk Usage
    Prev UpChapter 28. Monitoring Disk UsageHome Next

    28.1. Determining Disk Usage

    +28.1. Determining Disk Usage

    28.1. Determining Disk Usage
    Prev UpChapter 28. Monitoring Disk UsageHome Next

    28.1. Determining Disk Usage

    Each table has a primary heap disk file where most of the data is stored. If the table has any columns with potentially-wide values, there also might be a TOAST file associated with the table, @@ -80,4 +80,4 @@ bigtable | 3290 customer | 3144

    -

    Prev Up Next
    Chapter 28. Monitoring Disk Usage Home 28.2. Disk Full Failure
    \ No newline at end of file +

    Prev Up Next
    Chapter 28. Monitoring Disk Usage Home 28.2. Disk Full Failure
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/diskusage.html postgresql-13-13.12/doc/src/sgml/html/diskusage.html --- postgresql-13-13.11/doc/src/sgml/html/diskusage.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/diskusage.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 28. Monitoring Disk Usage
    Chapter 28. Monitoring Disk Usage
    Prev UpPart III. Server AdministrationHome Next

    Chapter 28. Monitoring Disk Usage

    Table of Contents

    28.1. Determining Disk Usage
    28.2. Disk Full Failure

    +Chapter 28. Monitoring Disk Usage

    Chapter 28. Monitoring Disk Usage
    Prev UpPart III. Server AdministrationHome Next

    Chapter 28. Monitoring Disk Usage

    Table of Contents

    28.1. Determining Disk Usage
    28.2. Disk Full Failure

    This chapter discusses how to monitor the disk usage of a PostgreSQL database system. -

    Prev Up Next
    27.5. Dynamic Tracing Home 28.1. Determining Disk Usage
    \ No newline at end of file +

    Prev Up Next
    27.5. Dynamic Tracing Home 28.1. Determining Disk Usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dml-delete.html postgresql-13-13.12/doc/src/sgml/html/dml-delete.html --- postgresql-13-13.11/doc/src/sgml/html/dml-delete.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dml-delete.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -6.3. Deleting Data
    6.3. Deleting Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.3. Deleting Data

    +6.3. Deleting Data

    6.3. Deleting Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.3. Deleting Data

    So far we have explained how to add data to tables and how to change data. What remains is to discuss how to remove data that is no longer needed. Just as adding data is only possible in whole @@ -25,4 +25,4 @@ DELETE FROM products;

    then all rows in the table will be deleted! Caveat programmer. -

    Prev Up Next
    6.2. Updating Data Home 6.4. Returning Data from Modified Rows
    \ No newline at end of file +

    Prev Up Next
    6.2. Updating Data Home 6.4. Returning Data from Modified Rows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dml-insert.html postgresql-13-13.12/doc/src/sgml/html/dml-insert.html --- postgresql-13-13.11/doc/src/sgml/html/dml-insert.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dml-insert.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -6.1. Inserting Data
    6.1. Inserting Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.1. Inserting Data

    +6.1. Inserting Data

    6.1. Inserting Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.1. Inserting Data

    When a table is created, it contains no data. The first thing to do before a database can be of much use is to insert data. Data is conceptually inserted one row at a time. Of course you can also @@ -78,4 +78,4 @@ command, but is more efficient. Refer to Section 14.4 for more information on improving bulk loading performance. -

    Prev Up Next
    Chapter 6. Data Manipulation Home 6.2. Updating Data
    \ No newline at end of file +

    Prev Up Next
    Chapter 6. Data Manipulation Home 6.2. Updating Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dml-returning.html postgresql-13-13.12/doc/src/sgml/html/dml-returning.html --- postgresql-13-13.11/doc/src/sgml/html/dml-returning.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dml-returning.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -6.4. Returning Data from Modified Rows
    6.4. Returning Data from Modified Rows
    Prev UpChapter 6. Data ManipulationHome Next

    6.4. Returning Data from Modified Rows

    +6.4. Returning Data from Modified Rows

    6.4. Returning Data from Modified Rows
    Prev UpChapter 6. Data ManipulationHome Next

    6.4. Returning Data from Modified Rows

    Sometimes it is useful to obtain data from modified rows while they are being manipulated. The INSERT, UPDATE, and DELETE commands all have an @@ -50,4 +50,4 @@ the data available to RETURNING is the row as modified by the triggers. Thus, inspecting columns computed by triggers is another common use-case for RETURNING. -

    Prev Up Next
    6.3. Deleting Data Home Chapter 7. Queries
    \ No newline at end of file +

    Prev Up Next
    6.3. Deleting Data Home Chapter 7. Queries
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dml-update.html postgresql-13-13.12/doc/src/sgml/html/dml-update.html --- postgresql-13-13.11/doc/src/sgml/html/dml-update.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dml-update.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -6.2. Updating Data
    6.2. Updating Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.2. Updating Data

    +6.2. Updating Data

    6.2. Updating Data
    Prev UpChapter 6. Data ManipulationHome Next

    6.2. Updating Data

    The modification of data that is already in the database is referred to as updating. You can update individual rows, all the rows in a table, or a subset of all rows. Each column can be @@ -58,4 +58,4 @@ 

     UPDATE mytable SET a = 5, b = 3, c = 1 WHERE a > 0;

    -

    Prev Up Next
    6.1. Inserting Data Home 6.3. Deleting Data
    \ No newline at end of file +

    Prev Up Next
    6.1. Inserting Data Home 6.3. Deleting Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dml.html postgresql-13-13.12/doc/src/sgml/html/dml.html --- postgresql-13-13.11/doc/src/sgml/html/dml.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dml.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,9 +1,9 @@ -Chapter 6. Data Manipulation
    Chapter 6. Data Manipulation
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 6. Data Manipulation

    Table of Contents

    6.1. Inserting Data
    6.2. Updating Data
    6.3. Deleting Data
    6.4. Returning Data from Modified Rows

    +Chapter 6. Data Manipulation

    Chapter 6. Data Manipulation
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 6. Data Manipulation

    Table of Contents

    6.1. Inserting Data
    6.2. Updating Data
    6.3. Deleting Data
    6.4. Returning Data from Modified Rows

    The previous chapter discussed how to create tables and other structures to hold your data. Now it is time to fill the tables with data. This chapter covers how to insert, update, and delete table data. The chapter after this will finally explain how to extract your long-lost data from the database. -

    Prev Up Next
    5.14. Dependency Tracking Home 6.1. Inserting Data
    \ No newline at end of file +

    Prev Up Next
    5.14. Dependency Tracking Home 6.1. Inserting Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide-authoring.html postgresql-13-13.12/doc/src/sgml/html/docguide-authoring.html --- postgresql-13-13.11/doc/src/sgml/html/docguide-authoring.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide-authoring.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -J.4. Documentation Authoring
    J.4. Documentation Authoring
    Prev UpAppendix J. DocumentationHome Next

    J.4. Documentation Authoring

    J.4.1. Emacs

    +J.4. Documentation Authoring

    J.4. Documentation Authoring
    Prev UpAppendix J. DocumentationHome Next

    J.4. Documentation Authoring

    J.4.1. Emacs

    The documentation sources are most conveniently modified with an editor that has a mode for editing XML, and even more so if it has some awareness of XML schema languages so that it can know about @@ -20,4 +20,4 @@

    src/tools/editors/emacs.samples contains recommended settings for this mode. -

    Prev Up Next
    J.3. Building the Documentation Home J.5. Style Guide
    \ No newline at end of file +

    Prev Up Next
    J.3. Building the Documentation Home J.5. Style Guide
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide-build.html postgresql-13-13.12/doc/src/sgml/html/docguide-build.html --- postgresql-13-13.11/doc/src/sgml/html/docguide-build.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide-build.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -J.3. Building the Documentation
    J.3. Building the Documentation
    Prev UpAppendix J. DocumentationHome Next

    J.3. Building the Documentation

    J.3.1. HTML
    J.3.2. Manpages
    J.3.3. PDF
    J.3.4. Plain Text Files
    J.3.5. Syntax Check

    +J.3. Building the Documentation

    J.3. Building the Documentation
    Prev UpAppendix J. DocumentationHome Next

    J.3. Building the Documentation

    J.3.1. HTML
    J.3.2. Manpages
    J.3.3. PDF
    J.3.4. Plain Text Files
    J.3.5. Syntax Check

    Once you have everything set up, change to the directory doc/src/sgml and run one of the commands described in the following subsections to build the @@ -88,4 +88,4 @@ 

     doc/src/sgml$ make check

    -

    Prev Up Next
    J.2. Tool Sets Home J.4. Documentation Authoring
    \ No newline at end of file +

    Prev Up Next
    J.2. Tool Sets Home J.4. Documentation Authoring
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide-docbook.html postgresql-13-13.12/doc/src/sgml/html/docguide-docbook.html --- postgresql-13-13.11/doc/src/sgml/html/docguide-docbook.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide-docbook.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -J.1. DocBook
    J.1. DocBook
    Prev UpAppendix J. DocumentationHome Next

    J.1. DocBook

    +J.1. DocBook

    J.1. DocBook
    Prev UpAppendix J. DocumentationHome Next

    J.1. DocBook

    The documentation sources are written in DocBook, which is a markup language defined in XML. In what @@ -20,4 +20,4 @@ FreeBSD Documentation Project also uses DocBook and has some good information, including a number of style guidelines that might be worth considering. -

    Prev Up Next
    Appendix J. Documentation Home J.2. Tool Sets
    \ No newline at end of file +

    Prev Up Next
    Appendix J. Documentation Home J.2. Tool Sets
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide-style.html postgresql-13-13.12/doc/src/sgml/html/docguide-style.html --- postgresql-13-13.11/doc/src/sgml/html/docguide-style.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide-style.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -J.5. Style Guide
    J.5. Style Guide
    Prev UpAppendix J. DocumentationHome Next

    J.5. Style Guide

    J.5.1. Reference Pages

    J.5.1. Reference Pages

    +J.5. Style Guide

    J.5. Style Guide
    Prev UpAppendix J. DocumentationHome Next

    J.5. Style Guide

    J.5.1. Reference Pages

    J.5.1. Reference Pages

    Reference pages should follow a standard layout. This allows users to find the desired information more quickly, and it also encourages writers to document all relevant aspects of a command. @@ -86,4 +86,4 @@ database system it is compatible. The See Also section of SQL commands should list SQL commands before cross-references to programs. -

    Prev Up Next
    J.4. Documentation Authoring Home Appendix K. PostgreSQL Limits
    \ No newline at end of file +

    Prev Up Next
    J.4. Documentation Authoring Home Appendix K. PostgreSQL Limits
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide-toolsets.html postgresql-13-13.12/doc/src/sgml/html/docguide-toolsets.html --- postgresql-13-13.11/doc/src/sgml/html/docguide-toolsets.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide-toolsets.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -J.2. Tool Sets
    J.2. Tool Sets
    Prev UpAppendix J. DocumentationHome Next

    J.2. Tool Sets

    J.2.1. Installation on Fedora, RHEL, and Derivatives
    J.2.2. Installation on FreeBSD
    J.2.3. Debian Packages
    J.2.4. macOS
    J.2.5. Detection by configure

    +J.2. Tool Sets

    J.2. Tool Sets
    Prev UpAppendix J. DocumentationHome Next

    J.2. Tool Sets

    J.2.1. Installation on Fedora, RHEL, and Derivatives
    J.2.2. Installation on FreeBSD
    J.2.3. Debian Packages
    J.2.4. macOS
    J.2.5. Detection by configure

    The following tools are used to process the documentation. Some might be optional, as noted. @@ -112,4 +112,4 @@ 

     ./configure ... XMLLINT=/opt/local/bin/xmllint ...

    -

    Prev Up Next
    J.1. DocBook Home J.3. Building the Documentation
    \ No newline at end of file +

    Prev Up Next
    J.1. DocBook Home J.3. Building the Documentation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/docguide.html postgresql-13-13.12/doc/src/sgml/html/docguide.html --- postgresql-13-13.11/doc/src/sgml/html/docguide.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/docguide.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix J. Documentation
    Appendix J. Documentation
    Prev UpPart VIII. AppendixesHome Next
    Prev Up Next
    I.1. Getting the Source via Git Home J.1. DocBook
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/domains.html postgresql-13-13.12/doc/src/sgml/html/domains.html --- postgresql-13-13.11/doc/src/sgml/html/domains.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/domains.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.18. Domain Types
    8.18. Domain Types
    Prev UpChapter 8. Data TypesHome Next

    8.18. Domain Types

    +8.18. Domain Types

    8.18. Domain Types
    Prev UpChapter 8. Data TypesHome Next

    8.18. Domain Types

    A domain is a user-defined data type that is based on another underlying type. Optionally, it can have constraints that restrict its valid values to a subset of @@ -31,4 +31,4 @@ domain's constraints will be checked.

    For additional information see CREATE DOMAIN. -

    Prev Up Next
    8.17. Range Types Home 8.19. Object Identifier Types
    \ No newline at end of file +

    Prev Up Next
    8.17. Range Types Home 8.19. Object Identifier Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/dynamic-trace.html postgresql-13-13.12/doc/src/sgml/html/dynamic-trace.html --- postgresql-13-13.11/doc/src/sgml/html/dynamic-trace.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/dynamic-trace.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -27.5. Dynamic Tracing
    27.5. Dynamic Tracing
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.5. Dynamic Tracing

    27.5.1. Compiling for Dynamic Tracing
    27.5.2. Built-in Probes
    27.5.3. Using Probes
    27.5.4. Defining New Probes

    +27.5. Dynamic Tracing

    27.5. Dynamic Tracing
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.5. Dynamic Tracing

    27.5.1. Compiling for Dynamic Tracing
    27.5.2. Built-in Probes
    27.5.3. Using Probes
    27.5.4. Defining New Probes

    PostgreSQL provides facilities to support dynamic tracing of the database server. This allows an external utility to be called at specific points in the code and thereby trace @@ -298,4 +298,4 @@ Each trace macro has a corresponding ENABLED macro.

    -

    Prev Up Next
    27.4. Progress Reporting Home Chapter 28. Monitoring Disk Usage
    \ No newline at end of file +

    Prev Up Next
    27.4. Progress Reporting Home Chapter 28. Monitoring Disk Usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/earthdistance.html postgresql-13-13.12/doc/src/sgml/html/earthdistance.html --- postgresql-13-13.11/doc/src/sgml/html/earthdistance.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/earthdistance.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.13. earthdistance
    F.13. earthdistance
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.13. earthdistance

    F.13.1. Cube-Based Earth Distances
    F.13.2. Point-Based Earth Distances

    +F.13. earthdistance

    F.13. earthdistance
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.13. earthdistance

    F.13.1. Cube-Based Earth Distances
    F.13.2. Point-Based Earth Distances

    The earthdistance module provides two different approaches to calculating great circle distances on the surface of the Earth. The one described first depends on the cube module. @@ -154,4 +154,4 @@ you need to be careful about the edge conditions near the poles and near +/- 180 degrees of longitude. The cube-based representation avoids these discontinuities. -

    Prev Up Next
    F.12. dict_xsyn Home F.14. file_fdw
    \ No newline at end of file +

    Prev Up Next
    F.12. dict_xsyn Home F.14. file_fdw
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-commands.html postgresql-13-13.12/doc/src/sgml/html/ecpg-commands.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-commands.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-commands.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.3. Running SQL Commands
    35.3. Running SQL Commands
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.3. Running SQL Commands

    35.3.1. Executing SQL Statements
    35.3.2. Using Cursors
    35.3.3. Managing Transactions
    35.3.4. Prepared Statements

    +35.3. Running SQL Commands

    35.3. Running SQL Commands
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.3. Running SQL Commands

    35.3.1. Executing SQL Statements
    35.3.2. Using Cursors
    35.3.3. Managing Transactions
    35.3.4. Prepared Statements

    Any SQL command can be run from within an embedded SQL application. Below are some examples of how to do that.

    35.3.1. Executing SQL Statements

    @@ -162,4 +162,4 @@ see PREPARE. Also see Section 35.5 for more details about using placeholders and input parameters. -

    Prev Up Next
    35.2. Managing Database Connections Home 35.4. Using Host Variables
    \ No newline at end of file +

    Prev Up Next
    35.2. Managing Database Connections Home 35.4. Using Host Variables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-concept.html postgresql-13-13.12/doc/src/sgml/html/ecpg-concept.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-concept.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-concept.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.1. The Concept
    35.1. The Concept
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.1. The Concept

    +35.1. The Concept

    35.1. The Concept
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.1. The Concept

    An embedded SQL program consists of code written in an ordinary programming language, in this case C, mixed with SQL commands in specially marked sections. To build the program, the source code (*.pgc) @@ -40,4 +40,4 @@ program, however, follows the C standard of not accepting nested comments.

    The following sections explain all the embedded SQL statements. -

    Prev Up Next
    Chapter 35. ECPG — Embedded SQL in C Home 35.2. Managing Database Connections
    \ No newline at end of file +

    Prev Up Next
    Chapter 35. ECPG — Embedded SQL in C Home 35.2. Managing Database Connections
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-connect.html postgresql-13-13.12/doc/src/sgml/html/ecpg-connect.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-connect.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-connect.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.2. Managing Database Connections
    35.2. Managing Database Connections
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.2. Managing Database Connections

    35.2.1. Connecting to the Database Server
    35.2.2. Choosing a Connection
    35.2.3. Closing a Connection

    +35.2. Managing Database Connections

    35.2. Managing Database Connections
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.2. Managing Database Connections

    35.2.1. Connecting to the Database Server
    35.2.2. Choosing a Connection
    35.2.3. Closing a Connection

    This section describes how to open, close, and switch database connections.

    35.2.1. Connecting to the Database Server

    @@ -195,4 +195,4 @@

    It is good style that an application always explicitly disconnect from every connection it opened. -

    Prev Up Next
    35.1. The Concept Home 35.3. Running SQL Commands
    \ No newline at end of file +

    Prev Up Next
    35.1. The Concept Home 35.3. Running SQL Commands
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-cpp.html postgresql-13-13.12/doc/src/sgml/html/ecpg-cpp.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-cpp.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-cpp.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.13. C++ Applications
    35.13. C++ Applications
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.13. C++ Applications

    35.13.1. Scope for Host Variables
    35.13.2. C++ Application Development with External C Module

    +35.13. C++ Applications

    35.13. C++ Applications
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.13. C++ Applications

    35.13.1. Scope for Host Variables
    35.13.2. C++ Application Development with External C Module

    ECPG has some limited support for C++ applications. This section describes some caveats.

    @@ -225,4 +225,4 @@ 

     c++ test_cpp.o test_mod.o -lecpg -o test_cpp

    -

    Prev Up Next
    35.12. Large Objects Home 35.14. Embedded SQL Commands
    \ No newline at end of file +

    Prev Up Next
    35.12. Large Objects Home 35.14. Embedded SQL Commands
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-descriptors.html postgresql-13-13.12/doc/src/sgml/html/ecpg-descriptors.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-descriptors.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-descriptors.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.7. Using Descriptor Areas
    35.7. Using Descriptor Areas
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.7. Using Descriptor Areas

    35.7.1. Named SQL Descriptor Areas
    35.7.2. SQLDA Descriptor Areas

    +35.7. Using Descriptor Areas

    35.7. Using Descriptor Areas
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.7. Using Descriptor Areas

    35.7.1. Named SQL Descriptor Areas
    35.7.2. SQLDA Descriptor Areas

    An SQL descriptor area is a more sophisticated method for processing the result of a SELECT, FETCH or a DESCRIBE statement. An SQL descriptor area groups @@ -709,4 +709,4 @@ tup_inserted = 0 (type: 9) tup_updated = 0 (type: 9) tup_deleted = 0 (type: 9) -


    Prev Up Next
    35.6. pgtypes Library Home 35.8. Error Handling
    \ No newline at end of file +
    Prev Up Next
    35.6. pgtypes Library Home 35.8. Error Handling
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-develop.html postgresql-13-13.12/doc/src/sgml/html/ecpg-develop.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-develop.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-develop.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -35.17. Internals
    35.17. Internals
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.17. Internals

    +35.17. Internals

    35.17. Internals
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.17. Internals

    This section explains how ECPG works internally. This information can occasionally be useful to help users understand how to use ECPG. @@ -121,4 +121,4 @@

    (The indentation here is added for readability and not something the preprocessor does.) -

    Prev Up Next
    35.16. Oracle Compatibility Mode Home Chapter 36. The Information Schema
    \ No newline at end of file +

    Prev Up Next
    35.16. Oracle Compatibility Mode Home Chapter 36. The Information Schema
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-dynamic.html postgresql-13-13.12/doc/src/sgml/html/ecpg-dynamic.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-dynamic.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-dynamic.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.5. Dynamic SQL
    35.5. Dynamic SQL
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.5. Dynamic SQL

    35.5.1. Executing Statements without a Result Set
    35.5.2. Executing a Statement with Input Parameters
    35.5.3. Executing a Statement with a Result Set

    +35.5. Dynamic SQL

    35.5. Dynamic SQL
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.5. Dynamic SQL

    35.5.1. Executing Statements without a Result Set
    35.5.2. Executing a Statement with Input Parameters
    35.5.3. Executing a Statement with a Result Set

    In many cases, the particular SQL statements that an application has to execute are known at the time the application is written. In some cases, however, the SQL statements are composed at run time @@ -100,4 +100,4 @@ EXEC SQL COMMIT; EXEC SQL DISCONNECT ALL;

    -

    Prev Up Next
    35.4. Using Host Variables Home 35.6. pgtypes Library
    \ No newline at end of file +

    Prev Up Next
    35.4. Using Host Variables Home 35.6. pgtypes Library
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-errors.html postgresql-13-13.12/doc/src/sgml/html/ecpg-errors.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-errors.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-errors.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.8. Error Handling
    35.8. Error Handling
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.8. Error Handling

    35.8.1. Setting Callbacks
    35.8.2. sqlca
    35.8.3. SQLSTATE vs. SQLCODE

    +35.8. Error Handling

    35.8. Error Handling
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.8. Error Handling

    35.8.1. Setting Callbacks
    35.8.2. sqlca
    35.8.3. SQLSTATE vs. SQLCODE

    This section describes how you can handle exceptional conditions and warnings in an embedded SQL program. There are two nonexclusive facilities for this. @@ -438,4 +438,4 @@

    -605 (ECPG_WARNING_PORTAL_EXISTS)

    An existing cursor name was specified. (SQLSTATE 42P03)

    -

    Prev Up Next
    35.7. Using Descriptor Areas Home 35.9. Preprocessor Directives
    \ No newline at end of file +

    Prev Up Next
    35.7. Using Descriptor Areas Home 35.9. Preprocessor Directives
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-informix-compat.html postgresql-13-13.12/doc/src/sgml/html/ecpg-informix-compat.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-informix-compat.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-informix-compat.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -35.15. Informix Compatibility Mode
    35.15. Informix Compatibility Mode
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.15. Informix Compatibility Mode

    35.15.1. Additional Types
    35.15.2. Additional/Missing Embedded SQL Statements
    35.15.3. Informix-compatible SQLDA Descriptor Areas
    35.15.4. Additional Functions
    35.15.5. Additional Constants

    +35.15. Informix Compatibility Mode

    35.15. Informix Compatibility Mode
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.15. Informix Compatibility Mode

    35.15.1. Additional Types
    35.15.2. Additional/Missing Embedded SQL Statements
    35.15.3. Informix-compatible SQLDA Descriptor Areas
    35.15.4. Additional Functions
    35.15.5. Additional Constants

    ecpg can be run in a so-called Informix compatibility mode. If this mode is active, it tries to behave as if it were the Informix precompiler for Informix E/SQL. Generally spoken this will allow you to use @@ -889,4 +889,4 @@ characters it cannot parse. Internally it is defined as -1264 (the Informix definition).

    -

    Prev Up Next
    WHENEVER Home 35.16. Oracle Compatibility Mode
    \ No newline at end of file +

    Prev Up Next
    WHENEVER Home 35.16. Oracle Compatibility Mode
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-library.html postgresql-13-13.12/doc/src/sgml/html/ecpg-library.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-library.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-library.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.11. Library Functions
    35.11. Library Functions
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.11. Library Functions

    +35.11. Library Functions

    35.11. Library Functions
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.11. Library Functions

    The libecpg library primarily contains “hidden” functions that are used to implement the functionality expressed by the embedded SQL commands. But there @@ -43,4 +43,4 @@ returns true if you are connected to a database and false if not. connection_name can be NULL if a single connection is being used. -

    Prev Up Next
    35.10. Processing Embedded SQL Programs Home 35.12. Large Objects
    \ No newline at end of file +

    Prev Up Next
    35.10. Processing Embedded SQL Programs Home 35.12. Large Objects
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-lo.html postgresql-13-13.12/doc/src/sgml/html/ecpg-lo.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-lo.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-lo.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.12. Large Objects
    35.12. Large Objects
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.12. Large Objects

    +35.12. Large Objects

    35.12. Large Objects
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.12. Large Objects

    Large objects are not directly supported by ECPG, but ECPG application can manipulate large objects through the libpq large object functions, obtaining the necessary PGconn @@ -97,4 +97,4 @@ EXEC SQL DISCONNECT ALL; return 0; } -


    Prev Up Next
    35.11. Library Functions Home 35.13. C++ Applications
    \ No newline at end of file +
    Prev Up Next
    35.11. Library Functions Home 35.13. C++ Applications
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-oracle-compat.html postgresql-13-13.12/doc/src/sgml/html/ecpg-oracle-compat.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-oracle-compat.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-oracle-compat.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -35.16. Oracle Compatibility Mode
    35.16. Oracle Compatibility Mode
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.16. Oracle Compatibility Mode

    +35.16. Oracle Compatibility Mode

    35.16. Oracle Compatibility Mode
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.16. Oracle Compatibility Mode

    ecpg can be run in a so-called Oracle compatibility mode. If this mode is active, it tries to behave as if it were Oracle Pro*C. @@ -16,4 +16,4 @@ Set the null indicator to -1 when character arrays receive empty character string types

    -

    Prev Up Next
    35.15. Informix Compatibility Mode Home 35.17. Internals
    \ No newline at end of file +

    Prev Up Next
    35.15. Informix Compatibility Mode Home 35.17. Internals
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-pgtypes.html postgresql-13-13.12/doc/src/sgml/html/ecpg-pgtypes.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-pgtypes.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-pgtypes.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.6. pgtypes Library
    35.6. pgtypes Library
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.6. pgtypes Library

    35.6.1. Character Strings
    35.6.2. The numeric Type
    35.6.3. The date Type
    35.6.4. The timestamp Type
    35.6.5. The interval Type
    35.6.6. The decimal Type
    35.6.7. errno Values of pgtypeslib
    35.6.8. Special Constants of pgtypeslib

    +35.6. pgtypes Library

    35.6. pgtypes Library
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.6. pgtypes Library

    35.6.1. Character Strings
    35.6.2. The numeric Type
    35.6.3. The date Type
    35.6.4. The timestamp Type
    35.6.5. The interval Type
    35.6.6. The decimal Type
    35.6.7. errno Values of pgtypeslib
    35.6.8. Special Constants of pgtypeslib

    The pgtypes library maps PostgreSQL database types to C equivalents that can be used in C programs. It also offers functions to do basic calculations with those types within C, i.e., without @@ -762,4 +762,4 @@ errno != 0 after each call to PGTYPEStimestamp_from_asc.

    -

    Prev Up Next
    35.5. Dynamic SQL Home 35.7. Using Descriptor Areas
    \ No newline at end of file +

    Prev Up Next
    35.5. Dynamic SQL Home 35.7. Using Descriptor Areas
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-preproc.html postgresql-13-13.12/doc/src/sgml/html/ecpg-preproc.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-preproc.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-preproc.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.9. Preprocessor Directives
    35.9. Preprocessor Directives
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.9. Preprocessor Directives

    35.9.1. Including Files
    35.9.2. The define and undef Directives
    35.9.3. ifdef, ifndef, elif, else, and endif Directives

    +35.9. Preprocessor Directives

    35.9. Preprocessor Directives
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.9. Preprocessor Directives

    35.9.1. Including Files
    35.9.2. The define and undef Directives
    35.9.3. ifdef, ifndef, elif, else, and endif Directives

    Several preprocessor directives are available that modify how the ecpg preprocessor parses and processes a file. @@ -126,4 +126,4 @@ EXEC SQL SET TIMEZONE TO 'GMT'; EXEC SQL endif;

    -

    Prev Up Next
    35.8. Error Handling Home 35.10. Processing Embedded SQL Programs
    \ No newline at end of file +

    Prev Up Next
    35.8. Error Handling Home 35.10. Processing Embedded SQL Programs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-process.html postgresql-13-13.12/doc/src/sgml/html/ecpg-process.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-process.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-process.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.10. Processing Embedded SQL Programs
    35.10. Processing Embedded SQL Programs
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.10. Processing Embedded SQL Programs

    +35.10. Processing Embedded SQL Programs

    35.10. Processing Embedded SQL Programs
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.10. Processing Embedded SQL Programs

    Now that you have an idea how to form embedded SQL C programs, you probably want to know how to compile them. Before compiling you run the file through the embedded SQL @@ -65,4 +65,4 @@ The ecpg library is thread-safe by default. However, you might need to use some threading command-line options to compile your client code. -

    Prev Up Next
    35.9. Preprocessor Directives Home 35.11. Library Functions
    \ No newline at end of file +

    Prev Up Next
    35.9. Preprocessor Directives Home 35.11. Library Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -ALLOCATE DESCRIPTOR
    ALLOCATE DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next

    ALLOCATE DESCRIPTOR

    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area

    Synopsis

    +ALLOCATE DESCRIPTOR
    ALLOCATE DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next
    ALLOCATE DESCRIPTOR
    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area
    Synopsis
     ALLOCATE DESCRIPTOR name
 
    Description
    
      ALLOCATE DESCRIPTOR allocates a new named SQL
@@ -16,4 +16,4 @@

    Compatibility

    ALLOCATE DESCRIPTOR is specified in the SQL standard. -

    Prev Up Next
    35.14. Embedded SQL Commands Home CONNECT
    \ No newline at end of file +

    Prev Up Next
    35.14. Embedded SQL Commands Home CONNECT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-commands.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-commands.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-commands.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-commands.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,7 +1,7 @@ -35.14. Embedded SQL Commands
    35.14. Embedded SQL Commands
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.14. Embedded SQL Commands

    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area
    CONNECT — establish a database connection
    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area
    DECLARE — define a cursor
    DESCRIBE — obtain information about a prepared statement or result set
    DISCONNECT — terminate a database connection
    EXECUTE IMMEDIATE — dynamically prepare and execute a statement
    GET DESCRIPTOR — get information from an SQL descriptor area
    OPEN — open a dynamic cursor
    PREPARE — prepare a statement for execution
    SET AUTOCOMMIT — set the autocommit behavior of the current session
    SET CONNECTION — select a database connection
    SET DESCRIPTOR — set information in an SQL descriptor area
    TYPE — define a new data type
    VAR — define a variable
    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised

    +35.14. Embedded SQL Commands

    35.14. Embedded SQL Commands
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.14. Embedded SQL Commands

    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area
    CONNECT — establish a database connection
    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area
    DECLARE — define a cursor
    DESCRIBE — obtain information about a prepared statement or result set
    DISCONNECT — terminate a database connection
    EXECUTE IMMEDIATE — dynamically prepare and execute a statement
    GET DESCRIPTOR — get information from an SQL descriptor area
    OPEN — open a dynamic cursor
    PREPARE — prepare a statement for execution
    SET AUTOCOMMIT — set the autocommit behavior of the current session
    SET CONNECTION — select a database connection
    SET DESCRIPTOR — set information in an SQL descriptor area
    TYPE — define a new data type
    VAR — define a variable
    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised

    This section describes all SQL commands that are specific to embedded SQL. Also refer to the SQL commands listed in SQL Commands, which can also be used in embedded SQL, unless stated otherwise. -

    Prev Up Next
    35.13. C++ Applications Home ALLOCATE DESCRIPTOR
    \ No newline at end of file +

    Prev Up Next
    35.13. C++ Applications Home ALLOCATE DESCRIPTOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-connect.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-connect.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-connect.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-connect.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -CONNECT
    CONNECT
    Prev Up35.14. Embedded SQL CommandsHome Next

    CONNECT

    CONNECT — establish a database connection

    Synopsis

    +CONNECT
    CONNECT
    Prev Up35.14. Embedded SQL CommandsHome Next
    CONNECT
    CONNECT — establish a database connection
    Synopsis
     CONNECT TO connection_target [ AS connection_name ] [ USER connection_user ]
 CONNECT TO DEFAULT
 CONNECT connection_user
@@ -106,4 +106,4 @@
      CONNECT is specified in the SQL standard, but
      the format of the connection parameters is
      implementation-specific.
-    
    Prev Up Next
    ALLOCATE DESCRIPTOR Home DEALLOCATE DESCRIPTOR
    
\ No newline at end of file
+
    Prev Up Next
    ALLOCATE DESCRIPTOR Home DEALLOCATE DESCRIPTOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -DEALLOCATE DESCRIPTOR
    DEALLOCATE DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next

    DEALLOCATE DESCRIPTOR

    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area

    Synopsis

    +DEALLOCATE DESCRIPTOR
    DEALLOCATE DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next
    DEALLOCATE DESCRIPTOR
    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area
    Synopsis
     DEALLOCATE DESCRIPTOR name
 
    Description
    
      DEALLOCATE DESCRIPTOR deallocates a named SQL
@@ -13,4 +13,4 @@

    Compatibility

    DEALLOCATE DESCRIPTOR is specified in the SQL standard. -

    Prev Up Next
    CONNECT Home DECLARE
    \ No newline at end of file +

    Prev Up Next
    CONNECT Home DECLARE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-declare.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-declare.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-declare.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-declare.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -DECLARE
    DECLARE
    Prev Up35.14. Embedded SQL CommandsHome Next

    DECLARE

    DECLARE — define a cursor

    Synopsis

    +DECLARE
    DECLARE
    Prev Up35.14. Embedded SQL CommandsHome Next
    DECLARE
    DECLARE — define a cursor
    Synopsis
     DECLARE cursor_name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR prepared_name
 DECLARE cursor_name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ] CURSOR [ { WITH | WITHOUT } HOLD ] FOR query
 
    Description
    
@@ -40,4 +40,4 @@

    Compatibility

    DECLARE is specified in the SQL standard. -

    See Also

    OPEN, CLOSE, DECLARE
    Prev Up Next
    DEALLOCATE DESCRIPTOR Home DESCRIBE
    \ No newline at end of file +

    See Also

    OPEN, CLOSE, DECLARE
    Prev Up Next
    DEALLOCATE DESCRIPTOR Home DESCRIBE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-describe.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-describe.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-describe.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-describe.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -DESCRIBE
    DESCRIBE
    Prev Up35.14. Embedded SQL CommandsHome Next

    DESCRIBE

    DESCRIBE — obtain information about a prepared statement or result set

    Synopsis

    +DESCRIBE
    DESCRIBE
    Prev Up35.14. Embedded SQL CommandsHome Next
    DESCRIBE
    DESCRIBE — obtain information about a prepared statement or result set
    Synopsis
     DESCRIBE [ OUTPUT ] prepared_name USING [ SQL ] DESCRIPTOR descriptor_name
 DESCRIBE [ OUTPUT ] prepared_name INTO [ SQL ] DESCRIPTOR descriptor_name
 DESCRIBE [ OUTPUT ] prepared_name INTO sqlda_name
@@ -23,4 +23,4 @@
 EXEC SQL DEALLOCATE DESCRIPTOR mydesc;
 
    Compatibility
    
      DESCRIBE is specified in the SQL standard.
-    
    Prev Up Next
    DECLARE Home DISCONNECT
    
\ No newline at end of file
+
    Prev Up Next
    DECLARE Home DISCONNECT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-disconnect.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-disconnect.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-disconnect.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-disconnect.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -DISCONNECT
    DISCONNECT
    Prev Up35.14. Embedded SQL CommandsHome Next

    DISCONNECT

    DISCONNECT — terminate a database connection

    Synopsis

    +DISCONNECT
    DISCONNECT
    Prev Up35.14. Embedded SQL CommandsHome Next
    DISCONNECT
    DISCONNECT — terminate a database connection
    Synopsis
     DISCONNECT connection_name
 DISCONNECT [ CURRENT ]
 DISCONNECT DEFAULT
@@ -37,4 +37,4 @@
 }
 
    Compatibility
    
      DISCONNECT is specified in the SQL standard.
-    
    Prev Up Next
    DESCRIBE Home EXECUTE IMMEDIATE
    
\ No newline at end of file
+
    Prev Up Next
    DESCRIBE Home EXECUTE IMMEDIATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-execute-immediate.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-execute-immediate.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-execute-immediate.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-execute-immediate.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -EXECUTE IMMEDIATE
    EXECUTE IMMEDIATE
    Prev Up35.14. Embedded SQL CommandsHome Next

    EXECUTE IMMEDIATE

    EXECUTE IMMEDIATE — dynamically prepare and execute a statement

    Synopsis

    +EXECUTE IMMEDIATE
    EXECUTE IMMEDIATE
    Prev Up35.14. Embedded SQL CommandsHome Next
    EXECUTE IMMEDIATE
    EXECUTE IMMEDIATE — dynamically prepare and execute a statement
    Synopsis
     EXECUTE IMMEDIATE string
 
    Description
    
      EXECUTE IMMEDIATE immediately prepares and
@@ -18,4 +18,4 @@

    Compatibility

    EXECUTE IMMEDIATE is specified in the SQL standard. -

    Prev Up Next
    DISCONNECT Home GET DESCRIPTOR
    \ No newline at end of file +

    Prev Up Next
    DISCONNECT Home GET DESCRIPTOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-get-descriptor.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-get-descriptor.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-get-descriptor.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-get-descriptor.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -GET DESCRIPTOR
    GET DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next

    GET DESCRIPTOR

    GET DESCRIPTOR — get information from an SQL descriptor area

    Synopsis

    +GET DESCRIPTOR
    GET DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next
    GET DESCRIPTOR
    GET DESCRIPTOR — get information from an SQL descriptor area
    Synopsis
     GET DESCRIPTOR descriptor_name :cvariable = descriptor_header_item [, ... ]
 GET DESCRIPTOR descriptor_name VALUE column_number :cvariable = descriptor_item [, ... ]
 
    Description
    
@@ -101,4 +101,4 @@

    Compatibility

    GET DESCRIPTOR is specified in the SQL standard. -

    Prev Up Next
    EXECUTE IMMEDIATE Home OPEN
    \ No newline at end of file +

    Prev Up Next
    EXECUTE IMMEDIATE Home OPEN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-open.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-open.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-open.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-open.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -OPEN
    OPEN
    Prev Up35.14. Embedded SQL CommandsHome Next

    OPEN

    OPEN — open a dynamic cursor

    Synopsis

    +OPEN
    OPEN
    Prev Up35.14. Embedded SQL CommandsHome Next
    OPEN
    OPEN — open a dynamic cursor
    Synopsis
     OPEN cursor_name
 OPEN cursor_name USING value [, ... ]
 OPEN cursor_name USING SQL DESCRIPTOR descriptor_name
@@ -28,4 +28,4 @@
 EXEC SQL OPEN :curname1;
 
    Compatibility
    
      OPEN is specified in the SQL standard.
-    
    See Also
    DECLARE, CLOSE
    Prev Up Next
    GET DESCRIPTOR Home PREPARE
    
\ No newline at end of file
+

    See Also

    DECLARE, CLOSE
    Prev Up Next
    GET DESCRIPTOR Home PREPARE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-prepare.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-prepare.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-prepare.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-prepare.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -PREPARE
    PREPARE
    Prev Up35.14. Embedded SQL CommandsHome Next

    PREPARE

    PREPARE — prepare a statement for execution

    Synopsis

    +PREPARE
    PREPARE
    Prev Up35.14. Embedded SQL CommandsHome Next
    PREPARE
    PREPARE — prepare a statement for execution
    Synopsis
     PREPARE name FROM string
 
    Description
    
      PREPARE prepares a statement dynamically
@@ -22,4 +22,4 @@
 EXEC SQL EXECUTE foo USING SQL DESCRIPTOR indesc INTO SQL DESCRIPTOR outdesc;

    Compatibility

    PREPARE is specified in the SQL standard. -

    See Also

    EXECUTE
    Prev Up Next
    OPEN Home SET AUTOCOMMIT
    \ No newline at end of file +

    See Also

    EXECUTE
    Prev Up Next
    OPEN Home SET AUTOCOMMIT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-autocommit.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-autocommit.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-autocommit.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-autocommit.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -SET AUTOCOMMIT
    SET AUTOCOMMIT
    Prev Up35.14. Embedded SQL CommandsHome Next

    SET AUTOCOMMIT

    SET AUTOCOMMIT — set the autocommit behavior of the current session

    Synopsis

    +SET AUTOCOMMIT
    SET AUTOCOMMIT
    Prev Up35.14. Embedded SQL CommandsHome Next
    SET AUTOCOMMIT
    SET AUTOCOMMIT — set the autocommit behavior of the current session
    Synopsis
     SET AUTOCOMMIT { = | TO } { ON | OFF }
 
    Description
    
      SET AUTOCOMMIT sets the autocommit behavior of
@@ -10,4 +10,4 @@
      where each individual statement is committed implicitly.
     
    Compatibility
    
      SET AUTOCOMMIT is an extension of PostgreSQL ECPG.
-    
    Prev Up Next
    PREPARE Home SET CONNECTION
    
\ No newline at end of file
+
    Prev Up Next
    PREPARE Home SET CONNECTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-connection.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-connection.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-connection.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-connection.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -SET CONNECTION
    SET CONNECTION
    Prev Up35.14. Embedded SQL CommandsHome Next

    SET CONNECTION

    SET CONNECTION — select a database connection

    Synopsis

    +SET CONNECTION
    SET CONNECTION
    Prev Up35.14. Embedded SQL CommandsHome Next
    SET CONNECTION
    SET CONNECTION — select a database connection
    Synopsis
     SET CONNECTION [ TO | = ] connection_name
 
    Description
    
      SET CONNECTION sets the “current”
@@ -15,4 +15,4 @@
 EXEC SQL SET CONNECTION = con1;

    Compatibility

    SET CONNECTION is specified in the SQL standard. -

    Prev Up Next
    SET AUTOCOMMIT Home SET DESCRIPTOR
    \ No newline at end of file +

    Prev Up Next
    SET AUTOCOMMIT Home SET DESCRIPTOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-descriptor.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-descriptor.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-set-descriptor.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-set-descriptor.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -SET DESCRIPTOR
    SET DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next

    SET DESCRIPTOR

    SET DESCRIPTOR — set information in an SQL descriptor area

    Synopsis

    +SET DESCRIPTOR
    SET DESCRIPTOR
    Prev Up35.14. Embedded SQL CommandsHome Next
    SET DESCRIPTOR
    SET DESCRIPTOR — set information in an SQL descriptor area
    Synopsis
     SET DESCRIPTOR descriptor_name descriptor_header_item = value [, ... ]
 SET DESCRIPTOR descriptor_name VALUE number descriptor_item = value [, ...]
 
    Description
    
@@ -35,4 +35,4 @@
 EXEC SQL SET DESCRIPTOR indesc VALUE 2 INDICATOR = :val2null, DATA = :val2;

    Compatibility

    SET DESCRIPTOR is specified in the SQL standard. -

    Prev Up Next
    SET CONNECTION Home TYPE
    \ No newline at end of file +

    Prev Up Next
    SET CONNECTION Home TYPE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-type.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-type.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-type.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-type.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -TYPE
    TYPE
    Prev Up35.14. Embedded SQL CommandsHome Next

    TYPE

    TYPE — define a new data type

    Synopsis

    +TYPE
    TYPE
    Prev Up35.14. Embedded SQL CommandsHome Next
    TYPE
    TYPE — define a new data type
    Synopsis
     TYPE type_name IS ctype
 
    Description
    
      The TYPE command defines a new C type.  It is
@@ -85,4 +85,4 @@

    Compatibility

    The TYPE command is a PostgreSQL extension. -

    Prev Up Next
    SET DESCRIPTOR Home VAR
    \ No newline at end of file +

    Prev Up Next
    SET DESCRIPTOR Home VAR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-var.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-var.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-var.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-var.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -VAR
    VAR
    Prev Up35.14. Embedded SQL CommandsHome Next

    VAR

    VAR — define a variable

    Synopsis

    +VAR
    VAR
    Prev Up35.14. Embedded SQL CommandsHome Next
    VAR
    VAR — define a variable
    Synopsis
     VAR varname IS ctype
 
    Description
    
      The VAR command assigns a new C data type
@@ -16,4 +16,4 @@
 EXEC SQL VAR a IS int;

    Compatibility

    The VAR command is a PostgreSQL extension. -

    Prev Up Next
    TYPE Home WHENEVER
    \ No newline at end of file +

    Prev Up Next
    TYPE Home WHENEVER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-whenever.html postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-whenever.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-sql-whenever.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-sql-whenever.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -WHENEVER
    WHENEVER
    Prev Up35.14. Embedded SQL CommandsHome Next

    WHENEVER

    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised

    Synopsis

    +WHENEVER
    WHENEVER
    Prev Up35.14. Embedded SQL CommandsHome Next
    WHENEVER
    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised
    Synopsis
     WHENEVER { NOT FOUND | SQLERROR | SQLWARNING } action
 
    Description
    
      Define a behavior which is called on the special cases (Rows not
@@ -54,4 +54,4 @@
     
    Compatibility
    
      WHENEVER is specified in the SQL standard, but
      most of the actions are PostgreSQL extensions.
-    
    Prev Up Next
    VAR Home 35.15. Informix Compatibility Mode
    
\ No newline at end of file
+
    Prev Up Next
    VAR Home 35.15. Informix Compatibility Mode
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg-variables.html postgresql-13-13.12/doc/src/sgml/html/ecpg-variables.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg-variables.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg-variables.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -35.4. Using Host Variables
    35.4. Using Host Variables
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.4. Using Host Variables

    35.4.1. Overview
    35.4.2. Declare Sections
    35.4.3. Retrieving Query Results
    35.4.4. Type Mapping
    35.4.5. Handling Nonprimitive SQL Data Types
    35.4.6. Indicators

    +35.4. Using Host Variables

    35.4. Using Host Variables
    Prev UpChapter 35. ECPG — Embedded SQL in CHome Next

    35.4. Using Host Variables

    35.4.1. Overview
    35.4.2. Declare Sections
    35.4.3. Retrieving Query Results
    35.4.4. Type Mapping
    35.4.5. Handling Nonprimitive SQL Data Types
    35.4.6. Indicators

    In Section 35.3 you saw how you can execute SQL statements from an embedded SQL program. Some of those statements only used fixed values and did not provide a way to insert @@ -878,4 +878,4 @@ input and output) for character string types as empty string and for integer types as the lowest possible value for type (for example, INT_MIN for int). -

    Prev Up Next
    35.3. Running SQL Commands Home 35.5. Dynamic SQL
    \ No newline at end of file +

    Prev Up Next
    35.3. Running SQL Commands Home 35.5. Dynamic SQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ecpg.html postgresql-13-13.12/doc/src/sgml/html/ecpg.html --- postgresql-13-13.11/doc/src/sgml/html/ecpg.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ecpg.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 35. ECPG — Embedded SQL in C
    Chapter 35. ECPG — Embedded SQL in C
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 35. ECPG — Embedded SQL in C

    Table of Contents

    35.1. The Concept
    35.2. Managing Database Connections
    35.2.1. Connecting to the Database Server
    35.2.2. Choosing a Connection
    35.2.3. Closing a Connection
    35.3. Running SQL Commands
    35.3.1. Executing SQL Statements
    35.3.2. Using Cursors
    35.3.3. Managing Transactions
    35.3.4. Prepared Statements
    35.4. Using Host Variables
    35.4.1. Overview
    35.4.2. Declare Sections
    35.4.3. Retrieving Query Results
    35.4.4. Type Mapping
    35.4.5. Handling Nonprimitive SQL Data Types
    35.4.6. Indicators
    35.5. Dynamic SQL
    35.5.1. Executing Statements without a Result Set
    35.5.2. Executing a Statement with Input Parameters
    35.5.3. Executing a Statement with a Result Set
    35.6. pgtypes Library
    35.6.1. Character Strings
    35.6.2. The numeric Type
    35.6.3. The date Type
    35.6.4. The timestamp Type
    35.6.5. The interval Type
    35.6.6. The decimal Type
    35.6.7. errno Values of pgtypeslib
    35.6.8. Special Constants of pgtypeslib
    35.7. Using Descriptor Areas
    35.7.1. Named SQL Descriptor Areas
    35.7.2. SQLDA Descriptor Areas
    35.8. Error Handling
    35.8.1. Setting Callbacks
    35.8.2. sqlca
    35.8.3. SQLSTATE vs. SQLCODE
    35.9. Preprocessor Directives
    35.9.1. Including Files
    35.9.2. The define and undef Directives
    35.9.3. ifdef, ifndef, elif, else, and endif Directives
    35.10. Processing Embedded SQL Programs
    35.11. Library Functions
    35.12. Large Objects
    35.13. C++ Applications
    35.13.1. Scope for Host Variables
    35.13.2. C++ Application Development with External C Module
    35.14. Embedded SQL Commands
    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area
    CONNECT — establish a database connection
    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area
    DECLARE — define a cursor
    DESCRIBE — obtain information about a prepared statement or result set
    DISCONNECT — terminate a database connection
    EXECUTE IMMEDIATE — dynamically prepare and execute a statement
    GET DESCRIPTOR — get information from an SQL descriptor area
    OPEN — open a dynamic cursor
    PREPARE — prepare a statement for execution
    SET AUTOCOMMIT — set the autocommit behavior of the current session
    SET CONNECTION — select a database connection
    SET DESCRIPTOR — set information in an SQL descriptor area
    TYPE — define a new data type
    VAR — define a variable
    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised
    35.15. Informix Compatibility Mode
    35.15.1. Additional Types
    35.15.2. Additional/Missing Embedded SQL Statements
    35.15.3. Informix-compatible SQLDA Descriptor Areas
    35.15.4. Additional Functions
    35.15.5. Additional Constants
    35.16. Oracle Compatibility Mode
    35.17. Internals

    +Chapter 35. ECPG — Embedded SQL in C

    Chapter 35. ECPG — Embedded SQL in C
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 35. ECPG — Embedded SQL in C

    Table of Contents

    35.1. The Concept
    35.2. Managing Database Connections
    35.2.1. Connecting to the Database Server
    35.2.2. Choosing a Connection
    35.2.3. Closing a Connection
    35.3. Running SQL Commands
    35.3.1. Executing SQL Statements
    35.3.2. Using Cursors
    35.3.3. Managing Transactions
    35.3.4. Prepared Statements
    35.4. Using Host Variables
    35.4.1. Overview
    35.4.2. Declare Sections
    35.4.3. Retrieving Query Results
    35.4.4. Type Mapping
    35.4.5. Handling Nonprimitive SQL Data Types
    35.4.6. Indicators
    35.5. Dynamic SQL
    35.5.1. Executing Statements without a Result Set
    35.5.2. Executing a Statement with Input Parameters
    35.5.3. Executing a Statement with a Result Set
    35.6. pgtypes Library
    35.6.1. Character Strings
    35.6.2. The numeric Type
    35.6.3. The date Type
    35.6.4. The timestamp Type
    35.6.5. The interval Type
    35.6.6. The decimal Type
    35.6.7. errno Values of pgtypeslib
    35.6.8. Special Constants of pgtypeslib
    35.7. Using Descriptor Areas
    35.7.1. Named SQL Descriptor Areas
    35.7.2. SQLDA Descriptor Areas
    35.8. Error Handling
    35.8.1. Setting Callbacks
    35.8.2. sqlca
    35.8.3. SQLSTATE vs. SQLCODE
    35.9. Preprocessor Directives
    35.9.1. Including Files
    35.9.2. The define and undef Directives
    35.9.3. ifdef, ifndef, elif, else, and endif Directives
    35.10. Processing Embedded SQL Programs
    35.11. Library Functions
    35.12. Large Objects
    35.13. C++ Applications
    35.13.1. Scope for Host Variables
    35.13.2. C++ Application Development with External C Module
    35.14. Embedded SQL Commands
    ALLOCATE DESCRIPTOR — allocate an SQL descriptor area
    CONNECT — establish a database connection
    DEALLOCATE DESCRIPTOR — deallocate an SQL descriptor area
    DECLARE — define a cursor
    DESCRIBE — obtain information about a prepared statement or result set
    DISCONNECT — terminate a database connection
    EXECUTE IMMEDIATE — dynamically prepare and execute a statement
    GET DESCRIPTOR — get information from an SQL descriptor area
    OPEN — open a dynamic cursor
    PREPARE — prepare a statement for execution
    SET AUTOCOMMIT — set the autocommit behavior of the current session
    SET CONNECTION — select a database connection
    SET DESCRIPTOR — set information in an SQL descriptor area
    TYPE — define a new data type
    VAR — define a variable
    WHENEVER — specify the action to be taken when an SQL statement causes a specific class condition to be raised
    35.15. Informix Compatibility Mode
    35.15.1. Additional Types
    35.15.2. Additional/Missing Embedded SQL Statements
    35.15.3. Informix-compatible SQLDA Descriptor Areas
    35.15.4. Additional Functions
    35.15.5. Additional Constants
    35.16. Oracle Compatibility Mode
    35.17. Internals

    This chapter describes the embedded SQL package for PostgreSQL. It was written by Linus Tolke () and Michael Meskes @@ -10,4 +10,4 @@ This documentation is quite incomplete. But since this interface is standardized, additional information can be found in many resources about SQL. -

    Prev Up Next
    34.5. Example Program Home 35.1. The Concept
    \ No newline at end of file +

    Prev Up Next
    34.5. Example Program Home 35.1. The Concept
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/encryption-options.html postgresql-13-13.12/doc/src/sgml/html/encryption-options.html --- postgresql-13-13.11/doc/src/sgml/html/encryption-options.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/encryption-options.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.8. Encryption Options
    18.8. Encryption Options
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.8. Encryption Options

    +18.8. Encryption Options

    18.8. Encryption Options
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.8. Encryption Options

    PostgreSQL offers encryption at several levels, and provides flexibility in protecting data from disclosure due to database server theft, unscrupulous administrators, and @@ -81,4 +81,4 @@ never appears on the database server. Data is encrypted on the client before being sent to the server, and database results have to be decrypted on the client before being used. -

    Prev Up Next
    18.7. Preventing Server Spoofing Home 18.9. Secure TCP/IP Connections with SSL
    \ No newline at end of file +

    Prev Up Next
    18.7. Preventing Server Spoofing Home 18.9. Secure TCP/IP Connections with SSL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/errcodes-appendix.html postgresql-13-13.12/doc/src/sgml/html/errcodes-appendix.html --- postgresql-13-13.11/doc/src/sgml/html/errcodes-appendix.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/errcodes-appendix.html 2023-08-07 20:32:34.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix A. PostgreSQL Error Codes
    Appendix A. PostgreSQL Error Codes
    Prev UpPart VIII. AppendixesHome Next

    Appendix A. PostgreSQL Error Codes

    +Appendix A. PostgreSQL Error Codes

    Appendix A. PostgreSQL Error Codes
    Prev UpPart VIII. AppendixesHome Next

    Appendix A. PostgreSQL Error Codes

    All messages emitted by the PostgreSQL server are assigned five-character error codes that follow the SQL standard's conventions for “SQLSTATE” codes. Applications @@ -20,7 +20,7 @@ what to do from the error class.

    Table A.1 lists all the error codes defined in - PostgreSQL 13.11. (Some are not actually + PostgreSQL 13.12. (Some are not actually used at present, but are defined by the SQL standard.) The error classes are also shown. For each error class there is a “standard” error code having the last three characters @@ -42,4 +42,4 @@ As of PostgreSQL 9.3, complete coverage for this feature exists only for errors in SQLSTATE class 23 (integrity constraint violation), but this is likely to be expanded in future. -

    Table A.1. PostgreSQL Error Codes

    Error CodeCondition Name
    Class 00 — Successful Completion
    00000successful_completion
    Class 01 — Warning
    01000warning
    0100Cdynamic_result_sets_returned
    01008implicit_zero_bit_padding
    01003null_value_eliminated_in_set_function
    01007privilege_not_granted
    01006privilege_not_revoked
    01004string_data_right_truncation
    01P01deprecated_feature
    Class 02 — No Data (this is also a warning class per the SQL standard)
    02000no_data
    02001no_additional_dynamic_result_sets_returned
    Class 03 — SQL Statement Not Yet Complete
    03000sql_statement_not_yet_complete
    Class 08 — Connection Exception
    08000connection_exception
    08003connection_does_not_exist
    08006connection_failure
    08001sqlclient_unable_to_establish_sqlconnection
    08004sqlserver_rejected_establishment_of_sqlconnection
    08007transaction_resolution_unknown
    08P01protocol_violation
    Class 09 — Triggered Action Exception
    09000triggered_action_exception
    Class 0A — Feature Not Supported
    0A000feature_not_supported
    Class 0B — Invalid Transaction Initiation
    0B000invalid_transaction_initiation
    Class 0F — Locator Exception
    0F000locator_exception
    0F001invalid_locator_specification
    Class 0L — Invalid Grantor
    0L000invalid_grantor
    0LP01invalid_grant_operation
    Class 0P — Invalid Role Specification
    0P000invalid_role_specification
    Class 0Z — Diagnostics Exception
    0Z000diagnostics_exception
    0Z002stacked_diagnostics_accessed_without_active_handler
    Class 20 — Case Not Found
    20000case_not_found
    Class 21 — Cardinality Violation
    21000cardinality_violation
    Class 22 — Data Exception
    22000data_exception
    2202Earray_subscript_error
    22021character_not_in_repertoire
    22008datetime_field_overflow
    22012division_by_zero
    22005error_in_assignment
    2200Bescape_character_conflict
    22022indicator_overflow
    22015interval_field_overflow
    2201Einvalid_argument_for_logarithm
    22014invalid_argument_for_ntile_function
    22016invalid_argument_for_nth_value_function
    2201Finvalid_argument_for_power_function
    2201Ginvalid_argument_for_width_bucket_function
    22018invalid_character_value_for_cast
    22007invalid_datetime_format
    22019invalid_escape_character
    2200Dinvalid_escape_octet
    22025invalid_escape_sequence
    22P06nonstandard_use_of_escape_character
    22010invalid_indicator_parameter_value
    22023invalid_parameter_value
    22013invalid_preceding_or_following_size
    2201Binvalid_regular_expression
    2201Winvalid_row_count_in_limit_clause
    2201Xinvalid_row_count_in_result_offset_clause
    2202Hinvalid_tablesample_argument
    2202Ginvalid_tablesample_repeat
    22009invalid_time_zone_displacement_value
    2200Cinvalid_use_of_escape_character
    2200Gmost_specific_type_mismatch
    22004null_value_not_allowed
    22002null_value_no_indicator_parameter
    22003numeric_value_out_of_range
    2200Hsequence_generator_limit_exceeded
    22026string_data_length_mismatch
    22001string_data_right_truncation
    22011substring_error
    22027trim_error
    22024unterminated_c_string
    2200Fzero_length_character_string
    22P01floating_point_exception
    22P02invalid_text_representation
    22P03invalid_binary_representation
    22P04bad_copy_file_format
    22P05untranslatable_character
    2200Lnot_an_xml_document
    2200Minvalid_xml_document
    2200Ninvalid_xml_content
    2200Sinvalid_xml_comment
    2200Tinvalid_xml_processing_instruction
    22030duplicate_json_object_key_value
    22031invalid_argument_for_sql_json_datetime_function
    22032invalid_json_text
    22033invalid_sql_json_subscript
    22034more_than_one_sql_json_item
    22035no_sql_json_item
    22036non_numeric_sql_json_item
    22037non_unique_keys_in_a_json_object
    22038singleton_sql_json_item_required
    22039sql_json_array_not_found
    2203Asql_json_member_not_found
    2203Bsql_json_number_not_found
    2203Csql_json_object_not_found
    2203Dtoo_many_json_array_elements
    2203Etoo_many_json_object_members
    2203Fsql_json_scalar_required
    Class 23 — Integrity Constraint Violation
    23000integrity_constraint_violation
    23001restrict_violation
    23502not_null_violation
    23503foreign_key_violation
    23505unique_violation
    23514check_violation
    23P01exclusion_violation
    Class 24 — Invalid Cursor State
    24000invalid_cursor_state
    Class 25 — Invalid Transaction State
    25000invalid_transaction_state
    25001active_sql_transaction
    25002branch_transaction_already_active
    25008held_cursor_requires_same_isolation_level
    25003inappropriate_access_mode_for_branch_transaction
    25004inappropriate_isolation_level_for_branch_transaction
    25005no_active_sql_transaction_for_branch_transaction
    25006read_only_sql_transaction
    25007schema_and_data_statement_mixing_not_supported
    25P01no_active_sql_transaction
    25P02in_failed_sql_transaction
    25P03idle_in_transaction_session_timeout
    Class 26 — Invalid SQL Statement Name
    26000invalid_sql_statement_name
    Class 27 — Triggered Data Change Violation
    27000triggered_data_change_violation
    Class 28 — Invalid Authorization Specification
    28000invalid_authorization_specification
    28P01invalid_password
    Class 2B — Dependent Privilege Descriptors Still Exist
    2B000dependent_privilege_descriptors_still_exist
    2BP01dependent_objects_still_exist
    Class 2D — Invalid Transaction Termination
    2D000invalid_transaction_termination
    Class 2F — SQL Routine Exception
    2F000sql_routine_exception
    2F005function_executed_no_return_statement
    2F002modifying_sql_data_not_permitted
    2F003prohibited_sql_statement_attempted
    2F004reading_sql_data_not_permitted
    Class 34 — Invalid Cursor Name
    34000invalid_cursor_name
    Class 38 — External Routine Exception
    38000external_routine_exception
    38001containing_sql_not_permitted
    38002modifying_sql_data_not_permitted
    38003prohibited_sql_statement_attempted
    38004reading_sql_data_not_permitted
    Class 39 — External Routine Invocation Exception
    39000external_routine_invocation_exception
    39001invalid_sqlstate_returned
    39004null_value_not_allowed
    39P01trigger_protocol_violated
    39P02srf_protocol_violated
    39P03event_trigger_protocol_violated
    Class 3B — Savepoint Exception
    3B000savepoint_exception
    3B001invalid_savepoint_specification
    Class 3D — Invalid Catalog Name
    3D000invalid_catalog_name
    Class 3F — Invalid Schema Name
    3F000invalid_schema_name
    Class 40 — Transaction Rollback
    40000transaction_rollback
    40002transaction_integrity_constraint_violation
    40001serialization_failure
    40003statement_completion_unknown
    40P01deadlock_detected
    Class 42 — Syntax Error or Access Rule Violation
    42000syntax_error_or_access_rule_violation
    42601syntax_error
    42501insufficient_privilege
    42846cannot_coerce
    42803grouping_error
    42P20windowing_error
    42P19invalid_recursion
    42830invalid_foreign_key
    42602invalid_name
    42622name_too_long
    42939reserved_name
    42804datatype_mismatch
    42P18indeterminate_datatype
    42P21collation_mismatch
    42P22indeterminate_collation
    42809wrong_object_type
    428C9generated_always
    42703undefined_column
    42883undefined_function
    42P01undefined_table
    42P02undefined_parameter
    42704undefined_object
    42701duplicate_column
    42P03duplicate_cursor
    42P04duplicate_database
    42723duplicate_function
    42P05duplicate_prepared_statement
    42P06duplicate_schema
    42P07duplicate_table
    42712duplicate_alias
    42710duplicate_object
    42702ambiguous_column
    42725ambiguous_function
    42P08ambiguous_parameter
    42P09ambiguous_alias
    42P10invalid_column_reference
    42611invalid_column_definition
    42P11invalid_cursor_definition
    42P12invalid_database_definition
    42P13invalid_function_definition
    42P14invalid_prepared_statement_definition
    42P15invalid_schema_definition
    42P16invalid_table_definition
    42P17invalid_object_definition
    Class 44 — WITH CHECK OPTION Violation
    44000with_check_option_violation
    Class 53 — Insufficient Resources
    53000insufficient_resources
    53100disk_full
    53200out_of_memory
    53300too_many_connections
    53400configuration_limit_exceeded
    Class 54 — Program Limit Exceeded
    54000program_limit_exceeded
    54001statement_too_complex
    54011too_many_columns
    54023too_many_arguments
    Class 55 — Object Not In Prerequisite State
    55000object_not_in_prerequisite_state
    55006object_in_use
    55P02cant_change_runtime_param
    55P03lock_not_available
    55P04unsafe_new_enum_value_usage
    Class 57 — Operator Intervention
    57000operator_intervention
    57014query_canceled
    57P01admin_shutdown
    57P02crash_shutdown
    57P03cannot_connect_now
    57P04database_dropped
    Class 58 — System Error (errors external to PostgreSQL itself)
    58000system_error
    58030io_error
    58P01undefined_file
    58P02duplicate_file
    Class 72 — Snapshot Failure
    72000snapshot_too_old
    Class F0 — Configuration File Error
    F0000config_file_error
    F0001lock_file_exists
    Class HV — Foreign Data Wrapper Error (SQL/MED)
    HV000fdw_error
    HV005fdw_column_name_not_found
    HV002fdw_dynamic_parameter_value_needed
    HV010fdw_function_sequence_error
    HV021fdw_inconsistent_descriptor_information
    HV024fdw_invalid_attribute_value
    HV007fdw_invalid_column_name
    HV008fdw_invalid_column_number
    HV004fdw_invalid_data_type
    HV006fdw_invalid_data_type_descriptors
    HV091fdw_invalid_descriptor_field_identifier
    HV00Bfdw_invalid_handle
    HV00Cfdw_invalid_option_index
    HV00Dfdw_invalid_option_name
    HV090fdw_invalid_string_length_or_buffer_length
    HV00Afdw_invalid_string_format
    HV009fdw_invalid_use_of_null_pointer
    HV014fdw_too_many_handles
    HV001fdw_out_of_memory
    HV00Pfdw_no_schemas
    HV00Jfdw_option_name_not_found
    HV00Kfdw_reply_handle
    HV00Qfdw_schema_not_found
    HV00Rfdw_table_not_found
    HV00Lfdw_unable_to_create_execution
    HV00Mfdw_unable_to_create_reply
    HV00Nfdw_unable_to_establish_connection
    Class P0 — PL/pgSQL Error
    P0000plpgsql_error
    P0001raise_exception
    P0002no_data_found
    P0003too_many_rows
    P0004assert_failure
    Class XX — Internal Error
    XX000internal_error
    XX001data_corrupted
    XX002index_corrupted

    Prev Up Next
    Part VIII. Appendixes Home Appendix B. Date/Time Support
    \ No newline at end of file +

    Table A.1. PostgreSQL Error Codes

    Error CodeCondition Name
    Class 00 — Successful Completion
    00000successful_completion
    Class 01 — Warning
    01000warning
    0100Cdynamic_result_sets_returned
    01008implicit_zero_bit_padding
    01003null_value_eliminated_in_set_function
    01007privilege_not_granted
    01006privilege_not_revoked
    01004string_data_right_truncation
    01P01deprecated_feature
    Class 02 — No Data (this is also a warning class per the SQL standard)
    02000no_data
    02001no_additional_dynamic_result_sets_returned
    Class 03 — SQL Statement Not Yet Complete
    03000sql_statement_not_yet_complete
    Class 08 — Connection Exception
    08000connection_exception
    08003connection_does_not_exist
    08006connection_failure
    08001sqlclient_unable_to_establish_sqlconnection
    08004sqlserver_rejected_establishment_of_sqlconnection
    08007transaction_resolution_unknown
    08P01protocol_violation
    Class 09 — Triggered Action Exception
    09000triggered_action_exception
    Class 0A — Feature Not Supported
    0A000feature_not_supported
    Class 0B — Invalid Transaction Initiation
    0B000invalid_transaction_initiation
    Class 0F — Locator Exception
    0F000locator_exception
    0F001invalid_locator_specification
    Class 0L — Invalid Grantor
    0L000invalid_grantor
    0LP01invalid_grant_operation
    Class 0P — Invalid Role Specification
    0P000invalid_role_specification
    Class 0Z — Diagnostics Exception
    0Z000diagnostics_exception
    0Z002stacked_diagnostics_accessed_without_active_handler
    Class 20 — Case Not Found
    20000case_not_found
    Class 21 — Cardinality Violation
    21000cardinality_violation
    Class 22 — Data Exception
    22000data_exception
    2202Earray_subscript_error
    22021character_not_in_repertoire
    22008datetime_field_overflow
    22012division_by_zero
    22005error_in_assignment
    2200Bescape_character_conflict
    22022indicator_overflow
    22015interval_field_overflow
    2201Einvalid_argument_for_logarithm
    22014invalid_argument_for_ntile_function
    22016invalid_argument_for_nth_value_function
    2201Finvalid_argument_for_power_function
    2201Ginvalid_argument_for_width_bucket_function
    22018invalid_character_value_for_cast
    22007invalid_datetime_format
    22019invalid_escape_character
    2200Dinvalid_escape_octet
    22025invalid_escape_sequence
    22P06nonstandard_use_of_escape_character
    22010invalid_indicator_parameter_value
    22023invalid_parameter_value
    22013invalid_preceding_or_following_size
    2201Binvalid_regular_expression
    2201Winvalid_row_count_in_limit_clause
    2201Xinvalid_row_count_in_result_offset_clause
    2202Hinvalid_tablesample_argument
    2202Ginvalid_tablesample_repeat
    22009invalid_time_zone_displacement_value
    2200Cinvalid_use_of_escape_character
    2200Gmost_specific_type_mismatch
    22004null_value_not_allowed
    22002null_value_no_indicator_parameter
    22003numeric_value_out_of_range
    2200Hsequence_generator_limit_exceeded
    22026string_data_length_mismatch
    22001string_data_right_truncation
    22011substring_error
    22027trim_error
    22024unterminated_c_string
    2200Fzero_length_character_string
    22P01floating_point_exception
    22P02invalid_text_representation
    22P03invalid_binary_representation
    22P04bad_copy_file_format
    22P05untranslatable_character
    2200Lnot_an_xml_document
    2200Minvalid_xml_document
    2200Ninvalid_xml_content
    2200Sinvalid_xml_comment
    2200Tinvalid_xml_processing_instruction
    22030duplicate_json_object_key_value
    22031invalid_argument_for_sql_json_datetime_function
    22032invalid_json_text
    22033invalid_sql_json_subscript
    22034more_than_one_sql_json_item
    22035no_sql_json_item
    22036non_numeric_sql_json_item
    22037non_unique_keys_in_a_json_object
    22038singleton_sql_json_item_required
    22039sql_json_array_not_found
    2203Asql_json_member_not_found
    2203Bsql_json_number_not_found
    2203Csql_json_object_not_found
    2203Dtoo_many_json_array_elements
    2203Etoo_many_json_object_members
    2203Fsql_json_scalar_required
    Class 23 — Integrity Constraint Violation
    23000integrity_constraint_violation
    23001restrict_violation
    23502not_null_violation
    23503foreign_key_violation
    23505unique_violation
    23514check_violation
    23P01exclusion_violation
    Class 24 — Invalid Cursor State
    24000invalid_cursor_state
    Class 25 — Invalid Transaction State
    25000invalid_transaction_state
    25001active_sql_transaction
    25002branch_transaction_already_active
    25008held_cursor_requires_same_isolation_level
    25003inappropriate_access_mode_for_branch_transaction
    25004inappropriate_isolation_level_for_branch_transaction
    25005no_active_sql_transaction_for_branch_transaction
    25006read_only_sql_transaction
    25007schema_and_data_statement_mixing_not_supported
    25P01no_active_sql_transaction
    25P02in_failed_sql_transaction
    25P03idle_in_transaction_session_timeout
    Class 26 — Invalid SQL Statement Name
    26000invalid_sql_statement_name
    Class 27 — Triggered Data Change Violation
    27000triggered_data_change_violation
    Class 28 — Invalid Authorization Specification
    28000invalid_authorization_specification
    28P01invalid_password
    Class 2B — Dependent Privilege Descriptors Still Exist
    2B000dependent_privilege_descriptors_still_exist
    2BP01dependent_objects_still_exist
    Class 2D — Invalid Transaction Termination
    2D000invalid_transaction_termination
    Class 2F — SQL Routine Exception
    2F000sql_routine_exception
    2F005function_executed_no_return_statement
    2F002modifying_sql_data_not_permitted
    2F003prohibited_sql_statement_attempted
    2F004reading_sql_data_not_permitted
    Class 34 — Invalid Cursor Name
    34000invalid_cursor_name
    Class 38 — External Routine Exception
    38000external_routine_exception
    38001containing_sql_not_permitted
    38002modifying_sql_data_not_permitted
    38003prohibited_sql_statement_attempted
    38004reading_sql_data_not_permitted
    Class 39 — External Routine Invocation Exception
    39000external_routine_invocation_exception
    39001invalid_sqlstate_returned
    39004null_value_not_allowed
    39P01trigger_protocol_violated
    39P02srf_protocol_violated
    39P03event_trigger_protocol_violated
    Class 3B — Savepoint Exception
    3B000savepoint_exception
    3B001invalid_savepoint_specification
    Class 3D — Invalid Catalog Name
    3D000invalid_catalog_name
    Class 3F — Invalid Schema Name
    3F000invalid_schema_name
    Class 40 — Transaction Rollback
    40000transaction_rollback
    40002transaction_integrity_constraint_violation
    40001serialization_failure
    40003statement_completion_unknown
    40P01deadlock_detected
    Class 42 — Syntax Error or Access Rule Violation
    42000syntax_error_or_access_rule_violation
    42601syntax_error
    42501insufficient_privilege
    42846cannot_coerce
    42803grouping_error
    42P20windowing_error
    42P19invalid_recursion
    42830invalid_foreign_key
    42602invalid_name
    42622name_too_long
    42939reserved_name
    42804datatype_mismatch
    42P18indeterminate_datatype
    42P21collation_mismatch
    42P22indeterminate_collation
    42809wrong_object_type
    428C9generated_always
    42703undefined_column
    42883undefined_function
    42P01undefined_table
    42P02undefined_parameter
    42704undefined_object
    42701duplicate_column
    42P03duplicate_cursor
    42P04duplicate_database
    42723duplicate_function
    42P05duplicate_prepared_statement
    42P06duplicate_schema
    42P07duplicate_table
    42712duplicate_alias
    42710duplicate_object
    42702ambiguous_column
    42725ambiguous_function
    42P08ambiguous_parameter
    42P09ambiguous_alias
    42P10invalid_column_reference
    42611invalid_column_definition
    42P11invalid_cursor_definition
    42P12invalid_database_definition
    42P13invalid_function_definition
    42P14invalid_prepared_statement_definition
    42P15invalid_schema_definition
    42P16invalid_table_definition
    42P17invalid_object_definition
    Class 44 — WITH CHECK OPTION Violation
    44000with_check_option_violation
    Class 53 — Insufficient Resources
    53000insufficient_resources
    53100disk_full
    53200out_of_memory
    53300too_many_connections
    53400configuration_limit_exceeded
    Class 54 — Program Limit Exceeded
    54000program_limit_exceeded
    54001statement_too_complex
    54011too_many_columns
    54023too_many_arguments
    Class 55 — Object Not In Prerequisite State
    55000object_not_in_prerequisite_state
    55006object_in_use
    55P02cant_change_runtime_param
    55P03lock_not_available
    55P04unsafe_new_enum_value_usage
    Class 57 — Operator Intervention
    57000operator_intervention
    57014query_canceled
    57P01admin_shutdown
    57P02crash_shutdown
    57P03cannot_connect_now
    57P04database_dropped
    Class 58 — System Error (errors external to PostgreSQL itself)
    58000system_error
    58030io_error
    58P01undefined_file
    58P02duplicate_file
    Class 72 — Snapshot Failure
    72000snapshot_too_old
    Class F0 — Configuration File Error
    F0000config_file_error
    F0001lock_file_exists
    Class HV — Foreign Data Wrapper Error (SQL/MED)
    HV000fdw_error
    HV005fdw_column_name_not_found
    HV002fdw_dynamic_parameter_value_needed
    HV010fdw_function_sequence_error
    HV021fdw_inconsistent_descriptor_information
    HV024fdw_invalid_attribute_value
    HV007fdw_invalid_column_name
    HV008fdw_invalid_column_number
    HV004fdw_invalid_data_type
    HV006fdw_invalid_data_type_descriptors
    HV091fdw_invalid_descriptor_field_identifier
    HV00Bfdw_invalid_handle
    HV00Cfdw_invalid_option_index
    HV00Dfdw_invalid_option_name
    HV090fdw_invalid_string_length_or_buffer_length
    HV00Afdw_invalid_string_format
    HV009fdw_invalid_use_of_null_pointer
    HV014fdw_too_many_handles
    HV001fdw_out_of_memory
    HV00Pfdw_no_schemas
    HV00Jfdw_option_name_not_found
    HV00Kfdw_reply_handle
    HV00Qfdw_schema_not_found
    HV00Rfdw_table_not_found
    HV00Lfdw_unable_to_create_execution
    HV00Mfdw_unable_to_create_reply
    HV00Nfdw_unable_to_establish_connection
    Class P0 — PL/pgSQL Error
    P0000plpgsql_error
    P0001raise_exception
    P0002no_data_found
    P0003too_many_rows
    P0004assert_failure
    Class XX — Internal Error
    XX000internal_error
    XX001data_corrupted
    XX002index_corrupted

    Prev Up Next
    Part VIII. Appendixes Home Appendix B. Date/Time Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/error-message-reporting.html postgresql-13-13.12/doc/src/sgml/html/error-message-reporting.html --- postgresql-13-13.11/doc/src/sgml/html/error-message-reporting.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/error-message-reporting.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -53.2. Reporting Errors Within the Server
    53.2. Reporting Errors Within the Server
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.2. Reporting Errors Within the Server

    +53.2. Reporting Errors Within the Server

    53.2. Reporting Errors Within the Server
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.2. Reporting Errors Within the Server

    Error, warning, and log messages generated within the server code should be created using ereport, or its older cousin elog. The use of this function is complex enough to @@ -242,4 +242,4 @@ routines will not affect it. That would not be true if you were to write strerror(errno) explicitly in errmsg's parameter list; accordingly, do not do so. -

    Prev Up Next
    53.1. Formatting Home 53.3. Error Message Style Guide
    \ No newline at end of file +

    Prev Up Next
    53.1. Formatting Home 53.3. Error Message Style Guide
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/error-style-guide.html postgresql-13-13.12/doc/src/sgml/html/error-style-guide.html --- postgresql-13-13.11/doc/src/sgml/html/error-style-guide.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/error-style-guide.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -53.3. Error Message Style Guide
    53.3. Error Message Style Guide
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.3. Error Message Style Guide

    +53.3. Error Message Style Guide

    53.3. Error Message Style Guide
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.3. Error Message Style Guide

    This style guide is offered in the hope of maintaining a consistent, user-friendly style throughout all the messages generated by PostgreSQL. @@ -247,4 +247,4 @@ Keep in mind that error message texts need to be translated into other languages. Follow the guidelines in Section 54.2.2 to avoid making life difficult for translators. -

    Prev Up Next
    53.2. Reporting Errors Within the Server Home 53.4. Miscellaneous Coding Conventions
    \ No newline at end of file +

    Prev Up Next
    53.2. Reporting Errors Within the Server Home 53.4. Miscellaneous Coding Conventions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-log-registration.html postgresql-13-13.12/doc/src/sgml/html/event-log-registration.html --- postgresql-13-13.11/doc/src/sgml/html/event-log-registration.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-log-registration.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.12. Registering Event Log on Windows
    18.12. Registering Event Log on Windows
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.12. Registering Event Log on Windows

    +18.12. Registering Event Log on Windows

    18.12. Registering Event Log on Windows
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.12. Registering Event Log on Windows

    To register a Windows event log library with the operating system, issue this command: @@ -25,4 +25,4 @@ To enable event logging in the database server, modify log_destination to include eventlog in postgresql.conf. -

    Prev Up Next
    18.11. Secure TCP/IP Connections with SSH Tunnels Home Chapter 19. Server Configuration
    \ No newline at end of file +

    Prev Up Next
    18.11. Secure TCP/IP Connections with SSH Tunnels Home Chapter 19. Server Configuration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-trigger-definition.html postgresql-13-13.12/doc/src/sgml/html/event-trigger-definition.html --- postgresql-13-13.11/doc/src/sgml/html/event-trigger-definition.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-trigger-definition.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -39.1. Overview of Event Trigger Behavior
    39.1. Overview of Event Trigger Behavior
    Prev UpChapter 39. Event TriggersHome Next

    39.1. Overview of Event Trigger Behavior

    +39.1. Overview of Event Trigger Behavior

    39.1. Overview of Event Trigger Behavior
    Prev UpChapter 39. Event TriggersHome Next

    39.1. Overview of Event Trigger Behavior

    An event trigger fires whenever the event with which it is associated occurs in the database in which it is defined. Currently, the only supported events are @@ -75,4 +75,4 @@ trigger can be fired only for particular commands which the user wishes to intercept. A common use of such triggers is to restrict the range of DDL operations which users may perform. -

    Prev Up Next
    Chapter 39. Event Triggers Home 39.2. Event Trigger Firing Matrix
    \ No newline at end of file +

    Prev Up Next
    Chapter 39. Event Triggers Home 39.2. Event Trigger Firing Matrix
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-trigger-example.html postgresql-13-13.12/doc/src/sgml/html/event-trigger-example.html --- postgresql-13-13.11/doc/src/sgml/html/event-trigger-example.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-trigger-example.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -39.4. A Complete Event Trigger Example
    39.4. A Complete Event Trigger Example
    Prev UpChapter 39. Event TriggersHome Next

    39.4. A Complete Event Trigger Example

    +39.4. A Complete Event Trigger Example

    39.4. A Complete Event Trigger Example
    Prev UpChapter 39. Event TriggersHome Next

    39.4. A Complete Event Trigger Example

    Here is a very simple example of an event trigger function written in C. (Examples of triggers written in procedural languages can be found in the documentation of the procedural languages.) @@ -75,4 +75,4 @@

    (Recall that DDL commands on event triggers themselves are not affected by event triggers.) -

    Prev Up Next
    39.3. Writing Event Trigger Functions in C Home 39.5. A Table Rewrite Event Trigger Example
    \ No newline at end of file +

    Prev Up Next
    39.3. Writing Event Trigger Functions in C Home 39.5. A Table Rewrite Event Trigger Example
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-trigger-interface.html postgresql-13-13.12/doc/src/sgml/html/event-trigger-interface.html --- postgresql-13-13.11/doc/src/sgml/html/event-trigger-interface.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-trigger-interface.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -39.3. Writing Event Trigger Functions in C
    39.3. Writing Event Trigger Functions in C
    Prev UpChapter 39. Event TriggersHome Next

    39.3. Writing Event Trigger Functions in C

    +39.3. Writing Event Trigger Functions in C

    39.3. Writing Event Trigger Functions in C
    Prev UpChapter 39. Event TriggersHome Next

    39.3. Writing Event Trigger Functions in C

    This section describes the low-level details of the interface to an event trigger function. This information is only needed when writing event trigger functions in C. If you are using a higher-level language @@ -65,4 +65,4 @@ An event trigger function must return a NULL pointer (not an SQL null value, that is, do not set isNull true). -

    Prev Up Next
    39.2. Event Trigger Firing Matrix Home 39.4. A Complete Event Trigger Example
    \ No newline at end of file +

    Prev Up Next
    39.2. Event Trigger Firing Matrix Home 39.4. A Complete Event Trigger Example
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-trigger-matrix.html postgresql-13-13.12/doc/src/sgml/html/event-trigger-matrix.html --- postgresql-13-13.11/doc/src/sgml/html/event-trigger-matrix.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-trigger-matrix.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -39.2. Event Trigger Firing Matrix
    39.2. Event Trigger Firing Matrix
    Prev UpChapter 39. Event TriggersHome Next

    39.2. Event Trigger Firing Matrix

    +39.2. Event Trigger Firing Matrix

    39.2. Event Trigger Firing Matrix
    Prev UpChapter 39. Event TriggersHome Next

    39.2. Event Trigger Firing Matrix

    Table 39.1 lists all commands for which event triggers are supported. -

    Table 39.1. Event Trigger Support by Command Tag

    Command Tagddl_​command_​startddl_​command_​endsql_​droptable_​rewriteNotes
    ALTER AGGREGATEXX-- 
    ALTER COLLATIONXX-- 
    ALTER CONVERSIONXX-- 
    ALTER DOMAINXX-- 
    ALTER DEFAULT PRIVILEGESXX-- 
    ALTER EXTENSIONXX-- 
    ALTER FOREIGN DATA WRAPPERXX-- 
    ALTER FOREIGN TABLEXXX- 
    ALTER FUNCTIONXX-- 
    ALTER LANGUAGEXX-- 
    ALTER LARGE OBJECTXX-- 
    ALTER MATERIALIZED VIEWXX-- 
    ALTER OPERATORXX-- 
    ALTER OPERATOR CLASSXX-- 
    ALTER OPERATOR FAMILYXX-- 
    ALTER POLICYXX-- 
    ALTER PROCEDUREXX-- 
    ALTER PUBLICATIONXX-- 
    ALTER ROUTINEXX-- 
    ALTER SCHEMAXX-- 
    ALTER SEQUENCEXX-- 
    ALTER SERVERXX-- 
    ALTER STATISTICSXX-- 
    ALTER SUBSCRIPTIONXX-- 
    ALTER TABLEXXXX 
    ALTER TEXT SEARCH CONFIGURATIONXX-- 
    ALTER TEXT SEARCH DICTIONARYXX-- 
    ALTER TEXT SEARCH PARSERXX-- 
    ALTER TEXT SEARCH TEMPLATEXX-- 
    ALTER TRIGGERXX-- 
    ALTER TYPEXX-X 
    ALTER USER MAPPINGXX-- 
    ALTER VIEWXX-- 
    COMMENTXX--Only for local objects
    CREATE ACCESS METHODXX-- 
    CREATE AGGREGATEXX-- 
    CREATE CASTXX-- 
    CREATE COLLATIONXX-- 
    CREATE CONVERSIONXX-- 
    CREATE DOMAINXX-- 
    CREATE EXTENSIONXX-- 
    CREATE FOREIGN DATA WRAPPERXX-- 
    CREATE FOREIGN TABLEXX-- 
    CREATE FUNCTIONXX-- 
    CREATE INDEXXX-- 
    CREATE LANGUAGEXX-- 
    CREATE MATERIALIZED VIEWXX-- 
    CREATE OPERATORXX-- 
    CREATE OPERATOR CLASSXX-- 
    CREATE OPERATOR FAMILYXX-- 
    CREATE POLICYXX-- 
    CREATE PROCEDUREXX-- 
    CREATE PUBLICATIONXX-- 
    CREATE RULEXX-- 
    CREATE SCHEMAXX-- 
    CREATE SEQUENCEXX-- 
    CREATE SERVERXX-- 
    CREATE STATISTICSXX-- 
    CREATE SUBSCRIPTIONXX-- 
    CREATE TABLEXX-- 
    CREATE TABLE ASXX-- 
    CREATE TEXT SEARCH CONFIGURATIONXX-- 
    CREATE TEXT SEARCH DICTIONARYXX-- 
    CREATE TEXT SEARCH PARSERXX-- 
    CREATE TEXT SEARCH TEMPLATEXX-- 
    CREATE TRIGGERXX-- 
    CREATE TYPEXX-- 
    CREATE USER MAPPINGXX-- 
    CREATE VIEWXX-- 
    DROP ACCESS METHODXXX- 
    DROP AGGREGATEXXX- 
    DROP CASTXXX- 
    DROP COLLATIONXXX- 
    DROP CONVERSIONXXX- 
    DROP DOMAINXXX- 
    DROP EXTENSIONXXX- 
    DROP FOREIGN DATA WRAPPERXXX- 
    DROP FOREIGN TABLEXXX- 
    DROP FUNCTIONXXX- 
    DROP INDEXXXX- 
    DROP LANGUAGEXXX- 
    DROP MATERIALIZED VIEWXXX- 
    DROP OPERATORXXX- 
    DROP OPERATOR CLASSXXX- 
    DROP OPERATOR FAMILYXXX- 
    DROP OWNEDXXX- 
    DROP POLICYXXX- 
    DROP PROCEDUREXXX- 
    DROP PUBLICATIONXXX- 
    DROP ROUTINEXXX- 
    DROP RULEXXX- 
    DROP SCHEMAXXX- 
    DROP SEQUENCEXXX- 
    DROP SERVERXXX- 
    DROP STATISTICSXXX- 
    DROP SUBSCRIPTIONXXX- 
    DROP TABLEXXX- 
    DROP TEXT SEARCH CONFIGURATIONXXX- 
    DROP TEXT SEARCH DICTIONARYXXX- 
    DROP TEXT SEARCH PARSERXXX- 
    DROP TEXT SEARCH TEMPLATEXXX- 
    DROP TRIGGERXXX- 
    DROP TYPEXXX- 
    DROP USER MAPPINGXXX- 
    DROP VIEWXXX- 
    GRANTXX--Only for local objects
    IMPORT FOREIGN SCHEMAXX-- 
    REFRESH MATERIALIZED VIEWXX-- 
    REVOKEXX--Only for local objects
    SECURITY LABELXX--Only for local objects
    SELECT INTOXX-- 

    Prev Up Next
    39.1. Overview of Event Trigger Behavior Home 39.3. Writing Event Trigger Functions in C
    \ No newline at end of file +

    Table 39.1. Event Trigger Support by Command Tag

    Command Tagddl_​command_​startddl_​command_​endsql_​droptable_​rewriteNotes
    ALTER AGGREGATEXX-- 
    ALTER COLLATIONXX-- 
    ALTER CONVERSIONXX-- 
    ALTER DOMAINXX-- 
    ALTER DEFAULT PRIVILEGESXX-- 
    ALTER EXTENSIONXX-- 
    ALTER FOREIGN DATA WRAPPERXX-- 
    ALTER FOREIGN TABLEXXX- 
    ALTER FUNCTIONXX-- 
    ALTER LANGUAGEXX-- 
    ALTER LARGE OBJECTXX-- 
    ALTER MATERIALIZED VIEWXX-- 
    ALTER OPERATORXX-- 
    ALTER OPERATOR CLASSXX-- 
    ALTER OPERATOR FAMILYXX-- 
    ALTER POLICYXX-- 
    ALTER PROCEDUREXX-- 
    ALTER PUBLICATIONXX-- 
    ALTER ROUTINEXX-- 
    ALTER SCHEMAXX-- 
    ALTER SEQUENCEXX-- 
    ALTER SERVERXX-- 
    ALTER STATISTICSXX-- 
    ALTER SUBSCRIPTIONXX-- 
    ALTER TABLEXXXX 
    ALTER TEXT SEARCH CONFIGURATIONXX-- 
    ALTER TEXT SEARCH DICTIONARYXX-- 
    ALTER TEXT SEARCH PARSERXX-- 
    ALTER TEXT SEARCH TEMPLATEXX-- 
    ALTER TRIGGERXX-- 
    ALTER TYPEXX-X 
    ALTER USER MAPPINGXX-- 
    ALTER VIEWXX-- 
    COMMENTXX--Only for local objects
    CREATE ACCESS METHODXX-- 
    CREATE AGGREGATEXX-- 
    CREATE CASTXX-- 
    CREATE COLLATIONXX-- 
    CREATE CONVERSIONXX-- 
    CREATE DOMAINXX-- 
    CREATE EXTENSIONXX-- 
    CREATE FOREIGN DATA WRAPPERXX-- 
    CREATE FOREIGN TABLEXX-- 
    CREATE FUNCTIONXX-- 
    CREATE INDEXXX-- 
    CREATE LANGUAGEXX-- 
    CREATE MATERIALIZED VIEWXX-- 
    CREATE OPERATORXX-- 
    CREATE OPERATOR CLASSXX-- 
    CREATE OPERATOR FAMILYXX-- 
    CREATE POLICYXX-- 
    CREATE PROCEDUREXX-- 
    CREATE PUBLICATIONXX-- 
    CREATE RULEXX-- 
    CREATE SCHEMAXX-- 
    CREATE SEQUENCEXX-- 
    CREATE SERVERXX-- 
    CREATE STATISTICSXX-- 
    CREATE SUBSCRIPTIONXX-- 
    CREATE TABLEXX-- 
    CREATE TABLE ASXX-- 
    CREATE TEXT SEARCH CONFIGURATIONXX-- 
    CREATE TEXT SEARCH DICTIONARYXX-- 
    CREATE TEXT SEARCH PARSERXX-- 
    CREATE TEXT SEARCH TEMPLATEXX-- 
    CREATE TRIGGERXX-- 
    CREATE TYPEXX-- 
    CREATE USER MAPPINGXX-- 
    CREATE VIEWXX-- 
    DROP ACCESS METHODXXX- 
    DROP AGGREGATEXXX- 
    DROP CASTXXX- 
    DROP COLLATIONXXX- 
    DROP CONVERSIONXXX- 
    DROP DOMAINXXX- 
    DROP EXTENSIONXXX- 
    DROP FOREIGN DATA WRAPPERXXX- 
    DROP FOREIGN TABLEXXX- 
    DROP FUNCTIONXXX- 
    DROP INDEXXXX- 
    DROP LANGUAGEXXX- 
    DROP MATERIALIZED VIEWXXX- 
    DROP OPERATORXXX- 
    DROP OPERATOR CLASSXXX- 
    DROP OPERATOR FAMILYXXX- 
    DROP OWNEDXXX- 
    DROP POLICYXXX- 
    DROP PROCEDUREXXX- 
    DROP PUBLICATIONXXX- 
    DROP ROUTINEXXX- 
    DROP RULEXXX- 
    DROP SCHEMAXXX- 
    DROP SEQUENCEXXX- 
    DROP SERVERXXX- 
    DROP STATISTICSXXX- 
    DROP SUBSCRIPTIONXXX- 
    DROP TABLEXXX- 
    DROP TEXT SEARCH CONFIGURATIONXXX- 
    DROP TEXT SEARCH DICTIONARYXXX- 
    DROP TEXT SEARCH PARSERXXX- 
    DROP TEXT SEARCH TEMPLATEXXX- 
    DROP TRIGGERXXX- 
    DROP TYPEXXX- 
    DROP USER MAPPINGXXX- 
    DROP VIEWXXX- 
    GRANTXX--Only for local objects
    IMPORT FOREIGN SCHEMAXX-- 
    REFRESH MATERIALIZED VIEWXX-- 
    REVOKEXX--Only for local objects
    SECURITY LABELXX--Only for local objects
    SELECT INTOXX-- 

    Prev Up Next
    39.1. Overview of Event Trigger Behavior Home 39.3. Writing Event Trigger Functions in C
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-trigger-table-rewrite-example.html postgresql-13-13.12/doc/src/sgml/html/event-trigger-table-rewrite-example.html --- postgresql-13-13.11/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -39.5. A Table Rewrite Event Trigger Example
    39.5. A Table Rewrite Event Trigger Example
    Prev UpChapter 39. Event TriggersHome Next

    39.5. A Table Rewrite Event Trigger Example

    +39.5. A Table Rewrite Event Trigger Example

    39.5. A Table Rewrite Event Trigger Example
    Prev UpChapter 39. Event TriggersHome Next

    39.5. A Table Rewrite Event Trigger Example

    Thanks to the table_rewrite event, it is possible to implement a table rewriting policy only allowing the rewrite in maintenance windows.

    @@ -45,4 +45,4 @@ ON table_rewrite EXECUTE FUNCTION no_rewrite();

    -

    Prev Up Next
    39.4. A Complete Event Trigger Example Home Chapter 40. The Rule System
    \ No newline at end of file +

    Prev Up Next
    39.4. A Complete Event Trigger Example Home Chapter 40. The Rule System
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/event-triggers.html postgresql-13-13.12/doc/src/sgml/html/event-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/event-triggers.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/event-triggers.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 39. Event Triggers
    Chapter 39. Event Triggers
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 39. Event Triggers

    Table of Contents

    39.1. Overview of Event Trigger Behavior
    39.2. Event Trigger Firing Matrix
    39.3. Writing Event Trigger Functions in C
    39.4. A Complete Event Trigger Example
    39.5. A Table Rewrite Event Trigger Example

    +Chapter 39. Event Triggers

    Chapter 39. Event Triggers
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 39. Event Triggers

    Table of Contents

    39.1. Overview of Event Trigger Behavior
    39.2. Event Trigger Firing Matrix
    39.3. Writing Event Trigger Functions in C
    39.4. A Complete Event Trigger Example
    39.5. A Table Rewrite Event Trigger Example

    To supplement the trigger mechanism discussed in Chapter 38, PostgreSQL also provides event triggers. Unlike regular triggers, which are attached to a single table and capture only DML events, @@ -9,4 +9,4 @@ Like regular triggers, event triggers can be written in any procedural language that includes event trigger support, or in C, but not in plain SQL. -

    Prev Up Next
    38.4. A Complete Trigger Example Home 39.1. Overview of Event Trigger Behavior
    \ No newline at end of file +

    Prev Up Next
    38.4. A Complete Trigger Example Home 39.1. Overview of Event Trigger Behavior
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/executor.html postgresql-13-13.12/doc/src/sgml/html/executor.html --- postgresql-13-13.11/doc/src/sgml/html/executor.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/executor.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.6. Executor
    50.6. Executor
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.6. Executor

    +50.6. Executor

    50.6. Executor
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.6. Executor

    The executor takes the plan created by the planner/optimizer and recursively processes it to extract the required set of rows. This is essentially a demand-pull pipeline mechanism. @@ -67,4 +67,4 @@ trivial plan tree consisting of a single Result node, which computes just one result row, feeding that up to ModifyTable to perform the insertion. -

    Prev Up Next
    50.5. Planner/Optimizer Home Chapter 51. System Catalogs
    \ No newline at end of file +

    Prev Up Next
    50.5. Planner/Optimizer Home Chapter 51. System Catalogs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/explicit-joins.html postgresql-13-13.12/doc/src/sgml/html/explicit-joins.html --- postgresql-13-13.11/doc/src/sgml/html/explicit-joins.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/explicit-joins.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -14.3. Controlling the Planner with Explicit JOIN Clauses
    14.3. Controlling the Planner with Explicit JOIN Clauses
    Prev UpChapter 14. Performance TipsHome Next

    14.3. Controlling the Planner with Explicit JOIN Clauses

    +14.3. Controlling the Planner with Explicit JOIN Clauses

    14.3. Controlling the Planner with Explicit JOIN Clauses
    Prev UpChapter 14. Performance TipsHome Next

    14.3. Controlling the Planner with Explicit JOIN Clauses

    It is possible to control the query planner to some extent by using the explicit JOIN syntax. To see why this matters, we first need some background. @@ -141,4 +141,4 @@ to control join order with explicit joins). But you might set them differently if you are trying to fine-tune the trade-off between planning time and run time. -

    Prev Up Next
    14.2. Statistics Used by the Planner Home 14.4. Populating a Database
    \ No newline at end of file +

    Prev Up Next
    14.2. Statistics Used by the Planner Home 14.4. Populating a Database
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/explicit-locking.html postgresql-13-13.12/doc/src/sgml/html/explicit-locking.html --- postgresql-13-13.11/doc/src/sgml/html/explicit-locking.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/explicit-locking.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -13.3. Explicit Locking
    13.3. Explicit Locking
    Prev UpChapter 13. Concurrency ControlHome Next

    13.3. Explicit Locking

    13.3.1. Table-Level Locks
    13.3.2. Row-Level Locks
    13.3.3. Page-Level Locks
    13.3.4. Deadlocks
    13.3.5. Advisory Locks

    +13.3. Explicit Locking

    13.3. Explicit Locking
    Prev UpChapter 13. Concurrency ControlHome Next

    13.3. Explicit Locking

    13.3.1. Table-Level Locks
    13.3.2. Row-Level Locks
    13.3.3. Page-Level Locks
    13.3.4. Deadlocks
    13.3.5. Advisory Locks

    PostgreSQL provides various lock modes to control concurrent access to data in tables. These modes can be used for application-controlled locking in situations where @@ -391,4 +391,4 @@

    The functions provided to manipulate advisory locks are described in Section 9.27.10. -

    Prev Up Next
    13.2. Transaction Isolation Home 13.4. Data Consistency Checks at the Application Level
    \ No newline at end of file +

    Prev Up Next
    13.2. Transaction Isolation Home 13.4. Data Consistency Checks at the Application Level
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/extend-extensions.html postgresql-13-13.12/doc/src/sgml/html/extend-extensions.html --- postgresql-13-13.11/doc/src/sgml/html/extend-extensions.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/extend-extensions.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.17. Packaging Related Objects into an Extension
    37.17. Packaging Related Objects into an Extension
    Prev UpChapter 37. Extending SQLHome Next

    37.17. Packaging Related Objects into an Extension

    37.17.1. Extension Files
    37.17.2. Extension Relocatability
    37.17.3. Extension Configuration Tables
    37.17.4. Extension Updates
    37.17.5. Installing Extensions Using Update Scripts
    37.17.6. Security Considerations for Extensions
    37.17.7. Extension Example

    +37.17. Packaging Related Objects into an Extension

    37.17. Packaging Related Objects into an Extension
    Prev UpChapter 37. Extending SQLHome Next

    37.17. Packaging Related Objects into an Extension

    37.17.1. Extension Files
    37.17.2. Extension Relocatability
    37.17.3. Extension Configuration Tables
    37.17.4. Extension Updates
    37.17.5. Installing Extensions Using Update Scripts
    37.17.6. Security Considerations for Extensions
    37.17.7. Extension Example

    A useful extension to PostgreSQL typically includes multiple SQL objects; for example, a new data type will require new functions, new operators, and probably new index operator classes. @@ -623,4 +623,4 @@ Once the files are installed, use the CREATE EXTENSION command to load the objects into any particular database. -

    Prev Up Next
    37.16. Interfacing Extensions to Indexes Home 37.18. Extension Building Infrastructure
    \ No newline at end of file +

    Prev Up Next
    37.16. Interfacing Extensions to Indexes Home 37.18. Extension Building Infrastructure
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/extend-how.html postgresql-13-13.12/doc/src/sgml/html/extend-how.html --- postgresql-13-13.11/doc/src/sgml/html/extend-how.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/extend-how.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.1. How Extensibility Works
    37.1. How Extensibility Works
    Prev UpChapter 37. Extending SQLHome Next

    37.1. How Extensibility Works

    +37.1. How Extensibility Works

    37.1. How Extensibility Works
    Prev UpChapter 37. Extending SQLHome Next

    37.1. How Extensibility Works

    PostgreSQL is extensible because its operation is catalog-driven. If you are familiar with standard relational database systems, you know that they store information @@ -30,4 +30,4 @@ fly” makes PostgreSQL uniquely suited for rapid prototyping of new applications and storage structures. -

    Prev Up Next
    Chapter 37. Extending SQL Home 37.2. The PostgreSQL Type System
    \ No newline at end of file +

    Prev Up Next
    Chapter 37. Extending SQL Home 37.2. The PostgreSQL Type System
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/extend-pgxs.html postgresql-13-13.12/doc/src/sgml/html/extend-pgxs.html --- postgresql-13-13.11/doc/src/sgml/html/extend-pgxs.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/extend-pgxs.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.18. Extension Building Infrastructure
    37.18. Extension Building Infrastructure
    Prev UpChapter 37. Extending SQLHome Next

    37.18. Extension Building Infrastructure

    +37.18. Extension Building Infrastructure

    37.18. Extension Building Infrastructure
    Prev UpChapter 37. Extending SQLHome Next

    37.18. Extension Building Infrastructure

    If you are thinking about distributing your PostgreSQL extension modules, setting up a portable build system for them can be fairly difficult. Therefore @@ -224,4 +224,4 @@ output_iso/results/ directory (for tests in ISOLATION), then copy them to expected/ if they match what you expect from the test. -

    Prev Up Next
    37.17. Packaging Related Objects into an Extension Home Chapter 38. Triggers
    \ No newline at end of file +

    Prev Up Next
    37.17. Packaging Related Objects into an Extension Home Chapter 38. Triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/extend-type-system.html postgresql-13-13.12/doc/src/sgml/html/extend-type-system.html --- postgresql-13-13.11/doc/src/sgml/html/extend-type-system.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/extend-type-system.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.2. The PostgreSQL Type System
    37.2. The PostgreSQL Type System
    Prev UpChapter 37. Extending SQLHome Next

    37.2. The PostgreSQL Type System

    37.2.1. Base Types
    37.2.2. Container Types
    37.2.3. Domains
    37.2.4. Pseudo-Types
    37.2.5. Polymorphic Types

    +37.2. The PostgreSQL Type System

    37.2. The PostgreSQL Type System
    Prev UpChapter 37. Extending SQLHome Next

    37.2. The PostgreSQL Type System

    37.2.1. Base Types
    37.2.2. Container Types
    37.2.3. Domains
    37.2.4. Pseudo-Types
    37.2.5. Polymorphic Types

    PostgreSQL data types can be divided into base types, container types, domains, and pseudo-types.

    37.2.1. Base Types

    @@ -204,4 +204,4 @@ the same as if you had written the appropriate number of anynonarray or anycompatiblenonarray parameters. -

    Prev Up Next
    37.1. How Extensibility Works Home 37.3. User-Defined Functions
    \ No newline at end of file +

    Prev Up Next
    37.1. How Extensibility Works Home 37.3. User-Defined Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/extend.html postgresql-13-13.12/doc/src/sgml/html/extend.html --- postgresql-13-13.11/doc/src/sgml/html/extend.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/extend.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 37. Extending SQL
    Chapter 37. Extending SQL
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 37. Extending SQL

    Table of Contents

    37.1. How Extensibility Works
    37.2. The PostgreSQL Type System
    37.2.1. Base Types
    37.2.2. Container Types
    37.2.3. Domains
    37.2.4. Pseudo-Types
    37.2.5. Polymorphic Types
    37.3. User-Defined Functions
    37.4. User-Defined Procedures
    37.5. Query Language (SQL) Functions
    37.5.1. Arguments for SQL Functions
    37.5.2. SQL Functions on Base Types
    37.5.3. SQL Functions on Composite Types
    37.5.4. SQL Functions with Output Parameters
    37.5.5. SQL Functions with Variable Numbers of Arguments
    37.5.6. SQL Functions with Default Values for Arguments
    37.5.7. SQL Functions as Table Sources
    37.5.8. SQL Functions Returning Sets
    37.5.9. SQL Functions Returning TABLE
    37.5.10. Polymorphic SQL Functions
    37.5.11. SQL Functions with Collations
    37.6. Function Overloading
    37.7. Function Volatility Categories
    37.8. Procedural Language Functions
    37.9. Internal Functions
    37.10. C-Language Functions
    37.10.1. Dynamic Loading
    37.10.2. Base Types in C-Language Functions
    37.10.3. Version 1 Calling Conventions
    37.10.4. Writing Code
    37.10.5. Compiling and Linking Dynamically-Loaded Functions
    37.10.6. Composite-Type Arguments
    37.10.7. Returning Rows (Composite Types)
    37.10.8. Returning Sets
    37.10.9. Polymorphic Arguments and Return Types
    37.10.10. Shared Memory and LWLocks
    37.10.11. Using C++ for Extensibility
    37.11. Function Optimization Information
    37.12. User-Defined Aggregates
    37.12.1. Moving-Aggregate Mode
    37.12.2. Polymorphic and Variadic Aggregates
    37.12.3. Ordered-Set Aggregates
    37.12.4. Partial Aggregation
    37.12.5. Support Functions for Aggregates
    37.13. User-Defined Types
    37.13.1. TOAST Considerations
    37.14. User-Defined Operators
    37.15. Operator Optimization Information
    37.15.1. COMMUTATOR
    37.15.2. NEGATOR
    37.15.3. RESTRICT
    37.15.4. JOIN
    37.15.5. HASHES
    37.15.6. MERGES
    37.16. Interfacing Extensions to Indexes
    37.16.1. Index Methods and Operator Classes
    37.16.2. Index Method Strategies
    37.16.3. Index Method Support Routines
    37.16.4. An Example
    37.16.5. Operator Classes and Operator Families
    37.16.6. System Dependencies on Operator Classes
    37.16.7. Ordering Operators
    37.16.8. Special Features of Operator Classes
    37.17. Packaging Related Objects into an Extension
    37.17.1. Extension Files
    37.17.2. Extension Relocatability
    37.17.3. Extension Configuration Tables
    37.17.4. Extension Updates
    37.17.5. Installing Extensions Using Update Scripts
    37.17.6. Security Considerations for Extensions
    37.17.7. Extension Example
    37.18. Extension Building Infrastructure

    +Chapter 37. Extending SQL

    Chapter 37. Extending SQL
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 37. Extending SQL

    Table of Contents

    37.1. How Extensibility Works
    37.2. The PostgreSQL Type System
    37.2.1. Base Types
    37.2.2. Container Types
    37.2.3. Domains
    37.2.4. Pseudo-Types
    37.2.5. Polymorphic Types
    37.3. User-Defined Functions
    37.4. User-Defined Procedures
    37.5. Query Language (SQL) Functions
    37.5.1. Arguments for SQL Functions
    37.5.2. SQL Functions on Base Types
    37.5.3. SQL Functions on Composite Types
    37.5.4. SQL Functions with Output Parameters
    37.5.5. SQL Functions with Variable Numbers of Arguments
    37.5.6. SQL Functions with Default Values for Arguments
    37.5.7. SQL Functions as Table Sources
    37.5.8. SQL Functions Returning Sets
    37.5.9. SQL Functions Returning TABLE
    37.5.10. Polymorphic SQL Functions
    37.5.11. SQL Functions with Collations
    37.6. Function Overloading
    37.7. Function Volatility Categories
    37.8. Procedural Language Functions
    37.9. Internal Functions
    37.10. C-Language Functions
    37.10.1. Dynamic Loading
    37.10.2. Base Types in C-Language Functions
    37.10.3. Version 1 Calling Conventions
    37.10.4. Writing Code
    37.10.5. Compiling and Linking Dynamically-Loaded Functions
    37.10.6. Composite-Type Arguments
    37.10.7. Returning Rows (Composite Types)
    37.10.8. Returning Sets
    37.10.9. Polymorphic Arguments and Return Types
    37.10.10. Shared Memory and LWLocks
    37.10.11. Using C++ for Extensibility
    37.11. Function Optimization Information
    37.12. User-Defined Aggregates
    37.12.1. Moving-Aggregate Mode
    37.12.2. Polymorphic and Variadic Aggregates
    37.12.3. Ordered-Set Aggregates
    37.12.4. Partial Aggregation
    37.12.5. Support Functions for Aggregates
    37.13. User-Defined Types
    37.13.1. TOAST Considerations
    37.14. User-Defined Operators
    37.15. Operator Optimization Information
    37.15.1. COMMUTATOR
    37.15.2. NEGATOR
    37.15.3. RESTRICT
    37.15.4. JOIN
    37.15.5. HASHES
    37.15.6. MERGES
    37.16. Interfacing Extensions to Indexes
    37.16.1. Index Methods and Operator Classes
    37.16.2. Index Method Strategies
    37.16.3. Index Method Support Routines
    37.16.4. An Example
    37.16.5. Operator Classes and Operator Families
    37.16.6. System Dependencies on Operator Classes
    37.16.7. Ordering Operators
    37.16.8. Special Features of Operator Classes
    37.17. Packaging Related Objects into an Extension
    37.17.1. Extension Files
    37.17.2. Extension Relocatability
    37.17.3. Extension Configuration Tables
    37.17.4. Extension Updates
    37.17.5. Installing Extensions Using Update Scripts
    37.17.6. Security Considerations for Extensions
    37.17.7. Extension Example
    37.18. Extension Building Infrastructure

    In the sections that follow, we will discuss how you can extend the PostgreSQL SQL query language by adding: @@ -17,4 +17,4 @@

  • packages of related objects (starting in Section 37.17)

    • -

    Prev Up Next
    Part V. Server Programming Home 37.1. How Extensibility Works
    \ No newline at end of file +

    Prev Up Next
    Part V. Server Programming Home 37.1. How Extensibility Works
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/external-admin-tools.html postgresql-13-13.12/doc/src/sgml/html/external-admin-tools.html --- postgresql-13-13.11/doc/src/sgml/html/external-admin-tools.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/external-admin-tools.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,7 +1,7 @@ -H.2. Administration Tools
    H.2. Administration Tools
    Prev UpAppendix H. External ProjectsHome Next

    H.2. Administration Tools

    +H.2. Administration Tools

    H.2. Administration Tools
    Prev UpAppendix H. External ProjectsHome Next

    H.2. Administration Tools

    There are several administration tools available for PostgreSQL. The most popular is pgAdmin, and there are several commercially available ones as well. -

    Prev Up Next
    H.1. Client Interfaces Home H.3. Procedural Languages
    \ No newline at end of file +

    Prev Up Next
    H.1. Client Interfaces Home H.3. Procedural Languages
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/external-extensions.html postgresql-13-13.12/doc/src/sgml/html/external-extensions.html --- postgresql-13-13.11/doc/src/sgml/html/external-extensions.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/external-extensions.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -H.4. Extensions
    H.4. Extensions
    Prev UpAppendix H. External ProjectsHome Next

    H.4. Extensions

    +H.4. Extensions

    H.4. Extensions
    Prev UpAppendix H. External ProjectsHome Next

    H.4. Extensions

    PostgreSQL is designed to be easily extensible. For this reason, extensions loaded into the database can function just like features that are built in. The @@ -11,4 +11,4 @@ externally. For example, Slony-I is a popular master/standby replication solution that is developed independently from the core project. -

    Prev Up Next
    H.3. Procedural Languages Home Appendix I. The Source Code Repository
    \ No newline at end of file +

    Prev Up Next
    H.3. Procedural Languages Home Appendix I. The Source Code Repository
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/external-interfaces.html postgresql-13-13.12/doc/src/sgml/html/external-interfaces.html --- postgresql-13-13.11/doc/src/sgml/html/external-interfaces.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/external-interfaces.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -H.1. Client Interfaces
    H.1. Client Interfaces
    Prev UpAppendix H. External ProjectsHome Next

    H.1. Client Interfaces

    +H.1. Client Interfaces

    H.1. Client Interfaces
    Prev UpAppendix H. External ProjectsHome Next

    H.1. Client Interfaces

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

    Prev Up Next
    Appendix H. External Projects Home H.2. Administration Tools
    \ No newline at end of file +

    Table H.1. Externally Maintained Client Interfaces

    NameLanguageCommentsWebsite
    DBD::PgPerlPerl DBI driverhttps://metacpan.org/release/DBD-Pg
    JDBCJavaType 4 JDBC driverhttps://jdbc.postgresql.org/
    libpqxxC++C++ interfacehttps://pqxx.org/
    node-postgresJavaScriptNode.js driverhttps://node-postgres.com/
    Npgsql.NET.NET data providerhttps://www.npgsql.org/
    pgtclTcl https://github.com/flightaware/Pgtcl
    pgtclngTcl https://sourceforge.net/projects/pgtclng/
    pqGoPure Go driver for Go's database/sqlhttps://github.com/lib/pq
    psqlODBCODBCODBC driverhttps://odbc.postgresql.org/
    psycopgPythonDB API 2.0-complianthttps://www.psycopg.org/

    Prev Up Next
    Appendix H. External Projects Home H.2. Administration Tools
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/external-pl.html postgresql-13-13.12/doc/src/sgml/html/external-pl.html --- postgresql-13-13.11/doc/src/sgml/html/external-pl.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/external-pl.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -H.3. Procedural Languages
    H.3. Procedural Languages
    Prev UpAppendix H. External ProjectsHome Next

    H.3. Procedural Languages

    +H.3. Procedural Languages

    H.3. Procedural Languages
    Prev UpAppendix H. External ProjectsHome Next

    H.3. Procedural Languages

    PostgreSQL includes several procedural languages with the base distribution: PL/pgSQL, PL/Tcl, PL/Perl, and PL/Python. @@ -11,4 +11,4 @@ license as PostgreSQL. For more information on each procedural language, including licensing information, refer to its website and documentation. -

    Table H.2. Externally Maintained Procedural Languages

    NameLanguageWebsite
    PL/JavaJavahttps://tada.github.io/pljava/
    PL/LuaLuahttps://github.com/pllua/pllua-ng
    PL/RRhttps://github.com/postgres-plr/plr
    PL/shUnix shellhttps://github.com/petere/plsh
    PL/v8JavaScripthttps://github.com/plv8/plv8

    Prev Up Next
    H.2. Administration Tools Home H.4. Extensions
    \ No newline at end of file +

    Table H.2. Externally Maintained Procedural Languages

    NameLanguageWebsite
    PL/JavaJavahttps://tada.github.io/pljava/
    PL/LuaLuahttps://github.com/pllua/pllua-ng
    PL/RRhttps://github.com/postgres-plr/plr
    PL/shUnix shellhttps://github.com/petere/plsh
    PL/v8JavaScripthttps://github.com/plv8/plv8

    Prev Up Next
    H.2. Administration Tools Home H.4. Extensions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/external-projects.html postgresql-13-13.12/doc/src/sgml/html/external-projects.html --- postgresql-13-13.11/doc/src/sgml/html/external-projects.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/external-projects.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,7 +1,7 @@ -Appendix H. External Projects
    Appendix H. External Projects
    Prev UpPart VIII. AppendixesHome Next

    Appendix H. External Projects

    Table of Contents

    H.1. Client Interfaces
    H.2. Administration Tools
    H.3. Procedural Languages
    H.4. Extensions

    +Appendix H. External Projects

    Appendix H. External Projects
    Prev UpPart VIII. AppendixesHome Next

    Appendix H. External Projects

    Table of Contents

    H.1. Client Interfaces
    H.2. Administration Tools
    H.3. Procedural Languages
    H.4. Extensions

    PostgreSQL is a complex software project, and managing the project is difficult. We have found that many enhancements to PostgreSQL can be more efficiently developed separately from the core project. -

    Prev Up Next
    G.2. Server Applications Home H.1. Client Interfaces
    \ No newline at end of file +

    Prev Up Next
    G.2. Server Applications Home H.1. Client Interfaces
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdw-callbacks.html postgresql-13-13.12/doc/src/sgml/html/fdw-callbacks.html --- postgresql-13-13.11/doc/src/sgml/html/fdw-callbacks.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdw-callbacks.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -56.2. Foreign Data Wrapper Callback Routines
    56.2. Foreign Data Wrapper Callback Routines
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next
    Prev Up Next
    56.1. Foreign Data Wrapper Functions Home 56.3. Foreign Data Wrapper Helper Functions
    \ No newline at end of file +

    Prev Up Next
    56.1. Foreign Data Wrapper Functions Home 56.3. Foreign Data Wrapper Helper Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdw-functions.html postgresql-13-13.12/doc/src/sgml/html/fdw-functions.html --- postgresql-13-13.11/doc/src/sgml/html/fdw-functions.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdw-functions.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -56.1. Foreign Data Wrapper Functions
    56.1. Foreign Data Wrapper Functions
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.1. Foreign Data Wrapper Functions

    +56.1. Foreign Data Wrapper Functions

    56.1. Foreign Data Wrapper Functions
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.1. Foreign Data Wrapper Functions

    The FDW author needs to implement a handler function, and optionally a validator function. Both functions must be written in a compiled language such as C, using the version-1 interface. @@ -33,4 +33,4 @@ or ForeignTableRelationId). If no validator function is supplied, options are not checked at object creation time or object alteration time. -

    Prev Up Next
    Chapter 56. Writing a Foreign Data Wrapper Home 56.2. Foreign Data Wrapper Callback Routines
    \ No newline at end of file +

    Prev Up Next
    Chapter 56. Writing a Foreign Data Wrapper Home 56.2. Foreign Data Wrapper Callback Routines
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdw-helpers.html postgresql-13-13.12/doc/src/sgml/html/fdw-helpers.html --- postgresql-13-13.11/doc/src/sgml/html/fdw-helpers.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdw-helpers.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -56.3. Foreign Data Wrapper Helper Functions
    56.3. Foreign Data Wrapper Helper Functions
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.3. Foreign Data Wrapper Helper Functions

    +56.3. Foreign Data Wrapper Helper Functions

    56.3. Foreign Data Wrapper Helper Functions
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.3. Foreign Data Wrapper Helper Functions

    Several helper functions are exported from the core server so that authors of foreign data wrappers can get easy access to attributes of FDW-related objects, such as FDW options. @@ -111,4 +111,4 @@ This function returns a ForeignServer object for the foreign server with the given name. If the server is not found, return NULL if missing_ok is true, otherwise raise an error. -

    Prev Up Next
    56.2. Foreign Data Wrapper Callback Routines Home 56.4. Foreign Data Wrapper Query Planning
    \ No newline at end of file +

    Prev Up Next
    56.2. Foreign Data Wrapper Callback Routines Home 56.4. Foreign Data Wrapper Query Planning
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdw-planning.html postgresql-13-13.12/doc/src/sgml/html/fdw-planning.html --- postgresql-13-13.11/doc/src/sgml/html/fdw-planning.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdw-planning.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -56.4. Foreign Data Wrapper Query Planning
    56.4. Foreign Data Wrapper Query Planning
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.4. Foreign Data Wrapper Query Planning

    +56.4. Foreign Data Wrapper Query Planning

    56.4. Foreign Data Wrapper Query Planning
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.4. Foreign Data Wrapper Query Planning

    The FDW callback functions GetForeignRelSize, GetForeignPaths, GetForeignPlan, PlanForeignModify, GetForeignJoinPaths, @@ -188,4 +188,4 @@ exclusion constraints on remote tables are not locally known. This in turn implies that ON CONFLICT DO UPDATE is not supported, since the specification is mandatory there. -

    Prev Up Next
    56.3. Foreign Data Wrapper Helper Functions Home 56.5. Row Locking in Foreign Data Wrappers
    \ No newline at end of file +

    Prev Up Next
    56.3. Foreign Data Wrapper Helper Functions Home 56.5. Row Locking in Foreign Data Wrappers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdw-row-locking.html postgresql-13-13.12/doc/src/sgml/html/fdw-row-locking.html --- postgresql-13-13.11/doc/src/sgml/html/fdw-row-locking.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdw-row-locking.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -56.5. Row Locking in Foreign Data Wrappers
    56.5. Row Locking in Foreign Data Wrappers
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.5. Row Locking in Foreign Data Wrappers

    +56.5. Row Locking in Foreign Data Wrappers

    56.5. Row Locking in Foreign Data Wrappers
    Prev UpChapter 56. Writing a Foreign Data WrapperHome Next

    56.5. Row Locking in Foreign Data Wrappers

    If an FDW's underlying storage mechanism has a concept of locking individual rows to prevent concurrent updates of those rows, it is usually worthwhile for the FDW to perform row-level locking with as @@ -90,4 +90,4 @@ in src/include/nodes/plannodes.h, and the comments for ExecRowMark in src/include/nodes/execnodes.h for additional information. -

    Prev Up Next
    56.4. Foreign Data Wrapper Query Planning Home Chapter 57. Writing a Table Sampling Method
    \ No newline at end of file +

    Prev Up Next
    56.4. Foreign Data Wrapper Query Planning Home Chapter 57. Writing a Table Sampling Method
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fdwhandler.html postgresql-13-13.12/doc/src/sgml/html/fdwhandler.html --- postgresql-13-13.11/doc/src/sgml/html/fdwhandler.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fdwhandler.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 56. Writing a Foreign Data Wrapper
    Chapter 56. Writing a Foreign Data Wrapper
    Prev UpPart VII. InternalsHome Next

    Chapter 56. Writing a Foreign Data Wrapper

    Table of Contents

    56.1. Foreign Data Wrapper Functions
    56.2. Foreign Data Wrapper Callback Routines
    56.2.1. FDW Routines for Scanning Foreign Tables
    56.2.2. FDW Routines for Scanning Foreign Joins
    56.2.3. FDW Routines for Planning Post-Scan/Join Processing
    56.2.4. FDW Routines for Updating Foreign Tables
    56.2.5. FDW Routines for Row Locking
    56.2.6. FDW Routines for EXPLAIN
    56.2.7. FDW Routines for ANALYZE
    56.2.8. FDW Routines for IMPORT FOREIGN SCHEMA
    56.2.9. FDW Routines for Parallel Execution
    56.2.10. FDW Routines for Reparameterization of Paths
    56.3. Foreign Data Wrapper Helper Functions
    56.4. Foreign Data Wrapper Query Planning
    56.5. Row Locking in Foreign Data Wrappers

    +Chapter 56. Writing a Foreign Data Wrapper

    Chapter 56. Writing a Foreign Data Wrapper
    Prev UpPart VII. InternalsHome Next

    Chapter 56. Writing a Foreign Data Wrapper

    Table of Contents

    56.1. Foreign Data Wrapper Functions
    56.2. Foreign Data Wrapper Callback Routines
    56.2.1. FDW Routines for Scanning Foreign Tables
    56.2.2. FDW Routines for Scanning Foreign Joins
    56.2.3. FDW Routines for Planning Post-Scan/Join Processing
    56.2.4. FDW Routines for Updating Foreign Tables
    56.2.5. FDW Routines for Row Locking
    56.2.6. FDW Routines for EXPLAIN
    56.2.7. FDW Routines for ANALYZE
    56.2.8. FDW Routines for IMPORT FOREIGN SCHEMA
    56.2.9. FDW Routines for Parallel Execution
    56.2.10. FDW Routines for Reparameterization of Paths
    56.3. Foreign Data Wrapper Helper Functions
    56.4. Foreign Data Wrapper Query Planning
    56.5. Row Locking in Foreign Data Wrappers

    All operations on a foreign table are handled through its foreign data wrapper, which consists of a set of functions that the core server calls. The foreign data wrapper is responsible for fetching @@ -18,4 +18,4 @@ However, PostgreSQL does not implement that API, because the effort to accommodate it into PostgreSQL would be large, and the standard API hasn't gained wide adoption anyway. -

    Prev Up Next
    Chapter 55. Writing a Procedural Language Handler Home 56.1. Foreign Data Wrapper Functions
    \ No newline at end of file +

    Prev Up Next
    Chapter 55. Writing a Procedural Language Handler Home 56.1. Foreign Data Wrapper Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/features-sql-standard.html postgresql-13-13.12/doc/src/sgml/html/features-sql-standard.html --- postgresql-13-13.11/doc/src/sgml/html/features-sql-standard.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/features-sql-standard.html 2023-08-07 20:32:35.000000000 +0000 @@ -1,4 +1,4 @@ -D.1. Supported Features
    D.1. Supported Features
    Prev UpAppendix D. SQL ConformanceHome Next

    D.1. Supported Features

    +D.1. Supported Features

    D.1. Supported Features
    Prev UpAppendix D. SQL ConformanceHome Next

    D.1. Supported Features

    IdentifierCore?DescriptionComment
    B012 Embedded C 
    B021 Direct SQL 
    E011CoreNumeric data types 
    E011-01CoreINTEGER and SMALLINT data types 
    E011-02CoreREAL, DOUBLE PRECISION, and FLOAT data types 
    E011-03CoreDECIMAL and NUMERIC data types 
    E011-04CoreArithmetic operators 
    E011-05CoreNumeric comparison 
    E011-06CoreImplicit casting among the numeric data types 
    E021CoreCharacter data types 
    E021-01CoreCHARACTER data type 
    E021-02CoreCHARACTER VARYING data type 
    E021-03CoreCharacter literals 
    E021-04CoreCHARACTER_LENGTH functiontrims trailing spaces from CHARACTER values before counting
    E021-05CoreOCTET_LENGTH function 
    E021-06CoreSUBSTRING function 
    E021-07CoreCharacter concatenation 
    E021-08CoreUPPER and LOWER functions 
    E021-09CoreTRIM function 
    E021-10CoreImplicit casting among the character string types 
    E021-11CorePOSITION function 
    E021-12CoreCharacter comparison 
    E031CoreIdentifiers 
    E031-01CoreDelimited identifiers 
    E031-02CoreLower case identifiers 
    E031-03CoreTrailing underscore 
    E051CoreBasic query specification 
    E051-01CoreSELECT DISTINCT 
    E051-02CoreGROUP BY clause 
    E051-04CoreGROUP BY can contain columns not in <select list> 
    E051-05CoreSelect list items can be renamed 
    E051-06CoreHAVING clause 
    E051-07CoreQualified * in select list 
    E051-08CoreCorrelation names in the FROM clause 
    E051-09CoreRename columns in the FROM clause 
    E061CoreBasic predicates and search conditions 
    E061-01CoreComparison predicate 
    E061-02CoreBETWEEN predicate 
    E061-03CoreIN predicate with list of values 
    E061-04CoreLIKE predicate 
    E061-05CoreLIKE predicate ESCAPE clause 
    E061-06CoreNULL predicate 
    E061-07CoreQuantified comparison predicate 
    E061-08CoreEXISTS predicate 
    E061-09CoreSubqueries in comparison predicate 
    E061-11CoreSubqueries in IN predicate 
    E061-12CoreSubqueries in quantified comparison predicate 
    E061-13CoreCorrelated subqueries 
    E061-14CoreSearch condition 
    E071CoreBasic query expressions 
    E071-01CoreUNION DISTINCT table operator 
    E071-02CoreUNION ALL table operator 
    E071-03CoreEXCEPT DISTINCT table operator 
    E071-05CoreColumns combined via table operators need not have exactly the same data type 
    E071-06CoreTable operators in subqueries 
    E081CoreBasic Privileges 
    E081-01CoreSELECT privilege 
    E081-02CoreDELETE privilege 
    E081-03CoreINSERT privilege at the table level 
    E081-04CoreUPDATE privilege at the table level 
    E081-05CoreUPDATE privilege at the column level 
    E081-06CoreREFERENCES privilege at the table level 
    E081-07CoreREFERENCES privilege at the column level 
    E081-08CoreWITH GRANT OPTION 
    E081-09CoreUSAGE privilege 
    E081-10CoreEXECUTE privilege 
    E091CoreSet functions 
    E091-01CoreAVG 
    E091-02CoreCOUNT 
    E091-03CoreMAX 
    E091-04CoreMIN 
    E091-05CoreSUM 
    E091-06CoreALL quantifier 
    E091-07CoreDISTINCT quantifier 
    E101CoreBasic data manipulation 
    E101-01CoreINSERT statement 
    E101-03CoreSearched UPDATE statement 
    E101-04CoreSearched DELETE statement 
    E111CoreSingle row SELECT statement 
    E121CoreBasic cursor support 
    E121-01CoreDECLARE CURSOR 
    E121-02CoreORDER BY columns need not be in select list 
    E121-03CoreValue expressions in ORDER BY clause 
    E121-04CoreOPEN statement 
    E121-06CorePositioned UPDATE statement 
    E121-07CorePositioned DELETE statement 
    E121-08CoreCLOSE statement 
    E121-10CoreFETCH statement implicit NEXT 
    E121-17CoreWITH HOLD cursors 
    E131CoreNull value support (nulls in lieu of values) 
    E141CoreBasic integrity constraints 
    E141-01CoreNOT NULL constraints 
    E141-02CoreUNIQUE constraints of NOT NULL columns 
    E141-03CorePRIMARY KEY constraints 
    E141-04CoreBasic FOREIGN KEY constraint with the NO ACTION default for both referential delete action and referential update action 
    E141-06CoreCHECK constraints 
    E141-07CoreColumn defaults 
    E141-08CoreNOT NULL inferred on PRIMARY KEY 
    E141-10CoreNames in a foreign key can be specified in any order 
    E151CoreTransaction support 
    E151-01CoreCOMMIT statement 
    E151-02CoreROLLBACK statement 
    E152CoreBasic SET TRANSACTION statement 
    E152-01CoreSET TRANSACTION statement: ISOLATION LEVEL SERIALIZABLE clause 
    E152-02CoreSET TRANSACTION statement: READ ONLY and READ WRITE clauses 
    E153CoreUpdatable queries with subqueries 
    E161CoreSQL comments using leading double minus 
    E171CoreSQLSTATE support 
    E182CoreHost language binding 
    F021CoreBasic information schema 
    F021-01CoreCOLUMNS view 
    F021-02CoreTABLES view 
    F021-03CoreVIEWS view 
    F021-04CoreTABLE_CONSTRAINTS view 
    F021-05CoreREFERENTIAL_CONSTRAINTS view 
    F021-06CoreCHECK_CONSTRAINTS view 
    F031CoreBasic schema manipulation 
    F031-01CoreCREATE TABLE statement to create persistent base tables 
    F031-02CoreCREATE VIEW statement 
    F031-03CoreGRANT statement 
    F031-04CoreALTER TABLE statement: ADD COLUMN clause 
    F031-13CoreDROP TABLE statement: RESTRICT clause 
    F031-16CoreDROP VIEW statement: RESTRICT clause 
    F031-19CoreREVOKE statement: RESTRICT clause 
    F032 CASCADE drop behavior 
    F033 ALTER TABLE statement: DROP COLUMN clause 
    F034 Extended REVOKE statement 
    F034-01 REVOKE statement performed by other than the owner of a schema object 
    F034-02 REVOKE statement: GRANT OPTION FOR clause 
    F034-03 REVOKE statement to revoke a privilege that the grantee has WITH GRANT OPTION 
    F041CoreBasic joined table 
    F041-01CoreInner join (but not necessarily the INNER keyword) 
    F041-02CoreINNER keyword 
    F041-03CoreLEFT OUTER JOIN 
    F041-04CoreRIGHT OUTER JOIN 
    F041-05CoreOuter joins can be nested 
    F041-07CoreThe inner table in a left or right outer join can also be used in an inner join 
    F041-08CoreAll comparison operators are supported (rather than just =) 
    F051CoreBasic date and time 
    F051-01CoreDATE data type (including support of DATE literal) 
    F051-02CoreTIME data type (including support of TIME literal) with fractional seconds precision of at least 0 
    F051-03CoreTIMESTAMP data type (including support of TIMESTAMP literal) with fractional seconds precision of at least 0 and 6 
    F051-04CoreComparison predicate on DATE, TIME, and TIMESTAMP data types 
    F051-05CoreExplicit CAST between datetime types and character string types 
    F051-06CoreCURRENT_DATE 
    F051-07CoreLOCALTIME 
    F051-08CoreLOCALTIMESTAMP 
    F052 Intervals and datetime arithmetic 
    F053 OVERLAPS predicate 
    F081CoreUNION and EXCEPT in views 
    F111 Isolation levels other than SERIALIZABLE 
    F111-01 READ UNCOMMITTED isolation level 
    F111-02 READ COMMITTED isolation level 
    F111-03 REPEATABLE READ isolation level 
    F131CoreGrouped operations 
    F131-01CoreWHERE, GROUP BY, and HAVING clauses supported in queries with grouped views 
    F131-02CoreMultiple tables supported in queries with grouped views 
    F131-03CoreSet functions supported in queries with grouped views 
    F131-04CoreSubqueries with GROUP BY and HAVING clauses and grouped views 
    F131-05CoreSingle row SELECT with GROUP BY and HAVING clauses and grouped views 
    F171 Multiple schemas per user 
    F181CoreMultiple module support 
    F191 Referential delete actions 
    F200 TRUNCATE TABLE statement 
    F201CoreCAST function 
    F202 TRUNCATE TABLE: identity column restart option 
    F221CoreExplicit defaults 
    F222 INSERT statement: DEFAULT VALUES clause 
    F231 Privilege tables 
    F231-01 TABLE_PRIVILEGES view 
    F231-02 COLUMN_PRIVILEGES view 
    F231-03 USAGE_PRIVILEGES view 
    F251 Domain support 
    F261CoreCASE expression 
    F261-01CoreSimple CASE 
    F261-02CoreSearched CASE 
    F261-03CoreNULLIF 
    F261-04CoreCOALESCE 
    F262 Extended CASE expression 
    F271 Compound character literals 
    F281 LIKE enhancements 
    F302 INTERSECT table operator 
    F302-01 INTERSECT DISTINCT table operator 
    F302-02 INTERSECT ALL table operator 
    F304 EXCEPT ALL table operator 
    F311CoreSchema definition statement 
    F311-01CoreCREATE SCHEMA 
    F311-02CoreCREATE TABLE for persistent base tables 
    F311-03CoreCREATE VIEW 
    F311-04CoreCREATE VIEW: WITH CHECK OPTION 
    F311-05CoreGRANT statement 
    F321 User authorization 
    F361 Subprogram support 
    F381 Extended schema manipulation 
    F381-01 ALTER TABLE statement: ALTER COLUMN clause 
    F381-02 ALTER TABLE statement: ADD CONSTRAINT clause 
    F381-03 ALTER TABLE statement: DROP CONSTRAINT clause 
    F382 Alter column data type 
    F383 Set column not null clause 
    F384 Drop identity property clause 
    F385 Drop column generation expression clause 
    F386 Set identity column generation clause 
    F391 Long identifiers 
    F392 Unicode escapes in identifiers 
    F393 Unicode escapes in literals 
    F394 Optional normal form specification 
    F401 Extended joined table 
    F401-01 NATURAL JOIN 
    F401-02 FULL OUTER JOIN 
    F401-04 CROSS JOIN 
    F402 Named column joins for LOBs, arrays, and multisets 
    F411 Time zone specificationdifferences regarding literal interpretation
    F421 National character 
    F431 Read-only scrollable cursors 
    F431-01 FETCH with explicit NEXT 
    F431-02 FETCH FIRST 
    F431-03 FETCH LAST 
    F431-04 FETCH PRIOR 
    F431-05 FETCH ABSOLUTE 
    F431-06 FETCH RELATIVE 
    F441 Extended set function support 
    F442 Mixed column references in set functions 
    F471CoreScalar subquery values 
    F481CoreExpanded NULL predicate 
    F491 Constraint management 
    F501CoreFeatures and conformance views 
    F501-01CoreSQL_FEATURES view 
    F501-02CoreSQL_SIZING view 
    F502 Enhanced documentation tables 
    F531 Temporary tables 
    F555 Enhanced seconds precision 
    F561 Full value expressions 
    F571 Truth value tests 
    F591 Derived tables 
    F611 Indicator data types 
    F641 Row and table constructors 
    F651 Catalog name qualifiers 
    F661 Simple tables 
    F672 Retrospective check constraints 
    F690 Collation supportbut no character set support
    F692 Extended collation support 
    F701 Referential update actions 
    F711 ALTER domain 
    F731 INSERT column privileges 
    F751 View CHECK enhancements 
    F761 Session management 
    F762 CURRENT_CATALOG 
    F763 CURRENT_SCHEMA 
    F771 Connection management 
    F781 Self-referencing operations 
    F791 Insensitive cursors 
    F801 Full set function 
    F850 Top-level <order by clause> in <query expression> 
    F851 <order by clause> in subqueries 
    F852 Top-level <order by clause> in views 
    F855 Nested <order by clause> in <query expression> 
    F856 Nested <fetch first clause> in <query expression> 
    F857 Top-level <fetch first clause> in <query expression> 
    F858 <fetch first clause> in subqueries 
    F859 Top-level <fetch first clause> in views 
    F860 <fetch first row count> in <fetch first clause> 
    F861 Top-level <result offset clause> in <query expression> 
    F862 <result offset clause> in subqueries 
    F863 Nested <result offset clause> in <query expression> 
    F864 Top-level <result offset clause> in views 
    F865 <offset row count> in <result offset clause> 
    F867 FETCH FIRST clause: WITH TIES option 
    S071 SQL paths in function and type name resolution 
    S092 Arrays of user-defined types 
    S095 Array constructors by query 
    S096 Optional array bounds 
    S098 ARRAY_AGG 
    S111 ONLY in query expressions 
    S201 SQL-invoked routines on arrays 
    S201-01 Array parameters 
    S201-02 Array as result type of functions 
    S211 User-defined cast functions 
    S301 Enhanced UNNEST 
    T031 BOOLEAN data type 
    T071 BIGINT data type 
    T121 WITH (excluding RECURSIVE) in query expression 
    T122 WITH (excluding RECURSIVE) in subquery 
    T131 Recursive query 
    T132 Recursive query in subquery 
    T141 SIMILAR predicate 
    T151 DISTINCT predicate 
    T152 DISTINCT predicate with negation 
    T171 LIKE clause in table definition 
    T172 AS subquery clause in table definition 
    T173 Extended LIKE clause in table definition 
    T174 Identity columns 
    T177 Sequence generator support: simple restart option 
    T178 Identity columns: simple restart option 
    T191 Referential action RESTRICT 
    T201 Comparable data types for referential constraints 
    T211-01 Triggers activated on UPDATE, INSERT, or DELETE of one base table 
    T211-02 BEFORE triggers 
    T211-03 AFTER triggers 
    T211-04 FOR EACH ROW triggers 
    T211-05 Ability to specify a search condition that must be true before the trigger is invoked 
    T211-07 TRIGGER privilege 
    T212 Enhanced trigger capability 
    T213 INSTEAD OF triggers 
    T231 Sensitive cursors 
    T241 START TRANSACTION statement 
    T261 Chained transactions 
    T271 Savepoints 
    T281 SELECT privilege with column granularity 
    T285 Enhanced derived column names 
    T312 OVERLAY function 
    T321-01CoreUser-defined functions with no overloading 
    T321-02CoreUser-defined stored procedures with no overloading 
    T321-03CoreFunction invocation 
    T321-04CoreCALL statement 
    T321-06CoreROUTINES view 
    T321-07CorePARAMETERS view 
    T323 Explicit security for external routines 
    T325 Qualified SQL parameter references 
    T331 Basic roles 
    T341 Overloading of SQL-invoked functions and procedures 
    T351 Bracketed SQL comments (/*...*/ comments) 
    T431 Extended grouping capabilities 
    T432 Nested and concatenated GROUPING SETS 
    T433 Multiargument GROUPING function 
    T441 ABS and MOD functions 
    T461 Symmetric BETWEEN predicate 
    T491 LATERAL derived table 
    T501 Enhanced EXISTS predicate 
    T521 Named arguments in CALL statement 
    T523 Default values for INOUT parameters of SQL-invoked procedures 
    T524 Named arguments in routine invocations other than a CALL statement 
    T525 Default values for parameters of SQL-invoked functions 
    T551 Optional key words for default syntax 
    T581 Regular expression substring function 
    T591 UNIQUE constraints of possibly null columns 
    T611 Elementary OLAP operations 
    T612 Advanced OLAP operations 
    T613 Sampling 
    T614 NTILE function 
    T615 LEAD and LAG functions 
    T617 FIRST_VALUE and LAST_VALUE function 
    T620 WINDOW clause: GROUPS option 
    T621 Enhanced numeric functions 
    T622 Trigonometric functions 
    T623 General logarithm functions 
    T624 Common logarithm functions 
    T631CoreIN predicate with one list element 
    T651 SQL-schema statements in SQL routines 
    T653 SQL-schema statements in external routines 
    T655 Cyclically dependent routines 
    T831 SQL/JSON path language: strict mode 
    T832 SQL/JSON path language: item method 
    T833 SQL/JSON path language: multiple subscripts 
    T834 SQL/JSON path language: wildcard member accessor 
    T835 SQL/JSON path language: filter expressions 
    T836 SQL/JSON path language: starts with predicate 
    T837 SQL/JSON path language: regex_like predicate 
    X010 XML type 
    X011 Arrays of XML type 
    X014 Attributes of XML type 
    X016 Persistent XML values 
    X020 XMLConcat 
    X031 XMLElement 
    X032 XMLForest 
    X034 XMLAgg 
    X035 XMLAgg: ORDER BY option 
    X036 XMLComment 
    X037 XMLPI 
    X040 Basic table mapping 
    X041 Basic table mapping: nulls absent 
    X042 Basic table mapping: null as nil 
    X043 Basic table mapping: table as forest 
    X044 Basic table mapping: table as element 
    X045 Basic table mapping: with target namespace 
    X046 Basic table mapping: data mapping 
    X047 Basic table mapping: metadata mapping 
    X048 Basic table mapping: base64 encoding of binary strings 
    X049 Basic table mapping: hex encoding of binary strings 
    X050 Advanced table mapping 
    X051 Advanced table mapping: nulls absent 
    X052 Advanced table mapping: null as nil 
    X053 Advanced table mapping: table as forest 
    X054 Advanced table mapping: table as element 
    X055 Advanced table mapping: with target namespace 
    X056 Advanced table mapping: data mapping 
    X057 Advanced table mapping: metadata mapping 
    X058 Advanced table mapping: base64 encoding of binary strings 
    X059 Advanced table mapping: hex encoding of binary strings 
    X060 XMLParse: character string input and CONTENT option 
    X061 XMLParse: character string input and DOCUMENT option 
    X070 XMLSerialize: character string serialization and CONTENT option 
    X071 XMLSerialize: character string serialization and DOCUMENT option 
    X072 XMLSerialize: character string serialization 
    X090 XML document predicate 
    X120 XML parameters in SQL routines 
    X121 XML parameters in external routines 
    X221 XML passing mechanism BY VALUE 
    X301 XMLTable: derived column list option 
    X302 XMLTable: ordinality column option 
    X303 XMLTable: column default option 
    X304 XMLTable: passing a context itemmust be XML DOCUMENT
    X400 Name and identifier mapping 
    X410 Alter column data type: XML type 

    -

    Prev Up Next
    Appendix D. SQL Conformance Home D.2. Unsupported Features
    \ No newline at end of file +

    Prev Up Next
    Appendix D. SQL Conformance Home D.2. Unsupported Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/features.html postgresql-13-13.12/doc/src/sgml/html/features.html --- postgresql-13-13.11/doc/src/sgml/html/features.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/features.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix D. SQL Conformance
    Appendix D. SQL Conformance
    Prev UpPart VIII. AppendixesHome Next

    Appendix D. SQL Conformance

    Table of Contents

    D.1. Supported Features
    D.2. Unsupported Features
    D.3. XML Limits and Conformance to SQL/XML
    D.3.1. Queries Are Restricted to XPath 1.0
    D.3.2. Incidental Limits of the Implementation

    +Appendix D. SQL Conformance

    Appendix D. SQL Conformance
    Prev UpPart VIII. AppendixesHome Next

    Appendix D. SQL Conformance

    Table of Contents

    D.1. Supported Features
    D.2. Unsupported Features
    D.3. XML Limits and Conformance to SQL/XML
    D.3.1. Queries Are Restricted to XPath 1.0
    D.3.2. Incidental Limits of the Implementation

    This section attempts to outline to what extent PostgreSQL conforms to the current SQL standard. The following information is not a full statement of @@ -70,4 +70,4 @@ Feature codes containing a hyphen are subfeatures. Therefore, if a particular subfeature is not supported, the main feature is listed as unsupported even if some other subfeatures are supported. -

    Prev Up Next
    Appendix C. SQL Key Words Home D.1. Supported Features
    \ No newline at end of file +

    Prev Up Next
    Appendix C. SQL Key Words Home D.1. Supported Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/file-fdw.html postgresql-13-13.12/doc/src/sgml/html/file-fdw.html --- postgresql-13-13.11/doc/src/sgml/html/file-fdw.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/file-fdw.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.14. file_fdw
    F.14. file_fdw
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.14. file_fdw

    +F.14. file_fdw

    F.14. file_fdw
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.14. file_fdw

    The file_fdw module provides the foreign-data wrapper file_fdw, which can be used to access data files in the server's file system, or to execute programs on the server @@ -140,4 +140,4 @@

    That's it — now you can query your log directly. In production, of course, you would need to define some way to deal with log rotation. -


    Prev Up Next
    F.13. earthdistance Home F.15. fuzzystrmatch
    \ No newline at end of file +


    Prev Up Next
    F.13. earthdistance Home F.15. fuzzystrmatch
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-admin.html postgresql-13-13.12/doc/src/sgml/html/functions-admin.html --- postgresql-13-13.11/doc/src/sgml/html/functions-admin.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-admin.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -9.27. System Administration Functions
    9.27. System Administration Functions
    Prev UpChapter 9. Functions and OperatorsHome Next
    Prev Up Next
    9.26. System Information Functions and Operators Home 9.28. Trigger Functions
    \ No newline at end of file +


    Prev Up Next
    9.26. System Information Functions and Operators Home 9.28. Trigger Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-aggregate.html postgresql-13-13.12/doc/src/sgml/html/functions-aggregate.html --- postgresql-13-13.11/doc/src/sgml/html/functions-aggregate.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-aggregate.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.21. Aggregate Functions
    9.21. Aggregate Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.21. Aggregate Functions

    +9.21. Aggregate Functions

    9.21. Aggregate Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.21. Aggregate Functions

    Aggregate functions compute a single result from a set of input values. The built-in general-purpose aggregate functions are listed in Table 9.55 @@ -680,4 +680,4 @@ neither make nor model was grouped by in the last row (which therefore is an aggregate over all the input rows). -

    Prev Up Next
    9.20. Range Functions and Operators Home 9.22. Window Functions
    \ No newline at end of file +

    Prev Up Next
    9.20. Range Functions and Operators Home 9.22. Window Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-array.html postgresql-13-13.12/doc/src/sgml/html/functions-array.html --- postgresql-13-13.11/doc/src/sgml/html/functions-array.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-array.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.19. Array Functions and Operators
    9.19. Array Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.19. Array Functions and Operators

    +9.19. Array Functions and Operators

    9.19. Array Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.19. Array Functions and Operators

    Table 9.51 shows the specialized operators available for array types. In addition to those, the usual comparison operators shown in Table 9.1 are available for @@ -399,4 +399,4 @@

    See also Section 9.21 about the aggregate function array_agg for use with arrays. -

    Prev Up Next
    9.18. Conditional Expressions Home 9.20. Range Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.18. Conditional Expressions Home 9.20. Range Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-binarystring.html postgresql-13-13.12/doc/src/sgml/html/functions-binarystring.html --- postgresql-13-13.11/doc/src/sgml/html/functions-binarystring.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-binarystring.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.5. Binary String Functions and Operators
    9.5. Binary String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.5. Binary String Functions and Operators

    +9.5. Binary String Functions and Operators

    9.5. Binary String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.5. Binary String Functions and Operators

    This section describes functions and operators for examining and manipulating binary strings, that is values of type bytea. Many of these are equivalent, in purpose and syntax, to the @@ -465,4 +465,4 @@ See also the aggregate function string_agg in Section 9.21 and the large object functions in Section 34.4. -

    Prev Up Next
    9.4. String Functions and Operators Home 9.6. Bit String Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.4. String Functions and Operators Home 9.6. Bit String Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-bitstring.html postgresql-13-13.12/doc/src/sgml/html/functions-bitstring.html --- postgresql-13-13.11/doc/src/sgml/html/functions-bitstring.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-bitstring.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.6. Bit String Functions and Operators
    9.6. Bit String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.6. Bit String Functions and Operators

    +9.6. Bit String Functions and Operators

    9.6. Bit String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.6. Bit String Functions and Operators

    This section describes functions and operators for examining and manipulating bit strings, that is values of the types bit and bit varying. (While only @@ -220,4 +220,4 @@ Note that casting to just “bit” means casting to bit(1), and so will deliver only the least significant bit of the integer. -

    Prev Up Next
    9.5. Binary String Functions and Operators Home 9.7. Pattern Matching
    \ No newline at end of file +

    Prev Up Next
    9.5. Binary String Functions and Operators Home 9.7. Pattern Matching
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-comparison.html postgresql-13-13.12/doc/src/sgml/html/functions-comparison.html --- postgresql-13-13.11/doc/src/sgml/html/functions-comparison.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-comparison.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.2. Comparison Functions and Operators
    9.2. Comparison Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.2. Comparison Functions and Operators

    +9.2. Comparison Functions and Operators

    9.2. Comparison Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.2. Comparison Functions and Operators

    The usual comparison operators are available, as shown in Table 9.1.

    Table 9.1. Comparison Operators

    OperatorDescription
    datatype < datatype @@ -397,4 +397,4 @@

    num_nulls(1, NULL, 2) → 1 -


    Prev Up Next
    9.1. Logical Operators Home 9.3. Mathematical Functions and Operators
    \ No newline at end of file +


    Prev Up Next
    9.1. Logical Operators Home 9.3. Mathematical Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-comparisons.html postgresql-13-13.12/doc/src/sgml/html/functions-comparisons.html --- postgresql-13-13.11/doc/src/sgml/html/functions-comparisons.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-comparisons.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.24. Row and Array Comparisons
    9.24. Row and Array Comparisons
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.24. Row and Array Comparisons

    9.24.1. IN
    9.24.2. NOT IN
    9.24.3. ANY/SOME (array)
    9.24.4. ALL (array)
    9.24.5. Row Constructor Comparison
    9.24.6. Composite Type Comparison

    +9.24. Row and Array Comparisons

    9.24. Row and Array Comparisons
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.24. Row and Array Comparisons

    9.24.1. IN
    9.24.2. NOT IN
    9.24.3. ANY/SOME (array)
    9.24.4. ALL (array)
    9.24.5. Row Constructor Comparison
    9.24.6. Composite Type Comparison

    This section describes several specialized constructs for making multiple comparisons between groups of values. These forms are syntactically related to the subquery forms of the previous section, @@ -13,7 +13,7 @@ expression IN (value [, ...])

    The right-hand side is a parenthesized list - of scalar expressions. The result is “true” if the left-hand expression's + of expressions. The result is “true” if the left-hand expression's result is equal to any of the right-hand expressions. This is a shorthand notation for @@ -34,7 +34,7 @@ expression NOT IN (value [, ...])

    The right-hand side is a parenthesized list - of scalar expressions. The result is “true” if the left-hand expression's + of expressions. The result is “true” if the left-hand expression's result is unequal to all of the right-hand expressions. This is a shorthand notation for @@ -109,21 +109,23 @@

    Each side is a row constructor, as described in Section 4.2.13. - The two row values must have the same number of fields. - Each side is evaluated and they are compared row-wise. Row constructor - comparisons are allowed when the operator is + The two row constructors must have the same number of fields. + The given operator is applied to each pair + of corresponding fields. (Since the fields could be of different + types, this means that a different specific operator could be selected + for each pair.) + All the selected operators must be members of some B-tree operator + class, or be the negator of an = member of a B-tree + operator class, meaning that row constructor comparison is only + possible when the operator is =, <>, <, <=, - > or - >=. - Every row element must be of a type which has a default B-tree operator - class or the attempted comparison may generate an error. -

    Note

    - Errors related to the number or types of elements might not occur if - the comparison is resolved using earlier columns. -

    + >, or + >=, + or has semantics similar to one of these. +

    The = and <> cases work slightly differently from the others. Two rows are considered equal if all their corresponding members are non-null and equal; the rows @@ -210,4 +212,4 @@ for materialized views and might be useful for other specialized purposes such as replication and B-Tree deduplication (see Section 63.4.2). They are not intended to be generally useful for writing queries, though. -

    Prev Up Next
    9.23. Subquery Expressions Home 9.25. Set Returning Functions
    \ No newline at end of file +

    Prev Up Next
    9.23. Subquery Expressions Home 9.25. Set Returning Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-conditional.html postgresql-13-13.12/doc/src/sgml/html/functions-conditional.html --- postgresql-13-13.11/doc/src/sgml/html/functions-conditional.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-conditional.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.18. Conditional Expressions
    9.18. Conditional Expressions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.18. Conditional Expressions

    9.18.1. CASE
    9.18.2. COALESCE
    9.18.3. NULLIF
    9.18.4. GREATEST and LEAST

    +9.18. Conditional Expressions

    9.18. Conditional Expressions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.18. Conditional Expressions

    9.18.1. CASE
    9.18.2. COALESCE
    9.18.3. NULLIF
    9.18.4. GREATEST and LEAST

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

    Tip

    @@ -184,4 +184,4 @@ the SQL standard, but are a common extension. Some other databases make them return NULL if any argument is NULL, rather than only when all are NULL. -

    Prev Up Next
    9.17. Sequence Manipulation Functions Home 9.19. Array Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.17. Sequence Manipulation Functions Home 9.19. Array Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-datetime.html postgresql-13-13.12/doc/src/sgml/html/functions-datetime.html --- postgresql-13-13.11/doc/src/sgml/html/functions-datetime.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-datetime.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.9. Date/Time Functions and Operators
    9.9. Date/Time Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.9. Date/Time Functions and Operators

    9.9.1. EXTRACT, date_part
    9.9.2. date_trunc
    9.9.3. AT TIME ZONE
    9.9.4. Current Date/Time
    9.9.5. Delaying Execution

    +9.9. Date/Time Functions and Operators

    9.9. Date/Time Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.9. Date/Time Functions and Operators

    9.9.1. EXTRACT, date_part
    9.9.2. date_trunc
    9.9.3. AT TIME ZONE
    9.9.4. Current Date/Time
    9.9.5. Delaying Execution

    Table 9.32 shows the available functions for date/time value processing, with details appearing in the following subsections. Table 9.31 illustrates the behaviors of @@ -1259,4 +1259,4 @@ when calling pg_sleep or its variants. Otherwise other sessions might have to wait for your sleeping process, slowing down the entire system. -

    Prev Up Next
    9.8. Data Type Formatting Functions Home 9.10. Enum Support Functions
    \ No newline at end of file +

    Prev Up Next
    9.8. Data Type Formatting Functions Home 9.10. Enum Support Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-enum.html postgresql-13-13.12/doc/src/sgml/html/functions-enum.html --- postgresql-13-13.11/doc/src/sgml/html/functions-enum.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-enum.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.10. Enum Support Functions
    9.10. Enum Support Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.10. Enum Support Functions

    +9.10. Enum Support Functions

    9.10. Enum Support Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.10. Enum Support Functions

    For enum types (described in Section 8.7), there are several functions that allow cleaner programming without hard-coding particular values of an enum type. @@ -81,4 +81,4 @@ the type can be passed, with the same result. It is more common to apply these functions to a table column or function argument than to a hardwired type name as used in the examples. -

    Prev Up Next
    9.9. Date/Time Functions and Operators Home 9.11. Geometric Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.9. Date/Time Functions and Operators Home 9.11. Geometric Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-event-triggers.html postgresql-13-13.12/doc/src/sgml/html/functions-event-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/functions-event-triggers.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-event-triggers.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -9.29. Event Trigger Functions
    9.29. Event Trigger Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.29. Event Trigger Functions

    9.29.1. Capturing Changes at Command End
    9.29.2. Processing Objects Dropped by a DDL Command
    9.29.3. Handling a Table Rewrite Event

    +9.29. Event Trigger Functions

    9.29. Event Trigger Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.29. Event Trigger Functions

    9.29.1. Capturing Changes at Command End
    9.29.2. Processing Objects Dropped by a DDL Command
    9.29.3. Handling a Table Rewrite Event

    PostgreSQL provides these helper functions to retrieve information from event triggers.

    @@ -130,4 +130,4 @@ ON table_rewrite EXECUTE FUNCTION test_event_trigger_table_rewrite_oid();

    -

    Prev Up Next
    9.28. Trigger Functions Home 9.30. Statistics Information Functions
    \ No newline at end of file +

    Prev Up Next
    9.28. Trigger Functions Home 9.30. Statistics Information Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-formatting.html postgresql-13-13.12/doc/src/sgml/html/functions-formatting.html --- postgresql-13-13.11/doc/src/sgml/html/functions-formatting.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-formatting.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.8. Data Type Formatting Functions
    9.8. Data Type Formatting Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.8. Data Type Formatting Functions

    +9.8. Data Type Formatting Functions

    9.8. Data Type Formatting Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.8. Data Type Formatting Functions

    The PostgreSQL formatting functions provide a powerful set of tools for converting various data types (date/time, integer, floating point, numeric) to formatted strings @@ -403,4 +403,4 @@

    Table 9.29. Template Pattern Modifiers for Numeric Formatting

    ModifierDescriptionExample
    FM prefixfill mode (suppress trailing zeroes and padding blanks)FM99.99
    TH suffixupper case ordinal number suffix999TH
    th suffixlower case ordinal number suffix999th

    Table 9.30 shows some examples of the use of the to_char function. -

    Table 9.30. to_char Examples

    ExpressionResult
    to_char(current_timestamp, 'Day, DD  HH12:MI:SS')'Tuesday  , 06  05:39:18'
    to_char(current_timestamp, 'FMDay, FMDD  HH12:MI:SS')'Tuesday, 6  05:39:18'
    to_char(-0.1, '99.99')'  -.10'
    to_char(-0.1, 'FM9.99')'-.1'
    to_char(-0.1, 'FM90.99')'-0.1'
    to_char(0.1, '0.9')' 0.1'
    to_char(12, '9990999.9')'    0012.0'
    to_char(12, 'FM9990999.9')'0012.'
    to_char(485, '999')' 485'
    to_char(-485, '999')'-485'
    to_char(485, '9 9 9')' 4 8 5'
    to_char(1485, '9,999')' 1,485'
    to_char(1485, '9G999')' 1 485'
    to_char(148.5, '999.999')' 148.500'
    to_char(148.5, 'FM999.999')'148.5'
    to_char(148.5, 'FM999.990')'148.500'
    to_char(148.5, '999D999')' 148,500'
    to_char(3148.5, '9G999D999')' 3 148,500'
    to_char(-485, '999S')'485-'
    to_char(-485, '999MI')'485-'
    to_char(485, '999MI')'485 '
    to_char(485, 'FM999MI')'485'
    to_char(485, 'PL999')'+485'
    to_char(485, 'SG999')'+485'
    to_char(-485, 'SG999')'-485'
    to_char(-485, '9SG99')'4-85'
    to_char(-485, '999PR')'<485>'
    to_char(485, 'L999')'DM 485'
    to_char(485, 'RN')'        CDLXXXV'
    to_char(485, 'FMRN')'CDLXXXV'
    to_char(5.2, 'FMRN')'V'
    to_char(482, '999th')' 482nd'
    to_char(485, '"Good number:"999')'Good number: 485'
    to_char(485.8, '"Pre:"999" Post:" .999')'Pre: 485 Post: .800'
    to_char(12, '99V999')' 12000'
    to_char(12.4, '99V999')' 12400'
    to_char(12.45, '99V9')' 125'
    to_char(0.0004859, '9.99EEEE')' 4.86e-04'

    Prev Up Next
    9.7. Pattern Matching Home 9.9. Date/Time Functions and Operators
    \ No newline at end of file +

    Table 9.30. to_char Examples

    ExpressionResult
    to_char(current_timestamp, 'Day, DD  HH12:MI:SS')'Tuesday  , 06  05:39:18'
    to_char(current_timestamp, 'FMDay, FMDD  HH12:MI:SS')'Tuesday, 6  05:39:18'
    to_char(-0.1, '99.99')'  -.10'
    to_char(-0.1, 'FM9.99')'-.1'
    to_char(-0.1, 'FM90.99')'-0.1'
    to_char(0.1, '0.9')' 0.1'
    to_char(12, '9990999.9')'    0012.0'
    to_char(12, 'FM9990999.9')'0012.'
    to_char(485, '999')' 485'
    to_char(-485, '999')'-485'
    to_char(485, '9 9 9')' 4 8 5'
    to_char(1485, '9,999')' 1,485'
    to_char(1485, '9G999')' 1 485'
    to_char(148.5, '999.999')' 148.500'
    to_char(148.5, 'FM999.999')'148.5'
    to_char(148.5, 'FM999.990')'148.500'
    to_char(148.5, '999D999')' 148,500'
    to_char(3148.5, '9G999D999')' 3 148,500'
    to_char(-485, '999S')'485-'
    to_char(-485, '999MI')'485-'
    to_char(485, '999MI')'485 '
    to_char(485, 'FM999MI')'485'
    to_char(485, 'PL999')'+485'
    to_char(485, 'SG999')'+485'
    to_char(-485, 'SG999')'-485'
    to_char(-485, '9SG99')'4-85'
    to_char(-485, '999PR')'<485>'
    to_char(485, 'L999')'DM 485'
    to_char(485, 'RN')'        CDLXXXV'
    to_char(485, 'FMRN')'CDLXXXV'
    to_char(5.2, 'FMRN')'V'
    to_char(482, '999th')' 482nd'
    to_char(485, '"Good number:"999')'Good number: 485'
    to_char(485.8, '"Pre:"999" Post:" .999')'Pre: 485 Post: .800'
    to_char(12, '99V999')' 12000'
    to_char(12.4, '99V999')' 12400'
    to_char(12.45, '99V9')' 125'
    to_char(0.0004859, '9.99EEEE')' 4.86e-04'

    Prev Up Next
    9.7. Pattern Matching Home 9.9. Date/Time Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-geometry.html postgresql-13-13.12/doc/src/sgml/html/functions-geometry.html --- postgresql-13-13.11/doc/src/sgml/html/functions-geometry.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-geometry.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.11. Geometric Functions and Operators
    9.11. Geometric Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.11. Geometric Functions and Operators

    +9.11. Geometric Functions and Operators

    9.11. Geometric Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.11. Geometric Functions and Operators

    The geometric types point, box, lseg, line, path, polygon, and circle have a large set of @@ -903,4 +903,4 @@ UPDATE t SET p[1] = ... changes the Y coordinate. In the same way, a value of type box or lseg can be treated as an array of two point values. -

    Prev Up Next
    9.10. Enum Support Functions Home 9.12. Network Address Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.10. Enum Support Functions Home 9.12. Network Address Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-info.html postgresql-13-13.12/doc/src/sgml/html/functions-info.html --- postgresql-13-13.11/doc/src/sgml/html/functions-info.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-info.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.26. System Information Functions and Operators
    9.26. System Information Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.26. System Information Functions and Operators

    +9.26. System Information Functions and Operators

    9.26. System Information Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.26. System Information Functions and Operators

    Table 9.63 shows several functions that extract session and system information.

    @@ -1669,4 +1669,4 @@

    Returns information about recovery state, as shown in Table 9.82. -


    Table 9.79. pg_control_checkpoint Output Columns

    Column NameData Type
    checkpoint_lsnpg_lsn
    redo_lsnpg_lsn
    redo_wal_filetext
    timeline_idinteger
    prev_timeline_idinteger
    full_page_writesboolean
    next_xidtext
    next_oidoid
    next_multixact_idxid
    next_multi_offsetxid
    oldest_xidxid
    oldest_xid_dbidoid
    oldest_active_xidxid
    oldest_multi_xidxid
    oldest_multi_dbidoid
    oldest_commit_ts_xidxid
    newest_commit_ts_xidxid
    checkpoint_timetimestamp with time zone

    Table 9.80. pg_control_system Output Columns

    Column NameData Type
    pg_control_versioninteger
    catalog_version_nointeger
    system_identifierbigint
    pg_control_last_modifiedtimestamp with time zone

    Table 9.81. pg_control_init Output Columns

    Column NameData Type
    max_data_alignmentinteger
    database_block_sizeinteger
    blocks_per_segmentinteger
    wal_block_sizeinteger
    bytes_per_wal_segmentinteger
    max_identifier_lengthinteger
    max_index_columnsinteger
    max_toast_chunk_sizeinteger
    large_object_chunk_sizeinteger
    float8_pass_by_valueboolean
    data_page_checksum_versioninteger

    Table 9.82. pg_control_recovery Output Columns

    Column NameData Type
    min_recovery_end_lsnpg_lsn
    min_recovery_end_timelineinteger
    backup_start_lsnpg_lsn
    backup_end_lsnpg_lsn
    end_of_backup_record_requiredboolean

    Prev Up Next
    9.25. Set Returning Functions Home 9.27. System Administration Functions
    \ No newline at end of file +


    Table 9.79. pg_control_checkpoint Output Columns

    Column NameData Type
    checkpoint_lsnpg_lsn
    redo_lsnpg_lsn
    redo_wal_filetext
    timeline_idinteger
    prev_timeline_idinteger
    full_page_writesboolean
    next_xidtext
    next_oidoid
    next_multixact_idxid
    next_multi_offsetxid
    oldest_xidxid
    oldest_xid_dbidoid
    oldest_active_xidxid
    oldest_multi_xidxid
    oldest_multi_dbidoid
    oldest_commit_ts_xidxid
    newest_commit_ts_xidxid
    checkpoint_timetimestamp with time zone

    Table 9.80. pg_control_system Output Columns

    Column NameData Type
    pg_control_versioninteger
    catalog_version_nointeger
    system_identifierbigint
    pg_control_last_modifiedtimestamp with time zone

    Table 9.81. pg_control_init Output Columns

    Column NameData Type
    max_data_alignmentinteger
    database_block_sizeinteger
    blocks_per_segmentinteger
    wal_block_sizeinteger
    bytes_per_wal_segmentinteger
    max_identifier_lengthinteger
    max_index_columnsinteger
    max_toast_chunk_sizeinteger
    large_object_chunk_sizeinteger
    float8_pass_by_valueboolean
    data_page_checksum_versioninteger

    Table 9.82. pg_control_recovery Output Columns

    Column NameData Type
    min_recovery_end_lsnpg_lsn
    min_recovery_end_timelineinteger
    backup_start_lsnpg_lsn
    backup_end_lsnpg_lsn
    end_of_backup_record_requiredboolean

    Prev Up Next
    9.25. Set Returning Functions Home 9.27. System Administration Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-json.html postgresql-13-13.12/doc/src/sgml/html/functions-json.html --- postgresql-13-13.11/doc/src/sgml/html/functions-json.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-json.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.16. JSON Functions and Operators
    9.16. JSON Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.16. JSON Functions and Operators

    9.16.1. Processing and Creating JSON Data
    9.16.2. The SQL/JSON Path Language

    +9.16. JSON Functions and Operators

    9.16. JSON Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.16. JSON Functions and Operators

    9.16.1. Processing and Creating JSON Data
    9.16.2. The SQL/JSON Path Language

    This section describes:

    • @@ -1778,4 +1778,4 @@ 

       $.* ? (@ like_regex "^\\d+$")

      -

    Prev Up Next
    9.15. XML Functions Home 9.17. Sequence Manipulation Functions
    \ No newline at end of file +

    Prev Up Next
    9.15. XML Functions Home 9.17. Sequence Manipulation Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-logical.html postgresql-13-13.12/doc/src/sgml/html/functions-logical.html --- postgresql-13-13.11/doc/src/sgml/html/functions-logical.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-logical.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.1. Logical Operators
    9.1. Logical Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.1. Logical Operators

    +9.1. Logical Operators

    9.1. Logical Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.1. Logical Operators

    The usual logical operators are available: @@ -33,4 +33,4 @@ without affecting the result. (However, it is not guaranteed that the left operand is evaluated before the right operand. See Section 4.2.14 for more information about the order of evaluation of subexpressions.) -

    Prev Up Next
    Chapter 9. Functions and Operators Home 9.2. Comparison Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    Chapter 9. Functions and Operators Home 9.2. Comparison Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-matching.html postgresql-13-13.12/doc/src/sgml/html/functions-matching.html --- postgresql-13-13.11/doc/src/sgml/html/functions-matching.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-matching.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.7. Pattern Matching
    9.7. Pattern Matching
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.7. Pattern Matching

    9.7.1. LIKE
    9.7.2. SIMILAR TO Regular Expressions
    9.7.3. POSIX Regular Expressions

    +9.7. Pattern Matching

    9.7. Pattern Matching
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.7. Pattern Matching

    9.7.1. LIKE
    9.7.2. SIMILAR TO Regular Expressions
    9.7.3. POSIX Regular Expressions

    There are three separate approaches to pattern matching provided by PostgreSQL: the traditional SQL LIKE operator, the @@ -1245,4 +1245,4 @@ backslash.

    -

    Prev Up Next
    9.6. Bit String Functions and Operators Home 9.8. Data Type Formatting Functions
    \ No newline at end of file +

    Prev Up Next
    9.6. Bit String Functions and Operators Home 9.8. Data Type Formatting Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-math.html postgresql-13-13.12/doc/src/sgml/html/functions-math.html --- postgresql-13-13.11/doc/src/sgml/html/functions-math.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-math.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.3. Mathematical Functions and Operators
    9.3. Mathematical Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.3. Mathematical Functions and Operators

    +9.3. Mathematical Functions and Operators

    9.3. Mathematical Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.3. Mathematical Functions and Operators

    Mathematical operators are provided for many PostgreSQL types. For types without standard mathematical conventions @@ -1019,4 +1019,4 @@

    atanh(0.5) → 0.5493061443340548 -


    Prev Up Next
    9.2. Comparison Functions and Operators Home 9.4. String Functions and Operators
    \ No newline at end of file +


    Prev Up Next
    9.2. Comparison Functions and Operators Home 9.4. String Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-net.html postgresql-13-13.12/doc/src/sgml/html/functions-net.html --- postgresql-13-13.11/doc/src/sgml/html/functions-net.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-net.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.12. Network Address Functions and Operators
    9.12. Network Address Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.12. Network Address Functions and Operators

    +9.12. Network Address Functions and Operators

    9.12. Network Address Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.12. Network Address Functions and Operators

    The IP network address types, cidr and inet, support the usual comparison operators shown in Table 9.1 @@ -394,4 +394,4 @@

    macaddr8_set7bit(macaddr8 '00:34:56:ab:cd:ef') → 02:34:56:ff:fe:ab:cd:ef -


    Prev Up Next
    9.11. Geometric Functions and Operators Home 9.13. Text Search Functions and Operators
    \ No newline at end of file +


    Prev Up Next
    9.11. Geometric Functions and Operators Home 9.13. Text Search Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-range.html postgresql-13-13.12/doc/src/sgml/html/functions-range.html --- postgresql-13-13.11/doc/src/sgml/html/functions-range.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-range.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.20. Range Functions and Operators
    9.20. Range Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.20. Range Functions and Operators

    +9.20. Range Functions and Operators

    9.20. Range Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.20. Range Functions and Operators

    See Section 8.17 for an overview of range types.

    Table 9.53 shows the specialized operators @@ -261,4 +261,4 @@ The lower_inc, upper_inc, lower_inf, and upper_inf functions all return false for an empty range. -

    Prev Up Next
    9.19. Array Functions and Operators Home 9.21. Aggregate Functions
    \ No newline at end of file +

    Prev Up Next
    9.19. Array Functions and Operators Home 9.21. Aggregate Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-sequence.html postgresql-13-13.12/doc/src/sgml/html/functions-sequence.html --- postgresql-13-13.11/doc/src/sgml/html/functions-sequence.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-sequence.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.17. Sequence Manipulation Functions
    9.17. Sequence Manipulation Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.17. Sequence Manipulation Functions

    +9.17. Sequence Manipulation Functions

    9.17. Sequence Manipulation Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.17. Sequence Manipulation Functions

    This section describes functions for operating on sequence objects, also called sequence generators or just sequences. Sequence objects are special single-row tables created with CREATE SEQUENCE. @@ -180,4 +180,4 @@ Of course, the argument of a sequence function can be an expression as well as a constant. If it is a text expression then the implicit coercion will result in a run-time lookup. -

    Prev Up Next
    9.16. JSON Functions and Operators Home 9.18. Conditional Expressions
    \ No newline at end of file +

    Prev Up Next
    9.16. JSON Functions and Operators Home 9.18. Conditional Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-srf.html postgresql-13-13.12/doc/src/sgml/html/functions-srf.html --- postgresql-13-13.11/doc/src/sgml/html/functions-srf.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-srf.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.25. Set Returning Functions
    9.25. Set Returning Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.25. Set Returning Functions

    +9.25. Set Returning Functions

    9.25. Set Returning Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.25. Set Returning Functions

    This section describes functions that possibly return more than one row. The most widely used functions in this class are series generating functions, as detailed in Table 9.61 and @@ -215,4 +215,4 @@ pg_subtrans | 19 (19 rows)

    -

    Prev Up Next
    9.24. Row and Array Comparisons Home 9.26. System Information Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.24. Row and Array Comparisons Home 9.26. System Information Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-statistics.html postgresql-13-13.12/doc/src/sgml/html/functions-statistics.html --- postgresql-13-13.11/doc/src/sgml/html/functions-statistics.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-statistics.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -9.30. Statistics Information Functions
    9.30. Statistics Information Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.30. Statistics Information Functions

    9.30.1. Inspecting MCV Lists

    +9.30. Statistics Information Functions

    9.30. Statistics Information Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.30. Statistics Information Functions

    9.30.1. Inspecting MCV Lists

    PostgreSQL provides a function to inspect complex statistics defined using the CREATE STATISTICS command.

    9.30.1. Inspecting MCV Lists

    @@ -21,4 +21,4 @@
     Values of the pg_mcv_list type can be obtained only from the
     pg_statistic_ext_data.stxdmcv
     column.
-
    Prev Up Next
    9.29. Event Trigger Functions Home Chapter 10. Type Conversion
    \ No newline at end of file +

    Prev Up Next
    9.29. Event Trigger Functions Home Chapter 10. Type Conversion
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-string.html postgresql-13-13.12/doc/src/sgml/html/functions-string.html --- postgresql-13-13.11/doc/src/sgml/html/functions-string.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-string.html 2023-08-07 20:32:09.000000000 +0000 @@ -1,5 +1,5 @@ -9.4. String Functions and Operators
    9.4. String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.4. String Functions and Operators

    9.4.1. format

    +9.4. String Functions and Operators

    9.4. String Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.4. String Functions and Operators

    9.4.1. format

    This section describes functions and operators for examining and manipulating string values. Strings in this context include values of the types character, character varying, @@ -998,4 +998,4 @@ The %I and %L format specifiers are particularly useful for safely constructing dynamic SQL statements. See Example 42.1. -

    Prev Up Next
    9.3. Mathematical Functions and Operators Home 9.5. Binary String Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.3. Mathematical Functions and Operators Home 9.5. Binary String Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-subquery.html postgresql-13-13.12/doc/src/sgml/html/functions-subquery.html --- postgresql-13-13.11/doc/src/sgml/html/functions-subquery.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-subquery.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.23. Subquery Expressions
    9.23. Subquery Expressions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.23. Subquery Expressions

    9.23.1. EXISTS
    9.23.2. IN
    9.23.3. NOT IN
    9.23.4. ANY/SOME
    9.23.5. ALL
    9.23.6. Single-Row Comparison

    +9.23. Subquery Expressions

    9.23. Subquery Expressions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.23. Subquery Expressions

    9.23.1. EXISTS
    9.23.2. IN
    9.23.3. NOT IN
    9.23.4. ANY/SOME
    9.23.5. ALL
    9.23.6. Single-Row Comparison

    This section describes the SQL-compliant subquery expressions available in PostgreSQL. All of the expression forms documented in this section return @@ -210,4 +210,4 @@

    See Section 9.24.5 for details about the meaning of a row constructor comparison. -

    Prev Up Next
    9.22. Window Functions Home 9.24. Row and Array Comparisons
    \ No newline at end of file +

    Prev Up Next
    9.22. Window Functions Home 9.24. Row and Array Comparisons
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-textsearch.html postgresql-13-13.12/doc/src/sgml/html/functions-textsearch.html --- postgresql-13-13.11/doc/src/sgml/html/functions-textsearch.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-textsearch.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.13. Text Search Functions and Operators
    9.13. Text Search Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.13. Text Search Functions and Operators

    +9.13. Text Search Functions and Operators

    9.13. Text Search Functions and Operators
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.13. Text Search Functions and Operators

    Table 9.41, Table 9.42 and Table 9.43 @@ -750,4 +750,4 @@

    ts_stat('SELECT vector FROM apod') → (foo,10,15) ... -


    Prev Up Next
    9.12. Network Address Functions and Operators Home 9.14. UUID Functions
    \ No newline at end of file +


    Prev Up Next
    9.12. Network Address Functions and Operators Home 9.14. UUID Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-trigger.html postgresql-13-13.12/doc/src/sgml/html/functions-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/functions-trigger.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-trigger.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -9.28. Trigger Functions
    9.28. Trigger Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.28. Trigger Functions

    +9.28. Trigger Functions

    9.28. Trigger Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.28. Trigger Functions

    While many uses of triggers involve user-written trigger functions, PostgreSQL provides a few built-in trigger functions that can be used directly in user-defined triggers. These @@ -90,4 +90,4 @@ choose a trigger name that comes after the name of any other trigger you might have on the table. (Hence the “z” prefix in the example.) -

    Prev Up Next
    9.27. System Administration Functions Home 9.29. Event Trigger Functions
    \ No newline at end of file +

    Prev Up Next
    9.27. System Administration Functions Home 9.29. Event Trigger Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-uuid.html postgresql-13-13.12/doc/src/sgml/html/functions-uuid.html --- postgresql-13-13.11/doc/src/sgml/html/functions-uuid.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-uuid.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.14. UUID Functions
    9.14. UUID Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.14. UUID Functions

    +9.14. UUID Functions

    9.14. UUID Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.14. UUID Functions

    PostgreSQL includes one function to generate a UUID: 

     gen_random_uuid () → uuid
@@ -13,4 +13,4 @@
    PostgreSQL also provides the usual comparison
    operators shown in Table 9.1 for
    UUIDs.
-
    Prev Up Next
    9.13. Text Search Functions and Operators Home 9.15. XML Functions
    \ No newline at end of file +

    Prev Up Next
    9.13. Text Search Functions and Operators Home 9.15. XML Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-window.html postgresql-13-13.12/doc/src/sgml/html/functions-window.html --- postgresql-13-13.11/doc/src/sgml/html/functions-window.html 2023-05-08 21:33:51.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-window.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.22. Window Functions
    9.22. Window Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.22. Window Functions

    +9.22. Window Functions

    9.22. Window Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.22. Window Functions

    Window functions provide the ability to perform calculations across sets of rows that are related to the current query row. See Section 3.5 for an introduction to this @@ -179,4 +179,4 @@ default FROM FIRST behavior is supported. (You can achieve the result of FROM LAST by reversing the ORDER BY ordering.) -

    Prev Up Next
    9.21. Aggregate Functions Home 9.23. Subquery Expressions
    \ No newline at end of file +

    Prev Up Next
    9.21. Aggregate Functions Home 9.23. Subquery Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions-xml.html postgresql-13-13.12/doc/src/sgml/html/functions-xml.html --- postgresql-13-13.11/doc/src/sgml/html/functions-xml.html 2023-05-08 21:33:50.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions-xml.html 2023-08-07 20:32:10.000000000 +0000 @@ -1,5 +1,5 @@ -9.15. XML Functions
    9.15. XML Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.15. XML Functions

    9.15.1. Producing XML Content
    9.15.2. XML Predicates
    9.15.3. Processing XML
    9.15.4. Mapping Tables to XML

    +9.15. XML Functions

    9.15. XML Functions
    Prev UpChapter 9. Functions and OperatorsHome Next

    9.15. XML Functions

    9.15.1. Producing XML Content
    9.15.2. XML Predicates
    9.15.3. Processing XML
    9.15.4. Mapping Tables to XML

    The functions and function-like expressions described in this section operate on values of type xml. See Section 8.13 for information about the xml type. The function-like expressions xmlparse @@ -908,4 +908,4 @@ will be put into content form with each such disallowed node replaced by its string value, as defined for the XPath 1.0 string function. -

    Prev Up Next
    9.14. UUID Functions Home 9.16. JSON Functions and Operators
    \ No newline at end of file +

    Prev Up Next
    9.14. UUID Functions Home 9.16. JSON Functions and Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/functions.html postgresql-13-13.12/doc/src/sgml/html/functions.html --- postgresql-13-13.11/doc/src/sgml/html/functions.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/functions.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 9. Functions and Operators
    Chapter 9. Functions and Operators
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 9. Functions and Operators

    Table of Contents

    9.1. Logical Operators
    9.2. Comparison Functions and Operators
    9.3. Mathematical Functions and Operators
    9.4. String Functions and Operators
    9.4.1. format
    9.5. Binary String Functions and Operators
    9.6. Bit String Functions and Operators
    9.7. Pattern Matching
    9.7.1. LIKE
    9.7.2. SIMILAR TO Regular Expressions
    9.7.3. POSIX Regular Expressions
    9.8. Data Type Formatting Functions
    9.9. Date/Time Functions and Operators
    9.9.1. EXTRACT, date_part
    9.9.2. date_trunc
    9.9.3. AT TIME ZONE
    9.9.4. Current Date/Time
    9.9.5. Delaying Execution
    9.10. Enum Support Functions
    9.11. Geometric Functions and Operators
    9.12. Network Address Functions and Operators
    9.13. Text Search Functions and Operators
    9.14. UUID Functions
    9.15. XML Functions
    9.15.1. Producing XML Content
    9.15.2. XML Predicates
    9.15.3. Processing XML
    9.15.4. Mapping Tables to XML
    9.16. JSON Functions and Operators
    9.16.1. Processing and Creating JSON Data
    9.16.2. The SQL/JSON Path Language
    9.17. Sequence Manipulation Functions
    9.18. Conditional Expressions
    9.18.1. CASE
    9.18.2. COALESCE
    9.18.3. NULLIF
    9.18.4. GREATEST and LEAST
    9.19. Array Functions and Operators
    9.20. Range Functions and Operators
    9.21. Aggregate Functions
    9.22. Window Functions
    9.23. Subquery Expressions
    9.23.1. EXISTS
    9.23.2. IN
    9.23.3. NOT IN
    9.23.4. ANY/SOME
    9.23.5. ALL
    9.23.6. Single-Row Comparison
    9.24. Row and Array Comparisons
    9.24.1. IN
    9.24.2. NOT IN
    9.24.3. ANY/SOME (array)
    9.24.4. ALL (array)
    9.24.5. Row Constructor Comparison
    9.24.6. Composite Type Comparison
    9.25. Set Returning Functions
    9.26. System Information Functions and Operators
    9.27. System Administration Functions
    9.27.1. Configuration Settings Functions
    9.27.2. Server Signaling Functions
    9.27.3. Backup Control Functions
    9.27.4. Recovery Control Functions
    9.27.5. Snapshot Synchronization Functions
    9.27.6. Replication Management Functions
    9.27.7. Database Object Management Functions
    9.27.8. Index Maintenance Functions
    9.27.9. Generic File Access Functions
    9.27.10. Advisory Lock Functions
    9.28. Trigger Functions
    9.29. Event Trigger Functions
    9.29.1. Capturing Changes at Command End
    9.29.2. Processing Objects Dropped by a DDL Command
    9.29.3. Handling a Table Rewrite Event
    9.30. Statistics Information Functions
    9.30.1. Inspecting MCV Lists

    +Chapter 9. Functions and Operators

    Chapter 9. Functions and Operators
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 9. Functions and Operators

    Table of Contents

    9.1. Logical Operators
    9.2. Comparison Functions and Operators
    9.3. Mathematical Functions and Operators
    9.4. String Functions and Operators
    9.4.1. format
    9.5. Binary String Functions and Operators
    9.6. Bit String Functions and Operators
    9.7. Pattern Matching
    9.7.1. LIKE
    9.7.2. SIMILAR TO Regular Expressions
    9.7.3. POSIX Regular Expressions
    9.8. Data Type Formatting Functions
    9.9. Date/Time Functions and Operators
    9.9.1. EXTRACT, date_part
    9.9.2. date_trunc
    9.9.3. AT TIME ZONE
    9.9.4. Current Date/Time
    9.9.5. Delaying Execution
    9.10. Enum Support Functions
    9.11. Geometric Functions and Operators
    9.12. Network Address Functions and Operators
    9.13. Text Search Functions and Operators
    9.14. UUID Functions
    9.15. XML Functions
    9.15.1. Producing XML Content
    9.15.2. XML Predicates
    9.15.3. Processing XML
    9.15.4. Mapping Tables to XML
    9.16. JSON Functions and Operators
    9.16.1. Processing and Creating JSON Data
    9.16.2. The SQL/JSON Path Language
    9.17. Sequence Manipulation Functions
    9.18. Conditional Expressions
    9.18.1. CASE
    9.18.2. COALESCE
    9.18.3. NULLIF
    9.18.4. GREATEST and LEAST
    9.19. Array Functions and Operators
    9.20. Range Functions and Operators
    9.21. Aggregate Functions
    9.22. Window Functions
    9.23. Subquery Expressions
    9.23.1. EXISTS
    9.23.2. IN
    9.23.3. NOT IN
    9.23.4. ANY/SOME
    9.23.5. ALL
    9.23.6. Single-Row Comparison
    9.24. Row and Array Comparisons
    9.24.1. IN
    9.24.2. NOT IN
    9.24.3. ANY/SOME (array)
    9.24.4. ALL (array)
    9.24.5. Row Constructor Comparison
    9.24.6. Composite Type Comparison
    9.25. Set Returning Functions
    9.26. System Information Functions and Operators
    9.27. System Administration Functions
    9.27.1. Configuration Settings Functions
    9.27.2. Server Signaling Functions
    9.27.3. Backup Control Functions
    9.27.4. Recovery Control Functions
    9.27.5. Snapshot Synchronization Functions
    9.27.6. Replication Management Functions
    9.27.7. Database Object Management Functions
    9.27.8. Index Maintenance Functions
    9.27.9. Generic File Access Functions
    9.27.10. Advisory Lock Functions
    9.28. Trigger Functions
    9.29. Event Trigger Functions
    9.29.1. Capturing Changes at Command End
    9.29.2. Processing Objects Dropped by a DDL Command
    9.29.3. Handling a Table Rewrite Event
    9.30. Statistics Information Functions
    9.30.1. Inspecting MCV Lists

    PostgreSQL provides a large number of functions and operators for the built-in data types. This chapter describes most of them, although additional special-purpose functions @@ -30,4 +30,4 @@ is present in other SQL database management systems, and in many cases this functionality is compatible and consistent between the various implementations. -

    Prev Up Next
    8.21. Pseudo-Types Home 9.1. Logical Operators
    \ No newline at end of file +

    Prev Up Next
    8.21. Pseudo-Types Home 9.1. Logical Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/fuzzystrmatch.html postgresql-13-13.12/doc/src/sgml/html/fuzzystrmatch.html --- postgresql-13-13.11/doc/src/sgml/html/fuzzystrmatch.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/fuzzystrmatch.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.15. fuzzystrmatch
    F.15. fuzzystrmatch
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.15. fuzzystrmatch

    F.15.1. Soundex
    F.15.2. Levenshtein
    F.15.3. Metaphone
    F.15.4. Double Metaphone

    +F.15. fuzzystrmatch

    F.15. fuzzystrmatch
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.15. fuzzystrmatch

    F.15.1. Soundex
    F.15.2. Levenshtein
    F.15.3. Metaphone
    F.15.4. Double Metaphone

    The fuzzystrmatch module provides several functions to determine similarities and distance between strings.

    Caution

    @@ -135,4 +135,4 @@ ------------ KMP (1 row) -

    Prev Up Next
    F.14. file_fdw Home F.16. hstore
    \ No newline at end of file +
    Prev Up Next
    F.14. file_fdw Home F.16. hstore
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/generic-wal.html postgresql-13-13.12/doc/src/sgml/html/generic-wal.html --- postgresql-13-13.11/doc/src/sgml/html/generic-wal.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/generic-wal.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 62. Generic WAL Records
    Chapter 62. Generic WAL Records
    Prev UpPart VII. InternalsHome Next

    Chapter 62. Generic WAL Records

    +Chapter 62. Generic WAL Records

    Chapter 62. Generic WAL Records
    Prev UpPart VII. InternalsHome Next

    Chapter 62. Generic WAL Records

    Although all built-in WAL-logged modules have their own types of WAL records, there is also a generic WAL record type, which describes changes to pages in a generic way. This is useful for extensions that provide @@ -92,4 +92,4 @@ comparison. This is not very compact for the case of moving data within a page, and might be improved in the future.

    -

    Prev Up Next
    61.6. Index Cost Estimation Functions Home Chapter 63. B-Tree Indexes
    \ No newline at end of file +

    Prev Up Next
    61.6. Index Cost Estimation Functions Home Chapter 63. B-Tree Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/geqo-biblio.html postgresql-13-13.12/doc/src/sgml/html/geqo-biblio.html --- postgresql-13-13.11/doc/src/sgml/html/geqo-biblio.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/geqo-biblio.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -59.4. Further Reading
    59.4. Further Reading
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.4. Further Reading

    +59.4. Further Reading

    59.4. Further Reading
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.4. Further Reading

    The following resources contain additional information about genetic algorithms: @@ -15,4 +15,4 @@

  • [fong]

    • -

    Prev Up Next
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL Home Chapter 60. Table Access Method Interface Definition
    \ No newline at end of file +

    Prev Up Next
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL Home Chapter 60. Table Access Method Interface Definition
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/geqo-intro.html postgresql-13-13.12/doc/src/sgml/html/geqo-intro.html --- postgresql-13-13.11/doc/src/sgml/html/geqo-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/geqo-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -59.1. Query Handling as a Complex Optimization Problem
    59.1. Query Handling as a Complex Optimization Problem
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.1. Query Handling as a Complex Optimization Problem

    +59.1. Query Handling as a Complex Optimization Problem

    59.1. Query Handling as a Complex Optimization Problem
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.1. Query Handling as a Complex Optimization Problem

    Among all relational operators the most difficult one to process and optimize is the join. The number of possible query plans grows exponentially with the @@ -33,4 +33,4 @@ genetic algorithm to solve the join ordering problem in a manner that is efficient for queries involving large numbers of joins. -

    Prev Up Next
    Chapter 59. Genetic Query Optimizer Home 59.2. Genetic Algorithms
    \ No newline at end of file +

    Prev Up Next
    Chapter 59. Genetic Query Optimizer Home 59.2. Genetic Algorithms
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/geqo-intro2.html postgresql-13-13.12/doc/src/sgml/html/geqo-intro2.html --- postgresql-13-13.11/doc/src/sgml/html/geqo-intro2.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/geqo-intro2.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -59.2. Genetic Algorithms
    59.2. Genetic Algorithms
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.2. Genetic Algorithms

    +59.2. Genetic Algorithms

    59.2. Genetic Algorithms
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.2. Genetic Algorithms

    The genetic algorithm (GA) is a heuristic optimization method which operates through randomized search. The set of possible solutions for the optimization problem is considered as a @@ -24,4 +24,4 @@ strongly that a GA is not a pure random search for a solution to a problem. A GA uses stochastic processes, but the result is distinctly non-random (better than random). -

    Prev Up Next
    59.1. Query Handling as a Complex Optimization Problem Home 59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    \ No newline at end of file +

    Prev Up Next
    59.1. Query Handling as a Complex Optimization Problem Home 59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/geqo-pg-intro.html postgresql-13-13.12/doc/src/sgml/html/geqo-pg-intro.html --- postgresql-13-13.11/doc/src/sgml/html/geqo-pg-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/geqo-pg-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.3. Genetic Query Optimization (GEQO) in PostgreSQL

    59.3.1. Generating Possible Plans with GEQO
    59.3.2. Future Implementation Tasks for +59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    Prev UpChapter 59. Genetic Query OptimizerHome Next

    59.3. Genetic Query Optimization (GEQO) in PostgreSQL

    59.3.1. Generating Possible Plans with GEQO
    59.3.2. Future Implementation Tasks for PostgreSQL GEQO

    The GEQO module approaches the query optimization problem as though it were the well-known traveling salesman @@ -104,4 +104,4 @@ of the rest of the tour, but this is certainly not true for query optimization. Thus it is questionable whether edge recombination crossover is the most effective mutation procedure. -

    Prev Up Next
    59.2. Genetic Algorithms Home 59.4. Further Reading
    \ No newline at end of file +

    Prev Up Next
    59.2. Genetic Algorithms Home 59.4. Further Reading
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/geqo.html postgresql-13-13.12/doc/src/sgml/html/geqo.html --- postgresql-13-13.11/doc/src/sgml/html/geqo.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/geqo.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,8 +1,8 @@ -Chapter 59. Genetic Query Optimizer
    Chapter 59. Genetic Query Optimizer
    Prev UpPart VII. InternalsHome Next

    Chapter 59. Genetic Query Optimizer

    Table of Contents

    59.1. Query Handling as a Complex Optimization Problem
    59.2. Genetic Algorithms
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    59.3.1. Generating Possible Plans with GEQO
    59.3.2. Future Implementation Tasks for +Chapter 59. Genetic Query Optimizer
    Chapter 59. Genetic Query Optimizer
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    58.3. Executing Custom Scans Home 59.1. Query Handling as a Complex Optimization Problem
    \ No newline at end of file +

    Prev Up Next
    58.3. Executing Custom Scans Home 59.1. Query Handling as a Complex Optimization Problem
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-builtin-opclasses.html postgresql-13-13.12/doc/src/sgml/html/gin-builtin-opclasses.html --- postgresql-13-13.11/doc/src/sgml/html/gin-builtin-opclasses.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-builtin-opclasses.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.2. Built-in Operator Classes
    66.2. Built-in Operator Classes
    Prev UpChapter 66. GIN IndexesHome Next

    66.2. Built-in Operator Classes

    +66.2. Built-in Operator Classes

    66.2. Built-in Operator Classes
    Prev UpChapter 66. GIN IndexesHome Next

    66.2. Built-in Operator Classes

    The core PostgreSQL distribution includes the GIN operator classes shown in Table 66.1. @@ -29,4 +29,4 @@ is the default. jsonb_path_ops supports fewer operators but offers better performance for those operators. See Section 8.14.4 for details. -

    Prev Up Next
    66.1. Introduction Home 66.3. Extensibility
    \ No newline at end of file +

    Prev Up Next
    66.1. Introduction Home 66.3. Extensibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-examples.html postgresql-13-13.12/doc/src/sgml/html/gin-examples.html --- postgresql-13-13.11/doc/src/sgml/html/gin-examples.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-examples.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.7. Examples
    66.7. Examples
    Prev UpChapter 66. GIN IndexesHome Next

    66.7. Examples

    +66.7. Examples

    66.7. Examples
    Prev UpChapter 66. GIN IndexesHome Next

    66.7. Examples

    The core PostgreSQL distribution includes the GIN operator classes previously shown in Table 66.1. @@ -7,4 +7,4 @@ GIN operator classes:

    btree_gin

    B-tree equivalent functionality for several data types

    hstore

    Module for storing (key, value) pairs

    intarray

    Enhanced support for int[]

    pg_trgm

    Text similarity using trigram matching

    -

    Prev Up Next
    66.6. Limitations Home Chapter 67. BRIN Indexes
    \ No newline at end of file +

    Prev Up Next
    66.6. Limitations Home Chapter 67. BRIN Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-extensibility.html postgresql-13-13.12/doc/src/sgml/html/gin-extensibility.html --- postgresql-13-13.11/doc/src/sgml/html/gin-extensibility.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-extensibility.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.3. Extensibility
    66.3. Extensibility
    Prev UpChapter 66. GIN IndexesHome Next

    66.3. Extensibility

    +66.3. Extensibility

    66.3. Extensibility
    Prev UpChapter 66. GIN IndexesHome Next

    66.3. Extensibility

    The GIN interface has a high level of abstraction, requiring the access method implementer only to implement the semantics of the data type being accessed. The GIN layer itself @@ -234,4 +234,4 @@ recommended that the SQL declarations of these three support functions use the opclass's indexed data type for the query argument, even though the actual type might be something else depending on the operator. -

    Prev Up Next
    66.2. Built-in Operator Classes Home 66.4. Implementation
    \ No newline at end of file +

    Prev Up Next
    66.2. Built-in Operator Classes Home 66.4. Implementation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-implementation.html postgresql-13-13.12/doc/src/sgml/html/gin-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/gin-implementation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-implementation.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.4. Implementation
    66.4. Implementation
    Prev UpChapter 66. GIN IndexesHome Next

    66.4. Implementation

    66.4.1. GIN Fast Update Technique
    66.4.2. Partial Match Algorithm

    +66.4. Implementation

    66.4. Implementation
    Prev UpChapter 66. GIN IndexesHome Next

    66.4. Implementation

    66.4.1. GIN Fast Update Technique
    66.4.2. Partial Match Algorithm

    Internally, a GIN index contains a B-tree index constructed over keys, where each key is an element of one or more indexed items (a member of an array, for example) and where each tuple in a leaf @@ -61,4 +61,4 @@ index key, less than zero for a non-match that is still within the range to be searched, or greater than zero if the index key is past the range that could match. -

    Prev Up Next
    66.3. Extensibility Home 66.5. GIN Tips and Tricks
    \ No newline at end of file +

    Prev Up Next
    66.3. Extensibility Home 66.5. GIN Tips and Tricks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-intro.html postgresql-13-13.12/doc/src/sgml/html/gin-intro.html --- postgresql-13-13.11/doc/src/sgml/html/gin-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.1. Introduction
    66.1. Introduction
    Prev UpChapter 66. GIN IndexesHome Next

    66.1. Introduction

    +66.1. Introduction

    66.1. Introduction
    Prev UpChapter 66. GIN IndexesHome Next

    66.1. Introduction

    GIN stands for Generalized Inverted Index. GIN is designed for handling cases where the items to be indexed are composite values, and the queries to be handled by @@ -37,4 +37,4 @@ maintained by Teodor Sigaev and Oleg Bartunov. There is more information about GIN on their website. -

    Prev Up Next
    Chapter 66. GIN Indexes Home 66.2. Built-in Operator Classes
    \ No newline at end of file +

    Prev Up Next
    Chapter 66. GIN Indexes Home 66.2. Built-in Operator Classes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-limit.html postgresql-13-13.12/doc/src/sgml/html/gin-limit.html --- postgresql-13-13.11/doc/src/sgml/html/gin-limit.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-limit.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.6. Limitations
    66.6. Limitations
    Prev UpChapter 66. GIN IndexesHome Next

    66.6. Limitations

    +66.6. Limitations

    66.6. Limitations
    Prev UpChapter 66. GIN IndexesHome Next

    66.6. Limitations

    GIN assumes that indexable operators are strict. This means that extractValue will not be called at all on a null item value (instead, a placeholder index entry is created automatically), @@ -7,4 +7,4 @@ value either (instead, the query is presumed to be unsatisfiable). Note however that null key values contained within a non-null composite item or query value are supported. -

    Prev Up Next
    66.5. GIN Tips and Tricks Home 66.7. Examples
    \ No newline at end of file +

    Prev Up Next
    66.5. GIN Tips and Tricks Home 66.7. Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin-tips.html postgresql-13-13.12/doc/src/sgml/html/gin-tips.html --- postgresql-13-13.11/doc/src/sgml/html/gin-tips.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin-tips.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -66.5. GIN Tips and Tricks
    66.5. GIN Tips and Tricks
    Prev UpChapter 66. GIN IndexesHome Next

    66.5. GIN Tips and Tricks

    Create vs. insert

    +66.5. GIN Tips and Tricks

    66.5. GIN Tips and Tricks
    Prev UpChapter 66. GIN IndexesHome Next

    66.5. GIN Tips and Tricks

    Create vs. insert

    Insertion into a GIN index can be slow due to the likelihood of many keys being inserted for each item. So, for bulk insertions into a table it is advisable to drop the GIN @@ -54,4 +54,4 @@

    From experience, values in the thousands (e.g., 5000 — 20000) work well. -

    Prev Up Next
    66.4. Implementation Home 66.6. Limitations
    \ No newline at end of file +

    Prev Up Next
    66.4. Implementation Home 66.6. Limitations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gin.html postgresql-13-13.12/doc/src/sgml/html/gin.html --- postgresql-13-13.11/doc/src/sgml/html/gin.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gin.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 66. GIN Indexes
    Chapter 66. GIN Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    65.5. Examples Home 66.1. Introduction
    \ No newline at end of file +Chapter 66. GIN Indexes
    Chapter 66. GIN Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    65.5. Examples Home 66.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist-builtin-opclasses.html postgresql-13-13.12/doc/src/sgml/html/gist-builtin-opclasses.html --- postgresql-13-13.11/doc/src/sgml/html/gist-builtin-opclasses.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist-builtin-opclasses.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -64.2. Built-in Operator Classes
    64.2. Built-in Operator Classes
    Prev UpChapter 64. GiST IndexesHome Next

    64.2. Built-in Operator Classes

    +64.2. Built-in Operator Classes

    64.2. Built-in Operator Classes
    Prev UpChapter 64. GiST IndexesHome Next

    64.2. Built-in Operator Classes

    The core PostgreSQL distribution includes the GiST operator classes shown in Table 64.1. @@ -107,4 +107,4 @@ 

     CREATE INDEX ON my_table USING GIST (my_inet_column inet_ops);

    -

    Prev Up Next
    64.1. Introduction Home 64.3. Extensibility
    \ No newline at end of file +

    Prev Up Next
    64.1. Introduction Home 64.3. Extensibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist-examples.html postgresql-13-13.12/doc/src/sgml/html/gist-examples.html --- postgresql-13-13.11/doc/src/sgml/html/gist-examples.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist-examples.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -64.5. Examples
    64.5. Examples
    Prev UpChapter 64. GiST IndexesHome Next

    64.5. Examples

    +64.5. Examples

    64.5. Examples
    Prev UpChapter 64. GiST IndexesHome Next

    64.5. Examples

    The PostgreSQL source distribution includes several examples of index methods implemented using GiST. The core system currently provides text search @@ -10,4 +10,4 @@ operator classes:

    btree_gist

    B-tree equivalent functionality for several data types

    cube

    Indexing for multidimensional cubes

    hstore

    Module for storing (key, value) pairs

    intarray

    RD-Tree for one-dimensional array of int4 values

    ltree

    Indexing for tree-like structures

    pg_trgm

    Text similarity using trigram matching

    seg

    Indexing for “float ranges”

    -

    Prev Up Next
    64.4. Implementation Home Chapter 65. SP-GiST Indexes
    \ No newline at end of file +

    Prev Up Next
    64.4. Implementation Home Chapter 65. SP-GiST Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist-extensibility.html postgresql-13-13.12/doc/src/sgml/html/gist-extensibility.html --- postgresql-13-13.11/doc/src/sgml/html/gist-extensibility.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist-extensibility.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -64.3. Extensibility
    64.3. Extensibility
    Prev UpChapter 64. GiST IndexesHome Next

    64.3. Extensibility

    +64.3. Extensibility

    64.3. Extensibility
    Prev UpChapter 64. GiST IndexesHome Next

    64.3. Extensibility

    Traditionally, implementing a new index access method meant a lot of difficult work. It was necessary to understand the inner workings of the database, such as the lock manager and Write-Ahead Log. The @@ -752,4 +752,4 @@ index scan, index build, or index tuple insertion). Be careful to pfree the previous value when replacing a fn_extra value, or the leak will accumulate for the duration of the operation. -

    Prev Up Next
    64.2. Built-in Operator Classes Home 64.4. Implementation
    \ No newline at end of file +

    Prev Up Next
    64.2. Built-in Operator Classes Home 64.4. Implementation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist-implementation.html postgresql-13-13.12/doc/src/sgml/html/gist-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/gist-implementation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist-implementation.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -64.4. Implementation
    64.4. Implementation
    Prev UpChapter 64. GiST IndexesHome Next

    64.4. Implementation

    64.4.1. GiST Buffering Build

    64.4.1. GiST Buffering Build

    +64.4. Implementation

    64.4. Implementation
    Prev UpChapter 64. GiST IndexesHome Next

    64.4. Implementation

    64.4.1. GiST Buffering Build

    64.4.1. GiST Buffering Build

    Building large GiST indexes by simply inserting all the tuples tends to be slow, because if the index tuples are scattered across the index and the index is large enough to not fit in cache, the insertions need to perform @@ -24,4 +24,4 @@ to the CREATE INDEX command. The default behavior is good for most cases, but turning buffering off might speed up the build somewhat if the input data is ordered. -

    Prev Up Next
    64.3. Extensibility Home 64.5. Examples
    \ No newline at end of file +

    Prev Up Next
    64.3. Extensibility Home 64.5. Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist-intro.html postgresql-13-13.12/doc/src/sgml/html/gist-intro.html --- postgresql-13-13.11/doc/src/sgml/html/gist-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -64.1. Introduction
    64.1. Introduction
    Prev UpChapter 64. GiST IndexesHome Next

    64.1. Introduction

    +64.1. Introduction

    64.1. Introduction
    Prev UpChapter 64. GiST IndexesHome Next

    64.1. Introduction

    GiST stands for Generalized Search Tree. It is a balanced, tree-structured access method, that acts as a base template in which to implement arbitrary indexing schemes. B-trees, R-trees and many @@ -20,4 +20,4 @@ maintained by Teodor Sigaev and Oleg Bartunov, and there is more information on their web site. -

    Prev Up Next
    Chapter 64. GiST Indexes Home 64.2. Built-in Operator Classes
    \ No newline at end of file +

    Prev Up Next
    Chapter 64. GiST Indexes Home 64.2. Built-in Operator Classes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gist.html postgresql-13-13.12/doc/src/sgml/html/gist.html --- postgresql-13-13.11/doc/src/sgml/html/gist.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gist.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 64. GiST Indexes
    Chapter 64. GiST Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    63.4. Implementation Home 64.1. Introduction
    \ No newline at end of file +Chapter 64. GiST Indexes
    Chapter 64. GiST Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    63.4. Implementation Home 64.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/git.html postgresql-13-13.12/doc/src/sgml/html/git.html --- postgresql-13-13.11/doc/src/sgml/html/git.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/git.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -I.1. Getting the Source via Git
    I.1. Getting the Source via Git
    Prev UpAppendix I. The Source Code RepositoryHome Next

    I.1. Getting the Source via Git

    +I.1. Getting the Source via Git

    I.1. Getting the Source via Git
    Prev UpAppendix I. The Source Code RepositoryHome Next

    I.1. Getting the Source via Git

    With Git you will make a copy of the entire code repository on your local machine, so you will have access to all history and branches offline. This is the fastest and most flexible way to develop or test @@ -39,4 +39,4 @@ Git can do a lot more things than just fetch the source. For more information, consult the Git man pages, or see the website at https://git-scm.com. -

    Prev Up Next
    Appendix I. The Source Code Repository Home Appendix J. Documentation
    \ No newline at end of file +

    Prev Up Next
    Appendix I. The Source Code Repository Home Appendix J. Documentation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/glossary.html postgresql-13-13.12/doc/src/sgml/html/glossary.html --- postgresql-13-13.11/doc/src/sgml/html/glossary.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/glossary.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix M. Glossary
    Appendix M. Glossary
    Prev UpPart VIII. AppendixesHome Next

    Appendix M. Glossary

    +Appendix M. Glossary

    Appendix M. Glossary
    Prev UpPart VIII. AppendixesHome Next

    Appendix M. Glossary

    This is a list of terms and their meaning in the context of PostgreSQL and relational database systems in general. @@ -995,4 +995,4 @@ It comprises many individual WAL records written sequentially to WAL files. -

    Prev Up Next
    Appendix L. Acronyms Home Appendix N. Color Support
    \ No newline at end of file +

    Prev Up Next
    Appendix L. Acronyms Home Appendix N. Color Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gssapi-auth.html postgresql-13-13.12/doc/src/sgml/html/gssapi-auth.html --- postgresql-13-13.11/doc/src/sgml/html/gssapi-auth.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gssapi-auth.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.6. GSSAPI Authentication
    20.6. GSSAPI Authentication
    Prev UpChapter 20. Client AuthenticationHome Next

    20.6. GSSAPI Authentication

    +20.6. GSSAPI Authentication

    20.6. GSSAPI Authentication
    Prev UpChapter 20. Client AuthenticationHome Next

    20.6. GSSAPI Authentication

    GSSAPI is an industry-standard protocol for secure authentication defined in RFC 2743. @@ -115,4 +115,4 @@ parameter. If that is set to true, client principals are matched to user map entries case-insensitively. krb_realm, if set, is also matched case-insensitively. -

    Prev Up Next
    20.5. Password Authentication Home 20.7. SSPI Authentication
    \ No newline at end of file +

    Prev Up Next
    20.5. Password Authentication Home 20.7. SSPI Authentication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/gssapi-enc.html postgresql-13-13.12/doc/src/sgml/html/gssapi-enc.html --- postgresql-13-13.11/doc/src/sgml/html/gssapi-enc.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/gssapi-enc.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.10. Secure TCP/IP Connections with GSSAPI Encryption
    18.10. Secure TCP/IP Connections with GSSAPI Encryption
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.10. Secure TCP/IP Connections with GSSAPI Encryption

    18.10.1. Basic Setup

    +18.10. Secure TCP/IP Connections with GSSAPI Encryption

    18.10. Secure TCP/IP Connections with GSSAPI Encryption
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.10. Secure TCP/IP Connections with GSSAPI Encryption

    18.10.1. Basic Setup

    PostgreSQL also has native support for using GSSAPI to encrypt client/server communications for increased security. Support requires that a GSSAPI @@ -28,4 +28,4 @@ behavior, GSSAPI encryption requires no setup beyond that which is necessary for GSSAPI authentication. (For more information on configuring that, see Section 20.6.) -

    Prev Up Next
    18.9. Secure TCP/IP Connections with SSL Home 18.11. Secure TCP/IP Connections with SSH Tunnels
    \ No newline at end of file +

    Prev Up Next
    18.9. Secure TCP/IP Connections with SSL Home 18.11. Secure TCP/IP Connections with SSH Tunnels
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/hash-implementation.html postgresql-13-13.12/doc/src/sgml/html/hash-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/hash-implementation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/hash-implementation.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -68.2. Implementation
    68.2. Implementation
    Prev UpChapter 68. Hash IndexesHome Next

    68.2. Implementation

    +68.2. Implementation

    68.2. Implementation
    Prev UpChapter 68. Hash IndexesHome Next

    68.2. Implementation

    There are four kinds of pages in a hash index: the meta page (page zero), which contains statically allocated control information; primary bucket pages; overflow pages; and bitmap pages, which keep track of overflow @@ -33,4 +33,4 @@ src/backend/access/hash/README. The split algorithm is crash safe and can be restarted if not completed successfully. -

    Prev Up Next
    68.1. Overview Home Chapter 69. Database Physical Storage
    \ No newline at end of file +

    Prev Up Next
    68.1. Overview Home Chapter 69. Database Physical Storage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/hash-index.html postgresql-13-13.12/doc/src/sgml/html/hash-index.html --- postgresql-13-13.11/doc/src/sgml/html/hash-index.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/hash-index.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 68. Hash Indexes
    Chapter 68. Hash Indexes
    Prev UpPart VII. InternalsHome Next

    Chapter 68. Hash Indexes

    Table of Contents

    68.1. Overview
    68.2. Implementation
    Prev Up Next
    67.3. Extensibility Home 68.1. Overview
    \ No newline at end of file +Chapter 68. Hash Indexes
    Chapter 68. Hash Indexes
    Prev UpPart VII. InternalsHome Next

    Chapter 68. Hash Indexes

    Table of Contents

    68.1. Overview
    68.2. Implementation
    Prev Up Next
    67.3. Extensibility Home 68.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/hash-intro.html postgresql-13-13.12/doc/src/sgml/html/hash-intro.html --- postgresql-13-13.11/doc/src/sgml/html/hash-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/hash-intro.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -68.1. Overview
    68.1. Overview
    Prev UpChapter 68. Hash IndexesHome Next

    68.1. Overview

    +68.1. Overview

    68.1. Overview
    Prev UpChapter 68. Hash IndexesHome Next

    68.1. Overview

    PostgreSQL includes an implementation of persistent on-disk hash indexes, which are fully crash recoverable. Any data type can be indexed by a @@ -74,4 +74,4 @@ The expansion occurs in the foreground, which could increase execution time for user inserts. Thus, hash indexes may not be suitable for tables with rapidly increasing number of rows. -

    Prev Up Next
    Chapter 68. Hash Indexes Home 68.2. Implementation
    \ No newline at end of file +

    Prev Up Next
    Chapter 68. Hash Indexes Home 68.2. Implementation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/high-availability.html postgresql-13-13.12/doc/src/sgml/html/high-availability.html --- postgresql-13-13.11/doc/src/sgml/html/high-availability.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/high-availability.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 26. High Availability, Load Balancing, and Replication
    Chapter 26. High Availability, Load Balancing, and Replication
    Prev UpPart III. Server AdministrationHome Next

    Chapter 26. High Availability, Load Balancing, and Replication

    Table of Contents

    26.1. Comparison of Different Solutions
    26.2. Log-Shipping Standby Servers
    26.2.1. Planning
    26.2.2. Standby Server Operation
    26.2.3. Preparing the Master for Standby Servers
    26.2.4. Setting Up a Standby Server
    26.2.5. Streaming Replication
    26.2.6. Replication Slots
    26.2.7. Cascading Replication
    26.2.8. Synchronous Replication
    26.2.9. Continuous Archiving in Standby
    26.3. Failover
    26.4. Alternative Method for Log Shipping
    26.4.1. Implementation
    26.4.2. Record-Based Log Shipping
    26.5. Hot Standby
    26.5.1. User's Overview
    26.5.2. Handling Query Conflicts
    26.5.3. Administrator's Overview
    26.5.4. Hot Standby Parameter Reference
    26.5.5. Caveats

    +Chapter 26. High Availability, Load Balancing, and Replication

    Chapter 26. High Availability, Load Balancing, and Replication
    Prev UpPart III. Server AdministrationHome Next
    Prev Up Next
    25.3. Continuous Archiving and Point-in-Time Recovery (PITR) Home 26.1. Comparison of Different Solutions
    \ No newline at end of file +

    Prev Up Next
    25.3. Continuous Archiving and Point-in-Time Recovery (PITR) Home 26.1. Comparison of Different Solutions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/history.html postgresql-13-13.12/doc/src/sgml/html/history.html --- postgresql-13-13.11/doc/src/sgml/html/history.html 2023-05-08 21:33:47.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/history.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,9 +1,9 @@ -2. A Brief History of PostgreSQL
    2. A Brief History of PostgreSQL
    Prev UpPrefaceHome Next

    2. A Brief History of PostgreSQL

    2.1. The Berkeley POSTGRES Project
    2.2. Postgres95
    2.3. PostgreSQL

    +2. A Brief History of PostgreSQL

    2. A Brief History of PostgreSQL
    Prev UpPrefaceHome Next

    2. A Brief History of PostgreSQL

    2.1. The Berkeley POSTGRES Project
    2.2. Postgres95
    2.3. PostgreSQL

    The object-relational database management system now known as PostgreSQL is derived from the POSTGRES package written at the - University of California at Berkeley. With over two decades of + University of California at Berkeley. With decades of development behind it, PostgreSQL is now the most advanced open-source database available anywhere.

    2.1. The Berkeley POSTGRES Project

    @@ -137,4 +137,4 @@

    Details about what has happened in PostgreSQL since then can be found in Appendix E. -

    Prev Up Next
    1.  What Is PostgreSQL? Home 3. Conventions
    \ No newline at end of file +

    Prev Up Next
    1.  What Is PostgreSQL? Home 3. Conventions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/hot-standby.html postgresql-13-13.12/doc/src/sgml/html/hot-standby.html --- postgresql-13-13.11/doc/src/sgml/html/hot-standby.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/hot-standby.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -26.5. Hot Standby
    26.5. Hot Standby
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.5. Hot Standby

    26.5.1. User's Overview
    26.5.2. Handling Query Conflicts
    26.5.3. Administrator's Overview
    26.5.4. Hot Standby Parameter Reference
    26.5.5. Caveats

    +26.5. Hot Standby

    26.5. Hot Standby
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.5. Hot Standby

    26.5.1. User's Overview
    26.5.2. Handling Query Conflicts
    26.5.3. Administrator's Overview
    26.5.4. Hot Standby Parameter Reference
    26.5.5. Caveats

    Hot Standby is the term used to describe the ability to connect to the server and run read-only queries while the server is in archive recovery or standby mode. This @@ -538,4 +538,4 @@ hot standby mode will generate an error.

    -

    Prev Up Next
    26.4. Alternative Method for Log Shipping Home Chapter 27. Monitoring Database Activity
    \ No newline at end of file +

    Prev Up Next
    26.4. Alternative Method for Log Shipping Home Chapter 27. Monitoring Database Activity
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/how-parallel-query-works.html postgresql-13-13.12/doc/src/sgml/html/how-parallel-query-works.html --- postgresql-13-13.11/doc/src/sgml/html/how-parallel-query-works.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/how-parallel-query-works.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -15.1. How Parallel Query Works
    15.1. How Parallel Query Works
    Prev UpChapter 15. Parallel QueryHome Next

    15.1. How Parallel Query Works

    +15.1. How Parallel Query Works

    15.1. How Parallel Query Works
    Prev UpChapter 15. Parallel QueryHome Next

    15.1. How Parallel Query Works

    When the optimizer determines that parallel query is the fastest execution strategy for a particular query, it will create a query plan that includes a Gather or Gather Merge @@ -68,4 +68,4 @@ order-preserving merge. In contrast, Gather reads tuples from the workers in whatever order is convenient, destroying any sort order that may have existed. -

    Prev Up Next
    Chapter 15. Parallel Query Home 15.2. When Can Parallel Query Be Used?
    \ No newline at end of file +

    Prev Up Next
    Chapter 15. Parallel Query Home 15.2. When Can Parallel Query Be Used?
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/hstore.html postgresql-13-13.12/doc/src/sgml/html/hstore.html --- postgresql-13-13.11/doc/src/sgml/html/hstore.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/hstore.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.16. hstore
    F.16. hstore
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.16. hstore

    F.16.1. hstore External Representation
    F.16.2. hstore Operators and Functions
    F.16.3. Indexes
    F.16.4. Examples
    F.16.5. Statistics
    F.16.6. Compatibility
    F.16.7. Transforms
    F.16.8. Authors

    +F.16. hstore

    F.16. hstore
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.16. hstore

    F.16.1. hstore External Representation
    F.16.2. hstore Operators and Functions
    F.16.3. Indexes
    F.16.4. Examples
    F.16.5. Statistics
    F.16.6. Compatibility
    F.16.7. Transforms
    F.16.8. Authors

    This module implements the hstore data type for storing sets of key/value pairs within a single PostgreSQL value. This can be useful in various scenarios, such as rows with many attributes @@ -666,4 +666,4 @@

    Additional enhancements by Andrew Gierth , United Kingdom -

    Prev Up Next
    F.15. fuzzystrmatch Home F.17. intagg
    \ No newline at end of file +

    Prev Up Next
    F.15. fuzzystrmatch Home F.17. intagg
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-api.html postgresql-13-13.12/doc/src/sgml/html/index-api.html --- postgresql-13-13.11/doc/src/sgml/html/index-api.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-api.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.1. Basic API Structure for Indexes
    61.1. Basic API Structure for Indexes
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.1. Basic API Structure for Indexes

    +61.1. Basic API Structure for Indexes

    61.1. Basic API Structure for Indexes
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.1. Basic API Structure for Indexes

    Each index access method is described by a row in the pg_am system catalog. The pg_am entry @@ -176,4 +176,4 @@ sensible: it means that there can only be one key column, but there can also be included column(s). Also, included columns must be allowed to be null, independently of amoptionalkey. -

    Prev Up Next
    Chapter 61. Index Access Method Interface Definition Home 61.2. Index Access Method Functions
    \ No newline at end of file +

    Prev Up Next
    Chapter 61. Index Access Method Interface Definition Home 61.2. Index Access Method Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-cost-estimation.html postgresql-13-13.12/doc/src/sgml/html/index-cost-estimation.html --- postgresql-13-13.11/doc/src/sgml/html/index-cost-estimation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-cost-estimation.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.6. Index Cost Estimation Functions
    61.6. Index Cost Estimation Functions
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.6. Index Cost Estimation Functions

    +61.6. Index Cost Estimation Functions

    61.6. Index Cost Estimation Functions
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.6. Index Cost Estimation Functions

    The amcostestimate function is given information describing a possible index scan, including lists of WHERE and ORDER BY clauses that have been determined to be usable with the index. It must return estimates @@ -139,4 +139,4 @@

    Examples of cost estimator functions can be found in src/backend/utils/adt/selfuncs.c. -

    Prev Up Next
    61.5. Index Uniqueness Checks Home Chapter 62. Generic WAL Records
    \ No newline at end of file +

    Prev Up Next
    61.5. Index Uniqueness Checks Home Chapter 62. Generic WAL Records
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-functions.html postgresql-13-13.12/doc/src/sgml/html/index-functions.html --- postgresql-13-13.11/doc/src/sgml/html/index-functions.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-functions.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.2. Index Access Method Functions
    61.2. Index Access Method Functions
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.2. Index Access Method Functions

    +61.2. Index Access Method Functions

    61.2. Index Access Method Functions
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.2. Index Access Method Functions

    The index construction and maintenance functions that an index access method must provide in IndexAmRoutine are:

    @@ -429,4 +429,4 @@ must be restarted. It should reset any shared state set up by aminitparallelscan such that the scan will be restarted from the beginning. -

    Prev Up Next
    61.1. Basic API Structure for Indexes Home 61.3. Index Scanning
    \ No newline at end of file +

    Prev Up Next
    61.1. Basic API Structure for Indexes Home 61.3. Index Scanning
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-locking.html postgresql-13-13.12/doc/src/sgml/html/index-locking.html --- postgresql-13-13.11/doc/src/sgml/html/index-locking.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-locking.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.4. Index Locking Considerations
    61.4. Index Locking Considerations
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.4. Index Locking Considerations

    +61.4. Index Locking Considerations

    61.4. Index Locking Considerations
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.4. Index Locking Considerations

    Index access methods must handle concurrent updates of the index by multiple processes. The core PostgreSQL system obtains @@ -88,4 +88,4 @@ integrity. When the flag is set, it indicates that the index access method implements finer-grained predicate locking, which will tend to reduce the frequency of such transaction cancellations. -

    Prev Up Next
    61.3. Index Scanning Home 61.5. Index Uniqueness Checks
    \ No newline at end of file +

    Prev Up Next
    61.3. Index Scanning Home 61.5. Index Uniqueness Checks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-scanning.html postgresql-13-13.12/doc/src/sgml/html/index-scanning.html --- postgresql-13-13.11/doc/src/sgml/html/index-scanning.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-scanning.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.3. Index Scanning
    61.3. Index Scanning
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.3. Index Scanning

    +61.3. Index Scanning

    61.3. Index Scanning
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.3. Index Scanning

    In an index scan, the index access method is responsible for regurgitating the TIDs of all the tuples it has been told about that match the scan keys. The access method is not involved in @@ -120,4 +120,4 @@ Note that it is permitted for an access method to implement only amgetbitmap and not amgettuple, or vice versa, if its internal implementation is unsuited to one API or the other. -

    Prev Up Next
    61.2. Index Access Method Functions Home 61.4. Index Locking Considerations
    \ No newline at end of file +

    Prev Up Next
    61.2. Index Access Method Functions Home 61.4. Index Locking Considerations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index-unique-checks.html postgresql-13-13.12/doc/src/sgml/html/index-unique-checks.html --- postgresql-13-13.11/doc/src/sgml/html/index-unique-checks.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index-unique-checks.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -61.5. Index Uniqueness Checks
    61.5. Index Uniqueness Checks
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.5. Index Uniqueness Checks

    +61.5. Index Uniqueness Checks

    61.5. Index Uniqueness Checks
    Prev UpChapter 61. Index Access Method Interface DefinitionHome Next

    61.5. Index Uniqueness Checks

    PostgreSQL enforces SQL uniqueness constraints using unique indexes, which are indexes that disallow multiple entries with identical keys. An access method that supports this @@ -106,4 +106,4 @@ target row is found in the recheck verifies that we are scanning for the same tuple values as were used in the original insertion.

    -

    Prev Up Next
    61.4. Index Locking Considerations Home 61.6. Index Cost Estimation Functions
    \ No newline at end of file +

    Prev Up Next
    61.4. Index Locking Considerations Home 61.6. Index Cost Estimation Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/index.html postgresql-13-13.12/doc/src/sgml/html/index.html --- postgresql-13-13.11/doc/src/sgml/html/index.html 2023-05-08 21:34:20.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/index.html 2023-08-07 20:32:40.000000000 +0000 @@ -1,2 +1,2 @@ -PostgreSQL 13.11 Documentation
    PostgreSQL 13.11 Documentation
         Next

    PostgreSQL 13.11 Documentation

    The PostgreSQL Global Development Group

    Copyright © 1996–2023 The PostgreSQL Global Development Group

    Table of Contents

    Preface
    1. What Is PostgreSQL?
    2. A Brief History of PostgreSQL
    3. Conventions
    4. Further Information
    5. Bug Reporting Guidelines
    I. Tutorial
    1. Getting Started
    2. The SQL Language
    3. Advanced Features
    II. The SQL Language
    4. SQL Syntax
    5. Data Definition
    6. Data Manipulation
    7. Queries
    8. Data Types
    9. Functions and Operators
    10. Type Conversion
    11. Indexes
    12. Full Text Search
    13. Concurrency Control
    14. Performance Tips
    15. Parallel Query
    III. Server Administration
    16. Installation from Source Code
    17. Installation from Source Code on Windows
    18. Server Setup and Operation
    19. Server Configuration
    20. Client Authentication
    21. Database Roles
    22. Managing Databases
    23. Localization
    24. Routine Database Maintenance Tasks
    25. Backup and Restore
    26. High Availability, Load Balancing, and Replication
    27. Monitoring Database Activity
    28. Monitoring Disk Usage
    29. Reliability and the Write-Ahead Log
    30. Logical Replication
    31. Just-in-Time Compilation (JIT)
    32. Regression Tests
    IV. Client Interfaces
    33. libpq — C Library
    34. Large Objects
    35. ECPG — Embedded SQL in C
    36. The Information Schema
    V. Server Programming
    37. Extending SQL
    38. Triggers
    39. Event Triggers
    40. The Rule System
    41. Procedural Languages
    42. PL/pgSQL — SQL Procedural Language
    43. PL/Tcl — Tcl Procedural Language
    44. PL/Perl — Perl Procedural Language
    45. PL/Python — Python Procedural Language
    46. Server Programming Interface
    47. Background Worker Processes
    48. Logical Decoding
    49. Replication Progress Tracking
    VI. Reference
    I. SQL Commands
    II. PostgreSQL Client Applications
    III. PostgreSQL Server Applications
    VII. Internals
    50. Overview of PostgreSQL Internals
    51. System Catalogs
    52. Frontend/Backend Protocol
    53. PostgreSQL Coding Conventions
    54. Native Language Support
    55. Writing a Procedural Language Handler
    56. Writing a Foreign Data Wrapper
    57. Writing a Table Sampling Method
    58. Writing a Custom Scan Provider
    59. Genetic Query Optimizer
    60. Table Access Method Interface Definition
    61. Index Access Method Interface Definition
    62. Generic WAL Records
    63. B-Tree Indexes
    64. GiST Indexes
    65. SP-GiST Indexes
    66. GIN Indexes
    67. BRIN Indexes
    68. Hash Indexes
    69. Database Physical Storage
    70. System Catalog Declarations and Initial Contents
    71. How the Planner Uses Statistics
    72. Backup Manifest Format
    VIII. Appendixes
    A. PostgreSQL Error Codes
    B. Date/Time Support
    C. SQL Key Words
    D. SQL Conformance
    E. Release Notes
    F. Additional Supplied Modules
    G. Additional Supplied Programs
    H. External Projects
    I. The Source Code Repository
    J. Documentation
    K. PostgreSQL Limits
    L. Acronyms
    M. Glossary
    N. Color Support
    O. Obsolete or Renamed Features
    Bibliography
    Index
       Next
       Preface
    \ No newline at end of file +PostgreSQL 13.12 Documentation
    PostgreSQL 13.12 Documentation
         Next

    PostgreSQL 13.12 Documentation

    The PostgreSQL Global Development Group

    Copyright © 1996–2023 The PostgreSQL Global Development Group

    Table of Contents

    Preface
    1. What Is PostgreSQL?
    2. A Brief History of PostgreSQL
    3. Conventions
    4. Further Information
    5. Bug Reporting Guidelines
    I. Tutorial
    1. Getting Started
    2. The SQL Language
    3. Advanced Features
    II. The SQL Language
    4. SQL Syntax
    5. Data Definition
    6. Data Manipulation
    7. Queries
    8. Data Types
    9. Functions and Operators
    10. Type Conversion
    11. Indexes
    12. Full Text Search
    13. Concurrency Control
    14. Performance Tips
    15. Parallel Query
    III. Server Administration
    16. Installation from Source Code
    17. Installation from Source Code on Windows
    18. Server Setup and Operation
    19. Server Configuration
    20. Client Authentication
    21. Database Roles
    22. Managing Databases
    23. Localization
    24. Routine Database Maintenance Tasks
    25. Backup and Restore
    26. High Availability, Load Balancing, and Replication
    27. Monitoring Database Activity
    28. Monitoring Disk Usage
    29. Reliability and the Write-Ahead Log
    30. Logical Replication
    31. Just-in-Time Compilation (JIT)
    32. Regression Tests
    IV. Client Interfaces
    33. libpq — C Library
    34. Large Objects
    35. ECPG — Embedded SQL in C
    36. The Information Schema
    V. Server Programming
    37. Extending SQL
    38. Triggers
    39. Event Triggers
    40. The Rule System
    41. Procedural Languages
    42. PL/pgSQL — SQL Procedural Language
    43. PL/Tcl — Tcl Procedural Language
    44. PL/Perl — Perl Procedural Language
    45. PL/Python — Python Procedural Language
    46. Server Programming Interface
    47. Background Worker Processes
    48. Logical Decoding
    49. Replication Progress Tracking
    VI. Reference
    I. SQL Commands
    II. PostgreSQL Client Applications
    III. PostgreSQL Server Applications
    VII. Internals
    50. Overview of PostgreSQL Internals
    51. System Catalogs
    52. Frontend/Backend Protocol
    53. PostgreSQL Coding Conventions
    54. Native Language Support
    55. Writing a Procedural Language Handler
    56. Writing a Foreign Data Wrapper
    57. Writing a Table Sampling Method
    58. Writing a Custom Scan Provider
    59. Genetic Query Optimizer
    60. Table Access Method Interface Definition
    61. Index Access Method Interface Definition
    62. Generic WAL Records
    63. B-Tree Indexes
    64. GiST Indexes
    65. SP-GiST Indexes
    66. GIN Indexes
    67. BRIN Indexes
    68. Hash Indexes
    69. Database Physical Storage
    70. System Catalog Declarations and Initial Contents
    71. How the Planner Uses Statistics
    72. Backup Manifest Format
    VIII. Appendixes
    A. PostgreSQL Error Codes
    B. Date/Time Support
    C. SQL Key Words
    D. SQL Conformance
    E. Release Notes
    F. Additional Supplied Modules
    G. Additional Supplied Programs
    H. External Projects
    I. The Source Code Repository
    J. Documentation
    K. PostgreSQL Limits
    L. Acronyms
    M. Glossary
    N. Color Support
    O. Obsolete or Renamed Features
    Bibliography
    Index
       Next
       Preface
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexam.html postgresql-13-13.12/doc/src/sgml/html/indexam.html --- postgresql-13-13.11/doc/src/sgml/html/indexam.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexam.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 61. Index Access Method Interface Definition
    Chapter 61. Index Access Method Interface Definition
    Prev UpPart VII. InternalsHome Next

    Chapter 61. Index Access Method Interface Definition

    Table of Contents

    61.1. Basic API Structure for Indexes
    61.2. Index Access Method Functions
    61.3. Index Scanning
    61.4. Index Locking Considerations
    61.5. Index Uniqueness Checks
    61.6. Index Cost Estimation Functions

    +Chapter 61. Index Access Method Interface Definition

    Chapter 61. Index Access Method Interface Definition
    Prev UpPart VII. InternalsHome Next

    Chapter 61. Index Access Method Interface Definition

    Table of Contents

    61.1. Basic API Structure for Indexes
    61.2. Index Access Method Functions
    61.3. Index Scanning
    61.4. Index Locking Considerations
    61.5. Index Uniqueness Checks
    61.6. Index Cost Estimation Functions

    This chapter defines the interface between the core PostgreSQL system and index access methods, which manage individual index types. The core system @@ -32,4 +32,4 @@ statement; but indexes do not deal with those, either.) Index entries for dead tuples are reclaimed (by vacuuming) when the dead tuples themselves are reclaimed. -

    Prev Up Next
    Chapter 60. Table Access Method Interface Definition Home 61.1. Basic API Structure for Indexes
    \ No newline at end of file +

    Prev Up Next
    Chapter 60. Table Access Method Interface Definition Home 61.1. Basic API Structure for Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-bitmap-scans.html postgresql-13-13.12/doc/src/sgml/html/indexes-bitmap-scans.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-bitmap-scans.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-bitmap-scans.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.5. Combining Multiple Indexes
    11.5. Combining Multiple Indexes
    Prev UpChapter 11. IndexesHome Next

    11.5. Combining Multiple Indexes

    +11.5. Combining Multiple Indexes

    11.5. Combining Multiple Indexes
    Prev UpChapter 11. IndexesHome Next

    11.5. Combining Multiple Indexes

    A single index scan can only use query clauses that use the index's columns with operators of its operator class and are joined with AND. For example, given an index on (a, b) @@ -58,4 +58,4 @@ common. If one of the types of query is much less common than the others, you'd probably settle for creating just the two indexes that best match the common types. -

    Prev Up Next
    11.4. Indexes and ORDER BY Home 11.6. Unique Indexes
    \ No newline at end of file +

    Prev Up Next
    11.4. Indexes and ORDER BY Home 11.6. Unique Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-collations.html postgresql-13-13.12/doc/src/sgml/html/indexes-collations.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-collations.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-collations.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.11. Indexes and Collations
    11.11. Indexes and Collations
    Prev UpChapter 11. IndexesHome Next

    11.11. Indexes and Collations

    +11.11. Indexes and Collations

    11.11. Indexes and Collations
    Prev UpChapter 11. IndexesHome Next

    11.11. Indexes and Collations

    An index can support only one collation per index column. If multiple collations are of interest, multiple indexes may be needed.

    @@ -28,4 +28,4 @@ 

     CREATE INDEX test1c_content_y_index ON test1c (content COLLATE "y");

    -

    Prev Up Next
    11.10. Operator Classes and Operator Families Home 11.12. Examining Index Usage
    \ No newline at end of file +

    Prev Up Next
    11.10. Operator Classes and Operator Families Home 11.12. Examining Index Usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-examine.html postgresql-13-13.12/doc/src/sgml/html/indexes-examine.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-examine.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-examine.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.12. Examining Index Usage
    11.12. Examining Index Usage
    Prev UpChapter 11. IndexesHome Next

    11.12. Examining Index Usage

    +11.12. Examining Index Usage

    11.12. Examining Index Usage
    Prev UpChapter 11. IndexesHome Next

    11.12. Examining Index Usage

    Although indexes in PostgreSQL do not need maintenance or tuning, it is still important to check which indexes are actually used by the real-life query workload. @@ -79,4 +79,4 @@ appropriate, then you might have to resort to forcing index usage explicitly. You might also want to contact the PostgreSQL developers to examine the issue. -

    Prev Up Next
    11.11. Indexes and Collations Home Chapter 12. Full Text Search
    \ No newline at end of file +

    Prev Up Next
    11.11. Indexes and Collations Home Chapter 12. Full Text Search
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-expressional.html postgresql-13-13.12/doc/src/sgml/html/indexes-expressional.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-expressional.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-expressional.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.7. Indexes on Expressions
    11.7. Indexes on Expressions
    Prev UpChapter 11. IndexesHome Next

    11.7. Indexes on Expressions

    +11.7. Indexes on Expressions

    11.7. Indexes on Expressions
    Prev UpChapter 11. IndexesHome Next

    11.7. Indexes on Expressions

    An index column need not be just a column of the underlying table, but can be a function or scalar expression computed from one or more columns of the table. This feature is useful to obtain fast @@ -46,4 +46,4 @@ and so the speed of the search is equivalent to any other simple index query. Thus, indexes on expressions are useful when retrieval speed is more important than insertion and update speed. -

    Prev Up Next
    11.6. Unique Indexes Home 11.8. Partial Indexes
    \ No newline at end of file +

    Prev Up Next
    11.6. Unique Indexes Home 11.8. Partial Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-index-only-scans.html postgresql-13-13.12/doc/src/sgml/html/indexes-index-only-scans.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-index-only-scans.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-index-only-scans.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.9. Index-Only Scans and Covering Indexes
    11.9. Index-Only Scans and Covering Indexes
    Prev UpChapter 11. IndexesHome Next

    11.9. Index-Only Scans and Covering Indexes

    +11.9. Index-Only Scans and Covering Indexes

    11.9. Index-Only Scans and Covering Indexes
    Prev UpChapter 11. IndexesHome Next

    11.9. Index-Only Scans and Covering Indexes

    All indexes in PostgreSQL are secondary indexes, meaning that each index is stored separately from the table's main data area (which is called the @@ -206,4 +206,4 @@ checked in the plan. PostgreSQL versions 9.6 and later will recognize such cases and allow index-only scans to be generated, but older versions will not. -

    Prev Up Next
    11.8. Partial Indexes Home 11.10. Operator Classes and Operator Families
    \ No newline at end of file +

    Prev Up Next
    11.8. Partial Indexes Home 11.10. Operator Classes and Operator Families
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-intro.html postgresql-13-13.12/doc/src/sgml/html/indexes-intro.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-intro.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-intro.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.1. Introduction
    11.1. Introduction
    Prev UpChapter 11. IndexesHome Next

    11.1. Introduction

    +11.1. Introduction

    11.1. Introduction
    Prev UpChapter 11. IndexesHome Next

    11.1. Introduction

    Suppose we have a table similar to this: 

     CREATE TABLE test1 (
@@ -74,4 +74,4 @@
    tuples.
    Therefore indexes that are seldom or never used in queries
    should be removed.
-
    Prev Up Next
    Chapter 11. Indexes Home 11.2. Index Types
    \ No newline at end of file +

    Prev Up Next
    Chapter 11. Indexes Home 11.2. Index Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-multicolumn.html postgresql-13-13.12/doc/src/sgml/html/indexes-multicolumn.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-multicolumn.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-multicolumn.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.3. Multicolumn Indexes
    11.3. Multicolumn Indexes
    Prev UpChapter 11. IndexesHome Next

    11.3. Multicolumn Indexes

    +11.3. Multicolumn Indexes

    11.3. Multicolumn Indexes
    Prev UpChapter 11. IndexesHome Next

    11.3. Multicolumn Indexes

    An index can be defined on more than one column of a table. For example, if you have a table of this form: 

    @@ -77,4 +77,4 @@
    Section 11.5 and
    Section 11.9 for some discussion of the
    merits of different index configurations.
-
    Prev Up Next
    11.2. Index Types Home 11.4. Indexes and ORDER BY
    \ No newline at end of file +

    Prev Up Next
    11.2. Index Types Home 11.4. Indexes and ORDER BY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-opclass.html postgresql-13-13.12/doc/src/sgml/html/indexes-opclass.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-opclass.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-opclass.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.10. Operator Classes and Operator Families
    11.10. Operator Classes and Operator Families
    Prev UpChapter 11. IndexesHome Next

    11.10. Operator Classes and Operator Families

    +11.10. Operator Classes and Operator Families

    11.10. Operator Classes and Operator Families
    Prev UpChapter 11. IndexesHome Next

    11.10. Operator Classes and Operator Families

    An index definition can specify an operator class for each column of an index. 

    @@ -104,4 +104,4 @@
     commands \dAc, \dAf,
     and \dAo, which provide slightly more sophisticated
     versions of these queries.
-
    Prev Up Next
    11.9. Index-Only Scans and Covering Indexes Home 11.11. Indexes and Collations
    \ No newline at end of file +

    Prev Up Next
    11.9. Index-Only Scans and Covering Indexes Home 11.11. Indexes and Collations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-ordering.html postgresql-13-13.12/doc/src/sgml/html/indexes-ordering.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-ordering.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-ordering.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.4. Indexes and ORDER BY
    11.4. Indexes and ORDER BY
    Prev UpChapter 11. IndexesHome Next

    11.4. Indexes and ORDER BY

    +11.4. Indexes and ORDER BY

    11.4. Indexes and ORDER BY
    Prev UpChapter 11. IndexesHome Next

    11.4. Indexes and ORDER BY

    In addition to simply finding the rows to be returned by a query, an index may be able to deliver them in a specific sorted order. This allows a query's ORDER BY specification to be honored @@ -61,4 +61,4 @@ speedups for certain queries. Whether it's worth maintaining such an index depends on how often you use queries that require a special sort ordering. -

    Prev Up Next
    11.3. Multicolumn Indexes Home 11.5. Combining Multiple Indexes
    \ No newline at end of file +

    Prev Up Next
    11.3. Multicolumn Indexes Home 11.5. Combining Multiple Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-partial.html postgresql-13-13.12/doc/src/sgml/html/indexes-partial.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-partial.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-partial.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.8. Partial Indexes
    11.8. Partial Indexes
    Prev UpChapter 11. IndexesHome Next

    11.8. Partial Indexes

    +11.8. Partial Indexes

    11.8. Partial Indexes
    Prev UpChapter 11. IndexesHome Next

    11.8. Partial Indexes

    A partial index is an index built over a subset of a table; the subset is defined by a conditional expression (called the predicate of the @@ -209,4 +209,4 @@ far better performance is possible.


    More information about partial indexes can be found in [ston89b], [olson93], and [seshadri95]. -

    Prev Up Next
    11.7. Indexes on Expressions Home 11.9. Index-Only Scans and Covering Indexes
    \ No newline at end of file +

    Prev Up Next
    11.7. Indexes on Expressions Home 11.9. Index-Only Scans and Covering Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-types.html postgresql-13-13.12/doc/src/sgml/html/indexes-types.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-types.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-types.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.2. Index Types
    11.2. Index Types
    Prev UpChapter 11. IndexesHome Next

    11.2. Index Types

    +11.2. Index Types

    11.2. Index Types
    Prev UpChapter 11. IndexesHome Next

    11.2. Index Types

    PostgreSQL provides several index types: B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension bloom. Each index type uses a different @@ -150,4 +150,4 @@ The BRIN operator classes included in the standard distribution are documented in Table 67.1. For more information see Chapter 67. -

    Prev Up Next
    11.1. Introduction Home 11.3. Multicolumn Indexes
    \ No newline at end of file +

    Prev Up Next
    11.1. Introduction Home 11.3. Multicolumn Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes-unique.html postgresql-13-13.12/doc/src/sgml/html/indexes-unique.html --- postgresql-13-13.11/doc/src/sgml/html/indexes-unique.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes-unique.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -11.6. Unique Indexes
    11.6. Unique Indexes
    Prev UpChapter 11. IndexesHome Next

    11.6. Unique Indexes

    +11.6. Unique Indexes

    11.6. Unique Indexes
    Prev UpChapter 11. IndexesHome Next

    11.6. Unique Indexes

    Indexes can also be used to enforce uniqueness of a column's value, or the uniqueness of the combined values of more than one column. 

    @@ -21,4 +21,4 @@
     There's no need to manually
     create indexes on unique columns; doing so would just duplicate
     the automatically-created index.
-
    Prev Up Next
    11.5. Combining Multiple Indexes Home 11.7. Indexes on Expressions
    \ No newline at end of file +

    Prev Up Next
    11.5. Combining Multiple Indexes Home 11.7. Indexes on Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/indexes.html postgresql-13-13.12/doc/src/sgml/html/indexes.html --- postgresql-13-13.11/doc/src/sgml/html/indexes.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/indexes.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,8 +1,8 @@ -Chapter 11. Indexes
    Chapter 11. Indexes
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 11. Indexes

    Table of Contents

    11.1. Introduction
    11.2. Index Types
    11.3. Multicolumn Indexes
    11.4. Indexes and ORDER BY
    11.5. Combining Multiple Indexes
    11.6. Unique Indexes
    11.7. Indexes on Expressions
    11.8. Partial Indexes
    11.9. Index-Only Scans and Covering Indexes
    11.10. Operator Classes and Operator Families
    11.11. Indexes and Collations
    11.12. Examining Index Usage

    +Chapter 11. Indexes

    Chapter 11. Indexes
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 11. Indexes

    Table of Contents

    11.1. Introduction
    11.2. Index Types
    11.3. Multicolumn Indexes
    11.4. Indexes and ORDER BY
    11.5. Combining Multiple Indexes
    11.6. Unique Indexes
    11.7. Indexes on Expressions
    11.8. Partial Indexes
    11.9. Index-Only Scans and Covering Indexes
    11.10. Operator Classes and Operator Families
    11.11. Indexes and Collations
    11.12. Examining Index Usage

    Indexes are a common way to enhance database performance. An index allows the database server to find and retrieve specific rows much faster than it could do without an index. But indexes also add overhead to the database system as a whole, so they should be used sensibly. -

    Prev Up Next
    10.6. SELECT Output Columns Home 11.1. Introduction
    \ No newline at end of file +

    Prev Up Next
    10.6. SELECT Output Columns Home 11.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/information-schema.html postgresql-13-13.12/doc/src/sgml/html/information-schema.html --- postgresql-13-13.11/doc/src/sgml/html/information-schema.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/information-schema.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 36. The Information Schema
    Chapter 36. The Information Schema
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 36. The Information Schema

    Table of Contents

    36.1. The Schema
    36.2. Data Types
    36.3. information_schema_catalog_name
    36.4. administrable_role_​authorizations
    36.5. applicable_roles
    36.6. attributes
    36.7. character_sets
    36.8. check_constraint_routine_usage
    36.9. check_constraints
    36.10. collations
    36.11. collation_character_set_​applicability
    36.12. column_column_usage
    36.13. column_domain_usage
    36.14. column_options
    36.15. column_privileges
    36.16. column_udt_usage
    36.17. columns
    36.18. constraint_column_usage
    36.19. constraint_table_usage
    36.20. data_type_privileges
    36.21. domain_constraints
    36.22. domain_udt_usage
    36.23. domains
    36.24. element_types
    36.25. enabled_roles
    36.26. foreign_data_wrapper_options
    36.27. foreign_data_wrappers
    36.28. foreign_server_options
    36.29. foreign_servers
    36.30. foreign_table_options
    36.31. foreign_tables
    36.32. key_column_usage
    36.33. parameters
    36.34. referential_constraints
    36.35. role_column_grants
    36.36. role_routine_grants
    36.37. role_table_grants
    36.38. role_udt_grants
    36.39. role_usage_grants
    36.40. routine_privileges
    36.41. routines
    36.42. schemata
    36.43. sequences
    36.44. sql_features
    36.45. sql_implementation_info
    36.46. sql_parts
    36.47. sql_sizing
    36.48. table_constraints
    36.49. table_privileges
    36.50. tables
    36.51. transforms
    36.52. triggered_update_columns
    36.53. triggers
    36.54. udt_privileges
    36.55. usage_privileges
    36.56. user_defined_types
    36.57. user_mapping_options
    36.58. user_mappings
    36.59. view_column_usage
    36.60. view_routine_usage
    36.61. view_table_usage
    36.62. views

    +Chapter 36. The Information Schema

    Chapter 36. The Information Schema
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 36. The Information Schema

    Table of Contents

    36.1. The Schema
    36.2. Data Types
    36.3. information_schema_catalog_name
    36.4. administrable_role_​authorizations
    36.5. applicable_roles
    36.6. attributes
    36.7. character_sets
    36.8. check_constraint_routine_usage
    36.9. check_constraints
    36.10. collations
    36.11. collation_character_set_​applicability
    36.12. column_column_usage
    36.13. column_domain_usage
    36.14. column_options
    36.15. column_privileges
    36.16. column_udt_usage
    36.17. columns
    36.18. constraint_column_usage
    36.19. constraint_table_usage
    36.20. data_type_privileges
    36.21. domain_constraints
    36.22. domain_udt_usage
    36.23. domains
    36.24. element_types
    36.25. enabled_roles
    36.26. foreign_data_wrapper_options
    36.27. foreign_data_wrappers
    36.28. foreign_server_options
    36.29. foreign_servers
    36.30. foreign_table_options
    36.31. foreign_tables
    36.32. key_column_usage
    36.33. parameters
    36.34. referential_constraints
    36.35. role_column_grants
    36.36. role_routine_grants
    36.37. role_table_grants
    36.38. role_udt_grants
    36.39. role_usage_grants
    36.40. routine_privileges
    36.41. routines
    36.42. schemata
    36.43. sequences
    36.44. sql_features
    36.45. sql_implementation_info
    36.46. sql_parts
    36.47. sql_sizing
    36.48. table_constraints
    36.49. table_privileges
    36.50. tables
    36.51. transforms
    36.52. triggered_update_columns
    36.53. triggers
    36.54. udt_privileges
    36.55. usage_privileges
    36.56. user_defined_types
    36.57. user_mapping_options
    36.58. user_mappings
    36.59. view_column_usage
    36.60. view_routine_usage
    36.61. view_table_usage
    36.62. views

    The information schema consists of a set of views that contain information about the objects defined in the current database. The information schema is defined in the SQL standard and can therefore @@ -28,4 +28,4 @@ issues but contain the table name to help distinguish duplicate rows, e.g., constraint_column_usage, constraint_table_usage, table_constraints. -

    Prev Up Next
    35.17. Internals Home 36.1. The Schema
    \ No newline at end of file +

    Prev Up Next
    35.17. Internals Home 36.1. The Schema
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-administrable-role-authorizations.html postgresql-13-13.12/doc/src/sgml/html/infoschema-administrable-role-authorizations.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.4. administrable_role_​authorizations
    36.4. administrable_role_​authorizations
    Prev UpChapter 36. The Information SchemaHome Next

    36.4. administrable_role_​authorizations

    +36.4. administrable_role_​authorizations

    36.4. administrable_role_​authorizations
    Prev UpChapter 36. The Information SchemaHome Next

    36.4. administrable_role_​authorizations

    The view administrable_role_authorizations identifies all roles that the current user has the admin option for. @@ -25,4 +25,4 @@

    Always YES -


    Prev Up Next
    36.3. information_schema_catalog_name Home 36.5. applicable_roles
    \ No newline at end of file +


    Prev Up Next
    36.3. information_schema_catalog_name Home 36.5. applicable_roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-applicable-roles.html postgresql-13-13.12/doc/src/sgml/html/infoschema-applicable-roles.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-applicable-roles.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-applicable-roles.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.5. applicable_roles
    36.5. applicable_roles
    Prev UpChapter 36. The Information SchemaHome Next

    36.5. applicable_roles

    +36.5. applicable_roles

    36.5. applicable_roles
    Prev UpChapter 36. The Information SchemaHome Next

    36.5. applicable_roles

    The view applicable_roles identifies all roles whose privileges the current user can use. This means there is some chain of role grants from the current user to the role in @@ -30,4 +30,4 @@

    YES if the grantee has the admin option on the role, NO if not -


    Prev Up Next
    36.4. administrable_role_​authorizations Home 36.6. attributes
    \ No newline at end of file +


    Prev Up Next
    36.4. administrable_role_​authorizations Home 36.6. attributes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-attributes.html postgresql-13-13.12/doc/src/sgml/html/infoschema-attributes.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-attributes.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-attributes.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.6. attributes
    36.6. attributes
    Prev UpChapter 36. The Information SchemaHome Next

    36.6. attributes

    +36.6. attributes

    36.6. attributes
    Prev UpChapter 36. The Information SchemaHome Next

    36.6. attributes

    The view attributes contains information about the attributes of composite data types defined in the database. (Note that the view does not give information about table columns, @@ -223,4 +223,4 @@


    See also under Section 36.17, a similarly structured view, for further information on some of the columns. -

    Prev Up Next
    36.5. applicable_roles Home 36.7. character_sets
    \ No newline at end of file +

    Prev Up Next
    36.5. applicable_roles Home 36.7. character_sets
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-character-sets.html postgresql-13-13.12/doc/src/sgml/html/infoschema-character-sets.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-character-sets.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-character-sets.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.7. character_sets
    36.7. character_sets
    Prev UpChapter 36. The Information SchemaHome Next

    36.7. character_sets

    +36.7. character_sets

    36.7. character_sets
    Prev UpChapter 36. The Information SchemaHome Next

    36.7. character_sets

    The view character_sets identifies the character sets available in the current database. Since PostgreSQL does not support multiple character sets within one database, this view only @@ -83,4 +83,4 @@ settings of the current database. If there is no such collation, then this column and the associated schema and catalog columns are null. -


    Prev Up Next
    36.6. attributes Home 36.8. check_constraint_routine_usage
    \ No newline at end of file +


    Prev Up Next
    36.6. attributes Home 36.8. check_constraint_routine_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.8. check_constraint_routine_usage
    36.8. check_constraint_routine_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.8. check_constraint_routine_usage

    +36.8. check_constraint_routine_usage

    36.8. check_constraint_routine_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.8. check_constraint_routine_usage

    The view check_constraint_routine_usage identifies routines (functions and procedures) that are used by a check constraint. Only those routines are shown that are owned by @@ -39,4 +39,4 @@

    The “specific name” of the function. See Section 36.41 for more information. -


    Prev Up Next
    36.7. character_sets Home 36.9. check_constraints
    \ No newline at end of file +


    Prev Up Next
    36.7. character_sets Home 36.9. check_constraints
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-check-constraints.html postgresql-13-13.12/doc/src/sgml/html/infoschema-check-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-check-constraints.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-check-constraints.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.9. check_constraints
    36.9. check_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.9. check_constraints

    +36.9. check_constraints

    36.9. check_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.9. check_constraints

    The view check_constraints contains all check constraints, either defined on a table or on a domain, that are owned by a currently enabled role. (The owner of the table or @@ -29,4 +29,4 @@

    The check expression of the check constraint -


    Prev Up Next
    36.8. check_constraint_routine_usage Home 36.10. collations
    \ No newline at end of file +


    Prev Up Next
    36.8. check_constraint_routine_usage Home 36.10. collations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-collation-character-set-applicab.html postgresql-13-13.12/doc/src/sgml/html/infoschema-collation-character-set-applicab.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.11. collation_character_set_​applicability
    36.11. collation_character_set_​applicability
    Prev UpChapter 36. The Information SchemaHome Next

    36.11. collation_character_set_​applicability

    +36.11. collation_character_set_​applicability

    36.11. collation_character_set_​applicability
    Prev UpChapter 36. The Information SchemaHome Next

    36.11. collation_character_set_​applicability

    The view collation_character_set_applicability identifies which character set the available collations are applicable to. In PostgreSQL, there is only one character set per @@ -41,4 +41,4 @@

    Name of the character set -


    Prev Up Next
    36.10. collations Home 36.12. column_column_usage
    \ No newline at end of file +


    Prev Up Next
    36.10. collations Home 36.12. column_column_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-collations.html postgresql-13-13.12/doc/src/sgml/html/infoschema-collations.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-collations.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-collations.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.10. collations
    36.10. collations
    Prev UpChapter 36. The Information SchemaHome Next

    36.10. collations

    +36.10. collations

    36.10. collations
    Prev UpChapter 36. The Information SchemaHome Next

    36.10. collations

    The view collations contains the collations available in the current database.

    Table 36.8. collations Columns

    @@ -28,4 +28,4 @@

    Always NO PAD (The alternative PAD SPACE is not supported by PostgreSQL.) -


    Prev Up Next
    36.9. check_constraints Home 36.11. collation_character_set_​applicability
    \ No newline at end of file +


    Prev Up Next
    36.9. check_constraints Home 36.11. collation_character_set_​applicability
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-column-column-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-column-column-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-column-column-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-column-column-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.12. column_column_usage
    36.12. column_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.12. column_column_usage

    +36.12. column_column_usage

    36.12. column_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.12. column_column_usage

    The view column_column_usage identifies all generated columns that depend on another base column in the same table. Only tables owned by a currently enabled role are included. @@ -33,4 +33,4 @@

    Name of the generated column -


    Prev Up Next
    36.11. collation_character_set_​applicability Home 36.13. column_domain_usage
    \ No newline at end of file +


    Prev Up Next
    36.11. collation_character_set_​applicability Home 36.13. column_domain_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-column-domain-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-column-domain-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-column-domain-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-column-domain-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.13. column_domain_usage
    36.13. column_domain_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.13. column_domain_usage

    +36.13. column_domain_usage

    36.13. column_domain_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.13. column_domain_usage

    The view column_domain_usage identifies all columns (of a table or a view) that make use of some domain defined in the current database and owned by a currently enabled role. @@ -43,4 +43,4 @@

    Name of the column -


    Prev Up Next
    36.12. column_column_usage Home 36.14. column_options
    \ No newline at end of file +


    Prev Up Next
    36.12. column_column_usage Home 36.14. column_options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-column-options.html postgresql-13-13.12/doc/src/sgml/html/infoschema-column-options.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-column-options.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-column-options.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.14. column_options
    36.14. column_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.14. column_options

    +36.14. column_options

    36.14. column_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.14. column_options

    The view column_options contains all the options defined for foreign table columns in the current database. Only those foreign table columns are shown that the current user has access to @@ -39,4 +39,4 @@

    Value of the option -


    Prev Up Next
    36.13. column_domain_usage Home 36.15. column_privileges
    \ No newline at end of file +


    Prev Up Next
    36.13. column_domain_usage Home 36.15. column_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-column-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-column-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-column-privileges.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-column-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.15. column_privileges
    36.15. column_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.15. column_privileges

    +36.15. column_privileges

    36.15. column_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.15. column_privileges

    The view column_privileges identifies all privileges granted on columns to a currently enabled role or by a currently enabled role. There is one row for each combination of @@ -57,4 +57,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.14. column_options Home 36.16. column_udt_usage
    \ No newline at end of file +


    Prev Up Next
    36.14. column_options Home 36.16. column_udt_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-column-udt-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-column-udt-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-column-udt-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-column-udt-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.16. column_udt_usage
    36.16. column_udt_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.16. column_udt_usage

    +36.16. column_udt_usage

    36.16. column_udt_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.16. column_udt_usage

    The view column_udt_usage identifies all columns that use data types owned by a currently enabled role. Note that in PostgreSQL, built-in data types behave @@ -49,4 +49,4 @@

    Name of the column -


    Prev Up Next
    36.15. column_privileges Home 36.17. columns
    \ No newline at end of file +


    Prev Up Next
    36.15. column_privileges Home 36.17. columns
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-columns.html postgresql-13-13.12/doc/src/sgml/html/infoschema-columns.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-columns.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-columns.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.17. columns
    36.17. columns
    Prev UpChapter 36. The Information SchemaHome Next

    36.17. columns

    +36.17. columns

    36.17. columns
    Prev UpChapter 36. The Information SchemaHome Next

    36.17. columns

    The view columns contains information about all table columns (or view columns) in the database. System columns (ctid, etc.) are not included. Only those columns are @@ -334,4 +334,4 @@ columns with their associated data types and treat domains as separate types, you could write coalesce(domain_name, udt_name), etc. -

    Prev Up Next
    36.16. column_udt_usage Home 36.18. constraint_column_usage
    \ No newline at end of file +

    Prev Up Next
    36.16. column_udt_usage Home 36.18. constraint_column_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-constraint-column-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-constraint-column-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-constraint-column-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-constraint-column-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.18. constraint_column_usage
    36.18. constraint_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.18. constraint_column_usage

    +36.18. constraint_column_usage

    36.18. constraint_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.18. constraint_column_usage

    The view constraint_column_usage identifies all columns in the current database that are used by some constraint. Only those columns are shown that are contained in a table owned by @@ -52,4 +52,4 @@

    Name of the constraint -


    Prev Up Next
    36.17. columns Home 36.19. constraint_table_usage
    \ No newline at end of file +


    Prev Up Next
    36.17. columns Home 36.19. constraint_table_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-constraint-table-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-constraint-table-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-constraint-table-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-constraint-table-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.19. constraint_table_usage
    36.19. constraint_table_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.19. constraint_table_usage

    +36.19. constraint_table_usage

    36.19. constraint_table_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.19. constraint_table_usage

    The view constraint_table_usage identifies all tables in the current database that are used by some constraint and are owned by a currently enabled role. (This is different from the @@ -47,4 +47,4 @@

    Name of the constraint -


    Prev Up Next
    36.18. constraint_column_usage Home 36.20. data_type_privileges
    \ No newline at end of file +


    Prev Up Next
    36.18. constraint_column_usage Home 36.20. data_type_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-data-type-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-data-type-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-data-type-privileges.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-data-type-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.20. data_type_privileges
    36.20. data_type_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.20. data_type_privileges

    +36.20. data_type_privileges

    36.20. data_type_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.20. data_type_privileges

    The view data_type_privileges identifies all data type descriptors that the current user has access to, by way of being the owner of the described object or having some privilege @@ -49,4 +49,4 @@

    The identifier of the data type descriptor, which is unique among the data type descriptors for that same object. -


    Prev Up Next
    36.19. constraint_table_usage Home 36.21. domain_constraints
    \ No newline at end of file +


    Prev Up Next
    36.19. constraint_table_usage Home 36.21. domain_constraints
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-datatypes.html postgresql-13-13.12/doc/src/sgml/html/infoschema-datatypes.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-datatypes.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-datatypes.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.2. Data Types
    36.2. Data Types
    Prev UpChapter 36. The Information SchemaHome Next

    36.2. Data Types

    +36.2. Data Types

    36.2. Data Types
    Prev UpChapter 36. The Information SchemaHome Next

    36.2. Data Types

    The columns of the information schema views use special data types that are defined in the information schema. These are defined as simple domains over ordinary built-in types. You should not use @@ -30,4 +30,4 @@

    Every column in the information schema has one of these five types. -

    Prev Up Next
    36.1. The Schema Home 36.3. information_schema_catalog_name
    \ No newline at end of file +

    Prev Up Next
    36.1. The Schema Home 36.3. information_schema_catalog_name
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-domain-constraints.html postgresql-13-13.12/doc/src/sgml/html/infoschema-domain-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-domain-constraints.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-domain-constraints.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.21. domain_constraints
    36.21. domain_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.21. domain_constraints

    +36.21. domain_constraints

    36.21. domain_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.21. domain_constraints

    The view domain_constraints contains all constraints belonging to domains defined in the current database. Only those domains are shown that the current user has access to (by way of being the owner or @@ -49,4 +49,4 @@

    YES if the constraint is deferrable and initially deferred, NO if not -


    Prev Up Next
    36.20. data_type_privileges Home 36.22. domain_udt_usage
    \ No newline at end of file +


    Prev Up Next
    36.20. data_type_privileges Home 36.22. domain_udt_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-domain-udt-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-domain-udt-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-domain-udt-usage.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-domain-udt-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.22. domain_udt_usage
    36.22. domain_udt_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.22. domain_udt_usage

    +36.22. domain_udt_usage

    36.22. domain_udt_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.22. domain_udt_usage

    The view domain_udt_usage identifies all domains that are based on data types owned by a currently enabled role. Note that in PostgreSQL, built-in data @@ -40,4 +40,4 @@

    Name of the domain -


    Prev Up Next
    36.21. domain_constraints Home 36.23. domains
    \ No newline at end of file +


    Prev Up Next
    36.21. domain_constraints Home 36.23. domains
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-domains.html postgresql-13-13.12/doc/src/sgml/html/infoschema-domains.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-domains.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-domains.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.23. domains
    36.23. domains
    Prev UpChapter 36. The Information SchemaHome Next

    36.23. domains

    +36.23. domains

    36.23. domains
    Prev UpChapter 36. The Information SchemaHome Next

    36.23. domains

    The view domains contains all domains defined in the current database. Only those domains are shown that the current user has access to (by way of being the owner or having some privilege). @@ -193,4 +193,4 @@ instances of such identifiers. (The specific format of the identifier is not defined and not guaranteed to remain the same in future versions.) -


    Prev Up Next
    36.22. domain_udt_usage Home 36.24. element_types
    \ No newline at end of file +


    Prev Up Next
    36.22. domain_udt_usage Home 36.24. element_types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-element-types.html postgresql-13-13.12/doc/src/sgml/html/infoschema-element-types.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-element-types.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-element-types.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.24. element_types
    36.24. element_types
    Prev UpChapter 36. The Information SchemaHome Next

    36.24. element_types

    +36.24. element_types

    36.24. element_types
    Prev UpChapter 36. The Information SchemaHome Next

    36.24. element_types

    The view element_types contains the data type descriptors of the elements of arrays. When a table column, composite-type attribute, domain, function parameter, or function return value is defined to @@ -191,4 +191,4 @@

    An identifier of the data type descriptor of the element. This is currently not useful. -


    Prev Up Next
    36.23. domains Home 36.25. enabled_roles
    \ No newline at end of file +


    Prev Up Next
    36.23. domains Home 36.25. enabled_roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-enabled-roles.html postgresql-13-13.12/doc/src/sgml/html/infoschema-enabled-roles.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-enabled-roles.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-enabled-roles.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.25. enabled_roles
    36.25. enabled_roles
    Prev UpChapter 36. The Information SchemaHome Next

    36.25. enabled_roles

    +36.25. enabled_roles

    36.25. enabled_roles
    Prev UpChapter 36. The Information SchemaHome Next

    36.25. enabled_roles

    The view enabled_roles identifies the currently “enabled roles”. The enabled roles are recursively defined as the current user together with all roles that have been @@ -25,4 +25,4 @@

    Name of a role -


    Prev Up Next
    36.24. element_types Home 36.26. foreign_data_wrapper_options
    \ No newline at end of file +


    Prev Up Next
    36.24. element_types Home 36.26. foreign_data_wrapper_options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.26. foreign_data_wrapper_options
    36.26. foreign_data_wrapper_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.26. foreign_data_wrapper_options

    +36.26. foreign_data_wrapper_options

    36.26. foreign_data_wrapper_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.26. foreign_data_wrapper_options

    The view foreign_data_wrapper_options contains all the options defined for foreign-data wrappers in the current database. Only those foreign-data wrappers are shown that the @@ -30,4 +30,4 @@

    Value of the option -


    Prev Up Next
    36.25. enabled_roles Home 36.27. foreign_data_wrappers
    \ No newline at end of file +


    Prev Up Next
    36.25. enabled_roles Home 36.27. foreign_data_wrappers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-data-wrappers.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-data-wrappers.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.27. foreign_data_wrappers
    36.27. foreign_data_wrappers
    Prev UpChapter 36. The Information SchemaHome Next

    36.27. foreign_data_wrappers

    +36.27. foreign_data_wrappers

    36.27. foreign_data_wrappers
    Prev UpChapter 36. The Information SchemaHome Next

    36.27. foreign_data_wrappers

    The view foreign_data_wrappers contains all foreign-data wrappers defined in the current database. Only those foreign-data wrappers are shown that the current user has access to @@ -35,4 +35,4 @@

    Language used to implement this foreign-data wrapper -


    Prev Up Next
    36.26. foreign_data_wrapper_options Home 36.28. foreign_server_options
    \ No newline at end of file +


    Prev Up Next
    36.26. foreign_data_wrapper_options Home 36.28. foreign_server_options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-server-options.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-server-options.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-server-options.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-server-options.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.28. foreign_server_options
    36.28. foreign_server_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.28. foreign_server_options

    +36.28. foreign_server_options

    36.28. foreign_server_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.28. foreign_server_options

    The view foreign_server_options contains all the options defined for foreign servers in the current database. Only those foreign servers are shown that the current user has access to @@ -29,4 +29,4 @@

    Value of the option -


    Prev Up Next
    36.27. foreign_data_wrappers Home 36.29. foreign_servers
    \ No newline at end of file +


    Prev Up Next
    36.27. foreign_data_wrappers Home 36.29. foreign_servers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-servers.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-servers.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-servers.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-servers.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.29. foreign_servers
    36.29. foreign_servers
    Prev UpChapter 36. The Information SchemaHome Next

    36.29. foreign_servers

    +36.29. foreign_servers

    36.29. foreign_servers
    Prev UpChapter 36. The Information SchemaHome Next

    36.29. foreign_servers

    The view foreign_servers contains all foreign servers defined in the current database. Only those foreign servers are shown that the current user has access to (by way of @@ -45,4 +45,4 @@

    Name of the owner of the foreign server -


    Prev Up Next
    36.28. foreign_server_options Home 36.30. foreign_table_options
    \ No newline at end of file +


    Prev Up Next
    36.28. foreign_server_options Home 36.30. foreign_table_options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-table-options.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-table-options.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-table-options.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-table-options.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.30. foreign_table_options
    36.30. foreign_table_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.30. foreign_table_options

    +36.30. foreign_table_options

    36.30. foreign_table_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.30. foreign_table_options

    The view foreign_table_options contains all the options defined for foreign tables in the current database. Only those foreign tables are shown that the current user has access to @@ -34,4 +34,4 @@

    Value of the option -


    Prev Up Next
    36.29. foreign_servers Home 36.31. foreign_tables
    \ No newline at end of file +


    Prev Up Next
    36.29. foreign_servers Home 36.31. foreign_tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-tables.html postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-tables.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-foreign-tables.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-foreign-tables.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.31. foreign_tables
    36.31. foreign_tables
    Prev UpChapter 36. The Information SchemaHome Next

    36.31. foreign_tables

    +36.31. foreign_tables

    36.31. foreign_tables
    Prev UpChapter 36. The Information SchemaHome Next

    36.31. foreign_tables

    The view foreign_tables contains all foreign tables defined in the current database. Only those foreign tables are shown that the current user has access to (by way of @@ -34,4 +34,4 @@

    Name of the foreign server -


    Prev Up Next
    36.30. foreign_table_options Home 36.32. key_column_usage
    \ No newline at end of file +


    Prev Up Next
    36.30. foreign_table_options Home 36.32. key_column_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-information-schema-catalog-name.html postgresql-13-13.12/doc/src/sgml/html/infoschema-information-schema-catalog-name.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.3. information_schema_catalog_name
    36.3. information_schema_catalog_name
    Prev UpChapter 36. The Information SchemaHome Next

    36.3. information_schema_catalog_name

    +36.3. information_schema_catalog_name

    36.3. information_schema_catalog_name
    Prev UpChapter 36. The Information SchemaHome Next

    36.3. information_schema_catalog_name

    information_schema_catalog_name is a table that always contains one row and one column containing the name of the current database (current catalog, in SQL terminology). @@ -13,4 +13,4 @@

    Name of the database that contains this information schema -


    Prev Up Next
    36.2. Data Types Home 36.4. administrable_role_​authorizations
    \ No newline at end of file +


    Prev Up Next
    36.2. Data Types Home 36.4. administrable_role_​authorizations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-key-column-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-key-column-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-key-column-usage.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-key-column-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.32. key_column_usage
    36.32. key_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.32. key_column_usage

    +36.32. key_column_usage

    36.32. key_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.32. key_column_usage

    The view key_column_usage identifies all columns in the current database that are restricted by some unique, primary key, or foreign key constraint. Check constraints are not included @@ -62,4 +62,4 @@ For a foreign-key constraint, ordinal position of the referenced column within its unique constraint (count starts at 1); otherwise null -


    Prev Up Next
    36.31. foreign_tables Home 36.33. parameters
    \ No newline at end of file +


    Prev Up Next
    36.31. foreign_tables Home 36.33. parameters
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-parameters.html postgresql-13-13.12/doc/src/sgml/html/infoschema-parameters.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-parameters.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-parameters.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.33. parameters
    36.33. parameters
    Prev UpChapter 36. The Information SchemaHome Next

    36.33. parameters

    +36.33. parameters

    36.33. parameters
    Prev UpChapter 36. The Information SchemaHome Next

    36.33. parameters

    The view parameters contains information about the parameters (arguments) of all functions in the current database. Only those functions are shown that the current user has access to @@ -185,4 +185,4 @@

    The default expression of the parameter, or null if none or if the function is not owned by a currently enabled role. -


    Prev Up Next
    36.32. key_column_usage Home 36.34. referential_constraints
    \ No newline at end of file +


    Prev Up Next
    36.32. key_column_usage Home 36.34. referential_constraints
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-referential-constraints.html postgresql-13-13.12/doc/src/sgml/html/infoschema-referential-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-referential-constraints.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-referential-constraints.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.34. referential_constraints
    36.34. referential_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.34. referential_constraints

    +36.34. referential_constraints

    36.34. referential_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.34. referential_constraints

    The view referential_constraints contains all referential (foreign key) constraints in the current database. Only those constraints are shown for which the current user has @@ -67,4 +67,4 @@ CASCADE, SET NULL, SET DEFAULT, RESTRICT, or NO ACTION. -


    Prev Up Next
    36.33. parameters Home 36.35. role_column_grants
    \ No newline at end of file +


    Prev Up Next
    36.33. parameters Home 36.35. role_column_grants
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-role-column-grants.html postgresql-13-13.12/doc/src/sgml/html/infoschema-role-column-grants.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-role-column-grants.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-role-column-grants.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.35. role_column_grants
    36.35. role_column_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.35. role_column_grants

    +36.35. role_column_grants

    36.35. role_column_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.35. role_column_grants

    The view role_column_grants identifies all privileges granted on columns where the grantor or grantee is a currently enabled role. Further information can be found under @@ -55,4 +55,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.34. referential_constraints Home 36.36. role_routine_grants
    \ No newline at end of file +


    Prev Up Next
    36.34. referential_constraints Home 36.36. role_routine_grants
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-role-routine-grants.html postgresql-13-13.12/doc/src/sgml/html/infoschema-role-routine-grants.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-role-routine-grants.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-role-routine-grants.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.36. role_routine_grants
    36.36. role_routine_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.36. role_routine_grants

    +36.36. role_routine_grants

    36.36. role_routine_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.36. role_routine_grants

    The view role_routine_grants identifies all privileges granted on functions where the grantor or grantee is a currently enabled role. Further information can be found under @@ -63,4 +63,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.35. role_column_grants Home 36.37. role_table_grants
    \ No newline at end of file +


    Prev Up Next
    36.35. role_column_grants Home 36.37. role_table_grants
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-role-table-grants.html postgresql-13-13.12/doc/src/sgml/html/infoschema-role-table-grants.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-role-table-grants.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-role-table-grants.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.37. role_table_grants
    36.37. role_table_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.37. role_table_grants

    +36.37. role_table_grants

    36.37. role_table_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.37. role_table_grants

    The view role_table_grants identifies all privileges granted on tables or views where the grantor or grantee is a currently enabled role. Further information can be found @@ -61,4 +61,4 @@ in the SELECT privilege, so this column shows YES if the privilege is SELECT, else NO. -


    Prev Up Next
    36.36. role_routine_grants Home 36.38. role_udt_grants
    \ No newline at end of file +


    Prev Up Next
    36.36. role_routine_grants Home 36.38. role_udt_grants
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-role-udt-grants.html postgresql-13-13.12/doc/src/sgml/html/infoschema-role-udt-grants.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-role-udt-grants.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-role-udt-grants.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.38. role_udt_grants
    36.38. role_udt_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.38. role_udt_grants

    +36.38. role_udt_grants

    36.38. role_udt_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.38. role_udt_grants

    The view role_udt_grants is intended to identify USAGE privileges granted on user-defined types where the grantor or grantee is a currently enabled role. Further @@ -50,4 +50,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.37. role_table_grants Home 36.39. role_usage_grants
    \ No newline at end of file +


    Prev Up Next
    36.37. role_table_grants Home 36.39. role_usage_grants
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-role-usage-grants.html postgresql-13-13.12/doc/src/sgml/html/infoschema-role-usage-grants.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-role-usage-grants.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-role-usage-grants.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.39. role_usage_grants
    36.39. role_usage_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.39. role_usage_grants

    +36.39. role_usage_grants

    36.39. role_usage_grants
    Prev UpChapter 36. The Information SchemaHome Next

    36.39. role_usage_grants

    The view role_usage_grants identifies USAGE privileges granted on various kinds of objects where the grantor or grantee is a currently enabled role. @@ -54,4 +54,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.38. role_udt_grants Home 36.40. routine_privileges
    \ No newline at end of file +


    Prev Up Next
    36.38. role_udt_grants Home 36.40. routine_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-routine-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-routine-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-routine-privileges.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-routine-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.40. routine_privileges
    36.40. routine_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.40. routine_privileges

    +36.40. routine_privileges

    36.40. routine_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.40. routine_privileges

    The view routine_privileges identifies all privileges granted on functions to a currently enabled role or by a currently enabled role. There is one row for each combination of function, @@ -59,4 +59,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.39. role_usage_grants Home 36.41. routines
    \ No newline at end of file +


    Prev Up Next
    36.39. role_usage_grants Home 36.41. routines
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-routines.html postgresql-13-13.12/doc/src/sgml/html/infoschema-routines.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-routines.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-routines.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.41. routines
    36.41. routines
    Prev UpChapter 36. The Information SchemaHome Next

    36.41. routines

    +36.41. routines

    36.41. routines
    Prev UpChapter 36. The Information SchemaHome Next

    36.41. routines

    The view routines contains all functions and procedures in the current database. Only those functions and procedures are shown that the current user has access to (by way of being the owner or having some @@ -461,4 +461,4 @@

    Applies to a feature not available in PostgreSQL -


    Prev Up Next
    36.40. routine_privileges Home 36.42. schemata
    \ No newline at end of file +


    Prev Up Next
    36.40. routine_privileges Home 36.42. schemata
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-schema.html postgresql-13-13.12/doc/src/sgml/html/infoschema-schema.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-schema.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-schema.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.1. The Schema
    36.1. The Schema
    Prev UpChapter 36. The Information SchemaHome Next

    36.1. The Schema

    +36.1. The Schema

    36.1. The Schema
    Prev UpChapter 36. The Information SchemaHome Next

    36.1. The Schema

    The information schema itself is a schema named information_schema. This schema automatically exists in all databases. The owner of this schema is the initial @@ -13,4 +13,4 @@ schema are generic names that might occur in user applications, you should be careful if you want to put the information schema in the path. -

    Prev Up Next
    Chapter 36. The Information Schema Home 36.2. Data Types
    \ No newline at end of file +

    Prev Up Next
    Chapter 36. The Information Schema Home 36.2. Data Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-schemata.html postgresql-13-13.12/doc/src/sgml/html/infoschema-schemata.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-schemata.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-schemata.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.42. schemata
    36.42. schemata
    Prev UpChapter 36. The Information SchemaHome Next

    36.42. schemata

    +36.42. schemata

    36.42. schemata
    Prev UpChapter 36. The Information SchemaHome Next

    36.42. schemata

    The view schemata contains all schemas in the current database that the current user has access to (by way of being the owner or having some privilege). @@ -43,4 +43,4 @@

    Applies to a feature not available in PostgreSQL -


    Prev Up Next
    36.41. routines Home 36.43. sequences
    \ No newline at end of file +


    Prev Up Next
    36.41. routines Home 36.43. sequences
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-sequences.html postgresql-13-13.12/doc/src/sgml/html/infoschema-sequences.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-sequences.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-sequences.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.43. sequences
    36.43. sequences
    Prev UpChapter 36. The Information SchemaHome Next

    36.43. sequences

    +36.43. sequences

    36.43. sequences
    Prev UpChapter 36. The Information SchemaHome Next

    36.43. sequences

    The view sequences contains all sequences defined in the current database. Only those sequences are shown that the current user has access to (by way of being the owner or @@ -84,4 +84,4 @@


    Note that in accordance with the SQL standard, the start, minimum, maximum, and increment values are returned as character strings. -

    Prev Up Next
    36.42. schemata Home 36.44. sql_features
    \ No newline at end of file +

    Prev Up Next
    36.42. schemata Home 36.44. sql_features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-features.html postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-features.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-features.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-features.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.44. sql_features
    36.44. sql_features
    Prev UpChapter 36. The Information SchemaHome Next

    36.44. sql_features

    +36.44. sql_features

    36.44. sql_features
    Prev UpChapter 36. The Information SchemaHome Next

    36.44. sql_features

    The table sql_features contains information about which formal features defined in the SQL standard are supported by PostgreSQL. This is the @@ -47,4 +47,4 @@

    Possibly a comment about the supported status of the feature -


    Prev Up Next
    36.43. sequences Home 36.45. sql_implementation_info
    \ No newline at end of file +


    Prev Up Next
    36.43. sequences Home 36.45. sql_implementation_info
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-implementation-info.html postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-implementation-info.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-implementation-info.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-implementation-info.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.45. sql_implementation_info
    36.45. sql_implementation_info
    Prev UpChapter 36. The Information SchemaHome Next

    36.45. sql_implementation_info

    +36.45. sql_implementation_info

    36.45. sql_implementation_info
    Prev UpChapter 36. The Information SchemaHome Next

    36.45. sql_implementation_info

    The table sql_implementation_info contains information about various aspects that are left implementation-defined by the SQL standard. This information is @@ -42,4 +42,4 @@

    Possibly a comment pertaining to the implementation information item -


    Prev Up Next
    36.44. sql_features Home 36.46. sql_parts
    \ No newline at end of file +


    Prev Up Next
    36.44. sql_features Home 36.46. sql_parts
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-parts.html postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-parts.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-parts.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-parts.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.46. sql_parts
    36.46. sql_parts
    Prev UpChapter 36. The Information SchemaHome Next

    36.46. sql_parts

    +36.46. sql_parts

    36.46. sql_parts
    Prev UpChapter 36. The Information SchemaHome Next

    36.46. sql_parts

    The table sql_parts contains information about which of the several parts of the SQL standard are supported by PostgreSQL. @@ -36,4 +36,4 @@

    Possibly a comment about the supported status of the part -


    Prev Up Next
    36.45. sql_implementation_info Home 36.47. sql_sizing
    \ No newline at end of file +


    Prev Up Next
    36.45. sql_implementation_info Home 36.47. sql_sizing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-sizing.html postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-sizing.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-sql-sizing.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-sql-sizing.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.47. sql_sizing
    36.47. sql_sizing
    Prev UpChapter 36. The Information SchemaHome Next

    36.47. sql_sizing

    +36.47. sql_sizing

    36.47. sql_sizing
    Prev UpChapter 36. The Information SchemaHome Next

    36.47. sql_sizing

    The table sql_sizing contains information about various size limits and maximum values in PostgreSQL. This information is @@ -35,4 +35,4 @@

    Possibly a comment pertaining to the sizing item -


    Prev Up Next
    36.46. sql_parts Home 36.48. table_constraints
    \ No newline at end of file +


    Prev Up Next
    36.46. sql_parts Home 36.48. table_constraints
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-table-constraints.html postgresql-13-13.12/doc/src/sgml/html/infoschema-table-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-table-constraints.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-table-constraints.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.48. table_constraints
    36.48. table_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.48. table_constraints

    +36.48. table_constraints

    36.48. table_constraints
    Prev UpChapter 36. The Information SchemaHome Next

    36.48. table_constraints

    The view table_constraints contains all constraints belonging to tables that the current user owns or has some privilege other than SELECT on. @@ -62,4 +62,4 @@ Applies to a feature not available in PostgreSQL (currently always YES) -


    Prev Up Next
    36.47. sql_sizing Home 36.49. table_privileges
    \ No newline at end of file +


    Prev Up Next
    36.47. sql_sizing Home 36.49. table_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-table-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-table-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-table-privileges.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-table-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.49. table_privileges
    36.49. table_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.49. table_privileges

    +36.49. table_privileges

    36.49. table_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.49. table_privileges

    The view table_privileges identifies all privileges granted on tables or views to a currently enabled role or by a currently enabled role. There is one row for each @@ -57,4 +57,4 @@ in the SELECT privilege, so this column shows YES if the privilege is SELECT, else NO. -


    Prev Up Next
    36.48. table_constraints Home 36.50. tables
    \ No newline at end of file +


    Prev Up Next
    36.48. table_constraints Home 36.50. tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-tables.html postgresql-13-13.12/doc/src/sgml/html/infoschema-tables.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-tables.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-tables.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.50. tables
    36.50. tables
    Prev UpChapter 36. The Information SchemaHome Next

    36.50. tables

    +36.50. tables

    36.50. tables
    Prev UpChapter 36. The Information SchemaHome Next

    36.50. tables

    The view tables contains all tables and views defined in the current database. Only those tables and views are shown that the current user has access to (by way of being the @@ -79,4 +79,4 @@

    Not yet implemented -


    Prev Up Next
    36.49. table_privileges Home 36.51. transforms
    \ No newline at end of file +


    Prev Up Next
    36.49. table_privileges Home 36.51. transforms
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-transforms.html postgresql-13-13.12/doc/src/sgml/html/infoschema-transforms.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-transforms.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-transforms.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.51. transforms
    36.51. transforms
    Prev UpChapter 36. The Information SchemaHome Next

    36.51. transforms

    +36.51. transforms

    36.51. transforms
    Prev UpChapter 36. The Information SchemaHome Next

    36.51. transforms

    The view transforms contains information about the transforms defined in the current database. More precisely, it contains a row for each function contained in a transform (the “from SQL” @@ -52,4 +52,4 @@

    FROM SQL or TO SQL -


    Prev Up Next
    36.50. tables Home 36.52. triggered_update_columns
    \ No newline at end of file +


    Prev Up Next
    36.50. tables Home 36.52. triggered_update_columns
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-triggered-update-columns.html postgresql-13-13.12/doc/src/sgml/html/infoschema-triggered-update-columns.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-triggered-update-columns.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-triggered-update-columns.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.52. triggered_update_columns
    36.52. triggered_update_columns
    Prev UpChapter 36. The Information SchemaHome Next

    36.52. triggered_update_columns

    +36.52. triggered_update_columns

    36.52. triggered_update_columns
    Prev UpChapter 36. The Information SchemaHome Next

    36.52. triggered_update_columns

    For triggers in the current database that specify a column list (like UPDATE OF column1, column2), the view triggered_update_columns identifies these @@ -48,4 +48,4 @@

    Name of the column that the trigger is defined on -


    Prev Up Next
    36.51. transforms Home 36.53. triggers
    \ No newline at end of file +


    Prev Up Next
    36.51. transforms Home 36.53. triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-triggers.html postgresql-13-13.12/doc/src/sgml/html/infoschema-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-triggers.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-triggers.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.53. triggers
    36.53. triggers
    Prev UpChapter 36. The Information SchemaHome Next

    36.53. triggers

    +36.53. triggers

    36.53. triggers
    Prev UpChapter 36. The Information SchemaHome Next

    36.53. triggers

    The view triggers contains all triggers defined in the current database on tables and views that the current user owns or has some privilege other than SELECT on. @@ -147,4 +147,4 @@ respectively. That was how they were named in the SQL:1999 standard. The new naming conforms to SQL:2003 and later. -

    Prev Up Next
    36.52. triggered_update_columns Home 36.54. udt_privileges
    \ No newline at end of file +

    Prev Up Next
    36.52. triggered_update_columns Home 36.54. udt_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-udt-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-udt-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-udt-privileges.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-udt-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.54. udt_privileges
    36.54. udt_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.54. udt_privileges

    +36.54. udt_privileges

    36.54. udt_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.54. udt_privileges

    The view udt_privileges identifies USAGE privileges granted on user-defined types to a currently enabled role or by a currently enabled role. There is one row for @@ -47,4 +47,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.53. triggers Home 36.55. usage_privileges
    \ No newline at end of file +


    Prev Up Next
    36.53. triggers Home 36.55. usage_privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-usage-privileges.html postgresql-13-13.12/doc/src/sgml/html/infoschema-usage-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-usage-privileges.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-usage-privileges.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.55. usage_privileges
    36.55. usage_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.55. usage_privileges

    +36.55. usage_privileges

    36.55. usage_privileges
    Prev UpChapter 36. The Information SchemaHome Next

    36.55. usage_privileges

    The view usage_privileges identifies USAGE privileges granted on various kinds of objects to a currently enabled role or by a currently enabled role. @@ -63,4 +63,4 @@

    YES if the privilege is grantable, NO if not -


    Prev Up Next
    36.54. udt_privileges Home 36.56. user_defined_types
    \ No newline at end of file +


    Prev Up Next
    36.54. udt_privileges Home 36.56. user_defined_types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-user-defined-types.html postgresql-13-13.12/doc/src/sgml/html/infoschema-user-defined-types.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-user-defined-types.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-user-defined-types.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.56. user_defined_types
    36.56. user_defined_types
    Prev UpChapter 36. The Information SchemaHome Next

    36.56. user_defined_types

    +36.56. user_defined_types

    36.56. user_defined_types
    Prev UpChapter 36. The Information SchemaHome Next

    36.56. user_defined_types

    The view user_defined_types currently contains all composite types defined in the current database. Only those types are shown that the current user has access to (by way @@ -165,4 +165,4 @@

    Applies to a feature not available in PostgreSQL -


    Prev Up Next
    36.55. usage_privileges Home 36.57. user_mapping_options
    \ No newline at end of file +


    Prev Up Next
    36.55. usage_privileges Home 36.57. user_mapping_options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-user-mapping-options.html postgresql-13-13.12/doc/src/sgml/html/infoschema-user-mapping-options.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-user-mapping-options.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-user-mapping-options.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.57. user_mapping_options
    36.57. user_mapping_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.57. user_mapping_options

    +36.57. user_mapping_options

    36.57. user_mapping_options
    Prev UpChapter 36. The Information SchemaHome Next

    36.57. user_mapping_options

    The view user_mapping_options contains all the options defined for user mappings in the current database. Only those user mappings are shown where the current user has access to @@ -42,4 +42,4 @@ server owner, or the current user is a superuser. The intent is to protect password information stored as user mapping option. -


    Prev Up Next
    36.56. user_defined_types Home 36.58. user_mappings
    \ No newline at end of file +


    Prev Up Next
    36.56. user_defined_types Home 36.58. user_mappings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-user-mappings.html postgresql-13-13.12/doc/src/sgml/html/infoschema-user-mappings.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-user-mappings.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-user-mappings.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.58. user_mappings
    36.58. user_mappings
    Prev UpChapter 36. The Information SchemaHome Next

    36.58. user_mappings

    +36.58. user_mappings

    36.58. user_mappings
    Prev UpChapter 36. The Information SchemaHome Next

    36.58. user_mappings

    The view user_mappings contains all user mappings defined in the current database. Only those user mappings are shown where the current user has access to the corresponding @@ -27,4 +27,4 @@

    Name of the foreign server used by this mapping -


    Prev Up Next
    36.57. user_mapping_options Home 36.59. view_column_usage
    \ No newline at end of file +


    Prev Up Next
    36.57. user_mapping_options Home 36.59. view_column_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-view-column-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-view-column-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-view-column-usage.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-view-column-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.59. view_column_usage
    36.59. view_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.59. view_column_usage

    +36.59. view_column_usage

    36.59. view_column_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.59. view_column_usage

    The view view_column_usage identifies all columns that are used in the query expression of a view (the SELECT statement that defines the view). A @@ -51,4 +51,4 @@

    Name of the column that is used by the view -


    Prev Up Next
    36.58. user_mappings Home 36.60. view_routine_usage
    \ No newline at end of file +


    Prev Up Next
    36.58. user_mappings Home 36.60. view_routine_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-view-routine-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-view-routine-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-view-routine-usage.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-view-routine-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.60. view_routine_usage
    36.60. view_routine_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.60. view_routine_usage

    +36.60. view_routine_usage

    36.60. view_routine_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.60. view_routine_usage

    The view view_routine_usage identifies all routines (functions and procedures) that are used in the query expression of a view (the SELECT statement that @@ -40,4 +40,4 @@

    The “specific name” of the function. See Section 36.41 for more information. -


    Prev Up Next
    36.59. view_column_usage Home 36.61. view_table_usage
    \ No newline at end of file +


    Prev Up Next
    36.59. view_column_usage Home 36.61. view_table_usage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-view-table-usage.html postgresql-13-13.12/doc/src/sgml/html/infoschema-view-table-usage.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-view-table-usage.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-view-table-usage.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.61. view_table_usage
    36.61. view_table_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.61. view_table_usage

    +36.61. view_table_usage

    36.61. view_table_usage
    Prev UpChapter 36. The Information SchemaHome Next

    36.61. view_table_usage

    The view view_table_usage identifies all tables that are used in the query expression of a view (the SELECT statement that defines the view). A @@ -44,4 +44,4 @@

    Name of the table that is used by the view -


    Prev Up Next
    36.60. view_routine_usage Home 36.62. views
    \ No newline at end of file +


    Prev Up Next
    36.60. view_routine_usage Home 36.62. views
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/infoschema-views.html postgresql-13-13.12/doc/src/sgml/html/infoschema-views.html --- postgresql-13-13.11/doc/src/sgml/html/infoschema-views.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/infoschema-views.html 2023-08-07 20:32:17.000000000 +0000 @@ -1,5 +1,5 @@ -36.62. views
    36.62. views
    Prev UpChapter 36. The Information SchemaHome Next

    36.62. views

    +36.62. views

    36.62. views
    Prev UpChapter 36. The Information SchemaHome Next

    36.62. views

    The view views contains all views defined in the current database. Only those views are shown that the current user has access to (by way of being the owner or having some privilege). @@ -67,4 +67,4 @@

    YES if the view has an INSTEAD OF INSERT trigger defined on it, NO if not -


    Prev Up Next
    36.61. view_table_usage Home Part V. Server Programming
    \ No newline at end of file +


    Prev Up Next
    36.61. view_table_usage Home Part V. Server Programming
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-getsource.html postgresql-13-13.12/doc/src/sgml/html/install-getsource.html --- postgresql-13-13.11/doc/src/sgml/html/install-getsource.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-getsource.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,14 +1,14 @@ -16.3. Getting the Source
    16.3. Getting the Source
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.3. Getting the Source

    - The PostgreSQL 13.11 sources can be obtained from the +16.3. Getting the Source

    16.3. Getting the Source
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.3. Getting the Source

    + The PostgreSQL 13.12 sources can be obtained from the download section of our website: https://www.postgresql.org/download/. You - should get a file named postgresql-13.11.tar.gz - or postgresql-13.11.tar.bz2. After + should get a file named postgresql-13.12.tar.gz + or postgresql-13.12.tar.bz2. After you have obtained the file, unpack it: 

    -gunzip postgresql-13.11.tar.gz
-tar xf postgresql-13.11.tar
+gunzip postgresql-13.12.tar.gz
+tar xf postgresql-13.12.tar

    (Use bunzip2 instead of gunzip if you have the .bz2 file. Also, note that most @@ -16,11 +16,11 @@ directly, so you don't really need the separate gunzip or bunzip2 step.) This will create a directory - postgresql-13.11 under the current directory + postgresql-13.12 under the current directory with the PostgreSQL sources. Change into that directory for the rest of the installation procedure.

    You can also get the source directly from the version control repository, see Appendix I. -

    Prev Up Next
    16.2. Requirements Home 16.4. Installation Procedure
    \ No newline at end of file +

    Prev Up Next
    16.2. Requirements Home 16.4. Installation Procedure
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-post.html postgresql-13-13.12/doc/src/sgml/html/install-post.html --- postgresql-13-13.11/doc/src/sgml/html/install-post.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-post.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.5. Post-Installation Setup
    16.5. Post-Installation Setup
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.5. Post-Installation Setup

    16.5.1. Shared Libraries
    16.5.2. Environment Variables

    16.5.1. Shared Libraries

    +16.5. Post-Installation Setup

    16.5. Post-Installation Setup
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.5. Post-Installation Setup

    16.5.1. Shared Libraries
    16.5.2. Environment Variables

    16.5.1. Shared Libraries

    On some systems with shared libraries you need to tell the system how to find the newly installed shared libraries. The systems on which this is @@ -100,4 +100,4 @@ user that plans to use the database sets PGHOST. This is not required, however; the settings can be communicated via command line options to most client programs. -

    Prev Up Next
    16.4. Installation Procedure Home 16.6. Supported Platforms
    \ No newline at end of file +

    Prev Up Next
    16.4. Installation Procedure Home 16.6. Supported Platforms
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-procedure.html postgresql-13-13.12/doc/src/sgml/html/install-procedure.html --- postgresql-13-13.11/doc/src/sgml/html/install-procedure.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-procedure.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.4. Installation Procedure
    16.4. Installation Procedure
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.4. Installation Procedure

    16.4.1. configure Options
    16.4.2. configure Environment Variables

    1. Configuration

      +16.4. Installation Procedure

      16.4. Installation Procedure
      Prev UpChapter 16. Installation from Source CodeHome Next

      16.4. Installation Procedure

      16.4.1. configure Options
      16.4.2. configure Environment Variables

      1. Configuration

        The first step of the installation procedure is to configure the source tree for your system and choose the options you would like. This is done by running the configure script. For a @@ -814,4 +814,4 @@ makefiles. Which to use is a matter of preference, but a common habit among developers is to use PROFILE for one-time flag adjustments, while COPT might be kept set all the time. -

    Prev Up Next
    16.3. Getting the Source Home 16.5. Post-Installation Setup
    \ No newline at end of file +

    Prev Up Next
    16.3. Getting the Source Home 16.5. Post-Installation Setup
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-requirements.html postgresql-13-13.12/doc/src/sgml/html/install-requirements.html --- postgresql-13-13.11/doc/src/sgml/html/install-requirements.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-requirements.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.2. Requirements
    16.2. Requirements
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.2. Requirements

    +16.2. Requirements

    16.2. Requirements
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.2. Requirements

    In general, a modern Unix-compatible platform should be able to run PostgreSQL. The platforms that had received specific testing at the @@ -188,4 +188,4 @@ run the regression tests you will temporarily need up to an extra 300 MB. Use the df command to check free disk space. -

    Prev Up Next
    16.1. Short Version Home 16.3. Getting the Source
    \ No newline at end of file +

    Prev Up Next
    16.1. Short Version Home 16.3. Getting the Source
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-short.html postgresql-13-13.12/doc/src/sgml/html/install-short.html --- postgresql-13-13.11/doc/src/sgml/html/install-short.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-short.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.1. Short Version
    16.1. Short Version
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.1. Short Version

    +16.1. Short Version

    16.1. Short Version
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.1. Short Version

     ./configure
 make
@@ -16,4 +16,4 @@

    The long version is the rest of this chapter. -

    Prev Up Next
    Chapter 16. Installation from Source Code Home 16.2. Requirements
    \ No newline at end of file +

    Prev Up Next
    Chapter 16. Installation from Source Code Home 16.2. Requirements
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-windows-full.html postgresql-13-13.12/doc/src/sgml/html/install-windows-full.html --- postgresql-13-13.11/doc/src/sgml/html/install-windows-full.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-windows-full.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,6 +1,6 @@ 17.1. Building with Visual C++ or the Microsoft Windows SDK
    17.1. Building with Visual C++ or the - Microsoft Windows SDK
    Prev UpChapter 17. Installation from Source Code on WindowsHome Next

    17.1. Building with Visual C++ or the + Microsoft Windows SDKPrev UpChapter 17. Installation from Source Code on WindowsHome Next

    17.1. Building with Visual C++ or the Microsoft Windows SDK

    17.1.1. Requirements
    17.1.2. Special Considerations for 64-Bit Windows
    17.1.3. Building
    17.1.4. Cleaning and Installing
    17.1.5. Running the Regression Tests

    PostgreSQL can be built using the Visual C++ compiler suite from Microsoft. These compilers can be either from Visual Studio, @@ -304,4 +304,4 @@ tar, that would be the command found in PATH.

    -

    Prev Up Next
    Chapter 17. Installation from Source Code on Windows Home Chapter 18. Server Setup and Operation
    \ No newline at end of file +

    Prev Up Next
    Chapter 17. Installation from Source Code on Windows Home Chapter 18. Server Setup and Operation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/install-windows.html postgresql-13-13.12/doc/src/sgml/html/install-windows.html --- postgresql-13-13.11/doc/src/sgml/html/install-windows.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/install-windows.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 17. Installation from Source Code on Windows
    Chapter 17. Installation from Source Code on Windows
    Prev UpPart III. Server AdministrationHome Next

    Chapter 17. Installation from Source Code on Windows

    Table of Contents

    17.1. Building with Visual C++ or the +Chapter 17. Installation from Source Code on Windows
    Chapter 17. Installation from Source Code on Windows
    Prev UpPart III. Server AdministrationHome Next

    Chapter 17. Installation from Source Code on Windows

    Table of Contents

    17.1. Building with Visual C++ or the Microsoft Windows SDK
    17.1.1. Requirements
    17.1.2. Special Considerations for 64-Bit Windows
    17.1.3. Building
    17.1.4. Cleaning and Installing
    17.1.5. Running the Regression Tests

    It is recommended that most users download the binary distribution for Windows, available as a graphical installer package @@ -39,5 +39,5 @@ line editing. The Cygwin build does support command line editing, so it should be used where psql is needed for interactive use on Windows. -

    Prev Up Next
    16.7. Platform-Specific Notes Home 17.1. Building with Visual C++ or the +

    Prev Up Next
    16.7. Platform-Specific Notes Home 17.1. Building with Visual C++ or the Microsoft Windows SDK
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/installation-platform-notes.html postgresql-13-13.12/doc/src/sgml/html/installation-platform-notes.html --- postgresql-13-13.11/doc/src/sgml/html/installation-platform-notes.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/installation-platform-notes.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.7. Platform-Specific Notes
    16.7. Platform-Specific Notes
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.7. Platform-Specific Notes

    16.7.1. AIX
    16.7.2. Cygwin
    16.7.3. macOS
    16.7.4. MinGW/Native Windows
    16.7.5. Solaris

    +16.7. Platform-Specific Notes

    16.7. Platform-Specific Notes
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.7. Platform-Specific Notes

    16.7.1. AIX
    16.7.2. Cygwin
    16.7.3. macOS
    16.7.4. MinGW/Native Windows
    16.7.5. Solaris

    This section documents additional platform-specific issues regarding the installation and setup of PostgreSQL. Be sure to read the installation instructions, and in @@ -307,4 +307,4 @@

    your DTrace installation is too old to handle probes in static functions. You need Solaris 10u4 or newer to use DTrace. -

    Prev Up Next
    16.6. Supported Platforms Home Chapter 17. Installation from Source Code on Windows
    \ No newline at end of file +

    Prev Up Next
    16.6. Supported Platforms Home Chapter 17. Installation from Source Code on Windows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/installation.html postgresql-13-13.12/doc/src/sgml/html/installation.html --- postgresql-13-13.11/doc/src/sgml/html/installation.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/installation.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 16. Installation from Source Code
    Chapter 16. Installation from Source Code
    Prev UpPart III. Server AdministrationHome Next

    Chapter 16. Installation from Source Code

    Table of Contents

    16.1. Short Version
    16.2. Requirements
    16.3. Getting the Source
    16.4. Installation Procedure
    16.4.1. configure Options
    16.4.2. configure Environment Variables
    16.5. Post-Installation Setup
    16.5.1. Shared Libraries
    16.5.2. Environment Variables
    16.6. Supported Platforms
    16.7. Platform-Specific Notes
    16.7.1. AIX
    16.7.2. Cygwin
    16.7.3. macOS
    16.7.4. MinGW/Native Windows
    16.7.5. Solaris

    +Chapter 16. Installation from Source Code

    Chapter 16. Installation from Source Code
    Prev UpPart III. Server AdministrationHome Next

    Chapter 16. Installation from Source Code

    Table of Contents

    16.1. Short Version
    16.2. Requirements
    16.3. Getting the Source
    16.4. Installation Procedure
    16.4.1. configure Options
    16.4.2. configure Environment Variables
    16.5. Post-Installation Setup
    16.5.1. Shared Libraries
    16.5.2. Environment Variables
    16.6. Supported Platforms
    16.7. Platform-Specific Notes
    16.7.1. AIX
    16.7.2. Cygwin
    16.7.3. macOS
    16.7.4. MinGW/Native Windows
    16.7.5. Solaris

    This chapter describes the installation of PostgreSQL using the source code distribution. If you are installing a pre-packaged distribution, @@ -10,4 +10,4 @@ Windows, read this chapter if you intend to build with MinGW or Cygwin; but if you intend to build with Microsoft's Visual C++, see Chapter 17 instead. -

    Prev Up Next
    Part III. Server Administration Home 16.1. Short Version
    \ No newline at end of file +

    Prev Up Next
    Part III. Server Administration Home 16.1. Short Version
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/intagg.html postgresql-13-13.12/doc/src/sgml/html/intagg.html --- postgresql-13-13.11/doc/src/sgml/html/intagg.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/intagg.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.17. intagg
    F.17. intagg
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.17. intagg

    F.17.1. Functions
    F.17.2. Sample Uses

    +F.17. intagg

    F.17. intagg
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.17. intagg

    F.17.1. Functions
    F.17.2. Sample Uses

    The intagg module provides an integer aggregator and an enumerator. intagg is now obsolete, because there are built-in functions that provide a superset of its capabilities. @@ -86,4 +86,4 @@ GROUP BY right ORDER BY count DESC;

    -

    Prev Up Next
    F.16. hstore Home F.18. intarray
    \ No newline at end of file +

    Prev Up Next
    F.16. hstore Home F.18. intarray
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/intarray.html postgresql-13-13.12/doc/src/sgml/html/intarray.html --- postgresql-13-13.11/doc/src/sgml/html/intarray.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/intarray.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.18. intarray
    F.18. intarray
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.18. intarray

    F.18.1. intarray Functions and Operators
    F.18.2. Index Support
    F.18.3. Example
    F.18.4. Benchmark
    F.18.5. Authors

    +F.18. intarray

    F.18. intarray
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.18. intarray

    F.18.1. intarray Functions and Operators
    F.18.2. Index Support
    F.18.3. Example
    F.18.4. Benchmark
    F.18.5. Authors

    The intarray module provides a number of useful functions and operators for manipulating null-free arrays of integers. There is also support for indexed searches using some of the operators. @@ -323,4 +323,4 @@ http://www.sai.msu.su/~megera/postgres/gist/ for additional information. Andrey Oktyabrski did a great work on adding new functions and operations. -

    Prev Up Next
    F.17. intagg Home F.19. isn
    \ No newline at end of file +

    Prev Up Next
    F.17. intagg Home F.19. isn
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/internals.html postgresql-13-13.12/doc/src/sgml/html/internals.html --- postgresql-13-13.11/doc/src/sgml/html/internals.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/internals.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -Part VII. Internals
    Part VII. Internals
    Prev UpPostgreSQL 13.11 DocumentationHome Next

    Part VII. Internals

    +Part VII. Internals

    Part VII. Internals
    Prev UpPostgreSQL 13.12 DocumentationHome Next

    Part VII. Internals

    This part contains assorted information that might be of use to PostgreSQL developers. -

    Table of Contents

    50. Overview of PostgreSQL Internals
    50.1. The Path of a Query
    50.2. How Connections Are Established
    50.3. The Parser Stage
    50.4. The PostgreSQL Rule System
    50.5. Planner/Optimizer
    50.6. Executor
    51. System Catalogs
    51.1. Overview
    51.2. pg_aggregate
    51.3. pg_am
    51.4. pg_amop
    51.5. pg_amproc
    51.6. pg_attrdef
    51.7. pg_attribute
    51.8. pg_authid
    51.9. pg_auth_members
    51.10. pg_cast
    51.11. pg_class
    51.12. pg_collation
    51.13. pg_constraint
    51.14. pg_conversion
    51.15. pg_database
    51.16. pg_db_role_setting
    51.17. pg_default_acl
    51.18. pg_depend
    51.19. pg_description
    51.20. pg_enum
    51.21. pg_event_trigger
    51.22. pg_extension
    51.23. pg_foreign_data_wrapper
    51.24. pg_foreign_server
    51.25. pg_foreign_table
    51.26. pg_index
    51.27. pg_inherits
    51.28. pg_init_privs
    51.29. pg_language
    51.30. pg_largeobject
    51.31. pg_largeobject_metadata
    51.32. pg_namespace
    51.33. pg_opclass
    51.34. pg_operator
    51.35. pg_opfamily
    51.36. pg_partitioned_table
    51.37. pg_policy
    51.38. pg_proc
    51.39. pg_publication
    51.40. pg_publication_rel
    51.41. pg_range
    51.42. pg_replication_origin
    51.43. pg_rewrite
    51.44. pg_seclabel
    51.45. pg_sequence
    51.46. pg_shdepend
    51.47. pg_shdescription
    51.48. pg_shseclabel
    51.49. pg_statistic
    51.50. pg_statistic_ext
    51.51. pg_statistic_ext_data
    51.52. pg_subscription
    51.53. pg_subscription_rel
    51.54. pg_tablespace
    51.55. pg_transform
    51.56. pg_trigger
    51.57. pg_ts_config
    51.58. pg_ts_config_map
    51.59. pg_ts_dict
    51.60. pg_ts_parser
    51.61. pg_ts_template
    51.62. pg_type
    51.63. pg_user_mapping
    51.64. System Views
    51.65. pg_available_extensions
    51.66. pg_available_extension_versions
    51.67. pg_config
    51.68. pg_cursors
    51.69. pg_file_settings
    51.70. pg_group
    51.71. pg_hba_file_rules
    51.72. pg_indexes
    51.73. pg_locks
    51.74. pg_matviews
    51.75. pg_policies
    51.76. pg_prepared_statements
    51.77. pg_prepared_xacts
    51.78. pg_publication_tables
    51.79. pg_replication_origin_status
    51.80. pg_replication_slots
    51.81. pg_roles
    51.82. pg_rules
    51.83. pg_seclabels
    51.84. pg_sequences
    51.85. pg_settings
    51.86. pg_shadow
    51.87. pg_shmem_allocations
    51.88. pg_stats
    51.89. pg_stats_ext
    51.90. pg_tables
    51.91. pg_timezone_abbrevs
    51.92. pg_timezone_names
    51.93. pg_user
    51.94. pg_user_mappings
    51.95. pg_views
    52. Frontend/Backend Protocol
    52.1. Overview
    52.2. Message Flow
    52.3. SASL Authentication
    52.4. Streaming Replication Protocol
    52.5. Logical Streaming Replication Protocol
    52.6. Message Data Types
    52.7. Message Formats
    52.8. Error and Notice Message Fields
    52.9. Logical Replication Message Formats
    52.10. Summary of Changes since Protocol 2.0
    53. PostgreSQL Coding Conventions
    53.1. Formatting
    53.2. Reporting Errors Within the Server
    53.3. Error Message Style Guide
    53.4. Miscellaneous Coding Conventions
    54. Native Language Support
    54.1. For the Translator
    54.2. For the Programmer
    55. Writing a Procedural Language Handler
    56. Writing a Foreign Data Wrapper
    56.1. Foreign Data Wrapper Functions
    56.2. Foreign Data Wrapper Callback Routines
    56.3. Foreign Data Wrapper Helper Functions
    56.4. Foreign Data Wrapper Query Planning
    56.5. Row Locking in Foreign Data Wrappers
    57. Writing a Table Sampling Method
    57.1. Sampling Method Support Functions
    58. Writing a Custom Scan Provider
    58.1. Creating Custom Scan Paths
    58.2. Creating Custom Scan Plans
    58.3. Executing Custom Scans
    59. Genetic Query Optimizer
    59.1. Query Handling as a Complex Optimization Problem
    59.2. Genetic Algorithms
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    59.4. Further Reading
    60. Table Access Method Interface Definition
    61. Index Access Method Interface Definition
    61.1. Basic API Structure for Indexes
    61.2. Index Access Method Functions
    61.3. Index Scanning
    61.4. Index Locking Considerations
    61.5. Index Uniqueness Checks
    61.6. Index Cost Estimation Functions
    62. Generic WAL Records
    63. B-Tree Indexes
    63.1. Introduction
    63.2. Behavior of B-Tree Operator Classes
    63.3. B-Tree Support Functions
    63.4. Implementation
    64. GiST Indexes
    64.1. Introduction
    64.2. Built-in Operator Classes
    64.3. Extensibility
    64.4. Implementation
    64.5. Examples
    65. SP-GiST Indexes
    65.1. Introduction
    65.2. Built-in Operator Classes
    65.3. Extensibility
    65.4. Implementation
    65.5. Examples
    66. GIN Indexes
    66.1. Introduction
    66.2. Built-in Operator Classes
    66.3. Extensibility
    66.4. Implementation
    66.5. GIN Tips and Tricks
    66.6. Limitations
    66.7. Examples
    67. BRIN Indexes
    67.1. Introduction
    67.2. Built-in Operator Classes
    67.3. Extensibility
    68. Hash Indexes
    68.1. Overview
    68.2. Implementation
    69. Database Physical Storage
    69.1. Database File Layout
    69.2. TOAST
    69.3. Free Space Map
    69.4. Visibility Map
    69.5. The Initialization Fork
    69.6. Database Page Layout
    69.7. Heap-Only Tuples (HOT)
    70. System Catalog Declarations and Initial Contents
    70.1. System Catalog Declaration Rules
    70.2. System Catalog Initial Data
    70.3. BKI File Format
    70.4. BKI Commands
    70.5. Structure of the Bootstrap BKI File
    70.6. BKI Example
    71. How the Planner Uses Statistics
    71.1. Row Estimation Examples
    71.2. Multivariate Statistics Examples
    71.3. Planner Statistics and Security
    72. Backup Manifest Format
    72.1. Backup Manifest Top-level Object
    72.2. Backup Manifest File Object
    72.3. Backup Manifest WAL Range Object
    Prev Up Next
    postmaster Home Chapter 50. Overview of PostgreSQL Internals
    \ No newline at end of file +

    Table of Contents

    50. Overview of PostgreSQL Internals
    50.1. The Path of a Query
    50.2. How Connections Are Established
    50.3. The Parser Stage
    50.4. The PostgreSQL Rule System
    50.5. Planner/Optimizer
    50.6. Executor
    51. System Catalogs
    51.1. Overview
    51.2. pg_aggregate
    51.3. pg_am
    51.4. pg_amop
    51.5. pg_amproc
    51.6. pg_attrdef
    51.7. pg_attribute
    51.8. pg_authid
    51.9. pg_auth_members
    51.10. pg_cast
    51.11. pg_class
    51.12. pg_collation
    51.13. pg_constraint
    51.14. pg_conversion
    51.15. pg_database
    51.16. pg_db_role_setting
    51.17. pg_default_acl
    51.18. pg_depend
    51.19. pg_description
    51.20. pg_enum
    51.21. pg_event_trigger
    51.22. pg_extension
    51.23. pg_foreign_data_wrapper
    51.24. pg_foreign_server
    51.25. pg_foreign_table
    51.26. pg_index
    51.27. pg_inherits
    51.28. pg_init_privs
    51.29. pg_language
    51.30. pg_largeobject
    51.31. pg_largeobject_metadata
    51.32. pg_namespace
    51.33. pg_opclass
    51.34. pg_operator
    51.35. pg_opfamily
    51.36. pg_partitioned_table
    51.37. pg_policy
    51.38. pg_proc
    51.39. pg_publication
    51.40. pg_publication_rel
    51.41. pg_range
    51.42. pg_replication_origin
    51.43. pg_rewrite
    51.44. pg_seclabel
    51.45. pg_sequence
    51.46. pg_shdepend
    51.47. pg_shdescription
    51.48. pg_shseclabel
    51.49. pg_statistic
    51.50. pg_statistic_ext
    51.51. pg_statistic_ext_data
    51.52. pg_subscription
    51.53. pg_subscription_rel
    51.54. pg_tablespace
    51.55. pg_transform
    51.56. pg_trigger
    51.57. pg_ts_config
    51.58. pg_ts_config_map
    51.59. pg_ts_dict
    51.60. pg_ts_parser
    51.61. pg_ts_template
    51.62. pg_type
    51.63. pg_user_mapping
    51.64. System Views
    51.65. pg_available_extensions
    51.66. pg_available_extension_versions
    51.67. pg_config
    51.68. pg_cursors
    51.69. pg_file_settings
    51.70. pg_group
    51.71. pg_hba_file_rules
    51.72. pg_indexes
    51.73. pg_locks
    51.74. pg_matviews
    51.75. pg_policies
    51.76. pg_prepared_statements
    51.77. pg_prepared_xacts
    51.78. pg_publication_tables
    51.79. pg_replication_origin_status
    51.80. pg_replication_slots
    51.81. pg_roles
    51.82. pg_rules
    51.83. pg_seclabels
    51.84. pg_sequences
    51.85. pg_settings
    51.86. pg_shadow
    51.87. pg_shmem_allocations
    51.88. pg_stats
    51.89. pg_stats_ext
    51.90. pg_tables
    51.91. pg_timezone_abbrevs
    51.92. pg_timezone_names
    51.93. pg_user
    51.94. pg_user_mappings
    51.95. pg_views
    52. Frontend/Backend Protocol
    52.1. Overview
    52.2. Message Flow
    52.3. SASL Authentication
    52.4. Streaming Replication Protocol
    52.5. Logical Streaming Replication Protocol
    52.6. Message Data Types
    52.7. Message Formats
    52.8. Error and Notice Message Fields
    52.9. Logical Replication Message Formats
    52.10. Summary of Changes since Protocol 2.0
    53. PostgreSQL Coding Conventions
    53.1. Formatting
    53.2. Reporting Errors Within the Server
    53.3. Error Message Style Guide
    53.4. Miscellaneous Coding Conventions
    54. Native Language Support
    54.1. For the Translator
    54.2. For the Programmer
    55. Writing a Procedural Language Handler
    56. Writing a Foreign Data Wrapper
    56.1. Foreign Data Wrapper Functions
    56.2. Foreign Data Wrapper Callback Routines
    56.3. Foreign Data Wrapper Helper Functions
    56.4. Foreign Data Wrapper Query Planning
    56.5. Row Locking in Foreign Data Wrappers
    57. Writing a Table Sampling Method
    57.1. Sampling Method Support Functions
    58. Writing a Custom Scan Provider
    58.1. Creating Custom Scan Paths
    58.2. Creating Custom Scan Plans
    58.3. Executing Custom Scans
    59. Genetic Query Optimizer
    59.1. Query Handling as a Complex Optimization Problem
    59.2. Genetic Algorithms
    59.3. Genetic Query Optimization (GEQO) in PostgreSQL
    59.4. Further Reading
    60. Table Access Method Interface Definition
    61. Index Access Method Interface Definition
    61.1. Basic API Structure for Indexes
    61.2. Index Access Method Functions
    61.3. Index Scanning
    61.4. Index Locking Considerations
    61.5. Index Uniqueness Checks
    61.6. Index Cost Estimation Functions
    62. Generic WAL Records
    63. B-Tree Indexes
    63.1. Introduction
    63.2. Behavior of B-Tree Operator Classes
    63.3. B-Tree Support Functions
    63.4. Implementation
    64. GiST Indexes
    64.1. Introduction
    64.2. Built-in Operator Classes
    64.3. Extensibility
    64.4. Implementation
    64.5. Examples
    65. SP-GiST Indexes
    65.1. Introduction
    65.2. Built-in Operator Classes
    65.3. Extensibility
    65.4. Implementation
    65.5. Examples
    66. GIN Indexes
    66.1. Introduction
    66.2. Built-in Operator Classes
    66.3. Extensibility
    66.4. Implementation
    66.5. GIN Tips and Tricks
    66.6. Limitations
    66.7. Examples
    67. BRIN Indexes
    67.1. Introduction
    67.2. Built-in Operator Classes
    67.3. Extensibility
    68. Hash Indexes
    68.1. Overview
    68.2. Implementation
    69. Database Physical Storage
    69.1. Database File Layout
    69.2. TOAST
    69.3. Free Space Map
    69.4. Visibility Map
    69.5. The Initialization Fork
    69.6. Database Page Layout
    69.7. Heap-Only Tuples (HOT)
    70. System Catalog Declarations and Initial Contents
    70.1. System Catalog Declaration Rules
    70.2. System Catalog Initial Data
    70.3. BKI File Format
    70.4. BKI Commands
    70.5. Structure of the Bootstrap BKI File
    70.6. BKI Example
    71. How the Planner Uses Statistics
    71.1. Row Estimation Examples
    71.2. Multivariate Statistics Examples
    71.3. Planner Statistics and Security
    72. Backup Manifest Format
    72.1. Backup Manifest Top-level Object
    72.2. Backup Manifest File Object
    72.3. Backup Manifest WAL Range Object
    Prev Up Next
    postmaster Home Chapter 50. Overview of PostgreSQL Internals
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/intro-whatis.html postgresql-13-13.12/doc/src/sgml/html/intro-whatis.html --- postgresql-13-13.11/doc/src/sgml/html/intro-whatis.html 2023-05-08 21:33:47.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/intro-whatis.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -1.  What Is PostgreSQL?
    1.  What Is PostgreSQL?
    Prev UpPrefaceHome Next

    1.  What Is PostgreSQL?

    +1.  What Is PostgreSQL?

    1.  What Is PostgreSQL?
    Prev UpPrefaceHome Next

    1.  What Is PostgreSQL?

    PostgreSQL is an object-relational database management system (ORDBMS) based on @@ -23,4 +23,4 @@ PostgreSQL can be used, modified, and distributed by anyone free of charge for any purpose, be it private, commercial, or academic. -

    Prev Up Next
    Preface Home 2. A Brief History of PostgreSQL
    \ No newline at end of file +

    Prev Up Next
    Preface Home 2. A Brief History of PostgreSQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/isn.html postgresql-13-13.12/doc/src/sgml/html/isn.html --- postgresql-13-13.11/doc/src/sgml/html/isn.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/isn.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.19. isn
    F.19. isn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.19. isn

    F.19.1. Data Types
    F.19.2. Casts
    F.19.3. Functions and Operators
    F.19.4. Examples
    F.19.5. Bibliography
    F.19.6. Author

    +F.19. isn

    F.19. isn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.19. isn

    F.19.1. Data Types
    F.19.2. Casts
    F.19.3. Functions and Operators
    F.19.4. Examples
    F.19.5. Bibliography
    F.19.6. Author

    The isn module provides data types for the following international product numbering standards: EAN13, UPC, ISBN (books), ISMN (music), and ISSN (serials). Numbers are validated on input according to a @@ -206,4 +206,4 @@

    This module was inspired by Garrett A. Wollman's isbn_issn code. -

    Prev Up Next
    F.18. intarray Home F.20. lo
    \ No newline at end of file +

    Prev Up Next
    F.18. intarray Home F.20. lo
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/jit-configuration.html postgresql-13-13.12/doc/src/sgml/html/jit-configuration.html --- postgresql-13-13.11/doc/src/sgml/html/jit-configuration.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/jit-configuration.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -31.3. Configuration
    31.3. Configuration
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.3. Configuration

    +31.3. Configuration

    31.3. Configuration
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.3. Configuration

    The configuration variable jit determines whether JIT compilation is enabled or disabled. @@ -14,4 +14,4 @@ For development and debugging purposes a few additional configuration parameters exist, as described in Section 19.17. -

    Prev Up Next
    31.2. When to JIT? Home 31.4. Extensibility
    \ No newline at end of file +

    Prev Up Next
    31.2. When to JIT? Home 31.4. Extensibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/jit-decision.html postgresql-13-13.12/doc/src/sgml/html/jit-decision.html --- postgresql-13-13.11/doc/src/sgml/html/jit-decision.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/jit-decision.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -31.2. When to JIT?
    31.2. When to JIT?
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.2. When to JIT?

    +31.2. When to JIT?

    31.2. When to JIT?
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.2. When to JIT?

    JIT compilation is beneficial primarily for long-running CPU-bound queries. Frequently these will be analytical queries. For short queries the added overhead of performing JIT compilation @@ -68,4 +68,4 @@ As visible here, JIT was used, but inlining and expensive optimization were not. If jit_inline_above_cost or jit_optimize_above_cost were also lowered, that would change. -

    Prev Up Next
    31.1. What Is JIT compilation? Home 31.3. Configuration
    \ No newline at end of file +

    Prev Up Next
    31.1. What Is JIT compilation? Home 31.3. Configuration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/jit-extensibility.html postgresql-13-13.12/doc/src/sgml/html/jit-extensibility.html --- postgresql-13-13.11/doc/src/sgml/html/jit-extensibility.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/jit-extensibility.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -31.4. Extensibility
    31.4. Extensibility
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.4. Extensibility

    31.4.1. Inlining Support for Extensions
    31.4.2. Pluggable JIT Providers

    31.4.1. Inlining Support for Extensions

    +31.4. Extensibility

    31.4. Extensibility
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.4. Extensibility

    31.4.1. Inlining Support for Extensions
    31.4.2. Pluggable JIT Providers

    31.4.1. Inlining Support for Extensions

    PostgreSQL's JIT implementation can inline the bodies of functions of types C and internal, as well as @@ -48,4 +48,4 @@ extern void _PG_jit_provider_init(JitProviderCallbacks *cb);

    -

    Prev Up Next
    31.3. Configuration Home Chapter 32. Regression Tests
    \ No newline at end of file +

    Prev Up Next
    31.3. Configuration Home Chapter 32. Regression Tests
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/jit-reason.html postgresql-13-13.12/doc/src/sgml/html/jit-reason.html --- postgresql-13-13.11/doc/src/sgml/html/jit-reason.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/jit-reason.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -31.1. What Is JIT compilation?
    31.1. What Is JIT compilation?
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.1. What Is JIT compilation?

    31.1.1. JIT Accelerated Operations
    31.1.2. Inlining
    31.1.3. Optimization

    +31.1. What Is JIT compilation?

    31.1. What Is JIT compilation?
    Prev UpChapter 31. Just-in-Time Compilation (JIT)Home Next

    31.1. What Is JIT compilation?

    31.1.1. JIT Accelerated Operations
    31.1.2. Inlining
    31.1.3. Optimization

    Just-in-Time (JIT) compilation is the process of turning some form of interpreted program evaluation into a native program, and doing so at run time. @@ -44,4 +44,4 @@ longer-running queries. See https://llvm.org/docs/Passes.html#transform-passes for more details about optimizations. -

    Prev Up Next
    Chapter 31. Just-in-Time Compilation (JIT) Home 31.2. When to JIT?
    \ No newline at end of file +

    Prev Up Next
    Chapter 31. Just-in-Time Compilation (JIT) Home 31.2. When to JIT?
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/jit.html postgresql-13-13.12/doc/src/sgml/html/jit.html --- postgresql-13-13.11/doc/src/sgml/html/jit.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/jit.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 31. Just-in-Time Compilation (JIT)
    Chapter 31. Just-in-Time Compilation (JIT)
    Prev UpPart III. Server AdministrationHome Next

    Chapter 31. Just-in-Time Compilation (JIT)

    Table of Contents

    31.1. What Is JIT compilation?
    31.1.1. JIT Accelerated Operations
    31.1.2. Inlining
    31.1.3. Optimization
    31.2. When to JIT?
    31.3. Configuration
    31.4. Extensibility
    31.4.1. Inlining Support for Extensions
    31.4.2. Pluggable JIT Providers

    +Chapter 31. Just-in-Time Compilation (JIT)

    Chapter 31. Just-in-Time Compilation (JIT)
    Prev UpPart III. Server AdministrationHome Next

    Chapter 31. Just-in-Time Compilation (JIT)

    Table of Contents

    31.1. What Is JIT compilation?
    31.1.1. JIT Accelerated Operations
    31.1.2. Inlining
    31.1.3. Optimization
    31.2. When to JIT?
    31.3. Configuration
    31.4. Extensibility
    31.4.1. Inlining Support for Extensions
    31.4.2. Pluggable JIT Providers

    This chapter explains what just-in-time compilation is, and how it can be configured in PostgreSQL. -

    Prev Up Next
    30.9. Quick Setup Home 31.1. What Is JIT compilation?
    \ No newline at end of file +

    Prev Up Next
    30.9. Quick Setup Home 31.1. What Is JIT compilation?
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/kernel-resources.html postgresql-13-13.12/doc/src/sgml/html/kernel-resources.html --- postgresql-13-13.11/doc/src/sgml/html/kernel-resources.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/kernel-resources.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.4. Managing Kernel Resources
    18.4. Managing Kernel Resources
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.4. Managing Kernel Resources

    18.4.1. Shared Memory and Semaphores
    18.4.2. systemd RemoveIPC
    18.4.3. Resource Limits
    18.4.4. Linux Memory Overcommit
    18.4.5. Linux Huge Pages

    +18.4. Managing Kernel Resources

    18.4. Managing Kernel Resources
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.4. Managing Kernel Resources

    18.4.1. Shared Memory and Semaphores
    18.4.2. systemd RemoveIPC
    18.4.3. Resource Limits
    18.4.4. Linux Memory Overcommit
    18.4.5. Linux Huge Pages

    PostgreSQL can sometimes exhaust various operating system resource limits, especially when multiple copies of the server are running on the same system, or in very large installations. This section explains @@ -538,4 +538,4 @@ For a detailed description of the Linux huge pages feature have a look at https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt. -

    Prev Up Next
    18.3. Starting the Database Server Home 18.5. Shutting Down the Server
    \ No newline at end of file +

    Prev Up Next
    18.3. Starting the Database Server Home 18.5. Shutting Down the Server
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/largeobjects.html postgresql-13-13.12/doc/src/sgml/html/largeobjects.html --- postgresql-13-13.11/doc/src/sgml/html/largeobjects.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/largeobjects.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 34. Large Objects
    Chapter 34. Large Objects
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 34. Large Objects

    Table of Contents

    34.1. Introduction
    34.2. Implementation Features
    34.3. Client Interfaces
    34.3.1. Creating a Large Object
    34.3.2. Importing a Large Object
    34.3.3. Exporting a Large Object
    34.3.4. Opening an Existing Large Object
    34.3.5. Writing Data to a Large Object
    34.3.6. Reading Data from a Large Object
    34.3.7. Seeking in a Large Object
    34.3.8. Obtaining the Seek Position of a Large Object
    34.3.9. Truncating a Large Object
    34.3.10. Closing a Large Object Descriptor
    34.3.11. Removing a Large Object
    34.4. Server-Side Functions
    34.5. Example Program

    +Chapter 34. Large Objects

    Chapter 34. Large Objects
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 34. Large Objects

    Table of Contents

    34.1. Introduction
    34.2. Implementation Features
    34.3. Client Interfaces
    34.3.1. Creating a Large Object
    34.3.2. Importing a Large Object
    34.3.3. Exporting a Large Object
    34.3.4. Opening an Existing Large Object
    34.3.5. Writing Data to a Large Object
    34.3.6. Reading Data from a Large Object
    34.3.7. Seeking in a Large Object
    34.3.8. Obtaining the Seek Position of a Large Object
    34.3.9. Truncating a Large Object
    34.3.10. Closing a Large Object Descriptor
    34.3.11. Removing a Large Object
    34.4. Server-Side Functions
    34.5. Example Program

    PostgreSQL has a large object facility, which provides stream-style access to user data that is stored in a special large-object structure. Streaming access is useful @@ -14,4 +14,4 @@ equivalent functionality. Other interfaces might use the large object interface internally to provide generic support for large values. This is not described here. -

    Prev Up Next
    33.21. Example Programs Home 34.1. Introduction
    \ No newline at end of file +

    Prev Up Next
    33.21. Example Programs Home 34.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-async.html postgresql-13-13.12/doc/src/sgml/html/libpq-async.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-async.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-async.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.4. Asynchronous Command Processing
    33.4. Asynchronous Command Processing
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.4. Asynchronous Command Processing

    +33.4. Asynchronous Command Processing

    33.4. Asynchronous Command Processing
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.4. Asynchronous Command Processing

    The PQexec function is adequate for submitting commands in normal, synchronous applications. It has a few deficiencies, however, that can be of importance to some users: @@ -328,4 +328,4 @@ messages, and won't read our data until we read its.) Once PQflush returns 0, wait for the socket to be read-ready and then read the response as described above. -

    Prev Up Next
    33.3. Command Execution Functions Home 33.5. Retrieving Query Results Row-by-Row
    \ No newline at end of file +

    Prev Up Next
    33.3. Command Execution Functions Home 33.5. Retrieving Query Results Row-by-Row
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-build.html postgresql-13-13.12/doc/src/sgml/html/libpq-build.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-build.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-build.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.20. Building libpq Programs
    33.20. Building libpq Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.20. Building libpq Programs

    +33.20. Building libpq Programs

    33.20. Building libpq Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.20. Building libpq Programs

    To build (i.e., compile and link) a program using libpq you need to do all of the following things: @@ -103,4 +103,4 @@ This means you forgot the -L option or did not specify the right directory.

    -

    Prev Up Next
    33.19. Behavior in Threaded Programs Home 33.21. Example Programs
    \ No newline at end of file +

    Prev Up Next
    33.19. Behavior in Threaded Programs Home 33.21. Example Programs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-cancel.html postgresql-13-13.12/doc/src/sgml/html/libpq-cancel.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-cancel.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-cancel.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.6. Canceling Queries in Progress
    33.6. Canceling Queries in Progress
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.6. Canceling Queries in Progress

    +33.6. Canceling Queries in Progress

    33.6. Canceling Queries in Progress
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.6. Canceling Queries in Progress

    A client application can request cancellation of a command that is still being processed by the server, using the functions described in this section. @@ -71,4 +71,4 @@ that overwriting the PGconn's error message will mess up the operation currently in progress on the connection.

    -

    Prev Up Next
    33.5. Retrieving Query Results Row-by-Row Home 33.7. The Fast-Path Interface
    \ No newline at end of file +

    Prev Up Next
    33.5. Retrieving Query Results Row-by-Row Home 33.7. The Fast-Path Interface
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-connect.html postgresql-13-13.12/doc/src/sgml/html/libpq-connect.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-connect.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-connect.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -33.1. Database Connection Control Functions
    33.1. Database Connection Control Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.1. Database Connection Control Functions

    33.1.1. Connection Strings
    33.1.2. Parameter Key Words

    +33.1. Database Connection Control Functions

    33.1. Database Connection Control Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.1. Database Connection Control Functions

    33.1.1. Connection Strings
    33.1.2. Parameter Key Words

    The following functions deal with making a connection to a PostgreSQL backend server. An application program can have several backend connections open at @@ -1080,4 +1080,4 @@ attempt had failed. The default value of this parameter, any, regards all connections as acceptable.

    -

    Prev Up Next
    Chapter 33. libpq — C Library Home 33.2. Connection Status Functions
    \ No newline at end of file +

    Prev Up Next
    Chapter 33. libpq — C Library Home 33.2. Connection Status Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-control.html postgresql-13-13.12/doc/src/sgml/html/libpq-control.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-control.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-control.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.10. Control Functions
    33.10. Control Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.10. Control Functions

    +33.10. Control Functions

    33.10. Control Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.10. Control Functions

    These functions control miscellaneous details of libpq's behavior.

    PQclientEncoding

    @@ -109,4 +109,4 @@ 

     void PQuntrace(PGconn *conn);

    -

    Prev Up Next
    33.9. Functions Associated with the COPY Command Home 33.11. Miscellaneous Functions
    \ No newline at end of file +

    Prev Up Next
    33.9. Functions Associated with the COPY Command Home 33.11. Miscellaneous Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-copy.html postgresql-13-13.12/doc/src/sgml/html/libpq-copy.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-copy.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-copy.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.9. Functions Associated with the COPY Command
    33.9. Functions Associated with the COPY Command
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.9. Functions Associated with the COPY Command

    33.9.1. Functions for Sending COPY Data
    33.9.2. Functions for Receiving COPY Data
    33.9.3. Obsolete Functions for COPY

    +33.9. Functions Associated with the COPY Command

    33.9. Functions Associated with the COPY Command
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.9. Functions Associated with the COPY Command

    33.9.1. Functions for Sending COPY Data
    33.9.2. Functions for Receiving COPY Data
    33.9.3. Obsolete Functions for COPY

    The COPY command in PostgreSQL has options to read from or write to the network connection used by libpq. @@ -302,4 +302,4 @@ is done after PQendcopy. This will work correctly only if the COPY is the only SQL command in the command string. -

    Prev Up Next
    33.8. Asynchronous Notification Home 33.10. Control Functions
    \ No newline at end of file +

    Prev Up Next
    33.8. Asynchronous Notification Home 33.10. Control Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-envars.html postgresql-13-13.12/doc/src/sgml/html/libpq-envars.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-envars.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-envars.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.14. Environment Variables
    33.14. Environment Variables
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.14. Environment Variables

    +33.14. Environment Variables

    33.14. Environment Variables
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.14. Environment Variables

    The following environment variables can be used to select default connection parameter values, which will be used by PQconnectdb, PQsetdbLogin and @@ -147,4 +147,4 @@ PGLOCALEDIR sets the directory containing the locale files for message localization.

    -

    Prev Up Next
    33.13. Event System Home 33.15. The Password File
    \ No newline at end of file +

    Prev Up Next
    33.13. Event System Home 33.15. The Password File
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-events.html postgresql-13-13.12/doc/src/sgml/html/libpq-events.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-events.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-events.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.13. Event System
    33.13. Event System
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.13. Event System

    33.13.1. Event Types
    33.13.2. Event Callback Procedure
    33.13.3. Event Support Functions
    33.13.4. Event Example

    +33.13. Event System

    33.13. Event System
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.13. Event System

    33.13.1. Event Types
    33.13.2. Event Callback Procedure
    33.13.3. Event Support Functions
    33.13.4. Event Example

    libpq's event system is designed to notify registered event handlers about interesting libpq events, such as the creation or @@ -423,4 +423,4 @@ return true; /* event processing succeeded */ } -

    Prev Up Next
    33.12. Notice Processing Home 33.14. Environment Variables
    \ No newline at end of file +
    Prev Up Next
    33.12. Notice Processing Home 33.14. Environment Variables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-example.html postgresql-13-13.12/doc/src/sgml/html/libpq-example.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-example.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-example.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.21. Example Programs
    33.21. Example Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.21. Example Programs

    +33.21. Example Programs

    33.21. Example Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.21. Example Programs

    These examples and others can be found in the directory src/test/examples in the source code distribution. @@ -529,4 +529,4 @@ return 0; } -


    Prev Up Next
    33.20. Building libpq Programs Home Chapter 34. Large Objects
    \ No newline at end of file +
    Prev Up Next
    33.20. Building libpq Programs Home Chapter 34. Large Objects
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-exec.html postgresql-13-13.12/doc/src/sgml/html/libpq-exec.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-exec.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-exec.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.3. Command Execution Functions
    33.3. Command Execution Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.3. Command Execution Functions

    33.3.1. Main Functions
    33.3.2. Retrieving Query Result Information
    33.3.3. Retrieving Other Result Information
    33.3.4. Escaping Strings for Inclusion in SQL Commands

    +33.3. Command Execution Functions

    33.3. Command Execution Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.3. Command Execution Functions

    33.3.1. Main Functions
    33.3.2. Retrieving Query Result Information
    33.3.3. Retrieving Other Result Information
    33.3.4. Escaping Strings for Inclusion in SQL Commands

    Once a connection to a database server has been successfully established, the functions described here are used to perform SQL queries and commands. @@ -1045,4 +1045,4 @@ to be “escaped” when received from PQgetvalue. In particular this means there is no need for string quoting considerations, and so no need for a PGconn parameter. -

    Prev Up Next
    33.2. Connection Status Functions Home 33.4. Asynchronous Command Processing
    \ No newline at end of file +

    Prev Up Next
    33.2. Connection Status Functions Home 33.4. Asynchronous Command Processing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-fastpath.html postgresql-13-13.12/doc/src/sgml/html/libpq-fastpath.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-fastpath.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-fastpath.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.7. The Fast-Path Interface
    33.7. The Fast-Path Interface
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.7. The Fast-Path Interface

    +33.7. The Fast-Path Interface

    33.7. The Fast-Path Interface
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.7. The Fast-Path Interface

    PostgreSQL provides a fast-path interface to send simple function calls to the server.

    Tip

    @@ -85,4 +85,4 @@ Note that it is not possible to handle set-valued results when using this interface. Also, the function must be a plain function, not an aggregate, window function, or procedure. -

    Prev Up Next
    33.6. Canceling Queries in Progress Home 33.8. Asynchronous Notification
    \ No newline at end of file +

    Prev Up Next
    33.6. Canceling Queries in Progress Home 33.8. Asynchronous Notification
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-ldap.html postgresql-13-13.12/doc/src/sgml/html/libpq-ldap.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-ldap.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-ldap.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.17. LDAP Lookup of Connection Parameters
    33.17. LDAP Lookup of Connection Parameters
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.17. LDAP Lookup of Connection Parameters

    +33.17. LDAP Lookup of Connection Parameters

    33.17. LDAP Lookup of Connection Parameters
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.17. LDAP Lookup of Connection Parameters

    If libpq has been compiled with LDAP support (option --with-ldap for configure) it is possible to retrieve connection options like host @@ -59,4 +59,4 @@ user=appuser ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)

    -

    Prev Up Next
    33.16. The Connection Service File Home 33.18. SSL Support
    \ No newline at end of file +

    Prev Up Next
    33.16. The Connection Service File Home 33.18. SSL Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-misc.html postgresql-13-13.12/doc/src/sgml/html/libpq-misc.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-misc.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-misc.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.11. Miscellaneous Functions
    33.11. Miscellaneous Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.11. Miscellaneous Functions

    +33.11. Miscellaneous Functions

    33.11. Miscellaneous Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.11. Miscellaneous Functions

    As always, there are some functions that just don't fit anywhere.

    PQfreemem

    Frees memory allocated by libpq. @@ -229,4 +229,4 @@ it cannot be used to detect required functionality in earlier versions, since calling it will create a link dependency on version 9.1 or later. -

    Prev Up Next
    33.10. Control Functions Home 33.12. Notice Processing
    \ No newline at end of file +

    Prev Up Next
    33.10. Control Functions Home 33.12. Notice Processing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-notice-processing.html postgresql-13-13.12/doc/src/sgml/html/libpq-notice-processing.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-notice-processing.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-notice-processing.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.12. Notice Processing
    33.12. Notice Processing
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.12. Notice Processing

    +33.12. Notice Processing

    33.12. Notice Processing
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.12. Notice Processing

    Notice and warning messages generated by the server are not returned by the query execution functions, since they do not imply failure of the query. Instead they are passed to a notice handling function, and @@ -83,4 +83,4 @@ PGconn's current notice handling pointers are copied into the PGresult for possible use by functions like PQgetvalue. -

    Prev Up Next
    33.11. Miscellaneous Functions Home 33.13. Event System
    \ No newline at end of file +

    Prev Up Next
    33.11. Miscellaneous Functions Home 33.13. Event System
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-notify.html postgresql-13-13.12/doc/src/sgml/html/libpq-notify.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-notify.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-notify.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.8. Asynchronous Notification
    33.8. Asynchronous Notification
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.8. Asynchronous Notification

    +33.8. Asynchronous Notification

    33.8. Asynchronous Notification
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.8. Asynchronous Notification

    PostgreSQL offers asynchronous notification via the LISTEN and NOTIFY commands. A client session registers its interest in a particular @@ -70,4 +70,4 @@ to check PQnotifies after each PQgetResult or PQexec, to see if any notifications came in during the processing of the command. -

    Prev Up Next
    33.7. The Fast-Path Interface Home 33.9. Functions Associated with the COPY Command
    \ No newline at end of file +

    Prev Up Next
    33.7. The Fast-Path Interface Home 33.9. Functions Associated with the COPY Command
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-pgpass.html postgresql-13-13.12/doc/src/sgml/html/libpq-pgpass.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-pgpass.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-pgpass.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.15. The Password File
    33.15. The Password File
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.15. The Password File

    +33.15. The Password File

    33.15. The Password File
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.15. The Password File

    The file .pgpass in a user's home directory can contain passwords to be used if the connection requires a password (and no password has been @@ -42,4 +42,4 @@ strict than this, the file will be ignored. On Microsoft Windows, it is assumed that the file is stored in a directory that is secure, so no special permissions check is made. -

    Prev Up Next
    33.14. Environment Variables Home 33.16. The Connection Service File
    \ No newline at end of file +

    Prev Up Next
    33.14. Environment Variables Home 33.16. The Connection Service File
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-pgservice.html postgresql-13-13.12/doc/src/sgml/html/libpq-pgservice.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-pgservice.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-pgservice.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.16. The Connection Service File
    33.16. The Connection Service File
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.16. The Connection Service File

    +33.16. The Connection Service File

    33.16. The Connection Service File
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.16. The Connection Service File

    The connection service file allows libpq connection parameters to be associated with a single service name. That service name can then be specified in a libpq connection string, and the associated settings will be @@ -49,4 +49,4 @@ host somehost, port 5434, user admin, and other parameters as set by environment variables or built-in defaults. -

    Prev Up Next
    33.15. The Password File Home 33.17. LDAP Lookup of Connection Parameters
    \ No newline at end of file +

    Prev Up Next
    33.15. The Password File Home 33.17. LDAP Lookup of Connection Parameters
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-single-row-mode.html postgresql-13-13.12/doc/src/sgml/html/libpq-single-row-mode.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-single-row-mode.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-single-row-mode.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.5. Retrieving Query Results Row-by-Row
    33.5. Retrieving Query Results Row-by-Row
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.5. Retrieving Query Results Row-by-Row

    +33.5. Retrieving Query Results Row-by-Row

    33.5. Retrieving Query Results Row-by-Row
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.5. Retrieving Query Results Row-by-Row

    Ordinarily, libpq collects a SQL command's entire result and returns it to the application as a single PGresult. This can be unworkable for commands @@ -56,4 +56,4 @@ proper transactional behavior, the application must be designed to discard or undo whatever has been done with the previously-processed rows, if the query ultimately fails. -

    Prev Up Next
    33.4. Asynchronous Command Processing Home 33.6. Canceling Queries in Progress
    \ No newline at end of file +

    Prev Up Next
    33.4. Asynchronous Command Processing Home 33.6. Canceling Queries in Progress
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-ssl.html postgresql-13-13.12/doc/src/sgml/html/libpq-ssl.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-ssl.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-ssl.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.18. SSL Support
    33.18. SSL Support
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.18. SSL Support

    33.18.1. Client Verification of Server Certificates
    33.18.2. Client Certificates
    33.18.3. Protection Provided in Different Modes
    33.18.4. SSL Client File Usage
    33.18.5. SSL Library Initialization

    +33.18. SSL Support

    33.18. SSL Support
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.18. SSL Support

    33.18.1. Client Verification of Server Certificates
    33.18.2. Client Certificates
    33.18.3. Protection Provided in Different Modes
    33.18.4. SSL Client File Usage
    33.18.5. SSL Library Initialization

    PostgreSQL has native support for using SSL connections to encrypt client/server communications for increased security. See Section 18.9 for details about the server-side @@ -254,4 +254,4 @@ might be preferable for applications that need to work with older versions of libpq.

    -

    Prev Up Next
    33.17. LDAP Lookup of Connection Parameters Home 33.19. Behavior in Threaded Programs
    \ No newline at end of file +

    Prev Up Next
    33.17. LDAP Lookup of Connection Parameters Home 33.19. Behavior in Threaded Programs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-status.html postgresql-13-13.12/doc/src/sgml/html/libpq-status.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-status.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-status.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -33.2. Connection Status Functions
    33.2. Connection Status Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.2. Connection Status Functions

    +33.2. Connection Status Functions

    33.2. Connection Status Functions
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.2. Connection Status Functions

    These functions can be used to interrogate the status of an existing database connection object.

    Tip

    @@ -415,4 +415,4 @@ PQsslInUse instead, and for more details about the connection, use PQsslAttribute.

    -

    Prev Up Next
    33.1. Database Connection Control Functions Home 33.3. Command Execution Functions
    \ No newline at end of file +

    Prev Up Next
    33.1. Database Connection Control Functions Home 33.3. Command Execution Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq-threading.html postgresql-13-13.12/doc/src/sgml/html/libpq-threading.html --- postgresql-13-13.11/doc/src/sgml/html/libpq-threading.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq-threading.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -33.19. Behavior in Threaded Programs
    33.19. Behavior in Threaded Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.19. Behavior in Threaded Programs

    +33.19. Behavior in Threaded Programs

    33.19. Behavior in Threaded Programs
    Prev UpChapter 33. libpq — C LibraryHome Next

    33.19. Behavior in Threaded Programs

    libpq is reentrant and thread-safe by default. You might need to use special compiler command-line options when you compile your application code. Refer to your @@ -44,4 +44,4 @@ function PQregisterThreadLock in the libpq source code for a way to do cooperative locking between libpq and your application. -

    Prev Up Next
    33.18. SSL Support Home 33.20. Building libpq Programs
    \ No newline at end of file +

    Prev Up Next
    33.18. SSL Support Home 33.20. Building libpq Programs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/libpq.html postgresql-13-13.12/doc/src/sgml/html/libpq.html --- postgresql-13-13.11/doc/src/sgml/html/libpq.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/libpq.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 33. libpq — C Library
    Chapter 33. libpq — C Library
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 33. libpq — C Library

    Table of Contents

    33.1. Database Connection Control Functions
    33.1.1. Connection Strings
    33.1.2. Parameter Key Words
    33.2. Connection Status Functions
    33.3. Command Execution Functions
    33.3.1. Main Functions
    33.3.2. Retrieving Query Result Information
    33.3.3. Retrieving Other Result Information
    33.3.4. Escaping Strings for Inclusion in SQL Commands
    33.4. Asynchronous Command Processing
    33.5. Retrieving Query Results Row-by-Row
    33.6. Canceling Queries in Progress
    33.7. The Fast-Path Interface
    33.8. Asynchronous Notification
    33.9. Functions Associated with the COPY Command
    33.9.1. Functions for Sending COPY Data
    33.9.2. Functions for Receiving COPY Data
    33.9.3. Obsolete Functions for COPY
    33.10. Control Functions
    33.11. Miscellaneous Functions
    33.12. Notice Processing
    33.13. Event System
    33.13.1. Event Types
    33.13.2. Event Callback Procedure
    33.13.3. Event Support Functions
    33.13.4. Event Example
    33.14. Environment Variables
    33.15. The Password File
    33.16. The Connection Service File
    33.17. LDAP Lookup of Connection Parameters
    33.18. SSL Support
    33.18.1. Client Verification of Server Certificates
    33.18.2. Client Certificates
    33.18.3. Protection Provided in Different Modes
    33.18.4. SSL Client File Usage
    33.18.5. SSL Library Initialization
    33.19. Behavior in Threaded Programs
    33.20. Building libpq Programs
    33.21. Example Programs

    +Chapter 33. libpq — C Library

    Chapter 33. libpq — C Library
    Prev UpPart IV. Client InterfacesHome Next

    Chapter 33. libpq — C Library

    Table of Contents

    33.1. Database Connection Control Functions
    33.1.1. Connection Strings
    33.1.2. Parameter Key Words
    33.2. Connection Status Functions
    33.3. Command Execution Functions
    33.3.1. Main Functions
    33.3.2. Retrieving Query Result Information
    33.3.3. Retrieving Other Result Information
    33.3.4. Escaping Strings for Inclusion in SQL Commands
    33.4. Asynchronous Command Processing
    33.5. Retrieving Query Results Row-by-Row
    33.6. Canceling Queries in Progress
    33.7. The Fast-Path Interface
    33.8. Asynchronous Notification
    33.9. Functions Associated with the COPY Command
    33.9.1. Functions for Sending COPY Data
    33.9.2. Functions for Receiving COPY Data
    33.9.3. Obsolete Functions for COPY
    33.10. Control Functions
    33.11. Miscellaneous Functions
    33.12. Notice Processing
    33.13. Event System
    33.13.1. Event Types
    33.13.2. Event Callback Procedure
    33.13.3. Event Support Functions
    33.13.4. Event Example
    33.14. Environment Variables
    33.15. The Password File
    33.16. The Connection Service File
    33.17. LDAP Lookup of Connection Parameters
    33.18. SSL Support
    33.18.1. Client Verification of Server Certificates
    33.18.2. Client Certificates
    33.18.3. Protection Provided in Different Modes
    33.18.4. SSL Client File Usage
    33.18.5. SSL Library Initialization
    33.19. Behavior in Threaded Programs
    33.20. Building libpq Programs
    33.21. Example Programs

    libpq is the C application programmer's interface to PostgreSQL. libpq is a set of library functions that allow @@ -26,4 +26,4 @@ include the header file libpq-fe.h and must link with the libpq library. -

    Prev Up Next
    Part IV. Client Interfaces Home 33.1. Database Connection Control Functions
    \ No newline at end of file +

    Prev Up Next
    Part IV. Client Interfaces Home 33.1. Database Connection Control Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/limits.html postgresql-13-13.12/doc/src/sgml/html/limits.html --- postgresql-13-13.11/doc/src/sgml/html/limits.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/limits.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix K. PostgreSQL Limits
    Appendix K. PostgreSQL Limits
    Prev UpPart VIII. AppendixesHome Next

    Appendix K. PostgreSQL Limits

    +Appendix K. PostgreSQL Limits

    Appendix K. PostgreSQL Limits
    Prev UpPart VIII. AppendixesHome Next

    Appendix K. PostgreSQL Limits

    Table K.1 describes various hard limits of PostgreSQL. However, practical limits, such as performance limitations or available disk space may apply before absolute @@ -24,4 +24,4 @@ column limit. Moreover, although the dropped column values for newly created tuples are internally marked as null in the tuple's null bitmap, the null bitmap also occupies space. -

    Prev Up Next
    J.5. Style Guide Home Appendix L. Acronyms
    \ No newline at end of file +

    Prev Up Next
    J.5. Style Guide Home Appendix L. Acronyms
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo-examplesect.html postgresql-13-13.12/doc/src/sgml/html/lo-examplesect.html --- postgresql-13-13.11/doc/src/sgml/html/lo-examplesect.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo-examplesect.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -34.5. Example Program
    34.5. Example Program
    Prev UpChapter 34. Large ObjectsHome Next

    34.5. Example Program

    +34.5. Example Program

    34.5. Example Program
    Prev UpChapter 34. Large ObjectsHome Next

    34.5. Example Program

    Example 34.1 is a sample program which shows how the large object interface in libpq can be used. Parts of the program are @@ -281,4 +281,4 @@ return 0; } -


    Prev Up Next
    34.4. Server-Side Functions Home Chapter 35. ECPG — Embedded SQL in C
    \ No newline at end of file +
    Prev Up Next
    34.4. Server-Side Functions Home Chapter 35. ECPG — Embedded SQL in C
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo-funcs.html postgresql-13-13.12/doc/src/sgml/html/lo-funcs.html --- postgresql-13-13.11/doc/src/sgml/html/lo-funcs.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo-funcs.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -34.4. Server-Side Functions
    34.4. Server-Side Functions
    Prev UpChapter 34. Large ObjectsHome Next

    34.4. Server-Side Functions

    +34.4. Server-Side Functions

    34.4. Server-Side Functions
    Prev UpChapter 34. Large ObjectsHome Next

    34.4. Server-Side Functions

    Server-side functions tailored for manipulating large objects from SQL are listed in Table 34.1.

    Table 34.1. SQL-Oriented Large Object Functions

    @@ -114,4 +114,4 @@ but the names of the server-side functions differ from the client side interfaces in that they do not contain underscores. You must call these functions as loread and lowrite. -

    Prev Up Next
    34.3. Client Interfaces Home 34.5. Example Program
    \ No newline at end of file +

    Prev Up Next
    34.3. Client Interfaces Home 34.5. Example Program
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo-implementation.html postgresql-13-13.12/doc/src/sgml/html/lo-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/lo-implementation.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo-implementation.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -34.2. Implementation Features
    34.2. Implementation Features
    Prev UpChapter 34. Large ObjectsHome Next

    34.2. Implementation Features

    +34.2. Implementation Features

    34.2. Implementation Features
    Prev UpChapter 34. Large ObjectsHome Next

    34.2. Implementation Features

    The large object implementation breaks large objects up into “chunks” and stores the chunks in rows in the database. A B-tree index guarantees fast @@ -27,4 +27,4 @@ comment on, or change the owner of a large object. To adjust this behavior for compatibility with prior releases, see the lo_compat_privileges run-time parameter. -

    Prev Up Next
    34.1. Introduction Home 34.3. Client Interfaces
    \ No newline at end of file +

    Prev Up Next
    34.1. Introduction Home 34.3. Client Interfaces
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo-interfaces.html postgresql-13-13.12/doc/src/sgml/html/lo-interfaces.html --- postgresql-13-13.11/doc/src/sgml/html/lo-interfaces.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo-interfaces.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -34.3. Client Interfaces
    34.3. Client Interfaces
    Prev UpChapter 34. Large ObjectsHome Next
    Prev Up Next
    34.2. Implementation Features Home 34.4. Server-Side Functions
    \ No newline at end of file +

    Prev Up Next
    34.2. Implementation Features Home 34.4. Server-Side Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo-intro.html postgresql-13-13.12/doc/src/sgml/html/lo-intro.html --- postgresql-13-13.11/doc/src/sgml/html/lo-intro.html 2023-05-08 21:33:57.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo-intro.html 2023-08-07 20:32:16.000000000 +0000 @@ -1,5 +1,5 @@ -34.1. Introduction
    34.1. Introduction
    Prev UpChapter 34. Large ObjectsHome Next

    34.1. Introduction

    +34.1. Introduction

    34.1. Introduction
    Prev UpChapter 34. Large ObjectsHome Next

    34.1. Introduction

    All large objects are stored in a single system table named pg_largeobject. Each large object also has an entry in the system table pg_largeobject_metadata. Large objects can be created, modified, and deleted using a read/write API @@ -15,4 +15,4 @@ most 1 GB. Also, reading and updating portions of a large object can be done efficiently, while most operations on a TOASTed field will read or write the whole value as a unit. -

    Prev Up Next
    Chapter 34. Large Objects Home 34.2. Implementation Features
    \ No newline at end of file +

    Prev Up Next
    Chapter 34. Large Objects Home 34.2. Implementation Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/lo.html postgresql-13-13.12/doc/src/sgml/html/lo.html --- postgresql-13-13.11/doc/src/sgml/html/lo.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/lo.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.20. lo
    F.20. lo
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.20. lo

    F.20.1. Rationale
    F.20.2. How to Use It
    F.20.3. Limitations
    F.20.4. Author

    +F.20. lo

    F.20. lo
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.20. lo

    F.20.1. Rationale
    F.20.2. How to Use It
    F.20.3. Limitations
    F.20.4. Author

    The lo module provides support for managing Large Objects (also called LOs or BLOBs). This includes a data type lo and a trigger lo_manage. @@ -72,4 +72,4 @@ the triggers.

    F.20.4. Author

    Peter Mount -

    Prev Up Next
    F.19. isn Home F.21. ltree
    \ No newline at end of file +

    Prev Up Next
    F.19. isn Home F.21. ltree
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/locale.html postgresql-13-13.12/doc/src/sgml/html/locale.html --- postgresql-13-13.11/doc/src/sgml/html/locale.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/locale.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -23.1. Locale Support
    23.1. Locale Support
    Prev UpChapter 23. LocalizationHome Next

    23.1. Locale Support

    23.1.1. Overview
    23.1.2. Behavior
    23.1.3. Problems

    +23.1. Locale Support

    23.1. Locale Support
    Prev UpChapter 23. LocalizationHome Next

    23.1. Locale Support

    23.1.1. Overview
    23.1.2. Behavior
    23.1.3. Problems

    Locale support refers to an application respecting cultural preferences regarding alphabets, sorting, number formatting, etc. PostgreSQL uses the standard ISO @@ -179,4 +179,4 @@ translated, your assistance would be appreciated. If you want to help, refer to Chapter 54 or write to the developers' mailing list. -

    Prev Up Next
    Chapter 23. Localization Home 23.2. Collation Support
    \ No newline at end of file +

    Prev Up Next
    Chapter 23. Localization Home 23.2. Collation Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/locking-indexes.html postgresql-13-13.12/doc/src/sgml/html/locking-indexes.html --- postgresql-13-13.11/doc/src/sgml/html/locking-indexes.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/locking-indexes.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -13.6. Locking and Indexes
    13.6. Locking and Indexes
    Prev UpChapter 13. Concurrency ControlHome Next

    13.6. Locking and Indexes

    +13.6. Locking and Indexes

    13.6. Locking and Indexes
    Prev UpChapter 13. Concurrency ControlHome Next

    13.6. Locking and Indexes

    Though PostgreSQL provides nonblocking read/write access to table data, nonblocking read/write access is not currently offered for every @@ -39,4 +39,4 @@ applications that need to index scalar data. When dealing with non-scalar data, B-trees are not useful, and GiST, SP-GiST or GIN indexes should be used instead. -

    Prev Up Next
    13.5. Caveats Home Chapter 14. Performance Tips
    \ No newline at end of file +

    Prev Up Next
    13.5. Caveats Home Chapter 14. Performance Tips
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/log-shipping-alternative.html postgresql-13-13.12/doc/src/sgml/html/log-shipping-alternative.html --- postgresql-13-13.11/doc/src/sgml/html/log-shipping-alternative.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/log-shipping-alternative.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -26.4. Alternative Method for Log Shipping
    26.4. Alternative Method for Log Shipping
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.4. Alternative Method for Log Shipping

    26.4.1. Implementation
    26.4.2. Record-Based Log Shipping

    +26.4. Alternative Method for Log Shipping

    26.4. Alternative Method for Log Shipping
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.4. Alternative Method for Log Shipping

    26.4.1. Implementation
    26.4.2. Record-Based Log Shipping

    An alternative to the built-in standby mode described in the previous sections is to use a restore_command that polls the archive location. This was the only option available in versions 8.4 and below. See the @@ -129,4 +129,4 @@ Starting with PostgreSQL version 9.0, you can use streaming replication (see Section 26.2.5) to achieve the same benefits with less effort. -

    Prev Up Next
    26.3. Failover Home 26.5. Hot Standby
    \ No newline at end of file +

    Prev Up Next
    26.3. Failover Home 26.5. Hot Standby
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logfile-maintenance.html postgresql-13-13.12/doc/src/sgml/html/logfile-maintenance.html --- postgresql-13-13.11/doc/src/sgml/html/logfile-maintenance.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logfile-maintenance.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -24.3. Log File Maintenance
    24.3. Log File Maintenance
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.3. Log File Maintenance

    +24.3. Log File Maintenance

    24.3. Log File Maintenance
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.3. Log File Maintenance

    It is a good idea to save the database server's log output somewhere, rather than just discarding it via /dev/null. The log output is invaluable when diagnosing @@ -109,4 +109,4 @@ check_postgres provides Nagios alerts when important messages appear in the log files, as well as detection of many other extraordinary conditions. -

    Prev Up Next
    24.2. Routine Reindexing Home Chapter 25. Backup and Restore
    \ No newline at end of file +

    Prev Up Next
    24.2. Routine Reindexing Home Chapter 25. Backup and Restore
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-architecture.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-architecture.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-architecture.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-architecture.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.5. Architecture
    30.5. Architecture
    Prev UpChapter 30. Logical ReplicationHome Next

    30.5. Architecture

    30.5.1. Initial Snapshot

    +30.5. Architecture

    30.5. Architecture
    Prev UpChapter 30. Logical ReplicationHome Next

    30.5. Architecture

    30.5.1. Initial Snapshot

    Logical replication starts by copying a snapshot of the data on the publisher database. Once that is done, changes on the publisher are sent to the subscriber as they occur in real time. The subscriber applies data @@ -21,9 +21,13 @@ they are received, in correct transactional order.

    The apply process on the subscriber database always runs with - session_replication_role set - to replica, which produces the usual effects on triggers - and constraints. + session_replication_role + set to replica. This means that, by default, + triggers and rules will not fire on a subscriber. Users can optionally choose to + enable triggers and rules on a table using the + ALTER TABLE command + and the ENABLE TRIGGER and ENABLE RULE + clauses.

    The logical replication apply process currently only fires row triggers, not statement triggers. The initial table synchronization, however, is @@ -40,4 +44,4 @@ logical replication. Once the synchronization is done, the control of the replication of the table is given back to the main apply process where the replication continues as normal. -

    Prev Up Next
    30.4. Restrictions Home 30.6. Monitoring
    \ No newline at end of file +

    Prev Up Next
    30.4. Restrictions Home 30.6. Monitoring
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-config.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-config.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-config.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-config.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.8. Configuration Settings
    30.8. Configuration Settings
    Prev UpChapter 30. Logical ReplicationHome Next

    30.8. Configuration Settings

    +30.8. Configuration Settings

    30.8. Configuration Settings
    Prev UpChapter 30. Logical ReplicationHome Next

    30.8. Configuration Settings

    Logical replication requires several configuration options to be set.

    On the publisher side, wal_level must be set to @@ -20,4 +20,4 @@ (max_logical_replication_workers + 1). Note that some extensions and parallel queries also take worker slots from max_worker_processes. -

    Prev Up Next
    30.7. Security Home 30.9. Quick Setup
    \ No newline at end of file +

    Prev Up Next
    30.7. Security Home 30.9. Quick Setup
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-conflicts.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-conflicts.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-conflicts.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-conflicts.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.3. Conflicts
    30.3. Conflicts
    Prev UpChapter 30. Logical ReplicationHome Next

    30.3. Conflicts

    +30.3. Conflicts

    30.3. Conflicts
    Prev UpChapter 30. Logical ReplicationHome Next

    30.3. Conflicts

    Logical replication behaves similarly to normal DML operations in that the data will be updated even if it was changed locally on the subscriber node. If incoming data violates any constraints the replication will @@ -21,4 +21,4 @@ and a position. The current position of origins can be seen in the pg_replication_origin_status system view. -

    Prev Up Next
    30.2. Subscription Home 30.4. Restrictions
    \ No newline at end of file +

    Prev Up Next
    30.2. Subscription Home 30.4. Restrictions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-monitoring.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-monitoring.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-monitoring.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-monitoring.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.6. Monitoring
    30.6. Monitoring
    Prev UpChapter 30. Logical ReplicationHome Next

    30.6. Monitoring

    +30.6. Monitoring

    30.6. Monitoring
    Prev UpChapter 30. Logical ReplicationHome Next

    30.6. Monitoring

    Because logical replication is based on a similar architecture as physical streaming replication, the monitoring on a publication node is similar to monitoring of a @@ -17,4 +17,4 @@ zero rows in this view. If the initial data synchronization of any table is in progress, there will be additional workers for the tables being synchronized. -

    Prev Up Next
    30.5. Architecture Home 30.7. Security
    \ No newline at end of file +

    Prev Up Next
    30.5. Architecture Home 30.7. Security
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-publication.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-publication.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-publication.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-publication.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.1. Publication
    30.1. Publication
    Prev UpChapter 30. Logical ReplicationHome Next

    30.1. Publication

    +30.1. Publication

    30.1. Publication
    Prev UpChapter 30. Logical ReplicationHome Next

    30.1. Publication

    A publication can be defined on any physical replication master. The node where a publication is defined is referred to as publisher. A publication is a set of changes @@ -47,4 +47,4 @@ TABLE and DROP TABLE operations are transactional; so the table will start or stop replicating at the correct snapshot once the transaction has committed. -

    Prev Up Next
    Chapter 30. Logical Replication Home 30.2. Subscription
    \ No newline at end of file +

    Prev Up Next
    Chapter 30. Logical Replication Home 30.2. Subscription
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-quick-setup.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-quick-setup.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-quick-setup.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-quick-setup.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.9. Quick Setup
    30.9. Quick Setup
    Prev UpChapter 30. Logical ReplicationHome Next

    30.9. Quick Setup

    +30.9. Quick Setup

    30.9. Quick Setup
    Prev UpChapter 30. Logical ReplicationHome Next

    30.9. Quick Setup

    First set the configuration options in postgresql.conf: 

     wal_level = logical
@@ -28,4 +28,4 @@
    initial table contents of the tables users and
    departments and then starts replicating
    incremental changes to those tables.
-
    Prev Up Next
    30.8. Configuration Settings Home Chapter 31. Just-in-Time Compilation (JIT)
    \ No newline at end of file +

    Prev Up Next
    30.8. Configuration Settings Home Chapter 31. Just-in-Time Compilation (JIT)
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-restrictions.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-restrictions.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-restrictions.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-restrictions.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.4. Restrictions
    30.4. Restrictions
    Prev UpChapter 30. Logical ReplicationHome Next

    30.4. Restrictions

    +30.4. Restrictions

    30.4. Restrictions
    Prev UpChapter 30. Logical ReplicationHome Next

    30.4. Restrictions

    Logical replication currently has the following restrictions or missing functionality. These might be addressed in future releases.

    • @@ -54,4 +54,4 @@ using the identity and schema of the partitioned root table instead of that of the individual leaf partitions in which the changes actually originate (see CREATE PUBLICATION). -

    Prev Up Next
    30.3. Conflicts Home 30.5. Architecture
    \ No newline at end of file +

    Prev Up Next
    30.3. Conflicts Home 30.5. Architecture
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-security.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-security.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-security.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-security.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.7. Security
    30.7. Security
    Prev UpChapter 30. Logical ReplicationHome Next

    30.7. Security

    +30.7. Security

    30.7. Security
    Prev UpChapter 30. Logical ReplicationHome Next

    30.7. Security

    A user able to modify the schema of subscriber-side tables can execute arbitrary code as a superuser. Limit ownership and TRIGGER privilege on such tables to roles that @@ -38,4 +38,4 @@ Privileges are only checked once at the start of a replication connection. They are not re-checked as each change record is read from the publisher, nor are they re-checked for each change when applied. -

    Prev Up Next
    30.6. Monitoring Home 30.8. Configuration Settings
    \ No newline at end of file +

    Prev Up Next
    30.6. Monitoring Home 30.8. Configuration Settings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication-subscription.html postgresql-13-13.12/doc/src/sgml/html/logical-replication-subscription.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication-subscription.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication-subscription.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -30.2. Subscription
    30.2. Subscription
    Prev UpChapter 30. Logical ReplicationHome Next

    30.2. Subscription

    30.2.1. Replication Slot Management

    +30.2. Subscription

    30.2. Subscription
    Prev UpChapter 30. Logical ReplicationHome Next

    30.2. Subscription

    30.2.1. Replication Slot Management

    A subscription is the downstream side of logical replication. The node where a subscription is defined is referred to as the subscriber. A subscription defines the connection @@ -96,4 +96,4 @@ eventually cause the disk to fill up. Such cases should be carefully investigated.

    -

    Prev Up Next
    30.1. Publication Home 30.3. Conflicts
    \ No newline at end of file +

    Prev Up Next
    30.1. Publication Home 30.3. Conflicts
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logical-replication.html postgresql-13-13.12/doc/src/sgml/html/logical-replication.html --- postgresql-13-13.11/doc/src/sgml/html/logical-replication.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logical-replication.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 30. Logical Replication
    Chapter 30. Logical Replication
    Prev UpPart III. Server AdministrationHome Next

    Chapter 30. Logical Replication

    Table of Contents

    30.1. Publication
    30.2. Subscription
    30.2.1. Replication Slot Management
    30.3. Conflicts
    30.4. Restrictions
    30.5. Architecture
    30.5.1. Initial Snapshot
    30.6. Monitoring
    30.7. Security
    30.8. Configuration Settings
    30.9. Quick Setup

    +Chapter 30. Logical Replication

    Chapter 30. Logical Replication
    Prev UpPart III. Server AdministrationHome Next

    Chapter 30. Logical Replication

    Table of Contents

    30.1. Publication
    30.2. Subscription
    30.2.1. Replication Slot Management
    30.3. Conflicts
    30.4. Restrictions
    30.5. Architecture
    30.5.1. Initial Snapshot
    30.6. Monitoring
    30.7. Security
    30.8. Configuration Settings
    30.9. Quick Setup

    Logical replication is a method of replicating data objects and their changes, based upon their replication identity (usually a primary key). We use the term logical in contrast to physical replication, which uses exact @@ -52,4 +52,4 @@ application, there will be no conflicts from a single subscription. On the other hand, if there are other writes done either by an application or by other subscribers to the same set of tables, conflicts can arise. -

    Prev Up Next
    29.5. WAL Internals Home 30.1. Publication
    \ No newline at end of file +

    Prev Up Next
    29.5. WAL Internals Home 30.1. Publication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-catalogs.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-catalogs.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-catalogs.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-catalogs.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.5. System Catalogs Related to Logical Decoding
    48.5. System Catalogs Related to Logical Decoding
    Prev UpChapter 48. Logical DecodingHome Next

    48.5. System Catalogs Related to Logical Decoding

    +48.5. System Catalogs Related to Logical Decoding

    48.5. System Catalogs Related to Logical Decoding
    Prev UpChapter 48. Logical DecodingHome Next
    Prev Up Next
    48.4. Logical Decoding SQL Interface Home 48.6. Logical Decoding Output Plugins
    \ No newline at end of file +

    Prev Up Next
    48.4. Logical Decoding SQL Interface Home 48.6. Logical Decoding Output Plugins
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-example.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-example.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-example.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-example.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.1. Logical Decoding Examples
    48.1. Logical Decoding Examples
    Prev UpChapter 48. Logical DecodingHome Next

    48.1. Logical Decoding Examples

    +48.1. Logical Decoding Examples

    48.1. Logical Decoding Examples
    Prev UpChapter 48. Logical DecodingHome Next

    48.1. Logical Decoding Examples

    The following example demonstrates controlling logical decoding using the SQL interface.

    @@ -116,4 +116,4 @@ COMMIT 693 Control+C $ pg_recvlogical -d postgres --slot=test --drop-slot -

    Prev Up Next
    Chapter 48. Logical Decoding Home 48.2. Logical Decoding Concepts
    \ No newline at end of file +
    Prev Up Next
    Chapter 48. Logical Decoding Home 48.2. Logical Decoding Concepts
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-explanation.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-explanation.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-explanation.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-explanation.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.2. Logical Decoding Concepts
    48.2. Logical Decoding Concepts
    Prev UpChapter 48. Logical DecodingHome Next

    48.2. Logical Decoding Concepts

    48.2.1. Logical Decoding
    48.2.2. Replication Slots
    48.2.3. Output Plugins
    48.2.4. Exported Snapshots

    48.2.1. Logical Decoding

    +48.2. Logical Decoding Concepts

    48.2. Logical Decoding Concepts
    Prev UpChapter 48. Logical DecodingHome Next

    48.2. Logical Decoding Concepts

    48.2.1. Logical Decoding
    48.2.2. Replication Slots
    48.2.3. Output Plugins
    48.2.4. Exported Snapshots

    48.2.1. Logical Decoding

    Logical decoding is the process of extracting all persistent changes to a database's tables into a coherent, easy to understand format which can be interpreted without detailed knowledge of the database's internal @@ -73,4 +73,4 @@ fail when connected to a hot standby. Applications that do not require snapshot export may suppress it with the NOEXPORT_SNAPSHOT option. -

    Prev Up Next
    48.1. Logical Decoding Examples Home 48.3. Streaming Replication Protocol Interface
    \ No newline at end of file +

    Prev Up Next
    48.1. Logical Decoding Examples Home 48.3. Streaming Replication Protocol Interface
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-output-plugin.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-output-plugin.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-output-plugin.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-output-plugin.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.6. Logical Decoding Output Plugins
    48.6. Logical Decoding Output Plugins
    Prev UpChapter 48. Logical DecodingHome Next
    Prev Up Next
    48.5. System Catalogs Related to Logical Decoding Home 48.7. Logical Decoding Output Writers
    \ No newline at end of file +

    Prev Up Next
    48.5. System Catalogs Related to Logical Decoding Home 48.7. Logical Decoding Output Writers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-sql.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-sql.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-sql.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-sql.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.4. Logical Decoding SQL Interface
    48.4. Logical Decoding SQL Interface
    Prev UpChapter 48. Logical DecodingHome Next

    48.4. Logical Decoding SQL Interface

    +48.4. Logical Decoding SQL Interface

    48.4. Logical Decoding SQL Interface
    Prev UpChapter 48. Logical DecodingHome Next

    48.4. Logical Decoding SQL Interface

    See Section 9.27.6 for detailed documentation on the SQL-level API for interacting with logical decoding.

    @@ -7,4 +7,4 @@ only supported on replication slots used over the streaming replication interface. The function interface and additional, non-core interfaces do not support synchronous replication. -

    Prev Up Next
    48.3. Streaming Replication Protocol Interface Home 48.5. System Catalogs Related to Logical Decoding
    \ No newline at end of file +

    Prev Up Next
    48.3. Streaming Replication Protocol Interface Home 48.5. System Catalogs Related to Logical Decoding
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-synchronous.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-synchronous.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-synchronous.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-synchronous.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.8. Synchronous Replication Support for Logical Decoding
    48.8. Synchronous Replication Support for Logical Decoding
    Prev UpChapter 48. Logical DecodingHome Next

    48.8. Synchronous Replication Support for Logical Decoding

    48.8.1. Overview
    48.8.2. Caveats

    48.8.1. Overview

    +48.8. Synchronous Replication Support for Logical Decoding

    48.8. Synchronous Replication Support for Logical Decoding
    Prev UpChapter 48. Logical DecodingHome Next

    48.8. Synchronous Replication Support for Logical Decoding

    48.8.1. Overview
    48.8.2. Caveats

    48.8.1. Overview

    Logical decoding can be used to build synchronous replication solutions with the same user interface as synchronous @@ -38,4 +38,4 @@ Note that these commands that can cause deadlock apply to not only explicitly indicated system catalog tables above but also to any other [user] catalog table. -

    Prev Up Next
    48.7. Logical Decoding Output Writers Home Chapter 49. Replication Progress Tracking
    \ No newline at end of file +

    Prev Up Next
    48.7. Logical Decoding Output Writers Home Chapter 49. Replication Progress Tracking
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-walsender.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-walsender.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-walsender.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-walsender.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -48.3. Streaming Replication Protocol Interface
    48.3. Streaming Replication Protocol Interface
    Prev UpChapter 48. Logical DecodingHome Next

    48.3. Streaming Replication Protocol Interface

    +48.3. Streaming Replication Protocol Interface

    48.3. Streaming Replication Protocol Interface
    Prev UpChapter 48. Logical DecodingHome Next

    48.3. Streaming Replication Protocol Interface

    The commands

    • CREATE_REPLICATION_SLOT slot_name LOGICAL output_plugin

    • DROP_REPLICATION_SLOT slot_name [ WAIT ]

    • START_REPLICATION SLOT slot_name LOGICAL ...

    are used to create, drop, and stream changes from a replication @@ -10,4 +10,4 @@ The command pg_recvlogical can be used to control logical decoding over a streaming replication connection. (It uses these commands internally.) -

    Prev Up Next
    48.2. Logical Decoding Concepts Home 48.4. Logical Decoding SQL Interface
    \ No newline at end of file +

    Prev Up Next
    48.2. Logical Decoding Concepts Home 48.4. Logical Decoding SQL Interface
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-writer.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-writer.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding-writer.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding-writer.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,9 +1,9 @@ -48.7. Logical Decoding Output Writers
    48.7. Logical Decoding Output Writers
    Prev UpChapter 48. Logical DecodingHome Next

    48.7. Logical Decoding Output Writers

    +48.7. Logical Decoding Output Writers

    48.7. Logical Decoding Output Writers
    Prev UpChapter 48. Logical DecodingHome Next

    48.7. Logical Decoding Output Writers

    It is possible to add more output methods for logical decoding. For details, see src/backend/replication/logical/logicalfuncs.c. Essentially, three functions need to be provided: one to read WAL, one to prepare writing output, and one to write the output (see Section 48.6.5). -

    Prev Up Next
    48.6. Logical Decoding Output Plugins Home 48.8. Synchronous Replication Support for Logical Decoding
    \ No newline at end of file +

    Prev Up Next
    48.6. Logical Decoding Output Plugins Home 48.8. Synchronous Replication Support for Logical Decoding
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/logicaldecoding.html postgresql-13-13.12/doc/src/sgml/html/logicaldecoding.html --- postgresql-13-13.11/doc/src/sgml/html/logicaldecoding.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/logicaldecoding.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 48. Logical Decoding
    Chapter 48. Logical Decoding
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 48. Logical Decoding

    Table of Contents

    48.1. Logical Decoding Examples
    48.2. Logical Decoding Concepts
    48.2.1. Logical Decoding
    48.2.2. Replication Slots
    48.2.3. Output Plugins
    48.2.4. Exported Snapshots
    48.3. Streaming Replication Protocol Interface
    48.4. Logical Decoding SQL Interface
    48.5. System Catalogs Related to Logical Decoding
    48.6. Logical Decoding Output Plugins
    48.6.1. Initialization Function
    48.6.2. Capabilities
    48.6.3. Output Modes
    48.6.4. Output Plugin Callbacks
    48.6.5. Functions for Producing Output
    48.7. Logical Decoding Output Writers
    48.8. Synchronous Replication Support for Logical Decoding
    48.8.1. Overview
    48.8.2. Caveats

    +Chapter 48. Logical Decoding

    Chapter 48. Logical Decoding
    Prev UpPart V. Server ProgrammingHome Next
    Prev Up Next
    Chapter 47. Background Worker Processes Home 48.1. Logical Decoding Examples
    \ No newline at end of file +

    Prev Up Next
    Chapter 47. Background Worker Processes Home 48.1. Logical Decoding Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ltree.html postgresql-13-13.12/doc/src/sgml/html/ltree.html --- postgresql-13-13.11/doc/src/sgml/html/ltree.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ltree.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.21. ltree
    F.21. ltree
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.21. ltree

    F.21.1. Definitions
    F.21.2. Operators and Functions
    F.21.3. Indexes
    F.21.4. Example
    F.21.5. Transforms
    F.21.6. Authors

    +F.21. ltree

    F.21. ltree
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.21. ltree

    F.21.1. Definitions
    F.21.2. Operators and Functions
    F.21.3. Indexes
    F.21.4. Example
    F.21.5. Transforms
    F.21.6. Authors

    This module implements a data type ltree for representing labels of data stored in a hierarchical tree-like structure. Extensive facilities for searching through label trees are provided. @@ -583,4 +583,4 @@ http://www.sai.msu.su/~megera/postgres/gist/ for additional information. Authors would like to thank Eugeny Rodichev for helpful discussions. Comments and bug reports are welcome. -

    Prev Up Next
    F.20. lo Home F.22. pageinspect
    \ No newline at end of file +

    Prev Up Next
    F.20. lo Home F.22. pageinspect
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/maintenance.html postgresql-13-13.12/doc/src/sgml/html/maintenance.html --- postgresql-13-13.11/doc/src/sgml/html/maintenance.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/maintenance.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 24. Routine Database Maintenance Tasks
    Chapter 24. Routine Database Maintenance Tasks
    Prev UpPart III. Server AdministrationHome Next

    Chapter 24. Routine Database Maintenance Tasks

    Table of Contents

    24.1. Routine Vacuuming
    24.1.1. Vacuuming Basics
    24.1.2. Recovering Disk Space
    24.1.3. Updating Planner Statistics
    24.1.4. Updating the Visibility Map
    24.1.5. Preventing Transaction ID Wraparound Failures
    24.1.6. The Autovacuum Daemon
    24.2. Routine Reindexing
    24.3. Log File Maintenance

    +Chapter 24. Routine Database Maintenance Tasks

    Chapter 24. Routine Database Maintenance Tasks
    Prev UpPart III. Server AdministrationHome Next

    Chapter 24. Routine Database Maintenance Tasks

    Table of Contents

    24.1. Routine Vacuuming
    24.1.1. Vacuuming Basics
    24.1.2. Recovering Disk Space
    24.1.3. Updating Planner Statistics
    24.1.4. Updating the Visibility Map
    24.1.5. Preventing Transaction ID Wraparound Failures
    24.1.6. The Autovacuum Daemon
    24.2. Routine Reindexing
    24.3. Log File Maintenance

    PostgreSQL, like any database software, requires that certain tasks be performed regularly to achieve optimum performance. The tasks discussed here are required, but they @@ -34,4 +34,4 @@ to some other database management systems. Nonetheless, appropriate attention to these tasks will go far towards ensuring a pleasant and productive experience with the system. -

    Prev Up Next
    23.3. Character Set Support Home 24.1. Routine Vacuuming
    \ No newline at end of file +

    Prev Up Next
    23.3. Character Set Support Home 24.1. Routine Vacuuming
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-config.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-config.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-config.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-config.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -22.4. Database Configuration
    22.4. Database Configuration
    Prev UpChapter 22. Managing DatabasesHome Next

    22.4. Database Configuration

    +22.4. Database Configuration

    22.4. Database Configuration
    Prev UpChapter 22. Managing DatabasesHome Next

    22.4. Database Configuration

    Recall from Chapter 19 that the PostgreSQL server provides a large number of run-time configuration variables. You can set database-specific @@ -22,4 +22,4 @@ will only be the default. To undo any such setting, use ALTER DATABASE dbname RESET varname. -

    Prev Up Next
    22.3. Template Databases Home 22.5. Destroying a Database
    \ No newline at end of file +

    Prev Up Next
    22.3. Template Databases Home 22.5. Destroying a Database
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-createdb.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-createdb.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-createdb.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-createdb.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -22.2. Creating a Database
    22.2. Creating a Database
    Prev UpChapter 22. Managing DatabasesHome Next

    22.2. Creating a Database

    +22.2. Creating a Database

    22.2. Creating a Database
    Prev UpChapter 22. Managing DatabasesHome Next

    22.2. Creating a Database

    In order to create a database, the PostgreSQL server must be up and running (see Section 18.3).

    @@ -70,4 +70,4 @@ from the shell. Only the superuser is allowed to create a database for someone else (that is, for a role you are not a member of). -

    Prev Up Next
    22.1. Overview Home 22.3. Template Databases
    \ No newline at end of file +

    Prev Up Next
    22.1. Overview Home 22.3. Template Databases
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-dropdb.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-dropdb.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-dropdb.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-dropdb.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -22.5. Destroying a Database
    22.5. Destroying a Database
    Prev UpChapter 22. Managing DatabasesHome Next

    22.5. Destroying a Database

    +22.5. Destroying a Database

    22.5. Destroying a Database
    Prev UpChapter 22. Managing DatabasesHome Next

    22.5. Destroying a Database

    Databases are destroyed with the command DROP DATABASE: 

    @@ -25,4 +25,4 @@

    (Unlike createdb, it is not the default action to drop the database with the current user name.) -

    Prev Up Next
    22.4. Database Configuration Home 22.6. Tablespaces
    \ No newline at end of file +

    Prev Up Next
    22.4. Database Configuration Home 22.6. Tablespaces
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-overview.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-overview.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-overview.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-overview.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -22.1. Overview
    22.1. Overview
    Prev UpChapter 22. Managing DatabasesHome Next

    22.1. Overview

    +22.1. Overview

    22.1. Overview
    Prev UpChapter 22. Managing DatabasesHome Next

    22.1. Overview

    A small number of objects, like role, database, and tablespace names, are defined at the cluster level and stored in the pg_global tablespace. Inside the cluster are @@ -56,4 +56,4 @@

    Note

    The SQL standard calls databases “catalogs”, but there is no difference in practice. -

    Prev Up Next
    Chapter 22. Managing Databases Home 22.2. Creating a Database
    \ No newline at end of file +

    Prev Up Next
    Chapter 22. Managing Databases Home 22.2. Creating a Database
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-tablespaces.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-tablespaces.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-tablespaces.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-tablespaces.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -22.6. Tablespaces
    22.6. Tablespaces
    Prev UpChapter 22. Managing DatabasesHome Next

    22.6. Tablespaces

    +22.6. Tablespaces

    22.6. Tablespaces
    Prev UpChapter 22. Managing DatabasesHome Next

    22.6. Tablespaces

    Tablespaces in PostgreSQL allow database administrators to define locations in the file system where the files representing database objects can be stored. Once created, a tablespace can be referred @@ -129,4 +129,4 @@ and earlier you will also need to update the pg_tablespace catalog with the new locations. (If you do not, pg_dump will continue to output the old tablespace locations.) -

    Prev Up Next
    22.5. Destroying a Database Home Chapter 23. Localization
    \ No newline at end of file +

    Prev Up Next
    22.5. Destroying a Database Home Chapter 23. Localization
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/manage-ag-templatedbs.html postgresql-13-13.12/doc/src/sgml/html/manage-ag-templatedbs.html --- postgresql-13-13.11/doc/src/sgml/html/manage-ag-templatedbs.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/manage-ag-templatedbs.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -22.3. Template Databases
    22.3. Template Databases
    Prev UpChapter 22. Managing DatabasesHome Next

    22.3. Template Databases

    +22.3. Template Databases

    22.3. Template Databases
    Prev UpChapter 22. Managing DatabasesHome Next

    22.3. Template Databases

    CREATE DATABASE actually works by copying an existing database. By default, it copies the standard system database named template1. Thus that @@ -85,4 +85,4 @@ cluster is initialized. This database is meant as a default database for users and applications to connect to. It is simply a copy of template1 and can be dropped and recreated if necessary. -

    Prev Up Next
    22.2. Creating a Database Home 22.4. Database Configuration
    \ No newline at end of file +

    Prev Up Next
    22.2. Creating a Database Home 22.4. Database Configuration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/managing-databases.html postgresql-13-13.12/doc/src/sgml/html/managing-databases.html --- postgresql-13-13.11/doc/src/sgml/html/managing-databases.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/managing-databases.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,9 +1,9 @@ -Chapter 22. Managing Databases
    Chapter 22. Managing Databases
    Prev UpPart III. Server AdministrationHome Next

    Chapter 22. Managing Databases

    Table of Contents

    22.1. Overview
    22.2. Creating a Database
    22.3. Template Databases
    22.4. Database Configuration
    22.5. Destroying a Database
    22.6. Tablespaces

    +Chapter 22. Managing Databases

    Chapter 22. Managing Databases
    Prev UpPart III. Server AdministrationHome Next

    Chapter 22. Managing Databases

    Table of Contents

    22.1. Overview
    22.2. Creating a Database
    22.3. Template Databases
    22.4. Database Configuration
    22.5. Destroying a Database
    22.6. Tablespaces

    Every instance of a running PostgreSQL server manages one or more databases. Databases are therefore the topmost hierarchical level for organizing SQL objects (“database objects”). This chapter describes the properties of databases, and how to create, manage, and destroy them. -

    Prev Up Next
    21.6. Function Security Home 22.1. Overview
    \ No newline at end of file +

    Prev Up Next
    21.6. Function Security Home 22.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/monitoring-locks.html postgresql-13-13.12/doc/src/sgml/html/monitoring-locks.html --- postgresql-13-13.11/doc/src/sgml/html/monitoring-locks.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/monitoring-locks.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -27.3. Viewing Locks
    27.3. Viewing Locks
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.3. Viewing Locks

    +27.3. Viewing Locks

    27.3. Viewing Locks
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.3. Viewing Locks

    Another useful tool for monitoring database activity is the pg_locks system table. It allows the database administrator to view information about the outstanding @@ -25,4 +25,4 @@ Section 51.73. For more information on locking and managing concurrency with PostgreSQL, refer to Chapter 13. -

    Prev Up Next
    27.2. The Statistics Collector Home 27.4. Progress Reporting
    \ No newline at end of file +

    Prev Up Next
    27.2. The Statistics Collector Home 27.4. Progress Reporting
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/monitoring-ps.html postgresql-13-13.12/doc/src/sgml/html/monitoring-ps.html --- postgresql-13-13.11/doc/src/sgml/html/monitoring-ps.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/monitoring-ps.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -27.1. Standard Unix Tools
    27.1. Standard Unix Tools
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.1. Standard Unix Tools

    +27.1. Standard Unix Tools

    27.1. Standard Unix Tools
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.1. Standard Unix Tools

    On most Unix platforms, PostgreSQL modifies its command title as reported by ps, so that individual server processes can readily be identified. A sample display is @@ -76,4 +76,4 @@ server process. If you fail to do all three things, the ps output for each server process will be the original postgres command line. -

    Prev Up Next
    Chapter 27. Monitoring Database Activity Home 27.2. The Statistics Collector
    \ No newline at end of file +

    Prev Up Next
    Chapter 27. Monitoring Database Activity Home 27.2. The Statistics Collector
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/monitoring-stats.html postgresql-13-13.12/doc/src/sgml/html/monitoring-stats.html --- postgresql-13-13.11/doc/src/sgml/html/monitoring-stats.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/monitoring-stats.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -27.2. The Statistics Collector
    27.2. The Statistics Collector
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.2. The Statistics Collector

    27.2.1. Statistics Collection Configuration
    27.2.2. Viewing Statistics
    27.2.3. pg_stat_activity
    27.2.4. pg_stat_replication
    27.2.5. pg_stat_wal_receiver
    27.2.6. pg_stat_subscription
    27.2.7. pg_stat_ssl
    27.2.8. pg_stat_gssapi
    27.2.9. pg_stat_archiver
    27.2.10. pg_stat_bgwriter
    27.2.11. pg_stat_database
    27.2.12. pg_stat_database_conflicts
    27.2.13. pg_stat_all_tables
    27.2.14. pg_stat_all_indexes
    27.2.15. pg_statio_all_tables
    27.2.16. pg_statio_all_indexes
    27.2.17. pg_statio_all_sequences
    27.2.18. pg_stat_user_functions
    27.2.19. pg_stat_slru
    27.2.20. Statistics Functions

    +27.2. The Statistics Collector

    27.2. The Statistics Collector
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    Prev Up Next
    27.1. Standard Unix Tools Home 27.3. Viewing Locks
    \ No newline at end of file +


    Prev Up Next
    27.1. Standard Unix Tools Home 27.3. Viewing Locks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/monitoring.html postgresql-13-13.12/doc/src/sgml/html/monitoring.html --- postgresql-13-13.11/doc/src/sgml/html/monitoring.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/monitoring.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 27. Monitoring Database Activity
    Chapter 27. Monitoring Database Activity
    Prev UpPart III. Server AdministrationHome Next

    Chapter 27. Monitoring Database Activity

    Table of Contents

    27.1. Standard Unix Tools
    27.2. The Statistics Collector
    27.2.1. Statistics Collection Configuration
    27.2.2. Viewing Statistics
    27.2.3. pg_stat_activity
    27.2.4. pg_stat_replication
    27.2.5. pg_stat_wal_receiver
    27.2.6. pg_stat_subscription
    27.2.7. pg_stat_ssl
    27.2.8. pg_stat_gssapi
    27.2.9. pg_stat_archiver
    27.2.10. pg_stat_bgwriter
    27.2.11. pg_stat_database
    27.2.12. pg_stat_database_conflicts
    27.2.13. pg_stat_all_tables
    27.2.14. pg_stat_all_indexes
    27.2.15. pg_statio_all_tables
    27.2.16. pg_statio_all_indexes
    27.2.17. pg_statio_all_sequences
    27.2.18. pg_stat_user_functions
    27.2.19. pg_stat_slru
    27.2.20. Statistics Functions
    27.3. Viewing Locks
    27.4. Progress Reporting
    27.4.1. ANALYZE Progress Reporting
    27.4.2. CREATE INDEX Progress Reporting
    27.4.3. VACUUM Progress Reporting
    27.4.4. CLUSTER Progress Reporting
    27.4.5. Base Backup Progress Reporting
    27.5. Dynamic Tracing
    27.5.1. Compiling for Dynamic Tracing
    27.5.2. Built-in Probes
    27.5.3. Using Probes
    27.5.4. Defining New Probes

    +Chapter 27. Monitoring Database Activity

    Chapter 27. Monitoring Database Activity
    Prev UpPart III. Server AdministrationHome Next
    Prev Up Next
    26.5. Hot Standby Home 27.1. Standard Unix Tools
    \ No newline at end of file +

    Prev Up Next
    26.5. Hot Standby Home 27.1. Standard Unix Tools
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/multibyte.html postgresql-13-13.12/doc/src/sgml/html/multibyte.html --- postgresql-13-13.11/doc/src/sgml/html/multibyte.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/multibyte.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -23.3. Character Set Support
    23.3. Character Set Support
    Prev UpChapter 23. LocalizationHome Next

    23.3. Character Set Support

    23.3.1. Supported Character Sets
    23.3.2. Setting the Character Set
    23.3.3. Automatic Character Set Conversion Between Server and Client
    23.3.4. Available Character Set Conversions
    23.3.5. Further Reading

    +23.3. Character Set Support

    23.3. Character Set Support
    Prev UpChapter 23. LocalizationHome Next

    23.3. Character Set Support

    23.3.1. Supported Character Sets
    23.3.2. Setting the Character Set
    23.3.3. Automatic Character Set Conversion Between Server and Client
    23.3.4. Available Character Set Conversions
    23.3.5. Further Reading

    The character set support in PostgreSQL allows you to store text in a variety of character sets (also called encodings), including @@ -348,4 +348,4 @@ UTF-8 (8-bit UCS/Unicode Transformation Format) is defined here.

    -

    Prev Up Next
    23.2. Collation Support Home Chapter 24. Routine Database Maintenance Tasks
    \ No newline at end of file +

    Prev Up Next
    23.2. Collation Support Home Chapter 24. Routine Database Maintenance Tasks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/multivariate-statistics-examples.html postgresql-13-13.12/doc/src/sgml/html/multivariate-statistics-examples.html --- postgresql-13-13.11/doc/src/sgml/html/multivariate-statistics-examples.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/multivariate-statistics-examples.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -71.2. Multivariate Statistics Examples
    71.2. Multivariate Statistics Examples
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.2. Multivariate Statistics Examples

    71.2.1. Functional Dependencies
    71.2.2. Multivariate N-Distinct Counts
    71.2.3. MCV Lists

    71.2.1. Functional Dependencies

    +71.2. Multivariate Statistics Examples

    71.2. Multivariate Statistics Examples
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.2. Multivariate Statistics Examples

    71.2.1. Functional Dependencies
    71.2.2. Multivariate N-Distinct Counts
    71.2.3. MCV Lists

    71.2.1. Functional Dependencies

    Multivariate correlation can be demonstrated with a very simple data set — a table with two columns, both containing the same values: @@ -207,4 +207,4 @@ Rows Removed by Filter: 10000

    -

    Prev Up Next
    71.1. Row Estimation Examples Home 71.3. Planner Statistics and Security
    \ No newline at end of file +

    Prev Up Next
    71.1. Row Estimation Examples Home 71.3. Planner Statistics and Security
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/mvcc-caveats.html postgresql-13-13.12/doc/src/sgml/html/mvcc-caveats.html --- postgresql-13-13.11/doc/src/sgml/html/mvcc-caveats.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/mvcc-caveats.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -13.5. Caveats
    13.5. Caveats
    Prev UpChapter 13. Concurrency ControlHome Next

    13.5. Caveats

    +13.5. Caveats

    13.5. Caveats
    Prev UpChapter 13. Concurrency ControlHome Next

    13.5. Caveats

    Some DDL commands, currently only TRUNCATE and the table-rewriting forms of ALTER TABLE, are not MVCC-safe. This means that after the truncation or rewrite commits, the @@ -31,4 +31,4 @@ contrast, queries that explicitly examine the system catalogs don't see rows representing concurrently created database objects, in the higher isolation levels. -

    Prev Up Next
    13.4. Data Consistency Checks at the Application Level Home 13.6. Locking and Indexes
    \ No newline at end of file +

    Prev Up Next
    13.4. Data Consistency Checks at the Application Level Home 13.6. Locking and Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/mvcc-intro.html postgresql-13-13.12/doc/src/sgml/html/mvcc-intro.html --- postgresql-13-13.11/doc/src/sgml/html/mvcc-intro.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/mvcc-intro.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -13.1. Introduction
    13.1. Introduction
    Prev UpChapter 13. Concurrency ControlHome Next

    13.1. Introduction

    +13.1. Introduction

    13.1. Introduction
    Prev UpChapter 13. Concurrency ControlHome Next

    13.1. Introduction

    PostgreSQL provides a rich set of tools for developers to manage concurrent access to data. Internally, data consistency is maintained by using a multiversion @@ -34,4 +34,4 @@ performance than locks. In addition, application-defined advisory locks provide a mechanism for acquiring locks that are not tied to a single transaction. -

    Prev Up Next
    Chapter 13. Concurrency Control Home 13.2. Transaction Isolation
    \ No newline at end of file +

    Prev Up Next
    Chapter 13. Concurrency Control Home 13.2. Transaction Isolation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/mvcc.html postgresql-13-13.12/doc/src/sgml/html/mvcc.html --- postgresql-13-13.11/doc/src/sgml/html/mvcc.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/mvcc.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 13. Concurrency Control
    Chapter 13. Concurrency Control
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 13. Concurrency Control

    Table of Contents

    13.1. Introduction
    13.2. Transaction Isolation
    13.2.1. Read Committed Isolation Level
    13.2.2. Repeatable Read Isolation Level
    13.2.3. Serializable Isolation Level
    13.3. Explicit Locking
    13.3.1. Table-Level Locks
    13.3.2. Row-Level Locks
    13.3.3. Page-Level Locks
    13.3.4. Deadlocks
    13.3.5. Advisory Locks
    13.4. Data Consistency Checks at the Application Level
    13.4.1. Enforcing Consistency with Serializable Transactions
    13.4.2. Enforcing Consistency with Explicit Blocking Locks
    13.5. Caveats
    13.6. Locking and Indexes

    +Chapter 13. Concurrency Control

    Chapter 13. Concurrency Control
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 13. Concurrency Control

    Table of Contents

    13.1. Introduction
    13.2. Transaction Isolation
    13.2.1. Read Committed Isolation Level
    13.2.2. Repeatable Read Isolation Level
    13.2.3. Serializable Isolation Level
    13.3. Explicit Locking
    13.3.1. Table-Level Locks
    13.3.2. Row-Level Locks
    13.3.3. Page-Level Locks
    13.3.4. Deadlocks
    13.3.5. Advisory Locks
    13.4. Data Consistency Checks at the Application Level
    13.4.1. Enforcing Consistency with Serializable Transactions
    13.4.2. Enforcing Consistency with Explicit Blocking Locks
    13.5. Caveats
    13.6. Locking and Indexes

    This chapter describes the behavior of the PostgreSQL database system when two or more sessions try to access the same data at the same time. The @@ -7,4 +7,4 @@ sessions while maintaining strict data integrity. Every developer of database applications should be familiar with the topics covered in this chapter. -

    Prev Up Next
    12.11. Limitations Home 13.1. Introduction
    \ No newline at end of file +

    Prev Up Next
    12.11. Limitations Home 13.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/nls-programmer.html postgresql-13-13.12/doc/src/sgml/html/nls-programmer.html --- postgresql-13-13.11/doc/src/sgml/html/nls-programmer.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/nls-programmer.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -54.2. For the Programmer
    54.2. For the Programmer
    Prev UpChapter 54. Native Language SupportHome Next

    54.2. For the Programmer

    54.2.1. Mechanics
    54.2.2. Message-Writing Guidelines

    54.2.1. Mechanics

    +54.2. For the Programmer

    54.2. For the Programmer
    Prev UpChapter 54. Native Language SupportHome Next

    54.2. For the Programmer

    54.2.1. Mechanics
    54.2.2. Message-Writing Guidelines

    54.2.1. Mechanics

    This section describes how to implement native language support in a program or library that is part of the PostgreSQL distribution. @@ -151,4 +151,4 @@ These comments are copied to the message catalog files so that the translators can see them.

    -

    Prev Up Next
    54.1. For the Translator Home Chapter 55. Writing a Procedural Language Handler
    \ No newline at end of file +

    Prev Up Next
    54.1. For the Translator Home Chapter 55. Writing a Procedural Language Handler
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/nls-translator.html postgresql-13-13.12/doc/src/sgml/html/nls-translator.html --- postgresql-13-13.11/doc/src/sgml/html/nls-translator.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/nls-translator.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -54.1. For the Translator
    54.1. For the Translator
    Prev UpChapter 54. Native Language SupportHome Next

    54.1. For the Translator

    54.1.1. Requirements
    54.1.2. Concepts
    54.1.3. Creating and Maintaining Message Catalogs
    54.1.4. Editing the PO Files

    +54.1. For the Translator

    54.1. For the Translator
    Prev UpChapter 54. Native Language SupportHome Next

    54.1. For the Translator

    54.1.1. Requirements
    54.1.2. Concepts
    54.1.3. Creating and Maintaining Message Catalogs
    54.1.4. Editing the PO Files

    PostgreSQL programs (server and client) can issue their messages in your favorite language — if the messages have been translated. @@ -215,4 +215,4 @@ speaking end users might also not understand it or find it ambiguous, so it's best to improve the message.

    -

    Prev Up Next
    Chapter 54. Native Language Support Home 54.2. For the Programmer
    \ No newline at end of file +

    Prev Up Next
    Chapter 54. Native Language Support Home 54.2. For the Programmer
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/nls.html postgresql-13-13.12/doc/src/sgml/html/nls.html --- postgresql-13-13.11/doc/src/sgml/html/nls.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/nls.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 54. Native Language Support
    Chapter 54. Native Language Support
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    53.4. Miscellaneous Coding Conventions Home 54.1. For the Translator
    \ No newline at end of file +Chapter 54. Native Language Support
    Chapter 54. Native Language Support
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    53.4. Miscellaneous Coding Conventions Home 54.1. For the Translator
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/non-durability.html postgresql-13-13.12/doc/src/sgml/html/non-durability.html --- postgresql-13-13.11/doc/src/sgml/html/non-durability.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/non-durability.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -14.5. Non-Durable Settings
    14.5. Non-Durable Settings
    Prev UpChapter 14. Performance TipsHome Next

    14.5. Non-Durable Settings

    +14.5. Non-Durable Settings

    14.5. Non-Durable Settings
    Prev UpChapter 14. Performance TipsHome Next

    14.5. Non-Durable Settings

    Durability is a database feature that guarantees the recording of committed transactions even if the server crashes or loses power. However, durability adds significant database overhead, @@ -36,4 +36,4 @@ tables to avoid WAL writes, though it makes the tables non-crash-safe.

    -

    Prev Up Next
    14.4. Populating a Database Home Chapter 15. Parallel Query
    \ No newline at end of file +

    Prev Up Next
    14.4. Populating a Database Home Chapter 15. Parallel Query
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/notation.html postgresql-13-13.12/doc/src/sgml/html/notation.html --- postgresql-13-13.11/doc/src/sgml/html/notation.html 2023-05-08 21:33:47.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/notation.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -3. Conventions
    3. Conventions
    Prev UpPrefaceHome Next

    3. Conventions

    +3. Conventions

    3. Conventions
    Prev UpPrefaceHome Next

    3. Conventions

    The following conventions are used in the synopsis of a command: brackets ([ and ]) indicate optional parts. Braces @@ -19,4 +19,4 @@ PostgreSQL system. These terms should not be interpreted too narrowly; this book does not have fixed presumptions about system administration procedures. -

    Prev Up Next
    2. A Brief History of PostgreSQL Home 4. Further Information
    \ No newline at end of file +

    Prev Up Next
    2. A Brief History of PostgreSQL Home 4. Further Information
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/oid2name.html postgresql-13-13.12/doc/src/sgml/html/oid2name.html --- postgresql-13-13.11/doc/src/sgml/html/oid2name.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/oid2name.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -oid2name
    oid2name
    Prev UpG.1. Client ApplicationsHome Next

    oid2name

    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory

    Synopsis

    oid2name [option...]

    Description

    +oid2name

    oid2name
    Prev UpG.1. Client ApplicationsHome Next

    oid2name

    oid2name — resolve OIDs and file nodes in a PostgreSQL data directory

    Synopsis

    oid2name [option...]

    Description

    oid2name is a utility program that helps administrators to examine the file structure used by PostgreSQL. To make use of it, you need to be familiar with the database file structure, which is described in @@ -189,4 +189,4 @@ 155156 foo

    Author

    B. Palmer -

    Prev Up Next
    G.1. Client Applications Home vacuumlo
    \ No newline at end of file +

    Prev Up Next
    G.1. Client Applications Home vacuumlo
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/overview.html postgresql-13-13.12/doc/src/sgml/html/overview.html --- postgresql-13-13.11/doc/src/sgml/html/overview.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/overview.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 50. Overview of PostgreSQL Internals
    Chapter 50. Overview of PostgreSQL Internals
    Prev UpPart VII. InternalsHome Next

    Chapter 50. Overview of PostgreSQL Internals

    Table of Contents

    50.1. The Path of a Query
    50.2. How Connections Are Established
    50.3. The Parser Stage
    50.3.1. Parser
    50.3.2. Transformation Process
    50.4. The PostgreSQL Rule System
    50.5. Planner/Optimizer
    50.5.1. Generating Possible Plans
    50.6. Executor

    Author

    +Chapter 50. Overview of PostgreSQL Internals

    Chapter 50. Overview of PostgreSQL Internals
    Prev UpPart VII. InternalsHome Next

    Chapter 50. Overview of PostgreSQL Internals

    Table of Contents

    50.1. The Path of a Query
    50.2. How Connections Are Established
    50.3. The Parser Stage
    50.3.1. Parser
    50.3.2. Transformation Process
    50.4. The PostgreSQL Rule System
    50.5. Planner/Optimizer
    50.5.1. Generating Possible Plans
    50.6. Executor

    Author

    This chapter originated as part of [sim98], Stefan Simkovics' Master's Thesis prepared at Vienna University of Technology under the direction @@ -15,4 +15,4 @@ understand the general sequence of operations that occur within the backend from the point at which a query is received, to the point at which the results are returned to the client. -

    Prev Up Next
    Part VII. Internals Home 50.1. The Path of a Query
    \ No newline at end of file +

    Prev Up Next
    Part VII. Internals Home 50.1. The Path of a Query
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pageinspect.html postgresql-13-13.12/doc/src/sgml/html/pageinspect.html --- postgresql-13-13.11/doc/src/sgml/html/pageinspect.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pageinspect.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.22. pageinspect
    F.22. pageinspect
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.22. pageinspect

    F.22.1. General Functions
    F.22.2. Heap Functions
    F.22.3. B-Tree Functions
    F.22.4. BRIN Functions
    F.22.5. GIN Functions
    F.22.6. Hash Functions

    +F.22. pageinspect

    F.22. pageinspect
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.22. pageinspect

    F.22.1. General Functions
    F.22.2. Heap Functions
    F.22.3. B-Tree Functions
    F.22.4. BRIN Functions
    F.22.5. GIN Functions
    F.22.6. Hash Functions

    The pageinspect module provides functions that allow you to inspect the contents of database pages at a low level, which is useful for debugging purposes. All of these functions may be used only by superusers. @@ -508,4 +508,4 @@ spares | {0,0,0,0,0,0,1,1,1,1,1,1,1,1,3,4,4,4,45,55,58,59,​508,567,628,704,1193,1202,1204} mapp | {65}

    -

    Prev Up Next
    F.21. ltree Home F.23. passwordcheck
    \ No newline at end of file +

    Prev Up Next
    F.21. ltree Home F.23. passwordcheck
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/parallel-plans.html postgresql-13-13.12/doc/src/sgml/html/parallel-plans.html --- postgresql-13-13.11/doc/src/sgml/html/parallel-plans.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/parallel-plans.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -15.3. Parallel Plans
    15.3. Parallel Plans
    Prev UpChapter 15. Parallel QueryHome Next

    15.3. Parallel Plans

    15.3.1. Parallel Scans
    15.3.2. Parallel Joins
    15.3.3. Parallel Aggregation
    15.3.4. Parallel Append
    15.3.5. Parallel Plan Tips

    +15.3. Parallel Plans

    15.3. Parallel Plans
    Prev UpChapter 15. Parallel QueryHome Next

    15.3. Parallel Plans

    15.3.1. Parallel Scans
    15.3.2. Parallel Joins
    15.3.3. Parallel Aggregation
    15.3.4. Parallel Append
    15.3.5. Parallel Plan Tips

    Because each worker executes the parallel portion of the plan to completion, it is not possible to simply take an ordinary query plan and run it using multiple workers. Each worker would produce a full @@ -151,4 +151,4 @@ This may be useful in determining whether the work is being evenly distributed between all plan nodes and more generally in understanding the performance characteristics of the plan. -

    Prev Up Next
    15.2. When Can Parallel Query Be Used? Home 15.4. Parallel Safety
    \ No newline at end of file +

    Prev Up Next
    15.2. When Can Parallel Query Be Used? Home 15.4. Parallel Safety
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/parallel-query.html postgresql-13-13.12/doc/src/sgml/html/parallel-query.html --- postgresql-13-13.11/doc/src/sgml/html/parallel-query.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/parallel-query.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 15. Parallel Query
    Chapter 15. Parallel Query
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 15. Parallel Query

    Table of Contents

    15.1. How Parallel Query Works
    15.2. When Can Parallel Query Be Used?
    15.3. Parallel Plans
    15.3.1. Parallel Scans
    15.3.2. Parallel Joins
    15.3.3. Parallel Aggregation
    15.3.4. Parallel Append
    15.3.5. Parallel Plan Tips
    15.4. Parallel Safety
    15.4.1. Parallel Labeling for Functions and Aggregates

    +Chapter 15. Parallel Query

    Chapter 15. Parallel Query
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 15. Parallel Query

    Table of Contents

    15.1. How Parallel Query Works
    15.2. When Can Parallel Query Be Used?
    15.3. Parallel Plans
    15.3.1. Parallel Scans
    15.3.2. Parallel Joins
    15.3.3. Parallel Aggregation
    15.3.4. Parallel Append
    15.3.5. Parallel Plan Tips
    15.4. Parallel Safety
    15.4.1. Parallel Labeling for Functions and Aggregates

    PostgreSQL can devise query plans that can leverage multiple CPUs in order to answer queries faster. This feature is known as parallel query. Many queries cannot benefit from parallel query, either @@ -12,4 +12,4 @@ few rows to the user will typically benefit most. This chapter explains some details of how parallel query works and in which situations it can be used so that users who wish to make use of it can understand what to expect. -

    Prev Up Next
    14.5. Non-Durable Settings Home 15.1. How Parallel Query Works
    \ No newline at end of file +

    Prev Up Next
    14.5. Non-Durable Settings Home 15.1. How Parallel Query Works
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/parallel-safety.html postgresql-13-13.12/doc/src/sgml/html/parallel-safety.html --- postgresql-13-13.11/doc/src/sgml/html/parallel-safety.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/parallel-safety.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -15.4. Parallel Safety
    15.4. Parallel Safety
    Prev UpChapter 15. Parallel QueryHome Next

    15.4. Parallel Safety

    15.4.1. Parallel Labeling for Functions and Aggregates

    +15.4. Parallel Safety

    15.4. Parallel Safety
    Prev UpChapter 15. Parallel QueryHome Next

    15.4. Parallel Safety

    15.4.1. Parallel Labeling for Functions and Aggregates

    The planner classifies operations involved in a query as either parallel safe, parallel restricted, or parallel unsafe. A parallel safe operation is one that @@ -80,4 +80,4 @@ the parallel portion of the query and defer the evaluation of the WHERE clause so that it happens above the Gather node. However, the planner does not do this. -

    Prev Up Next
    15.3. Parallel Plans Home Part III. Server Administration
    \ No newline at end of file +

    Prev Up Next
    15.3. Parallel Plans Home Part III. Server Administration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/parser-stage.html postgresql-13-13.12/doc/src/sgml/html/parser-stage.html --- postgresql-13-13.11/doc/src/sgml/html/parser-stage.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/parser-stage.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.3. The Parser Stage
    50.3. The Parser Stage
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.3. The Parser Stage

    50.3.1. Parser
    50.3.2. Transformation Process

    +50.3. The Parser Stage

    50.3. The Parser Stage
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.3. The Parser Stage

    50.3.1. Parser
    50.3.2. Transformation Process

    The parser stage consists of two parts:

    • @@ -88,4 +88,4 @@ name turns out to be an ordinary function or an aggregate function. Also, information about the actual data types of columns and expression results is added to the query tree. -

    Prev Up Next
    50.2. How Connections Are Established Home 50.4. The PostgreSQL Rule System
    \ No newline at end of file +

    Prev Up Next
    50.2. How Connections Are Established Home 50.4. The PostgreSQL Rule System
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/passwordcheck.html postgresql-13-13.12/doc/src/sgml/html/passwordcheck.html --- postgresql-13-13.11/doc/src/sgml/html/passwordcheck.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/passwordcheck.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.23. passwordcheck
    F.23. passwordcheck
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.23. passwordcheck

    +F.23. passwordcheck

    F.23. passwordcheck
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.23. passwordcheck

    The passwordcheck module checks users' passwords whenever they are set with CREATE ROLE or @@ -39,4 +39,4 @@ Alternatively, you could modify passwordcheck to reject pre-encrypted passwords, but forcing users to set their passwords in clear text carries its own security risks. -

    Prev Up Next
    F.22. pageinspect Home F.24. pg_buffercache
    \ No newline at end of file +

    Prev Up Next
    F.22. pageinspect Home F.24. pg_buffercache
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/performance-tips.html postgresql-13-13.12/doc/src/sgml/html/performance-tips.html --- postgresql-13-13.11/doc/src/sgml/html/performance-tips.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/performance-tips.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,7 +1,7 @@ -Chapter 14. Performance Tips
    Chapter 14. Performance Tips
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 14. Performance Tips

    Table of Contents

    14.1. Using EXPLAIN
    14.1.1. EXPLAIN Basics
    14.1.2. EXPLAIN ANALYZE
    14.1.3. Caveats
    14.2. Statistics Used by the Planner
    14.2.1. Single-Column Statistics
    14.2.2. Extended Statistics
    14.3. Controlling the Planner with Explicit JOIN Clauses
    14.4. Populating a Database
    14.4.1. Disable Autocommit
    14.4.2. Use COPY
    14.4.3. Remove Indexes
    14.4.4. Remove Foreign Key Constraints
    14.4.5. Increase maintenance_work_mem
    14.4.6. Increase max_wal_size
    14.4.7. Disable WAL Archival and Streaming Replication
    14.4.8. Run ANALYZE Afterwards
    14.4.9. Some Notes about pg_dump
    14.5. Non-Durable Settings

    +Chapter 14. Performance Tips

    Chapter 14. Performance Tips
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    13.6. Locking and Indexes Home 14.1. Using EXPLAIN
    \ No newline at end of file +

    Prev Up Next
    13.6. Locking and Indexes Home 14.1. Using EXPLAIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/perm-functions.html postgresql-13-13.12/doc/src/sgml/html/perm-functions.html --- postgresql-13-13.11/doc/src/sgml/html/perm-functions.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/perm-functions.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.6. Function Security
    21.6. Function Security
    Prev UpChapter 21. Database RolesHome Next

    21.6. Function Security

    +21.6. Function Security

    21.6. Function Security
    Prev UpChapter 21. Database RolesHome Next

    21.6. Function Security

    Functions, triggers and row-level security policies allow users to insert code into the backend server that other users might execute unintentionally. Hence, these mechanisms permit users to “Trojan @@ -19,4 +19,4 @@ are considered “untrusted”, and PostgreSQL allows only superusers to create functions written in those languages. -

    Prev Up Next
    21.5. Default Roles Home Chapter 22. Managing Databases
    \ No newline at end of file +

    Prev Up Next
    21.5. Default Roles Home Chapter 22. Managing Databases
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgarchivecleanup.html postgresql-13-13.12/doc/src/sgml/html/pgarchivecleanup.html --- postgresql-13-13.11/doc/src/sgml/html/pgarchivecleanup.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgarchivecleanup.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_archivecleanup
    pg_archivecleanup
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_archivecleanup

    pg_archivecleanup — clean up PostgreSQL WAL archive files

    Synopsis

    pg_archivecleanup [option...] archivelocation oldestkeptwalfile

    Description

    +pg_archivecleanup

    pg_archivecleanup
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_archivecleanup

    pg_archivecleanup — clean up PostgreSQL WAL archive files

    Synopsis

    pg_archivecleanup [option...] archivelocation oldestkeptwalfile

    Description

    pg_archivecleanup is designed to be used as an archive_cleanup_command to clean up WAL file archives when running as a standby server (see Section 26.2). @@ -91,4 +91,4 @@ produce debugging output in cleanup.log

  • remove no-longer-needed files from the archive directory -

    • See Also

    pg_standby
    Prev Up Next
    initdb Home pg_checksums
    \ No newline at end of file +

    See Also

    pg_standby
    Prev Up Next
    initdb Home pg_checksums
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgbench.html postgresql-13-13.12/doc/src/sgml/html/pgbench.html --- postgresql-13-13.11/doc/src/sgml/html/pgbench.html 2023-05-08 21:34:08.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgbench.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -pgbench
    pgbench
    Prev UpPostgreSQL Client ApplicationsHome Next

    pgbench

    pgbench — run a benchmark test on PostgreSQL

    Synopsis

    pgbench -i [option...] [dbname]

    pgbench [option...] [dbname]

    Description

    +pgbench

    pgbench
    Prev UpPostgreSQL Client ApplicationsHome Next

    pgbench

    pgbench — run a benchmark test on PostgreSQL

    Synopsis

    pgbench -i [option...] [dbname]

    pgbench [option...] [dbname]

    Description

    pgbench is a simple program for running benchmark tests on PostgreSQL. It runs the same sequence of SQL commands over and over, possibly in multiple concurrent database sessions, @@ -1399,4 +1399,4 @@ do not run pgbench in that database. pgbench uses unqualified names and does not manipulate the search path. -

    Prev Up Next
    pg_basebackup Home pg_config
    \ No newline at end of file +

    Prev Up Next
    pg_basebackup Home pg_config
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgbuffercache.html postgresql-13-13.12/doc/src/sgml/html/pgbuffercache.html --- postgresql-13-13.11/doc/src/sgml/html/pgbuffercache.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgbuffercache.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.24. pg_buffercache
    F.24. pg_buffercache
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.24. pg_buffercache

    F.24.1. The pg_buffercache View
    F.24.2. Sample Output
    F.24.3. Authors

    +F.24. pg_buffercache

    F.24. pg_buffercache
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.24. pg_buffercache

    F.24.1. The pg_buffercache View
    F.24.2. Sample Output
    F.24.3. Authors

    The pg_buffercache module provides a means for examining what's happening in the shared buffer cache in real time.

    @@ -115,4 +115,4 @@ Design suggestions: Neil Conway

    Debugging advice: Tom Lane -

    Prev Up Next
    F.23. passwordcheck Home F.25. pgcrypto
    \ No newline at end of file +

    Prev Up Next
    F.23. passwordcheck Home F.25. pgcrypto
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgcrypto.html postgresql-13-13.12/doc/src/sgml/html/pgcrypto.html --- postgresql-13-13.11/doc/src/sgml/html/pgcrypto.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgcrypto.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.25. pgcrypto
    F.25. pgcrypto
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.25. pgcrypto

    F.25.1. General Hashing Functions
    F.25.2. Password Hashing Functions
    F.25.3. PGP Encryption Functions
    F.25.4. Raw Encryption Functions
    F.25.5. Random-Data Functions
    F.25.6. Notes
    F.25.7. Author

    +F.25. pgcrypto

    F.25. pgcrypto
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.25. pgcrypto

    F.25.1. General Hashing Functions
    F.25.2. Password Hashing Functions
    F.25.3. PGP Encryption Functions
    F.25.4. Raw Encryption Functions
    F.25.5. Random-Data Functions
    F.25.6. Notes
    F.25.7. Author

    The pgcrypto module provides cryptographic functions for PostgreSQL.

    @@ -545,4 +545,4 @@ Marko Kreen

    pgcrypto uses code from the following sources: -

    AlgorithmAuthorSource origin
    DES cryptDavid Burren and othersFreeBSD libcrypt
    MD5 cryptPoul-Henning KampFreeBSD libcrypt
    Blowfish cryptSolar Designerwww.openwall.com
    Blowfish cipherSimon TathamPuTTY
    Rijndael cipherBrian GladmanOpenBSD sys/crypto
    MD5 hash and SHA1WIDE ProjectKAME kame/sys/crypto
    SHA256/384/512 Aaron D. GiffordOpenBSD sys/crypto
    BIGNUM mathMichael J. Frombergerdartmouth.edu/~sting/sw/imath
    Prev Up Next
    F.24. pg_buffercache Home F.26. pg_freespacemap
    \ No newline at end of file +

    AlgorithmAuthorSource origin
    DES cryptDavid Burren and othersFreeBSD libcrypt
    MD5 cryptPoul-Henning KampFreeBSD libcrypt
    Blowfish cryptSolar Designerwww.openwall.com
    Blowfish cipherSimon TathamPuTTY
    Rijndael cipherBrian GladmanOpenBSD sys/crypto
    MD5 hash and SHA1WIDE ProjectKAME kame/sys/crypto
    SHA256/384/512 Aaron D. GiffordOpenBSD sys/crypto
    BIGNUM mathMichael J. Frombergerdartmouth.edu/~sting/sw/imath
    Prev Up Next
    F.24. pg_buffercache Home F.26. pg_freespacemap
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgfreespacemap.html postgresql-13-13.12/doc/src/sgml/html/pgfreespacemap.html --- postgresql-13-13.11/doc/src/sgml/html/pgfreespacemap.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgfreespacemap.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.26. pg_freespacemap
    F.26. pg_freespacemap
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.26. pg_freespacemap

    F.26.1. Functions
    F.26.2. Sample Output
    F.26.3. Author

    +F.26. pg_freespacemap

    F.26. pg_freespacemap
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.26. pg_freespacemap

    F.26.1. Functions
    F.26.2. Sample Output
    F.26.3. Author

    The pg_freespacemap module provides a means for examining the free space map (FSM). It provides a function called pg_freespace, or two overloaded functions, to be @@ -67,4 +67,4 @@ Original version by Mark Kirkwood . Rewritten in version 8.4 to suit new FSM implementation by Heikki Linnakangas -

    Prev Up Next
    F.25. pgcrypto Home F.27. pg_prewarm
    \ No newline at end of file +

    Prev Up Next
    F.25. pgcrypto Home F.27. pg_prewarm
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgprewarm.html postgresql-13-13.12/doc/src/sgml/html/pgprewarm.html --- postgresql-13-13.11/doc/src/sgml/html/pgprewarm.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgprewarm.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.27. pg_prewarm
    F.27. pg_prewarm
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.27. pg_prewarm

    F.27.1. Functions
    F.27.2. Configuration Parameters
    F.27.3. Author

    +F.27. pg_prewarm

    F.27. pg_prewarm
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.27. pg_prewarm

    F.27.1. Functions
    F.27.2. Configuration Parameters
    F.27.3. Author

    The pg_prewarm module provides a convenient way to load relation data into either the operating system buffer cache or the PostgreSQL buffer cache. Prewarming @@ -79,4 +79,4 @@

    F.27.3. Author

    Robert Haas -

    Prev Up Next
    F.26. pg_freespacemap Home F.28. pgrowlocks
    \ No newline at end of file +

    Prev Up Next
    F.26. pg_freespacemap Home F.28. pgrowlocks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgrowlocks.html postgresql-13-13.12/doc/src/sgml/html/pgrowlocks.html --- postgresql-13-13.11/doc/src/sgml/html/pgrowlocks.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgrowlocks.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.28. pgrowlocks
    F.28. pgrowlocks
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.28. pgrowlocks

    F.28.1. Overview
    F.28.2. Sample Output
    F.28.3. Author

    +F.28. pgrowlocks

    F.28. pgrowlocks
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.28. pgrowlocks

    F.28.1. Overview
    F.28.2. Sample Output
    F.28.3. Author

    The pgrowlocks module provides a function to show row locking information for a specified table.

    @@ -48,4 +48,4 @@ (4 rows)

    F.28.3. Author

    Tatsuo Ishii -

    Prev Up Next
    F.27. pg_prewarm Home F.29. pg_stat_statements
    \ No newline at end of file +

    Prev Up Next
    F.27. pg_prewarm Home F.29. pg_stat_statements
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgstandby.html postgresql-13-13.12/doc/src/sgml/html/pgstandby.html --- postgresql-13-13.11/doc/src/sgml/html/pgstandby.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgstandby.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -pg_standby
    pg_standby
    Prev UpG.2. Server ApplicationsHome Next

    pg_standby

    pg_standby — supports the creation of a PostgreSQL warm standby server

    Synopsis

    pg_standby [option...] archivelocation nextwalfile walfilepath [restartwalfile]

    Description

    +pg_standby

    pg_standby
    Prev UpG.2. Server ApplicationsHome Next

    pg_standby

    pg_standby — supports the creation of a PostgreSQL warm standby server

    Synopsis

    pg_standby [option...] archivelocation nextwalfile walfilepath [restartwalfile]

    Description

    pg_standby supports creation of a “warm standby” database server. It is designed to be a production-ready program, as well as a customizable template should you require specific modifications. @@ -192,4 +192,4 @@ network.

    Author

    Simon Riggs -

    Prev Up Next
    G.2. Server Applications Home Appendix H. External Projects
    \ No newline at end of file +

    Prev Up Next
    G.2. Server Applications Home Appendix H. External Projects
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgstatstatements.html postgresql-13-13.12/doc/src/sgml/html/pgstatstatements.html --- postgresql-13-13.11/doc/src/sgml/html/pgstatstatements.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgstatstatements.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.29. pg_stat_statements
    F.29. pg_stat_statements
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.29. pg_stat_statements

    F.29.1. The pg_stat_statements View
    F.29.2. Functions
    F.29.3. Configuration Parameters
    F.29.4. Sample Output
    F.29.5. Authors

    +F.29. pg_stat_statements

    F.29. pg_stat_statements
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.29. pg_stat_statements

    F.29.1. The pg_stat_statements View
    F.29.2. Functions
    F.29.3. Configuration Parameters
    F.29.4. Sample Output
    F.29.5. Authors

    The pg_stat_statements module provides a means for tracking planning and execution statistics of all SQL statements executed by a server. @@ -501,4 +501,4 @@

    F.29.5. Authors

    Takahiro Itagaki . Query normalization added by Peter Geoghegan . -

    Prev Up Next
    F.28. pgrowlocks Home F.30. pgstattuple
    \ No newline at end of file +

    Prev Up Next
    F.28. pgrowlocks Home F.30. pgstattuple
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgstattuple.html postgresql-13-13.12/doc/src/sgml/html/pgstattuple.html --- postgresql-13-13.11/doc/src/sgml/html/pgstattuple.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgstattuple.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.30. pgstattuple
    F.30. pgstattuple
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.30. pgstattuple

    F.30.1. Functions
    F.30.2. Authors

    +F.30. pgstattuple

    F.30. pgstattuple
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.30. pgstattuple

    F.30.1. Functions
    F.30.2. Authors

    The pgstattuple module provides various functions to obtain tuple-level statistics.

    @@ -196,4 +196,4 @@ accurate to the byte.

    F.30.2. Authors

    Tatsuo Ishii, Satoshi Nagayasu and Abhijit Menon-Sen -

    Prev Up Next
    F.29. pg_stat_statements Home F.31. pg_trgm
    \ No newline at end of file +

    Prev Up Next
    F.29. pg_stat_statements Home F.31. pg_trgm
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgtestfsync.html postgresql-13-13.12/doc/src/sgml/html/pgtestfsync.html --- postgresql-13-13.11/doc/src/sgml/html/pgtestfsync.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgtestfsync.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_test_fsync
    pg_test_fsync
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_test_fsync

    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL

    Synopsis

    pg_test_fsync [option...]

    Description

    +pg_test_fsync

    pg_test_fsync
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_test_fsync

    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL

    Synopsis

    pg_test_fsync [option...]

    Description

    pg_test_fsync is intended to give you a reasonable idea of what the fastest wal_sync_method is on your specific system, @@ -38,4 +38,4 @@ color in diagnostic messages. Possible values are always, auto and never. -

    See Also

    postgres
    Prev Up Next
    pg_rewind Home pg_test_timing
    \ No newline at end of file +

    See Also

    postgres
    Prev Up Next
    pg_rewind Home pg_test_timing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgtesttiming.html postgresql-13-13.12/doc/src/sgml/html/pgtesttiming.html --- postgresql-13-13.11/doc/src/sgml/html/pgtesttiming.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgtesttiming.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_test_timing
    pg_test_timing
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_test_timing

    pg_test_timing — measure timing overhead

    Synopsis

    pg_test_timing [option...]

    Description

    +pg_test_timing

    pg_test_timing
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_test_timing

    pg_test_timing — measure timing overhead

    Synopsis

    pg_test_timing [option...]

    Description

    pg_test_timing is a tool to measure the timing overhead on your system and confirm that the system time never moves backwards. Systems that are slow to collect timing data can give less accurate @@ -176,4 +176,4 @@ Timer (PIT), the real-time clock (RTC), the Advanced Programmable Interrupt Controller (APIC) timer, and the Cyclone timer. These timers aim for millisecond resolution. -

    See Also

    EXPLAIN
    Prev Up Next
    pg_test_fsync Home pg_upgrade
    \ No newline at end of file +

    See Also

    EXPLAIN
    Prev Up Next
    pg_test_fsync Home pg_upgrade
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgtrgm.html postgresql-13-13.12/doc/src/sgml/html/pgtrgm.html --- postgresql-13-13.11/doc/src/sgml/html/pgtrgm.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgtrgm.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.31. pg_trgm
    F.31. pg_trgm
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.31. pg_trgm

    F.31.1. Trigram (or Trigraph) Concepts
    F.31.2. Functions and Operators
    F.31.3. GUC Parameters
    F.31.4. Index Support
    F.31.5. Text Search Integration
    F.31.6. References
    F.31.7. Authors

    +F.31. pg_trgm

    F.31. pg_trgm
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.31. pg_trgm

    F.31.1. Trigram (or Trigraph) Concepts
    F.31.2. Functions and Operators
    F.31.3. GUC Parameters
    F.31.4. Index Support
    F.31.5. Text Search Integration
    F.31.6. References
    F.31.7. Authors

    The pg_trgm module provides functions and operators for determining the similarity of alphanumeric text based on trigram matching, as @@ -420,4 +420,4 @@ Documentation: Christopher Kings-Lynne

    This module is sponsored by Delta-Soft Ltd., Moscow, Russia. -

    Prev Up Next
    F.30. pgstattuple Home F.32. pg_visibility
    \ No newline at end of file +

    Prev Up Next
    F.30. pgstattuple Home F.32. pg_visibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgupgrade.html postgresql-13-13.12/doc/src/sgml/html/pgupgrade.html --- postgresql-13-13.11/doc/src/sgml/html/pgupgrade.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgupgrade.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_upgrade
    pg_upgrade
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_upgrade

    pg_upgrade — upgrade a PostgreSQL server instance

    Synopsis

    pg_upgrade -b oldbindir [-B newbindir] -d oldconfigdir -D newconfigdir [option...]

    Description

    +pg_upgrade

    pg_upgrade
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_upgrade

    pg_upgrade — upgrade a PostgreSQL server instance

    Synopsis

    pg_upgrade -b oldbindir [-B newbindir] -d oldconfigdir -D newconfigdir [option...]

    Description

    pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore typically required for @@ -427,4 +427,4 @@ to make a backup of the old cluster and tablespaces, though the snapshot and copies must be created simultaneously or while the database server is down. -

    Prev Up Next
    pg_test_timing Home pg_waldump
    \ No newline at end of file +

    Prev Up Next
    pg_test_timing Home pg_waldump
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgvisibility.html postgresql-13-13.12/doc/src/sgml/html/pgvisibility.html --- postgresql-13-13.11/doc/src/sgml/html/pgvisibility.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgvisibility.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.32. pg_visibility
    F.32. pg_visibility
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.32. pg_visibility

    F.32.1. Functions
    F.32.2. Author

    +F.32. pg_visibility

    F.32. pg_visibility
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.32. pg_visibility

    F.32.1. Functions
    F.32.2. Author

    The pg_visibility module provides a means for examining the visibility map (VM) and page-level visibility information of a table. It also provides functions to check the integrity of a visibility map and to @@ -66,4 +66,4 @@ be executed by superusers.

    F.32.2. Author

    Robert Haas -

    Prev Up Next
    F.31. pg_trgm Home F.33. postgres_fdw
    \ No newline at end of file +

    Prev Up Next
    F.31. pg_trgm Home F.33. postgres_fdw
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgwaldump.html postgresql-13-13.12/doc/src/sgml/html/pgwaldump.html --- postgresql-13-13.11/doc/src/sgml/html/pgwaldump.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgwaldump.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -pg_waldump
    pg_waldump
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_waldump

    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster

    Synopsis

    pg_waldump [option...] [startseg [endseg]]

    Description

    +pg_waldump

    pg_waldump
    Prev UpPostgreSQL Server ApplicationsHome Next

    pg_waldump

    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster

    Synopsis

    pg_waldump [option...] [startseg [endseg]]

    Description

    pg_waldump displays the write-ahead log (WAL) and is mainly useful for debugging or educational purposes.

    @@ -73,4 +73,4 @@ pg_waldump cannot read WAL files with suffix .partial. If those files need to be read, .partial suffix needs to be removed from the file name. -

    Prev Up Next
    pg_upgrade Home postgres
    \ No newline at end of file +

    Prev Up Next
    pg_upgrade Home postgres
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pgxlogdump.html postgresql-13-13.12/doc/src/sgml/html/pgxlogdump.html --- postgresql-13-13.11/doc/src/sgml/html/pgxlogdump.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pgxlogdump.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,10 +1,10 @@ -O.2. pg_xlogdump renamed to pg_waldump
    O.2. pg_xlogdump renamed to pg_waldump
    Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

    O.2. pg_xlogdump renamed to pg_waldump

    +O.2. pg_xlogdump renamed to pg_waldump

    O.2. pg_xlogdump renamed to pg_waldump
    Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

    O.2. pg_xlogdump renamed to pg_waldump

    PostgreSQL 9.6 and below provided a command named pg_xlogdump to read write-ahead-log (WAL) files. This command was renamed to pg_waldump, see pg_waldump for documentation of pg_waldump and see - the release notes for PostgreSQL 10 for details + the release notes for PostgreSQL 10 for details on this change. -

    Prev Up Next
    O.1. recovery.conf file merged into postgresql.conf Home O.3. pg_resetxlog renamed to pg_resetwal
    \ No newline at end of file +

    Prev Up Next
    O.1. recovery.conf file merged into postgresql.conf Home O.3. pg_resetxlog renamed to pg_resetwal
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/planner-optimizer.html postgresql-13-13.12/doc/src/sgml/html/planner-optimizer.html --- postgresql-13-13.11/doc/src/sgml/html/planner-optimizer.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/planner-optimizer.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.5. Planner/Optimizer
    50.5. Planner/Optimizer
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.5. Planner/Optimizer

    50.5.1. Generating Possible Plans

    +50.5. Planner/Optimizer

    50.5. Planner/Optimizer
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.5. Planner/Optimizer

    50.5.1. Generating Possible Plans

    The task of the planner/optimizer is to create an optimal execution plan. A given SQL query (and hence, a query tree) can be actually executed in a wide variety of @@ -108,4 +108,4 @@ WHERE clause and computation of required output expressions to the most appropriate nodes of the plan tree. -

    Prev Up Next
    50.4. The PostgreSQL Rule System Home 50.6. Executor
    \ No newline at end of file +

    Prev Up Next
    50.4. The PostgreSQL Rule System Home 50.6. Executor
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/planner-stats-details.html postgresql-13-13.12/doc/src/sgml/html/planner-stats-details.html --- postgresql-13-13.11/doc/src/sgml/html/planner-stats-details.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/planner-stats-details.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 71. How the Planner Uses Statistics
    Chapter 71. How the Planner Uses Statistics
    Prev UpPart VII. InternalsHome Next

    Chapter 71. How the Planner Uses Statistics

    Table of Contents

    71.1. Row Estimation Examples
    71.2. Multivariate Statistics Examples
    71.2.1. Functional Dependencies
    71.2.2. Multivariate N-Distinct Counts
    71.2.3. MCV Lists
    71.3. Planner Statistics and Security

    +Chapter 71. How the Planner Uses Statistics

    Chapter 71. How the Planner Uses Statistics
    Prev UpPart VII. InternalsHome Next

    Chapter 71. How the Planner Uses Statistics

    Table of Contents

    71.1. Row Estimation Examples
    71.2. Multivariate Statistics Examples
    71.2.1. Functional Dependencies
    71.2.2. Multivariate N-Distinct Counts
    71.2.3. MCV Lists
    71.3. Planner Statistics and Security

    This chapter builds on the material covered in Section 14.1 and Section 14.2 to show some additional details about how the planner uses the system statistics to estimate the number of rows each part of a query might @@ -10,4 +10,4 @@ but to present an overview of how it works. This will perhaps ease the learning curve for someone who subsequently wishes to read the code. -

    Prev Up Next
    70.6. BKI Example Home 71.1. Row Estimation Examples
    \ No newline at end of file +

    Prev Up Next
    70.6. BKI Example Home 71.1. Row Estimation Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/planner-stats-security.html postgresql-13-13.12/doc/src/sgml/html/planner-stats-security.html --- postgresql-13-13.11/doc/src/sgml/html/planner-stats-security.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/planner-stats-security.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -71.3. Planner Statistics and Security
    71.3. Planner Statistics and Security
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.3. Planner Statistics and Security

    +71.3. Planner Statistics and Security

    71.3. Planner Statistics and Security
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.3. Planner Statistics and Security

    Access to the table pg_statistic is restricted to superusers, so that ordinary users cannot learn about the contents of the tables of other users from it. Some selectivity estimation functions will @@ -46,4 +46,4 @@ Selectivity estimation functions contained in third-party extensions that potentially operate on statistics with user-defined operators should follow the same security rules. Consult the PostgreSQL source code for guidance. -

    Prev Up Next
    71.2. Multivariate Statistics Examples Home Chapter 72. Backup Manifest Format
    \ No newline at end of file +

    Prev Up Next
    71.2. Multivariate Statistics Examples Home Chapter 72. Backup Manifest Format
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/planner-stats.html postgresql-13-13.12/doc/src/sgml/html/planner-stats.html --- postgresql-13-13.11/doc/src/sgml/html/planner-stats.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/planner-stats.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -14.2. Statistics Used by the Planner
    14.2. Statistics Used by the Planner
    Prev UpChapter 14. Performance TipsHome Next

    14.2. Statistics Used by the Planner

    14.2.1. Single-Column Statistics
    14.2.2. Extended Statistics

    14.2.1. Single-Column Statistics

    +14.2. Statistics Used by the Planner

    14.2. Statistics Used by the Planner
    Prev UpChapter 14. Performance TipsHome Next

    14.2. Statistics Used by the Planner

    14.2.1. Single-Column Statistics
    14.2.2. Extended Statistics

    14.2.1. Single-Column Statistics

    As we saw in the previous section, the query planner needs to estimate the number of rows retrieved by a query in order to make good choices of query plans. This section provides a quick look at the statistics @@ -333,4 +333,4 @@ and for which misestimation of the number of groups is resulting in bad plans. Otherwise, the ANALYZE and planning cycles are just wasted. -

    Prev Up Next
    14.1. Using EXPLAIN Home 14.3. Controlling the Planner with Explicit JOIN Clauses
    \ No newline at end of file +

    Prev Up Next
    14.1. Using EXPLAIN Home 14.3. Controlling the Planner with Explicit JOIN Clauses
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plhandler.html postgresql-13-13.12/doc/src/sgml/html/plhandler.html --- postgresql-13-13.11/doc/src/sgml/html/plhandler.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plhandler.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 55. Writing a Procedural Language Handler
    Chapter 55. Writing a Procedural Language Handler
    Prev UpPart VII. InternalsHome Next

    Chapter 55. Writing a Procedural Language Handler

    +Chapter 55. Writing a Procedural Language Handler

    Chapter 55. Writing a Procedural Language Handler
    Prev UpPart VII. InternalsHome Next

    Chapter 55. Writing a Procedural Language Handler

    All calls to functions that are written in a language other than the current “version 1” interface for compiled languages (this includes functions in user-defined procedural languages @@ -203,4 +203,4 @@ Look into the src/pl subdirectory of the source tree. The CREATE LANGUAGE reference page also has some useful details. -

    Prev Up Next
    54.2. For the Programmer Home Chapter 56. Writing a Foreign Data Wrapper
    \ No newline at end of file +

    Prev Up Next
    54.2. For the Programmer Home Chapter 56. Writing a Foreign Data Wrapper
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-builtins.html postgresql-13-13.12/doc/src/sgml/html/plperl-builtins.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-builtins.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-builtins.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.3. Built-in Functions
    44.3. Built-in Functions
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.3. Built-in Functions

    44.3.1. Database Access from PL/Perl
    44.3.2. Utility Functions in PL/Perl

    44.3.1. Database Access from PL/Perl

    +44.3. Built-in Functions

    44.3. Built-in Functions
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.3. Built-in Functions

    44.3.1. Database Access from PL/Perl
    44.3.2. Utility Functions in PL/Perl

    44.3.1. Database Access from PL/Perl

    Access to the database itself from your Perl function can be done via the following functions:

    @@ -357,4 +357,4 @@ Returns a true value if the given argument may be treated as an array reference, that is, if ref of the argument is ARRAY or PostgreSQL::InServer::ARRAY. Returns false otherwise. -

    Prev Up Next
    44.2. Data Values in PL/Perl Home 44.4. Global Values in PL/Perl
    \ No newline at end of file +

    Prev Up Next
    44.2. Data Values in PL/Perl Home 44.4. Global Values in PL/Perl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-data.html postgresql-13-13.12/doc/src/sgml/html/plperl-data.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-data.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-data.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.2. Data Values in PL/Perl
    44.2. Data Values in PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.2. Data Values in PL/Perl

    +44.2. Data Values in PL/Perl

    44.2. Data Values in PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.2. Data Values in PL/Perl

    The argument values supplied to a PL/Perl function's code are simply the input arguments converted to text form (just as if they had been displayed by a SELECT statement). @@ -11,4 +11,4 @@ improved by using a transform, as already illustrated for bool values. Several examples of transform modules are included in the PostgreSQL distribution. -

    Prev Up Next
    44.1. PL/Perl Functions and Arguments Home 44.3. Built-in Functions
    \ No newline at end of file +

    Prev Up Next
    44.1. PL/Perl Functions and Arguments Home 44.3. Built-in Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-event-triggers.html postgresql-13-13.12/doc/src/sgml/html/plperl-event-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-event-triggers.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-event-triggers.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.7. PL/Perl Event Triggers
    44.7. PL/Perl Event Triggers
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.7. PL/Perl Event Triggers

    +44.7. PL/Perl Event Triggers

    44.7. PL/Perl Event Triggers
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.7. PL/Perl Event Triggers

    PL/Perl can be used to write event trigger functions. In an event trigger function, the hash reference $_TD contains information about the current trigger event. $_TD is a global variable, @@ -25,4 +25,4 @@ ON ddl_command_start EXECUTE FUNCTION perlsnitch();

    -

    Prev Up Next
    44.6. PL/Perl Triggers Home 44.8. PL/Perl Under the Hood
    \ No newline at end of file +

    Prev Up Next
    44.6. PL/Perl Triggers Home 44.8. PL/Perl Under the Hood
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-funcs.html postgresql-13-13.12/doc/src/sgml/html/plperl-funcs.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-funcs.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-funcs.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.1. PL/Perl Functions and Arguments
    44.1. PL/Perl Functions and Arguments
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.1. PL/Perl Functions and Arguments

    +44.1. PL/Perl Functions and Arguments

    44.1. PL/Perl Functions and Arguments
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.1. PL/Perl Functions and Arguments

    To create a function in the PL/Perl language, use the standard CREATE FUNCTION syntax: @@ -305,4 +305,4 @@ at the top of the function body.

    The feature pragma is also available to use if your Perl is version 5.10.0 or higher. -

    Prev Up Next
    Chapter 44. PL/Perl — Perl Procedural Language Home 44.2. Data Values in PL/Perl
    \ No newline at end of file +

    Prev Up Next
    Chapter 44. PL/Perl — Perl Procedural Language Home 44.2. Data Values in PL/Perl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-global.html postgresql-13-13.12/doc/src/sgml/html/plperl-global.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-global.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-global.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.4. Global Values in PL/Perl
    44.4. Global Values in PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.4. Global Values in PL/Perl

    +44.4. Global Values in PL/Perl

    44.4. Global Values in PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.4. Global Values in PL/Perl

    You can use the global hash %_SHARED to store data, including code references, between function calls for the lifetime of the current session. @@ -62,4 +62,4 @@ functions that should communicate are owned by the same user, and mark them SECURITY DEFINER. You must of course take care that such functions can't be used to do anything unintended. -

    Prev Up Next
    44.3. Built-in Functions Home 44.5. Trusted and Untrusted PL/Perl
    \ No newline at end of file +

    Prev Up Next
    44.3. Built-in Functions Home 44.5. Trusted and Untrusted PL/Perl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-triggers.html postgresql-13-13.12/doc/src/sgml/html/plperl-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-triggers.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-triggers.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.6. PL/Perl Triggers
    44.6. PL/Perl Triggers
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.6. PL/Perl Triggers

    +44.6. PL/Perl Triggers

    44.6. PL/Perl Triggers
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.6. PL/Perl Triggers

    PL/Perl can be used to write trigger functions. In a trigger function, the hash reference $_TD contains information about the current trigger event. $_TD is a global variable, @@ -71,4 +71,4 @@ BEFORE INSERT OR UPDATE ON test FOR EACH ROW EXECUTE FUNCTION valid_id();

    -

    Prev Up Next
    44.5. Trusted and Untrusted PL/Perl Home 44.7. PL/Perl Event Triggers
    \ No newline at end of file +

    Prev Up Next
    44.5. Trusted and Untrusted PL/Perl Home 44.7. PL/Perl Event Triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-trusted.html postgresql-13-13.12/doc/src/sgml/html/plperl-trusted.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-trusted.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-trusted.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.5. Trusted and Untrusted PL/Perl
    44.5. Trusted and Untrusted PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.5. Trusted and Untrusted PL/Perl

    +44.5. Trusted and Untrusted PL/Perl

    44.5. Trusted and Untrusted PL/Perl
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.5. Trusted and Untrusted PL/Perl

    Normally, PL/Perl is installed as a “trusted” programming language named plperl. In this setup, certain Perl operations are disabled to preserve security. In general, the @@ -69,4 +69,4 @@ session, and so any one session can only execute either PL/PerlU functions, or PL/Perl functions that are all called by the same SQL role. -

    Prev Up Next
    44.4. Global Values in PL/Perl Home 44.6. PL/Perl Triggers
    \ No newline at end of file +

    Prev Up Next
    44.4. Global Values in PL/Perl Home 44.6. PL/Perl Triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl-under-the-hood.html postgresql-13-13.12/doc/src/sgml/html/plperl-under-the-hood.html --- postgresql-13-13.11/doc/src/sgml/html/plperl-under-the-hood.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl-under-the-hood.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -44.8. PL/Perl Under the Hood
    44.8. PL/Perl Under the Hood
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.8. PL/Perl Under the Hood

    44.8.1. Configuration
    44.8.2. Limitations and Missing Features

    44.8.1. Configuration

    +44.8. PL/Perl Under the Hood

    44.8. PL/Perl Under the Hood
    Prev UpChapter 44. PL/Perl — Perl Procedural LanguageHome Next

    44.8. PL/Perl Under the Hood

    44.8.1. Configuration
    44.8.2. Limitations and Missing Features

    44.8.1. Configuration

    This section lists configuration parameters that affect PL/Perl.

    plperl.on_init (string) @@ -108,4 +108,4 @@ file handles are not automatically flushed and objects are not automatically destroyed.

    -

    Prev Up Next
    44.7. PL/Perl Event Triggers Home Chapter 45. PL/Python — Python Procedural Language
    \ No newline at end of file +

    Prev Up Next
    44.7. PL/Perl Event Triggers Home Chapter 45. PL/Python — Python Procedural Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plperl.html postgresql-13-13.12/doc/src/sgml/html/plperl.html --- postgresql-13-13.11/doc/src/sgml/html/plperl.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plperl.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 44. PL/Perl — Perl Procedural Language
    Chapter 44. PL/Perl — Perl Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 44. PL/Perl — Perl Procedural Language

    Table of Contents

    44.1. PL/Perl Functions and Arguments
    44.2. Data Values in PL/Perl
    44.3. Built-in Functions
    44.3.1. Database Access from PL/Perl
    44.3.2. Utility Functions in PL/Perl
    44.4. Global Values in PL/Perl
    44.5. Trusted and Untrusted PL/Perl
    44.6. PL/Perl Triggers
    44.7. PL/Perl Event Triggers
    44.8. PL/Perl Under the Hood
    44.8.1. Configuration
    44.8.2. Limitations and Missing Features

    +Chapter 44. PL/Perl — Perl Procedural Language

    Chapter 44. PL/Perl — Perl Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 44. PL/Perl — Perl Procedural Language

    Table of Contents

    44.1. PL/Perl Functions and Arguments
    44.2. Data Values in PL/Perl
    44.3. Built-in Functions
    44.3.1. Database Access from PL/Perl
    44.3.2. Utility Functions in PL/Perl
    44.4. Global Values in PL/Perl
    44.5. Trusted and Untrusted PL/Perl
    44.6. PL/Perl Triggers
    44.7. PL/Perl Event Triggers
    44.8. PL/Perl Under the Hood
    44.8.1. Configuration
    44.8.2. Limitations and Missing Features

    PL/Perl is a loadable procedural language that enables you to write PostgreSQL functions and procedures in the Perl programming language. @@ -19,4 +19,4 @@ Users of source packages must specially enable the build of PL/Perl during the installation process. (Refer to Chapter 16 for more information.) Users of binary packages might find PL/Perl in a separate subpackage. -

    Prev Up Next
    43.12. Tcl Procedure Names Home 44.1. PL/Perl Functions and Arguments
    \ No newline at end of file +

    Prev Up Next
    43.12. Tcl Procedure Names Home 44.1. PL/Perl Functions and Arguments
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-control-structures.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-control-structures.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-control-structures.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-control-structures.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.6. Control Structures
    42.6. Control Structures
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.6. Control Structures

    42.6.1. Returning from a Function
    42.6.2. Returning from a Procedure
    42.6.3. Calling a Procedure
    42.6.4. Conditionals
    42.6.5. Simple Loops
    42.6.6. Looping through Query Results
    42.6.7. Looping through Arrays
    42.6.8. Trapping Errors
    42.6.9. Obtaining Execution Location Information

    +42.6. Control Structures

    42.6. Control Structures
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.6. Control Structures

    42.6.1. Returning from a Function
    42.6.2. Returning from a Procedure
    42.6.3. Calling a Procedure
    42.6.4. Conditionals
    42.6.5. Simple Loops
    42.6.6. Looping through Query Results
    42.6.7. Looping through Arrays
    42.6.8. Trapping Errors
    42.6.9. Obtaining Execution Location Information

    Control structures are probably the most useful (and important) part of PL/pgSQL. With PL/pgSQL's control structures, @@ -936,4 +936,4 @@ GET STACKED DIAGNOSTICS ... PG_EXCEPTION_CONTEXT returns the same sort of stack trace, but describing the location at which an error was detected, rather than the current location. -

    Prev Up Next
    42.5. Basic Statements Home 42.7. Cursors
    \ No newline at end of file +

    Prev Up Next
    42.5. Basic Statements Home 42.7. Cursors
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-cursors.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-cursors.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-cursors.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-cursors.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.7. Cursors
    42.7. Cursors
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.7. Cursors

    42.7.1. Declaring Cursor Variables
    42.7.2. Opening Cursors
    42.7.3. Using Cursors
    42.7.4. Looping through a Cursor's Result

    +42.7. Cursors

    42.7. Cursors
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.7. Cursors

    42.7.1. Declaring Cursor Variables
    42.7.2. Opening Cursors
    42.7.3. Using Cursors
    42.7.4. Looping through a Cursor's Result

    Rather than executing a whole query at once, it is possible to set up a cursor that encapsulates the query, and then read the query result a few rows at a time. One reason for doing this is @@ -383,4 +383,4 @@ existing definition of the variable name is ignored within the loop). Each row returned by the cursor is successively assigned to this record variable and the loop body is executed. -

    Prev Up Next
    42.6. Control Structures Home 42.8. Transaction Management
    \ No newline at end of file +

    Prev Up Next
    42.6. Control Structures Home 42.8. Transaction Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-declarations.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-declarations.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-declarations.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-declarations.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.3. Declarations
    42.3. Declarations
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.3. Declarations

    42.3.1. Declaring Function Parameters
    42.3.2. ALIAS
    42.3.3. Copying Types
    42.3.4. Row Types
    42.3.5. Record Types
    42.3.6. Collation of PL/pgSQL Variables

    +42.3. Declarations

    42.3. Declarations
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.3. Declarations

    42.3.1. Declaring Function Parameters
    42.3.2. ALIAS
    42.3.3. Copying Types
    42.3.4. Row Types
    42.3.5. Record Types
    42.3.6. Collation of PL/pgSQL Variables

    All variables used in a block must be declared in the declarations section of the block. (The only exceptions are that the loop variable of a FOR loop @@ -415,4 +415,4 @@ This overrides the collations associated with the table columns, parameters, or local variables used in the expression, just as would happen in a plain SQL command. -

    Prev Up Next
    42.2. Structure of PL/pgSQL Home 42.4. Expressions
    \ No newline at end of file +

    Prev Up Next
    42.2. Structure of PL/pgSQL Home 42.4. Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-development-tips.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-development-tips.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-development-tips.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-development-tips.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.12. Tips for Developing in PL/pgSQL
    42.12. Tips for Developing in PL/pgSQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.12. Tips for Developing in PL/pgSQL

    42.12.1. Handling of Quotation Marks
    42.12.2. Additional Compile-Time and Run-Time Checks

    +42.12. Tips for Developing in PL/pgSQL

    42.12. Tips for Developing in PL/pgSQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.12. Tips for Developing in PL/pgSQL

    42.12.1. Handling of Quotation Marks
    42.12.2. Additional Compile-Time and Run-Time Checks

    One good way to develop in PL/pgSQL is to use the text editor of your choice to create your functions, and in another window, use @@ -225,4 +225,4 @@ (1 row)

    -

    Prev Up Next
    42.11. PL/pgSQL under the Hood Home 42.13. Porting from Oracle PL/SQL
    \ No newline at end of file +

    Prev Up Next
    42.11. PL/pgSQL under the Hood Home 42.13. Porting from Oracle PL/SQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-errors-and-messages.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-errors-and-messages.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-errors-and-messages.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-errors-and-messages.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.9. Errors and Messages
    42.9. Errors and Messages
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.9. Errors and Messages

    42.9.1. Reporting Errors and Messages
    42.9.2. Checking Assertions

    42.9.1. Reporting Errors and Messages

    +42.9. Errors and Messages

    42.9. Errors and Messages
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.9. Errors and Messages

    42.9.1. Reporting Errors and Messages
    42.9.2. Checking Assertions

    42.9.1. Reporting Errors and Messages

    Use the RAISE statement to report messages and raise errors. @@ -145,4 +145,4 @@ Note that ASSERT is meant for detecting program bugs, not for reporting ordinary error conditions. Use the RAISE statement, described above, for that. -

    Prev Up Next
    42.8. Transaction Management Home 42.10. Trigger Functions
    \ No newline at end of file +

    Prev Up Next
    42.8. Transaction Management Home 42.10. Trigger Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-expressions.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-expressions.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-expressions.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-expressions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.4. Expressions
    42.4. Expressions
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.4. Expressions

    +42.4. Expressions

    42.4. Expressions
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.4. Expressions

    All expressions used in PL/pgSQL statements are processed using the server's main SQL executor. For example, when you write @@ -36,4 +36,4 @@ not important to a PL/pgSQL user, but they are useful to know when trying to diagnose a problem. More information appears in Section 42.11.2. -

    Prev Up Next
    42.3. Declarations Home 42.5. Basic Statements
    \ No newline at end of file +

    Prev Up Next
    42.3. Declarations Home 42.5. Basic Statements
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-implementation.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-implementation.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-implementation.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.11. PL/pgSQL under the Hood
    42.11. PL/pgSQL under the Hood
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.11. PL/pgSQL under the Hood

    42.11.1. Variable Substitution
    42.11.2. Plan Caching

    +42.11. PL/pgSQL under the Hood

    42.11. PL/pgSQL under the Hood
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.11. PL/pgSQL under the Hood

    42.11.1. Variable Substitution
    42.11.2. Plan Caching

    This section discusses some implementation details that are frequently important for PL/pgSQL users to know.

    42.11.1. Variable Substitution

    @@ -265,4 +265,4 @@ on each execution as the programmer expects. Even though this happens to work as expected, it's not terribly efficient, so use of the now() function would still be a better idea. -

    Prev Up Next
    42.10. Trigger Functions Home 42.12. Tips for Developing in PL/pgSQL
    \ No newline at end of file +

    Prev Up Next
    42.10. Trigger Functions Home 42.12. Tips for Developing in PL/pgSQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-overview.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-overview.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-overview.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-overview.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.1. Overview
    42.1. Overview
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.1. Overview

    42.1.1. Advantages of Using PL/pgSQL
    42.1.2. Supported Argument and Result Data Types

    +42.1. Overview

    42.1. Overview
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.1. Overview

    42.1.1. Advantages of Using PL/pgSQL
    42.1.2. Supported Argument and Result Data Types

    PL/pgSQL is a loadable procedural language for the PostgreSQL database system. The design goals of PL/pgSQL were to create @@ -100,4 +100,4 @@ Specific examples appear in Section 42.3.1 and Section 42.6.1. -

    Prev Up Next
    Chapter 42. PL/pgSQL — SQL Procedural Language Home 42.2. Structure of PL/pgSQL
    \ No newline at end of file +

    Prev Up Next
    Chapter 42. PL/pgSQL — SQL Procedural Language Home 42.2. Structure of PL/pgSQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-porting.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-porting.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-porting.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-porting.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.13. Porting from Oracle PL/SQL
    42.13. Porting from Oracle PL/SQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.13. Porting from Oracle PL/SQL

    42.13.1. Porting Examples
    42.13.2. Other Things to Watch For
    42.13.3. Appendix

    +42.13. Porting from Oracle PL/SQL

    42.13. Porting from Oracle PL/SQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.13. Porting from Oracle PL/SQL

    42.13.1. Porting Examples
    42.13.2. Other Things to Watch For
    42.13.3. Appendix

    This section explains differences between PostgreSQL's PL/pgSQL language and Oracle's PL/SQL language, @@ -556,4 +556,4 @@ END; $$ LANGUAGE plpgsql STRICT IMMUTABLE; -

    Prev Up Next
    42.12. Tips for Developing in PL/pgSQL Home Chapter 43. PL/Tcl — Tcl Procedural Language
    \ No newline at end of file +
    Prev Up Next
    42.12. Tips for Developing in PL/pgSQL Home Chapter 43. PL/Tcl — Tcl Procedural Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-statements.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-statements.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-statements.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-statements.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.5. Basic Statements
    42.5. Basic Statements
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.5. Basic Statements

    42.5.1. Assignment
    42.5.2. Executing a Command with No Result
    42.5.3. Executing a Query with a Single-Row Result
    42.5.4. Executing Dynamic Commands
    42.5.5. Obtaining the Result Status
    42.5.6. Doing Nothing At All

    +42.5. Basic Statements

    42.5. Basic Statements
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.5. Basic Statements

    42.5.1. Assignment
    42.5.2. Executing a Command with No Result
    42.5.3. Executing a Query with a Single-Row Result
    42.5.4. Executing Dynamic Commands
    42.5.5. Obtaining the Result Status
    42.5.6. Doing Nothing At All

    In this section and the following ones, we describe all the statement types that are explicitly understood by PL/pgSQL. @@ -549,4 +549,4 @@ NULL statements are required for situations such as this. PL/pgSQL allows you to just write nothing, instead. -

    Prev Up Next
    42.4. Expressions Home 42.6. Control Structures
    \ No newline at end of file +

    Prev Up Next
    42.4. Expressions Home 42.6. Control Structures
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-structure.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-structure.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-structure.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-structure.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.2. Structure of PL/pgSQL
    42.2. Structure of PL/pgSQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.2. Structure of PL/pgSQL

    +42.2. Structure of PL/pgSQL

    42.2. Structure of PL/pgSQL
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.2. Structure of PL/pgSQL

    Functions written in PL/pgSQL are defined to the server by executing CREATE FUNCTION commands. Such a command would normally look like, say, @@ -105,4 +105,4 @@ Also, a block containing an EXCEPTION clause effectively forms a subtransaction that can be rolled back without affecting the outer transaction. For more about that see Section 42.6.8. -

    Prev Up Next
    42.1. Overview Home 42.3. Declarations
    \ No newline at end of file +

    Prev Up Next
    42.1. Overview Home 42.3. Declarations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-transactions.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-transactions.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-transactions.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-transactions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.8. Transaction Management
    42.8. Transaction Management
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.8. Transaction Management

    +42.8. Transaction Management

    42.8. Transaction Management
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.8. Transaction Management

    In procedures invoked by the CALL command as well as in anonymous code blocks (DO command), it is possible to end transactions using the @@ -79,4 +79,4 @@ ... RETURNING).

    A transaction cannot be ended inside a block with exception handlers. -

    Prev Up Next
    42.7. Cursors Home 42.9. Errors and Messages
    \ No newline at end of file +

    Prev Up Next
    42.7. Cursors Home 42.9. Errors and Messages
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql-trigger.html postgresql-13-13.12/doc/src/sgml/html/plpgsql-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql-trigger.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql-trigger.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -42.10. Trigger Functions
    42.10. Trigger Functions
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.10. Trigger Functions

    42.10.1. Triggers on Data Changes
    42.10.2. Triggers on Events

    +42.10. Trigger Functions

    42.10. Trigger Functions
    Prev UpChapter 42. PL/pgSQL — SQL Procedural LanguageHome Next

    42.10. Trigger Functions

    42.10.1. Triggers on Data Changes
    42.10.2. Triggers on Events

    PL/pgSQL can be used to define trigger functions on data changes or database events. A trigger function is created with the CREATE FUNCTION @@ -513,4 +513,4 @@ $$ LANGUAGE plpgsql; CREATE EVENT TRIGGER snitch ON ddl_command_start EXECUTE FUNCTION snitch(); -


    Prev Up Next
    42.9. Errors and Messages Home 42.11. PL/pgSQL under the Hood
    \ No newline at end of file +
    Prev Up Next
    42.9. Errors and Messages Home 42.11. PL/pgSQL under the Hood
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpgsql.html postgresql-13-13.12/doc/src/sgml/html/plpgsql.html --- postgresql-13-13.11/doc/src/sgml/html/plpgsql.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpgsql.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 42. PL/pgSQL — SQL Procedural Language
    Chapter 42. PL/pgSQL — SQL Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 42. PL/pgSQL — SQL Procedural Language

    Table of Contents

    42.1. Overview
    42.1.1. Advantages of Using PL/pgSQL
    42.1.2. Supported Argument and Result Data Types
    42.2. Structure of PL/pgSQL
    42.3. Declarations
    42.3.1. Declaring Function Parameters
    42.3.2. ALIAS
    42.3.3. Copying Types
    42.3.4. Row Types
    42.3.5. Record Types
    42.3.6. Collation of PL/pgSQL Variables
    42.4. Expressions
    42.5. Basic Statements
    42.5.1. Assignment
    42.5.2. Executing a Command with No Result
    42.5.3. Executing a Query with a Single-Row Result
    42.5.4. Executing Dynamic Commands
    42.5.5. Obtaining the Result Status
    42.5.6. Doing Nothing At All
    42.6. Control Structures
    42.6.1. Returning from a Function
    42.6.2. Returning from a Procedure
    42.6.3. Calling a Procedure
    42.6.4. Conditionals
    42.6.5. Simple Loops
    42.6.6. Looping through Query Results
    42.6.7. Looping through Arrays
    42.6.8. Trapping Errors
    42.6.9. Obtaining Execution Location Information
    42.7. Cursors
    42.7.1. Declaring Cursor Variables
    42.7.2. Opening Cursors
    42.7.3. Using Cursors
    42.7.4. Looping through a Cursor's Result
    42.8. Transaction Management
    42.9. Errors and Messages
    42.9.1. Reporting Errors and Messages
    42.9.2. Checking Assertions
    42.10. Trigger Functions
    42.10.1. Triggers on Data Changes
    42.10.2. Triggers on Events
    42.11. PL/pgSQL under the Hood
    42.11.1. Variable Substitution
    42.11.2. Plan Caching
    42.12. Tips for Developing in PL/pgSQL
    42.12.1. Handling of Quotation Marks
    42.12.2. Additional Compile-Time and Run-Time Checks
    42.13. Porting from Oracle PL/SQL
    42.13.1. Porting Examples
    42.13.2. Other Things to Watch For
    42.13.3. Appendix
    Prev Up Next
    41.1. Installing Procedural Languages Home 42.1. Overview
    \ No newline at end of file +Chapter 42. PL/pgSQL — SQL Procedural Language
    Chapter 42. PL/pgSQL — SQL Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 42. PL/pgSQL — SQL Procedural Language

    Table of Contents

    42.1. Overview
    42.1.1. Advantages of Using PL/pgSQL
    42.1.2. Supported Argument and Result Data Types
    42.2. Structure of PL/pgSQL
    42.3. Declarations
    42.3.1. Declaring Function Parameters
    42.3.2. ALIAS
    42.3.3. Copying Types
    42.3.4. Row Types
    42.3.5. Record Types
    42.3.6. Collation of PL/pgSQL Variables
    42.4. Expressions
    42.5. Basic Statements
    42.5.1. Assignment
    42.5.2. Executing a Command with No Result
    42.5.3. Executing a Query with a Single-Row Result
    42.5.4. Executing Dynamic Commands
    42.5.5. Obtaining the Result Status
    42.5.6. Doing Nothing At All
    42.6. Control Structures
    42.6.1. Returning from a Function
    42.6.2. Returning from a Procedure
    42.6.3. Calling a Procedure
    42.6.4. Conditionals
    42.6.5. Simple Loops
    42.6.6. Looping through Query Results
    42.6.7. Looping through Arrays
    42.6.8. Trapping Errors
    42.6.9. Obtaining Execution Location Information
    42.7. Cursors
    42.7.1. Declaring Cursor Variables
    42.7.2. Opening Cursors
    42.7.3. Using Cursors
    42.7.4. Looping through a Cursor's Result
    42.8. Transaction Management
    42.9. Errors and Messages
    42.9.1. Reporting Errors and Messages
    42.9.2. Checking Assertions
    42.10. Trigger Functions
    42.10.1. Triggers on Data Changes
    42.10.2. Triggers on Events
    42.11. PL/pgSQL under the Hood
    42.11.1. Variable Substitution
    42.11.2. Plan Caching
    42.12. Tips for Developing in PL/pgSQL
    42.12.1. Handling of Quotation Marks
    42.12.2. Additional Compile-Time and Run-Time Checks
    42.13. Porting from Oracle PL/SQL
    42.13.1. Porting Examples
    42.13.2. Other Things to Watch For
    42.13.3. Appendix
    Prev Up Next
    41.1. Installing Procedural Languages Home 42.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-data.html postgresql-13-13.12/doc/src/sgml/html/plpython-data.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-data.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-data.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.3. Data Values
    45.3. Data Values
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.3. Data Values

    45.3.1. Data Type Mapping
    45.3.2. Null, None
    45.3.3. Arrays, Lists
    45.3.4. Composite Types
    45.3.5. Set-Returning Functions

    +45.3. Data Values

    45.3. Data Values
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.3. Data Values

    45.3.1. Data Type Mapping
    45.3.2. Null, None
    45.3.3. Arrays, Lists
    45.3.4. Composite Types
    45.3.5. Set-Returning Functions

    Generally speaking, the aim of PL/Python is to provide a “natural” mapping between the PostgreSQL and the Python worlds. This informs the data mapping rules described @@ -353,4 +353,4 @@ SELECT * FROM multiout_simple_setof(3);

    -

    Prev Up Next
    45.2. PL/Python Functions Home 45.4. Sharing Data
    \ No newline at end of file +

    Prev Up Next
    45.2. PL/Python Functions Home 45.4. Sharing Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-database.html postgresql-13-13.12/doc/src/sgml/html/plpython-database.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-database.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-database.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.7. Database Access
    45.7. Database Access
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.7. Database Access

    45.7.1. Database Access Functions
    45.7.2. Trapping Errors

    +45.7. Database Access

    45.7. Database Access
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.7. Database Access

    45.7.1. Database Access Functions
    45.7.2. Trapping Errors

    The PL/Python language module automatically imports a Python module called plpy. The functions and constants in this module are available to you in the Python code as @@ -235,4 +235,4 @@ the exception object. This attribute is a string value containing the “SQLSTATE” error code. This approach provides approximately the same functionality -

    Prev Up Next
    45.6. Trigger Functions Home 45.8. Explicit Subtransactions
    \ No newline at end of file +

    Prev Up Next
    45.6. Trigger Functions Home 45.8. Explicit Subtransactions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-do.html postgresql-13-13.12/doc/src/sgml/html/plpython-do.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-do.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-do.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.5. Anonymous Code Blocks
    45.5. Anonymous Code Blocks
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.5. Anonymous Code Blocks

    +45.5. Anonymous Code Blocks

    45.5. Anonymous Code Blocks
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.5. Anonymous Code Blocks

    PL/Python also supports anonymous code blocks called with the DO statement: @@ -11,4 +11,4 @@ An anonymous code block receives no arguments, and whatever value it might return is discarded. Otherwise it behaves just like a function. -

    Prev Up Next
    45.4. Sharing Data Home 45.6. Trigger Functions
    \ No newline at end of file +

    Prev Up Next
    45.4. Sharing Data Home 45.6. Trigger Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-envar.html postgresql-13-13.12/doc/src/sgml/html/plpython-envar.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-envar.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-envar.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.11. Environment Variables
    45.11. Environment Variables
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.11. Environment Variables

    +45.11. Environment Variables

    45.11. Environment Variables
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.11. Environment Variables

    Some of the environment variables that are accepted by the Python interpreter can also be used to affect PL/Python behavior. They would need to be set in the environment of the main PostgreSQL @@ -14,4 +14,4 @@ of PL/Python that some of the environment variables listed on the python man page are only effective in a command-line interpreter and not an embedded Python interpreter.) -

    Prev Up Next
    45.10. Utility Functions Home Chapter 46. Server Programming Interface
    \ No newline at end of file +

    Prev Up Next
    45.10. Utility Functions Home Chapter 46. Server Programming Interface
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-funcs.html postgresql-13-13.12/doc/src/sgml/html/plpython-funcs.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-funcs.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-funcs.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.2. PL/Python Functions
    45.2. PL/Python Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.2. PL/Python Functions

    +45.2. PL/Python Functions

    45.2. PL/Python Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.2. PL/Python Functions

    Functions in PL/Python are declared via the standard CREATE FUNCTION syntax: @@ -85,4 +85,4 @@ But it is advisable not to rely on this implementation detail of PL/Python. It is better to treat the function parameters as read-only. -

    Prev Up Next
    45.1. Python 2 vs. Python 3 Home 45.3. Data Values
    \ No newline at end of file +

    Prev Up Next
    45.1. Python 2 vs. Python 3 Home 45.3. Data Values
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-python23.html postgresql-13-13.12/doc/src/sgml/html/plpython-python23.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-python23.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-python23.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.1. Python 2 vs. Python 3
    45.1. Python 2 vs. Python 3
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.1. Python 2 vs. Python 3

    +45.1. Python 2 vs. Python 3

    45.1. Python 2 vs. Python 3
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.1. Python 2 vs. Python 3

    PL/Python supports both the Python 2 and Python 3 language variants. (The PostgreSQL installation instructions might contain more precise information about the exact supported minor versions @@ -84,4 +84,4 @@ Python major versions in a session, which will abort the session if a mismatch is detected. It is possible, however, to use both PL/Python variants in the same database, from separate sessions. -

    Prev Up Next
    Chapter 45. PL/Python — Python Procedural Language Home 45.2. PL/Python Functions
    \ No newline at end of file +

    Prev Up Next
    Chapter 45. PL/Python — Python Procedural Language Home 45.2. PL/Python Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-sharing.html postgresql-13-13.12/doc/src/sgml/html/plpython-sharing.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-sharing.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-sharing.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.4. Sharing Data
    45.4. Sharing Data
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.4. Sharing Data

    +45.4. Sharing Data

    45.4. Sharing Data
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.4. Sharing Data

    The global dictionary SD is available to store private data between repeated calls to the same function. The global dictionary GD is public data, @@ -11,4 +11,4 @@ myfunc are not available to myfunc2. The exception is the data in the GD dictionary, as mentioned above. -

    Prev Up Next
    45.3. Data Values Home 45.5. Anonymous Code Blocks
    \ No newline at end of file +

    Prev Up Next
    45.3. Data Values Home 45.5. Anonymous Code Blocks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-subtransaction.html postgresql-13-13.12/doc/src/sgml/html/plpython-subtransaction.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-subtransaction.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-subtransaction.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.8. Explicit Subtransactions
    45.8. Explicit Subtransactions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.8. Explicit Subtransactions

    45.8.1. Subtransaction Context Managers
    45.8.2. Older Python Versions

    +45.8. Explicit Subtransactions

    45.8. Explicit Subtransactions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.8. Explicit Subtransactions

    45.8.1. Subtransaction Context Managers
    45.8.2. Older Python Versions

    Recovering from errors caused by database access as described in Section 45.7.2 can lead to an undesirable situation where some operations succeed before one of them fails, @@ -97,4 +97,4 @@ plpy.execute(plan, [result]) $$ LANGUAGE plpythonu;

    -

    Prev Up Next
    45.7. Database Access Home 45.9. Transaction Management
    \ No newline at end of file +

    Prev Up Next
    45.7. Database Access Home 45.9. Transaction Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-transactions.html postgresql-13-13.12/doc/src/sgml/html/plpython-transactions.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-transactions.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-transactions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.9. Transaction Management
    45.9. Transaction Management
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.9. Transaction Management

    +45.9. Transaction Management

    45.9. Transaction Management
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.9. Transaction Management

    In a procedure called from the top level or an anonymous code block (DO command) called from the top level it is possible to control transactions. To commit the current transaction, call @@ -28,4 +28,4 @@

    Transactions cannot be ended when an explicit subtransaction is active. -

    Prev Up Next
    45.8. Explicit Subtransactions Home 45.10. Utility Functions
    \ No newline at end of file +

    Prev Up Next
    45.8. Explicit Subtransactions Home 45.10. Utility Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-trigger.html postgresql-13-13.12/doc/src/sgml/html/plpython-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-trigger.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-trigger.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.6. Trigger Functions
    45.6. Trigger Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.6. Trigger Functions

    +45.6. Trigger Functions

    45.6. Trigger Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.6. Trigger Functions

    When a function is used as a trigger, the dictionary TD contains trigger-related values:

    TD["event"]

    @@ -37,4 +37,4 @@ is INSERT or UPDATE you can return "MODIFY" to indicate you've modified the new row. Otherwise the return value is ignored. -

    Prev Up Next
    45.5. Anonymous Code Blocks Home 45.7. Database Access
    \ No newline at end of file +

    Prev Up Next
    45.5. Anonymous Code Blocks Home 45.7. Database Access
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython-util.html postgresql-13-13.12/doc/src/sgml/html/plpython-util.html --- postgresql-13-13.11/doc/src/sgml/html/plpython-util.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython-util.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -45.10. Utility Functions
    45.10. Utility Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.10. Utility Functions

    +45.10. Utility Functions

    45.10. Utility Functions
    Prev UpChapter 45. PL/Python — Python Procedural LanguageHome Next

    45.10. Utility Functions

    The plpy module also provides the functions

    plpy.debug(msg, **kwargs)
    plpy.log(msg, **kwargs)
    plpy.info(msg, **kwargs)
    plpy.notice(msg, **kwargs)
    plpy.warning(msg, **kwargs)
    plpy.error(msg, **kwargs)
    plpy.fatal(msg, **kwargs)

    @@ -57,4 +57,4 @@ plpy.quote_nullable(newvalue), plpy.quote_literal(keyvalue)))

    -

    Prev Up Next
    45.9. Transaction Management Home 45.11. Environment Variables
    \ No newline at end of file +

    Prev Up Next
    45.9. Transaction Management Home 45.11. Environment Variables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/plpython.html postgresql-13-13.12/doc/src/sgml/html/plpython.html --- postgresql-13-13.11/doc/src/sgml/html/plpython.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/plpython.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 45. PL/Python — Python Procedural Language
    Chapter 45. PL/Python — Python Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 45. PL/Python — Python Procedural Language

    Table of Contents

    45.1. Python 2 vs. Python 3
    45.2. PL/Python Functions
    45.3. Data Values
    45.3.1. Data Type Mapping
    45.3.2. Null, None
    45.3.3. Arrays, Lists
    45.3.4. Composite Types
    45.3.5. Set-Returning Functions
    45.4. Sharing Data
    45.5. Anonymous Code Blocks
    45.6. Trigger Functions
    45.7. Database Access
    45.7.1. Database Access Functions
    45.7.2. Trapping Errors
    45.8. Explicit Subtransactions
    45.8.1. Subtransaction Context Managers
    45.8.2. Older Python Versions
    45.9. Transaction Management
    45.10. Utility Functions
    45.11. Environment Variables

    +Chapter 45. PL/Python — Python Procedural Language

    Chapter 45. PL/Python — Python Procedural Language
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 45. PL/Python — Python Procedural Language

    Table of Contents

    45.1. Python 2 vs. Python 3
    45.2. PL/Python Functions
    45.3. Data Values
    45.3.1. Data Type Mapping
    45.3.2. Null, None
    45.3.3. Arrays, Lists
    45.3.4. Composite Types
    45.3.5. Set-Returning Functions
    45.4. Sharing Data
    45.5. Anonymous Code Blocks
    45.6. Trigger Functions
    45.7. Database Access
    45.7.1. Database Access Functions
    45.7.2. Trapping Errors
    45.8. Explicit Subtransactions
    45.8.1. Subtransaction Context Managers
    45.8.2. Older Python Versions
    45.9. Transaction Management
    45.10. Utility Functions
    45.11. Environment Variables

    The PL/Python procedural language allows PostgreSQL functions and procedures to be written in the Python language. @@ -26,4 +26,4 @@ PL/Python during the installation process. (Refer to the installation instructions for more information.) Users of binary packages might find PL/Python in a separate subpackage. -

    Prev Up Next
    44.8. PL/Perl Under the Hood Home 45.1. Python 2 vs. Python 3
    \ No newline at end of file +

    Prev Up Next
    44.8. PL/Perl Under the Hood Home 45.1. Python 2 vs. Python 3
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-config.html postgresql-13-13.12/doc/src/sgml/html/pltcl-config.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-config.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-config.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.11. PL/Tcl Configuration
    43.11. PL/Tcl Configuration
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.11. PL/Tcl Configuration

    +43.11. PL/Tcl Configuration

    43.11. PL/Tcl Configuration
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.11. PL/Tcl Configuration

    This section lists configuration parameters that affect PL/Tcl.

    @@ -39,4 +39,4 @@ This parameter is exactly like pltcl.start_proc, except that it applies to PL/TclU. The referenced function must be written in the pltclu language. -

    Prev Up Next
    43.10. Transaction Management Home 43.12. Tcl Procedure Names
    \ No newline at end of file +

    Prev Up Next
    43.10. Transaction Management Home 43.12. Tcl Procedure Names
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-data.html postgresql-13-13.12/doc/src/sgml/html/pltcl-data.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-data.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-data.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,9 +1,9 @@ -43.3. Data Values in PL/Tcl
    43.3. Data Values in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.3. Data Values in PL/Tcl

    +43.3. Data Values in PL/Tcl

    43.3. Data Values in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.3. Data Values in PL/Tcl

    The argument values supplied to a PL/Tcl function's code are simply the input arguments converted to text form (just as if they had been displayed by a SELECT statement). Conversely, the return and return_next commands will accept any string that is acceptable input format for the function's declared result type, or for the specified column of a composite result type. -

    Prev Up Next
    43.2. PL/Tcl Functions and Arguments Home 43.4. Global Data in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.2. PL/Tcl Functions and Arguments Home 43.4. Global Data in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-dbaccess.html postgresql-13-13.12/doc/src/sgml/html/pltcl-dbaccess.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-dbaccess.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-dbaccess.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.5. Database Access from PL/Tcl
    43.5. Database Access from PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.5. Database Access from PL/Tcl

    +43.5. Database Access from PL/Tcl

    43.5. Database Access from PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.5. Database Access from PL/Tcl

    In this section, we follow the usual Tcl convention of using question marks, rather than brackets, to indicate an optional element in a syntax synopsis. The following commands are available to access @@ -190,4 +190,4 @@ and Section 43.8 for more information.

    -

    Prev Up Next
    43.4. Global Data in PL/Tcl Home 43.6. Trigger Functions in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.4. Global Data in PL/Tcl Home 43.6. Trigger Functions in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-error-handling.html postgresql-13-13.12/doc/src/sgml/html/pltcl-error-handling.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-error-handling.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-error-handling.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.8. Error Handling in PL/Tcl
    43.8. Error Handling in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.8. Error Handling in PL/Tcl

    +43.8. Error Handling in PL/Tcl

    43.8. Error Handling in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.8. Error Handling in PL/Tcl

    Tcl code within or called from a PL/Tcl function can raise an error, either by executing some invalid operation or by generating an error using the Tcl error command or @@ -57,4 +57,4 @@

    (The double colons explicitly specify that errorCode is a global variable.) -

    Prev Up Next
    43.7. Event Trigger Functions in PL/Tcl Home 43.9. Explicit Subtransactions in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.7. Event Trigger Functions in PL/Tcl Home 43.9. Explicit Subtransactions in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-event-trigger.html postgresql-13-13.12/doc/src/sgml/html/pltcl-event-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-event-trigger.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-event-trigger.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.7. Event Trigger Functions in PL/Tcl
    43.7. Event Trigger Functions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.7. Event Trigger Functions in PL/Tcl

    +43.7. Event Trigger Functions in PL/Tcl

    43.7. Event Trigger Functions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.7. Event Trigger Functions in PL/Tcl

    Event trigger functions can be written in PL/Tcl. PostgreSQL requires that a function that is to be called as an event trigger must be declared as a function with no @@ -27,4 +27,4 @@ CREATE EVENT TRIGGER tcl_a_snitch ON ddl_command_start EXECUTE FUNCTION tclsnitch();

    -

    Prev Up Next
    43.6. Trigger Functions in PL/Tcl Home 43.8. Error Handling in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.6. Trigger Functions in PL/Tcl Home 43.8. Error Handling in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-functions.html postgresql-13-13.12/doc/src/sgml/html/pltcl-functions.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-functions.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-functions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.2. PL/Tcl Functions and Arguments
    43.2. PL/Tcl Functions and Arguments
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.2. PL/Tcl Functions and Arguments

    +43.2. PL/Tcl Functions and Arguments

    43.2. PL/Tcl Functions and Arguments
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.2. PL/Tcl Functions and Arguments

    To create a function in the PL/Tcl language, use the standard CREATE FUNCTION syntax: @@ -138,4 +138,4 @@ } $$ LANGUAGE pltcl;

    -

    Prev Up Next
    43.1. Overview Home 43.3. Data Values in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.1. Overview Home 43.3. Data Values in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-global.html postgresql-13-13.12/doc/src/sgml/html/pltcl-global.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-global.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-global.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.4. Global Data in PL/Tcl
    43.4. Global Data in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.4. Global Data in PL/Tcl

    +43.4. Global Data in PL/Tcl

    43.4. Global Data in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.4. Global Data in PL/Tcl

    Sometimes it is useful to have some global data that is held between two calls to a function or is shared between different functions. @@ -42,4 +42,4 @@

    An example of using GD appears in the spi_execp example below. -

    Prev Up Next
    43.3. Data Values in PL/Tcl Home 43.5. Database Access from PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.3. Data Values in PL/Tcl Home 43.5. Database Access from PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-overview.html postgresql-13-13.12/doc/src/sgml/html/pltcl-overview.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-overview.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-overview.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.1. Overview
    43.1. Overview
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.1. Overview

    +43.1. Overview

    43.1. Overview
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.1. Overview

    PL/Tcl offers most of the capabilities a function writer has in the C language, with a few restrictions, and with the addition of the powerful string processing libraries that are available for @@ -40,4 +40,4 @@ CREATE EXTENSION command, for example CREATE EXTENSION pltcl or CREATE EXTENSION pltclu. -

    Prev Up Next
    Chapter 43. PL/Tcl — Tcl Procedural Language Home 43.2. PL/Tcl Functions and Arguments
    \ No newline at end of file +

    Prev Up Next
    Chapter 43. PL/Tcl — Tcl Procedural Language Home 43.2. PL/Tcl Functions and Arguments
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-procnames.html postgresql-13-13.12/doc/src/sgml/html/pltcl-procnames.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-procnames.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-procnames.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.12. Tcl Procedure Names
    43.12. Tcl Procedure Names
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.12. Tcl Procedure Names

    +43.12. Tcl Procedure Names

    43.12. Tcl Procedure Names
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.12. Tcl Procedure Names

    In PostgreSQL, the same function name can be used for different function definitions as long as the number of arguments or their types differ. Tcl, however, requires all procedure names to be distinct. @@ -10,4 +10,4 @@ and different argument types will be different Tcl procedures, too. This is not normally a concern for a PL/Tcl programmer, but it might be visible when debugging. -

    Prev Up Next
    43.11. PL/Tcl Configuration Home Chapter 44. PL/Perl — Perl Procedural Language
    \ No newline at end of file +

    Prev Up Next
    43.11. PL/Tcl Configuration Home Chapter 44. PL/Perl — Perl Procedural Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-subtransactions.html postgresql-13-13.12/doc/src/sgml/html/pltcl-subtransactions.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-subtransactions.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-subtransactions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.9. Explicit Subtransactions in PL/Tcl
    43.9. Explicit Subtransactions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.9. Explicit Subtransactions in PL/Tcl

    +43.9. Explicit Subtransactions in PL/Tcl

    43.9. Explicit Subtransactions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.9. Explicit Subtransactions in PL/Tcl

    Recovering from errors caused by database access as described in Section 43.8 can lead to an undesirable situation where some operations succeed before one of them fails, @@ -64,4 +64,4 @@ subtransaction to be rolled back. However, non-error exits out of the contained Tcl code (for instance, due to return) do not cause a rollback. -

    Prev Up Next
    43.8. Error Handling in PL/Tcl Home 43.10. Transaction Management
    \ No newline at end of file +

    Prev Up Next
    43.8. Error Handling in PL/Tcl Home 43.10. Transaction Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-transactions.html postgresql-13-13.12/doc/src/sgml/html/pltcl-transactions.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-transactions.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-transactions.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.10. Transaction Management
    43.10. Transaction Management
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.10. Transaction Management

    +43.10. Transaction Management

    43.10. Transaction Management
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.10. Transaction Management

    In a procedure called from the top level or an anonymous code block (DO command) called from the top level it is possible to control transactions. To commit the current transaction, call the @@ -30,4 +30,4 @@

    Transactions cannot be ended when an explicit subtransaction is active. -

    Prev Up Next
    43.9. Explicit Subtransactions in PL/Tcl Home 43.11. PL/Tcl Configuration
    \ No newline at end of file +

    Prev Up Next
    43.9. Explicit Subtransactions in PL/Tcl Home 43.11. PL/Tcl Configuration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl-trigger.html postgresql-13-13.12/doc/src/sgml/html/pltcl-trigger.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl-trigger.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl-trigger.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -43.6. Trigger Functions in PL/Tcl
    43.6. Trigger Functions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.6. Trigger Functions in PL/Tcl

    +43.6. Trigger Functions in PL/Tcl

    43.6. Trigger Functions in PL/Tcl
    Prev UpChapter 43. PL/Tcl — Tcl Procedural LanguageHome Next

    43.6. Trigger Functions in PL/Tcl

    Trigger functions can be written in PL/Tcl. PostgreSQL requires that a function that is to be called as a trigger must be declared as a function with no arguments @@ -112,4 +112,4 @@ Notice that the trigger function itself does not know the column name; that's supplied from the trigger arguments. This lets the trigger function be reused with different tables. -

    Prev Up Next
    43.5. Database Access from PL/Tcl Home 43.7. Event Trigger Functions in PL/Tcl
    \ No newline at end of file +

    Prev Up Next
    43.5. Database Access from PL/Tcl Home 43.7. Event Trigger Functions in PL/Tcl
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/pltcl.html postgresql-13-13.12/doc/src/sgml/html/pltcl.html --- postgresql-13-13.11/doc/src/sgml/html/pltcl.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/pltcl.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,8 +1,8 @@ -Chapter 43. PL/Tcl — Tcl Procedural Language
    Chapter 43. PL/Tcl — Tcl Procedural Language
    Prev UpPart V. Server ProgrammingHome Next
    Prev Up Next
    42.13. Porting from Oracle PL/SQL Home 43.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/populate.html postgresql-13-13.12/doc/src/sgml/html/populate.html --- postgresql-13-13.11/doc/src/sgml/html/populate.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/populate.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -14.4. Populating a Database
    14.4. Populating a Database
    Prev UpChapter 14. Performance TipsHome Next

    14.4. Populating a Database

    14.4.1. Disable Autocommit
    14.4.2. Use COPY
    14.4.3. Remove Indexes
    14.4.4. Remove Foreign Key Constraints
    14.4.5. Increase maintenance_work_mem
    14.4.6. Increase max_wal_size
    14.4.7. Disable WAL Archival and Streaming Replication
    14.4.8. Run ANALYZE Afterwards
    14.4.9. Some Notes about pg_dump

    +14.4. Populating a Database

    14.4. Populating a Database
    Prev UpChapter 14. Performance TipsHome Next

    14.4. Populating a Database

    14.4.1. Disable Autocommit
    14.4.2. Use COPY
    14.4.3. Remove Indexes
    14.4.4. Remove Foreign Key Constraints
    14.4.5. Increase maintenance_work_mem
    14.4.6. Increase max_wal_size
    14.4.7. Disable WAL Archival and Streaming Replication
    14.4.8. Run ANALYZE Afterwards
    14.4.9. Some Notes about pg_dump

    One might need to insert a large amount of data when first populating a database. This section contains some suggestions on how to make this process as efficient as possible. @@ -201,4 +201,4 @@ the --disable-triggers option — but realize that that eliminates, rather than just postpones, foreign key validation, and so it is possible to insert bad data if you use it. -

    Prev Up Next
    14.3. Controlling the Planner with Explicit JOIN Clauses Home 14.5. Non-Durable Settings
    \ No newline at end of file +

    Prev Up Next
    14.3. Controlling the Planner with Explicit JOIN Clauses Home 14.5. Non-Durable Settings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/postgres-fdw.html postgresql-13-13.12/doc/src/sgml/html/postgres-fdw.html --- postgresql-13-13.11/doc/src/sgml/html/postgres-fdw.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/postgres-fdw.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.33. postgres_fdw
    F.33. postgres_fdw
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.33. postgres_fdw

    F.33.1. FDW Options of postgres_fdw
    F.33.2. Connection Management
    F.33.3. Transaction Management
    F.33.4. Remote Query Optimization
    F.33.5. Remote Query Execution Environment
    F.33.6. Cross-Version Compatibility
    F.33.7. Examples
    F.33.8. Author

    +F.33. postgres_fdw

    F.33. postgres_fdw
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.33. postgres_fdw

    F.33.1. FDW Options of postgres_fdw
    F.33.2. Connection Management
    F.33.3. Transaction Management
    F.33.4. Remote Query Optimization
    F.33.5. Remote Query Execution Environment
    F.33.6. Cross-Version Compatibility
    F.33.7. Examples
    F.33.8. Author

    The postgres_fdw module provides the foreign-data wrapper postgres_fdw, which can be used to access data stored in external PostgreSQL servers. @@ -449,4 +449,4 @@ preferable to constructing foreign table definitions manually.

    F.33.8. Author

    Shigeru Hanada -

    Prev Up Next
    F.32. pg_visibility Home F.34. seg
    \ No newline at end of file +

    Prev Up Next
    F.32. pg_visibility Home F.34. seg
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/postgres-user.html postgresql-13-13.12/doc/src/sgml/html/postgres-user.html --- postgresql-13-13.11/doc/src/sgml/html/postgres-user.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/postgres-user.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.1. The PostgreSQL User Account
    18.1. The PostgreSQL User Account
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.1. The PostgreSQL User Account

    +18.1. The PostgreSQL User Account

    18.1. The PostgreSQL User Account
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.1. The PostgreSQL User Account

    As with any server daemon that is accessible to the outside world, it is advisable to run PostgreSQL under a separate user account. This user account should only own the data @@ -17,4 +17,4 @@ useradd or adduser. The user name postgres is often used, and is assumed throughout this book, but you can use another name if you like. -

    Prev Up Next
    Chapter 18. Server Setup and Operation Home 18.2. Creating a Database Cluster
    \ No newline at end of file +

    Prev Up Next
    Chapter 18. Server Setup and Operation Home 18.2. Creating a Database Cluster
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/preface.html postgresql-13-13.12/doc/src/sgml/html/preface.html --- postgresql-13-13.11/doc/src/sgml/html/preface.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/preface.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -Preface
    Preface
    Prev UpPostgreSQL 13.11 DocumentationHome Next
    Prev Up Next
    PostgreSQL 13.11 Documentation Home 1.  What Is PostgreSQL?
    \ No newline at end of file +

    Prev Up Next
    PostgreSQL 13.12 Documentation Home 1.  What Is PostgreSQL?
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/preventing-server-spoofing.html postgresql-13-13.12/doc/src/sgml/html/preventing-server-spoofing.html --- postgresql-13-13.11/doc/src/sgml/html/preventing-server-spoofing.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/preventing-server-spoofing.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.7. Preventing Server Spoofing
    18.7. Preventing Server Spoofing
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.7. Preventing Server Spoofing

    +18.7. Preventing Server Spoofing

    18.7. Preventing Server Spoofing
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.7. Preventing Server Spoofing

    While the server is running, it is not possible for a malicious user to take the place of the normal database server. However, when the server is down, it is possible for a local user to spoof the normal @@ -41,4 +41,4 @@ (Section 20.1) and use gss authentication with them. The TCP client must connect using gssencmode=require. -

    Prev Up Next
    18.6. Upgrading a PostgreSQL Cluster Home 18.8. Encryption Options
    \ No newline at end of file +

    Prev Up Next
    18.6. Upgrading a PostgreSQL Cluster Home 18.8. Encryption Options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/progress-reporting.html postgresql-13-13.12/doc/src/sgml/html/progress-reporting.html --- postgresql-13-13.11/doc/src/sgml/html/progress-reporting.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/progress-reporting.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -27.4. Progress Reporting
    27.4. Progress Reporting
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.4. Progress Reporting

    27.4.1. ANALYZE Progress Reporting
    27.4.2. CREATE INDEX Progress Reporting
    27.4.3. VACUUM Progress Reporting
    27.4.4. CLUSTER Progress Reporting
    27.4.5. Base Backup Progress Reporting

    +27.4. Progress Reporting

    27.4. Progress Reporting
    Prev UpChapter 27. Monitoring Database ActivityHome Next

    27.4. Progress Reporting

    27.4.1. ANALYZE Progress Reporting
    27.4.2. CREATE INDEX Progress Reporting
    27.4.3. VACUUM Progress Reporting
    27.4.4. CLUSTER Progress Reporting
    27.4.5. Base Backup Progress Reporting

    PostgreSQL has the ability to report the progress of certain commands during command execution. Currently, the only commands which support progress reporting are ANALYZE, @@ -574,4 +574,4 @@ --wal-method=fetch is specified in pg_basebackup. The backup will end when this phase is completed. -


    Prev Up Next
    27.3. Viewing Locks Home 27.5. Dynamic Tracing
    \ No newline at end of file +
    Prev Up Next
    27.3. Viewing Locks Home 27.5. Dynamic Tracing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-changes.html postgresql-13-13.12/doc/src/sgml/html/protocol-changes.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-changes.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-changes.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.10. Summary of Changes since Protocol 2.0
    52.10. Summary of Changes since Protocol 2.0
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.10. Summary of Changes since Protocol 2.0

    +52.10. Summary of Changes since Protocol 2.0

    52.10. Summary of Changes since Protocol 2.0
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.10. Summary of Changes since Protocol 2.0

    This section provides a quick checklist of changes, for the benefit of developers trying to update existing client libraries to protocol 3.0.

    @@ -70,4 +70,4 @@

    The EmptyQueryResponse ('I') message used to include an empty string parameter; this has been removed. -

    Prev Up Next
    52.9. Logical Replication Message Formats Home Chapter 53. PostgreSQL Coding Conventions
    \ No newline at end of file +

    Prev Up Next
    52.9. Logical Replication Message Formats Home Chapter 53. PostgreSQL Coding Conventions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-error-fields.html postgresql-13-13.12/doc/src/sgml/html/protocol-error-fields.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-error-fields.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-error-fields.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.8. Error and Notice Message Fields
    52.8. Error and Notice Message Fields
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.8. Error and Notice Message Fields

    +52.8. Error and Notice Message Fields

    52.8. Error and Notice Message Fields
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.8. Error and Notice Message Fields

    This section describes the fields that can appear in ErrorResponse and NoticeResponse messages. Each field type has a single-byte identification token. Note that any given field type should appear at most once per @@ -132,4 +132,4 @@ needs; in particular it should break long lines as needed. Newline characters appearing in the error message fields should be treated as paragraph breaks, not line breaks. -

    Prev Up Next
    52.7. Message Formats Home 52.9. Logical Replication Message Formats
    \ No newline at end of file +

    Prev Up Next
    52.7. Message Formats Home 52.9. Logical Replication Message Formats
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-flow.html postgresql-13-13.12/doc/src/sgml/html/protocol-flow.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-flow.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-flow.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.2. Message Flow
    52.2. Message Flow
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.2. Message Flow

    52.2.1. Start-up
    52.2.2. Simple Query
    52.2.3. Extended Query
    52.2.4. Pipelining
    52.2.5. Function Call
    52.2.6. COPY Operations
    52.2.7. Asynchronous Operations
    52.2.8. Canceling Requests in Progress
    52.2.9. Termination
    52.2.10. SSL Session Encryption
    52.2.11. GSSAPI Session Encryption

    +52.2. Message Flow

    52.2. Message Flow
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.2. Message Flow

    52.2.1. Start-up
    52.2.2. Simple Query
    52.2.3. Extended Query
    52.2.4. Pipelining
    52.2.5. Function Call
    52.2.6. COPY Operations
    52.2.7. Asynchronous Operations
    52.2.8. Canceling Requests in Progress
    52.2.9. Termination
    52.2.10. SSL Session Encryption
    52.2.11. GSSAPI Session Encryption

    This section describes the message flow and the semantics of each message type. (Details of the exact representation of each message appear in Section 52.7.) There are @@ -965,4 +965,4 @@ force GSSAPI encryption, the administrator can configure the server to reject unencrypted sessions as a byproduct of authentication checking. -

    Prev Up Next
    52.1. Overview Home 52.3. SASL Authentication
    \ No newline at end of file +

    Prev Up Next
    52.1. Overview Home 52.3. SASL Authentication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-logical-replication.html postgresql-13-13.12/doc/src/sgml/html/protocol-logical-replication.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-logical-replication.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-logical-replication.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.5. Logical Streaming Replication Protocol
    52.5. Logical Streaming Replication Protocol
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.5. Logical Streaming Replication Protocol

    52.5.1. Logical Streaming Replication Parameters
    52.5.2. Logical Replication Protocol Messages
    52.5.3. Logical Replication Protocol Message Flow

    +52.5. Logical Streaming Replication Protocol

    52.5. Logical Streaming Replication Protocol
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.5. Logical Streaming Replication Protocol

    52.5.1. Logical Streaming Replication Parameters
    52.5.2. Logical Replication Protocol Messages
    52.5.3. Logical Replication Protocol Message Flow

    This section describes the logical replication protocol, which is the message flow started by the START_REPLICATION SLOT slot_name @@ -71,4 +71,4 @@ cache the contents of Type messages, and first consult that cache to see if the type OID is defined there. If not, look up the type OID locally. -

    Prev Up Next
    52.4. Streaming Replication Protocol Home 52.6. Message Data Types
    \ No newline at end of file +

    Prev Up Next
    52.4. Streaming Replication Protocol Home 52.6. Message Data Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-logicalrep-message-formats.html postgresql-13-13.12/doc/src/sgml/html/protocol-logicalrep-message-formats.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-logicalrep-message-formats.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-logicalrep-message-formats.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.9. Logical Replication Message Formats
    52.9. Logical Replication Message Formats
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.9. Logical Replication Message Formats

    +52.9. Logical Replication Message Formats

    52.9. Logical Replication Message Formats
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.9. Logical Replication Message Formats

    This section describes the detailed format of each logical replication message. These messages are returned either by the replication slot SQL interface or are sent by a walsender. In case of a walsender they are encapsulated inside the replication @@ -308,4 +308,4 @@ n is the above length.

    -

    Prev Up Next
    52.8. Error and Notice Message Fields Home 52.10. Summary of Changes since Protocol 2.0
    \ No newline at end of file +

    Prev Up Next
    52.8. Error and Notice Message Fields Home 52.10. Summary of Changes since Protocol 2.0
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-message-formats.html postgresql-13-13.12/doc/src/sgml/html/protocol-message-formats.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-message-formats.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-message-formats.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.7. Message Formats
    52.7. Message Formats
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.7. Message Formats

    +52.7. Message Formats

    52.7. Message Formats
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.7. Message Formats

    This section describes the detailed format of each message. Each is marked to indicate that it can be sent by a frontend (F), a backend (B), or both (F & B). @@ -1377,4 +1377,4 @@ Length of message contents in bytes, including self.

    -

    Prev Up Next
    52.6. Message Data Types Home 52.8. Error and Notice Message Fields
    \ No newline at end of file +

    Prev Up Next
    52.6. Message Data Types Home 52.8. Error and Notice Message Fields
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-message-types.html postgresql-13-13.12/doc/src/sgml/html/protocol-message-types.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-message-types.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-message-types.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.6. Message Data Types
    52.6. Message Data Types
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.6. Message Data Types

    +52.6. Message Data Types

    52.6. Message Data Types
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.6. Message Data Types

    This section describes the base data types used in messages.

    @@ -41,4 +41,4 @@ If c is specified it is the exact value. Eg. Byte2, Byte1('\n').

    -

    Prev Up Next
    52.5. Logical Streaming Replication Protocol Home 52.7. Message Formats
    \ No newline at end of file +

    Prev Up Next
    52.5. Logical Streaming Replication Protocol Home 52.7. Message Formats
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-overview.html postgresql-13-13.12/doc/src/sgml/html/protocol-overview.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-overview.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-overview.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.1. Overview
    52.1. Overview
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.1. Overview

    52.1.1. Messaging Overview
    52.1.2. Extended Query Overview
    52.1.3. Formats and Format Codes

    +52.1. Overview

    52.1. Overview
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.1. Overview

    52.1.1. Messaging Overview
    52.1.2. Extended Query Overview
    52.1.3. Formats and Format Codes

    The protocol has separate phases for startup and normal operation. In the startup phase, the frontend opens a connection to the server and authenticates itself to the satisfaction of the server. (This might @@ -109,4 +109,4 @@ or source code to learn about the binary representation. Keep in mind that binary representations for complex data types might change across server versions; the text format is usually the more portable choice. -

    Prev Up Next
    Chapter 52. Frontend/Backend Protocol Home 52.2. Message Flow
    \ No newline at end of file +

    Prev Up Next
    Chapter 52. Frontend/Backend Protocol Home 52.2. Message Flow
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol-replication.html postgresql-13-13.12/doc/src/sgml/html/protocol-replication.html --- postgresql-13-13.11/doc/src/sgml/html/protocol-replication.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol-replication.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.4. Streaming Replication Protocol
    52.4. Streaming Replication Protocol
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.4. Streaming Replication Protocol

    +52.4. Streaming Replication Protocol

    52.4. Streaming Replication Protocol
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.4. Streaming Replication Protocol

    To initiate streaming replication, the frontend sends the replication parameter in the startup message. A Boolean value of true (or on, @@ -497,4 +497,4 @@ the server supports it.

    -

    Prev Up Next
    52.3. SASL Authentication Home 52.5. Logical Streaming Replication Protocol
    \ No newline at end of file +

    Prev Up Next
    52.3. SASL Authentication Home 52.5. Logical Streaming Replication Protocol
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/protocol.html postgresql-13-13.12/doc/src/sgml/html/protocol.html --- postgresql-13-13.11/doc/src/sgml/html/protocol.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/protocol.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 52. Frontend/Backend Protocol
    Chapter 52. Frontend/Backend Protocol
    Prev UpPart VII. InternalsHome Next

    Chapter 52. Frontend/Backend Protocol

    Table of Contents

    52.1. Overview
    52.1.1. Messaging Overview
    52.1.2. Extended Query Overview
    52.1.3. Formats and Format Codes
    52.2. Message Flow
    52.2.1. Start-up
    52.2.2. Simple Query
    52.2.3. Extended Query
    52.2.4. Pipelining
    52.2.5. Function Call
    52.2.6. COPY Operations
    52.2.7. Asynchronous Operations
    52.2.8. Canceling Requests in Progress
    52.2.9. Termination
    52.2.10. SSL Session Encryption
    52.2.11. GSSAPI Session Encryption
    52.3. SASL Authentication
    52.3.1. SCRAM-SHA-256 Authentication
    52.4. Streaming Replication Protocol
    52.5. Logical Streaming Replication Protocol
    52.5.1. Logical Streaming Replication Parameters
    52.5.2. Logical Replication Protocol Messages
    52.5.3. Logical Replication Protocol Message Flow
    52.6. Message Data Types
    52.7. Message Formats
    52.8. Error and Notice Message Fields
    52.9. Logical Replication Message Formats
    52.10. Summary of Changes since Protocol 2.0

    +Chapter 52. Frontend/Backend Protocol

    Chapter 52. Frontend/Backend Protocol
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    51.95. pg_views Home 52.1. Overview
    \ No newline at end of file +

    Prev Up Next
    51.95. pg_views Home 52.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-limit.html postgresql-13-13.12/doc/src/sgml/html/queries-limit.html --- postgresql-13-13.11/doc/src/sgml/html/queries-limit.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-limit.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.6. LIMIT and OFFSET
    7.6. LIMIT and OFFSET
    Prev UpChapter 7. QueriesHome Next

    7.6. LIMIT and OFFSET

    +7.6. LIMIT and OFFSET

    7.6. LIMIT and OFFSET
    Prev UpChapter 7. QueriesHome Next

    7.6. LIMIT and OFFSET

    LIMIT and OFFSET allow you to retrieve just a portion of the rows that are generated by the rest of the query: 

    @@ -45,4 +45,4 @@
    The rows skipped by an OFFSET clause still have to be
    computed inside the server; therefore a large OFFSET
    might be inefficient.
-
    Prev Up Next
    7.5. Sorting Rows Home 7.7. VALUES Lists
    \ No newline at end of file +

    Prev Up Next
    7.5. Sorting Rows Home 7.7. VALUES Lists
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-order.html postgresql-13-13.12/doc/src/sgml/html/queries-order.html --- postgresql-13-13.11/doc/src/sgml/html/queries-order.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-order.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.5. Sorting Rows
    7.5. Sorting Rows
    Prev UpChapter 7. QueriesHome Next

    7.5. Sorting Rows

    +7.5. Sorting Rows

    7.5. Sorting Rows
    Prev UpChapter 7. QueriesHome Next

    7.5. Sorting Rows

    After a query has produced an output table (after the select list has been processed) it can optionally be sorted. If sorting is not chosen, the rows will be returned in an unspecified order. The actual @@ -73,4 +73,4 @@ > operators correspond to this sort ordering, but a user-defined data type's designer could choose to do something different. -

    Prev Up Next
    7.4. Combining Queries Home 7.6. LIMIT and OFFSET
    \ No newline at end of file +

    Prev Up Next
    7.4. Combining Queries Home 7.6. LIMIT and OFFSET
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-overview.html postgresql-13-13.12/doc/src/sgml/html/queries-overview.html --- postgresql-13-13.11/doc/src/sgml/html/queries-overview.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-overview.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -7.1. Overview
    7.1. Overview
    Prev UpChapter 7. QueriesHome Next

    7.1. Overview

    +7.1. Overview

    7.1. Overview
    Prev UpChapter 7. QueriesHome Next

    7.1. Overview

    The process of retrieving or the command to retrieve data from a database is called a query. In SQL the SELECT command is @@ -50,4 +50,4 @@ 

     SELECT random();

    -

    Prev Up Next
    Chapter 7. Queries Home 7.2. Table Expressions
    \ No newline at end of file +

    Prev Up Next
    Chapter 7. Queries Home 7.2. Table Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-select-lists.html postgresql-13-13.12/doc/src/sgml/html/queries-select-lists.html --- postgresql-13-13.11/doc/src/sgml/html/queries-select-lists.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-select-lists.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.3. Select Lists
    7.3. Select Lists
    Prev UpChapter 7. QueriesHome Next

    7.3. Select Lists

    7.3.1. Select-List Items
    7.3.2. Column Labels
    7.3.3. DISTINCT

    +7.3. Select Lists

    7.3. Select Lists
    Prev UpChapter 7. QueriesHome Next

    7.3. Select Lists

    7.3.1. Select-List Items
    7.3.2. Column Labels
    7.3.3. DISTINCT

    As shown in the previous section, the table expression in the SELECT command constructs an intermediate virtual table by possibly combining @@ -114,4 +114,4 @@ GROUP BY and subqueries in FROM, this construct can be avoided, but it is often the most convenient alternative. -

    Prev Up Next
    7.2. Table Expressions Home 7.4. Combining Queries
    \ No newline at end of file +

    Prev Up Next
    7.2. Table Expressions Home 7.4. Combining Queries
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-table-expressions.html postgresql-13-13.12/doc/src/sgml/html/queries-table-expressions.html --- postgresql-13-13.11/doc/src/sgml/html/queries-table-expressions.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-table-expressions.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.2. Table Expressions
    7.2. Table Expressions
    Prev UpChapter 7. QueriesHome Next

    7.2. Table Expressions

    7.2.1. The FROM Clause
    7.2.2. The WHERE Clause
    7.2.3. The GROUP BY and HAVING Clauses
    7.2.4. GROUPING SETS, CUBE, and ROLLUP
    7.2.5. Window Function Processing

    +7.2. Table Expressions

    7.2. Table Expressions
    Prev UpChapter 7. QueriesHome Next

    7.2. Table Expressions

    7.2.1. The FROM Clause
    7.2.2. The WHERE Clause
    7.2.3. The GROUP BY and HAVING Clauses
    7.2.4. GROUPING SETS, CUBE, and ROLLUP
    7.2.5. Window Function Processing

    A table expression computes a table. The table expression contains a FROM clause that is optionally followed by WHERE, GROUP BY, and @@ -543,7 +543,7 @@ key word is optional; the function's arguments can contain references to columns provided by preceding FROM items in any case.

    - A LATERAL item can appear at top level in the + A LATERAL item can appear at the top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that are on the left-hand side of a JOIN that it is on the right-hand side of. @@ -986,4 +986,4 @@ It is not recommended to rely on this, however. Use an explicit top-level ORDER BY clause if you want to be sure the results are sorted in a particular way. -

    Prev Up Next
    7.1. Overview Home 7.3. Select Lists
    \ No newline at end of file +

    Prev Up Next
    7.1. Overview Home 7.3. Select Lists
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-union.html postgresql-13-13.12/doc/src/sgml/html/queries-union.html --- postgresql-13-13.11/doc/src/sgml/html/queries-union.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-union.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.4. Combining Queries
    7.4. Combining Queries
    Prev UpChapter 7. QueriesHome Next

    7.4. Combining Queries

    +7.4. Combining Queries

    7.4. Combining Queries
    Prev UpChapter 7. QueriesHome Next

    7.4. Combining Queries

    The results of two queries can be combined using the set operations union, intersection, and difference. The syntax is 

    @@ -73,4 +73,4 @@
 
     SELECT a FROM b UNION (SELECT x FROM y LIMIT 10)
 
    
-
    Prev Up Next
    7.3. Select Lists Home 7.5. Sorting Rows
    \ No newline at end of file +

    Prev Up Next
    7.3. Select Lists Home 7.5. Sorting Rows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-values.html postgresql-13-13.12/doc/src/sgml/html/queries-values.html --- postgresql-13-13.11/doc/src/sgml/html/queries-values.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-values.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.7. VALUES Lists
    7.7. VALUES Lists
    Prev UpChapter 7. QueriesHome Next

    7.7. VALUES Lists

    +7.7. VALUES Lists

    7.7. VALUES Lists
    Prev UpChapter 7. QueriesHome Next

    7.7. VALUES Lists

    VALUES provides a way to generate a “constant table” that can be used in a query without having to actually create and populate a table on-disk. The syntax is @@ -57,4 +57,4 @@ and next most commonly as a subquery.

    For more information see VALUES. -

    Prev Up Next
    7.6. LIMIT and OFFSET Home 7.8. WITH Queries (Common Table Expressions)
    \ No newline at end of file +

    Prev Up Next
    7.6. LIMIT and OFFSET Home 7.8. WITH Queries (Common Table Expressions)
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries-with.html postgresql-13-13.12/doc/src/sgml/html/queries-with.html --- postgresql-13-13.11/doc/src/sgml/html/queries-with.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries-with.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -7.8. WITH Queries (Common Table Expressions)
    7.8. WITH Queries (Common Table Expressions)
    Prev UpChapter 7. QueriesHome Next

    7.8. WITH Queries (Common Table Expressions)

    7.8.1. SELECT in WITH
    7.8.2. Data-Modifying Statements in WITH

    +7.8. WITH Queries (Common Table Expressions)

    7.8. WITH Queries (Common Table Expressions)
    Prev UpChapter 7. QueriesHome Next

    7.8. WITH Queries (Common Table Expressions)

    7.8.1. SELECT in WITH
    7.8.2. Data-Modifying Statements in WITH

    WITH provides a way to write auxiliary statements for use in a larger query. These statements, which are often referred to as Common Table Expressions or CTEs, can be thought of as defining @@ -422,4 +422,4 @@ At present, any table used as the target of a data-modifying statement in WITH must not have a conditional rule, nor an ALSO rule, nor an INSTEAD rule that expands to multiple statements. -

    Prev Up Next
    7.7. VALUES Lists Home Chapter 8. Data Types
    \ No newline at end of file +

    Prev Up Next
    7.7. VALUES Lists Home Chapter 8. Data Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/queries.html postgresql-13-13.12/doc/src/sgml/html/queries.html --- postgresql-13-13.11/doc/src/sgml/html/queries.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/queries.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,6 +1,6 @@ -Chapter 7. Queries
    Chapter 7. Queries
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    6.4. Returning Data from Modified Rows Home 7.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/query-path.html postgresql-13-13.12/doc/src/sgml/html/query-path.html --- postgresql-13-13.11/doc/src/sgml/html/query-path.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/query-path.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.1. The Path of a Query
    50.1. The Path of a Query
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.1. The Path of a Query

    +50.1. The Path of a Query

    50.1. The Path of a Query
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.1. The Path of a Query

    Here we give a short overview of the stages a query has to pass in order to obtain a result.

    1. @@ -52,4 +52,4 @@ In the following sections we will cover each of the above listed items in more detail to give a better understanding of PostgreSQL's internal control and data structures. -

    Prev Up Next
    Chapter 50. Overview of PostgreSQL Internals Home 50.2. How Connections Are Established
    \ No newline at end of file +

    Prev Up Next
    Chapter 50. Overview of PostgreSQL Internals Home 50.2. How Connections Are Established
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/querytree.html postgresql-13-13.12/doc/src/sgml/html/querytree.html --- postgresql-13-13.11/doc/src/sgml/html/querytree.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/querytree.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.1. The Query Tree
    40.1. The Query Tree
    Prev UpChapter 40. The Rule SystemHome Next

    40.1. The Query Tree

    +40.1. The Query Tree

    40.1. The Query Tree
    Prev UpChapter 40. The Rule SystemHome Next

    40.1. The Query Tree

    To understand how the rule system works it is necessary to know when it is invoked and what its input and results are.

    @@ -149,4 +149,4 @@ doesn't have much to do with the fundamentals of the rule system.

    -

    Prev Up Next
    Chapter 40. The Rule System Home 40.2. Views and the Rule System
    \ No newline at end of file +

    Prev Up Next
    Chapter 40. The Rule System Home 40.2. Views and the Rule System
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rangetypes.html postgresql-13-13.12/doc/src/sgml/html/rangetypes.html --- postgresql-13-13.11/doc/src/sgml/html/rangetypes.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rangetypes.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.17. Range Types
    8.17. Range Types
    Prev UpChapter 8. Data TypesHome Next
    Prev Up Next
    8.16. Composite Types Home 8.18. Domain Types
    \ No newline at end of file +

    Prev Up Next
    8.16. Composite Types Home 8.18. Domain Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/recovery-config.html postgresql-13-13.12/doc/src/sgml/html/recovery-config.html --- postgresql-13-13.11/doc/src/sgml/html/recovery-config.html 2023-05-08 21:34:18.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/recovery-config.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,10 +1,10 @@ -O.1. recovery.conf file merged into postgresql.conf
    O.1. recovery.conf file merged into postgresql.conf
    Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

    O.1. recovery.conf file merged into postgresql.conf

    +O.1. recovery.conf file merged into postgresql.conf

    O.1. recovery.conf file merged into postgresql.conf
    Prev UpAppendix O. Obsolete or Renamed FeaturesHome Next

    O.1. recovery.conf file merged into postgresql.conf

    PostgreSQL 11 and below used a configuration file named recovery.conf to manage replicas and standbys. Support for this file was removed in PostgreSQL 12. See - the release notes for PostgreSQL 12 for details + the release notes for PostgreSQL 12 for details on this change.

    On PostgreSQL 12 and above, @@ -28,4 +28,4 @@ setting has been removed. A standby.signal file in the data directory is used instead. See Standby Server Operation for details. -

    Prev Up Next
    Appendix O. Obsolete or Renamed Features Home O.2. pg_xlogdump renamed to pg_waldump
    \ No newline at end of file +

    Prev Up Next
    Appendix O. Obsolete or Renamed Features Home O.2. pg_xlogdump renamed to pg_waldump
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/reference-client.html postgresql-13-13.12/doc/src/sgml/html/reference-client.html --- postgresql-13-13.11/doc/src/sgml/html/reference-client.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/reference-client.html 2023-08-07 20:32:28.000000000 +0000 @@ -1,5 +1,5 @@ -PostgreSQL Client Applications
    PostgreSQL Client Applications
    Prev UpPart VI. ReferenceHome Next

    PostgreSQL Client Applications

    +PostgreSQL Client Applications

    PostgreSQL Client Applications
    Prev UpPart VI. ReferenceHome Next

    PostgreSQL Client Applications

    This part contains reference information for PostgreSQL client applications and utilities. Not all of these commands are of general utility; some @@ -20,4 +20,4 @@

    pg_verifybackup — verify the integrity of a base backup of a PostgreSQL cluster
    psql — PostgreSQL interactive terminal -
    reindexdb — reindex a PostgreSQL database
    vacuumdb — garbage-collect and analyze a PostgreSQL database
    Prev Up Next
    VALUES Home clusterdb
    \ No newline at end of file +
    reindexdb — reindex a PostgreSQL database
    vacuumdb — garbage-collect and analyze a PostgreSQL database
    Prev Up Next
    VALUES Home clusterdb
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/reference-server.html postgresql-13-13.12/doc/src/sgml/html/reference-server.html --- postgresql-13-13.11/doc/src/sgml/html/reference-server.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/reference-server.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,8 +1,8 @@ -PostgreSQL Server Applications
    PostgreSQL Server Applications
    Prev UpPart VI. ReferenceHome Next

    PostgreSQL Server Applications

    +PostgreSQL Server Applications

    PostgreSQL Server Applications
    Prev UpPart VI. ReferenceHome Next

    PostgreSQL Server Applications

    This part contains reference information for PostgreSQL server applications and support utilities. These commands can only be run usefully on the host where the database server resides. Other utility programs are listed in PostgreSQL Client Applications. -

    Table of Contents

    initdb — create a new PostgreSQL database cluster
    pg_archivecleanup — clean up PostgreSQL WAL archive files
    pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster
    pg_controldata — display control information of a PostgreSQL database cluster
    pg_ctl — initialize, start, stop, or control a PostgreSQL server
    pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster
    pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL
    pg_test_timing — measure timing overhead
    pg_upgrade — upgrade a PostgreSQL server instance
    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster
    postgres — PostgreSQL database server
    postmaster — PostgreSQL database server
    Prev Up Next
    vacuumdb Home initdb
    \ No newline at end of file +

    Table of Contents

    initdb — create a new PostgreSQL database cluster
    pg_archivecleanup — clean up PostgreSQL WAL archive files
    pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster
    pg_controldata — display control information of a PostgreSQL database cluster
    pg_ctl — initialize, start, stop, or control a PostgreSQL server
    pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster
    pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL
    pg_test_timing — measure timing overhead
    pg_upgrade — upgrade a PostgreSQL server instance
    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster
    postgres — PostgreSQL database server
    postmaster — PostgreSQL database server
    Prev Up Next
    vacuumdb Home initdb
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/reference.html postgresql-13-13.12/doc/src/sgml/html/reference.html --- postgresql-13-13.11/doc/src/sgml/html/reference.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/reference.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -Part VI. Reference
    Part VI. Reference
    Prev UpPostgreSQL 13.11 DocumentationHome Next

    Part VI. Reference

    +Part VI. Reference

    Part VI. Reference
    Prev UpPostgreSQL 13.12 DocumentationHome Next

    Part VI. Reference

    The entries in this Reference are meant to provide in reasonable length an authoritative, complete, and formal summary about their respective subjects. More information about the use of @@ -27,4 +27,4 @@

    pg_verifybackup — verify the integrity of a base backup of a PostgreSQL cluster
    psql — PostgreSQL interactive terminal -
    reindexdb — reindex a PostgreSQL database
    vacuumdb — garbage-collect and analyze a PostgreSQL database
    III. PostgreSQL Server Applications
    initdb — create a new PostgreSQL database cluster
    pg_archivecleanup — clean up PostgreSQL WAL archive files
    pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster
    pg_controldata — display control information of a PostgreSQL database cluster
    pg_ctl — initialize, start, stop, or control a PostgreSQL server
    pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster
    pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL
    pg_test_timing — measure timing overhead
    pg_upgrade — upgrade a PostgreSQL server instance
    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster
    postgres — PostgreSQL database server
    postmaster — PostgreSQL database server
    Prev Up Next
    48.8. Synchronous Replication Support for Logical Decoding Home SQL Commands
    \ No newline at end of file +
    reindexdb — reindex a PostgreSQL database
    vacuumdb — garbage-collect and analyze a PostgreSQL database
    III. PostgreSQL Server Applications
    initdb — create a new PostgreSQL database cluster
    pg_archivecleanup — clean up PostgreSQL WAL archive files
    pg_checksums — enable, disable or check data checksums in a PostgreSQL database cluster
    pg_controldata — display control information of a PostgreSQL database cluster
    pg_ctl — initialize, start, stop, or control a PostgreSQL server
    pg_resetwal — reset the write-ahead log and other control information of a PostgreSQL database cluster
    pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
    pg_test_fsync — determine fastest wal_sync_method for PostgreSQL
    pg_test_timing — measure timing overhead
    pg_upgrade — upgrade a PostgreSQL server instance
    pg_waldump — display a human-readable rendering of the write-ahead log of a PostgreSQL database cluster
    postgres — PostgreSQL database server
    postmaster — PostgreSQL database server
    Prev Up Next
    48.8. Synchronous Replication Support for Logical Decoding Home SQL Commands
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress-coverage.html postgresql-13-13.12/doc/src/sgml/html/regress-coverage.html --- postgresql-13-13.11/doc/src/sgml/html/regress-coverage.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress-coverage.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -32.5. Test Coverage Examination
    32.5. Test Coverage Examination
    Prev UpChapter 32. Regression TestsHome Next

    32.5. Test Coverage Examination

    +32.5. Test Coverage Examination

    32.5. Test Coverage Examination
    Prev UpChapter 32. Regression TestsHome Next

    32.5. Test Coverage Examination

    The PostgreSQL source code can be compiled with coverage testing instrumentation, so that it becomes possible to examine which parts of the code are covered by the regression tests or any other @@ -33,4 +33,4 @@ 

     make coverage-clean

    -

    Prev Up Next
    32.4. TAP Tests Home Part IV. Client Interfaces
    \ No newline at end of file +

    Prev Up Next
    32.4. TAP Tests Home Part IV. Client Interfaces
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress-evaluation.html postgresql-13-13.12/doc/src/sgml/html/regress-evaluation.html --- postgresql-13-13.11/doc/src/sgml/html/regress-evaluation.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress-evaluation.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -32.2. Test Evaluation
    32.2. Test Evaluation
    Prev UpChapter 32. Regression TestsHome Next

    32.2. Test Evaluation

    32.2.1. Error Message Differences
    32.2.2. Locale Differences
    32.2.3. Date and Time Differences
    32.2.4. Floating-Point Differences
    32.2.5. Row Ordering Differences
    32.2.6. Insufficient Stack Depth
    32.2.7. The “random” Test
    32.2.8. Configuration Parameters

    +32.2. Test Evaluation

    32.2. Test Evaluation
    Prev UpChapter 32. Regression TestsHome Next

    32.2. Test Evaluation

    32.2.1. Error Message Differences
    32.2.2. Locale Differences
    32.2.3. Date and Time Differences
    32.2.4. Floating-Point Differences
    32.2.5. Row Ordering Differences
    32.2.6. Insufficient Stack Depth
    32.2.7. The “random” Test
    32.2.8. Configuration Parameters

    Some properly installed and fully functional PostgreSQL installations can “fail” some of these regression tests due to @@ -163,4 +163,4 @@ parameters such as enable_seqscan or enable_indexscan could cause plan changes that would affect the results of tests that use EXPLAIN. -

    Prev Up Next
    32.1. Running the Tests Home 32.3. Variant Comparison Files
    \ No newline at end of file +

    Prev Up Next
    32.1. Running the Tests Home 32.3. Variant Comparison Files
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress-run.html postgresql-13-13.12/doc/src/sgml/html/regress-run.html --- postgresql-13-13.11/doc/src/sgml/html/regress-run.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress-run.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -32.1. Running the Tests
    32.1. Running the Tests
    Prev UpChapter 32. Regression TestsHome Next

    32.1. Running the Tests

    32.1.1. Running the Tests Against a Temporary Installation
    32.1.2. Running the Tests Against an Existing Installation
    32.1.3. Additional Test Suites
    32.1.4. Locale and Encoding
    32.1.5. Extra Tests
    32.1.6. Testing Hot Standby

    +32.1. Running the Tests

    32.1. Running the Tests
    Prev UpChapter 32. Regression TestsHome Next

    32.1. Running the Tests

    32.1.1. Running the Tests Against a Temporary Installation
    32.1.2. Running the Tests Against an Existing Installation
    32.1.3. Additional Test Suites
    32.1.4. Locale and Encoding
    32.1.5. Extra Tests
    32.1.6. Testing Hot Standby

    The regression tests can be run against an already installed and running server, or using a temporary installation within the build tree. Furthermore, there is a “parallel” and a @@ -267,4 +267,4 @@ Some extreme behaviors can also be generated on the primary using the script src/test/regress/sql/hs_primary_extremes.sql to allow the behavior of the standby to be tested. -

    Prev Up Next
    Chapter 32. Regression Tests Home 32.2. Test Evaluation
    \ No newline at end of file +

    Prev Up Next
    Chapter 32. Regression Tests Home 32.2. Test Evaluation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress-tap.html postgresql-13-13.12/doc/src/sgml/html/regress-tap.html --- postgresql-13-13.11/doc/src/sgml/html/regress-tap.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress-tap.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -32.4. TAP Tests
    32.4. TAP Tests
    Prev UpChapter 32. Regression TestsHome Next

    32.4. TAP Tests

    +32.4. TAP Tests

    32.4. TAP Tests
    Prev UpChapter 32. Regression TestsHome Next

    32.4. TAP Tests

    Various tests, particularly the client program tests under src/bin, use the Perl TAP tools and are run using the Perl testing program prove. You can pass @@ -39,4 +39,4 @@ subdirectories contain both traditional-style and TAP-style tests, meaning that make installcheck will produce a mix of results from temporary servers and the already-running test server. -

    Prev Up Next
    32.3. Variant Comparison Files Home 32.5. Test Coverage Examination
    \ No newline at end of file +

    Prev Up Next
    32.3. Variant Comparison Files Home 32.5. Test Coverage Examination
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress-variant.html postgresql-13-13.12/doc/src/sgml/html/regress-variant.html --- postgresql-13-13.11/doc/src/sgml/html/regress-variant.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress-variant.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -32.3. Variant Comparison Files
    32.3. Variant Comparison Files
    Prev UpChapter 32. Regression TestsHome Next

    32.3. Variant Comparison Files

    +32.3. Variant Comparison Files

    32.3. Variant Comparison Files
    Prev UpChapter 32. Regression TestsHome Next

    32.3. Variant Comparison Files

    Since some of the tests inherently produce environment-dependent results, we have provided ways to specify alternate “expected” result files. Each regression test can have several comparison files @@ -74,4 +74,4 @@ the variant that seems to work best. Therefore it is safest to use this mechanism only for variant results that you are willing to consider equally valid in all contexts. -

    Prev Up Next
    32.2. Test Evaluation Home 32.4. TAP Tests
    \ No newline at end of file +

    Prev Up Next
    32.2. Test Evaluation Home 32.4. TAP Tests
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/regress.html postgresql-13-13.12/doc/src/sgml/html/regress.html --- postgresql-13-13.11/doc/src/sgml/html/regress.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/regress.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,7 +1,7 @@ -Chapter 32. Regression Tests
    Chapter 32. Regression Tests
    Prev UpPart III. Server AdministrationHome Next

    Chapter 32. Regression Tests

    Table of Contents

    32.1. Running the Tests
    32.1.1. Running the Tests Against a Temporary Installation
    32.1.2. Running the Tests Against an Existing Installation
    32.1.3. Additional Test Suites
    32.1.4. Locale and Encoding
    32.1.5. Extra Tests
    32.1.6. Testing Hot Standby
    32.2. Test Evaluation
    32.2.1. Error Message Differences
    32.2.2. Locale Differences
    32.2.3. Date and Time Differences
    32.2.4. Floating-Point Differences
    32.2.5. Row Ordering Differences
    32.2.6. Insufficient Stack Depth
    32.2.7. The “random” Test
    32.2.8. Configuration Parameters
    32.3. Variant Comparison Files
    32.4. TAP Tests
    32.5. Test Coverage Examination

    +Chapter 32. Regression Tests

    Chapter 32. Regression Tests
    Prev UpPart III. Server AdministrationHome Next
    Prev Up Next
    31.4. Extensibility Home 32.1. Running the Tests
    \ No newline at end of file +

    Prev Up Next
    31.4. Extensibility Home 32.1. Running the Tests
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-1.html postgresql-13-13.12/doc/src/sgml/html/release-13-1.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-1.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-1.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,11 +1,11 @@ -E.11. Release 13.1
    E.11. Release 13.1
    Prev UpAppendix E. Release NotesHome Next

    E.11. Release 13.1

    E.11.1. Migration to Version 13.1
    E.11.2. Changes

    Release date: 2020-11-12

    +E.12. Release 13.1

    E.12. Release 13.1
    Prev UpAppendix E. Release NotesHome Next

    E.12. Release 13.1

    E.12.1. Migration to Version 13.1
    E.12.2. Changes

    Release date: 2020-11-12

    This release contains a variety of fixes from 13.0. For information about new features in major release 13, see - Section E.12. -

    E.11.1. Migration to Version 13.1

    + Section E.13. +

    E.12.1. Migration to Version 13.1

    A dump/restore is not required for those running 13.X. -

    E.11.2. Changes

    • +

    E.12.2. Changes

    • Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) @@ -322,4 +322,4 @@ branches. This change also ensures that strftime() does not change errno unless it fails. -

    Prev Up Next
    E.10. Release 13.2 Home E.12. Release 13
    \ No newline at end of file +

    Prev Up Next
    E.11. Release 13.2 Home E.13. Release 13
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-10.html postgresql-13-13.12/doc/src/sgml/html/release-13-10.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-10.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-10.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.2. Release 13.10
    E.2. Release 13.10
    Prev UpAppendix E. Release NotesHome Next

    E.2. Release 13.10

    E.2.1. Migration to Version 13.10
    E.2.2. Changes

    Release date: 2023-02-09

    +E.3. Release 13.10

    E.3. Release 13.10
    Prev UpAppendix E. Release NotesHome Next

    E.3. Release 13.10

    E.3.1. Migration to Version 13.10
    E.3.2. Changes

    Release date: 2023-02-09

    This release contains a variety of fixes from 13.9. For information about new features in major release 13, see - Section E.12. -

    E.2.1. Migration to Version 13.10

    + Section E.13. +

    E.3.1. Migration to Version 13.10

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.7, - see Section E.5. -

    E.2.2. Changes

    E.3.2. Changes

    • libpq can leak memory contents after GSSAPI transport encryption initiation fails (Jacob Champion)

      @@ -286,4 +286,4 @@

      Notably, a new timezone America/Ciudad_Juarez has been split off from America/Ojinaga. -

    Prev Up Next
    E.1. Release 13.11 Home E.3. Release 13.9
    \ No newline at end of file +

    Prev Up Next
    E.2. Release 13.11 Home E.4. Release 13.9
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-11.html postgresql-13-13.12/doc/src/sgml/html/release-13-11.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-11.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-11.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.1. Release 13.11
    E.1. Release 13.11
    Prev UpAppendix E. Release NotesHome Next

    E.1. Release 13.11

    E.1.1. Migration to Version 13.11
    E.1.2. Changes

    Release date: 2023-05-11

    +E.2. Release 13.11

    E.2. Release 13.11
    Prev UpAppendix E. Release NotesHome Next

    E.2. Release 13.11

    E.2.1. Migration to Version 13.11
    E.2.2. Changes

    Release date: 2023-05-11

    This release contains a variety of fixes from 13.10. For information about new features in major release 13, see - Section E.12. -

    E.1.1. Migration to Version 13.11

    + Section E.13. +

    E.2.1. Migration to Version 13.11

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.7, - see Section E.5. -

    E.1.2. Changes

    E.2.2. Changes

    • Prevent CREATE SCHEMA from defeating changes in search_path (Alexander Lakhin)

      @@ -438,4 +438,4 @@ for consistency with other timezones observing Moscow time. Also, America/Yellowknife is no longer distinct from America/Edmonton; this affects some pre-1948 timestamps in that area. -

    Prev Up Next
    Appendix E. Release Notes Home E.2. Release 13.10
    \ No newline at end of file +

    Prev Up Next
    E.1. Release 13.12 Home E.3. Release 13.10
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-12.html postgresql-13-13.12/doc/src/sgml/html/release-13-12.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-12.html 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-12.html 2023-08-07 20:32:36.000000000 +0000 @@ -0,0 +1,267 @@ + +E.1. Release 13.12
    E.1. Release 13.12
    Prev UpAppendix E. Release NotesHome Next

    E.1. Release 13.12

    E.1.1. Migration to Version 13.12
    E.1.2. Changes

    Release date: 2023-08-10

    + This release contains a variety of fixes from 13.11. + For information about new features in major release 13, see + Section E.13. +

    E.1.1. Migration to Version 13.12

    + A dump/restore is not required for those running 13.X. +

    + However, if you use BRIN indexes, it may be advisable to reindex them; + see the second changelog entry below. +

    + Also, if you are upgrading from a version earlier than 13.7, + see Section E.6. +

    E.1.2. Changes

    • + Disallow substituting a schema or owner name into an extension script + if the name contains a quote, backslash, or dollar sign (Noah Misch) +

      + This restriction guards against SQL-injection hazards for trusted + extensions. +

      + The PostgreSQL Project thanks Micah Gate, + Valerie Woolard, Tim Carey-Smith, and Christoph Berg for reporting + this problem. + (CVE-2023-39417) +

    • + Fix confusion between empty (no rows) ranges and all-NULL ranges in + BRIN indexes, as well as incorrect merging of all-NULL summaries + (Tomas Vondra) +

      + Each of these oversights could result in forgetting that a BRIN + index range contains any NULL values, potentially allowing + subsequent queries that should return NULL values to miss doing so. +

      + This fix will not in itself correct faulty BRIN entries. + It's recommended to REINDEX any BRIN indexes that + may be used to search for nulls. +

    • + Avoid leaving a corrupted database behind when DROP + DATABASE is interrupted (Andres Freund) +

      + If DROP DATABASE was interrupted after it had + already begun taking irreversible steps, the target database + remained accessible (because the removal of + its pg_database row would roll back), + but it would have corrupt contents. Fix by marking the database + as inaccessible before we begin to perform irreversible operations. + A failure after that will leave the database still partially + present, but nothing can be done with it except to issue + another DROP DATABASE. +

    • + Ensure that partitioned indexes are correctly marked as valid or not + at creation (Michael Paquier) +

      + If a new partitioned index matches an existing but invalid index on + one of the partitions, the partitioned index could end up being + marked valid prematurely. This could lead to misbehavior or + assertion failures in subsequent queries on the partitioned table. +

    • + Ignore invalid child indexes when matching partitioned indexes to + child indexes during ALTER TABLE ATTACH PARTITION + (Michael Paquier) +

      + Such an index will now be ignored, and a new child index created + instead. +

    • + Fix possible failure when marking a partitioned index valid after + all of its partitions have been attached (Michael Paquier) +

      + The update of the index's pg_index entry + could use stale data for other columns. One reported symptom is + an “attempted to update invisible tuple” error. +

    • + Fix ALTER EXTENSION SET SCHEMA to complain if the + extension contains any objects outside the extension's schema + (Michael Paquier, Heikki Linnakangas) +

      + Erroring out if the extension contains objects in multiple schemas + was always intended; but the check was mis-coded so that it would + fail to detect some cases, leading to surprising behavior. +

    • + Don't use partial unique indexes for uniqueness proofs in the + planner (David Rowley) +

      + This could give rise to incorrect plans, since the presumed + uniqueness of rows read from a table might not hold if the index in + question isn't used to scan the table. +

    • + Avoid producing incorrect plans for foreign joins with + pseudoconstant join clauses (Etsuro Fujita) +

      + The planner currently lacks support for attaching pseudoconstant + join clauses to a pushed-down remote join, so disable generation + of remote joins in such cases. (A better solution will require + ABI-breaking changes of planner data structures, so it will have to + wait for a future major release.) +

    • + Correctly handle sub-SELECTs in RLS policy expressions and + security-barrier views when expanding rule actions (Tom Lane) +

    • + Fix race conditions in conflict detection + for SERIALIZABLE isolation mode + (Thomas Munro) +

      + Conflicts could be missed when using bitmap heap scans, when using + GIN indexes, and when examining an initially-empty btree index. + All these cases could lead to serializability failures due to + improperly allowing conflicting transactions to commit. +

    • + Fix hash join with an inner-side hash key that contains Params + coming from an outer nested loop (Tom Lane) +

      + When rescanning the join after the values of such Params have + changed, we must rebuild the hash table, but neglected to do so. + This could result in missing join output rows. +

    • + Fix intermittent failures when trying to update a field of a + composite column (Tom Lane) +

      + If the overall value of the composite column is wide enough to + require out-of-line toasting, then an unluckily-timed cache flush + could cause errors or server crashes. +

    • + Prevent query-lifespan memory leaks in some UPDATE + queries with triggers (Tomas Vondra) +

    • + Prevent query-lifespan memory leaks when an Incremental Sort plan + node is rescanned (James Coleman, Laurenz Albe, Tom Lane) +

    • + Accept fractional seconds in the input to jsonpath's + datetime() method (Tom Lane) +

    • + Prevent stack-overflow crashes with very complex text search + patterns (Tom Lane) +

    • + Allow tokens up to 10240 bytes long + in pg_hba.conf + and pg_ident.conf (Tom Lane) +

      + The previous limit of 256 bytes has been found insufficient for some + use-cases. +

    • + Fix mishandling of C++ out-of-memory conditions (Heikki Linnakangas) +

      + If JIT is in use, running out of memory in a + C++ new call would lead to + a PostgreSQL FATAL error, instead of the + expected C++ exception. +

    • + Fix rare null-pointer crash in plancache.c + (Tom Lane) +

    • + Avoid losing track of possibly-useful shared memory segments when a + page free results in coalescing ranges of free space (Dongming Liu) +

      + Ensure that the segment is moved into the + appropriate “bin” for its new amount of free space, so + that it will be found by subsequent searches. +

    • + Allow VACUUM to continue after detecting certain + types of b-tree index corruption (Peter Geoghegan) +

      + If an invalid sibling-page link is detected, log the issue and press + on, rather than throwing an error as before. Nothing short + of REINDEX will fix the broken index, but + preventing VACUUM from completing until that is + done risks making matters far worse. +

    • + Ensure that WrapLimitsVacuumLock is released + after VACUUM detects invalid data + in pg_database.datfrozenxid + or pg_database.datminmxid + (Andres Freund) +

      + Failure to release this lock could lead to a deadlock later, + although the lock would be cleaned up if the session exits or + encounters some other error. +

    • + Avoid double replay of prepared transactions during crash + recovery (suyu.cmj, Michael Paquier) +

      + After a crash partway through a checkpoint with some two-phase + transaction state data already flushed to disk by this checkpoint, + crash recovery could attempt to replay the prepared transaction(s) + twice, leading to a fatal error such as “lock is already + held” in the startup process. +

    • + Fix possible failure while promoting a standby server, if archiving + is enabled and two-phase transactions need to be recovered (Julian + Markwort) +

      + If any required two-phase transactions were logged in the most + recent (partial) log segment, promotion would fail with an incorrect + complaint about “requested WAL segment has already been + removed”. +

    • + Ensure that a newly created, but still empty table + is fsync'ed at the next checkpoint (Heikki + Linnakangas) +

      + Without this, if there is an operating system crash causing the + empty file to disappear, subsequent operations on the table might + fail with “could not open file” errors. +

    • + Ensure that creation of the init fork of an unlogged index is + WAL-logged (Heikki Linnakangas) +

      + While an unlogged index's main data fork is not WAL-logged, its init + fork should be, to ensure that we have a consistent state to restore + the index to after a crash. This step was missed if the init fork + contains no data, which is a case not used by any standard index AM; + but perhaps some extension behaves that way. +

    • + Fix missing reinitializations of delay-checkpoint-end flags + (suyu.cmj) +

      + This could result in unnecessary delays of checkpoints, or in + assertion failures in assert-enabled builds. +

    • + Fix overly strict assertion in jsonpath code + (David Rowley) +

      + This assertion failed if a query applied + the .type() operator to + a like_regex result. + There was no bug in non-assert builds. +

    • + Avoid assertion failure when processing an empty statement via the + extended query protocol in an already-aborted transaction (Tom Lane) +

    • + Fix contrib/fuzzystrmatch's + Soundex difference() function to handle empty + input sanely (Alexander Lakhin, Tom Lane) +

      + An input string containing no alphabetic characters resulted in + unpredictable output. +

    • + Tighten whitespace checks in contrib/hstore + input (Evan Jones) +

      + In some cases, characters would be falsely recognized as whitespace + and hence discarded. +

    • + Disallow oversize input arrays + with contrib/intarray's + gist__int_ops index opclass (Ankit Kumar Pandey, + Alexander Lakhin) +

      + Previously this code would report a NOTICE but + press on anyway, creating an invalid index entry that presents a + risk of crashes when the index is read. +

    • + Avoid useless double decompression of GiST index entries + in contrib/intarray (Konstantin Knizhnik, + Matthias van de Meent, Tom Lane) +

    • + Ensure + that pg_index.indisreplident + is kept up-to-date in relation cache entries (Shruthi Gowda) +

      + This value could be stale in some cases. There is no core code that + relies on the relation cache's copy, so this is only a latent bug as + far as Postgres itself is concerned; but there may be extensions for + which it is a live bug. +

    • + Silence deprecation warnings when compiling with OpenSSL 3.0.0 or + later (Peter Eisentraut) +

    Prev Up Next
    Appendix E. Release Notes Home E.2. Release 13.11
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-2.html postgresql-13-13.12/doc/src/sgml/html/release-13-2.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-2.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-2.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,16 +1,16 @@ -E.10. Release 13.2
    E.10. Release 13.2
    Prev UpAppendix E. Release NotesHome Next

    E.10. Release 13.2

    E.10.1. Migration to Version 13.2
    E.10.2. Changes

    Release date: 2021-02-11

    +E.11. Release 13.2

    E.11. Release 13.2
    Prev UpAppendix E. Release NotesHome Next

    E.11. Release 13.2

    E.11.1. Migration to Version 13.2
    E.11.2. Changes

    Release date: 2021-02-11

    This release contains a variety of fixes from 13.1. For information about new features in major release 13, see - Section E.12. -

    E.10.1. Migration to Version 13.2

    + Section E.13. +

    E.11.1. Migration to Version 13.2

    A dump/restore is not required for those running 13.X.

    However, see the first changelog item below concerning a possible need to update stored views. Also see the third and fourth changelog items, which describe cases in which reindexing indexes after the upgrade may be advisable. -

    E.10.2. Changes

    • +

    E.11.2. Changes

    • Fix failure to check per-column SELECT privileges in some join queries (Tom Lane)

      @@ -588,4 +588,4 @@

      Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart. -

    Prev Up Next
    E.9. Release 13.3 Home E.11. Release 13.1
    \ No newline at end of file +

    Prev Up Next
    E.10. Release 13.3 Home E.12. Release 13.1
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-3.html postgresql-13-13.12/doc/src/sgml/html/release-13-3.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-3.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-3.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.9. Release 13.3
    E.9. Release 13.3
    Prev UpAppendix E. Release NotesHome Next

    E.9. Release 13.3

    E.9.1. Migration to Version 13.3
    E.9.2. Changes

    Release date: 2021-05-13

    +E.10. Release 13.3

    E.10. Release 13.3
    Prev UpAppendix E. Release NotesHome Next

    E.10. Release 13.3

    E.10.1. Migration to Version 13.3
    E.10.2. Changes

    Release date: 2021-05-13

    This release contains a variety of fixes from 13.2. For information about new features in major release 13, see - Section E.12. -

    E.9.1. Migration to Version 13.3

    + Section E.13. +

    E.10.1. Migration to Version 13.3

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.2, - see Section E.10. -

    E.9.2. Changes

    E.10.2. Changes

    • Prevent integer overflows in array subscripting calculations (Tom Lane)

      @@ -335,4 +335,4 @@ compiler versions (Noah Misch)

    • Fix testing of PL/Python for Python 3 on Solaris (Noah Misch) -

    Prev Up Next
    E.8. Release 13.4 Home E.10. Release 13.2
    \ No newline at end of file +

    Prev Up Next
    E.9. Release 13.4 Home E.11. Release 13.2
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-4.html postgresql-13-13.12/doc/src/sgml/html/release-13-4.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-4.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-4.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.8. Release 13.4
    E.8. Release 13.4
    Prev UpAppendix E. Release NotesHome Next

    E.8. Release 13.4

    E.8.1. Migration to Version 13.4
    E.8.2. Changes

    Release date: 2021-08-12

    +E.9. Release 13.4

    E.9. Release 13.4
    Prev UpAppendix E. Release NotesHome Next

    E.9. Release 13.4

    E.9.1. Migration to Version 13.4
    E.9.2. Changes

    Release date: 2021-08-12

    This release contains a variety of fixes from 13.3. For information about new features in major release 13, see - Section E.12. -

    E.8.1. Migration to Version 13.4

    + Section E.13. +

    E.9.1. Migration to Version 13.4

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.2, - see Section E.10. -

    E.8.2. Changes

    E.9.2. Changes

    • Fix mis-planning of repeated application of a projection step (Tom Lane)

      @@ -472,4 +472,4 @@ In MSVC builds, include --with-pgport in the set of configure options reported by pg_config, if it had been specified (Andrew Dunstan) -

    Prev Up Next
    E.7. Release 13.5 Home E.9. Release 13.3
    \ No newline at end of file +

    Prev Up Next
    E.8. Release 13.5 Home E.10. Release 13.3
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-5.html postgresql-13-13.12/doc/src/sgml/html/release-13-5.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-5.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-5.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,9 +1,9 @@ -E.7. Release 13.5
    E.7. Release 13.5
    Prev UpAppendix E. Release NotesHome Next

    E.7. Release 13.5

    E.7.1. Migration to Version 13.5
    E.7.2. Changes

    Release date: 2021-11-11

    +E.8. Release 13.5

    E.8. Release 13.5
    Prev UpAppendix E. Release NotesHome Next

    E.8. Release 13.5

    E.8.1. Migration to Version 13.5
    E.8.2. Changes

    Release date: 2021-11-11

    This release contains a variety of fixes from 13.4. For information about new features in major release 13, see - Section E.12. -

    E.7.1. Migration to Version 13.5

    + Section E.13. +

    E.8.1. Migration to Version 13.5

    A dump/restore is not required for those running 13.X.

    However, note that installations using physical replication should @@ -16,8 +16,8 @@ possibly-affected indexes after updating.

    Also, if you are upgrading from a version earlier than 13.2, - see Section E.10. -

    E.7.2. Changes

    E.8.2. Changes

    • Make the server reject extraneous data after an SSL or GSS encryption handshake (Tom Lane)

      @@ -621,4 +621,4 @@ America/Curacao, America/Nassau, America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. In all these cases, the previous zone name remains as an alias. -

    Prev Up Next
    E.6. Release 13.6 Home E.8. Release 13.4
    \ No newline at end of file +

    Prev Up Next
    E.7. Release 13.6 Home E.9. Release 13.4
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-6.html postgresql-13-13.12/doc/src/sgml/html/release-13-6.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-6.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-6.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,9 +1,9 @@ -E.6. Release 13.6
    E.6. Release 13.6
    Prev UpAppendix E. Release NotesHome Next

    E.6. Release 13.6

    E.6.1. Migration to Version 13.6
    E.6.2. Changes

    Release date: 2022-02-10

    +E.7. Release 13.6

    E.7. Release 13.6
    Prev UpAppendix E. Release NotesHome Next

    E.7. Release 13.6

    E.7.1. Migration to Version 13.6
    E.7.2. Changes

    Release date: 2022-02-10

    This release contains a variety of fixes from 13.5. For information about new features in major release 13, see - Section E.12. -

    E.6.1. Migration to Version 13.6

    + Section E.13. +

    E.7.1. Migration to Version 13.6

    A dump/restore is not required for those running 13.X.

    However, if you have applied REINDEX CONCURRENTLY @@ -11,8 +11,8 @@ see the first changelog entry below.

    Also, if you are upgrading from a version earlier than 13.5, - see Section E.7. -

    E.6.2. Changes

    E.7.2. Changes

    • Enforce standard locking protocol for TOAST table updates, to prevent problems with REINDEX CONCURRENTLY (Michael Paquier)

      @@ -301,4 +301,4 @@ Allow the .bat wrapper scripts in our MSVC build system to be called without first changing into their directory (Anton Voloshin, Andrew Dunstan) -

    Prev Up Next
    E.5. Release 13.7 Home E.7. Release 13.5
    \ No newline at end of file +

    Prev Up Next
    E.6. Release 13.7 Home E.8. Release 13.5
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-7.html postgresql-13-13.12/doc/src/sgml/html/release-13-7.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-7.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-7.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,9 +1,9 @@ -E.5. Release 13.7
    E.5. Release 13.7
    Prev UpAppendix E. Release NotesHome Next

    E.5. Release 13.7

    E.5.1. Migration to Version 13.7
    E.5.2. Changes

    Release date: 2022-05-12

    +E.6. Release 13.7

    E.6. Release 13.7
    Prev UpAppendix E. Release NotesHome Next

    E.6. Release 13.7

    E.6.1. Migration to Version 13.7
    E.6.2. Changes

    Release date: 2022-05-12

    This release contains a variety of fixes from 13.6. For information about new features in major release 13, see - Section E.12. -

    E.5.1. Migration to Version 13.7

    + Section E.13. +

    E.6.1. Migration to Version 13.7

    A dump/restore is not required for those running 13.X.

    However, if you have any GiST indexes on columns of type @@ -12,8 +12,8 @@ See the second changelog entry below.

    Also, if you are upgrading from a version earlier than 13.6, - see Section E.6. -

    E.5.2. Changes

    E.6.2. Changes

    • Confine additional operations within “security restricted operation” sandboxes (Sergey Shinderuk, Noah Misch)

      @@ -325,4 +325,4 @@ Update time zone data files to tzdata release 2022a for DST law changes in Palestine, plus historical corrections for Chile and Ukraine. -

    Prev Up Next
    E.4. Release 13.8 Home E.6. Release 13.6
    \ No newline at end of file +

    Prev Up Next
    E.5. Release 13.8 Home E.7. Release 13.6
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-8.html postgresql-13-13.12/doc/src/sgml/html/release-13-8.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-8.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-8.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.4. Release 13.8
    E.4. Release 13.8
    Prev UpAppendix E. Release NotesHome Next

    E.4. Release 13.8

    E.4.1. Migration to Version 13.8
    E.4.2. Changes

    Release date: 2022-08-11

    +E.5. Release 13.8

    E.5. Release 13.8
    Prev UpAppendix E. Release NotesHome Next

    E.5. Release 13.8

    E.5.1. Migration to Version 13.8
    E.5.2. Changes

    Release date: 2022-08-11

    This release contains a variety of fixes from 13.7. For information about new features in major release 13, see - Section E.12. -

    E.4.1. Migration to Version 13.8

    + Section E.13. +

    E.5.1. Migration to Version 13.8

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.7, - see Section E.5. -

    E.4.2. Changes

    E.5.2. Changes

    • Do not let extension scripts replace objects not already belonging to the extension (Tom Lane)

      @@ -304,4 +304,4 @@ multiple OpenLDAP installations are present while building PostgreSQL (Tom Lane) -

    Prev Up Next
    E.3. Release 13.9 Home E.5. Release 13.7
    \ No newline at end of file +

    Prev Up Next
    E.4. Release 13.9 Home E.6. Release 13.7
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13-9.html postgresql-13-13.12/doc/src/sgml/html/release-13-9.html --- postgresql-13-13.11/doc/src/sgml/html/release-13-9.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13-9.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,14 +1,14 @@ -E.3. Release 13.9
    E.3. Release 13.9
    Prev UpAppendix E. Release NotesHome Next

    E.3. Release 13.9

    E.3.1. Migration to Version 13.9
    E.3.2. Changes

    Release date: 2022-11-10

    +E.4. Release 13.9

    E.4. Release 13.9
    Prev UpAppendix E. Release NotesHome Next

    E.4. Release 13.9

    E.4.1. Migration to Version 13.9
    E.4.2. Changes

    Release date: 2022-11-10

    This release contains a variety of fixes from 13.8. For information about new features in major release 13, see - Section E.12. -

    E.3.1. Migration to Version 13.9

    + Section E.13. +

    E.4.1. Migration to Version 13.9

    A dump/restore is not required for those running 13.X.

    However, if you are upgrading from a version earlier than 13.7, - see Section E.5. -

    E.3.2. Changes

    E.4.2. Changes

    • Avoid rare PANIC during updates occurring concurrently with VACUUM (Tom Lane, Jeff Davis)

      @@ -344,4 +344,4 @@ tzdb's backwards-compatibility options (see their PACKRATDATA and PACKRATLIST options). -

    Prev Up Next
    E.2. Release 13.10 Home E.4. Release 13.8
    \ No newline at end of file +

    Prev Up Next
    E.3. Release 13.10 Home E.5. Release 13.8
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-13.html postgresql-13-13.12/doc/src/sgml/html/release-13.html --- postgresql-13-13.11/doc/src/sgml/html/release-13.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-13.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -E.12. Release 13
    E.12. Release 13
    Prev UpAppendix E. Release NotesHome Next

    E.12. Release 13

    E.12.1. Overview
    E.12.2. Migration to Version 13
    E.12.3. Changes
    E.12.4. Acknowledgments

    Release date: 2020-09-24

    E.12.1. Overview

    +E.13. Release 13

    E.13. Release 13
    Prev UpAppendix E. Release NotesHome Next

    E.13. Release 13

    E.13.1. Overview
    E.13.2. Migration to Version 13
    E.13.3. Changes
    E.13.4. Acknowledgments

    Release date: 2020-09-24

    E.13.1. Overview

    PostgreSQL 13 contains many new features and enhancements, including:

    • @@ -18,7 +18,7 @@ The above items and other new features of PostgreSQL 13 are explained in more detail in the sections below. -

    E.12.2. Migration to Version 13

    +

    E.13.2. Migration to Version 13

    A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases. @@ -131,11 +131,11 @@ Fix pageinspect's bt_metap() to return more appropriate data types that are less likely to overflow (Peter Geoghegan) -

    E.12.3. Changes

    +

    E.13.3. Changes

    Below you will find a detailed account of the changes between PostgreSQL 13 and the previous major release. -

    E.12.3.1. Server

    E.12.3.1.1. Partitioning

    • +

      E.13.3.1. Server

      E.13.3.1.1. Partitioning

      • Allow pruning of partitions to happen in more cases (Yuzuko Hosoya, Amit Langote, Álvaro Herrera) @@ -174,7 +174,7 @@ Allow whole-row variables (that is, table.*) to be used in partitioning expressions (Amit Langote) -

      E.12.3.1.2. Indexes

      • +

      E.13.3.1.2. Indexes

      • More efficiently store duplicates in B-tree indexes (Anastasia Lubennikova, Peter Geoghegan)

        @@ -210,7 +210,7 @@ The index's collation must match that of the underlying column, but ALTER TABLE previously failed to check this. -

      E.12.3.1.3. Optimizer

      • +

      E.13.3.1.3. Optimizer

      • Improve the optimizer's selectivity estimation for containment/match operators (Tom Lane)

      • @@ -231,7 +231,7 @@ Allow functions in FROM clauses to be pulled up (inlined) if they evaluate to constants (Alexander Kuzmenkov, Aleksandr Parfenov) -

      E.12.3.1.4. General Performance

      • +

      E.13.3.1.4. General Performance

      • Implement incremental sorting (James Coleman, Alexander Korotkov, Tomas Vondra)

        @@ -314,7 +314,7 @@

      • Reduce memory usage for query strings and extension scripts that contain many SQL statements (Amit Langote) -

      E.12.3.1.5. Monitoring

      • +

      E.13.3.1.5. Monitoring
      E.12.3.1.6. System Views

      • +

      E.13.3.1.6. System Views

      • Add leader_pid to pg_stat_activity to report a parallel worker's leader process (Julien Rouhaud)

      • @@ -368,7 +368,7 @@ high as 1MB (Vyacheslav Makarov)

        The previous maximum was 100kB. -

      E.12.3.1.7. Wait Events

      • +

      E.13.3.1.7. Wait Events

      • Report a wait event while creating a DSM segment with posix_fallocate() (Thomas Munro)

      • @@ -386,7 +386,7 @@

      • Improve performance of wait events on BSD-based systems (Thomas Munro) -

      E.12.3.1.8. Authentication

      • +

      E.13.3.1.8. Authentication
      E.12.3.1.9. Server Configuration

      • +

      E.13.3.1.9. Server Configuration

      • Tighten rules on which utility commands are allowed in read-only transaction mode (Robert Haas)

        @@ -416,7 +416,7 @@ Enable support for Unix-domain sockets on Windows (Peter Eisentraut) -

      E.12.3.2. Streaming Replication and Recovery

      • +

    E.13.3.2. Streaming Replication and Recovery

    • Allow streaming replication configuration settings to be changed by reload (Sergei Kornilov)

      @@ -456,7 +456,7 @@ pages are referenced by WAL (Fujii Masao)

      This is enabled using ignore_invalid_pages. -

    E.12.3.3. Utility Commands

    • +

    E.13.3.3. Utility Commands

    • Allow VACUUM to process a table's indexes in parallel (Masahiko Sawada, Amit Kapila)

      @@ -522,7 +522,7 @@ Add structure member tg_updatedcols to allow C-language update triggers to know which column(s) were updated (Peter Eisentraut) -

    E.12.3.4. Data Types

    • +

    E.13.3.4. Data Types

    • Add polymorphic data types for use by functions requiring compatible arguments (Pavel Stehule)

      @@ -553,7 +553,7 @@ notation (Tom Lane)

      For example, (ROW(4, 5.0)).f1 now returns 4. -

    E.12.3.5. Functions

    • +

    E.13.3.5. Functions

    • Add alternate version of jsonb_set() with improved NULL handling (Andrew Dunstan)

      @@ -661,13 +661,13 @@

      The object can be a function, materialized view, index, or trigger. The syntax is ALTER .. NO DEPENDS ON. -

    E.12.3.6. PL/pgSQL

    • +

    E.13.3.6. PL/pgSQL

    • Improve performance of simple PL/pgSQL expressions (Tom Lane, Amit Langote)

    • Improve performance of PL/pgSQL functions that use immutable expressions (Konstantin Knizhnik) -

    E.12.3.7. Client Interfaces

    • +

    E.13.3.7. Client Interfaces

    • Allow libpq clients to require channel binding for encrypted connections (Jeff Davis)

      @@ -700,7 +700,7 @@ of the same if construct did not prevent expansion of the elif branch or following branches. -

    E.12.3.8. Client Applications

    E.12.3.8.1. psql

    • +

    E.13.3.8. Client Applications

    E.13.3.8.1. psql

    • Add transaction status (%x) to psql's default prompts (Vik Fearing) @@ -752,7 +752,7 @@

    • Add the PostgreSQL home page to command-line --help output (Peter Eisentraut) -

    E.12.3.8.2. pgbench

    • +

    E.13.3.8.2. pgbench

    • Allow pgbench to partition its “accounts” table (Fabien Coelho)

      @@ -767,7 +767,7 @@

    • Allow pgbench to show script contents using option --show-script (Fabien Coelho) -

    E.12.3.9. Server Applications

    • +

    E.13.3.9. Server Applications

    • Generate backup manifests for base backups, and verify them (Robert Haas)

      @@ -839,7 +839,7 @@ Use the directory of the pg_upgrade program as the default --new-bindir setting when running pg_upgrade (Daniel Gustafsson) -

    E.12.3.10. Documentation

    • +

    E.13.3.10. Documentation

    • Add a glossary to the documentation (Corey Huinker, Jürgen Purtz, Roger Harkavy, Álvaro Herrera) @@ -849,7 +849,7 @@

    • Upgrade to use DocBook 4.5 (Peter Eisentraut) -

    E.12.3.11. Source Code

    • +

    E.13.3.11. Source Code

    • Add support for building on Visual Studio 2019 (Haribabu Kommi)

    • Add build support for MSYS2 (Peter Eisentraut) @@ -914,7 +914,7 @@ TS_execute callbacks must now provide ternary (yes/no/maybe) logic. Calculating NOT queries accurately is now the default. -

    E.12.3.12. Additional Modules

    • +

    E.13.3.12. Additional Modules

    • Allow extensions to be specified as trusted (Tom Lane)

      @@ -977,8 +977,8 @@

    • Add B-tree index de-duplication processing columns to pageinspect output (Peter Geoghegan) -

    E.12.4. Acknowledgments

    +

    E.13.4. Acknowledgments

    The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues. -

    Abhijit Menon-Sen
    Adam Lee
    Adam Scott
    Adé Heyward
    Adrien Nayrat
    Ahsan Hadi
    Alastair McKinley
    Aleksandr Parfenov
    Alex Aktsipetrov
    Alex Macy
    Alex Shulgin
    Alexander Korotkov
    Alexander Kukushkin
    Alexander Kuzmenkov
    Alexander Lakhin
    Alexey Bashtanov
    Alexey Kondratov
    Álvaro Herrera
    Amit Kapila
    Amit Khandekar
    Amit Langote
    Amul Sul
    Anastasia Lubennikova
    Andreas Joseph Krogh
    Andreas Karlsson
    Andreas Kunert
    Andreas Seltenreich
    Andrei Zubkov
    Andres Freund
    Andrew Bille
    Andrew Dunstan
    Andrew Gierth
    Andrey Borodin
    Andrey Klychkov
    Andrey Lepikhov
    Anna Akenteva
    Anna Endo
    Anthony Nowocien
    Anton Vlasov
    Antonin Houska
    Ants Aasma
    Arne Roland
    Arnold Müller
    Arseny Sher
    Arthur Nascimento
    Arthur Zakirov
    Ashutosh Bapat
    Ashutosh Sharma
    Ashwin Agrawal
    Asif Rehman
    Asim Praveen
    Atsushi Torikoshi
    Augustinas Jokubauskas
    Austin Drenski
    Basil Bourque
    Beena Emerson
    Ben Cornett
    Benjie Gillam
    Benoît Lobréau
    Bernd Helmle
    Bharath Rupireddy
    Bhargav Kamineni
    Binguo Bao
    Brad DeJong
    Brandur Leach
    Brent Bates
    Brian Williams
    Bruce Momjian
    Cameron Ezell
    Cary Huang
    Chapman Flack
    Charles Offenbacher
    Chen Huajun
    Chenyang Lu
    Chris Bandy
    Chris Travers
    Christoph Berg
    Christophe Courtois
    Corey Huinker
    Craig Ringer
    Cuiping Lin
    Dagfinn Ilmari Mannsåker
    Daniel Fiori
    Daniel Gustafsson
    Daniel Vérité
    Daniel Westermann
    Darafei Praliaskouski
    Daryl Waycott
    Dave Cramer
    David Christensen
    David Fetter
    David G. Johnston
    David Gilman
    David Harper
    David Rowley
    David Steele
    David Zhang
    Davinder Singh
    Dean Rasheed
    Denis Stuchalin
    Dent John
    Didier Gautheron
    Dilip Kumar
    Dmitry Belyavsky
    Dmitry Dolgov
    Dmitry Ivanov
    Dmitry Telpt
    Dmitry Uspenskiy
    Dominik Czarnota
    Dongming Liu
    Ed Morley
    Edmund Horner
    Emre Hasegeli
    Eric Gillum
    Erik Rijkers
    Erwin Brandstetter
    Ethan Waldo
    Etsuro Fujita
    Eugen Konkov
    Euler Taveira
    Fabien Coelho
    Fabrízio de Royes Mello
    Felix Lechner
    Filip Janus
    Filip Rembialkowski
    Frank Gagnepain
    Georgios Kokolatos
    Gilles Darold
    Greg Nancarrow
    Grigory Smolkin
    Guancheng Luo
    Guillaume Lelarge
    Hadi Moshayedi
    Haiying Tang
    Hamid Akhtar
    Hans Buschmann
    Hao Wu
    Haribabu Kommi
    Haruka Takatsuka
    Heath Lord
    Heikki Linnakangas
    Himanshu Upadhyaya
    Hironobu Suzuki
    Hugh McMaster
    Hugh Ranalli
    Hugh Wang
    Ian Barwick
    Ibrar Ahmed
    Ildar Musin
    Insung Moon
    Ireneusz Pluta
    Isaac Morland
    Ivan Kartyshov
    Ivan Panchenko
    Ivan Sergio Borgonovo
    Jaime Casanova
    James Coleman
    James Gray
    James Hunter
    James Inform
    James Lucas
    Jan Mussler
    Jaroslav Sivy
    Jeevan Chalke
    Jeevan Ladhe
    Jeff Davis
    Jeff Janes
    Jehan-Guillaume de Rorthais
    Jeremy Evans
    Jeremy Schneider
    Jeremy Smith
    Jerry Sievers
    Jesper Pedersen
    Jesse Kinkead
    Jesse Zhang
    Jian Zhang
    Jie Zhang
    Jim Nasby
    Jimmy Yih
    Jobin Augustine
    Joe Conway
    John Hsu
    John Naylor
    Jon Jensen
    Jonathan Katz
    Jorge Gustavo Rocha
    Josef Šimánek
    Joseph Nahmias
    Juan José Santamaría Flecha
    Julian Backes
    Julien Rouhaud
    Jürgen Purtz
    Justin King
    Justin Pryzby
    Karl O. Pinc
    Keisuke Kuroda
    Keith Fiske
    Kelly Min
    Ken Tanzer
    Kirill Bychik
    Kirk Jamison
    Konstantin Knizhnik
    Kuntal Ghosh
    Kyle Kingsbury
    Kyotaro Horiguchi
    Lars Kanis
    Laurenz Albe
    Leif Gunnar Erlandsen
    Li Japin
    Liudmila Mantrova
    Lucas Viecelli
    Luis M. Carril
    Lukáš Sobotka
    Maciek Sakrejda
    Magnus Hagander
    Mahadevan Ramachandran
    Mahendra Singh Thalor
    Manuel Rigger
    Marc Munro
    Marcos David
    Marina Polyakova
    Mark Dilger
    Mark Wong
    Marko Tiikkaja
    Markus Winand
    Marti Raudsepp
    Martijn van Oosterhout
    Masahiko Sawada
    Masahiro Ikeda
    Masao Fujii
    Mateusz Guzik
    Matt Jibson
    Matteo Beccati
    Maxence Ahlouche
    Melanie Plageman
    Michael Banck
    Michael Luo
    Michael Meskes
    Michael Paquier
    Michail Nikolaev
    Mike Palmiotto
    Mithun Cy
    Movead Li
    Nathan Bossart
    Nazli Ugur Koyluoglu
    Neha Sharma
    Nicola Contu
    Nicolás Alvarez
    Nikhil Sontakke
    Nikita Glukhov
    Nikolay Shaplov
    Nino Floris
    Noah Misch
    Noriyoshi Shinoda
    Oleg Bartunov
    Oleg Samoilov
    Oleksii Kliukin
    Ondrej Jirman
    Panagiotis Mavrogiorgos
    Pascal Legrand
    Patrick McHardy
    Paul Guo
    Paul Jungwirth
    Paul Ramsey
    Paul Sivash
    Paul Spencer
    Pavan Deolasee
    Pavel Borisov
    Pavel Luzanov
    Pavel Stehule
    Pavel Suderevsky
    Peifeng Qiu
    Pengzhou Tang
    Peter Billen
    Peter Eisentraut
    Peter Geoghegan
    Peter Smith
    Petr Fedorov
    Petr Jelínek
    Phil Bayer
    Philip Semanchuk
    Philippe Beaudoin
    Pierre Ducroquet
    Pierre Giraud
    Piotr Gabriel Kosinski
    Piotr Wlodarczyk
    Prabhat Sahu
    Quan Zongliang
    Quentin Rameau
    Rafael Castro
    Rafia Sabih
    Raj Mohite
    Rajkumar Raghuwanshi
    Ramanarayana M
    Ranier Vilela
    Rares Salcudean
    Raúl Marín Rodríguez
    Raymond Martin
    Reijo Suhonen
    Richard Guo
    Robert Ford
    Robert Haas
    Robert Kahlert
    Robert Treat
    Robin Abbi
    Robins Tharakan
    Roger Harkavy
    Roman Peshkurov
    Rui DeSousa
    Rui Hai Jiang
    Rushabh Lathia
    Ryan Lambert
    Ryohei Takahashi
    Scott Ribe
    Sean Farrell
    Sehrope Sarkuni
    Sergei Agalakov
    Sergei Kornilov
    Sergey Cherkashin
    Shawn Debnath
    Shawn Wang
    Shay Rojansky
    Shenhao Wang
    Simon Riggs
    Slawomir Chodnicki
    Soumyadeep Chakraborty
    Stéphane Lorek
    Stephen Frost
    Steve Rogerson
    Steven Winfield
    Surafel Temesgen
    Suraj Kharage
    Takanori Asaba
    Takao Fujii
    Takayuki Tsunakawa
    Takuma Hoshiai
    Tatsuhito Kasahara
    Tatsuo Ishii
    Tatsuro Yamada
    Taylor Vesely
    Teodor Sigaev
    Tham Nguyen
    Thibaut Madelaine
    Thom Brown
    Thomas Kellerer
    Thomas Munro
    Tiago Anastacio
    Tim Clarke
    Tim Möhlmann
    Tom Ellis
    Tom Gottfried
    Tom Lane
    Tomas Vondra
    Tuomas Leikola
    Tushar Ahuja
    Victor Wagner
    Victor Yegorov
    Vignesh C
    Vik Fearing
    Vinay Banakar
    Vladimir Leskov
    Vladimir Sitnikov
    Vyacheslav Makarov
    Vyacheslav Shablistyy
    Will Leinweber
    William Crowell
    Wyatt Alt
    Yang Xiao
    Yaroslav Schekin
    Yi Huang
    Yigong Hu
    Yoann La Cancellera
    Yoshikazu Imai
    Yu Kimura
    Yugo Nagata
    Yuli Khodorkovskiy
    Yusuke Egashira
    Yuya Watari
    Yuzuko Hosoya
    ZhenHua Cai
    Prev Up Next
    E.11. Release 13.1 Home E.13. Prior Releases
    \ No newline at end of file +

    Abhijit Menon-Sen
    Adam Lee
    Adam Scott
    Adé Heyward
    Adrien Nayrat
    Ahsan Hadi
    Alastair McKinley
    Aleksandr Parfenov
    Alex Aktsipetrov
    Alex Macy
    Alex Shulgin
    Alexander Korotkov
    Alexander Kukushkin
    Alexander Kuzmenkov
    Alexander Lakhin
    Alexey Bashtanov
    Alexey Kondratov
    Álvaro Herrera
    Amit Kapila
    Amit Khandekar
    Amit Langote
    Amul Sul
    Anastasia Lubennikova
    Andreas Joseph Krogh
    Andreas Karlsson
    Andreas Kunert
    Andreas Seltenreich
    Andrei Zubkov
    Andres Freund
    Andrew Bille
    Andrew Dunstan
    Andrew Gierth
    Andrey Borodin
    Andrey Klychkov
    Andrey Lepikhov
    Anna Akenteva
    Anna Endo
    Anthony Nowocien
    Anton Vlasov
    Antonin Houska
    Ants Aasma
    Arne Roland
    Arnold Müller
    Arseny Sher
    Arthur Nascimento
    Arthur Zakirov
    Ashutosh Bapat
    Ashutosh Sharma
    Ashwin Agrawal
    Asif Rehman
    Asim Praveen
    Atsushi Torikoshi
    Augustinas Jokubauskas
    Austin Drenski
    Basil Bourque
    Beena Emerson
    Ben Cornett
    Benjie Gillam
    Benoît Lobréau
    Bernd Helmle
    Bharath Rupireddy
    Bhargav Kamineni
    Binguo Bao
    Brad DeJong
    Brandur Leach
    Brent Bates
    Brian Williams
    Bruce Momjian
    Cameron Ezell
    Cary Huang
    Chapman Flack
    Charles Offenbacher
    Chen Huajun
    Chenyang Lu
    Chris Bandy
    Chris Travers
    Christoph Berg
    Christophe Courtois
    Corey Huinker
    Craig Ringer
    Cuiping Lin
    Dagfinn Ilmari Mannsåker
    Daniel Fiori
    Daniel Gustafsson
    Daniel Vérité
    Daniel Westermann
    Darafei Praliaskouski
    Daryl Waycott
    Dave Cramer
    David Christensen
    David Fetter
    David G. Johnston
    David Gilman
    David Harper
    David Rowley
    David Steele
    David Zhang
    Davinder Singh
    Dean Rasheed
    Denis Stuchalin
    Dent John
    Didier Gautheron
    Dilip Kumar
    Dmitry Belyavsky
    Dmitry Dolgov
    Dmitry Ivanov
    Dmitry Telpt
    Dmitry Uspenskiy
    Dominik Czarnota
    Dongming Liu
    Ed Morley
    Edmund Horner
    Emre Hasegeli
    Eric Gillum
    Erik Rijkers
    Erwin Brandstetter
    Ethan Waldo
    Etsuro Fujita
    Eugen Konkov
    Euler Taveira
    Fabien Coelho
    Fabrízio de Royes Mello
    Felix Lechner
    Filip Janus
    Filip Rembialkowski
    Frank Gagnepain
    Georgios Kokolatos
    Gilles Darold
    Greg Nancarrow
    Grigory Smolkin
    Guancheng Luo
    Guillaume Lelarge
    Hadi Moshayedi
    Haiying Tang
    Hamid Akhtar
    Hans Buschmann
    Hao Wu
    Haribabu Kommi
    Haruka Takatsuka
    Heath Lord
    Heikki Linnakangas
    Himanshu Upadhyaya
    Hironobu Suzuki
    Hugh McMaster
    Hugh Ranalli
    Hugh Wang
    Ian Barwick
    Ibrar Ahmed
    Ildar Musin
    Insung Moon
    Ireneusz Pluta
    Isaac Morland
    Ivan Kartyshov
    Ivan Panchenko
    Ivan Sergio Borgonovo
    Jaime Casanova
    James Coleman
    James Gray
    James Hunter
    James Inform
    James Lucas
    Jan Mussler
    Jaroslav Sivy
    Jeevan Chalke
    Jeevan Ladhe
    Jeff Davis
    Jeff Janes
    Jehan-Guillaume de Rorthais
    Jeremy Evans
    Jeremy Schneider
    Jeremy Smith
    Jerry Sievers
    Jesper Pedersen
    Jesse Kinkead
    Jesse Zhang
    Jian Zhang
    Jie Zhang
    Jim Nasby
    Jimmy Yih
    Jobin Augustine
    Joe Conway
    John Hsu
    John Naylor
    Jon Jensen
    Jonathan Katz
    Jorge Gustavo Rocha
    Josef Šimánek
    Joseph Nahmias
    Juan José Santamaría Flecha
    Julian Backes
    Julien Rouhaud
    Jürgen Purtz
    Justin King
    Justin Pryzby
    Karl O. Pinc
    Keisuke Kuroda
    Keith Fiske
    Kelly Min
    Ken Tanzer
    Kirill Bychik
    Kirk Jamison
    Konstantin Knizhnik
    Kuntal Ghosh
    Kyle Kingsbury
    Kyotaro Horiguchi
    Lars Kanis
    Laurenz Albe
    Leif Gunnar Erlandsen
    Li Japin
    Liudmila Mantrova
    Lucas Viecelli
    Luis M. Carril
    Lukáš Sobotka
    Maciek Sakrejda
    Magnus Hagander
    Mahadevan Ramachandran
    Mahendra Singh Thalor
    Manuel Rigger
    Marc Munro
    Marcos David
    Marina Polyakova
    Mark Dilger
    Mark Wong
    Marko Tiikkaja
    Markus Winand
    Marti Raudsepp
    Martijn van Oosterhout
    Masahiko Sawada
    Masahiro Ikeda
    Masao Fujii
    Mateusz Guzik
    Matt Jibson
    Matteo Beccati
    Maxence Ahlouche
    Melanie Plageman
    Michael Banck
    Michael Luo
    Michael Meskes
    Michael Paquier
    Michail Nikolaev
    Mike Palmiotto
    Mithun Cy
    Movead Li
    Nathan Bossart
    Nazli Ugur Koyluoglu
    Neha Sharma
    Nicola Contu
    Nicolás Alvarez
    Nikhil Sontakke
    Nikita Glukhov
    Nikolay Shaplov
    Nino Floris
    Noah Misch
    Noriyoshi Shinoda
    Oleg Bartunov
    Oleg Samoilov
    Oleksii Kliukin
    Ondrej Jirman
    Panagiotis Mavrogiorgos
    Pascal Legrand
    Patrick McHardy
    Paul Guo
    Paul Jungwirth
    Paul Ramsey
    Paul Sivash
    Paul Spencer
    Pavan Deolasee
    Pavel Borisov
    Pavel Luzanov
    Pavel Stehule
    Pavel Suderevsky
    Peifeng Qiu
    Pengzhou Tang
    Peter Billen
    Peter Eisentraut
    Peter Geoghegan
    Peter Smith
    Petr Fedorov
    Petr Jelínek
    Phil Bayer
    Philip Semanchuk
    Philippe Beaudoin
    Pierre Ducroquet
    Pierre Giraud
    Piotr Gabriel Kosinski
    Piotr Wlodarczyk
    Prabhat Sahu
    Quan Zongliang
    Quentin Rameau
    Rafael Castro
    Rafia Sabih
    Raj Mohite
    Rajkumar Raghuwanshi
    Ramanarayana M
    Ranier Vilela
    Rares Salcudean
    Raúl Marín Rodríguez
    Raymond Martin
    Reijo Suhonen
    Richard Guo
    Robert Ford
    Robert Haas
    Robert Kahlert
    Robert Treat
    Robin Abbi
    Robins Tharakan
    Roger Harkavy
    Roman Peshkurov
    Rui DeSousa
    Rui Hai Jiang
    Rushabh Lathia
    Ryan Lambert
    Ryohei Takahashi
    Scott Ribe
    Sean Farrell
    Sehrope Sarkuni
    Sergei Agalakov
    Sergei Kornilov
    Sergey Cherkashin
    Shawn Debnath
    Shawn Wang
    Shay Rojansky
    Shenhao Wang
    Simon Riggs
    Slawomir Chodnicki
    Soumyadeep Chakraborty
    Stéphane Lorek
    Stephen Frost
    Steve Rogerson
    Steven Winfield
    Surafel Temesgen
    Suraj Kharage
    Takanori Asaba
    Takao Fujii
    Takayuki Tsunakawa
    Takuma Hoshiai
    Tatsuhito Kasahara
    Tatsuo Ishii
    Tatsuro Yamada
    Taylor Vesely
    Teodor Sigaev
    Tham Nguyen
    Thibaut Madelaine
    Thom Brown
    Thomas Kellerer
    Thomas Munro
    Tiago Anastacio
    Tim Clarke
    Tim Möhlmann
    Tom Ellis
    Tom Gottfried
    Tom Lane
    Tomas Vondra
    Tuomas Leikola
    Tushar Ahuja
    Victor Wagner
    Victor Yegorov
    Vignesh C
    Vik Fearing
    Vinay Banakar
    Vladimir Leskov
    Vladimir Sitnikov
    Vyacheslav Makarov
    Vyacheslav Shablistyy
    Will Leinweber
    William Crowell
    Wyatt Alt
    Yang Xiao
    Yaroslav Schekin
    Yi Huang
    Yigong Hu
    Yoann La Cancellera
    Yoshikazu Imai
    Yu Kimura
    Yugo Nagata
    Yuli Khodorkovskiy
    Yusuke Egashira
    Yuya Watari
    Yuzuko Hosoya
    ZhenHua Cai
    Prev Up Next
    E.12. Release 13.1 Home E.14. Prior Releases
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release-prior.html postgresql-13-13.12/doc/src/sgml/html/release-prior.html --- postgresql-13-13.11/doc/src/sgml/html/release-prior.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release-prior.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -E.13. Prior Releases
    E.13. Prior Releases
    Prev UpAppendix E. Release NotesHome Next

    E.13. Prior Releases

    +E.14. Prior Releases

    E.14. Prior Releases
    Prev UpAppendix E. Release NotesHome Next

    E.14. Prior Releases

    Release notes for prior release branches can be found at https://www.postgresql.org/docs/release/ -

    Prev Up Next
    E.12. Release 13 Home Appendix F. Additional Supplied Modules
    \ No newline at end of file +

    Prev Up Next
    E.13. Release 13 Home Appendix F. Additional Supplied Modules
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/release.html postgresql-13-13.12/doc/src/sgml/html/release.html --- postgresql-13-13.11/doc/src/sgml/html/release.html 2023-05-08 21:34:16.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/release.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix E. Release Notes
    Appendix E. Release Notes
    Prev UpPart VIII. AppendixesHome Next

    Appendix E. Release Notes

    Table of Contents

    E.1. Release 13.11
    E.1.1. Migration to Version 13.11
    E.1.2. Changes
    E.2. Release 13.10
    E.2.1. Migration to Version 13.10
    E.2.2. Changes
    E.3. Release 13.9
    E.3.1. Migration to Version 13.9
    E.3.2. Changes
    E.4. Release 13.8
    E.4.1. Migration to Version 13.8
    E.4.2. Changes
    E.5. Release 13.7
    E.5.1. Migration to Version 13.7
    E.5.2. Changes
    E.6. Release 13.6
    E.6.1. Migration to Version 13.6
    E.6.2. Changes
    E.7. Release 13.5
    E.7.1. Migration to Version 13.5
    E.7.2. Changes
    E.8. Release 13.4
    E.8.1. Migration to Version 13.4
    E.8.2. Changes
    E.9. Release 13.3
    E.9.1. Migration to Version 13.3
    E.9.2. Changes
    E.10. Release 13.2
    E.10.1. Migration to Version 13.2
    E.10.2. Changes
    E.11. Release 13.1
    E.11.1. Migration to Version 13.1
    E.11.2. Changes
    E.12. Release 13
    E.12.1. Overview
    E.12.2. Migration to Version 13
    E.12.3. Changes
    E.12.4. Acknowledgments
    E.13. Prior Releases

    +Appendix E. Release Notes

    Appendix E. Release Notes
    Prev UpPart VIII. AppendixesHome Next
    Prev Up Next
    D.3. XML Limits and Conformance to SQL/XML Home E.1. Release 13.11
    \ No newline at end of file +

    Prev Up Next
    D.3. XML Limits and Conformance to SQL/XML Home E.1. Release 13.12
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/replication-origins.html postgresql-13-13.12/doc/src/sgml/html/replication-origins.html --- postgresql-13-13.11/doc/src/sgml/html/replication-origins.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/replication-origins.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 49. Replication Progress Tracking
    Chapter 49. Replication Progress Tracking
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 49. Replication Progress Tracking

    +Chapter 49. Replication Progress Tracking

    Chapter 49. Replication Progress Tracking
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 49. Replication Progress Tracking

    Replication origins are intended to make it easier to implement logical replication solutions on top of logical decoding. @@ -65,4 +65,4 @@ to filter the logical decoding change stream based on the source. While less flexible, filtering via that callback is considerably more efficient than doing it in the output plugin. -

    Prev Up Next
    48.8. Synchronous Replication Support for Logical Decoding Home Part VI. Reference
    \ No newline at end of file +

    Prev Up Next
    48.8. Synchronous Replication Support for Logical Decoding Home Part VI. Reference
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/resources.html postgresql-13-13.12/doc/src/sgml/html/resources.html --- postgresql-13-13.11/doc/src/sgml/html/resources.html 2023-05-08 21:33:47.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/resources.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -4. Further Information
    4. Further Information
    Prev UpPrefaceHome Next

    4. Further Information

    +4. Further Information

    4. Further Information
    Prev UpPrefaceHome Next

    4. Further Information

    Besides the documentation, that is, this book, there are other resources about PostgreSQL: @@ -29,4 +29,4 @@ up and contribute it. If you add features to the code, contribute them.

    -

    Prev Up Next
    3. Conventions Home 5. Bug Reporting Guidelines
    \ No newline at end of file +

    Prev Up Next
    3. Conventions Home 5. Bug Reporting Guidelines
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/role-attributes.html postgresql-13-13.12/doc/src/sgml/html/role-attributes.html --- postgresql-13-13.11/doc/src/sgml/html/role-attributes.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/role-attributes.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.2. Role Attributes
    21.2. Role Attributes
    Prev UpChapter 21. Database RolesHome Next

    21.2. Role Attributes

    +21.2. Role Attributes

    21.2. Role Attributes
    Prev UpChapter 21. Database RolesHome Next

    21.2. Role Attributes

    A database role can have a number of attributes that define its privileges and interact with the client authentication system. @@ -117,4 +117,4 @@ Note that role-specific defaults attached to roles without LOGIN privilege are fairly useless, since they will never be invoked. -

    Prev Up Next
    21.1. Database Roles Home 21.3. Role Membership
    \ No newline at end of file +

    Prev Up Next
    21.1. Database Roles Home 21.3. Role Membership
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/role-membership.html postgresql-13-13.12/doc/src/sgml/html/role-membership.html --- postgresql-13-13.11/doc/src/sgml/html/role-membership.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/role-membership.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.3. Role Membership
    21.3. Role Membership
    Prev UpChapter 21. Database RolesHome Next

    21.3. Role Membership

    +21.3. Role Membership

    21.3. Role Membership
    Prev UpChapter 21. Database RolesHome Next

    21.3. Role Membership

    It is frequently convenient to group users together to ease management of privileges: that way, privileges can be granted to, or revoked from, a group as a whole. In PostgreSQL @@ -104,4 +104,4 @@

    Any memberships in the group role are automatically revoked (but the member roles are not otherwise affected). -

    Prev Up Next
    21.2. Role Attributes Home 21.4. Dropping Roles
    \ No newline at end of file +

    Prev Up Next
    21.2. Role Attributes Home 21.4. Dropping Roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/role-removal.html postgresql-13-13.12/doc/src/sgml/html/role-removal.html --- postgresql-13-13.11/doc/src/sgml/html/role-removal.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/role-removal.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -21.4. Dropping Roles
    21.4. Dropping Roles
    Prev UpChapter 21. Database RolesHome Next

    21.4. Dropping Roles

    +21.4. Dropping Roles

    21.4. Dropping Roles
    Prev UpChapter 21. Database RolesHome Next

    21.4. Dropping Roles

    Because roles can own database objects and can hold privileges to access other objects, dropping a role is often not just a matter of a quick DROP ROLE. Any objects owned by the role must @@ -51,4 +51,4 @@ If DROP ROLE is attempted while dependent objects still remain, it will issue messages identifying which objects need to be reassigned or dropped. -

    Prev Up Next
    21.3. Role Membership Home 21.5. Default Roles
    \ No newline at end of file +

    Prev Up Next
    21.3. Role Membership Home 21.5. Default Roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/routine-reindex.html postgresql-13-13.12/doc/src/sgml/html/routine-reindex.html --- postgresql-13-13.11/doc/src/sgml/html/routine-reindex.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/routine-reindex.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -24.2. Routine Reindexing
    24.2. Routine Reindexing
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.2. Routine Reindexing

    +24.2. Routine Reindexing

    24.2. Routine Reindexing
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.2. Routine Reindexing

    In some situations it is worthwhile to rebuild indexes periodically with the REINDEX command or a series of individual rebuilding steps. @@ -28,4 +28,4 @@ default, hence it is often preferable to execute it with its CONCURRENTLY option, which requires only a SHARE UPDATE EXCLUSIVE lock. -

    Prev Up Next
    24.1. Routine Vacuuming Home 24.3. Log File Maintenance
    \ No newline at end of file +

    Prev Up Next
    24.1. Routine Vacuuming Home 24.3. Log File Maintenance
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/routine-vacuuming.html postgresql-13-13.12/doc/src/sgml/html/routine-vacuuming.html --- postgresql-13-13.11/doc/src/sgml/html/routine-vacuuming.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/routine-vacuuming.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -24.1. Routine Vacuuming
    24.1. Routine Vacuuming
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.1. Routine Vacuuming

    24.1.1. Vacuuming Basics
    24.1.2. Recovering Disk Space
    24.1.3. Updating Planner Statistics
    24.1.4. Updating the Visibility Map
    24.1.5. Preventing Transaction ID Wraparound Failures
    24.1.6. The Autovacuum Daemon

    +24.1. Routine Vacuuming

    24.1. Routine Vacuuming
    Prev UpChapter 24. Routine Database Maintenance TasksHome Next

    24.1. Routine Vacuuming

    24.1.1. Vacuuming Basics
    24.1.2. Recovering Disk Space
    24.1.3. Updating Planner Statistics
    24.1.4. Updating the Visibility Map
    24.1.5. Preventing Transaction ID Wraparound Failures
    24.1.6. The Autovacuum Daemon

    PostgreSQL databases require periodic maintenance known as vacuuming. For many installations, it is sufficient to let vacuuming be performed by the autovacuum @@ -627,4 +627,4 @@ Regularly running commands that acquire locks conflicting with a SHARE UPDATE EXCLUSIVE lock (e.g., ANALYZE) can effectively prevent autovacuums from ever completing. -

    Prev Up Next
    Chapter 24. Routine Database Maintenance Tasks Home 24.2. Routine Reindexing
    \ No newline at end of file +

    Prev Up Next
    Chapter 24. Routine Database Maintenance Tasks Home 24.2. Routine Reindexing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/row-estimation-examples.html postgresql-13-13.12/doc/src/sgml/html/row-estimation-examples.html --- postgresql-13-13.11/doc/src/sgml/html/row-estimation-examples.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/row-estimation-examples.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -71.1. Row Estimation Examples
    71.1. Row Estimation Examples
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.1. Row Estimation Examples

    +71.1. Row Estimation Examples

    71.1. Row Estimation Examples
    Prev UpChapter 71. How the Planner Uses StatisticsHome Next

    71.1. Row Estimation Examples

    The examples shown below use tables in the PostgreSQL regression test database. The outputs shown are taken from version 8.3. @@ -396,4 +396,4 @@ src/backend/optimizer/path/clausesel.c. The operator-specific selectivity functions are mostly found in src/backend/utils/adt/selfuncs.c. -

    Prev Up Next
    Chapter 71. How the Planner Uses Statistics Home 71.2. Multivariate Statistics Examples
    \ No newline at end of file +

    Prev Up Next
    Chapter 71. How the Planner Uses Statistics Home 71.2. Multivariate Statistics Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rowtypes.html postgresql-13-13.12/doc/src/sgml/html/rowtypes.html --- postgresql-13-13.11/doc/src/sgml/html/rowtypes.html 2023-05-08 21:33:49.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rowtypes.html 2023-08-07 20:32:08.000000000 +0000 @@ -1,5 +1,5 @@ -8.16. Composite Types
    8.16. Composite Types
    Prev UpChapter 8. Data TypesHome Next

    8.16. Composite Types

    8.16.1. Declaration of Composite Types
    8.16.2. Constructing Composite Values
    8.16.3. Accessing Composite Types
    8.16.4. Modifying Composite Types
    8.16.5. Using Composite Types in Queries
    8.16.6. Composite Type Input and Output Syntax

    +8.16. Composite Types

    8.16. Composite Types
    Prev UpChapter 8. Data TypesHome Next

    8.16. Composite Types

    8.16.1. Declaration of Composite Types
    8.16.2. Constructing Composite Values
    8.16.3. Accessing Composite Types
    8.16.4. Modifying Composite Types
    8.16.5. Using Composite Types in Queries
    8.16.6. Composite Type Input and Output Syntax

    A composite type represents the structure of a row or record; it is essentially just a list of field names and their data types. PostgreSQL allows composite types to be @@ -420,4 +420,4 @@ commands. In ROW, individual field values are written the same way they would be written when not members of a composite. -

    Prev Up Next
    8.15. Arrays Home 8.17. Range Types
    \ No newline at end of file +

    Prev Up Next
    8.15. Arrays Home 8.17. Range Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rule-system.html postgresql-13-13.12/doc/src/sgml/html/rule-system.html --- postgresql-13-13.11/doc/src/sgml/html/rule-system.html 2023-05-08 21:34:09.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rule-system.html 2023-08-07 20:32:29.000000000 +0000 @@ -1,5 +1,5 @@ -50.4. The PostgreSQL Rule System
    50.4. The PostgreSQL Rule System
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.4. The PostgreSQL Rule System

    +50.4. The PostgreSQL Rule System

    50.4. The PostgreSQL Rule System
    Prev UpChapter 50. Overview of PostgreSQL InternalsHome Next

    50.4. The PostgreSQL Rule System

    PostgreSQL supports a powerful rule system for the specification of views and ambiguous view updates. @@ -27,4 +27,4 @@ rewriter are query trees, that is, there is no change in the representation or level of semantic detail in the trees. Rewriting can be thought of as a form of macro expansion. -

    Prev Up Next
    50.3. The Parser Stage Home 50.5. Planner/Optimizer
    \ No newline at end of file +

    Prev Up Next
    50.3. The Parser Stage Home 50.5. Planner/Optimizer
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-materializedviews.html postgresql-13-13.12/doc/src/sgml/html/rules-materializedviews.html --- postgresql-13-13.11/doc/src/sgml/html/rules-materializedviews.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-materializedviews.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.3. Materialized Views
    40.3. Materialized Views
    Prev UpChapter 40. The Rule SystemHome Next

    40.3. Materialized Views

    +40.3. Materialized Views

    40.3. Materialized Views
    Prev UpChapter 40. The Rule SystemHome Next

    40.3. Materialized Views

    Materialized views in PostgreSQL use the rule system like views do, but persist the results in a table-like form. The main differences between: @@ -179,4 +179,4 @@ If you can tolerate periodic update of the remote data to the local database, the performance benefit can be substantial. -

    Prev Up Next
    40.2. Views and the Rule System Home 40.4. Rules on INSERT, UPDATE, and DELETE
    \ No newline at end of file +

    Prev Up Next
    40.2. Views and the Rule System Home 40.4. Rules on INSERT, UPDATE, and DELETE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-privileges.html postgresql-13-13.12/doc/src/sgml/html/rules-privileges.html --- postgresql-13-13.11/doc/src/sgml/html/rules-privileges.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-privileges.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.5. Rules and Privileges
    40.5. Rules and Privileges
    Prev UpChapter 40. The Rule SystemHome Next

    40.5. Rules and Privileges

    +40.5. Rules and Privileges

    40.5. Rules and Privileges
    Prev UpChapter 40. The Rule SystemHome Next

    40.5. Rules and Privileges

    Due to rewriting of queries by the PostgreSQL rule system, other tables/views than those used in the original query get accessed. When update rules are used, this can include write access @@ -154,4 +154,4 @@ the optimizer statistics, the choice of plan). If these types of "covert channel" attacks are of concern, it is probably unwise to grant any access to the data at all. -

    Prev Up Next
    40.4. Rules on INSERT, UPDATE, and DELETE Home 40.6. Rules and Command Status
    \ No newline at end of file +

    Prev Up Next
    40.4. Rules on INSERT, UPDATE, and DELETE Home 40.6. Rules and Command Status
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-status.html postgresql-13-13.12/doc/src/sgml/html/rules-status.html --- postgresql-13-13.11/doc/src/sgml/html/rules-status.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-status.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.6. Rules and Command Status
    40.6. Rules and Command Status
    Prev UpChapter 40. The Rule SystemHome Next

    40.6. Rules and Command Status

    +40.6. Rules and Command Status

    40.6. Rules and Command Status
    Prev UpChapter 40. The Rule SystemHome Next

    40.6. Rules and Command Status

    The PostgreSQL server returns a command status string, such as INSERT 149592 1, for each command it receives. This is simple enough when there are no rules @@ -32,4 +32,4 @@ that sets the command status in the second case, by giving it the alphabetically last rule name among the active rules, so that it gets applied last. -

    Prev Up Next
    40.5. Rules and Privileges Home 40.7. Rules Versus Triggers
    \ No newline at end of file +

    Prev Up Next
    40.5. Rules and Privileges Home 40.7. Rules Versus Triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-triggers.html postgresql-13-13.12/doc/src/sgml/html/rules-triggers.html --- postgresql-13-13.11/doc/src/sgml/html/rules-triggers.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-triggers.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.7. Rules Versus Triggers
    40.7. Rules Versus Triggers
    Prev UpChapter 40. The Rule SystemHome Next

    40.7. Rules Versus Triggers

    +40.7. Rules Versus Triggers

    40.7. Rules Versus Triggers
    Prev UpChapter 40. The Rule SystemHome Next

    40.7. Rules Versus Triggers

    Many things that can be done using triggers can also be implemented using the PostgreSQL rule system. One of the things that cannot be implemented by @@ -175,4 +175,4 @@ The summary is, rules will only be significantly slower than triggers if their actions result in large and badly qualified joins, a situation where the planner fails. -

    Prev Up Next
    40.6. Rules and Command Status Home Chapter 41. Procedural Languages
    \ No newline at end of file +

    Prev Up Next
    40.6. Rules and Command Status Home Chapter 41. Procedural Languages
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-update.html postgresql-13-13.12/doc/src/sgml/html/rules-update.html --- postgresql-13-13.11/doc/src/sgml/html/rules-update.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-update.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.4. Rules on INSERT, UPDATE, and DELETE
    40.4. Rules on INSERT, UPDATE, and DELETE
    Prev UpChapter 40. The Rule SystemHome Next

    40.4. Rules on INSERT, UPDATE, and DELETE

    40.4.1. How Update Rules Work
    40.4.2. Cooperation with Views

    +40.4. Rules on INSERT, UPDATE, and DELETE

    40.4. Rules on INSERT, UPDATE, and DELETE
    Prev UpChapter 40. The Rule SystemHome Next

    40.4. Rules on INSERT, UPDATE, and DELETE

    40.4.1. How Update Rules Work
    40.4.2. Cooperation with Views

    Rules that are defined on INSERT, UPDATE, and DELETE are significantly different from the view rules described in the previous section. First, their CREATE @@ -747,4 +747,4 @@ There are probably only a few situations out in the real world where such a construct is necessary. But it makes you feel comfortable that it works. -

    Prev Up Next
    40.3. Materialized Views Home 40.5. Rules and Privileges
    \ No newline at end of file +

    Prev Up Next
    40.3. Materialized Views Home 40.5. Rules and Privileges
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules-views.html postgresql-13-13.12/doc/src/sgml/html/rules-views.html --- postgresql-13-13.11/doc/src/sgml/html/rules-views.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules-views.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -40.2. Views and the Rule System
    40.2. Views and the Rule System
    Prev UpChapter 40. The Rule SystemHome Next

    40.2. Views and the Rule System

    40.2.1. How SELECT Rules Work
    40.2.2. View Rules in Non-SELECT Statements
    40.2.3. The Power of Views in PostgreSQL
    40.2.4. Updating a View

    +40.2. Views and the Rule System

    40.2. Views and the Rule System
    Prev UpChapter 40. The Rule SystemHome Next

    40.2. Views and the Rule System

    40.2.1. How SELECT Rules Work
    40.2.2. View Rules in Non-SELECT Statements
    40.2.3. The Power of Views in PostgreSQL
    40.2.4. Updating a View

    Views in PostgreSQL are implemented using the rule system. In fact, there is essentially no difference between: @@ -498,4 +498,4 @@ triggers for the view, and the rewriter cannot automatically rewrite the query as an update on the underlying base relation, an error will be thrown because the executor cannot update a view as such. -

    Prev Up Next
    40.1. The Query Tree Home 40.3. Materialized Views
    \ No newline at end of file +

    Prev Up Next
    40.1. The Query Tree Home 40.3. Materialized Views
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/rules.html postgresql-13-13.12/doc/src/sgml/html/rules.html --- postgresql-13-13.11/doc/src/sgml/html/rules.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/rules.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 40. The Rule System
    Chapter 40. The Rule System
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 40. The Rule System

    Table of Contents

    40.1. The Query Tree
    40.2. Views and the Rule System
    40.2.1. How SELECT Rules Work
    40.2.2. View Rules in Non-SELECT Statements
    40.2.3. The Power of Views in PostgreSQL
    40.2.4. Updating a View
    40.3. Materialized Views
    40.4. Rules on INSERT, UPDATE, and DELETE
    40.4.1. How Update Rules Work
    40.4.2. Cooperation with Views
    40.5. Rules and Privileges
    40.6. Rules and Command Status
    40.7. Rules Versus Triggers

    +Chapter 40. The Rule System

    Chapter 40. The Rule System
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 40. The Rule System

    Table of Contents

    40.1. The Query Tree
    40.2. Views and the Rule System
    40.2.1. How SELECT Rules Work
    40.2.2. View Rules in Non-SELECT Statements
    40.2.3. The Power of Views in PostgreSQL
    40.2.4. Updating a View
    40.3. Materialized Views
    40.4. Rules on INSERT, UPDATE, and DELETE
    40.4.1. How Update Rules Work
    40.4.2. Cooperation with Views
    40.5. Rules and Privileges
    40.6. Rules and Command Status
    40.7. Rules Versus Triggers

    This chapter discusses the rule system in PostgreSQL. Production rule systems are conceptually simple, but there are many subtle points @@ -18,4 +18,4 @@ such as query language procedures, views, and versions. The theoretical foundations and the power of this rule system are also discussed in [ston90b] and [ong90]. -

    Prev Up Next
    39.5. A Table Rewrite Event Trigger Example Home 40.1. The Query Tree
    \ No newline at end of file +

    Prev Up Next
    39.5. A Table Rewrite Event Trigger Example Home 40.1. The Query Tree
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-autovacuum.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-autovacuum.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-autovacuum.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-autovacuum.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.10. Automatic Vacuuming
    19.10. Automatic Vacuuming
    Prev UpChapter 19. Server ConfigurationHome Next

    19.10. Automatic Vacuuming

    +19.10. Automatic Vacuuming

    19.10. Automatic Vacuuming
    Prev UpChapter 19. Server ConfigurationHome Next

    19.10. Automatic Vacuuming

    These settings control the behavior of the autovacuum feature. Refer to Section 24.1.6 for more information. Note that many of these settings can be overridden on a per-table @@ -178,4 +178,4 @@ file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters. -

    Prev Up Next
    19.9. Run-time Statistics Home 19.11. Client Connection Defaults
    \ No newline at end of file +

    Prev Up Next
    19.9. Run-time Statistics Home 19.11. Client Connection Defaults
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-client.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-client.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-client.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-client.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.11. Client Connection Defaults
    19.11. Client Connection Defaults
    Prev UpChapter 19. Server ConfigurationHome Next

    19.11. Client Connection Defaults

    19.11.1. Statement Behavior
    19.11.2. Locale and Formatting
    19.11.3. Shared Library Preloading
    19.11.4. Other Defaults

    19.11.1. Statement Behavior

    client_min_messages (enum) +19.11. Client Connection Defaults
    19.11. Client Connection Defaults
    Prev UpChapter 19. Server ConfigurationHome Next

    19.11. Client Connection Defaults

    19.11.1. Statement Behavior
    19.11.2. Locale and Formatting
    19.11.3. Shared Library Preloading
    19.11.4. Other Defaults

    19.11.1. Statement Behavior

    client_min_messages (enum)

    Controls which @@ -768,4 +768,4 @@

    Soft upper limit of the size of the set returned by GIN index scans. For more information see Section 66.5. -

    Prev Up Next
    19.10. Automatic Vacuuming Home 19.12. Lock Management
    \ No newline at end of file +

    Prev Up Next
    19.10. Automatic Vacuuming Home 19.12. Lock Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-compatible.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-compatible.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-compatible.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-compatible.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.13. Version and Platform Compatibility
    19.13. Version and Platform Compatibility
    Prev UpChapter 19. Server ConfigurationHome Next

    19.13. Version and Platform Compatibility

    19.13.1. Previous PostgreSQL Versions
    19.13.2. Platform and Client Compatibility

    19.13.1. Previous PostgreSQL Versions

    array_nulls (boolean) +19.13. Version and Platform Compatibility
    19.13. Version and Platform Compatibility
    Prev UpChapter 19. Server ConfigurationHome Next

    19.13. Version and Platform Compatibility

    19.13.1. Previous PostgreSQL Versions
    19.13.2. Platform and Client Compatibility

    19.13.1. Previous PostgreSQL Versions

    array_nulls (boolean)

    This controls whether the array input parser recognizes @@ -151,4 +151,4 @@ Thus, this option is not a general fix for bad programming.

    Refer to Section 9.2 for related information. -

    Prev Up Next
    19.12. Lock Management Home 19.14. Error Handling
    \ No newline at end of file +

    Prev Up Next
    19.12. Lock Management Home 19.14. Error Handling
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-connection.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-connection.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-connection.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-connection.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.3. Connections and Authentication
    19.3. Connections and Authentication
    Prev UpChapter 19. Server ConfigurationHome Next

    19.3. Connections and Authentication

    19.3.1. Connection Settings
    19.3.2. Authentication
    19.3.3. SSL

    19.3.1. Connection Settings

    listen_addresses (string) +19.3. Connections and Authentication
    19.3. Connections and Authentication
    Prev UpChapter 19. Server ConfigurationHome Next

    19.3. Connections and Authentication

    19.3.1. Connection Settings
    19.3.2. Authentication
    19.3.3. SSL

    19.3.1. Connection Settings

    listen_addresses (string)

    Specifies the TCP/IP address(es) on which the server is @@ -469,4 +469,4 @@

    This parameter can only be set in the postgresql.conf file or on the server command line. -

    Prev Up Next
    19.2. File Locations Home 19.4. Resource Consumption
    \ No newline at end of file +

    Prev Up Next
    19.2. File Locations Home 19.4. Resource Consumption
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-custom.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-custom.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-custom.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-custom.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.16. Customized Options
    19.16. Customized Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.16. Customized Options

    +19.16. Customized Options

    19.16. Customized Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.16. Customized Options

    This feature was designed to allow parameters not normally known to PostgreSQL to be added by add-on modules (such as procedural languages). This allows extension modules to be @@ -17,4 +17,4 @@ its variable definitions, convert any placeholder values according to those definitions, and issue warnings for any unrecognized placeholders that begin with its extension name. -

    Prev Up Next
    19.15. Preset Options Home 19.17. Developer Options
    \ No newline at end of file +

    Prev Up Next
    19.15. Preset Options Home 19.17. Developer Options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-developer.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-developer.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-developer.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-developer.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.17. Developer Options
    19.17. Developer Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.17. Developer Options

    +19.17. Developer Options

    19.17. Developer Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.17. Developer Options

    The following parameters are intended for work on the PostgreSQL source code, and in some cases to assist with recovery of severely damaged databases. There @@ -298,4 +298,4 @@ Determines whether tuple deforming is JIT compiled, when JIT compilation is activated (see Section 31.2). The default is on. -

    Prev Up Next
    19.16. Customized Options Home 19.18. Short Options
    \ No newline at end of file +

    Prev Up Next
    19.16. Customized Options Home 19.18. Short Options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-error-handling.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-error-handling.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-error-handling.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-error-handling.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.14. Error Handling
    19.14. Error Handling
    Prev UpChapter 19. Server ConfigurationHome Next

    19.14. Error Handling

    exit_on_error (boolean) +19.14. Error Handling
    19.14. Error Handling
    Prev UpChapter 19. Server ConfigurationHome Next

    19.14. Error Handling

    exit_on_error (boolean)

    If on, any error will terminate the current session. By default, @@ -40,4 +40,4 @@ operation can be retried in a later checkpoint. Only set it to on after investigating the operating system's treatment of buffered data in case of write-back failure. -

    Prev Up Next
    19.13. Version and Platform Compatibility Home 19.15. Preset Options
    \ No newline at end of file +

    Prev Up Next
    19.13. Version and Platform Compatibility Home 19.15. Preset Options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-file-locations.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-file-locations.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-file-locations.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-file-locations.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.2. File Locations
    19.2. File Locations
    Prev UpChapter 19. Server ConfigurationHome Next

    19.2. File Locations

    +19.2. File Locations

    19.2. File Locations
    Prev UpChapter 19. Server ConfigurationHome Next

    19.2. File Locations

    In addition to the postgresql.conf file already mentioned, PostgreSQL uses two other manually-edited configuration files, which control @@ -71,4 +71,4 @@ When setting any of these parameters, a relative path will be interpreted with respect to the directory in which postgres is started. -

    Prev Up Next
    19.1. Setting Parameters Home 19.3. Connections and Authentication
    \ No newline at end of file +

    Prev Up Next
    19.1. Setting Parameters Home 19.3. Connections and Authentication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-locks.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-locks.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-locks.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-locks.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.12. Lock Management
    19.12. Lock Management
    Prev UpChapter 19. Server ConfigurationHome Next

    19.12. Lock Management

    deadlock_timeout (integer) +19.12. Lock Management
    19.12. Lock Management
    Prev UpChapter 19. Server ConfigurationHome Next

    19.12. Lock Management

    deadlock_timeout (integer) @@ -80,4 +80,4 @@ before the lock is promoted to covering the whole page. The default is 2. This parameter can only be set in the postgresql.conf file or on the server command line. -

    Prev Up Next
    19.11. Client Connection Defaults Home 19.13. Version and Platform Compatibility
    \ No newline at end of file +

    Prev Up Next
    19.11. Client Connection Defaults Home 19.13. Version and Platform Compatibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-logging.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-logging.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-logging.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-logging.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.8. Error Reporting and Logging
    19.8. Error Reporting and Logging
    Prev UpChapter 19. Server ConfigurationHome Next

    19.8. Error Reporting and Logging

    19.8.1. Where to Log
    19.8.2. When to Log
    19.8.3. What to Log
    19.8.4. Using CSV-Format Log Output
    19.8.5. Process Title

    19.8.1. Where to Log

    log_destination (string) +19.8. Error Reporting and Logging
    19.8. Error Reporting and Logging
    Prev UpChapter 19. Server ConfigurationHome Next

    19.8. Error Reporting and Logging

    19.8.1. Where to Log
    19.8.2. When to Log
    19.8.3. What to Log
    19.8.4. Using CSV-Format Log Output
    19.8.5. Process Title

    19.8.1. Where to Log

    log_destination (string)

    PostgreSQL supports several methods @@ -827,4 +827,4 @@ defaults to off on Windows due to that platform's larger overhead for updating the process title. Only superusers can change this setting. -

    Prev Up Next
    19.7. Query Planning Home 19.9. Run-time Statistics
    \ No newline at end of file +

    Prev Up Next
    19.7. Query Planning Home 19.9. Run-time Statistics
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-preset.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-preset.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-preset.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-preset.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.15. Preset Options
    19.15. Preset Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.15. Preset Options

    +19.15. Preset Options

    19.15. Preset Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.15. Preset Options

    The following “parameters” are read-only, and are determined when PostgreSQL is compiled or when it is installed. As such, they have been excluded from the sample @@ -123,4 +123,4 @@

    Reports the size of write ahead log segments. The default value is 16MB. See Section 29.4 for more information. -

    Prev Up Next
    19.14. Error Handling Home 19.16. Customized Options
    \ No newline at end of file +

    Prev Up Next
    19.14. Error Handling Home 19.16. Customized Options
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-query.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-query.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-query.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-query.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.7. Query Planning
    19.7. Query Planning
    Prev UpChapter 19. Server ConfigurationHome Next

    19.7. Query Planning

    19.7.1. Planner Method Configuration
    19.7.2. Planner Cost Constants
    19.7.3. Genetic Query Optimizer
    19.7.4. Other Planner Options

    19.7.1. Planner Method Configuration

    +19.7. Query Planning

    19.7. Query Planning
    Prev UpChapter 19. Server ConfigurationHome Next

    19.7. Query Planning

    19.7.1. Planner Method Configuration
    19.7.2. Planner Cost Constants
    19.7.3. Genetic Query Optimizer
    19.7.4. Other Planner Options

    19.7.1. Planner Method Configuration

    These configuration parameters provide a crude method of influencing the query plans chosen by the query optimizer. If the default plan chosen by the optimizer for a particular query @@ -557,4 +557,4 @@ This setting is considered when a cached plan is to be executed, not when it is prepared. For more information see PREPARE. -

    Prev Up Next
    19.6. Replication Home 19.8. Error Reporting and Logging
    \ No newline at end of file +

    Prev Up Next
    19.6. Replication Home 19.8. Error Reporting and Logging
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-replication.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-replication.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-replication.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-replication.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.6. Replication
    19.6. Replication
    Prev UpChapter 19. Server ConfigurationHome Next

    19.6. Replication

    19.6.1. Sending Servers
    19.6.2. Master Server
    19.6.3. Standby Servers
    19.6.4. Subscribers

    +19.6. Replication

    19.6. Replication
    Prev UpChapter 19. Server ConfigurationHome Next

    19.6. Replication

    19.6.1. Sending Servers
    19.6.2. Master Server
    19.6.3. Standby Servers
    19.6.4. Subscribers

    These settings control the behavior of the built-in streaming replication feature (see Section 26.2.5). Servers will be either a @@ -552,4 +552,4 @@ The default value is 2. This parameter can only be set in the postgresql.conf file or on the server command line. -

    Prev Up Next
    19.5. Write Ahead Log Home 19.7. Query Planning
    \ No newline at end of file +

    Prev Up Next
    19.5. Write Ahead Log Home 19.7. Query Planning
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-resource.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-resource.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-resource.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-resource.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.4. Resource Consumption
    19.4. Resource Consumption
    Prev UpChapter 19. Server ConfigurationHome Next

    19.4. Resource Consumption

    19.4.1. Memory
    19.4.2. Disk
    19.4.3. Kernel Resource Usage
    19.4.4. Cost-based Vacuum Delay
    19.4.5. Background Writer
    19.4.6. Asynchronous Behavior

    19.4.1. Memory

    shared_buffers (integer) +19.4. Resource Consumption
    19.4. Resource Consumption
    Prev UpChapter 19. Server ConfigurationHome Next

    19.4. Resource Consumption

    19.4.1. Memory
    19.4.2. Disk
    19.4.3. Kernel Resource Usage
    19.4.4. Cost-based Vacuum Delay
    19.4.5. Background Writer
    19.4.6. Asynchronous Behavior

    19.4.1. Memory

    shared_buffers (integer)

    Sets the amount of memory the database server uses for shared @@ -663,4 +663,4 @@ affected by this setting, such as system catalogs. For such tables this setting will neither reduce bloat nor create a possibility of a “snapshot too old” error on scanning. -

    Prev Up Next
    19.3. Connections and Authentication Home 19.5. Write Ahead Log
    \ No newline at end of file +

    Prev Up Next
    19.3. Connections and Authentication Home 19.5. Write Ahead Log
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-short.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-short.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-short.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-short.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.18. Short Options
    19.18. Short Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.18. Short Options

    +19.18. Short Options

    19.18. Short Options
    Prev UpChapter 19. Server ConfigurationHome Next

    19.18. Short Options

    For convenience there are also single letter command-line option switches available for some parameters. They are described in Table 19.3. Some of these @@ -21,4 +21,4 @@ enable_tidscan = off -Ffsync = off-h xlisten_addresses = x-ilisten_addresses = '*'-k xunix_socket_directories = x-lssl = on-N xmax_connections = x-Oallow_system_table_mods = on-p xport = x-Pignore_system_indexes = on-slog_statement_stats = on-S xwork_mem = x-tpa, -tpl, -telog_parser_stats = on, log_planner_stats = on, - log_executor_stats = on-W xpost_auth_delay = x


    Prev Up Next
    19.17. Developer Options Home Chapter 20. Client Authentication
    \ No newline at end of file + log_executor_stats = on-W xpost_auth_delay = x
    Prev Up Next
    19.17. Developer Options Home Chapter 20. Client Authentication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-statistics.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-statistics.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-statistics.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-statistics.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.9. Run-time Statistics
    19.9. Run-time Statistics
    Prev UpChapter 19. Server ConfigurationHome Next

    19.9. Run-time Statistics

    19.9.1. Query and Index Statistics Collector
    19.9.2. Statistics Monitoring

    19.9.1. Query and Index Statistics Collector

    +19.9. Run-time Statistics

    19.9. Run-time Statistics
    Prev UpChapter 19. Server ConfigurationHome Next

    19.9. Run-time Statistics

    19.9.1. Query and Index Statistics Collector
    19.9.2. Statistics Monitoring

    19.9.1. Query and Index Statistics Collector

    These parameters control server-wide statistics collection features. When statistics collection is enabled, the data that is produced can be accessed via the pg_stat and @@ -86,4 +86,4 @@ log_statement_stats cannot be enabled together with any of the per-module options. All of these options are disabled by default. Only superusers can change these settings. -

    Prev Up Next
    19.8. Error Reporting and Logging Home 19.10. Automatic Vacuuming
    \ No newline at end of file +

    Prev Up Next
    19.8. Error Reporting and Logging Home 19.10. Automatic Vacuuming
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config-wal.html postgresql-13-13.12/doc/src/sgml/html/runtime-config-wal.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config-wal.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config-wal.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -19.5. Write Ahead Log
    19.5. Write Ahead Log
    Prev UpChapter 19. Server ConfigurationHome Next

    19.5. Write Ahead Log

    19.5.1. Settings
    19.5.2. Checkpoints
    19.5.3. Archiving
    19.5.4. Archive Recovery
    19.5.5. Recovery Target

    +19.5. Write Ahead Log

    19.5. Write Ahead Log
    Prev UpChapter 19. Server ConfigurationHome Next

    19.5. Write Ahead Log

    19.5.1. Settings
    19.5.2. Checkpoints
    19.5.3. Archiving
    19.5.4. Archive Recovery
    19.5.5. Recovery Target

    For additional information on tuning these settings, see Section 29.4.

    19.5.1. Settings

    wal_level (enum) @@ -758,4 +758,4 @@ In any case, if a recovery target is configured but the archive recovery ends before the target is reached, the server will shut down with a fatal error. -

    Prev Up Next
    19.4. Resource Consumption Home 19.6. Replication
    \ No newline at end of file +

    Prev Up Next
    19.4. Resource Consumption Home 19.6. Replication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime-config.html postgresql-13-13.12/doc/src/sgml/html/runtime-config.html --- postgresql-13-13.11/doc/src/sgml/html/runtime-config.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime-config.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,7 +1,7 @@ -Chapter 19. Server Configuration
    Chapter 19. Server Configuration
    Prev UpPart III. Server AdministrationHome Next

    Chapter 19. Server Configuration

    Table of Contents

    19.1. Setting Parameters
    19.1.1. Parameter Names and Values
    19.1.2. Parameter Interaction via the Configuration File
    19.1.3. Parameter Interaction via SQL
    19.1.4. Parameter Interaction via the Shell
    19.1.5. Managing Configuration File Contents
    19.2. File Locations
    19.3. Connections and Authentication
    19.3.1. Connection Settings
    19.3.2. Authentication
    19.3.3. SSL
    19.4. Resource Consumption
    19.4.1. Memory
    19.4.2. Disk
    19.4.3. Kernel Resource Usage
    19.4.4. Cost-based Vacuum Delay
    19.4.5. Background Writer
    19.4.6. Asynchronous Behavior
    19.5. Write Ahead Log
    19.5.1. Settings
    19.5.2. Checkpoints
    19.5.3. Archiving
    19.5.4. Archive Recovery
    19.5.5. Recovery Target
    19.6. Replication
    19.6.1. Sending Servers
    19.6.2. Master Server
    19.6.3. Standby Servers
    19.6.4. Subscribers
    19.7. Query Planning
    19.7.1. Planner Method Configuration
    19.7.2. Planner Cost Constants
    19.7.3. Genetic Query Optimizer
    19.7.4. Other Planner Options
    19.8. Error Reporting and Logging
    19.8.1. Where to Log
    19.8.2. When to Log
    19.8.3. What to Log
    19.8.4. Using CSV-Format Log Output
    19.8.5. Process Title
    19.9. Run-time Statistics
    19.9.1. Query and Index Statistics Collector
    19.9.2. Statistics Monitoring
    19.10. Automatic Vacuuming
    19.11. Client Connection Defaults
    19.11.1. Statement Behavior
    19.11.2. Locale and Formatting
    19.11.3. Shared Library Preloading
    19.11.4. Other Defaults
    19.12. Lock Management
    19.13. Version and Platform Compatibility
    19.13.1. Previous PostgreSQL Versions
    19.13.2. Platform and Client Compatibility
    19.14. Error Handling
    19.15. Preset Options
    19.16. Customized Options
    19.17. Developer Options
    19.18. Short Options

    +Chapter 19. Server Configuration

    Chapter 19. Server Configuration
    Prev UpPart III. Server AdministrationHome Next

    Chapter 19. Server Configuration

    Table of Contents

    19.1. Setting Parameters
    19.1.1. Parameter Names and Values
    19.1.2. Parameter Interaction via the Configuration File
    19.1.3. Parameter Interaction via SQL
    19.1.4. Parameter Interaction via the Shell
    19.1.5. Managing Configuration File Contents
    19.2. File Locations
    19.3. Connections and Authentication
    19.3.1. Connection Settings
    19.3.2. Authentication
    19.3.3. SSL
    19.4. Resource Consumption
    19.4.1. Memory
    19.4.2. Disk
    19.4.3. Kernel Resource Usage
    19.4.4. Cost-based Vacuum Delay
    19.4.5. Background Writer
    19.4.6. Asynchronous Behavior
    19.5. Write Ahead Log
    19.5.1. Settings
    19.5.2. Checkpoints
    19.5.3. Archiving
    19.5.4. Archive Recovery
    19.5.5. Recovery Target
    19.6. Replication
    19.6.1. Sending Servers
    19.6.2. Master Server
    19.6.3. Standby Servers
    19.6.4. Subscribers
    19.7. Query Planning
    19.7.1. Planner Method Configuration
    19.7.2. Planner Cost Constants
    19.7.3. Genetic Query Optimizer
    19.7.4. Other Planner Options
    19.8. Error Reporting and Logging
    19.8.1. Where to Log
    19.8.2. When to Log
    19.8.3. What to Log
    19.8.4. Using CSV-Format Log Output
    19.8.5. Process Title
    19.9. Run-time Statistics
    19.9.1. Query and Index Statistics Collector
    19.9.2. Statistics Monitoring
    19.10. Automatic Vacuuming
    19.11. Client Connection Defaults
    19.11.1. Statement Behavior
    19.11.2. Locale and Formatting
    19.11.3. Shared Library Preloading
    19.11.4. Other Defaults
    19.12. Lock Management
    19.13. Version and Platform Compatibility
    19.13.1. Previous PostgreSQL Versions
    19.13.2. Platform and Client Compatibility
    19.14. Error Handling
    19.15. Preset Options
    19.16. Customized Options
    19.17. Developer Options
    19.18. Short Options

    There are many configuration parameters that affect the behavior of the database system. In the first section of this chapter we describe how to interact with configuration parameters. The subsequent sections discuss each parameter in detail. -

    Prev Up Next
    18.12. Registering Event Log on Windows Home 19.1. Setting Parameters
    \ No newline at end of file +

    Prev Up Next
    18.12. Registering Event Log on Windows Home 19.1. Setting Parameters
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/runtime.html postgresql-13-13.12/doc/src/sgml/html/runtime.html --- postgresql-13-13.11/doc/src/sgml/html/runtime.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/runtime.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 18. Server Setup and Operation
    Chapter 18. Server Setup and Operation
    Prev UpPart III. Server AdministrationHome Next

    Chapter 18. Server Setup and Operation

    Table of Contents

    18.1. The PostgreSQL User Account
    18.2. Creating a Database Cluster
    18.2.1. Use of Secondary File Systems
    18.2.2. File Systems
    18.3. Starting the Database Server
    18.3.1. Server Start-up Failures
    18.3.2. Client Connection Problems
    18.4. Managing Kernel Resources
    18.4.1. Shared Memory and Semaphores
    18.4.2. systemd RemoveIPC
    18.4.3. Resource Limits
    18.4.4. Linux Memory Overcommit
    18.4.5. Linux Huge Pages
    18.5. Shutting Down the Server
    18.6. Upgrading a PostgreSQL Cluster
    18.6.1. Upgrading Data via pg_dumpall
    18.6.2. Upgrading Data via pg_upgrade
    18.6.3. Upgrading Data via Replication
    18.7. Preventing Server Spoofing
    18.8. Encryption Options
    18.9. Secure TCP/IP Connections with SSL
    18.9.1. Basic Setup
    18.9.2. OpenSSL Configuration
    18.9.3. Using Client Certificates
    18.9.4. SSL Server File Usage
    18.9.5. Creating Certificates
    18.10. Secure TCP/IP Connections with GSSAPI Encryption
    18.10.1. Basic Setup
    18.11. Secure TCP/IP Connections with SSH Tunnels
    18.12. Registering Event Log on Windows

    +Chapter 18. Server Setup and Operation

    Chapter 18. Server Setup and Operation
    Prev UpPart III. Server AdministrationHome Next
    Prev Up Next
    17.1. Building with Visual C++ or the - Microsoft Windows SDK Home 18.1. The PostgreSQL User Account
    \ No newline at end of file + Microsoft Windows SDK Home 18.1. The PostgreSQL User Account
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sasl-authentication.html postgresql-13-13.12/doc/src/sgml/html/sasl-authentication.html --- postgresql-13-13.11/doc/src/sgml/html/sasl-authentication.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sasl-authentication.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -52.3. SASL Authentication
    52.3. SASL Authentication
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.3. SASL Authentication

    52.3.1. SCRAM-SHA-256 Authentication

    +52.3. SASL Authentication

    52.3. SASL Authentication
    Prev UpChapter 52. Frontend/Backend ProtocolHome Next

    52.3. SASL Authentication

    52.3.1. SCRAM-SHA-256 Authentication

    SASL is a framework for authentication in connection-oriented protocols. At the moment, PostgreSQL implements two SASL authentication mechanisms, SCRAM-SHA-256 and SCRAM-SHA-256-PLUS. More @@ -100,4 +100,4 @@ Server sends an AuthenticationSASLFinal message, with the SCRAM server-final-message, followed immediately by an AuthenticationOk message. -

    Prev Up Next
    52.2. Message Flow Home 52.4. Streaming Replication Protocol
    \ No newline at end of file +

    Prev Up Next
    52.2. Message Flow Home 52.4. Streaming Replication Protocol
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/seg.html postgresql-13-13.12/doc/src/sgml/html/seg.html --- postgresql-13-13.11/doc/src/sgml/html/seg.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/seg.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.34. seg
    F.34. seg
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.34. seg

    F.34.1. Rationale
    F.34.2. Syntax
    F.34.3. Precision
    F.34.4. Usage
    F.34.5. Notes
    F.34.6. Credits

    +F.34. seg

    F.34. seg
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.34. seg

    F.34.1. Rationale
    F.34.2. Syntax
    F.34.3. Precision
    F.34.4. Usage
    F.34.5. Notes
    F.34.6. Credits

    This module implements a data type seg for representing line segments, or floating point intervals. seg can represent uncertainty in the interval endpoints, @@ -225,4 +225,4 @@ myself to create my own world and live undisturbed in it. And I would like to acknowledge my gratitude to Argonne Lab and to the U.S. Department of Energy for the years of faithful support of my database research. -

    Prev Up Next
    F.33. postgres_fdw Home F.35. sepgsql
    \ No newline at end of file +

    Prev Up Next
    F.33. postgres_fdw Home F.35. sepgsql
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sepgsql.html postgresql-13-13.12/doc/src/sgml/html/sepgsql.html --- postgresql-13-13.11/doc/src/sgml/html/sepgsql.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sepgsql.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.35. sepgsql
    F.35. sepgsql
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.35. sepgsql

    F.35.1. Overview
    F.35.2. Installation
    F.35.3. Regression Tests
    F.35.4. GUC Parameters
    F.35.5. Features
    F.35.6. Sepgsql Functions
    F.35.7. Limitations
    F.35.8. External Resources
    F.35.9. Author

    +F.35. sepgsql

    F.35. sepgsql
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.35. sepgsql

    F.35.1. Overview
    F.35.2. Installation
    F.35.3. Regression Tests
    F.35.4. GUC Parameters
    F.35.5. Features
    F.35.6. Sepgsql Functions
    F.35.7. Limitations
    F.35.8. External Resources
    F.35.9. Author

    sepgsql is a loadable module that supports label-based mandatory access control (MAC) based on SELinux security policy. @@ -517,4 +517,4 @@ It focuses primarily on Fedora, but is not limited to Fedora.

    F.35.9. Author

    KaiGai Kohei -

    Prev Up Next
    F.34. seg Home F.36. spi
    \ No newline at end of file +

    Prev Up Next
    F.34. seg Home F.36. spi
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/server-programming.html postgresql-13-13.12/doc/src/sgml/html/server-programming.html --- postgresql-13-13.11/doc/src/sgml/html/server-programming.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/server-programming.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -Part V. Server Programming
    Part V. Server Programming
    Prev UpPostgreSQL 13.11 DocumentationHome Next

    Part V. Server Programming

    +Part V. Server Programming

    Part V. Server Programming
    Prev UpPostgreSQL 13.12 DocumentationHome Next

    Part V. Server Programming

    This part is about extending the server functionality with user-defined functions, data types, triggers, etc. These are advanced topics which should probably be approached only after all @@ -10,4 +10,4 @@ general issues concerning server-side programming languages. It is essential to read at least the earlier sections of Chapter 37 (covering functions) before diving into the material about server-side programming languages. -

    Table of Contents

    37. Extending SQL
    37.1. How Extensibility Works
    37.2. The PostgreSQL Type System
    37.3. User-Defined Functions
    37.4. User-Defined Procedures
    37.5. Query Language (SQL) Functions
    37.6. Function Overloading
    37.7. Function Volatility Categories
    37.8. Procedural Language Functions
    37.9. Internal Functions
    37.10. C-Language Functions
    37.11. Function Optimization Information
    37.12. User-Defined Aggregates
    37.13. User-Defined Types
    37.14. User-Defined Operators
    37.15. Operator Optimization Information
    37.16. Interfacing Extensions to Indexes
    37.17. Packaging Related Objects into an Extension
    37.18. Extension Building Infrastructure
    38. Triggers
    38.1. Overview of Trigger Behavior
    38.2. Visibility of Data Changes
    38.3. Writing Trigger Functions in C
    38.4. A Complete Trigger Example
    39. Event Triggers
    39.1. Overview of Event Trigger Behavior
    39.2. Event Trigger Firing Matrix
    39.3. Writing Event Trigger Functions in C
    39.4. A Complete Event Trigger Example
    39.5. A Table Rewrite Event Trigger Example
    40. The Rule System
    40.1. The Query Tree
    40.2. Views and the Rule System
    40.3. Materialized Views
    40.4. Rules on INSERT, UPDATE, and DELETE
    40.5. Rules and Privileges
    40.6. Rules and Command Status
    40.7. Rules Versus Triggers
    41. Procedural Languages
    41.1. Installing Procedural Languages
    42. PL/pgSQL — SQL Procedural Language
    42.1. Overview
    42.2. Structure of PL/pgSQL
    42.3. Declarations
    42.4. Expressions
    42.5. Basic Statements
    42.6. Control Structures
    42.7. Cursors
    42.8. Transaction Management
    42.9. Errors and Messages
    42.10. Trigger Functions
    42.11. PL/pgSQL under the Hood
    42.12. Tips for Developing in PL/pgSQL
    42.13. Porting from Oracle PL/SQL
    43. PL/Tcl — Tcl Procedural Language
    43.1. Overview
    43.2. PL/Tcl Functions and Arguments
    43.3. Data Values in PL/Tcl
    43.4. Global Data in PL/Tcl
    43.5. Database Access from PL/Tcl
    43.6. Trigger Functions in PL/Tcl
    43.7. Event Trigger Functions in PL/Tcl
    43.8. Error Handling in PL/Tcl
    43.9. Explicit Subtransactions in PL/Tcl
    43.10. Transaction Management
    43.11. PL/Tcl Configuration
    43.12. Tcl Procedure Names
    44. PL/Perl — Perl Procedural Language
    44.1. PL/Perl Functions and Arguments
    44.2. Data Values in PL/Perl
    44.3. Built-in Functions
    44.4. Global Values in PL/Perl
    44.5. Trusted and Untrusted PL/Perl
    44.6. PL/Perl Triggers
    44.7. PL/Perl Event Triggers
    44.8. PL/Perl Under the Hood
    45. PL/Python — Python Procedural Language
    45.1. Python 2 vs. Python 3
    45.2. PL/Python Functions
    45.3. Data Values
    45.4. Sharing Data
    45.5. Anonymous Code Blocks
    45.6. Trigger Functions
    45.7. Database Access
    45.8. Explicit Subtransactions
    45.9. Transaction Management
    45.10. Utility Functions
    45.11. Environment Variables
    46. Server Programming Interface
    46.1. Interface Functions
    46.2. Interface Support Functions
    46.3. Memory Management
    46.4. Transaction Management
    46.5. Visibility of Data Changes
    46.6. Examples
    47. Background Worker Processes
    48. Logical Decoding
    48.1. Logical Decoding Examples
    48.2. Logical Decoding Concepts
    48.3. Streaming Replication Protocol Interface
    48.4. Logical Decoding SQL Interface
    48.5. System Catalogs Related to Logical Decoding
    48.6. Logical Decoding Output Plugins
    48.7. Logical Decoding Output Writers
    48.8. Synchronous Replication Support for Logical Decoding
    49. Replication Progress Tracking
    Prev Up Next
    36.62. views Home Chapter 37. Extending SQL
    \ No newline at end of file +

    Table of Contents

    37. Extending SQL
    37.1. How Extensibility Works
    37.2. The PostgreSQL Type System
    37.3. User-Defined Functions
    37.4. User-Defined Procedures
    37.5. Query Language (SQL) Functions
    37.6. Function Overloading
    37.7. Function Volatility Categories
    37.8. Procedural Language Functions
    37.9. Internal Functions
    37.10. C-Language Functions
    37.11. Function Optimization Information
    37.12. User-Defined Aggregates
    37.13. User-Defined Types
    37.14. User-Defined Operators
    37.15. Operator Optimization Information
    37.16. Interfacing Extensions to Indexes
    37.17. Packaging Related Objects into an Extension
    37.18. Extension Building Infrastructure
    38. Triggers
    38.1. Overview of Trigger Behavior
    38.2. Visibility of Data Changes
    38.3. Writing Trigger Functions in C
    38.4. A Complete Trigger Example
    39. Event Triggers
    39.1. Overview of Event Trigger Behavior
    39.2. Event Trigger Firing Matrix
    39.3. Writing Event Trigger Functions in C
    39.4. A Complete Event Trigger Example
    39.5. A Table Rewrite Event Trigger Example
    40. The Rule System
    40.1. The Query Tree
    40.2. Views and the Rule System
    40.3. Materialized Views
    40.4. Rules on INSERT, UPDATE, and DELETE
    40.5. Rules and Privileges
    40.6. Rules and Command Status
    40.7. Rules Versus Triggers
    41. Procedural Languages
    41.1. Installing Procedural Languages
    42. PL/pgSQL — SQL Procedural Language
    42.1. Overview
    42.2. Structure of PL/pgSQL
    42.3. Declarations
    42.4. Expressions
    42.5. Basic Statements
    42.6. Control Structures
    42.7. Cursors
    42.8. Transaction Management
    42.9. Errors and Messages
    42.10. Trigger Functions
    42.11. PL/pgSQL under the Hood
    42.12. Tips for Developing in PL/pgSQL
    42.13. Porting from Oracle PL/SQL
    43. PL/Tcl — Tcl Procedural Language
    43.1. Overview
    43.2. PL/Tcl Functions and Arguments
    43.3. Data Values in PL/Tcl
    43.4. Global Data in PL/Tcl
    43.5. Database Access from PL/Tcl
    43.6. Trigger Functions in PL/Tcl
    43.7. Event Trigger Functions in PL/Tcl
    43.8. Error Handling in PL/Tcl
    43.9. Explicit Subtransactions in PL/Tcl
    43.10. Transaction Management
    43.11. PL/Tcl Configuration
    43.12. Tcl Procedure Names
    44. PL/Perl — Perl Procedural Language
    44.1. PL/Perl Functions and Arguments
    44.2. Data Values in PL/Perl
    44.3. Built-in Functions
    44.4. Global Values in PL/Perl
    44.5. Trusted and Untrusted PL/Perl
    44.6. PL/Perl Triggers
    44.7. PL/Perl Event Triggers
    44.8. PL/Perl Under the Hood
    45. PL/Python — Python Procedural Language
    45.1. Python 2 vs. Python 3
    45.2. PL/Python Functions
    45.3. Data Values
    45.4. Sharing Data
    45.5. Anonymous Code Blocks
    45.6. Trigger Functions
    45.7. Database Access
    45.8. Explicit Subtransactions
    45.9. Transaction Management
    45.10. Utility Functions
    45.11. Environment Variables
    46. Server Programming Interface
    46.1. Interface Functions
    46.2. Interface Support Functions
    46.3. Memory Management
    46.4. Transaction Management
    46.5. Visibility of Data Changes
    46.6. Examples
    47. Background Worker Processes
    48. Logical Decoding
    48.1. Logical Decoding Examples
    48.2. Logical Decoding Concepts
    48.3. Streaming Replication Protocol Interface
    48.4. Logical Decoding SQL Interface
    48.5. System Catalogs Related to Logical Decoding
    48.6. Logical Decoding Output Plugins
    48.7. Logical Decoding Output Writers
    48.8. Synchronous Replication Support for Logical Decoding
    49. Replication Progress Tracking
    Prev Up Next
    36.62. views Home Chapter 37. Extending SQL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/server-shutdown.html postgresql-13-13.12/doc/src/sgml/html/server-shutdown.html --- postgresql-13-13.11/doc/src/sgml/html/server-shutdown.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/server-shutdown.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.5. Shutting Down the Server
    18.5. Shutting Down the Server
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.5. Shutting Down the Server

    +18.5. Shutting Down the Server

    18.5. Shutting Down the Server
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.5. Shutting Down the Server

    There are several ways to shut down the database server. Under the hood, they all reduce to sending a signal to the supervisor postgres process. @@ -69,4 +69,4 @@ continue, use pg_terminate_backend() (see Table 9.84) or send a SIGTERM signal to the child process associated with the session. -

    Prev Up Next
    18.4. Managing Kernel Resources Home 18.6. Upgrading a PostgreSQL Cluster
    \ No newline at end of file +

    Prev Up Next
    18.4. Managing Kernel Resources Home 18.6. Upgrading a PostgreSQL Cluster
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/server-start.html postgresql-13-13.12/doc/src/sgml/html/server-start.html --- postgresql-13-13.11/doc/src/sgml/html/server-start.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/server-start.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.3. Starting the Database Server
    18.3. Starting the Database Server
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.3. Starting the Database Server

    18.3.1. Server Start-up Failures
    18.3.2. Client Connection Problems

    +18.3. Starting the Database Server

    18.3. Starting the Database Server
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.3. Starting the Database Server

    18.3.1. Server Start-up Failures
    18.3.2. Client Connection Problems

    Before anyone can access the database, you must start the database server. The database server program is called postgres. @@ -254,4 +254,4 @@ such as Connection timed out might indicate more fundamental problems, like lack of network connectivity. -

    Prev Up Next
    18.2. Creating a Database Cluster Home 18.4. Managing Kernel Resources
    \ No newline at end of file +

    Prev Up Next
    18.2. Creating a Database Cluster Home 18.4. Managing Kernel Resources
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/source-conventions.html postgresql-13-13.12/doc/src/sgml/html/source-conventions.html --- postgresql-13-13.11/doc/src/sgml/html/source-conventions.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/source-conventions.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -53.4. Miscellaneous Coding Conventions
    53.4. Miscellaneous Coding Conventions
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.4. Miscellaneous Coding Conventions

    C Standard

    +53.4. Miscellaneous Coding Conventions

    53.4. Miscellaneous Coding Conventions
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.4. Miscellaneous Coding Conventions

    C Standard

    Code in PostgreSQL should only rely on language features available in the C99 standard. That means a conforming C99 compiler has to be able to compile postgres, at least aside @@ -103,4 +103,4 @@ 

     paramInfo->paramFetch(paramInfo, paramId);

    -

    Prev Up Next
    53.3. Error Message Style Guide Home Chapter 54. Native Language Support
    \ No newline at end of file +

    Prev Up Next
    53.3. Error Message Style Guide Home Chapter 54. Native Language Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/source-format.html postgresql-13-13.12/doc/src/sgml/html/source-format.html --- postgresql-13-13.11/doc/src/sgml/html/source-format.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/source-format.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -53.1. Formatting
    53.1. Formatting
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.1. Formatting

    +53.1. Formatting

    53.1. Formatting
    Prev UpChapter 53. PostgreSQL Coding ConventionsHome Next

    53.1. Formatting

    Source code formatting uses 4 column tab spacing, with tabs preserved (i.e., tabs are not expanded to spaces). Each logical indentation level is one additional tab stop. @@ -56,4 +56,4 @@ less -x4

    to make them show tabs appropriately. -

    Prev Up Next
    Chapter 53. PostgreSQL Coding Conventions Home 53.2. Reporting Errors Within the Server
    \ No newline at end of file +

    Prev Up Next
    Chapter 53. PostgreSQL Coding Conventions Home 53.2. Reporting Errors Within the Server
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/source.html postgresql-13-13.12/doc/src/sgml/html/source.html --- postgresql-13-13.11/doc/src/sgml/html/source.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/source.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 53. PostgreSQL Coding Conventions
    Chapter 53. PostgreSQL Coding Conventions
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    52.10. Summary of Changes since Protocol 2.0 Home 53.1. Formatting
    \ No newline at end of file +Chapter 53. PostgreSQL Coding Conventions
    Chapter 53. PostgreSQL Coding Conventions
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    52.10. Summary of Changes since Protocol 2.0 Home 53.1. Formatting
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sourcerepo.html postgresql-13-13.12/doc/src/sgml/html/sourcerepo.html --- postgresql-13-13.11/doc/src/sgml/html/sourcerepo.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sourcerepo.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -Appendix I. The Source Code Repository
    Appendix I. The Source Code Repository
    Prev UpPart VIII. AppendixesHome Next

    Appendix I. The Source Code Repository

    Table of Contents

    I.1. Getting the Source via Git

    +Appendix I. The Source Code Repository

    Appendix I. The Source Code Repository
    Prev UpPart VIII. AppendixesHome Next

    Appendix I. The Source Code Repository

    Table of Contents

    I.1. Getting the Source via Git

    The PostgreSQL source code is stored and managed using the Git version control system. A public mirror of the master repository is available; it is updated within a minute @@ -14,4 +14,4 @@ to build from a distribution tarball, because the files that these tools are used to build are included in the tarball. Other tool requirements are the same as shown in Section 16.2. -

    Prev Up Next
    H.4. Extensions Home I.1. Getting the Source via Git
    \ No newline at end of file +

    Prev Up Next
    H.4. Extensions Home I.1. Getting the Source via Git
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist-builtin-opclasses.html postgresql-13-13.12/doc/src/sgml/html/spgist-builtin-opclasses.html --- postgresql-13-13.11/doc/src/sgml/html/spgist-builtin-opclasses.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist-builtin-opclasses.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -65.2. Built-in Operator Classes
    65.2. Built-in Operator Classes
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.2. Built-in Operator Classes

    +65.2. Built-in Operator Classes

    65.2. Built-in Operator Classes
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.2. Built-in Operator Classes

    The core PostgreSQL distribution includes the SP-GiST operator classes shown in Table 65.1. @@ -97,4 +97,4 @@ poly_ops operator classes support the <-> ordering operator, which enables the k-nearest neighbor (k-NN) search over indexed point or polygon data sets. -

    Prev Up Next
    65.1. Introduction Home 65.3. Extensibility
    \ No newline at end of file +

    Prev Up Next
    65.1. Introduction Home 65.3. Extensibility
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist-examples.html postgresql-13-13.12/doc/src/sgml/html/spgist-examples.html --- postgresql-13-13.11/doc/src/sgml/html/spgist-examples.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist-examples.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,8 +1,8 @@ -65.5. Examples
    65.5. Examples
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.5. Examples

    +65.5. Examples

    65.5. Examples
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.5. Examples

    The PostgreSQL source distribution includes several examples of index operator classes for SP-GiST, as described in Table 65.1. Look into src/backend/access/spgist/ and src/backend/utils/adt/ to see the code. -

    Prev Up Next
    65.4. Implementation Home Chapter 66. GIN Indexes
    \ No newline at end of file +

    Prev Up Next
    65.4. Implementation Home Chapter 66. GIN Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist-extensibility.html postgresql-13-13.12/doc/src/sgml/html/spgist-extensibility.html --- postgresql-13-13.11/doc/src/sgml/html/spgist-extensibility.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist-extensibility.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -65.3. Extensibility
    65.3. Extensibility
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.3. Extensibility

    +65.3. Extensibility

    65.3. Extensibility
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.3. Extensibility

    SP-GiST offers an interface with a high level of abstraction, requiring the access method developer to implement only methods specific to a given data type. The SP-GiST core @@ -594,4 +594,4 @@ If the indexed column is of a collatable data type, the index collation will be passed to all the support methods, using the standard PG_GET_COLLATION() mechanism. -

    Prev Up Next
    65.2. Built-in Operator Classes Home 65.4. Implementation
    \ No newline at end of file +

    Prev Up Next
    65.2. Built-in Operator Classes Home 65.4. Implementation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist-implementation.html postgresql-13-13.12/doc/src/sgml/html/spgist-implementation.html --- postgresql-13-13.11/doc/src/sgml/html/spgist-implementation.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist-implementation.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -65.4. Implementation
    65.4. Implementation
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.4. Implementation

    65.4.1. SP-GiST Limits
    65.4.2. SP-GiST Without Node Labels
    65.4.3. “All-the-Same” Inner Tuples

    +65.4. Implementation

    65.4. Implementation
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.4. Implementation

    65.4.1. SP-GiST Limits
    65.4.2. SP-GiST Without Node Labels
    65.4.3. “All-the-Same” Inner Tuples

    This section covers implementation details and other tricks that are useful for implementers of SP-GiST operator classes to know. @@ -87,4 +87,4 @@ all equivalent. This may or may not require any special-case code, depending on how much the inner_consistent function normally assumes about the meaning of the nodes. -

    Prev Up Next
    65.3. Extensibility Home 65.5. Examples
    \ No newline at end of file +

    Prev Up Next
    65.3. Extensibility Home 65.5. Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist-intro.html postgresql-13-13.12/doc/src/sgml/html/spgist-intro.html --- postgresql-13-13.11/doc/src/sgml/html/spgist-intro.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist-intro.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -65.1. Introduction
    65.1. Introduction
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.1. Introduction

    +65.1. Introduction

    65.1. Introduction
    Prev UpChapter 65. SP-GiST IndexesHome Next

    65.1. Introduction

    SP-GiST is an abbreviation for space-partitioned GiST. SP-GiST supports partitioned search trees, which facilitate development of a wide range of different @@ -31,4 +31,4 @@ Sigaev and Oleg Bartunov, and there is more information on their web site. -

    Prev Up Next
    Chapter 65. SP-GiST Indexes Home 65.2. Built-in Operator Classes
    \ No newline at end of file +

    Prev Up Next
    Chapter 65. SP-GiST Indexes Home 65.2. Built-in Operator Classes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spgist.html postgresql-13-13.12/doc/src/sgml/html/spgist.html --- postgresql-13-13.11/doc/src/sgml/html/spgist.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spgist.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 65. SP-GiST Indexes
    Chapter 65. SP-GiST Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    64.5. Examples Home 65.1. Introduction
    \ No newline at end of file +Chapter 65. SP-GiST Indexes
    Chapter 65. SP-GiST Indexes
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    64.5. Examples Home 65.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-examples.html postgresql-13-13.12/doc/src/sgml/html/spi-examples.html --- postgresql-13-13.11/doc/src/sgml/html/spi-examples.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-examples.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -46.6. Examples
    46.6. Examples
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.6. Examples

    +46.6. Examples

    46.6. Examples
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.6. Examples

    This section contains a very simple example of SPI usage. The C function execq takes an SQL command as its first argument and a row count as its second, executes the command @@ -86,15 +86,16 @@ => INSERT INTO a VALUES (execq('INSERT INTO a VALUES (0)', 0)); INSERT 0 1 => SELECT execq('SELECT * FROM a', 0); -INFO: EXECQ: 0 -- inserted by execq -INFO: EXECQ: 1 -- returned by execq and inserted by upper INSERT +INFO: EXECQ: 0 -- inserted by execq +INFO: EXECQ: 1 -- returned by execq and inserted by upper INSERT execq ------- 2 (1 row) -=> SELECT execq('INSERT INTO a SELECT x + 2 FROM a', 1); +=> SELECT execq('INSERT INTO a SELECT x + 2 FROM a RETURNING *', 1); +INFO: EXECQ: 2 -- 0 + 2, then execution was stopped by count execq ------- 1 @@ -103,21 +104,38 @@ => SELECT execq('SELECT * FROM a', 10); INFO: EXECQ: 0 INFO: EXECQ: 1 -INFO: EXECQ: 2 -- 0 + 2, only one row inserted - as specified +INFO: EXECQ: 2 + + execq +------- + 3 -- 10 is the max value only, 3 is the real number of rows +(1 row) +=> SELECT execq('INSERT INTO a SELECT x + 10 FROM a', 1); execq ------- - 3 -- 10 is the max value only, 3 is the real number of rows + 3 -- all rows processed; count does not stop it, because nothing is returned (1 row) +=> SELECT * FROM a; + x +---- + 0 + 1 + 2 + 10 + 11 + 12 +(6 rows) + => DELETE FROM a; -DELETE 3 +DELETE 6 => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1); INSERT 0 1 => SELECT * FROM a; x --- - 1 -- no rows in a (0) + 1 + 1 -- 0 (no rows in a) + 1 (1 row) => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1); @@ -127,15 +145,16 @@ x --- 1 - 2 -- there was one row in a + 1 + 2 -- 1 (there was one row in a) + 1 (2 rows) --- This demonstrates the data changes visibility rule: +-- This demonstrates the data changes visibility rule. +-- execq is called twice and sees different numbers of rows each time: => INSERT INTO a SELECT execq('SELECT * FROM a', 0) * x FROM a; -INFO: EXECQ: 1 +INFO: EXECQ: 1 -- results from first execq INFO: EXECQ: 2 -INFO: EXECQ: 1 +INFO: EXECQ: 1 -- results from second execq INFO: EXECQ: 2 INFO: EXECQ: 2 INSERT 0 2 @@ -144,9 +163,8 @@ --- 1 2 - 2 -- 2 rows * 1 (x in first row) - 6 -- 3 rows (2 + 1 just inserted) * 2 (x in second row) -(4 rows) ^^^^^^ - rows visible to execq() in different invocations + 2 -- 2 rows * 1 (x in first row) + 6 -- 3 rows (2 + 1 just inserted) * 2 (x in second row) +(4 rows)

    -

    Prev Up Next
    46.5. Visibility of Data Changes Home Chapter 47. Background Worker Processes
    \ No newline at end of file +

    Prev Up Next
    46.5. Visibility of Data Changes Home Chapter 47. Background Worker Processes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-interface-support.html postgresql-13-13.12/doc/src/sgml/html/spi-interface-support.html --- postgresql-13-13.11/doc/src/sgml/html/spi-interface-support.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-interface-support.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,9 +1,9 @@ -46.2. Interface Support Functions
    46.2. Interface Support Functions
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.2. Interface Support Functions

    SPI_fname — determine the column name for the specified column number
    SPI_fnumber — determine the column number for the specified column name
    SPI_getvalue — return the string value of the specified column
    SPI_getbinval — return the binary value of the specified column
    SPI_gettype — return the data type name of the specified column
    SPI_gettypeid — return the data type OID of the specified column
    SPI_getrelname — return the name of the specified relation
    SPI_getnspname — return the namespace of the specified relation
    SPI_result_code_string — return error code as string

    +46.2. Interface Support Functions

    46.2. Interface Support Functions
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.2. Interface Support Functions

    SPI_fname — determine the column name for the specified column number
    SPI_fnumber — determine the column number for the specified column name
    SPI_getvalue — return the string value of the specified column
    SPI_getbinval — return the binary value of the specified column
    SPI_gettype — return the data type name of the specified column
    SPI_gettypeid — return the data type OID of the specified column
    SPI_getrelname — return the name of the specified relation
    SPI_getnspname — return the namespace of the specified relation
    SPI_result_code_string — return error code as string

    The functions described here provide an interface for extracting information from result sets returned by SPI_execute and other SPI functions.

    All functions described in this section can be used by both connected and unconnected C functions. -

    Prev Up Next
    SPI_register_trigger_data Home SPI_fname
    \ No newline at end of file +

    Prev Up Next
    SPI_register_trigger_data Home SPI_fname
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-interface.html postgresql-13-13.12/doc/src/sgml/html/spi-interface.html --- postgresql-13-13.11/doc/src/sgml/html/spi-interface.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-interface.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,6 +1,6 @@ -46.1. Interface Functions
    46.1. Interface Functions
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.1. Interface Functions

    SPI_connect — connect a C function to the SPI manager
    SPI_finish — disconnect a C function from the SPI manager
    SPI_execute — execute a command
    SPI_exec — execute a read/write command
    SPI_execute_with_args — execute a command with out-of-line parameters
    SPI_prepare — prepare a statement, without executing it yet
    SPI_prepare_cursor — prepare a statement, without executing it yet
    SPI_prepare_params — prepare a statement, without executing it yet
    SPI_getargcount — return the number of arguments needed by a statement +46.1. Interface Functions
    46.1. Interface Functions
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.1. Interface Functions

    SPI_connect — connect a C function to the SPI manager
    SPI_finish — disconnect a C function from the SPI manager
    SPI_execute — execute a command
    SPI_exec — execute a read/write command
    SPI_execute_with_args — execute a command with out-of-line parameters
    SPI_prepare — prepare a statement, without executing it yet
    SPI_prepare_cursor — prepare a statement, without executing it yet
    SPI_prepare_params — prepare a statement, without executing it yet
    SPI_getargcount — return the number of arguments needed by a statement prepared by SPI_prepare
    SPI_getargtypeid — return the data type OID for an argument of a statement prepared by SPI_prepare
    SPI_is_cursor_plan — return true if a statement prepared by SPI_prepare can be used with - SPI_cursor_open
    SPI_execute_plan — execute a statement prepared by SPI_prepare
    SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare
    SPI_execp — execute a statement in read/write mode
    SPI_cursor_open — set up a cursor using a statement created with SPI_prepare
    SPI_cursor_open_with_args — set up a cursor using a query and parameters
    SPI_cursor_open_with_paramlist — set up a cursor using parameters
    SPI_cursor_find — find an existing cursor by name
    SPI_cursor_fetch — fetch some rows from a cursor
    SPI_cursor_move — move a cursor
    SPI_scroll_cursor_fetch — fetch some rows from a cursor
    SPI_scroll_cursor_move — move a cursor
    SPI_cursor_close — close a cursor
    SPI_keepplan — save a prepared statement
    SPI_saveplan — save a prepared statement
    SPI_register_relation — make an ephemeral named relation available by name in SPI queries
    SPI_unregister_relation — remove an ephemeral named relation from the registry
    SPI_register_trigger_data — make ephemeral trigger data available in SPI queries
    Prev Up Next
    Chapter 46. Server Programming Interface Home SPI_connect
    \ No newline at end of file + SPI_cursor_open
    SPI_execute_plan — execute a statement prepared by SPI_prepare
    SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare
    SPI_execp — execute a statement in read/write mode
    SPI_cursor_open — set up a cursor using a statement created with SPI_prepare
    SPI_cursor_open_with_args — set up a cursor using a query and parameters
    SPI_cursor_open_with_paramlist — set up a cursor using parameters
    SPI_cursor_find — find an existing cursor by name
    SPI_cursor_fetch — fetch some rows from a cursor
    SPI_cursor_move — move a cursor
    SPI_scroll_cursor_fetch — fetch some rows from a cursor
    SPI_scroll_cursor_move — move a cursor
    SPI_cursor_close — close a cursor
    SPI_keepplan — save a prepared statement
    SPI_saveplan — save a prepared statement
    SPI_register_relation — make an ephemeral named relation available by name in SPI queries
    SPI_unregister_relation — remove an ephemeral named relation from the registry
    SPI_register_trigger_data — make ephemeral trigger data available in SPI queries
    Prev Up Next
    Chapter 46. Server Programming Interface Home SPI_connect
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-memory.html postgresql-13-13.12/doc/src/sgml/html/spi-memory.html --- postgresql-13-13.11/doc/src/sgml/html/spi-memory.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-memory.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -46.3. Memory Management
    46.3. Memory Management
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.3. Memory Management

    SPI_palloc — allocate memory in the upper executor context
    SPI_repalloc — reallocate memory in the upper executor context
    SPI_pfree — free memory in the upper executor context
    SPI_copytuple — make a copy of a row in the upper executor context
    SPI_returntuple — prepare to return a tuple as a Datum
    SPI_modifytuple — create a row by replacing selected fields of a given row
    SPI_freetuple — free a row allocated in the upper executor context
    SPI_freetuptable — free a row set created by SPI_execute or a similar +46.3. Memory Management
    46.3. Memory Management
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.3. Memory Management

    SPI_palloc — allocate memory in the upper executor context
    SPI_repalloc — reallocate memory in the upper executor context
    SPI_pfree — free memory in the upper executor context
    SPI_copytuple — make a copy of a row in the upper executor context
    SPI_returntuple — prepare to return a tuple as a Datum
    SPI_modifytuple — create a row by replacing selected fields of a given row
    SPI_freetuple — free a row allocated in the upper executor context
    SPI_freetuptable — free a row set created by SPI_execute or a similar function
    SPI_freeplan — free a previously saved prepared statement

    PostgreSQL allocates memory within @@ -43,4 +43,4 @@ SPI_finish) the current context is restored to the upper executor context, and all allocations made in the C function memory context are freed and cannot be used any more. -

    Prev Up Next
    SPI_result_code_string Home SPI_palloc
    \ No newline at end of file +

    Prev Up Next
    SPI_result_code_string Home SPI_palloc
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-realloc.html postgresql-13-13.12/doc/src/sgml/html/spi-realloc.html --- postgresql-13-13.11/doc/src/sgml/html/spi-realloc.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-realloc.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_repalloc
    SPI_repalloc
    Prev Up46.3. Memory ManagementHome Next

    SPI_repalloc

    SPI_repalloc — reallocate memory in the upper executor context

    Synopsis

    +SPI_repalloc
    SPI_repalloc
    Prev Up46.3. Memory ManagementHome Next
    SPI_repalloc
    SPI_repalloc — reallocate memory in the upper executor context
    Synopsis
     void * SPI_repalloc(void * pointer, Size size)
 
    Description
    
    SPI_repalloc changes the size of a memory
@@ -15,4 +15,4 @@
      
    Return Value
    
    pointer to new storage space of specified size with the contents
    copied from the existing area
-
    Prev Up Next
    SPI_palloc Home SPI_pfree
    \ No newline at end of file +

    Prev Up Next
    SPI_palloc Home SPI_pfree
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-commit.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-commit.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-commit.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-commit.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_commit
    SPI_commit
    Prev Up46.4. Transaction ManagementHome Next

    SPI_commit

    SPI_commit, SPI_commit_and_chain — commit the current transaction

    Synopsis

    +SPI_commit
    SPI_commit
    Prev Up46.4. Transaction ManagementHome Next
    SPI_commit
    SPI_commit, SPI_commit_and_chain — commit the current transaction
    Synopsis
     void SPI_commit(void)
 
     void SPI_commit_and_chain(void)
@@ -20,4 +20,4 @@
   
    
    These functions can only be executed if the SPI connection has been set as
    nonatomic in the call to SPI_connect_ext.
-  
    Prev Up Next
    46.4. Transaction Management Home SPI_rollback
    
\ No newline at end of file
+
    Prev Up Next
    46.4. Transaction Management Home SPI_rollback
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-connect.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-connect.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-connect.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-connect.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_connect
    SPI_connect
    Prev Up46.1. Interface FunctionsHome Next

    SPI_connect

    SPI_connect, SPI_connect_ext — connect a C function to the SPI manager

    Synopsis

    +SPI_connect
    SPI_connect
    Prev Up46.1. Interface FunctionsHome Next
    SPI_connect
    SPI_connect, SPI_connect_ext — connect a C function to the SPI manager
    Synopsis
     int SPI_connect(void)
 
     int SPI_connect_ext(int options)
@@ -25,4 +25,4 @@
       on success
      
    SPI_ERROR_CONNECT
    
       on error
-
    Prev Up Next
    46.1. Interface Functions Home SPI_finish
    \ No newline at end of file +

    Prev Up Next
    46.1. Interface Functions Home SPI_finish
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-copytuple.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-copytuple.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-copytuple.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-copytuple.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_copytuple
    SPI_copytuple
    Prev Up46.3. Memory ManagementHome Next

    SPI_copytuple

    SPI_copytuple — make a copy of a row in the upper executor context

    Synopsis

    +SPI_copytuple
    SPI_copytuple
    Prev Up46.3. Memory ManagementHome Next
    SPI_copytuple
    SPI_copytuple — make a copy of a row in the upper executor context
    Synopsis
     HeapTuple SPI_copytuple(HeapTuple row)
 
    Description
    
    SPI_copytuple makes a copy of a row in the
@@ -15,4 +15,4 @@
      
    Return Value
    
    the copied row, or NULL on error
    (see SPI_result for an error indication)
-
    Prev Up Next
    SPI_pfree Home SPI_returntuple
    \ No newline at end of file +

    Prev Up Next
    SPI_pfree Home SPI_returntuple
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-close.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-close.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-close.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-close.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_close
    SPI_cursor_close
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_close

    SPI_cursor_close — close a cursor

    Synopsis

    +SPI_cursor_close
    SPI_cursor_close
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_close
    SPI_cursor_close — close a cursor
    Synopsis
     void SPI_cursor_close(Portal portal)
 
    Description
    
    SPI_cursor_close closes a previously created
@@ -10,4 +10,4 @@
    invoked if it is desirable to release resources sooner.
   
    Arguments
    Portal portal
    
       portal containing the cursor
-     
    Prev Up Next
    SPI_scroll_cursor_move Home SPI_keepplan
    
\ No newline at end of file
+
    Prev Up Next
    SPI_scroll_cursor_move Home SPI_keepplan
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-fetch.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-fetch.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-fetch.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-fetch.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_fetch
    SPI_cursor_fetch
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_fetch

    SPI_cursor_fetch — fetch some rows from a cursor

    Synopsis

    +SPI_cursor_fetch
    SPI_cursor_fetch
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_fetch
    SPI_cursor_fetch — fetch some rows from a cursor
    Synopsis
     void SPI_cursor_fetch(Portal portal, bool forward, long count)
 
    Description
    
    SPI_cursor_fetch fetches some rows from a
@@ -19,4 +19,4 @@
   
    Notes
    
    Fetching backward may fail if the cursor's plan was not created
    with the CURSOR_OPT_SCROLL option.
-  
    Prev Up Next
    SPI_cursor_find Home SPI_cursor_move
    
\ No newline at end of file
+
    Prev Up Next
    SPI_cursor_find Home SPI_cursor_move
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-find.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-find.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-find.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-find.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_find
    SPI_cursor_find
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_find

    SPI_cursor_find — find an existing cursor by name

    Synopsis

    +SPI_cursor_find
    SPI_cursor_find
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_find
    SPI_cursor_find — find an existing cursor by name
    Synopsis
     Portal SPI_cursor_find(const char * name)
 
    Description
    
    SPI_cursor_find finds an existing portal by
@@ -10,4 +10,4 @@
      
    Return Value
    
    pointer to the portal with the specified name, or
    NULL if none was found
-
    Prev Up Next
    SPI_cursor_open_with_paramlist Home SPI_cursor_fetch
    \ No newline at end of file +

    Prev Up Next
    SPI_cursor_open_with_paramlist Home SPI_cursor_fetch
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-move.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-move.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-move.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-move.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_move
    SPI_cursor_move
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_move

    SPI_cursor_move — move a cursor

    Synopsis

    +SPI_cursor_move
    SPI_cursor_move
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_move
    SPI_cursor_move — move a cursor
    Synopsis
     void SPI_cursor_move(Portal portal, bool forward, long count)
 
    Description
    
    SPI_cursor_move skips over some number of rows
@@ -15,4 +15,4 @@
      
    Notes
    
    Moving backward may fail if the cursor's plan was not created
    with the CURSOR_OPT_SCROLL option.
-
    Prev Up Next
    SPI_cursor_fetch Home SPI_scroll_cursor_fetch
    \ No newline at end of file +

    Prev Up Next
    SPI_cursor_fetch Home SPI_scroll_cursor_fetch
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open-with-args.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open-with-args.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open-with-args.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open-with-args.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_open_with_args
    SPI_cursor_open_with_args
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_open_with_args

    SPI_cursor_open_with_args — set up a cursor using a query and parameters

    Synopsis

    +SPI_cursor_open_with_args
    SPI_cursor_open_with_args
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_open_with_args
    SPI_cursor_open_with_args — set up a cursor using a query and parameters
    Synopsis
     Portal SPI_cursor_open_with_args(const char *name,
                                  const char *command,
                                  int nargs, Oid *argtypes,
@@ -52,4 +52,4 @@
      
    Return Value
    
    Pointer to portal containing the cursor.  Note there is no error
    return convention; any error will be reported via elog.
-
    Prev Up Next
    SPI_cursor_open Home SPI_cursor_open_with_paramlist
    \ No newline at end of file +

    Prev Up Next
    SPI_cursor_open Home SPI_cursor_open_with_paramlist
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_open_with_paramlist
    SPI_cursor_open_with_paramlist
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_open_with_paramlist

    SPI_cursor_open_with_paramlist — set up a cursor using parameters

    Synopsis

    +SPI_cursor_open_with_paramlist
    SPI_cursor_open_with_paramlist
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_open_with_paramlist
    SPI_cursor_open_with_paramlist — set up a cursor using parameters
    Synopsis
     Portal SPI_cursor_open_with_paramlist(const char *name,
                                       SPIPlanPtr plan,
                                       ParamListInfo params,
@@ -27,4 +27,4 @@
      
    bool read_only
    true for read-only execution
    Return Value
    
    Pointer to portal containing the cursor.  Note there is no error
    return convention; any error will be reported via elog.
-
    Prev Up Next
    SPI_cursor_open_with_args Home SPI_cursor_find
    \ No newline at end of file +

    Prev Up Next
    SPI_cursor_open_with_args Home SPI_cursor_find
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-cursor-open.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-cursor-open.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_cursor_open
    SPI_cursor_open
    Prev Up46.1. Interface FunctionsHome Next

    SPI_cursor_open

    SPI_cursor_open — set up a cursor using a statement created with SPI_prepare

    Synopsis

    +SPI_cursor_open
    SPI_cursor_open
    Prev Up46.1. Interface FunctionsHome Next
    SPI_cursor_open
    SPI_cursor_open — set up a cursor using a statement created with SPI_prepare
    Synopsis
     Portal SPI_cursor_open(const char * name, SPIPlanPtr plan,
                        Datum * values, const char * nulls,
                        bool read_only)
@@ -44,4 +44,4 @@
      
    bool read_only
    true for read-only execution
    Return Value
    
    Pointer to portal containing the cursor.  Note there is no error
    return convention; any error will be reported via elog.
-
    Prev Up Next
    SPI_execp Home SPI_cursor_open_with_args
    \ No newline at end of file +

    Prev Up Next
    SPI_execp Home SPI_cursor_open_with_args
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-exec.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-exec.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-exec.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-exec.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_exec
    SPI_exec
    Prev Up46.1. Interface FunctionsHome Next

    SPI_exec

    SPI_exec — execute a read/write command

    Synopsis

    +SPI_exec
    SPI_exec
    Prev Up46.1. Interface FunctionsHome Next
    SPI_exec
    SPI_exec — execute a read/write command
    Synopsis
     int SPI_exec(const char * command, long count)
 
    Description
    
    SPI_exec is the same as
@@ -13,4 +13,4 @@
       or 0 for no limit
      
    Return Value
    
    See SPI_execute.
-
    Prev Up Next
    SPI_execute Home SPI_execute_with_args
    \ No newline at end of file +

    Prev Up Next
    SPI_execute Home SPI_execute_with_args
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-execp.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-execp.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-execp.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-execp.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_execp
    SPI_execp
    Prev Up46.1. Interface FunctionsHome Next

    SPI_execp

    SPI_execp — execute a statement in read/write mode

    Synopsis

    +SPI_execp
    SPI_execp
    Prev Up46.1. Interface FunctionsHome Next
    SPI_execp
    SPI_execp — execute a statement in read/write mode
    Synopsis
     int SPI_execp(SPIPlanPtr plan, Datum * values, const char * nulls, long count)
 
    Description
    
    SPI_execp is the same as
@@ -33,4 +33,4 @@
    SPI_processed and
    SPI_tuptable are set as in
    SPI_execute if successful.
-  
    Prev Up Next
    SPI_execute_plan_with_paramlist Home SPI_cursor_open
    
\ No newline at end of file
+
    Prev Up Next
    SPI_execute_plan_with_paramlist Home SPI_cursor_open
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_execute_plan_with_paramlist
    SPI_execute_plan_with_paramlist
    Prev Up46.1. Interface FunctionsHome Next

    SPI_execute_plan_with_paramlist

    SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare

    Synopsis

    +SPI_execute_plan_with_paramlist
    SPI_execute_plan_with_paramlist
    Prev Up46.1. Interface FunctionsHome Next
    SPI_execute_plan_with_paramlist
    SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare
    Synopsis
     int SPI_execute_plan_with_paramlist(SPIPlanPtr plan,
                                     ParamListInfo params,
                                     bool read_only,
@@ -26,4 +26,4 @@
    SPI_processed and
    SPI_tuptable are set as in
    SPI_execute_plan if successful.
-  
    Prev Up Next
    SPI_execute_plan Home SPI_execp
    
\ No newline at end of file
+
    Prev Up Next
    SPI_execute_plan Home SPI_execp
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-plan.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-plan.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-plan.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-plan.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_execute_plan
    SPI_execute_plan
    Prev Up46.1. Interface FunctionsHome Next

    SPI_execute_plan

    SPI_execute_plan — execute a statement prepared by SPI_prepare

    Synopsis

    +SPI_execute_plan
    SPI_execute_plan
    Prev Up46.1. Interface FunctionsHome Next
    SPI_execute_plan
    SPI_execute_plan — execute a statement prepared by SPI_prepare
    Synopsis
     int SPI_execute_plan(SPIPlanPtr plan, Datum * values, const char * nulls,
                      bool read_only, long count)
 
    Description
    
@@ -44,4 +44,4 @@
    SPI_processed and
    SPI_tuptable are set as in
    SPI_execute if successful.
-  
    Prev Up Next
    SPI_is_cursor_plan Home SPI_execute_plan_with_paramlist
    
\ No newline at end of file
+
    Prev Up Next
    SPI_is_cursor_plan Home SPI_execute_plan_with_paramlist
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-with-args.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-with-args.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute-with-args.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute-with-args.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_execute_with_args
    SPI_execute_with_args
    Prev Up46.1. Interface FunctionsHome Next

    SPI_execute_with_args

    SPI_execute_with_args — execute a command with out-of-line parameters

    Synopsis

    +SPI_execute_with_args
    SPI_execute_with_args
    Prev Up46.1. Interface FunctionsHome Next
    SPI_execute_with_args
    SPI_execute_with_args — execute a command with out-of-line parameters
    Synopsis
     int SPI_execute_with_args(const char *command,
                           int nargs, Oid *argtypes,
                           Datum *values, const char *nulls,
@@ -57,4 +57,4 @@
    SPI_processed and
    SPI_tuptable are set as in
    SPI_execute if successful.
-  
    Prev Up Next
    SPI_exec Home SPI_prepare
    
\ No newline at end of file
+
    Prev Up Next
    SPI_exec Home SPI_prepare
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-execute.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-execute.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_execute
    SPI_execute
    Prev Up46.1. Interface FunctionsHome Next

    SPI_execute

    SPI_execute — execute a command

    Synopsis

    +SPI_execute
    SPI_execute
    Prev Up46.1. Interface FunctionsHome Next
    SPI_execute
    SPI_execute — execute a command
    Synopsis
     int SPI_execute(const char * command, bool read_only, long count)
 
    Description
    
    SPI_execute executes the specified SQL command
@@ -174,4 +174,4 @@
    C function variables if you need to access the result table of
    SPI_execute or another query-execution function
    across later calls.
-  
    Prev Up Next
    SPI_finish Home SPI_exec
    
\ No newline at end of file
+
    Prev Up Next
    SPI_finish Home SPI_exec
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-finish.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-finish.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-finish.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-finish.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_finish
    SPI_finish
    Prev Up46.1. Interface FunctionsHome Next

    SPI_finish

    SPI_finish — disconnect a C function from the SPI manager

    Synopsis

    +SPI_finish
    SPI_finish
    Prev Up46.1. Interface FunctionsHome Next
    SPI_finish
    SPI_finish — disconnect a C function from the SPI manager
    Synopsis
     int SPI_finish(void)
 
    Description
    
    SPI_finish closes an existing connection to
@@ -12,4 +12,4 @@
       if properly disconnected
      
    SPI_ERROR_UNCONNECTED
    
       if called from an unconnected C function
-
    Prev Up Next
    SPI_connect Home SPI_execute
    \ No newline at end of file +

    Prev Up Next
    SPI_connect Home SPI_execute
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-fname.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-fname.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-fname.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-fname.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_fname
    SPI_fname
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_fname

    SPI_fname — determine the column name for the specified column number

    Synopsis

    +SPI_fname
    SPI_fname
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_fname
    SPI_fname — determine the column name for the specified column number
    Synopsis
     char * SPI_fname(TupleDesc rowdesc, int colnumber)
 
    Description
    
    SPI_fname returns a copy of the column name of the
@@ -14,4 +14,4 @@
    colnumber is out of range.
    SPI_result set to
    SPI_ERROR_NOATTRIBUTE on error.
-  
    Prev Up Next
    46.2. Interface Support Functions Home SPI_fnumber
    
\ No newline at end of file
+
    Prev Up Next
    46.2. Interface Support Functions Home SPI_fnumber
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-fnumber.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-fnumber.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-fnumber.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-fnumber.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_fnumber
    SPI_fnumber
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_fnumber

    SPI_fnumber — determine the column number for the specified column name

    Synopsis

    +SPI_fnumber
    SPI_fnumber
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_fnumber
    SPI_fnumber — determine the column number for the specified column name
    Synopsis
     int SPI_fnumber(TupleDesc rowdesc, const char * colname)
 
    Description
    
    SPI_fnumber returns the column number for the
@@ -19,4 +19,4 @@
    Column number (count starts at 1 for user-defined columns), or
    SPI_ERROR_NOATTRIBUTE if the named column was not
    found.
-  
    Prev Up Next
    SPI_fname Home SPI_getvalue
    
\ No newline at end of file
+
    Prev Up Next
    SPI_fname Home SPI_getvalue
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-freeplan.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-freeplan.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-freeplan.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-freeplan.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_freeplan
    SPI_freeplan
    Prev Up46.3. Memory ManagementHome Next

    SPI_freeplan

    SPI_freeplan — free a previously saved prepared statement

    Synopsis

    +SPI_freeplan
    SPI_freeplan
    Prev Up46.3. Memory ManagementHome Next
    SPI_freeplan
    SPI_freeplan — free a previously saved prepared statement
    Synopsis
     int SPI_freeplan(SPIPlanPtr plan)
 
    Description
    
    SPI_freeplan releases a prepared statement
@@ -11,4 +11,4 @@
    0 on success;
    SPI_ERROR_ARGUMENT if plan
    is NULL or invalid
-  
    Prev Up Next
    SPI_freetuptable Home 46.4. Transaction Management
    
\ No newline at end of file
+
    Prev Up Next
    SPI_freetuptable Home 46.4. Transaction Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-freetuple.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-freetuple.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-freetuple.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-freetuple.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_freetuple
    SPI_freetuple
    Prev Up46.3. Memory ManagementHome Next

    SPI_freetuple

    SPI_freetuple — free a row allocated in the upper executor context

    Synopsis

    +SPI_freetuple
    SPI_freetuple
    Prev Up46.3. Memory ManagementHome Next
    SPI_freetuple
    SPI_freetuple — free a row allocated in the upper executor context
    Synopsis
     void SPI_freetuple(HeapTuple row)
 
    Description
    
    SPI_freetuple frees a row previously allocated
@@ -10,4 +10,4 @@
    compatibility of existing code.
   
    Arguments
    HeapTuple row
    
       row to free
-     
    Prev Up Next
    SPI_modifytuple Home SPI_freetuptable
    
\ No newline at end of file
+
    Prev Up Next
    SPI_modifytuple Home SPI_freetuptable
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-freetupletable.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-freetupletable.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-freetupletable.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-freetupletable.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_freetuptable
    SPI_freetuptable
    Prev Up46.3. Memory ManagementHome Next

    SPI_freetuptable

    SPI_freetuptable — free a row set created by SPI_execute or a similar +SPI_freetuptable

    SPI_freetuptable
    Prev Up46.3. Memory ManagementHome Next

    SPI_freetuptable

    SPI_freetuptable — free a row set created by SPI_execute or a similar function

    Synopsis

     void SPI_freetuptable(SPITupleTable * tuptable)

    Description

    @@ -23,4 +23,4 @@ releases, duplicate deletions would lead to crashes.

    Arguments

    SPITupleTable * tuptable

    pointer to row set to free, or NULL to do nothing -

    Prev Up Next
    SPI_freetuple Home SPI_freeplan
    \ No newline at end of file +

    Prev Up Next
    SPI_freetuple Home SPI_freeplan
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getargcount.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getargcount.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getargcount.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getargcount.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getargcount
    SPI_getargcount
    Prev Up46.1. Interface FunctionsHome Next

    SPI_getargcount

    SPI_getargcount — return the number of arguments needed by a statement +SPI_getargcount

    SPI_getargcount
    Prev Up46.1. Interface FunctionsHome Next

    SPI_getargcount

    SPI_getargcount — return the number of arguments needed by a statement prepared by SPI_prepare

    Synopsis

     int SPI_getargcount(SPIPlanPtr plan)

    Description

    @@ -12,4 +12,4 @@ If the plan is NULL or invalid, SPI_result is set to SPI_ERROR_ARGUMENT and -1 is returned. -

    Prev Up Next
    SPI_prepare_params Home SPI_getargtypeid
    \ No newline at end of file +

    Prev Up Next
    SPI_prepare_params Home SPI_getargtypeid
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getargtypeid.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getargtypeid.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getargtypeid.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getargtypeid.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getargtypeid
    SPI_getargtypeid
    Prev Up46.1. Interface FunctionsHome Next

    SPI_getargtypeid

    SPI_getargtypeid — return the data type OID for an argument of +SPI_getargtypeid

    SPI_getargtypeid
    Prev Up46.1. Interface FunctionsHome Next

    SPI_getargtypeid

    SPI_getargtypeid — return the data type OID for an argument of a statement prepared by SPI_prepare

    Synopsis

     Oid SPI_getargtypeid(SPIPlanPtr plan, int argIndex)

    Description

    @@ -18,4 +18,4 @@ plan, SPI_result is set to SPI_ERROR_ARGUMENT and InvalidOid is returned. -

    Prev Up Next
    SPI_getargcount Home SPI_is_cursor_plan
    \ No newline at end of file +

    Prev Up Next
    SPI_getargcount Home SPI_is_cursor_plan
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getbinval.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getbinval.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getbinval.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getbinval.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getbinval
    SPI_getbinval
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_getbinval

    SPI_getbinval — return the binary value of the specified column

    Synopsis

    +SPI_getbinval
    SPI_getbinval
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_getbinval
    SPI_getbinval — return the binary value of the specified column
    Synopsis
     Datum SPI_getbinval(HeapTuple row, TupleDesc rowdesc, int colnumber,
                     bool * isnull)
 
    Description
    
@@ -24,4 +24,4 @@
   
    
    SPI_result is set to
    SPI_ERROR_NOATTRIBUTE on error.
-  
    Prev Up Next
    SPI_getvalue Home SPI_gettype
    
\ No newline at end of file
+
    Prev Up Next
    SPI_getvalue Home SPI_gettype
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getnspname.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getnspname.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getnspname.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getnspname.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getnspname
    SPI_getnspname
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_getnspname

    SPI_getnspname — return the namespace of the specified relation

    Synopsis

    +SPI_getnspname
    SPI_getnspname
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_getnspname
    SPI_getnspname — return the namespace of the specified relation
    Synopsis
     char * SPI_getnspname(Relation rel)
 
    Description
    
    SPI_getnspname returns a copy of the name of
@@ -11,4 +11,4 @@
       input relation
      
    Return Value
    
    The name of the specified relation's namespace.
-
    Prev Up Next
    SPI_getrelname Home SPI_result_code_string
    \ No newline at end of file +

    Prev Up Next
    SPI_getrelname Home SPI_result_code_string
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getrelname.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getrelname.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getrelname.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getrelname.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getrelname
    SPI_getrelname
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_getrelname

    SPI_getrelname — return the name of the specified relation

    Synopsis

    +SPI_getrelname
    SPI_getrelname
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_getrelname
    SPI_getrelname — return the name of the specified relation
    Synopsis
     char * SPI_getrelname(Relation rel)
 
    Description
    
    SPI_getrelname returns a copy of the name of the
@@ -9,4 +9,4 @@
       input relation
      
    Return Value
    
    The name of the specified relation.
-
    Prev Up Next
    SPI_gettypeid Home SPI_getnspname
    \ No newline at end of file +

    Prev Up Next
    SPI_gettypeid Home SPI_getnspname
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-gettype.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-gettype.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-gettype.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-gettype.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_gettype
    SPI_gettype
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_gettype

    SPI_gettype — return the data type name of the specified column

    Synopsis

    +SPI_gettype
    SPI_gettype
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_gettype
    SPI_gettype — return the data type name of the specified column
    Synopsis
     char * SPI_gettype(TupleDesc rowdesc, int colnumber)
 
    Description
    
    SPI_gettype returns a copy of the data type name of the
@@ -13,4 +13,4 @@
    The data type name of the specified column, or
    NULL on error.  SPI_result is
    set to SPI_ERROR_NOATTRIBUTE on error.
-  
    Prev Up Next
    SPI_getbinval Home SPI_gettypeid
    
\ No newline at end of file
+
    Prev Up Next
    SPI_getbinval Home SPI_gettypeid
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-gettypeid.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-gettypeid.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-gettypeid.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-gettypeid.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_gettypeid
    SPI_gettypeid
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_gettypeid

    SPI_gettypeid — return the data type OID of the specified column

    Synopsis

    +SPI_gettypeid
    SPI_gettypeid
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_gettypeid
    SPI_gettypeid — return the data type OID of the specified column
    Synopsis
     Oid SPI_gettypeid(TupleDesc rowdesc, int colnumber)
 
    Description
    
    SPI_gettypeid returns the
@@ -13,4 +13,4 @@
    or InvalidOid on error.  On error,
    SPI_result is set to
    SPI_ERROR_NOATTRIBUTE.
-  
    Prev Up Next
    SPI_gettype Home SPI_getrelname
    
\ No newline at end of file
+
    Prev Up Next
    SPI_gettype Home SPI_getrelname
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-getvalue.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-getvalue.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-getvalue.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-getvalue.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_getvalue
    SPI_getvalue
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_getvalue

    SPI_getvalue — return the string value of the specified column

    Synopsis

    +SPI_getvalue
    SPI_getvalue
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_getvalue
    SPI_getvalue — return the string value of the specified column
    Synopsis
     char * SPI_getvalue(HeapTuple row, TupleDesc rowdesc, int colnumber)
 
    Description
    
    SPI_getvalue returns the string representation
@@ -22,4 +22,4 @@
    SPI_ERROR_NOATTRIBUTE), or no output function is
    available (SPI_result is set to
    SPI_ERROR_NOOUTFUNC).
-  
    Prev Up Next
    SPI_fnumber Home SPI_getbinval
    
\ No newline at end of file
+
    Prev Up Next
    SPI_fnumber Home SPI_getbinval
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-is-cursor-plan.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-is-cursor-plan.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-is-cursor-plan.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-is-cursor-plan.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_is_cursor_plan
    SPI_is_cursor_plan
    Prev Up46.1. Interface FunctionsHome Next

    SPI_is_cursor_plan

    SPI_is_cursor_plan — return true if a statement +SPI_is_cursor_plan

    SPI_is_cursor_plan
    Prev Up46.1. Interface FunctionsHome Next

    SPI_is_cursor_plan

    SPI_is_cursor_plan — return true if a statement prepared by SPI_prepare can be used with SPI_cursor_open

    Synopsis

     bool SPI_is_cursor_plan(SPIPlanPtr plan)
@@ -24,4 +24,4 @@
     or if called when not connected to SPI), then
     SPI_result is set to a suitable error code
     and false is returned.
-
    Prev Up Next
    SPI_getargtypeid Home SPI_execute_plan
    \ No newline at end of file +

    Prev Up Next
    SPI_getargtypeid Home SPI_execute_plan
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-keepplan.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-keepplan.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-keepplan.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-keepplan.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_keepplan
    SPI_keepplan
    Prev Up46.1. Interface FunctionsHome Next

    SPI_keepplan

    SPI_keepplan — save a prepared statement

    Synopsis

    +SPI_keepplan
    SPI_keepplan
    Prev Up46.1. Interface FunctionsHome Next
    SPI_keepplan
    SPI_keepplan — save a prepared statement
    Synopsis
     int SPI_keepplan(SPIPlanPtr plan)
 
    Description
    
    SPI_keepplan saves a passed statement (prepared by
@@ -17,4 +17,4 @@
    The passed-in statement is relocated to permanent storage by means
    of pointer adjustment (no data copying is required).  If you later
    wish to delete it, use SPI_freeplan on it.
-  
    Prev Up Next
    SPI_cursor_close Home SPI_saveplan
    
\ No newline at end of file
+
    Prev Up Next
    SPI_cursor_close Home SPI_saveplan
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-modifytuple.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-modifytuple.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-modifytuple.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-modifytuple.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_modifytuple
    SPI_modifytuple
    Prev Up46.3. Memory ManagementHome Next

    SPI_modifytuple

    SPI_modifytuple — create a row by replacing selected fields of a given row

    Synopsis

    +SPI_modifytuple
    SPI_modifytuple
    Prev Up46.3. Memory ManagementHome Next
    SPI_modifytuple
    SPI_modifytuple — create a row by replacing selected fields of a given row
    Synopsis
     HeapTuple SPI_modifytuple(Relation rel, HeapTuple row, int ncols,
                           int * colnum, Datum * values, const char * nulls)
 
    Description
    
@@ -56,4 +56,4 @@
       
    SPI_ERROR_UNCONNECTED
    
        if SPI is not active
       
    
-
    Prev Up Next
    SPI_returntuple Home SPI_freetuple
    \ No newline at end of file +

    Prev Up Next
    SPI_returntuple Home SPI_freetuple
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-palloc.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-palloc.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-palloc.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-palloc.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_palloc
    SPI_palloc
    Prev Up46.3. Memory ManagementHome Next

    SPI_palloc

    SPI_palloc — allocate memory in the upper executor context

    Synopsis

    +SPI_palloc
    SPI_palloc
    Prev Up46.3. Memory ManagementHome Next
    SPI_palloc
    SPI_palloc — allocate memory in the upper executor context
    Synopsis
     void * SPI_palloc(Size size)
 
    Description
    
    SPI_palloc allocates memory in the upper
@@ -11,4 +11,4 @@
       size in bytes of storage to allocate
      
    Return Value
    
    pointer to new storage space of the specified size
-
    Prev Up Next
    46.3. Memory Management Home SPI_repalloc
    \ No newline at end of file +

    Prev Up Next
    46.3. Memory Management Home SPI_repalloc
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-pfree.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-pfree.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-pfree.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-pfree.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_pfree
    SPI_pfree
    Prev Up46.3. Memory ManagementHome Next

    SPI_pfree

    SPI_pfree — free memory in the upper executor context

    Synopsis

    +SPI_pfree
    SPI_pfree
    Prev Up46.3. Memory ManagementHome Next
    SPI_pfree
    SPI_pfree — free memory in the upper executor context
    Synopsis
     void SPI_pfree(void * pointer)
 
    Description
    
    SPI_pfree frees memory previously allocated
@@ -11,4 +11,4 @@
    compatibility of existing code.
   
    Arguments
    void * pointer
    
       pointer to existing storage to free
-     
    Prev Up Next
    SPI_repalloc Home SPI_copytuple
    
\ No newline at end of file
+
    Prev Up Next
    SPI_repalloc Home SPI_copytuple
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare-cursor.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare-cursor.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare-cursor.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare-cursor.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_prepare_cursor
    SPI_prepare_cursor
    Prev Up46.1. Interface FunctionsHome Next

    SPI_prepare_cursor

    SPI_prepare_cursor — prepare a statement, without executing it yet

    Synopsis

    +SPI_prepare_cursor
    SPI_prepare_cursor
    Prev Up46.1. Interface FunctionsHome Next
    SPI_prepare_cursor
    SPI_prepare_cursor — prepare a statement, without executing it yet
    Synopsis
     SPIPlanPtr SPI_prepare_cursor(const char * command, int nargs,
                               Oid * argtypes, int cursorOptions)
 
    Description
    
@@ -29,4 +29,4 @@
    CURSOR_OPT_GENERIC_PLAN, and
    CURSOR_OPT_CUSTOM_PLAN.  Note in particular that
    CURSOR_OPT_HOLD is ignored.
-  
    Prev Up Next
    SPI_prepare Home SPI_prepare_params
    
\ No newline at end of file
+
    Prev Up Next
    SPI_prepare Home SPI_prepare_params
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare-params.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare-params.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare-params.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare-params.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_prepare_params
    SPI_prepare_params
    Prev Up46.1. Interface FunctionsHome Next

    SPI_prepare_params

    SPI_prepare_params — prepare a statement, without executing it yet

    Synopsis

    +SPI_prepare_params
    SPI_prepare_params
    Prev Up46.1. Interface FunctionsHome Next
    SPI_prepare_params
    SPI_prepare_params — prepare a statement, without executing it yet
    Synopsis
     SPIPlanPtr SPI_prepare_params(const char * command,
                               ParserSetupHook parserSetup,
                               void * parserSetupArg,
@@ -21,4 +21,4 @@
      
    Return Value
    
    SPI_prepare_params has the same return conventions as
    SPI_prepare.
-
    Prev Up Next
    SPI_prepare_cursor Home SPI_getargcount
    \ No newline at end of file +

    Prev Up Next
    SPI_prepare_cursor Home SPI_getargcount
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-prepare.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-prepare.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_prepare
    SPI_prepare
    Prev Up46.1. Interface FunctionsHome Next

    SPI_prepare

    SPI_prepare — prepare a statement, without executing it yet

    Synopsis

    +SPI_prepare
    SPI_prepare
    Prev Up46.1. Interface FunctionsHome Next
    SPI_prepare
    SPI_prepare — prepare a statement, without executing it yet
    Synopsis
     SPIPlanPtr SPI_prepare(const char * command, int nargs, Oid * argtypes)
 
    Description
    
    SPI_prepare creates and returns a prepared
@@ -81,4 +81,4 @@
   
    
    The name SPIPlanPtr is somewhat historical, since the data
    structure no longer necessarily contains an execution plan.
-  
    Prev Up Next
    SPI_execute_with_args Home SPI_prepare_cursor
    
\ No newline at end of file
+
    Prev Up Next
    SPI_execute_with_args Home SPI_prepare_cursor
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-register-relation.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-register-relation.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-register-relation.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-register-relation.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_register_relation
    SPI_register_relation
    Prev Up46.1. Interface FunctionsHome Next

    SPI_register_relation

    SPI_register_relation — make an ephemeral named relation available by name in SPI queries

    Synopsis

    +SPI_register_relation
    SPI_register_relation
    Prev Up46.1. Interface FunctionsHome Next
    SPI_register_relation
    SPI_register_relation — make an ephemeral named relation available by name in SPI queries
    Synopsis
     int SPI_register_relation(EphemeralNamedRelation enr)
 
    Description
    
    SPI_register_relation makes an ephemeral named
@@ -26,4 +26,4 @@
        if the name specified in the name field of
        enr is already registered for this connection
       
    
-
    Prev Up Next
    SPI_saveplan Home SPI_unregister_relation
    \ No newline at end of file +

    Prev Up Next
    SPI_saveplan Home SPI_unregister_relation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-register-trigger-data.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-register-trigger-data.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-register-trigger-data.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-register-trigger-data.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_register_trigger_data
    SPI_register_trigger_data
    Prev Up46.1. Interface FunctionsHome Next

    SPI_register_trigger_data

    SPI_register_trigger_data — make ephemeral trigger data available in SPI queries

    Synopsis

    +SPI_register_trigger_data
    SPI_register_trigger_data
    Prev Up46.1. Interface FunctionsHome Next
    SPI_register_trigger_data
    SPI_register_trigger_data — make ephemeral trigger data available in SPI queries
    Synopsis
     int SPI_register_trigger_data(TriggerData *tdata)
 
    Description
    
    SPI_register_trigger_data makes any ephemeral
@@ -29,4 +29,4 @@
        if the name of any trigger data transient relation is already
        registered for this connection
       
    
-
    Prev Up Next
    SPI_unregister_relation Home 46.2. Interface Support Functions
    \ No newline at end of file +

    Prev Up Next
    SPI_unregister_relation Home 46.2. Interface Support Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-result-code-string.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-result-code-string.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-result-code-string.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-result-code-string.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_result_code_string
    SPI_result_code_string
    Prev Up46.2. Interface Support FunctionsHome Next

    SPI_result_code_string

    SPI_result_code_string — return error code as string

    Synopsis

    +SPI_result_code_string
    SPI_result_code_string
    Prev Up46.2. Interface Support FunctionsHome Next
    SPI_result_code_string
    SPI_result_code_string — return error code as string
    Synopsis
     const char * SPI_result_code_string(int code);
 
    Description
    
    SPI_result_code_string returns a string representation
@@ -9,4 +9,4 @@
       result code
      
    Return Value
    
    A string representation of the result code.
-
    Prev Up Next
    SPI_getnspname Home 46.3. Memory Management
    \ No newline at end of file +

    Prev Up Next
    SPI_getnspname Home 46.3. Memory Management
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-returntuple.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-returntuple.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-returntuple.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-returntuple.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_returntuple
    SPI_returntuple
    Prev Up46.3. Memory ManagementHome Next

    SPI_returntuple

    SPI_returntuple — prepare to return a tuple as a Datum

    Synopsis

    +SPI_returntuple
    SPI_returntuple
    Prev Up46.3. Memory ManagementHome Next
    SPI_returntuple
    SPI_returntuple — prepare to return a tuple as a Datum
    Synopsis
     HeapTupleHeader SPI_returntuple(HeapTuple row, TupleDesc rowdesc)
 
    Description
    
    SPI_returntuple makes a copy of a row in
@@ -23,4 +23,4 @@
    HeapTupleHeader pointing to copied row,
    or NULL on error
    (see SPI_result for an error indication)
-  
    Prev Up Next
    SPI_copytuple Home SPI_modifytuple
    
\ No newline at end of file
+
    Prev Up Next
    SPI_copytuple Home SPI_modifytuple
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-rollback.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-rollback.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-rollback.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-rollback.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_rollback
    SPI_rollback
    Prev Up46.4. Transaction ManagementHome Next

    SPI_rollback

    SPI_rollback, SPI_rollback_and_chain — abort the current transaction

    Synopsis

    +SPI_rollback
    SPI_rollback
    Prev Up46.4. Transaction ManagementHome Next
    SPI_rollback
    SPI_rollback, SPI_rollback_and_chain — abort the current transaction
    Synopsis
     void SPI_rollback(void)
 
     void SPI_rollback_and_chain(void)
@@ -17,4 +17,4 @@
   
    
    These functions can only be executed if the SPI connection has been set as
    nonatomic in the call to SPI_connect_ext.
-  
    Prev Up Next
    SPI_commit Home SPI_start_transaction
    
\ No newline at end of file
+
    Prev Up Next
    SPI_commit Home SPI_start_transaction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-saveplan.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-saveplan.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-saveplan.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-saveplan.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_saveplan
    SPI_saveplan
    Prev Up46.1. Interface FunctionsHome Next

    SPI_saveplan

    SPI_saveplan — save a prepared statement

    Synopsis

    +SPI_saveplan
    SPI_saveplan
    Prev Up46.1. Interface FunctionsHome Next
    SPI_saveplan
    SPI_saveplan — save a prepared statement
    Synopsis
     SPIPlanPtr SPI_saveplan(SPIPlanPtr plan)
 
    Description
    
    SPI_saveplan copies a passed statement (prepared by
@@ -27,4 +27,4 @@
    In most cases, SPI_keepplan is preferred to this
    function, since it accomplishes largely the same result without needing
    to physically copy the prepared statement's data structures.
-  
    Prev Up Next
    SPI_keepplan Home SPI_register_relation
    
\ No newline at end of file
+
    Prev Up Next
    SPI_keepplan Home SPI_register_relation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_scroll_cursor_fetch
    SPI_scroll_cursor_fetch
    Prev Up46.1. Interface FunctionsHome Next

    SPI_scroll_cursor_fetch

    SPI_scroll_cursor_fetch — fetch some rows from a cursor

    Synopsis

    +SPI_scroll_cursor_fetch
    SPI_scroll_cursor_fetch
    Prev Up46.1. Interface FunctionsHome Next
    SPI_scroll_cursor_fetch
    SPI_scroll_cursor_fetch — fetch some rows from a cursor
    Synopsis
     void SPI_scroll_cursor_fetch(Portal portal, FetchDirection direction,
                              long count)
 
    Description
    
@@ -31,4 +31,4 @@
    Direction values other than FETCH_FORWARD
    may fail if the cursor's plan was not created
    with the CURSOR_OPT_SCROLL option.
-  
    Prev Up Next
    SPI_cursor_move Home SPI_scroll_cursor_move
    
\ No newline at end of file
+
    Prev Up Next
    SPI_cursor_move Home SPI_scroll_cursor_move
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-scroll-cursor-move.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-scroll-cursor-move.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-scroll-cursor-move.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-scroll-cursor-move.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_scroll_cursor_move
    SPI_scroll_cursor_move
    Prev Up46.1. Interface FunctionsHome Next

    SPI_scroll_cursor_move

    SPI_scroll_cursor_move — move a cursor

    Synopsis

    +SPI_scroll_cursor_move
    SPI_scroll_cursor_move
    Prev Up46.1. Interface FunctionsHome Next
    SPI_scroll_cursor_move
    SPI_scroll_cursor_move — move a cursor
    Synopsis
     void SPI_scroll_cursor_move(Portal portal, FetchDirection direction,
                             long count)
 
    Description
    
@@ -33,4 +33,4 @@
    Direction values other than FETCH_FORWARD
    may fail if the cursor's plan was not created
    with the CURSOR_OPT_SCROLL option.
-  
    Prev Up Next
    SPI_scroll_cursor_fetch Home SPI_cursor_close
    
\ No newline at end of file
+
    Prev Up Next
    SPI_scroll_cursor_fetch Home SPI_cursor_close
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-start-transaction.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-start-transaction.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-start-transaction.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-start-transaction.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_start_transaction
    SPI_start_transaction
    Prev Up46.4. Transaction ManagementHome Next

    SPI_start_transaction

    SPI_start_transaction — obsolete function

    Synopsis

    +SPI_start_transaction
    SPI_start_transaction
    Prev Up46.4. Transaction ManagementHome Next
    SPI_start_transaction
    SPI_start_transaction — obsolete function
    Synopsis
     void SPI_start_transaction(void)
 
    Description
    
    SPI_start_transaction does nothing, and exists
@@ -8,4 +8,4 @@
    be required after calling SPI_commit
    or SPI_rollback, but now those functions start
    a new transaction automatically.
-  
    Prev Up Next
    SPI_rollback Home 46.5. Visibility of Data Changes
    
\ No newline at end of file
+
    Prev Up Next
    SPI_rollback Home 46.5. Visibility of Data Changes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-spi-unregister-relation.html postgresql-13-13.12/doc/src/sgml/html/spi-spi-unregister-relation.html --- postgresql-13-13.11/doc/src/sgml/html/spi-spi-unregister-relation.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-spi-unregister-relation.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -SPI_unregister_relation
    SPI_unregister_relation
    Prev Up46.1. Interface FunctionsHome Next

    SPI_unregister_relation

    SPI_unregister_relation — remove an ephemeral named relation from the registry

    Synopsis

    +SPI_unregister_relation
    SPI_unregister_relation
    Prev Up46.1. Interface FunctionsHome Next
    SPI_unregister_relation
    SPI_unregister_relation — remove an ephemeral named relation from the registry
    Synopsis
     int SPI_unregister_relation(const char * name)
 
    Description
    
    SPI_unregister_relation removes an ephemeral named
@@ -24,4 +24,4 @@
        if name is not found in the registry for the
        current connection
       
    
-
    Prev Up Next
    SPI_register_relation Home SPI_register_trigger_data
    \ No newline at end of file +

    Prev Up Next
    SPI_register_relation Home SPI_register_trigger_data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-transaction.html postgresql-13-13.12/doc/src/sgml/html/spi-transaction.html --- postgresql-13-13.11/doc/src/sgml/html/spi-transaction.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-transaction.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -46.4. Transaction Management
    46.4. Transaction Management
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.4. Transaction Management

    SPI_commit — commit the current transaction
    SPI_rollback — abort the current transaction
    SPI_start_transaction — obsolete function

    +46.4. Transaction Management

    46.4. Transaction Management
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.4. Transaction Management

    SPI_commit — commit the current transaction
    SPI_rollback — abort the current transaction
    SPI_start_transaction — obsolete function

    It is not possible to run transaction control commands such as COMMIT and ROLLBACK through SPI functions such as SPI_execute. There are, however, @@ -16,4 +16,4 @@ command, taking the context of the CALL invocation into account. SPI-using procedures implemented in C can implement the same logic, but the details of that are beyond the scope of this documentation. -

    Prev Up Next
    SPI_freeplan Home SPI_commit
    \ No newline at end of file +

    Prev Up Next
    SPI_freeplan Home SPI_commit
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi-visibility.html postgresql-13-13.12/doc/src/sgml/html/spi-visibility.html --- postgresql-13-13.11/doc/src/sgml/html/spi-visibility.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi-visibility.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -46.5. Visibility of Data Changes
    46.5. Visibility of Data Changes
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.5. Visibility of Data Changes

    +46.5. Visibility of Data Changes

    46.5. Visibility of Data Changes
    Prev UpChapter 46. Server Programming InterfaceHome Next

    46.5. Visibility of Data Changes

    The following rules govern the visibility of data changes in functions that use SPI (or any other C function): @@ -35,4 +35,4 @@

    The next section contains an example that illustrates the application of these rules. -

    Prev Up Next
    SPI_start_transaction Home 46.6. Examples
    \ No newline at end of file +

    Prev Up Next
    SPI_start_transaction Home 46.6. Examples
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/spi.html postgresql-13-13.12/doc/src/sgml/html/spi.html --- postgresql-13-13.11/doc/src/sgml/html/spi.html 2023-05-08 21:34:00.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/spi.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 46. Server Programming Interface
    Chapter 46. Server Programming Interface
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 46. Server Programming Interface

    Table of Contents

    46.1. Interface Functions
    SPI_connect — connect a C function to the SPI manager
    SPI_finish — disconnect a C function from the SPI manager
    SPI_execute — execute a command
    SPI_exec — execute a read/write command
    SPI_execute_with_args — execute a command with out-of-line parameters
    SPI_prepare — prepare a statement, without executing it yet
    SPI_prepare_cursor — prepare a statement, without executing it yet
    SPI_prepare_params — prepare a statement, without executing it yet
    SPI_getargcount — return the number of arguments needed by a statement +Chapter 46. Server Programming Interface
    Chapter 46. Server Programming Interface
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 46. Server Programming Interface

    Table of Contents

    46.1. Interface Functions
    SPI_connect — connect a C function to the SPI manager
    SPI_finish — disconnect a C function from the SPI manager
    SPI_execute — execute a command
    SPI_exec — execute a read/write command
    SPI_execute_with_args — execute a command with out-of-line parameters
    SPI_prepare — prepare a statement, without executing it yet
    SPI_prepare_cursor — prepare a statement, without executing it yet
    SPI_prepare_params — prepare a statement, without executing it yet
    SPI_getargcount — return the number of arguments needed by a statement prepared by SPI_prepare
    SPI_getargtypeid — return the data type OID for an argument of a statement prepared by SPI_prepare
    SPI_is_cursor_plan — return true if a statement prepared by SPI_prepare can be used with @@ -35,4 +35,4 @@

    Source code files that use SPI must include the header file executor/spi.h. -

    Prev Up Next
    45.11. Environment Variables Home 46.1. Interface Functions
    \ No newline at end of file +

    Prev Up Next
    45.11. Environment Variables Home 46.1. Interface Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-abort.html postgresql-13-13.12/doc/src/sgml/html/sql-abort.html --- postgresql-13-13.11/doc/src/sgml/html/sql-abort.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-abort.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -ABORT
    ABORT
    Prev UpSQL CommandsHome Next

    ABORT

    ABORT — abort the current transaction

    Synopsis

    +ABORT
    ABORT
    Prev UpSQL CommandsHome Next
    ABORT
    ABORT — abort the current transaction
    Synopsis
     ABORT [ WORK | TRANSACTION ] [ AND [ NO ] CHAIN ]
 
    Description
    
    ABORT rolls back the current transaction and causes
@@ -28,4 +28,4 @@
    This command is a PostgreSQL extension
    present for historical reasons. ROLLBACK is the
    equivalent standard SQL command.
-  
    Prev Up Next
    SQL Commands Home ALTER AGGREGATE
    
\ No newline at end of file
+
    Prev Up Next
    SQL Commands Home ALTER AGGREGATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alteraggregate.html postgresql-13-13.12/doc/src/sgml/html/sql-alteraggregate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alteraggregate.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alteraggregate.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER AGGREGATE
    ALTER AGGREGATE
    Prev UpSQL CommandsHome Next

    ALTER AGGREGATE

    ALTER AGGREGATE — change the definition of an aggregate function

    Synopsis

    +ALTER AGGREGATE
    ALTER AGGREGATE
    Prev UpSQL CommandsHome Next
    ALTER AGGREGATE
    ALTER AGGREGATE — change the definition of an aggregate function
    Synopsis
     ALTER AGGREGATE name ( aggregate_signature ) RENAME TO new_name
 ALTER AGGREGATE name ( aggregate_signature )
                 OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -80,4 +80,4 @@
 
    Compatibility
    
    There is no ALTER AGGREGATE statement in the SQL
    standard.
-  
    Prev Up Next
    ABORT Home ALTER COLLATION
    
\ No newline at end of file
+
    Prev Up Next
    ABORT Home ALTER COLLATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altercollation.html postgresql-13-13.12/doc/src/sgml/html/sql-altercollation.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altercollation.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altercollation.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER COLLATION
    ALTER COLLATION
    Prev UpSQL CommandsHome Next

    ALTER COLLATION

    ALTER COLLATION — change the definition of a collation

    Synopsis

    +ALTER COLLATION
    ALTER COLLATION
    Prev UpSQL CommandsHome Next
    ALTER COLLATION
    ALTER COLLATION — change the definition of a collation
    Synopsis
     ALTER COLLATION name REFRESH VERSION
 
 ALTER COLLATION name RENAME TO new_name
@@ -83,4 +83,4 @@
 
    Compatibility
    
    There is no ALTER COLLATION statement in the SQL
    standard.
-  
    Prev Up Next
    ALTER AGGREGATE Home ALTER CONVERSION
    
\ No newline at end of file
+
    Prev Up Next
    ALTER AGGREGATE Home ALTER CONVERSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterconversion.html postgresql-13-13.12/doc/src/sgml/html/sql-alterconversion.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterconversion.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterconversion.html 2023-08-07 20:32:20.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER CONVERSION
    ALTER CONVERSION
    Prev UpSQL CommandsHome Next

    ALTER CONVERSION

    ALTER CONVERSION — change the definition of a conversion

    Synopsis

    +ALTER CONVERSION
    ALTER CONVERSION
    Prev UpSQL CommandsHome Next
    ALTER CONVERSION
    ALTER CONVERSION — change the definition of a conversion
    Synopsis
     ALTER CONVERSION name RENAME TO new_name
 ALTER CONVERSION name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 ALTER CONVERSION name SET SCHEMA new_schema
@@ -36,4 +36,4 @@
 
    Compatibility
    
    There is no ALTER CONVERSION statement in the SQL
    standard.
-  
    Prev Up Next
    ALTER COLLATION Home ALTER DATABASE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER COLLATION Home ALTER DATABASE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterdatabase.html postgresql-13-13.12/doc/src/sgml/html/sql-alterdatabase.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterdatabase.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterdatabase.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER DATABASE
    ALTER DATABASE
    Prev UpSQL CommandsHome Next

    ALTER DATABASE

    ALTER DATABASE — change a database

    Synopsis

    +ALTER DATABASE
    ALTER DATABASE
    Prev UpSQL CommandsHome Next
    ALTER DATABASE
    ALTER DATABASE — change a database
    Synopsis
     ALTER DATABASE name [ [ WITH ] option [ ... ] ]
 
 where option can be:
@@ -105,4 +105,4 @@
 
    Compatibility
    
    The ALTER DATABASE statement is a
    PostgreSQL extension.
-  
    Prev Up Next
    ALTER CONVERSION Home ALTER DEFAULT PRIVILEGES
    
\ No newline at end of file
+
    Prev Up Next
    ALTER CONVERSION Home ALTER DEFAULT PRIVILEGES
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterdefaultprivileges.html postgresql-13-13.12/doc/src/sgml/html/sql-alterdefaultprivileges.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterdefaultprivileges.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterdefaultprivileges.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER DEFAULT PRIVILEGES
    ALTER DEFAULT PRIVILEGES
    Prev UpSQL CommandsHome Next

    ALTER DEFAULT PRIVILEGES

    ALTER DEFAULT PRIVILEGES — define default access privileges

    Synopsis

    +ALTER DEFAULT PRIVILEGES
    ALTER DEFAULT PRIVILEGES
    Prev UpSQL CommandsHome Next
    ALTER DEFAULT PRIVILEGES
    ALTER DEFAULT PRIVILEGES — define default access privileges
    Synopsis
     ALTER DEFAULT PRIVILEGES
     [ FOR { ROLE | USER } target_role [, ...] ]
     [ IN SCHEMA schema_name [, ...] ]
@@ -156,4 +156,4 @@
   
    Compatibility
    
    There is no ALTER DEFAULT PRIVILEGES statement in the SQL
    standard.
-  
    See Also
    GRANT, REVOKE
    Prev Up Next
    ALTER DATABASE Home ALTER DOMAIN
    
\ No newline at end of file
+

    See Also

    GRANT, REVOKE
    Prev Up Next
    ALTER DATABASE Home ALTER DOMAIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterdomain.html postgresql-13-13.12/doc/src/sgml/html/sql-alterdomain.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterdomain.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterdomain.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER DOMAIN
    ALTER DOMAIN
    Prev UpSQL CommandsHome Next

    ALTER DOMAIN

    ALTER DOMAIN — +ALTER DOMAIN

    ALTER DOMAIN
    Prev UpSQL CommandsHome Next

    ALTER DOMAIN

    ALTER DOMAIN — change the definition of a domain

    Synopsis

     ALTER DOMAIN name
@@ -149,4 +149,4 @@
    PostgreSQL extensions.  The NOT VALID
    clause of the ADD CONSTRAINT variant is also a
    PostgreSQL extension.
-
    Prev Up Next
    ALTER DEFAULT PRIVILEGES Home ALTER EVENT TRIGGER
    \ No newline at end of file +

    Prev Up Next
    ALTER DEFAULT PRIVILEGES Home ALTER EVENT TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altereventtrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-altereventtrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altereventtrigger.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altereventtrigger.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER EVENT TRIGGER
    ALTER EVENT TRIGGER
    Prev UpSQL CommandsHome Next

    ALTER EVENT TRIGGER

    ALTER EVENT TRIGGER — change the definition of an event trigger

    Synopsis

    +ALTER EVENT TRIGGER
    ALTER EVENT TRIGGER
    Prev UpSQL CommandsHome Next
    ALTER EVENT TRIGGER
    ALTER EVENT TRIGGER — change the definition of an event trigger
    Synopsis
     ALTER EVENT TRIGGER name DISABLE
 ALTER EVENT TRIGGER name ENABLE [ REPLICA | ALWAYS ]
 ALTER EVENT TRIGGER name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -22,4 +22,4 @@

    Compatibility

    There is no ALTER EVENT TRIGGER statement in the SQL standard. -

    Prev Up Next
    ALTER DOMAIN Home ALTER EXTENSION
    \ No newline at end of file +

    Prev Up Next
    ALTER DOMAIN Home ALTER EXTENSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterextension.html postgresql-13-13.12/doc/src/sgml/html/sql-alterextension.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterextension.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterextension.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER EXTENSION
    ALTER EXTENSION
    Prev UpSQL CommandsHome Next

    ALTER EXTENSION

    ALTER EXTENSION — +ALTER EXTENSION

    ALTER EXTENSION
    Prev UpSQL CommandsHome Next

    ALTER EXTENSION

    ALTER EXTENSION — change the definition of an extension

    Synopsis

     ALTER EXTENSION name UPDATE [ TO new_version ]
@@ -138,4 +138,4 @@

    Compatibility

    ALTER EXTENSION is a PostgreSQL extension. -

    Prev Up Next
    ALTER EVENT TRIGGER Home ALTER FOREIGN DATA WRAPPER
    \ No newline at end of file +

    Prev Up Next
    ALTER EVENT TRIGGER Home ALTER FOREIGN DATA WRAPPER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterforeigndatawrapper.html postgresql-13-13.12/doc/src/sgml/html/sql-alterforeigndatawrapper.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterforeigndatawrapper.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterforeigndatawrapper.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER FOREIGN DATA WRAPPER
    ALTER FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next

    ALTER FOREIGN DATA WRAPPER

    ALTER FOREIGN DATA WRAPPER — change the definition of a foreign-data wrapper

    Synopsis

    +ALTER FOREIGN DATA WRAPPER
    ALTER FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next
    ALTER FOREIGN DATA WRAPPER
    ALTER FOREIGN DATA WRAPPER — change the definition of a foreign-data wrapper
    Synopsis
     ALTER FOREIGN DATA WRAPPER name
     [ HANDLER handler_function | NO HANDLER ]
     [ VALIDATOR validator_function | NO VALIDATOR ]
@@ -65,4 +65,4 @@
    9075-9 (SQL/MED), except that the HANDLER,
    VALIDATOR, OWNER TO, and RENAME
    clauses are extensions.
-  
    Prev Up Next
    ALTER EXTENSION Home ALTER FOREIGN TABLE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER EXTENSION Home ALTER FOREIGN TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterforeigntable.html postgresql-13-13.12/doc/src/sgml/html/sql-alterforeigntable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterforeigntable.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterforeigntable.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER FOREIGN TABLE
    ALTER FOREIGN TABLE
    Prev UpSQL CommandsHome Next

    ALTER FOREIGN TABLE

    ALTER FOREIGN TABLE — change the definition of a foreign table

    Synopsis

    +ALTER FOREIGN TABLE
    ALTER FOREIGN TABLE
    Prev UpSQL CommandsHome Next
    ALTER FOREIGN TABLE
    ALTER FOREIGN TABLE — change the definition of a foreign table
    Synopsis
     ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] name [ * ]
     action [, ... ]
 ALTER FOREIGN TABLE [ IF EXISTS ] [ ONLY ] name [ * ]
@@ -221,7 +221,7 @@
   
    
    To change options of a foreign table:
 
    -ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2 'value2', DROP opt3 'value3');
+ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2 'value2', DROP opt3);
 
    Compatibility
    
    The forms ADD, DROP,
    and SET DATA TYPE
@@ -233,4 +233,4 @@
    ALTER FOREIGN TABLE DROP COLUMN can be used to drop the only
    column of a foreign table, leaving a zero-column table.  This is an
    extension of SQL, which disallows zero-column foreign tables.
-  
    Prev Up Next
    ALTER FOREIGN DATA WRAPPER Home ALTER FUNCTION
    
\ No newline at end of file
+
    Prev Up Next
    ALTER FOREIGN DATA WRAPPER Home ALTER FUNCTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterfunction.html postgresql-13-13.12/doc/src/sgml/html/sql-alterfunction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterfunction.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterfunction.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER FUNCTION
    ALTER FUNCTION
    Prev UpSQL CommandsHome Next

    ALTER FUNCTION

    ALTER FUNCTION — change the definition of a function

    Synopsis

    +ALTER FUNCTION
    ALTER FUNCTION
    Prev UpSQL CommandsHome Next
    ALTER FUNCTION
    ALTER FUNCTION — change the definition of a function
    Synopsis
     ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
     action [ ... ] [ RESTRICT ]
 ALTER FUNCTION name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
@@ -171,4 +171,4 @@
    or change the owner, schema, or volatility of a function. The standard also
    requires the RESTRICT key word, which is optional in
    PostgreSQL.
-  
    Prev Up Next
    ALTER FOREIGN TABLE Home ALTER GROUP
    
\ No newline at end of file
+
    Prev Up Next
    ALTER FOREIGN TABLE Home ALTER GROUP
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altergroup.html postgresql-13-13.12/doc/src/sgml/html/sql-altergroup.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altergroup.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altergroup.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER GROUP
    ALTER GROUP
    Prev UpSQL CommandsHome Next

    ALTER GROUP

    ALTER GROUP — change role name or membership

    Synopsis

    +ALTER GROUP
    ALTER GROUP
    Prev UpSQL CommandsHome Next
    ALTER GROUP
    ALTER GROUP — change role name or membership
    Synopsis
     ALTER GROUP role_specification ADD USER user_name [, ... ]
 ALTER GROUP role_specification DROP USER user_name [, ... ]
 
@@ -49,4 +49,4 @@
 
    Compatibility
    
    There is no ALTER GROUP statement in the SQL
    standard.
-  
    Prev Up Next
    ALTER FUNCTION Home ALTER INDEX
    
\ No newline at end of file
+
    Prev Up Next
    ALTER FUNCTION Home ALTER INDEX
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterindex.html postgresql-13-13.12/doc/src/sgml/html/sql-alterindex.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterindex.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterindex.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER INDEX
    ALTER INDEX
    Prev UpSQL CommandsHome Next

    ALTER INDEX

    ALTER INDEX — change the definition of an index

    Synopsis

    +ALTER INDEX
    ALTER INDEX
    Prev UpSQL CommandsHome Next
    ALTER INDEX
    ALTER INDEX — change the definition of an index
    Synopsis
     ALTER INDEX [ IF EXISTS ] name RENAME TO new_name
 ALTER INDEX [ IF EXISTS ] name SET TABLESPACE tablespace_name
 ALTER INDEX name ATTACH PARTITION index_name
@@ -135,4 +135,4 @@
 
    Compatibility
    
    ALTER INDEX is a PostgreSQL
    extension.
-  
    Prev Up Next
    ALTER GROUP Home ALTER LANGUAGE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER GROUP Home ALTER LANGUAGE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterlanguage.html postgresql-13-13.12/doc/src/sgml/html/sql-alterlanguage.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterlanguage.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterlanguage.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER LANGUAGE
    ALTER LANGUAGE
    Prev UpSQL CommandsHome Next

    ALTER LANGUAGE

    ALTER LANGUAGE — change the definition of a procedural language

    Synopsis

    +ALTER LANGUAGE
    ALTER LANGUAGE
    Prev UpSQL CommandsHome Next
    ALTER LANGUAGE
    ALTER LANGUAGE — change the definition of a procedural language
    Synopsis
     ALTER [ PROCEDURAL ] LANGUAGE name RENAME TO new_name
 ALTER [ PROCEDURAL ] LANGUAGE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 
    Description
    
@@ -16,4 +16,4 @@
      
    Compatibility
    
    There is no ALTER LANGUAGE statement in the SQL
    standard.
-
    Prev Up Next
    ALTER INDEX Home ALTER LARGE OBJECT
    \ No newline at end of file +

    Prev Up Next
    ALTER INDEX Home ALTER LARGE OBJECT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterlargeobject.html postgresql-13-13.12/doc/src/sgml/html/sql-alterlargeobject.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterlargeobject.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterlargeobject.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER LARGE OBJECT
    ALTER LARGE OBJECT
    Prev UpSQL CommandsHome Next

    ALTER LARGE OBJECT

    ALTER LARGE OBJECT — change the definition of a large object

    Synopsis

    +ALTER LARGE OBJECT
    ALTER LARGE OBJECT
    Prev UpSQL CommandsHome Next
    ALTER LARGE OBJECT
    ALTER LARGE OBJECT — change the definition of a large object
    Synopsis
     ALTER LARGE OBJECT large_object_oid OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 
    Description
    
    ALTER LARGE OBJECT changes the definition of a
@@ -17,4 +17,4 @@
      
    Compatibility
    
    There is no ALTER LARGE OBJECT statement in the SQL
    standard.
-  
    See Also
    Chapter 34
    Prev Up Next
    ALTER LANGUAGE Home ALTER MATERIALIZED VIEW
    \ No newline at end of file +

    See Also

    Chapter 34
    Prev Up Next
    ALTER LANGUAGE Home ALTER MATERIALIZED VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altermaterializedview.html postgresql-13-13.12/doc/src/sgml/html/sql-altermaterializedview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altermaterializedview.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altermaterializedview.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER MATERIALIZED VIEW
    ALTER MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next

    ALTER MATERIALIZED VIEW

    ALTER MATERIALIZED VIEW — change the definition of a materialized view

    Synopsis

    +ALTER MATERIALIZED VIEW
    ALTER MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next
    ALTER MATERIALIZED VIEW
    ALTER MATERIALIZED VIEW — change the definition of a materialized view
    Synopsis
     ALTER MATERIALIZED VIEW [ IF EXISTS ] name
     action [, ... ]
 ALTER MATERIALIZED VIEW name
@@ -69,4 +69,4 @@
 
    Compatibility
    
    ALTER MATERIALIZED VIEW is a
    PostgreSQL extension.
-  
    Prev Up Next
    ALTER LARGE OBJECT Home ALTER OPERATOR
    
\ No newline at end of file
+
    Prev Up Next
    ALTER LARGE OBJECT Home ALTER OPERATOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alteropclass.html postgresql-13-13.12/doc/src/sgml/html/sql-alteropclass.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alteropclass.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alteropclass.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER OPERATOR CLASS
    ALTER OPERATOR CLASS
    Prev UpSQL CommandsHome Next

    ALTER OPERATOR CLASS

    ALTER OPERATOR CLASS — change the definition of an operator class

    Synopsis

    +ALTER OPERATOR CLASS
    ALTER OPERATOR CLASS
    Prev UpSQL CommandsHome Next
    ALTER OPERATOR CLASS
    ALTER OPERATOR CLASS — change the definition of an operator class
    Synopsis
     ALTER OPERATOR CLASS name USING index_method
     RENAME TO new_name
 
@@ -33,4 +33,4 @@
      
    Compatibility
    
    There is no ALTER OPERATOR CLASS statement in
    the SQL standard.
-
    Prev Up Next
    ALTER OPERATOR Home ALTER OPERATOR FAMILY
    \ No newline at end of file +

    Prev Up Next
    ALTER OPERATOR Home ALTER OPERATOR FAMILY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alteroperator.html postgresql-13-13.12/doc/src/sgml/html/sql-alteroperator.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alteroperator.html 2023-05-08 21:34:01.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alteroperator.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER OPERATOR
    ALTER OPERATOR
    Prev UpSQL CommandsHome Next

    ALTER OPERATOR

    ALTER OPERATOR — change the definition of an operator

    Synopsis

    +ALTER OPERATOR
    ALTER OPERATOR
    Prev UpSQL CommandsHome Next
    ALTER OPERATOR
    ALTER OPERATOR — change the definition of an operator
    Synopsis
     ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } )
     OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 
@@ -47,4 +47,4 @@
 
    Compatibility
    
    There is no ALTER OPERATOR statement in
    the SQL standard.
-  
    Prev Up Next
    ALTER MATERIALIZED VIEW Home ALTER OPERATOR CLASS
    
\ No newline at end of file
+
    Prev Up Next
    ALTER MATERIALIZED VIEW Home ALTER OPERATOR CLASS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alteropfamily.html postgresql-13-13.12/doc/src/sgml/html/sql-alteropfamily.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alteropfamily.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alteropfamily.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER OPERATOR FAMILY
    ALTER OPERATOR FAMILY
    Prev UpSQL CommandsHome Next

    ALTER OPERATOR FAMILY

    ALTER OPERATOR FAMILY — change the definition of an operator family

    Synopsis

    +ALTER OPERATOR FAMILY
    ALTER OPERATOR FAMILY
    Prev UpSQL CommandsHome Next
    ALTER OPERATOR FAMILY
    ALTER OPERATOR FAMILY — change the definition of an operator family
    Synopsis
     ALTER OPERATOR FAMILY name USING index_method ADD
   {  OPERATOR strategy_number operator_name ( op_type, op_type )
               [ FOR SEARCH | FOR ORDER BY sort_family_name ]
@@ -178,4 +178,4 @@
 
    Compatibility
    
    There is no ALTER OPERATOR FAMILY statement in
    the SQL standard.
-  
    Prev Up Next
    ALTER OPERATOR CLASS Home ALTER POLICY
    
\ No newline at end of file
+
    Prev Up Next
    ALTER OPERATOR CLASS Home ALTER POLICY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterpolicy.html postgresql-13-13.12/doc/src/sgml/html/sql-alterpolicy.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterpolicy.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterpolicy.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER POLICY
    ALTER POLICY
    Prev UpSQL CommandsHome Next

    ALTER POLICY

    ALTER POLICY — change the definition of a row level security policy

    Synopsis

    +ALTER POLICY
    ALTER POLICY
    Prev UpSQL CommandsHome Next
    ALTER POLICY
    ALTER POLICY — change the definition of a row level security policy
    Synopsis
     ALTER POLICY name ON table_name RENAME TO new_name
 
 ALTER POLICY name ON table_name
@@ -42,4 +42,4 @@
       See CREATE POLICY for details.
      
    Compatibility
    
    ALTER POLICY is a PostgreSQL extension.
-
    Prev Up Next
    ALTER OPERATOR FAMILY Home ALTER PROCEDURE
    \ No newline at end of file +

    Prev Up Next
    ALTER OPERATOR FAMILY Home ALTER PROCEDURE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterprocedure.html postgresql-13-13.12/doc/src/sgml/html/sql-alterprocedure.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterprocedure.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterprocedure.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER PROCEDURE
    ALTER PROCEDURE
    Prev UpSQL CommandsHome Next

    ALTER PROCEDURE

    ALTER PROCEDURE — change the definition of a procedure

    Synopsis

    +ALTER PROCEDURE
    ALTER PROCEDURE
    Prev UpSQL CommandsHome Next
    ALTER PROCEDURE
    ALTER PROCEDURE — change the definition of a procedure
    Synopsis
     ALTER PROCEDURE name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
     action [ ... ] [ RESTRICT ]
 ALTER PROCEDURE name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
@@ -127,4 +127,4 @@
    or change the owner, schema, or volatility of a procedure. The standard also
    requires the RESTRICT key word, which is optional in
    PostgreSQL.
-  
    Prev Up Next
    ALTER POLICY Home ALTER PUBLICATION
    
\ No newline at end of file
+
    Prev Up Next
    ALTER POLICY Home ALTER PUBLICATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterpublication.html postgresql-13-13.12/doc/src/sgml/html/sql-alterpublication.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterpublication.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterpublication.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER PUBLICATION
    ALTER PUBLICATION
    Prev UpSQL CommandsHome Next

    ALTER PUBLICATION

    ALTER PUBLICATION — change the definition of a publication

    Synopsis

    +ALTER PUBLICATION
    ALTER PUBLICATION
    Prev UpSQL CommandsHome Next
    ALTER PUBLICATION
    ALTER PUBLICATION — change the definition of a publication
    Synopsis
     ALTER PUBLICATION name ADD TABLE [ ONLY ] table_name [ * ] [, ...]
 ALTER PUBLICATION name SET TABLE [ ONLY ] table_name [ * ] [, ...]
 ALTER PUBLICATION name DROP TABLE [ ONLY ] table_name [ * ] [, ...]
@@ -60,4 +60,4 @@
 
    Compatibility
    
    ALTER PUBLICATION is a PostgreSQL
    extension.
-  
    Prev Up Next
    ALTER PROCEDURE Home ALTER ROLE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER PROCEDURE Home ALTER ROLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterrole.html postgresql-13-13.12/doc/src/sgml/html/sql-alterrole.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterrole.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterrole.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER ROLE
    ALTER ROLE
    Prev UpSQL CommandsHome Next

    ALTER ROLE

    ALTER ROLE — change a database role

    Synopsis

    +ALTER ROLE
    ALTER ROLE
    Prev UpSQL CommandsHome Next
    ALTER ROLE
    ALTER ROLE — change a database role
    Synopsis
     ALTER ROLE role_specification [ WITH ] option [ ... ]
 
 where option can be:
@@ -185,4 +185,4 @@
 
    Compatibility
    
    The ALTER ROLE statement is a
    PostgreSQL extension.
-  
    Prev Up Next
    ALTER PUBLICATION Home ALTER ROUTINE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER PUBLICATION Home ALTER ROUTINE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterroutine.html postgresql-13-13.12/doc/src/sgml/html/sql-alterroutine.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterroutine.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterroutine.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER ROUTINE
    ALTER ROUTINE
    Prev UpSQL CommandsHome Next

    ALTER ROUTINE

    ALTER ROUTINE — change the definition of a routine

    Synopsis

    +ALTER ROUTINE
    ALTER ROUTINE
    Prev UpSQL CommandsHome Next
    ALTER ROUTINE
    ALTER ROUTINE — change the definition of a routine
    Synopsis
     ALTER ROUTINE name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
     action [ ... ] [ RESTRICT ]
 ALTER ROUTINE name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ]
@@ -46,4 +46,4 @@
    a PostgreSQL extension.
   
    See Also
    ALTER AGGREGATE, ALTER FUNCTION, ALTER PROCEDURE, DROP ROUTINE
    
    Note that there is no CREATE ROUTINE command.
-  
    Prev Up Next
    ALTER ROLE Home ALTER RULE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER ROLE Home ALTER RULE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterrule.html postgresql-13-13.12/doc/src/sgml/html/sql-alterrule.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterrule.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterrule.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER RULE
    ALTER RULE
    Prev UpSQL CommandsHome Next

    ALTER RULE

    ALTER RULE — change the definition of a rule

    Synopsis

    +ALTER RULE
    ALTER RULE
    Prev UpSQL CommandsHome Next
    ALTER RULE
    ALTER RULE — change the definition of a rule
    Synopsis
     ALTER RULE name ON table_name RENAME TO new_name
 
    Description
    
    ALTER RULE changes properties of an existing
@@ -22,4 +22,4 @@
    ALTER RULE is a
    PostgreSQL language extension, as is the
    entire query rewrite system.
-  
    Prev Up Next
    ALTER ROUTINE Home ALTER SCHEMA
    
\ No newline at end of file
+
    Prev Up Next
    ALTER ROUTINE Home ALTER SCHEMA
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterschema.html postgresql-13-13.12/doc/src/sgml/html/sql-alterschema.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterschema.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterschema.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER SCHEMA
    ALTER SCHEMA
    Prev UpSQL CommandsHome Next

    ALTER SCHEMA

    ALTER SCHEMA — change the definition of a schema

    Synopsis

    +ALTER SCHEMA
    ALTER SCHEMA
    Prev UpSQL CommandsHome Next
    ALTER SCHEMA
    ALTER SCHEMA — change the definition of a schema
    Synopsis
     ALTER SCHEMA name RENAME TO new_name
 ALTER SCHEMA name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 
    Description
    
@@ -23,4 +23,4 @@
      
    Compatibility
    
    There is no ALTER SCHEMA statement in the SQL
    standard.
-
    Prev Up Next
    ALTER RULE Home ALTER SEQUENCE
    \ No newline at end of file +

    Prev Up Next
    ALTER RULE Home ALTER SEQUENCE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altersequence.html postgresql-13-13.12/doc/src/sgml/html/sql-altersequence.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altersequence.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altersequence.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER SEQUENCE
    ALTER SEQUENCE
    Prev UpSQL CommandsHome Next

    ALTER SEQUENCE

    ALTER SEQUENCE — +ALTER SEQUENCE

    ALTER SEQUENCE
    Prev UpSQL CommandsHome Next

    ALTER SEQUENCE

    ALTER SEQUENCE — change the definition of a sequence generator

    Synopsis

     ALTER SEQUENCE [ IF EXISTS ] name
@@ -157,4 +157,4 @@
    OWNED BY, OWNER TO, RENAME TO, and
    SET SCHEMA clauses, which are
    PostgreSQL extensions.
-
    Prev Up Next
    ALTER SCHEMA Home ALTER SERVER
    \ No newline at end of file +

    Prev Up Next
    ALTER SCHEMA Home ALTER SERVER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterserver.html postgresql-13-13.12/doc/src/sgml/html/sql-alterserver.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterserver.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterserver.html 2023-08-07 20:32:21.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER SERVER
    ALTER SERVER
    Prev UpSQL CommandsHome Next

    ALTER SERVER

    ALTER SERVER — change the definition of a foreign server

    Synopsis

    +ALTER SERVER
    ALTER SERVER
    Prev UpSQL CommandsHome Next
    ALTER SERVER
    ALTER SERVER — change the definition of a foreign server
    Synopsis
     ALTER SERVER name [ VERSION 'new_version' ]
     [ OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] ) ]
 ALTER SERVER name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -45,4 +45,4 @@
    ALTER SERVER conforms to ISO/IEC 9075-9 (SQL/MED).
    The OWNER TO and RENAME forms are
    PostgreSQL extensions.
-  
    Prev Up Next
    ALTER SEQUENCE Home ALTER STATISTICS
    
\ No newline at end of file
+
    Prev Up Next
    ALTER SEQUENCE Home ALTER STATISTICS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterstatistics.html postgresql-13-13.12/doc/src/sgml/html/sql-alterstatistics.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterstatistics.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterstatistics.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER STATISTICS
    ALTER STATISTICS
    Prev UpSQL CommandsHome Next

    ALTER STATISTICS

    ALTER STATISTICS — +ALTER STATISTICS

    ALTER STATISTICS
    Prev UpSQL CommandsHome Next

    ALTER STATISTICS

    ALTER STATISTICS — change the definition of an extended statistics object

    Synopsis

     ALTER STATISTICS name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -43,4 +43,4 @@

    Compatibility

    There is no ALTER STATISTICS command in the SQL standard. -

    Prev Up Next
    ALTER SERVER Home ALTER SUBSCRIPTION
    \ No newline at end of file +

    Prev Up Next
    ALTER SERVER Home ALTER SUBSCRIPTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altersubscription.html postgresql-13-13.12/doc/src/sgml/html/sql-altersubscription.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altersubscription.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altersubscription.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER SUBSCRIPTION
    ALTER SUBSCRIPTION
    Prev UpSQL CommandsHome Next

    ALTER SUBSCRIPTION

    ALTER SUBSCRIPTION — change the definition of a subscription

    Synopsis

    +ALTER SUBSCRIPTION
    ALTER SUBSCRIPTION
    Prev UpSQL CommandsHome Next
    ALTER SUBSCRIPTION
    ALTER SUBSCRIPTION — change the definition of a subscription
    Synopsis
     ALTER SUBSCRIPTION name CONNECTION 'conninfo'
 ALTER SUBSCRIPTION name SET PUBLICATION publication_name [, ...] [ WITH ( set_publication_option [= value] [, ... ] ) ]
 ALTER SUBSCRIPTION name REFRESH PUBLICATION [ WITH ( refresh_option [= value] [, ... ] ) ]
@@ -83,4 +83,4 @@
 
    Compatibility
    
    ALTER SUBSCRIPTION is a PostgreSQL
    extension.
-  
    Prev Up Next
    ALTER STATISTICS Home ALTER SYSTEM
    
\ No newline at end of file
+
    Prev Up Next
    ALTER STATISTICS Home ALTER SYSTEM
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altersystem.html postgresql-13-13.12/doc/src/sgml/html/sql-altersystem.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altersystem.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altersystem.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER SYSTEM
    ALTER SYSTEM
    Prev UpSQL CommandsHome Next

    ALTER SYSTEM

    ALTER SYSTEM — change a server configuration parameter

    Synopsis

    +ALTER SYSTEM
    ALTER SYSTEM
    Prev UpSQL CommandsHome Next
    ALTER SYSTEM
    ALTER SYSTEM — change a server configuration parameter
    Synopsis
     ALTER SYSTEM SET configuration_parameter { TO | = } { value | 'value' | DEFAULT }
 
 ALTER SYSTEM RESET configuration_parameter
@@ -55,4 +55,4 @@
 
    Compatibility
    
    The ALTER SYSTEM statement is a
    PostgreSQL extension.
-  
    See Also
    SET, SHOW
    Prev Up Next
    ALTER SUBSCRIPTION Home ALTER TABLE
    
\ No newline at end of file
+

    See Also

    SET, SHOW
    Prev Up Next
    ALTER SUBSCRIPTION Home ALTER TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertable.html postgresql-13-13.12/doc/src/sgml/html/sql-altertable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertable.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertable.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TABLE
    ALTER TABLE
    Prev UpSQL CommandsHome Next

    ALTER TABLE

    ALTER TABLE — change the definition of a table

    Synopsis

    +ALTER TABLE
    ALTER TABLE
    Prev UpSQL CommandsHome Next
    ALTER TABLE
    ALTER TABLE — change the definition of a table
    Synopsis
     ALTER TABLE [ IF EXISTS ] [ ONLY ] name [ * ]
     action [, ... ]
 ALTER TABLE [ IF EXISTS ] [ ONLY ] name [ * ]
@@ -1016,4 +1016,4 @@
    ALTER TABLE DROP COLUMN can be used to drop the only
    column of a table, leaving a zero-column table.  This is an
    extension of SQL, which disallows zero-column tables.
-  
    See Also
    CREATE TABLE
    Prev Up Next
    ALTER SYSTEM Home ALTER TABLESPACE
    
\ No newline at end of file
+

    See Also

    CREATE TABLE
    Prev Up Next
    ALTER SYSTEM Home ALTER TABLESPACE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertablespace.html postgresql-13-13.12/doc/src/sgml/html/sql-altertablespace.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertablespace.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertablespace.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TABLESPACE
    ALTER TABLESPACE
    Prev UpSQL CommandsHome Next

    ALTER TABLESPACE

    ALTER TABLESPACE — change the definition of a tablespace

    Synopsis

    +ALTER TABLESPACE
    ALTER TABLESPACE
    Prev UpSQL CommandsHome Next
    ALTER TABLESPACE
    ALTER TABLESPACE — change the definition of a tablespace
    Synopsis
     ALTER TABLESPACE name RENAME TO new_name
 ALTER TABLESPACE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
 ALTER TABLESPACE name SET ( tablespace_option = value [, ... ] )
@@ -47,4 +47,4 @@
 
    Compatibility
    
    There is no ALTER TABLESPACE statement in
    the SQL standard.
-  
    Prev Up Next
    ALTER TABLE Home ALTER TEXT SEARCH CONFIGURATION
    
\ No newline at end of file
+
    Prev Up Next
    ALTER TABLE Home ALTER TEXT SEARCH CONFIGURATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-altertrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertrigger.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertrigger.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TRIGGER
    ALTER TRIGGER
    Prev UpSQL CommandsHome Next

    ALTER TRIGGER

    ALTER TRIGGER — change the definition of a trigger

    Synopsis

    +ALTER TRIGGER
    ALTER TRIGGER
    Prev UpSQL CommandsHome Next
    ALTER TRIGGER
    ALTER TRIGGER — change the definition of a trigger
    Synopsis
     ALTER TRIGGER name ON table_name RENAME TO new_name
 ALTER TRIGGER name ON table_name [ NO ] DEPENDS ON EXTENSION extension_name
 
    Description
    
@@ -39,4 +39,4 @@

    Compatibility

    ALTER TRIGGER is a PostgreSQL extension of the SQL standard. -

    See Also

    ALTER TABLE
    Prev Up Next
    ALTER TEXT SEARCH TEMPLATE Home ALTER TYPE
    \ No newline at end of file +

    See Also

    ALTER TABLE
    Prev Up Next
    ALTER TEXT SEARCH TEMPLATE Home ALTER TYPE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertsconfig.html postgresql-13-13.12/doc/src/sgml/html/sql-altertsconfig.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertsconfig.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertsconfig.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TEXT SEARCH CONFIGURATION
    ALTER TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next

    ALTER TEXT SEARCH CONFIGURATION

    ALTER TEXT SEARCH CONFIGURATION — change the definition of a text search configuration

    Synopsis

    +ALTER TEXT SEARCH CONFIGURATION
    ALTER TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next
    ALTER TEXT SEARCH CONFIGURATION
    ALTER TEXT SEARCH CONFIGURATION — change the definition of a text search configuration
    Synopsis
     ALTER TEXT SEARCH CONFIGURATION name
     ADD MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ]
 ALTER TEXT SEARCH CONFIGURATION name
@@ -65,4 +65,4 @@
 
    Compatibility
    
    There is no ALTER TEXT SEARCH CONFIGURATION statement in
    the SQL standard.
-  
    Prev Up Next
    ALTER TABLESPACE Home ALTER TEXT SEARCH DICTIONARY
    
\ No newline at end of file
+
    Prev Up Next
    ALTER TABLESPACE Home ALTER TEXT SEARCH DICTIONARY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertsdictionary.html postgresql-13-13.12/doc/src/sgml/html/sql-altertsdictionary.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertsdictionary.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertsdictionary.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TEXT SEARCH DICTIONARY
    ALTER TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next

    ALTER TEXT SEARCH DICTIONARY

    ALTER TEXT SEARCH DICTIONARY — change the definition of a text search dictionary

    Synopsis

    +ALTER TEXT SEARCH DICTIONARY
    ALTER TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next
    ALTER TEXT SEARCH DICTIONARY
    ALTER TEXT SEARCH DICTIONARY — change the definition of a text search dictionary
    Synopsis
     ALTER TEXT SEARCH DICTIONARY name (
     option [ = value ] [, ... ]
 )
@@ -57,4 +57,4 @@
   
    Compatibility
    
    There is no ALTER TEXT SEARCH DICTIONARY statement in
    the SQL standard.
-  
    Prev Up Next
    ALTER TEXT SEARCH CONFIGURATION Home ALTER TEXT SEARCH PARSER
    
\ No newline at end of file
+
    Prev Up Next
    ALTER TEXT SEARCH CONFIGURATION Home ALTER TEXT SEARCH PARSER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertsparser.html postgresql-13-13.12/doc/src/sgml/html/sql-altertsparser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertsparser.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertsparser.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TEXT SEARCH PARSER
    ALTER TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next

    ALTER TEXT SEARCH PARSER

    ALTER TEXT SEARCH PARSER — change the definition of a text search parser

    Synopsis

    +ALTER TEXT SEARCH PARSER
    ALTER TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next
    ALTER TEXT SEARCH PARSER
    ALTER TEXT SEARCH PARSER — change the definition of a text search parser
    Synopsis
     ALTER TEXT SEARCH PARSER name RENAME TO new_name
 ALTER TEXT SEARCH PARSER name SET SCHEMA new_schema
 
    Description
    
@@ -17,4 +17,4 @@
      
    Compatibility
    
    There is no ALTER TEXT SEARCH PARSER statement in
    the SQL standard.
-
    Prev Up Next
    ALTER TEXT SEARCH DICTIONARY Home ALTER TEXT SEARCH TEMPLATE
    \ No newline at end of file +

    Prev Up Next
    ALTER TEXT SEARCH DICTIONARY Home ALTER TEXT SEARCH TEMPLATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertstemplate.html postgresql-13-13.12/doc/src/sgml/html/sql-altertstemplate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertstemplate.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertstemplate.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TEXT SEARCH TEMPLATE
    ALTER TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next

    ALTER TEXT SEARCH TEMPLATE

    ALTER TEXT SEARCH TEMPLATE — change the definition of a text search template

    Synopsis

    +ALTER TEXT SEARCH TEMPLATE
    ALTER TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next
    ALTER TEXT SEARCH TEMPLATE
    ALTER TEXT SEARCH TEMPLATE — change the definition of a text search template
    Synopsis
     ALTER TEXT SEARCH TEMPLATE name RENAME TO new_name
 ALTER TEXT SEARCH TEMPLATE name SET SCHEMA new_schema
 
    Description
    
@@ -17,4 +17,4 @@
      
    Compatibility
    
    There is no ALTER TEXT SEARCH TEMPLATE statement in
    the SQL standard.
-
    Prev Up Next
    ALTER TEXT SEARCH PARSER Home ALTER TRIGGER
    \ No newline at end of file +

    Prev Up Next
    ALTER TEXT SEARCH PARSER Home ALTER TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-altertype.html postgresql-13-13.12/doc/src/sgml/html/sql-altertype.html --- postgresql-13-13.11/doc/src/sgml/html/sql-altertype.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-altertype.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER TYPE
    ALTER TYPE
    Prev UpSQL CommandsHome Next

    ALTER TYPE

    ALTER TYPE — +ALTER TYPE

    ALTER TYPE
    Prev UpSQL CommandsHome Next

    ALTER TYPE

    ALTER TYPE — change the definition of a type

    Synopsis

     ALTER TYPE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -218,4 +218,4 @@

    Compatibility

    The variants to add and drop attributes are part of the SQL standard; the other variants are PostgreSQL extensions. -

    Prev Up Next
    ALTER TRIGGER Home ALTER USER
    \ No newline at end of file +

    Prev Up Next
    ALTER TRIGGER Home ALTER USER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alteruser.html postgresql-13-13.12/doc/src/sgml/html/sql-alteruser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alteruser.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alteruser.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER USER
    ALTER USER
    Prev UpSQL CommandsHome Next

    ALTER USER

    ALTER USER — change a database role

    Synopsis

    +ALTER USER
    ALTER USER
    Prev UpSQL CommandsHome Next
    ALTER USER
    ALTER USER — change a database role
    Synopsis
     ALTER USER role_specification [ WITH ] option [ ... ]
 
 where option can be:
@@ -34,4 +34,4 @@
    The ALTER USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
-  
    See Also
    ALTER ROLE
    Prev Up Next
    ALTER TYPE Home ALTER USER MAPPING
    
\ No newline at end of file
+

    See Also

    ALTER ROLE
    Prev Up Next
    ALTER TYPE Home ALTER USER MAPPING
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterusermapping.html postgresql-13-13.12/doc/src/sgml/html/sql-alterusermapping.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterusermapping.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterusermapping.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER USER MAPPING
    ALTER USER MAPPING
    Prev UpSQL CommandsHome Next

    ALTER USER MAPPING

    ALTER USER MAPPING — change the definition of a user mapping

    Synopsis

    +ALTER USER MAPPING
    ALTER USER MAPPING
    Prev UpSQL CommandsHome Next
    ALTER USER MAPPING
    ALTER USER MAPPING — change the definition of a user mapping
    Synopsis
     ALTER USER MAPPING FOR { user_name | USER | CURRENT_USER | SESSION_USER | PUBLIC }
     SERVER server_name
     OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
@@ -40,4 +40,4 @@
    for ALTER USER MAPPING, PostgreSQL diverges from
    the standard here in the interest of consistency and
    interoperability.
-  
    Prev Up Next
    ALTER USER Home ALTER VIEW
    
\ No newline at end of file
+
    Prev Up Next
    ALTER USER Home ALTER VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-alterview.html postgresql-13-13.12/doc/src/sgml/html/sql-alterview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-alterview.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-alterview.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ALTER VIEW
    ALTER VIEW
    Prev UpSQL CommandsHome Next

    ALTER VIEW

    ALTER VIEW — change the definition of a view

    Synopsis

    +ALTER VIEW
    ALTER VIEW
    Prev UpSQL CommandsHome Next
    ALTER VIEW
    ALTER VIEW — change the definition of a view
    Synopsis
     ALTER VIEW [ IF EXISTS ] name ALTER [ COLUMN ] column_name SET DEFAULT expression
 ALTER VIEW [ IF EXISTS ] name ALTER [ COLUMN ] column_name DROP DEFAULT
 ALTER VIEW [ IF EXISTS ] name OWNER TO { new_owner | CURRENT_USER | SESSION_USER }
@@ -73,4 +73,4 @@
 
    Compatibility
    
    ALTER VIEW is a PostgreSQL
    extension of the SQL standard.
-  
    Prev Up Next
    ALTER USER MAPPING Home ANALYZE
    
\ No newline at end of file
+
    Prev Up Next
    ALTER USER MAPPING Home ANALYZE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-analyze.html postgresql-13-13.12/doc/src/sgml/html/sql-analyze.html --- postgresql-13-13.11/doc/src/sgml/html/sql-analyze.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-analyze.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -ANALYZE
    ANALYZE
    Prev UpSQL CommandsHome Next

    ANALYZE

    ANALYZE — collect statistics about a database

    Synopsis

    +ANALYZE
    ANALYZE
    Prev UpSQL CommandsHome Next
    ANALYZE
    ANALYZE — collect statistics about a database
    Synopsis
     ANALYZE [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
 ANALYZE [ VERBOSE ] [ table_and_columns [, ...] ]
 
@@ -181,4 +181,4 @@
     will be retained.
   
    Compatibility
    
    There is no ANALYZE statement in the SQL standard.
-  
    Prev Up Next
    ALTER VIEW Home BEGIN
    
\ No newline at end of file
+
    Prev Up Next
    ALTER VIEW Home BEGIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-begin.html postgresql-13-13.12/doc/src/sgml/html/sql-begin.html --- postgresql-13-13.11/doc/src/sgml/html/sql-begin.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-begin.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -BEGIN
    BEGIN
    Prev UpSQL CommandsHome Next

    BEGIN

    BEGIN — start a transaction block

    Synopsis

    +BEGIN
    BEGIN
    Prev UpSQL CommandsHome Next
    BEGIN
    BEGIN — start a transaction block
    Synopsis
     BEGIN [ WORK | TRANSACTION ] [ transaction_mode [, ...] ]
 
 where transaction_mode is one of:
@@ -68,4 +68,4 @@
    Incidentally, the BEGIN key word is used for a
    different purpose in embedded SQL. You are advised to be careful
    about the transaction semantics when porting database applications.
-  
    Prev Up Next
    ANALYZE Home CALL
    
\ No newline at end of file
+
    Prev Up Next
    ANALYZE Home CALL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-call.html postgresql-13-13.12/doc/src/sgml/html/sql-call.html --- postgresql-13-13.11/doc/src/sgml/html/sql-call.html 2023-05-08 21:34:02.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-call.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CALL
    CALL
    Prev UpSQL CommandsHome Next

    CALL

    CALL — invoke a procedure

    Synopsis

    +CALL
    CALL
    Prev UpSQL CommandsHome Next
    CALL
    CALL — invoke a procedure
    Synopsis
     CALL name ( [ argument ] [, ...] )
 
    Description
    
    CALL executes a procedure.
@@ -30,4 +30,4 @@
 CALL do_db_maintenance();

    Compatibility

    CALL conforms to the SQL standard. -

    Prev Up Next
    BEGIN Home CHECKPOINT
    \ No newline at end of file +

    Prev Up Next
    BEGIN Home CHECKPOINT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-checkpoint.html postgresql-13-13.12/doc/src/sgml/html/sql-checkpoint.html --- postgresql-13-13.11/doc/src/sgml/html/sql-checkpoint.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-checkpoint.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CHECKPOINT
    CHECKPOINT
    Prev UpSQL CommandsHome Next

    CHECKPOINT

    CHECKPOINT — force a write-ahead log checkpoint

    Synopsis

    +CHECKPOINT
    CHECKPOINT
    Prev UpSQL CommandsHome Next
    CHECKPOINT
    CHECKPOINT — force a write-ahead log checkpoint
    Synopsis
     CHECKPOINT
 
    Description
    
    A checkpoint is a point in the write-ahead log sequence at which
@@ -23,4 +23,4 @@
   
    Compatibility
    
    The CHECKPOINT command is a
    PostgreSQL language extension.
-  
    Prev Up Next
    CALL Home CLOSE
    
\ No newline at end of file
+
    Prev Up Next
    CALL Home CLOSE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-close.html postgresql-13-13.12/doc/src/sgml/html/sql-close.html --- postgresql-13-13.11/doc/src/sgml/html/sql-close.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-close.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CLOSE
    CLOSE
    Prev UpSQL CommandsHome Next

    CLOSE

    CLOSE — close a cursor

    Synopsis

    +CLOSE
    CLOSE
    Prev UpSQL CommandsHome Next
    CLOSE
    CLOSE — close a cursor
    Synopsis
     CLOSE { name | ALL }
 
    Description
    
    CLOSE frees the resources associated with an open cursor.
@@ -39,4 +39,4 @@
    CLOSE is fully conforming with the SQL
    standard. CLOSE ALL is a PostgreSQL
    extension.
-  
    See Also
    DECLARE, FETCH, MOVE
    Prev Up Next
    CHECKPOINT Home CLUSTER
    
\ No newline at end of file
+

    See Also

    DECLARE, FETCH, MOVE
    Prev Up Next
    CHECKPOINT Home CLUSTER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-cluster.html postgresql-13-13.12/doc/src/sgml/html/sql-cluster.html --- postgresql-13-13.11/doc/src/sgml/html/sql-cluster.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-cluster.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CLUSTER
    CLUSTER
    Prev UpSQL CommandsHome Next

    CLUSTER

    CLUSTER — cluster a table according to an index

    Synopsis

    +CLUSTER
    CLUSTER
    Prev UpSQL CommandsHome Next
    CLUSTER
    CLUSTER — cluster a table according to an index
    Synopsis
     CLUSTER [VERBOSE] table_name [ USING index_name ]
 CLUSTER [VERBOSE]
 
    Description
    
@@ -114,4 +114,4 @@

    is also supported for compatibility with pre-8.3 PostgreSQL versions. -

    See Also

    clusterdb
    Prev Up Next
    CLOSE Home COMMENT
    \ No newline at end of file +

    See Also

    clusterdb
    Prev Up Next
    CLOSE Home COMMENT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-commands.html postgresql-13-13.12/doc/src/sgml/html/sql-commands.html --- postgresql-13-13.11/doc/src/sgml/html/sql-commands.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-commands.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SQL Commands
    SQL Commands
    Prev UpPart VI. ReferenceHome Next

    SQL Commands

    +SQL Commands

    SQL Commands
    Prev UpPart VI. ReferenceHome Next

    SQL Commands

    This part contains reference information for the SQL commands supported by PostgreSQL. By “SQL” the @@ -16,4 +16,4 @@ change the definition of an extended statistics object

    ALTER SUBSCRIPTION — change the definition of a subscription
    ALTER SYSTEM — change a server configuration parameter
    ALTER TABLE — change the definition of a table
    ALTER TABLESPACE — change the definition of a tablespace
    ALTER TEXT SEARCH CONFIGURATION — change the definition of a text search configuration
    ALTER TEXT SEARCH DICTIONARY — change the definition of a text search dictionary
    ALTER TEXT SEARCH PARSER — change the definition of a text search parser
    ALTER TEXT SEARCH TEMPLATE — change the definition of a text search template
    ALTER TRIGGER — change the definition of a trigger
    ALTER TYPE — change the definition of a type -
    ALTER USER — change a database role
    ALTER USER MAPPING — change the definition of a user mapping
    ALTER VIEW — change the definition of a view
    ANALYZE — collect statistics about a database
    BEGIN — start a transaction block
    CALL — invoke a procedure
    CHECKPOINT — force a write-ahead log checkpoint
    CLOSE — close a cursor
    CLUSTER — cluster a table according to an index
    COMMENT — define or change the comment of an object
    COMMIT — commit the current transaction
    COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit
    COPY — copy data between a file and a table
    CREATE ACCESS METHOD — define a new access method
    CREATE AGGREGATE — define a new aggregate function
    CREATE CAST — define a new cast
    CREATE COLLATION — define a new collation
    CREATE CONVERSION — define a new encoding conversion
    CREATE DATABASE — create a new database
    CREATE DOMAIN — define a new domain
    CREATE EVENT TRIGGER — define a new event trigger
    CREATE EXTENSION — install an extension
    CREATE FOREIGN DATA WRAPPER — define a new foreign-data wrapper
    CREATE FOREIGN TABLE — define a new foreign table
    CREATE FUNCTION — define a new function
    CREATE GROUP — define a new database role
    CREATE INDEX — define a new index
    CREATE LANGUAGE — define a new procedural language
    CREATE MATERIALIZED VIEW — define a new materialized view
    CREATE OPERATOR — define a new operator
    CREATE OPERATOR CLASS — define a new operator class
    CREATE OPERATOR FAMILY — define a new operator family
    CREATE POLICY — define a new row level security policy for a table
    CREATE PROCEDURE — define a new procedure
    CREATE PUBLICATION — define a new publication
    CREATE ROLE — define a new database role
    CREATE RULE — define a new rewrite rule
    CREATE SCHEMA — define a new schema
    CREATE SEQUENCE — define a new sequence generator
    CREATE SERVER — define a new foreign server
    CREATE STATISTICS — define extended statistics
    CREATE SUBSCRIPTION — define a new subscription
    CREATE TABLE — define a new table
    CREATE TABLE AS — define a new table from the results of a query
    CREATE TABLESPACE — define a new tablespace
    CREATE TEXT SEARCH CONFIGURATION — define a new text search configuration
    CREATE TEXT SEARCH DICTIONARY — define a new text search dictionary
    CREATE TEXT SEARCH PARSER — define a new text search parser
    CREATE TEXT SEARCH TEMPLATE — define a new text search template
    CREATE TRANSFORM — define a new transform
    CREATE TRIGGER — define a new trigger
    CREATE TYPE — define a new data type
    CREATE USER — define a new database role
    CREATE USER MAPPING — define a new mapping of a user to a foreign server
    CREATE VIEW — define a new view
    DEALLOCATE — deallocate a prepared statement
    DECLARE — define a cursor
    DELETE — delete rows of a table
    DISCARD — discard session state
    DO — execute an anonymous code block
    DROP ACCESS METHOD — remove an access method
    DROP AGGREGATE — remove an aggregate function
    DROP CAST — remove a cast
    DROP COLLATION — remove a collation
    DROP CONVERSION — remove a conversion
    DROP DATABASE — remove a database
    DROP DOMAIN — remove a domain
    DROP EVENT TRIGGER — remove an event trigger
    DROP EXTENSION — remove an extension
    DROP FOREIGN DATA WRAPPER — remove a foreign-data wrapper
    DROP FOREIGN TABLE — remove a foreign table
    DROP FUNCTION — remove a function
    DROP GROUP — remove a database role
    DROP INDEX — remove an index
    DROP LANGUAGE — remove a procedural language
    DROP MATERIALIZED VIEW — remove a materialized view
    DROP OPERATOR — remove an operator
    DROP OPERATOR CLASS — remove an operator class
    DROP OPERATOR FAMILY — remove an operator family
    DROP OWNED — remove database objects owned by a database role
    DROP POLICY — remove a row level security policy from a table
    DROP PROCEDURE — remove a procedure
    DROP PUBLICATION — remove a publication
    DROP ROLE — remove a database role
    DROP ROUTINE — remove a routine
    DROP RULE — remove a rewrite rule
    DROP SCHEMA — remove a schema
    DROP SEQUENCE — remove a sequence
    DROP SERVER — remove a foreign server descriptor
    DROP STATISTICS — remove extended statistics
    DROP SUBSCRIPTION — remove a subscription
    DROP TABLE — remove a table
    DROP TABLESPACE — remove a tablespace
    DROP TEXT SEARCH CONFIGURATION — remove a text search configuration
    DROP TEXT SEARCH DICTIONARY — remove a text search dictionary
    DROP TEXT SEARCH PARSER — remove a text search parser
    DROP TEXT SEARCH TEMPLATE — remove a text search template
    DROP TRANSFORM — remove a transform
    DROP TRIGGER — remove a trigger
    DROP TYPE — remove a data type
    DROP USER — remove a database role
    DROP USER MAPPING — remove a user mapping for a foreign server
    DROP VIEW — remove a view
    END — commit the current transaction
    EXECUTE — execute a prepared statement
    EXPLAIN — show the execution plan of a statement
    FETCH — retrieve rows from a query using a cursor
    GRANT — define access privileges
    IMPORT FOREIGN SCHEMA — import table definitions from a foreign server
    INSERT — create new rows in a table
    LISTEN — listen for a notification
    LOAD — load a shared library file
    LOCK — lock a table
    MOVE — position a cursor
    NOTIFY — generate a notification
    PREPARE — prepare a statement for execution
    PREPARE TRANSACTION — prepare the current transaction for two-phase commit
    REASSIGN OWNED — change the ownership of database objects owned by a database role
    REFRESH MATERIALIZED VIEW — replace the contents of a materialized view
    REINDEX — rebuild indexes
    RELEASE SAVEPOINT — destroy a previously defined savepoint
    RESET — restore the value of a run-time parameter to the default value
    REVOKE — remove access privileges
    ROLLBACK — abort the current transaction
    ROLLBACK PREPARED — cancel a transaction that was earlier prepared for two-phase commit
    ROLLBACK TO SAVEPOINT — roll back to a savepoint
    SAVEPOINT — define a new savepoint within the current transaction
    SECURITY LABEL — define or change a security label applied to an object
    SELECT — retrieve rows from a table or view
    SELECT INTO — define a new table from the results of a query
    SET — change a run-time parameter
    SET CONSTRAINTS — set constraint check timing for the current transaction
    SET ROLE — set the current user identifier of the current session
    SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session
    SET TRANSACTION — set the characteristics of the current transaction
    SHOW — show the value of a run-time parameter
    START TRANSACTION — start a transaction block
    TRUNCATE — empty a table or set of tables
    UNLISTEN — stop listening for a notification
    UPDATE — update rows of a table
    VACUUM — garbage-collect and optionally analyze a database
    VALUES — compute a set of rows
    Prev Up Next
    Part VI. Reference Home ABORT
    \ No newline at end of file +
    ALTER USER — change a database role
    ALTER USER MAPPING — change the definition of a user mapping
    ALTER VIEW — change the definition of a view
    ANALYZE — collect statistics about a database
    BEGIN — start a transaction block
    CALL — invoke a procedure
    CHECKPOINT — force a write-ahead log checkpoint
    CLOSE — close a cursor
    CLUSTER — cluster a table according to an index
    COMMENT — define or change the comment of an object
    COMMIT — commit the current transaction
    COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit
    COPY — copy data between a file and a table
    CREATE ACCESS METHOD — define a new access method
    CREATE AGGREGATE — define a new aggregate function
    CREATE CAST — define a new cast
    CREATE COLLATION — define a new collation
    CREATE CONVERSION — define a new encoding conversion
    CREATE DATABASE — create a new database
    CREATE DOMAIN — define a new domain
    CREATE EVENT TRIGGER — define a new event trigger
    CREATE EXTENSION — install an extension
    CREATE FOREIGN DATA WRAPPER — define a new foreign-data wrapper
    CREATE FOREIGN TABLE — define a new foreign table
    CREATE FUNCTION — define a new function
    CREATE GROUP — define a new database role
    CREATE INDEX — define a new index
    CREATE LANGUAGE — define a new procedural language
    CREATE MATERIALIZED VIEW — define a new materialized view
    CREATE OPERATOR — define a new operator
    CREATE OPERATOR CLASS — define a new operator class
    CREATE OPERATOR FAMILY — define a new operator family
    CREATE POLICY — define a new row level security policy for a table
    CREATE PROCEDURE — define a new procedure
    CREATE PUBLICATION — define a new publication
    CREATE ROLE — define a new database role
    CREATE RULE — define a new rewrite rule
    CREATE SCHEMA — define a new schema
    CREATE SEQUENCE — define a new sequence generator
    CREATE SERVER — define a new foreign server
    CREATE STATISTICS — define extended statistics
    CREATE SUBSCRIPTION — define a new subscription
    CREATE TABLE — define a new table
    CREATE TABLE AS — define a new table from the results of a query
    CREATE TABLESPACE — define a new tablespace
    CREATE TEXT SEARCH CONFIGURATION — define a new text search configuration
    CREATE TEXT SEARCH DICTIONARY — define a new text search dictionary
    CREATE TEXT SEARCH PARSER — define a new text search parser
    CREATE TEXT SEARCH TEMPLATE — define a new text search template
    CREATE TRANSFORM — define a new transform
    CREATE TRIGGER — define a new trigger
    CREATE TYPE — define a new data type
    CREATE USER — define a new database role
    CREATE USER MAPPING — define a new mapping of a user to a foreign server
    CREATE VIEW — define a new view
    DEALLOCATE — deallocate a prepared statement
    DECLARE — define a cursor
    DELETE — delete rows of a table
    DISCARD — discard session state
    DO — execute an anonymous code block
    DROP ACCESS METHOD — remove an access method
    DROP AGGREGATE — remove an aggregate function
    DROP CAST — remove a cast
    DROP COLLATION — remove a collation
    DROP CONVERSION — remove a conversion
    DROP DATABASE — remove a database
    DROP DOMAIN — remove a domain
    DROP EVENT TRIGGER — remove an event trigger
    DROP EXTENSION — remove an extension
    DROP FOREIGN DATA WRAPPER — remove a foreign-data wrapper
    DROP FOREIGN TABLE — remove a foreign table
    DROP FUNCTION — remove a function
    DROP GROUP — remove a database role
    DROP INDEX — remove an index
    DROP LANGUAGE — remove a procedural language
    DROP MATERIALIZED VIEW — remove a materialized view
    DROP OPERATOR — remove an operator
    DROP OPERATOR CLASS — remove an operator class
    DROP OPERATOR FAMILY — remove an operator family
    DROP OWNED — remove database objects owned by a database role
    DROP POLICY — remove a row level security policy from a table
    DROP PROCEDURE — remove a procedure
    DROP PUBLICATION — remove a publication
    DROP ROLE — remove a database role
    DROP ROUTINE — remove a routine
    DROP RULE — remove a rewrite rule
    DROP SCHEMA — remove a schema
    DROP SEQUENCE — remove a sequence
    DROP SERVER — remove a foreign server descriptor
    DROP STATISTICS — remove extended statistics
    DROP SUBSCRIPTION — remove a subscription
    DROP TABLE — remove a table
    DROP TABLESPACE — remove a tablespace
    DROP TEXT SEARCH CONFIGURATION — remove a text search configuration
    DROP TEXT SEARCH DICTIONARY — remove a text search dictionary
    DROP TEXT SEARCH PARSER — remove a text search parser
    DROP TEXT SEARCH TEMPLATE — remove a text search template
    DROP TRANSFORM — remove a transform
    DROP TRIGGER — remove a trigger
    DROP TYPE — remove a data type
    DROP USER — remove a database role
    DROP USER MAPPING — remove a user mapping for a foreign server
    DROP VIEW — remove a view
    END — commit the current transaction
    EXECUTE — execute a prepared statement
    EXPLAIN — show the execution plan of a statement
    FETCH — retrieve rows from a query using a cursor
    GRANT — define access privileges
    IMPORT FOREIGN SCHEMA — import table definitions from a foreign server
    INSERT — create new rows in a table
    LISTEN — listen for a notification
    LOAD — load a shared library file
    LOCK — lock a table
    MOVE — position a cursor
    NOTIFY — generate a notification
    PREPARE — prepare a statement for execution
    PREPARE TRANSACTION — prepare the current transaction for two-phase commit
    REASSIGN OWNED — change the ownership of database objects owned by a database role
    REFRESH MATERIALIZED VIEW — replace the contents of a materialized view
    REINDEX — rebuild indexes
    RELEASE SAVEPOINT — destroy a previously defined savepoint
    RESET — restore the value of a run-time parameter to the default value
    REVOKE — remove access privileges
    ROLLBACK — abort the current transaction
    ROLLBACK PREPARED — cancel a transaction that was earlier prepared for two-phase commit
    ROLLBACK TO SAVEPOINT — roll back to a savepoint
    SAVEPOINT — define a new savepoint within the current transaction
    SECURITY LABEL — define or change a security label applied to an object
    SELECT — retrieve rows from a table or view
    SELECT INTO — define a new table from the results of a query
    SET — change a run-time parameter
    SET CONSTRAINTS — set constraint check timing for the current transaction
    SET ROLE — set the current user identifier of the current session
    SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session
    SET TRANSACTION — set the characteristics of the current transaction
    SHOW — show the value of a run-time parameter
    START TRANSACTION — start a transaction block
    TRUNCATE — empty a table or set of tables
    UNLISTEN — stop listening for a notification
    UPDATE — update rows of a table
    VACUUM — garbage-collect and optionally analyze a database
    VALUES — compute a set of rows
    Prev Up Next
    Part VI. Reference Home ABORT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-comment.html postgresql-13-13.12/doc/src/sgml/html/sql-comment.html --- postgresql-13-13.11/doc/src/sgml/html/sql-comment.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-comment.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -COMMENT
    COMMENT
    Prev UpSQL CommandsHome Next

    COMMENT

    COMMENT — define or change the comment of an object

    Synopsis

    +COMMENT
    COMMENT
    Prev UpSQL CommandsHome Next
    COMMENT
    COMMENT — define or change the comment of an object
    Synopsis
     COMMENT ON
 {
   ACCESS METHOD object_name |
@@ -197,4 +197,4 @@
 COMMENT ON VIEW my_view IS 'View of departmental costs';
 
    Compatibility
    
    There is no COMMENT command in the SQL standard.
-  
    Prev Up Next
    CLUSTER Home COMMIT
    
\ No newline at end of file
+
    Prev Up Next
    CLUSTER Home COMMIT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-commit-prepared.html postgresql-13-13.12/doc/src/sgml/html/sql-commit-prepared.html --- postgresql-13-13.11/doc/src/sgml/html/sql-commit-prepared.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-commit-prepared.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -COMMIT PREPARED
    COMMIT PREPARED
    Prev UpSQL CommandsHome Next

    COMMIT PREPARED

    COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit

    Synopsis

    +COMMIT PREPARED
    COMMIT PREPARED
    Prev UpSQL CommandsHome Next
    COMMIT PREPARED
    COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit
    Synopsis
     COMMIT PREPARED transaction_id
 
    Description
    
    COMMIT PREPARED commits a transaction that is in
@@ -30,4 +30,4 @@
    external transaction management systems, some of which are covered by
    standards (such as X/Open XA), but the SQL side of those systems is not
    standardized.
-  
    Prev Up Next
    COMMIT Home COPY
    
\ No newline at end of file
+
    Prev Up Next
    COMMIT Home COPY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-commit.html postgresql-13-13.12/doc/src/sgml/html/sql-commit.html --- postgresql-13-13.11/doc/src/sgml/html/sql-commit.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-commit.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -COMMIT
    COMMIT
    Prev UpSQL CommandsHome Next

    COMMIT

    COMMIT — commit the current transaction

    Synopsis

    +COMMIT
    COMMIT
    Prev UpSQL CommandsHome Next
    COMMIT
    COMMIT — commit the current transaction
    Synopsis
     COMMIT [ WORK | TRANSACTION ] [ AND [ NO ] CHAIN ]
 
    Description
    
    COMMIT commits the current transaction. All
@@ -25,4 +25,4 @@

    Compatibility

    The command COMMIT conforms to the SQL standard. The form COMMIT TRANSACTION is a PostgreSQL extension. -

    See Also

    BEGIN, ROLLBACK
    Prev Up Next
    COMMENT Home COMMIT PREPARED
    \ No newline at end of file +

    See Also

    BEGIN, ROLLBACK
    Prev Up Next
    COMMENT Home COMMIT PREPARED
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-copy.html postgresql-13-13.12/doc/src/sgml/html/sql-copy.html --- postgresql-13-13.11/doc/src/sgml/html/sql-copy.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-copy.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -COPY
    COPY
    Prev UpSQL CommandsHome Next

    COPY

    COPY — copy data between a file and a table

    Synopsis

    +COPY
    COPY
    Prev UpSQL CommandsHome Next
    COPY
    COPY — copy data between a file and a table
    Synopsis
     COPY table_name [ ( column_name [, ...] ) ]
     FROM { 'filename' | PROGRAM 'command' | STDIN }
     [ [ WITH ] ( option [, ...] ) ]
@@ -626,4 +626,4 @@
     TO { 'filename' | STDOUT }
     [ [USING] DELIMITERS 'delimiter_character' ]
     [ WITH NULL AS 'null_string' ]
-
    Prev Up Next
    COMMIT PREPARED Home CREATE ACCESS METHOD
    
\ No newline at end of file
+
    Prev Up Next
    COMMIT PREPARED Home CREATE ACCESS METHOD
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-create-access-method.html postgresql-13-13.12/doc/src/sgml/html/sql-create-access-method.html --- postgresql-13-13.11/doc/src/sgml/html/sql-create-access-method.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-create-access-method.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE ACCESS METHOD
    CREATE ACCESS METHOD
    Prev UpSQL CommandsHome Next

    CREATE ACCESS METHOD

    CREATE ACCESS METHOD — define a new access method

    Synopsis

    +CREATE ACCESS METHOD
    CREATE ACCESS METHOD
    Prev UpSQL CommandsHome Next
    CREATE ACCESS METHOD
    CREATE ACCESS METHOD — define a new access method
    Synopsis
     CREATE ACCESS METHOD name
     TYPE access_method_type
     HANDLER handler_function
@@ -36,4 +36,4 @@
 
    Compatibility
    
    CREATE ACCESS METHOD is a
    PostgreSQL extension.
-  
    Prev Up Next
    COPY Home CREATE AGGREGATE
    
\ No newline at end of file
+
    Prev Up Next
    COPY Home CREATE AGGREGATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createaggregate.html postgresql-13-13.12/doc/src/sgml/html/sql-createaggregate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createaggregate.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createaggregate.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE AGGREGATE
    CREATE AGGREGATE
    Prev UpSQL CommandsHome Next

    CREATE AGGREGATE

    CREATE AGGREGATE — define a new aggregate function

    Synopsis

    +CREATE AGGREGATE
    CREATE AGGREGATE
    Prev UpSQL CommandsHome Next
    CREATE AGGREGATE
    CREATE AGGREGATE — define a new aggregate function
    Synopsis
     CREATE [ OR REPLACE ] AGGREGATE name ( [ argmode ] [ argname ] arg_data_type [ , ... ] ) (
     SFUNC = sfunc,
     STYPE = state_data_type
@@ -507,4 +507,4 @@
    CREATE AGGREGATE is a
    PostgreSQL language extension.  The SQL
    standard does not provide for user-defined aggregate functions.
-  
    Prev Up Next
    CREATE ACCESS METHOD Home CREATE CAST
    
\ No newline at end of file
+
    Prev Up Next
    CREATE ACCESS METHOD Home CREATE CAST
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createcast.html postgresql-13-13.12/doc/src/sgml/html/sql-createcast.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createcast.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createcast.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE CAST
    CREATE CAST
    Prev UpSQL CommandsHome Next

    CREATE CAST

    CREATE CAST — define a new cast

    Synopsis

    +CREATE CAST
    CREATE CAST
    Prev UpSQL CommandsHome Next
    CREATE CAST
    CREATE CAST — define a new cast
    Synopsis
     CREATE CAST (source_type AS target_type)
     WITH FUNCTION function_name [ (argument_type [, ...]) ]
     [ AS ASSIGNMENT | AS IMPLICIT ]
@@ -253,4 +253,4 @@
    CREATE FUNCTION,
    CREATE TYPE,
    DROP CAST
-  
    Prev Up Next
    CREATE AGGREGATE Home CREATE COLLATION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE AGGREGATE Home CREATE COLLATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createcollation.html postgresql-13-13.12/doc/src/sgml/html/sql-createcollation.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createcollation.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createcollation.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE COLLATION
    CREATE COLLATION
    Prev UpSQL CommandsHome Next

    CREATE COLLATION

    CREATE COLLATION — define a new collation

    Synopsis

    +CREATE COLLATION
    CREATE COLLATION
    Prev UpSQL CommandsHome Next
    CREATE COLLATION
    CREATE COLLATION — define a new collation
    Synopsis
     CREATE COLLATION [ IF NOT EXISTS ] name (
     [ LOCALE = locale, ]
     [ LC_COLLATE = lc_collate, ]
@@ -106,4 +106,4 @@
    standard, but it is limited to copying an existing collation.  The
    syntax to create a new collation is
    a PostgreSQL extension.
-  
    Prev Up Next
    CREATE CAST Home CREATE CONVERSION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE CAST Home CREATE CONVERSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createconversion.html postgresql-13-13.12/doc/src/sgml/html/sql-createconversion.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createconversion.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createconversion.html 2023-08-07 20:32:22.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE CONVERSION
    CREATE CONVERSION
    Prev UpSQL CommandsHome Next

    CREATE CONVERSION

    CREATE CONVERSION — define a new encoding conversion

    Synopsis

    +CREATE CONVERSION
    CREATE CONVERSION
    Prev UpSQL CommandsHome Next
    CREATE CONVERSION
    CREATE CONVERSION — define a new encoding conversion
    Synopsis
     CREATE [ DEFAULT ] CONVERSION name
     FOR source_encoding TO dest_encoding FROM function_name
 
    Description
    
@@ -63,4 +63,4 @@
     There is no CREATE CONVERSION
     statement in the SQL standard, but a CREATE TRANSLATION
     statement that is very similar in purpose and syntax.
-  
    Prev Up Next
    CREATE COLLATION Home CREATE DATABASE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE COLLATION Home CREATE DATABASE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createdatabase.html postgresql-13-13.12/doc/src/sgml/html/sql-createdatabase.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createdatabase.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createdatabase.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE DATABASE
    CREATE DATABASE
    Prev UpSQL CommandsHome Next

    CREATE DATABASE

    CREATE DATABASE — create a new database

    Synopsis

    +CREATE DATABASE
    CREATE DATABASE
    Prev UpSQL CommandsHome Next
    CREATE DATABASE
    CREATE DATABASE — create a new database
    Synopsis
     CREATE DATABASE name
     [ WITH ] [ OWNER [=] user_name ]
            [ TEMPLATE [=] template ]
@@ -188,4 +188,4 @@
    There is no CREATE DATABASE statement in the SQL
    standard.  Databases are equivalent to catalogs, whose creation is
    implementation-defined.
-  
    Prev Up Next
    CREATE CONVERSION Home CREATE DOMAIN
    
\ No newline at end of file
+
    Prev Up Next
    CREATE CONVERSION Home CREATE DOMAIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createdomain.html postgresql-13-13.12/doc/src/sgml/html/sql-createdomain.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createdomain.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createdomain.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE DOMAIN
    CREATE DOMAIN
    Prev UpSQL CommandsHome Next

    CREATE DOMAIN

    CREATE DOMAIN — define a new domain

    Synopsis

    +CREATE DOMAIN
    CREATE DOMAIN
    Prev UpSQL CommandsHome Next
    CREATE DOMAIN
    CREATE DOMAIN — define a new domain
    Synopsis
     CREATE DOMAIN name [ AS ] data_type
     [ COLLATE collation ]
     [ DEFAULT expression ]
@@ -145,4 +145,4 @@
 
    Compatibility
    
    The command CREATE DOMAIN conforms to the SQL
    standard.
-  
    Prev Up Next
    CREATE DATABASE Home CREATE EVENT TRIGGER
    
\ No newline at end of file
+
    Prev Up Next
    CREATE DATABASE Home CREATE EVENT TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createeventtrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-createeventtrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createeventtrigger.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createeventtrigger.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE EVENT TRIGGER
    CREATE EVENT TRIGGER
    Prev UpSQL CommandsHome Next

    CREATE EVENT TRIGGER

    CREATE EVENT TRIGGER — define a new event trigger

    Synopsis

    +CREATE EVENT TRIGGER
    CREATE EVENT TRIGGER
    Prev UpSQL CommandsHome Next
    CREATE EVENT TRIGGER
    CREATE EVENT TRIGGER — define a new event trigger
    Synopsis
     CREATE EVENT TRIGGER name
     ON event
     [ WHEN filter_variable IN (filter_value [, ... ]) [ AND ... ] ]
@@ -62,4 +62,4 @@
 
    Compatibility
    
    There is no CREATE EVENT TRIGGER statement in the
    SQL standard.
-  
    Prev Up Next
    CREATE DOMAIN Home CREATE EXTENSION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE DOMAIN Home CREATE EXTENSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createextension.html postgresql-13-13.12/doc/src/sgml/html/sql-createextension.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createextension.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createextension.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE EXTENSION
    CREATE EXTENSION
    Prev UpSQL CommandsHome Next

    CREATE EXTENSION

    CREATE EXTENSION — install an extension

    Synopsis

    +CREATE EXTENSION
    CREATE EXTENSION
    Prev UpSQL CommandsHome Next
    CREATE EXTENSION
    CREATE EXTENSION — install an extension
    Synopsis
     CREATE EXTENSION [ IF NOT EXISTS ] extension_name
     [ WITH ] [ SCHEMA schema_name ]
              [ VERSION version ]
@@ -126,4 +126,4 @@
   
    Compatibility
    
    CREATE EXTENSION is a PostgreSQL
    extension.
-  
    Prev Up Next
    CREATE EVENT TRIGGER Home CREATE FOREIGN DATA WRAPPER
    
\ No newline at end of file
+
    Prev Up Next
    CREATE EVENT TRIGGER Home CREATE FOREIGN DATA WRAPPER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createforeigndatawrapper.html postgresql-13-13.12/doc/src/sgml/html/sql-createforeigndatawrapper.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createforeigndatawrapper.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createforeigndatawrapper.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE FOREIGN DATA WRAPPER
    CREATE FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next

    CREATE FOREIGN DATA WRAPPER

    CREATE FOREIGN DATA WRAPPER — define a new foreign-data wrapper

    Synopsis

    +CREATE FOREIGN DATA WRAPPER
    CREATE FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next
    CREATE FOREIGN DATA WRAPPER
    CREATE FOREIGN DATA WRAPPER — define a new foreign-data wrapper
    Synopsis
     CREATE FOREIGN DATA WRAPPER name
     [ HANDLER handler_function | NO HANDLER ]
     [ VALIDATOR validator_function | NO VALIDATOR ]
@@ -74,4 +74,4 @@
   
    
    Note, however, that the SQL/MED functionality as a whole is not yet
    conforming.
-  
    Prev Up Next
    CREATE EXTENSION Home CREATE FOREIGN TABLE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE EXTENSION Home CREATE FOREIGN TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createforeigntable.html postgresql-13-13.12/doc/src/sgml/html/sql-createforeigntable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createforeigntable.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createforeigntable.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE FOREIGN TABLE
    CREATE FOREIGN TABLE
    Prev UpSQL CommandsHome Next

    CREATE FOREIGN TABLE

    CREATE FOREIGN TABLE — define a new foreign table

    Synopsis

    +CREATE FOREIGN TABLE
    CREATE FOREIGN TABLE
    Prev UpSQL CommandsHome Next
    CREATE FOREIGN TABLE
    CREATE FOREIGN TABLE — define a new foreign table
    Synopsis
     CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [
   { column_name data_type [ OPTIONS ( option 'value' [, ... ] ) ] [ COLLATE collation ] [ column_constraint [ ... ] ]
     | table_constraint }
@@ -241,4 +241,4 @@
    The ability to specify column default values is also
    a PostgreSQL extension.  Table inheritance, in the form
    defined by PostgreSQL, is nonstandard.
-  
    Prev Up Next
    CREATE FOREIGN DATA WRAPPER Home CREATE FUNCTION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE FOREIGN DATA WRAPPER Home CREATE FUNCTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createfunction.html postgresql-13-13.12/doc/src/sgml/html/sql-createfunction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createfunction.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createfunction.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE FUNCTION
    CREATE FUNCTION
    Prev UpSQL CommandsHome Next

    CREATE FUNCTION

    CREATE FUNCTION — define a new function

    Synopsis

    +CREATE FUNCTION
    CREATE FUNCTION
    Prev UpSQL CommandsHome Next
    CREATE FUNCTION
    CREATE FUNCTION — define a new function
    Synopsis
     CREATE [ OR REPLACE ] FUNCTION
     name ( [ [ argmode ] [ argname ] argtype [ { DEFAULT | = } default_expr ] [, ...] ] )
     [ RETURNS rettype
@@ -490,4 +490,4 @@
    For parameter defaults, the SQL standard specifies only the syntax with
    the DEFAULT key word.  The syntax
    with = is used in T-SQL and Firebird.
-  
    Prev Up Next
    CREATE FOREIGN TABLE Home CREATE GROUP
    
\ No newline at end of file
+
    Prev Up Next
    CREATE FOREIGN TABLE Home CREATE GROUP
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-creategroup.html postgresql-13-13.12/doc/src/sgml/html/sql-creategroup.html --- postgresql-13-13.11/doc/src/sgml/html/sql-creategroup.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-creategroup.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE GROUP
    CREATE GROUP
    Prev UpSQL CommandsHome Next

    CREATE GROUP

    CREATE GROUP — define a new database role

    Synopsis

    +CREATE GROUP
    CREATE GROUP
    Prev UpSQL CommandsHome Next
    CREATE GROUP
    CREATE GROUP — define a new database role
    Synopsis
     CREATE GROUP name [ [ WITH ] option [ ... ] ]
 
 where option can be:
@@ -26,4 +26,4 @@
   
    Compatibility
    
    There is no CREATE GROUP statement in the SQL
    standard.
-  
    See Also
    CREATE ROLE
    Prev Up Next
    CREATE FUNCTION Home CREATE INDEX
    
\ No newline at end of file
+

    See Also

    CREATE ROLE
    Prev Up Next
    CREATE FUNCTION Home CREATE INDEX
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createindex.html postgresql-13-13.12/doc/src/sgml/html/sql-createindex.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createindex.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createindex.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE INDEX
    CREATE INDEX
    Prev UpSQL CommandsHome Next

    CREATE INDEX

    CREATE INDEX — define a new index

    Synopsis

    +CREATE INDEX
    CREATE INDEX
    Prev UpSQL CommandsHome Next
    CREATE INDEX
    CREATE INDEX — define a new index
    Synopsis
     CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] name ] ON [ ONLY ] table_name [ USING method ]
     ( { column_name | ( expression ) } [ COLLATE collation ] [ opclass [ ( opclass_parameter = value [, ... ] ) ] ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] [, ...] )
     [ INCLUDE ( column_name [, ...] ) ]
@@ -536,4 +536,4 @@
    CREATE INDEX is a
    PostgreSQL language extension.  There
    are no provisions for indexes in the SQL standard.
-  
    Prev Up Next
    CREATE GROUP Home CREATE LANGUAGE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE GROUP Home CREATE LANGUAGE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createlanguage.html postgresql-13-13.12/doc/src/sgml/html/sql-createlanguage.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createlanguage.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createlanguage.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE LANGUAGE
    CREATE LANGUAGE
    Prev UpSQL CommandsHome Next

    CREATE LANGUAGE

    CREATE LANGUAGE — define a new procedural language

    Synopsis

    +CREATE LANGUAGE
    CREATE LANGUAGE
    Prev UpSQL CommandsHome Next
    CREATE LANGUAGE
    CREATE LANGUAGE — define a new procedural language
    Synopsis
     CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
     HANDLER call_handler [ INLINE inline_handler ] [ VALIDATOR valfunction ]
 CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
@@ -120,4 +120,4 @@
 
    Compatibility
    
    CREATE LANGUAGE is a
    PostgreSQL extension.
-  
    Prev Up Next
    CREATE INDEX Home CREATE MATERIALIZED VIEW
    
\ No newline at end of file
+
    Prev Up Next
    CREATE INDEX Home CREATE MATERIALIZED VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-creatematerializedview.html postgresql-13-13.12/doc/src/sgml/html/sql-creatematerializedview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-creatematerializedview.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-creatematerializedview.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE MATERIALIZED VIEW
    CREATE MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next

    CREATE MATERIALIZED VIEW

    CREATE MATERIALIZED VIEW — define a new materialized view

    Synopsis

    +CREATE MATERIALIZED VIEW
    CREATE MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next
    CREATE MATERIALIZED VIEW
    CREATE MATERIALIZED VIEW — define a new materialized view
    Synopsis
     CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] table_name
     [ (column_name [, ...] ) ]
     [ USING method ]
@@ -62,4 +62,4 @@
      
    Compatibility
    
    CREATE MATERIALIZED VIEW is a
    PostgreSQL extension.
-
    Prev Up Next
    CREATE LANGUAGE Home CREATE OPERATOR
    \ No newline at end of file +

    Prev Up Next
    CREATE LANGUAGE Home CREATE OPERATOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createopclass.html postgresql-13-13.12/doc/src/sgml/html/sql-createopclass.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createopclass.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createopclass.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE OPERATOR CLASS
    CREATE OPERATOR CLASS
    Prev UpSQL CommandsHome Next

    CREATE OPERATOR CLASS

    CREATE OPERATOR CLASS — define a new operator class

    Synopsis

    +CREATE OPERATOR CLASS
    CREATE OPERATOR CLASS
    Prev UpSQL CommandsHome Next
    CREATE OPERATOR CLASS
    CREATE OPERATOR CLASS — define a new operator class
    Synopsis
     CREATE OPERATOR CLASS name [ DEFAULT ] FOR TYPE data_type
   USING index_method [ FAMILY family_name ] AS
   {  OPERATOR strategy_number operator_name [ ( op_type, op_type ) ] [ FOR SEARCH | FOR ORDER BY sort_family_name ]
@@ -149,4 +149,4 @@
    PostgreSQL extension.  There is no
    CREATE OPERATOR CLASS statement in the SQL
    standard.
-  
    Prev Up Next
    CREATE OPERATOR Home CREATE OPERATOR FAMILY
    
\ No newline at end of file
+
    Prev Up Next
    CREATE OPERATOR Home CREATE OPERATOR FAMILY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createoperator.html postgresql-13-13.12/doc/src/sgml/html/sql-createoperator.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createoperator.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createoperator.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE OPERATOR
    CREATE OPERATOR
    Prev UpSQL CommandsHome Next

    CREATE OPERATOR

    CREATE OPERATOR — define a new operator

    Synopsis

    +CREATE OPERATOR
    CREATE OPERATOR
    Prev UpSQL CommandsHome Next
    CREATE OPERATOR
    CREATE OPERATOR — define a new operator
    Synopsis
     CREATE OPERATOR name (
     {FUNCTION|PROCEDURE} = function_name
     [, LEFTARG = left_type ] [, RIGHTARG = right_type ]
@@ -138,4 +138,4 @@
    CREATE OPERATOR is a
    PostgreSQL extension.  There are no
    provisions for user-defined operators in the SQL standard.
-  
    Prev Up Next
    CREATE MATERIALIZED VIEW Home CREATE OPERATOR CLASS
    
\ No newline at end of file
+
    Prev Up Next
    CREATE MATERIALIZED VIEW Home CREATE OPERATOR CLASS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createopfamily.html postgresql-13-13.12/doc/src/sgml/html/sql-createopfamily.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createopfamily.html 2023-05-08 21:34:03.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createopfamily.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE OPERATOR FAMILY
    CREATE OPERATOR FAMILY
    Prev UpSQL CommandsHome Next

    CREATE OPERATOR FAMILY

    CREATE OPERATOR FAMILY — define a new operator family

    Synopsis

    +CREATE OPERATOR FAMILY
    CREATE OPERATOR FAMILY
    Prev UpSQL CommandsHome Next
    CREATE OPERATOR FAMILY
    CREATE OPERATOR FAMILY — define a new operator family
    Synopsis
     CREATE OPERATOR FAMILY name USING index_method
 
    Description
    
    CREATE OPERATOR FAMILY creates a new operator family.
@@ -40,4 +40,4 @@
    PostgreSQL extension.  There is no
    CREATE OPERATOR FAMILY statement in the SQL
    standard.
-  
    Prev Up Next
    CREATE OPERATOR CLASS Home CREATE POLICY
    
\ No newline at end of file
+
    Prev Up Next
    CREATE OPERATOR CLASS Home CREATE POLICY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createpolicy.html postgresql-13-13.12/doc/src/sgml/html/sql-createpolicy.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createpolicy.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createpolicy.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE POLICY
    CREATE POLICY
    Prev UpSQL CommandsHome Next

    CREATE POLICY

    CREATE POLICY — define a new row level security policy for a table

    Synopsis

    +CREATE POLICY
    CREATE POLICY
    Prev UpSQL CommandsHome Next
    CREATE POLICY
    CREATE POLICY — define a new row level security policy for a table
    Synopsis
     CREATE POLICY name ON table_name
     [ AS { PERMISSIVE | RESTRICTIVE } ]
     [ FOR { ALL | SELECT | INSERT | UPDATE | DELETE } ]
@@ -345,4 +345,4 @@
   
    Compatibility
    
    CREATE POLICY is a PostgreSQL
    extension.
-  
    Prev Up Next
    CREATE OPERATOR FAMILY Home CREATE PROCEDURE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE OPERATOR FAMILY Home CREATE PROCEDURE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createprocedure.html postgresql-13-13.12/doc/src/sgml/html/sql-createprocedure.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createprocedure.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createprocedure.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE PROCEDURE
    CREATE PROCEDURE
    Prev UpSQL CommandsHome Next

    CREATE PROCEDURE

    CREATE PROCEDURE — define a new procedure

    Synopsis

    +CREATE PROCEDURE
    CREATE PROCEDURE
    Prev UpSQL CommandsHome Next
    CREATE PROCEDURE
    CREATE PROCEDURE — define a new procedure
    Synopsis
     CREATE [ OR REPLACE ] PROCEDURE
     name ( [ [ argmode ] [ argname ] argtype [ { DEFAULT | = } default_expr ] [, ...] ] )
   { LANGUAGE lang_name
@@ -169,4 +169,4 @@
    standard.  The PostgreSQL version is similar but
    not fully compatible.  For details see
    also CREATE FUNCTION.
-  
    Prev Up Next
    CREATE POLICY Home CREATE PUBLICATION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE POLICY Home CREATE PUBLICATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createpublication.html postgresql-13-13.12/doc/src/sgml/html/sql-createpublication.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createpublication.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createpublication.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE PUBLICATION
    CREATE PUBLICATION
    Prev UpSQL CommandsHome Next

    CREATE PUBLICATION

    CREATE PUBLICATION — define a new publication

    Synopsis

    +CREATE PUBLICATION
    CREATE PUBLICATION
    Prev UpSQL CommandsHome Next
    CREATE PUBLICATION
    CREATE PUBLICATION — define a new publication
    Synopsis
     CREATE PUBLICATION name
     [ FOR TABLE [ ONLY ] table_name [ * ] [, ...]
       | FOR ALL TABLES ]
@@ -116,4 +116,4 @@
 
    Compatibility
    
    CREATE PUBLICATION is a PostgreSQL
    extension.
-  
    Prev Up Next
    CREATE PROCEDURE Home CREATE ROLE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE PROCEDURE Home CREATE ROLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createrole.html postgresql-13-13.12/doc/src/sgml/html/sql-createrole.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createrole.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createrole.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE ROLE
    CREATE ROLE
    Prev UpSQL CommandsHome Next

    CREATE ROLE

    CREATE ROLE — define a new database role

    Synopsis

    +CREATE ROLE
    CREATE ROLE
    Prev UpSQL CommandsHome Next
    CREATE ROLE
    CREATE ROLE — define a new database role
    Synopsis
     CREATE ROLE name [ [ WITH ] option [ ... ] ]
 
 where option can be:
@@ -266,4 +266,4 @@
    The behavior specified by the SQL standard is most closely approximated
    by giving users the NOINHERIT attribute, while roles are
    given the INHERIT attribute.
-  
    Prev Up Next
    CREATE PUBLICATION Home CREATE RULE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE PUBLICATION Home CREATE RULE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createrule.html postgresql-13-13.12/doc/src/sgml/html/sql-createrule.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createrule.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createrule.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE RULE
    CREATE RULE
    Prev UpSQL CommandsHome Next

    CREATE RULE

    CREATE RULE — define a new rewrite rule

    Synopsis

    +CREATE RULE
    CREATE RULE
    Prev UpSQL CommandsHome Next
    CREATE RULE
    CREATE RULE — define a new rewrite rule
    Synopsis
     CREATE [ OR REPLACE ] RULE name AS ON event
     TO table_name [ WHERE condition ]
     DO [ ALSO | INSTEAD ] { NOTHING | command | ( command ; command ... ) }
@@ -171,4 +171,4 @@
    CREATE RULE is a
    PostgreSQL language extension, as is the
    entire query rewrite system.
-  
    Prev Up Next
    CREATE ROLE Home CREATE SCHEMA
    
\ No newline at end of file
+
    Prev Up Next
    CREATE ROLE Home CREATE SCHEMA
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createschema.html postgresql-13-13.12/doc/src/sgml/html/sql-createschema.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createschema.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createschema.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE SCHEMA
    CREATE SCHEMA
    Prev UpSQL CommandsHome Next

    CREATE SCHEMA

    CREATE SCHEMA — define a new schema

    Synopsis

    +CREATE SCHEMA
    CREATE SCHEMA
    Prev UpSQL CommandsHome Next
    CREATE SCHEMA
    CREATE SCHEMA — define a new schema
    Synopsis
     CREATE SCHEMA schema_name [ AUTHORIZATION role_specification ] [ schema_element [ ... ] ]
 CREATE SCHEMA AUTHORIZATION role_specification [ schema_element [ ... ] ]
 CREATE SCHEMA IF NOT EXISTS schema_name [ AUTHORIZATION role_specification ]
@@ -114,4 +114,4 @@
   
    
    The IF NOT EXISTS option is a
    PostgreSQL extension.
-  
    Prev Up Next
    CREATE RULE Home CREATE SEQUENCE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE RULE Home CREATE SEQUENCE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createsequence.html postgresql-13-13.12/doc/src/sgml/html/sql-createsequence.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createsequence.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createsequence.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE SEQUENCE
    CREATE SEQUENCE
    Prev UpSQL CommandsHome Next

    CREATE SEQUENCE

    CREATE SEQUENCE — define a new sequence generator

    Synopsis

    +CREATE SEQUENCE
    CREATE SEQUENCE
    Prev UpSQL CommandsHome Next
    CREATE SEQUENCE
    CREATE SEQUENCE — define a new sequence generator
    Synopsis
     CREATE [ TEMPORARY | TEMP ] SEQUENCE [ IF NOT EXISTS ] name
     [ AS data_type ]
     [ INCREMENT [ BY ] increment ]
@@ -198,4 +198,4 @@
      
  • 
       The OWNED BY clause is a PostgreSQL
       extension.
-
    • Prev Up Next
    CREATE SCHEMA Home CREATE SERVER
    \ No newline at end of file +

    Prev Up Next
    CREATE SCHEMA Home CREATE SERVER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createserver.html postgresql-13-13.12/doc/src/sgml/html/sql-createserver.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createserver.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createserver.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE SERVER
    CREATE SERVER
    Prev UpSQL CommandsHome Next

    CREATE SERVER

    CREATE SERVER — define a new foreign server

    Synopsis

    +CREATE SERVER
    CREATE SERVER
    Prev UpSQL CommandsHome Next
    CREATE SERVER
    CREATE SERVER — define a new foreign server
    Synopsis
     CREATE SERVER [ IF NOT EXISTS ] server_name [ TYPE 'server_type' ] [ VERSION 'server_version' ]
     FOREIGN DATA WRAPPER fdw_name
     [ OPTIONS ( option 'value' [, ... ] ) ]
@@ -50,4 +50,4 @@
    See postgres_fdw for more details.
   
    Compatibility
    
    CREATE SERVER conforms to ISO/IEC 9075-9 (SQL/MED).
-  
    Prev Up Next
    CREATE SEQUENCE Home CREATE STATISTICS
    
\ No newline at end of file
+
    Prev Up Next
    CREATE SEQUENCE Home CREATE STATISTICS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createstatistics.html postgresql-13-13.12/doc/src/sgml/html/sql-createstatistics.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createstatistics.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createstatistics.html 2023-08-07 20:32:23.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE STATISTICS
    CREATE STATISTICS
    Prev UpSQL CommandsHome Next

    CREATE STATISTICS

    CREATE STATISTICS — define extended statistics

    Synopsis

    +CREATE STATISTICS
    CREATE STATISTICS
    Prev UpSQL CommandsHome Next
    CREATE STATISTICS
    CREATE STATISTICS — define extended statistics
    Synopsis
     CREATE STATISTICS [ IF NOT EXISTS ] statistics_name
     [ ( statistics_kind [, ... ] ) ]
     ON column_name, column_name [, ...]
@@ -46,6 +46,10 @@
    You must be the owner of a table to create a statistics object
    reading it.  Once created, however, the ownership of the statistics
    object is independent of the underlying table(s).
+  
    
+   Extended statistics are not currently used by the planner for selectivity
+   estimations made for table joins.  This limitation will likely be removed
+   in a future version of PostgreSQL.
   
    Examples
    
    Create table t1 with two functionally dependent columns, i.e.,
    knowledge of a value in the first column is sufficient for determining the
@@ -110,4 +114,4 @@
    in the table, allowing it to generate better estimates in both cases.
   
    Compatibility
    
    There is no CREATE STATISTICS command in the SQL standard.
-  
    Prev Up Next
    CREATE SERVER Home CREATE SUBSCRIPTION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE SERVER Home CREATE SUBSCRIPTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createsubscription.html postgresql-13-13.12/doc/src/sgml/html/sql-createsubscription.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createsubscription.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createsubscription.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE SUBSCRIPTION
    CREATE SUBSCRIPTION
    Prev UpSQL CommandsHome Next

    CREATE SUBSCRIPTION

    CREATE SUBSCRIPTION — define a new subscription

    Synopsis

    +CREATE SUBSCRIPTION
    CREATE SUBSCRIPTION
    Prev UpSQL CommandsHome Next
    CREATE SUBSCRIPTION
    CREATE SUBSCRIPTION — define a new subscription
    Synopsis
     CREATE SUBSCRIPTION subscription_name
     CONNECTION 'conninfo'
     PUBLICATION publication_name [, ...]
@@ -129,4 +129,4 @@
 
    Compatibility
    
    CREATE SUBSCRIPTION is a PostgreSQL
    extension.
-  
    Prev Up Next
    CREATE STATISTICS Home CREATE TABLE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE STATISTICS Home CREATE TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtable.html postgresql-13-13.12/doc/src/sgml/html/sql-createtable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtable.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtable.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TABLE
    CREATE TABLE
    Prev UpSQL CommandsHome Next

    CREATE TABLE

    CREATE TABLE — define a new table

    Synopsis

    +CREATE TABLE
    CREATE TABLE
    Prev UpSQL CommandsHome Next
    CREATE TABLE
    CREATE TABLE — define a new table
    Synopsis
     CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] table_name ( [
   { column_name data_type [ COLLATE collation ] [ column_constraint [ ... ] ]
     | table_constraint
@@ -1413,4 +1413,4 @@
    
    PARTITION OF Clause
    
     The PARTITION OF clause is a
     PostgreSQL extension.
-
    Prev Up Next
    CREATE SUBSCRIPTION Home CREATE TABLE AS
    \ No newline at end of file +

    Prev Up Next
    CREATE SUBSCRIPTION Home CREATE TABLE AS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtableas.html postgresql-13-13.12/doc/src/sgml/html/sql-createtableas.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtableas.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtableas.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TABLE AS
    CREATE TABLE AS
    Prev UpSQL CommandsHome Next

    CREATE TABLE AS

    CREATE TABLE AS — define a new table from the results of a query

    Synopsis

    +CREATE TABLE AS
    CREATE TABLE AS
    Prev UpSQL CommandsHome Next
    CREATE TABLE AS
    CREATE TABLE AS — define a new table from the results of a query
    Synopsis
     CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] table_name
     [ (column_name [, ...] ) ]
     [ USING method ]
@@ -142,4 +142,4 @@
       The PostgreSQL concept of tablespaces is not
       part of the standard.  Hence, the clause TABLESPACE
       is an extension.
-
    Prev Up Next
    CREATE TABLE Home CREATE TABLESPACE
    \ No newline at end of file +

    Prev Up Next
    CREATE TABLE Home CREATE TABLESPACE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtablespace.html postgresql-13-13.12/doc/src/sgml/html/sql-createtablespace.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtablespace.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtablespace.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TABLESPACE
    CREATE TABLESPACE
    Prev UpSQL CommandsHome Next

    CREATE TABLESPACE

    CREATE TABLESPACE — define a new tablespace

    Synopsis

    +CREATE TABLESPACE
    CREATE TABLESPACE
    Prev UpSQL CommandsHome Next
    CREATE TABLESPACE
    CREATE TABLESPACE — define a new tablespace
    Synopsis
     CREATE TABLESPACE tablespace_name
     [ OWNER { new_owner | CURRENT_USER | SESSION_USER } ]
     LOCATION 'directory'
@@ -77,4 +77,4 @@
 
    Compatibility
    
    CREATE TABLESPACE is a PostgreSQL
    extension.
-  
    Prev Up Next
    CREATE TABLE AS Home CREATE TEXT SEARCH CONFIGURATION
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TABLE AS Home CREATE TEXT SEARCH CONFIGURATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtransform.html postgresql-13-13.12/doc/src/sgml/html/sql-createtransform.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtransform.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtransform.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TRANSFORM
    CREATE TRANSFORM
    Prev UpSQL CommandsHome Next

    CREATE TRANSFORM

    CREATE TRANSFORM — define a new transform

    Synopsis

    +CREATE TRANSFORM
    CREATE TRANSFORM
    Prev UpSQL CommandsHome Next
    CREATE TRANSFORM
    CREATE TRANSFORM — define a new transform
    Synopsis
     CREATE [ OR REPLACE ] TRANSFORM FOR type_name LANGUAGE lang_name (
     FROM SQL WITH FUNCTION from_sql_function_name [ (argument_type [, ...]) ],
     TO SQL WITH FUNCTION to_sql_function_name [ (argument_type [, ...]) ]
@@ -103,4 +103,4 @@
    CREATE LANGUAGE,
    CREATE TYPE,
    DROP TRANSFORM
-  
    Prev Up Next
    CREATE TEXT SEARCH TEMPLATE Home CREATE TRIGGER
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TEXT SEARCH TEMPLATE Home CREATE TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-createtrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtrigger.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtrigger.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TRIGGER
    CREATE TRIGGER
    Prev UpSQL CommandsHome Next

    CREATE TRIGGER

    CREATE TRIGGER — define a new trigger

    Synopsis

    +CREATE TRIGGER
    CREATE TRIGGER
    Prev UpSQL CommandsHome Next
    CREATE TRIGGER
    CREATE TRIGGER — define a new trigger
    Synopsis
     CREATE [ CONSTRAINT ] TRIGGER name { BEFORE | AFTER | INSTEAD OF } { event [ OR ... ] }
     ON table_name
     [ FROM referenced_table_name ]
@@ -435,4 +435,4 @@
    CREATE CONSTRAINT TRIGGER is a
    PostgreSQL extension of the SQL
    standard.
-  
    Prev Up Next
    CREATE TRANSFORM Home CREATE TYPE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TRANSFORM Home CREATE TYPE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtsconfig.html postgresql-13-13.12/doc/src/sgml/html/sql-createtsconfig.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtsconfig.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtsconfig.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TEXT SEARCH CONFIGURATION
    CREATE TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next

    CREATE TEXT SEARCH CONFIGURATION

    CREATE TEXT SEARCH CONFIGURATION — define a new text search configuration

    Synopsis

    +CREATE TEXT SEARCH CONFIGURATION
    CREATE TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next
    CREATE TEXT SEARCH CONFIGURATION
    CREATE TEXT SEARCH CONFIGURATION — define a new text search configuration
    Synopsis
     CREATE TEXT SEARCH CONFIGURATION name (
     PARSER = parser_name |
     COPY = source_config
@@ -37,4 +37,4 @@
   
    Compatibility
    
    There is no CREATE TEXT SEARCH CONFIGURATION statement
    in the SQL standard.
-  
    Prev Up Next
    CREATE TABLESPACE Home CREATE TEXT SEARCH DICTIONARY
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TABLESPACE Home CREATE TEXT SEARCH DICTIONARY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtsdictionary.html postgresql-13-13.12/doc/src/sgml/html/sql-createtsdictionary.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtsdictionary.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtsdictionary.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TEXT SEARCH DICTIONARY
    CREATE TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next

    CREATE TEXT SEARCH DICTIONARY

    CREATE TEXT SEARCH DICTIONARY — define a new text search dictionary

    Synopsis

    +CREATE TEXT SEARCH DICTIONARY
    CREATE TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next
    CREATE TEXT SEARCH DICTIONARY
    CREATE TEXT SEARCH DICTIONARY — define a new text search dictionary
    Synopsis
     CREATE TEXT SEARCH DICTIONARY name (
     TEMPLATE = template
     [, option = value [, ... ]]
@@ -44,4 +44,4 @@
 
    Compatibility
    
    There is no CREATE TEXT SEARCH DICTIONARY statement in
    the SQL standard.
-  
    Prev Up Next
    CREATE TEXT SEARCH CONFIGURATION Home CREATE TEXT SEARCH PARSER
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TEXT SEARCH CONFIGURATION Home CREATE TEXT SEARCH PARSER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtsparser.html postgresql-13-13.12/doc/src/sgml/html/sql-createtsparser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtsparser.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtsparser.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TEXT SEARCH PARSER
    CREATE TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next

    CREATE TEXT SEARCH PARSER

    CREATE TEXT SEARCH PARSER — define a new text search parser

    Synopsis

    +CREATE TEXT SEARCH PARSER
    CREATE TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next
    CREATE TEXT SEARCH PARSER
    CREATE TEXT SEARCH PARSER — define a new text search parser
    Synopsis
     CREATE TEXT SEARCH PARSER name (
     START = start_function ,
     GETTOKEN = gettoken_function ,
@@ -48,4 +48,4 @@
    There is no
    CREATE TEXT SEARCH PARSER statement in the SQL
    standard.
-  
    Prev Up Next
    CREATE TEXT SEARCH DICTIONARY Home CREATE TEXT SEARCH TEMPLATE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TEXT SEARCH DICTIONARY Home CREATE TEXT SEARCH TEMPLATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtstemplate.html postgresql-13-13.12/doc/src/sgml/html/sql-createtstemplate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtstemplate.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtstemplate.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TEXT SEARCH TEMPLATE
    CREATE TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next

    CREATE TEXT SEARCH TEMPLATE

    CREATE TEXT SEARCH TEMPLATE — define a new text search template

    Synopsis

    +CREATE TEXT SEARCH TEMPLATE
    CREATE TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next
    CREATE TEXT SEARCH TEMPLATE
    CREATE TEXT SEARCH TEMPLATE — define a new text search template
    Synopsis
     CREATE TEXT SEARCH TEMPLATE name (
     [ INIT = init_function , ]
     LEXIZE = lexize_function
@@ -42,4 +42,4 @@
    There is no
    CREATE TEXT SEARCH TEMPLATE statement in the SQL
    standard.
-  
    Prev Up Next
    CREATE TEXT SEARCH PARSER Home CREATE TRANSFORM
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TEXT SEARCH PARSER Home CREATE TRANSFORM
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createtype.html postgresql-13-13.12/doc/src/sgml/html/sql-createtype.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createtype.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createtype.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE TYPE
    CREATE TYPE
    Prev UpSQL CommandsHome Next

    CREATE TYPE

    CREATE TYPE — define a new data type

    Synopsis

    +CREATE TYPE
    CREATE TYPE
    Prev UpSQL CommandsHome Next
    CREATE TYPE
    CREATE TYPE — define a new data type
    Synopsis
     CREATE TYPE name AS
     ( [ attribute_name data_type [ COLLATE collation ] [, ... ] ] )
 
@@ -597,4 +597,4 @@
    The ability to create a composite type with zero attributes is
    a PostgreSQL-specific deviation from the
    standard (analogous to the same case in CREATE TABLE).
-  
    Prev Up Next
    CREATE TRIGGER Home CREATE USER
    
\ No newline at end of file
+
    Prev Up Next
    CREATE TRIGGER Home CREATE USER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createuser.html postgresql-13-13.12/doc/src/sgml/html/sql-createuser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createuser.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createuser.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE USER
    CREATE USER
    Prev UpSQL CommandsHome Next

    CREATE USER

    CREATE USER — define a new database role

    Synopsis

    +CREATE USER
    CREATE USER
    Prev UpSQL CommandsHome Next
    CREATE USER
    CREATE USER — define a new database role
    Synopsis
     CREATE USER name [ [ WITH ] option [ ... ] ]
 
 where option can be:
@@ -32,4 +32,4 @@
    The CREATE USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
-  
    See Also
    CREATE ROLE
    Prev Up Next
    CREATE TYPE Home CREATE USER MAPPING
    
\ No newline at end of file
+

    See Also

    CREATE ROLE
    Prev Up Next
    CREATE TYPE Home CREATE USER MAPPING
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createusermapping.html postgresql-13-13.12/doc/src/sgml/html/sql-createusermapping.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createusermapping.html 2023-05-08 21:34:04.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createusermapping.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE USER MAPPING
    CREATE USER MAPPING
    Prev UpSQL CommandsHome Next

    CREATE USER MAPPING

    CREATE USER MAPPING — define a new mapping of a user to a foreign server

    Synopsis

    +CREATE USER MAPPING
    CREATE USER MAPPING
    Prev UpSQL CommandsHome Next
    CREATE USER MAPPING
    CREATE USER MAPPING — define a new mapping of a user to a foreign server
    Synopsis
     CREATE USER MAPPING [ IF NOT EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC }
     SERVER server_name
     [ OPTIONS ( option 'value' [ , ... ] ) ]
@@ -39,4 +39,4 @@
 CREATE USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'secret');
 
    Compatibility
    
    CREATE USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED).
-  
    Prev Up Next
    CREATE USER Home CREATE VIEW
    
\ No newline at end of file
+
    Prev Up Next
    CREATE USER Home CREATE VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-createview.html postgresql-13-13.12/doc/src/sgml/html/sql-createview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-createview.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-createview.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -CREATE VIEW
    CREATE VIEW
    Prev UpSQL CommandsHome Next

    CREATE VIEW

    CREATE VIEW — define a new view

    Synopsis

    +CREATE VIEW
    CREATE VIEW
    Prev UpSQL CommandsHome Next
    CREATE VIEW
    CREATE VIEW — define a new view
    Synopsis
     CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] [ RECURSIVE ] VIEW name [ ( column_name [, ...] ) ]
     [ WITH ( view_option_name [= view_option_value] [, ... ] ) ]
     AS query
@@ -288,4 +288,4 @@
    PostgreSQL language extension.
    So is the concept of a temporary view.
    The WITH ( ... ) clause is an extension as well.
-  
    Prev Up Next
    CREATE USER MAPPING Home DEALLOCATE
    
\ No newline at end of file
+
    Prev Up Next
    CREATE USER MAPPING Home DEALLOCATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-deallocate.html postgresql-13-13.12/doc/src/sgml/html/sql-deallocate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-deallocate.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-deallocate.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DEALLOCATE
    DEALLOCATE
    Prev UpSQL CommandsHome Next

    DEALLOCATE

    DEALLOCATE — deallocate a prepared statement

    Synopsis

    +DEALLOCATE
    DEALLOCATE
    Prev UpSQL CommandsHome Next
    DEALLOCATE
    DEALLOCATE — deallocate a prepared statement
    Synopsis
     DEALLOCATE [ PREPARE ] { name | ALL }
 
    Description
    
    DEALLOCATE is used to deallocate a previously
@@ -16,4 +16,4 @@
      
    Compatibility
    
    The SQL standard includes a DEALLOCATE
    statement, but it is only for use in embedded SQL.
-  
    See Also
    EXECUTE, PREPARE
    Prev Up Next
    CREATE VIEW Home DECLARE
    \ No newline at end of file +

    See Also

    EXECUTE, PREPARE
    Prev Up Next
    CREATE VIEW Home DECLARE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-declare.html postgresql-13-13.12/doc/src/sgml/html/sql-declare.html --- postgresql-13-13.11/doc/src/sgml/html/sql-declare.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-declare.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DECLARE
    DECLARE
    Prev UpSQL CommandsHome Next

    DECLARE

    DECLARE — define a cursor

    Synopsis

    +DECLARE
    DECLARE
    Prev UpSQL CommandsHome Next
    DECLARE
    DECLARE — define a cursor
    Synopsis
     DECLARE name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
     CURSOR [ { WITH | WITHOUT } HOLD ] FOR query
 
    Description
    
@@ -191,4 +191,4 @@
   
    
    Binary cursors are a PostgreSQL
    extension.
-  
    See Also
    CLOSE, FETCH, MOVE
    Prev Up Next
    DEALLOCATE Home DELETE
    
\ No newline at end of file
+

    See Also

    CLOSE, FETCH, MOVE
    Prev Up Next
    DEALLOCATE Home DELETE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-delete.html postgresql-13-13.12/doc/src/sgml/html/sql-delete.html --- postgresql-13-13.11/doc/src/sgml/html/sql-delete.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-delete.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DELETE
    DELETE
    Prev UpSQL CommandsHome Next

    DELETE

    DELETE — delete rows of a table

    Synopsis

    +DELETE
    DELETE
    Prev UpSQL CommandsHome Next
    DELETE
    DELETE — delete rows of a table
    Synopsis
     [ WITH [ RECURSIVE ] with_query [, ...] ]
 DELETE FROM [ ONLY ] table_name [ * ] [ [ AS ] alias ]
     [ USING from_item [, ...] ]
@@ -142,4 +142,4 @@
    that the USING and RETURNING clauses
    are PostgreSQL extensions, as is the ability
    to use WITH with DELETE.
-  
    See Also
    TRUNCATE
    Prev Up Next
    DECLARE Home DISCARD
    
\ No newline at end of file
+

    See Also

    TRUNCATE
    Prev Up Next
    DECLARE Home DISCARD
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-discard.html postgresql-13-13.12/doc/src/sgml/html/sql-discard.html --- postgresql-13-13.11/doc/src/sgml/html/sql-discard.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-discard.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DISCARD
    DISCARD
    Prev UpSQL CommandsHome Next

    DISCARD

    DISCARD — discard session state

    Synopsis

    +DISCARD
    DISCARD
    Prev UpSQL CommandsHome Next
    DISCARD
    DISCARD — discard session state
    Synopsis
     DISCARD { ALL | PLANS | SEQUENCES | TEMPORARY | TEMP }
 
    Description
    
    DISCARD releases internal resources associated with a
@@ -38,4 +38,4 @@
     DISCARD ALL cannot be executed inside a transaction block.
    
    Compatibility
    
    DISCARD is a PostgreSQL extension.
-  
    Prev Up Next
    DELETE Home DO
    
\ No newline at end of file
+
    Prev Up Next
    DELETE Home DO
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-do.html postgresql-13-13.12/doc/src/sgml/html/sql-do.html --- postgresql-13-13.11/doc/src/sgml/html/sql-do.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-do.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DO
    DO
    Prev UpSQL CommandsHome Next

    DO

    DO — execute an anonymous code block

    Synopsis

    +DO
    DO
    Prev UpSQL CommandsHome Next
    DO
    DO — execute an anonymous code block
    Synopsis
     DO [ LANGUAGE lang_name ] code
 
    Description
    
    DO executes an anonymous code block, or in other
@@ -46,4 +46,4 @@
 END$$;

    Compatibility

    There is no DO statement in the SQL standard. -

    Prev Up Next
    DISCARD Home DROP ACCESS METHOD
    \ No newline at end of file +

    Prev Up Next
    DISCARD Home DROP ACCESS METHOD
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-drop-access-method.html postgresql-13-13.12/doc/src/sgml/html/sql-drop-access-method.html --- postgresql-13-13.11/doc/src/sgml/html/sql-drop-access-method.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-drop-access-method.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP ACCESS METHOD
    DROP ACCESS METHOD
    Prev UpSQL CommandsHome Next

    DROP ACCESS METHOD

    DROP ACCESS METHOD — remove an access method

    Synopsis

    +DROP ACCESS METHOD
    DROP ACCESS METHOD
    Prev UpSQL CommandsHome Next
    DROP ACCESS METHOD
    DROP ACCESS METHOD — remove an access method
    Synopsis
     DROP ACCESS METHOD [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP ACCESS METHOD removes an existing access method.
@@ -24,4 +24,4 @@

    Compatibility

    DROP ACCESS METHOD is a PostgreSQL extension. -

    Prev Up Next
    DO Home DROP AGGREGATE
    \ No newline at end of file +

    Prev Up Next
    DO Home DROP AGGREGATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-drop-owned.html postgresql-13-13.12/doc/src/sgml/html/sql-drop-owned.html --- postgresql-13-13.11/doc/src/sgml/html/sql-drop-owned.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-drop-owned.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP OWNED
    DROP OWNED
    Prev UpSQL CommandsHome Next

    DROP OWNED

    DROP OWNED — remove database objects owned by a database role

    Synopsis

    +DROP OWNED
    DROP OWNED
    Prev UpSQL CommandsHome Next
    DROP OWNED
    DROP OWNED — remove database objects owned by a database role
    Synopsis
     DROP OWNED BY { name | CURRENT_USER | SESSION_USER } [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP OWNED drops all the objects within the current
@@ -38,4 +38,4 @@
   
    Compatibility
    
    The DROP OWNED command is a
    PostgreSQL extension.
-  
    Prev Up Next
    DROP OPERATOR FAMILY Home DROP POLICY
    
\ No newline at end of file
+
    Prev Up Next
    DROP OPERATOR FAMILY Home DROP POLICY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropaggregate.html postgresql-13-13.12/doc/src/sgml/html/sql-dropaggregate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropaggregate.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropaggregate.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP AGGREGATE
    DROP AGGREGATE
    Prev UpSQL CommandsHome Next

    DROP AGGREGATE

    DROP AGGREGATE — remove an aggregate function

    Synopsis

    +DROP AGGREGATE
    DROP AGGREGATE
    Prev UpSQL CommandsHome Next
    DROP AGGREGATE
    DROP AGGREGATE — remove an aggregate function
    Synopsis
     DROP AGGREGATE [ IF EXISTS ] name ( aggregate_signature ) [, ...] [ CASCADE | RESTRICT ]
 
 where aggregate_signature is:
@@ -62,4 +62,4 @@
 
    Compatibility
    
    There is no DROP AGGREGATE statement in the SQL
    standard.
-  
    Prev Up Next
    DROP ACCESS METHOD Home DROP CAST
    
\ No newline at end of file
+
    Prev Up Next
    DROP ACCESS METHOD Home DROP CAST
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropcast.html postgresql-13-13.12/doc/src/sgml/html/sql-dropcast.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropcast.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropcast.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP CAST
    DROP CAST
    Prev UpSQL CommandsHome Next

    DROP CAST

    DROP CAST — remove a cast

    Synopsis

    +DROP CAST
    DROP CAST
    Prev UpSQL CommandsHome Next
    DROP CAST
    DROP CAST — remove a cast
    Synopsis
     DROP CAST [ IF EXISTS ] (source_type AS target_type) [ CASCADE | RESTRICT ]
 
    Description
    
    DROP CAST removes a previously defined cast.
@@ -23,4 +23,4 @@
 DROP CAST (text AS int);

    Compatibility

    The DROP CAST command conforms to the SQL standard. -

    See Also

    CREATE CAST
    Prev Up Next
    DROP AGGREGATE Home DROP COLLATION
    \ No newline at end of file +

    See Also

    CREATE CAST
    Prev Up Next
    DROP AGGREGATE Home DROP COLLATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropcollation.html postgresql-13-13.12/doc/src/sgml/html/sql-dropcollation.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropcollation.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropcollation.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP COLLATION
    DROP COLLATION
    Prev UpSQL CommandsHome Next

    DROP COLLATION

    DROP COLLATION — remove a collation

    Synopsis

    +DROP COLLATION
    DROP COLLATION
    Prev UpSQL CommandsHome Next
    DROP COLLATION
    DROP COLLATION — remove a collation
    Synopsis
     DROP COLLATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP COLLATION removes a previously defined collation.
@@ -25,4 +25,4 @@
    The DROP COLLATION command conforms to the
    SQL standard, apart from the IF
    EXISTS option, which is a PostgreSQL extension.
-  
    Prev Up Next
    DROP CAST Home DROP CONVERSION
    
\ No newline at end of file
+
    Prev Up Next
    DROP CAST Home DROP CONVERSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropconversion.html postgresql-13-13.12/doc/src/sgml/html/sql-dropconversion.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropconversion.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropconversion.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP CONVERSION
    DROP CONVERSION
    Prev UpSQL CommandsHome Next

    DROP CONVERSION

    DROP CONVERSION — remove a conversion

    Synopsis

    +DROP CONVERSION
    DROP CONVERSION
    Prev UpSQL CommandsHome Next
    DROP CONVERSION
    DROP CONVERSION — remove a conversion
    Synopsis
     DROP CONVERSION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP CONVERSION removes a previously defined conversion.
@@ -23,4 +23,4 @@
    goes along with the CREATE TRANSLATION statement
    that is similar to the CREATE CONVERSION
    statement in PostgreSQL.
-  
    Prev Up Next
    DROP COLLATION Home DROP DATABASE
    
\ No newline at end of file
+
    Prev Up Next
    DROP COLLATION Home DROP DATABASE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropdatabase.html postgresql-13-13.12/doc/src/sgml/html/sql-dropdatabase.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropdatabase.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropdatabase.html 2023-08-07 20:32:24.000000000 +0000 @@ -1,5 +1,5 @@ -DROP DATABASE
    DROP DATABASE
    Prev UpSQL CommandsHome Next

    DROP DATABASE

    DROP DATABASE — remove a database

    Synopsis

    +DROP DATABASE
    DROP DATABASE
    Prev UpSQL CommandsHome Next
    DROP DATABASE
    DROP DATABASE — remove a database
    Synopsis
     DROP DATABASE [ IF EXISTS ] name [ [ WITH ] ( option [, ...] ) ]
 
 where option can be:
@@ -41,4 +41,4 @@
    which is a wrapper around this command.
   
    Compatibility
    
    There is no DROP DATABASE statement in the SQL standard.
-  
    Prev Up Next
    DROP CONVERSION Home DROP DOMAIN
    
\ No newline at end of file
+
    Prev Up Next
    DROP CONVERSION Home DROP DOMAIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropdomain.html postgresql-13-13.12/doc/src/sgml/html/sql-dropdomain.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropdomain.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropdomain.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP DOMAIN
    DROP DOMAIN
    Prev UpSQL CommandsHome Next

    DROP DOMAIN

    DROP DOMAIN — remove a domain

    Synopsis

    +DROP DOMAIN
    DROP DOMAIN
    Prev UpSQL CommandsHome Next
    DROP DOMAIN
    DROP DOMAIN — remove a domain
    Synopsis
     DROP DOMAIN [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP DOMAIN removes a domain.  Only the owner of
@@ -26,4 +26,4 @@
    This command conforms to the SQL standard, except for the
    IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP DATABASE Home DROP EVENT TRIGGER
    
\ No newline at end of file
+
    Prev Up Next
    DROP DATABASE Home DROP EVENT TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropeventtrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-dropeventtrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropeventtrigger.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropeventtrigger.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP EVENT TRIGGER
    DROP EVENT TRIGGER
    Prev UpSQL CommandsHome Next

    DROP EVENT TRIGGER

    DROP EVENT TRIGGER — remove an event trigger

    Synopsis

    +DROP EVENT TRIGGER
    DROP EVENT TRIGGER
    Prev UpSQL CommandsHome Next
    DROP EVENT TRIGGER
    DROP EVENT TRIGGER — remove an event trigger
    Synopsis
     DROP EVENT TRIGGER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP EVENT TRIGGER removes an existing event trigger.
@@ -25,4 +25,4 @@

    Compatibility

    There is no DROP EVENT TRIGGER statement in the SQL standard. -

    Prev Up Next
    DROP DOMAIN Home DROP EXTENSION
    \ No newline at end of file +

    Prev Up Next
    DROP DOMAIN Home DROP EXTENSION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropextension.html postgresql-13-13.12/doc/src/sgml/html/sql-dropextension.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropextension.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropextension.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP EXTENSION
    DROP EXTENSION
    Prev UpSQL CommandsHome Next

    DROP EXTENSION

    DROP EXTENSION — remove an extension

    Synopsis

    +DROP EXTENSION
    DROP EXTENSION
    Prev UpSQL CommandsHome Next
    DROP EXTENSION
    DROP EXTENSION — remove an extension
    Synopsis
     DROP EXTENSION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP EXTENSION removes extensions from the database.
@@ -34,4 +34,4 @@
   
    Compatibility
    
    DROP EXTENSION is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP EVENT TRIGGER Home DROP FOREIGN DATA WRAPPER
    
\ No newline at end of file
+
    Prev Up Next
    DROP EVENT TRIGGER Home DROP FOREIGN DATA WRAPPER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropforeigndatawrapper.html postgresql-13-13.12/doc/src/sgml/html/sql-dropforeigndatawrapper.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropforeigndatawrapper.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropforeigndatawrapper.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP FOREIGN DATA WRAPPER
    DROP FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next

    DROP FOREIGN DATA WRAPPER

    DROP FOREIGN DATA WRAPPER — remove a foreign-data wrapper

    Synopsis

    +DROP FOREIGN DATA WRAPPER
    DROP FOREIGN DATA WRAPPER
    Prev UpSQL CommandsHome Next
    DROP FOREIGN DATA WRAPPER
    DROP FOREIGN DATA WRAPPER — remove a foreign-data wrapper
    Synopsis
     DROP FOREIGN DATA WRAPPER [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP FOREIGN DATA WRAPPER removes an existing
@@ -26,4 +26,4 @@
    DROP FOREIGN DATA WRAPPER conforms to ISO/IEC
    9075-9 (SQL/MED).  The IF EXISTS clause is
    a PostgreSQL extension.
-  
    Prev Up Next
    DROP EXTENSION Home DROP FOREIGN TABLE
    
\ No newline at end of file
+
    Prev Up Next
    DROP EXTENSION Home DROP FOREIGN TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropforeigntable.html postgresql-13-13.12/doc/src/sgml/html/sql-dropforeigntable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropforeigntable.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropforeigntable.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP FOREIGN TABLE
    DROP FOREIGN TABLE
    Prev UpSQL CommandsHome Next

    DROP FOREIGN TABLE

    DROP FOREIGN TABLE — remove a foreign table

    Synopsis

    +DROP FOREIGN TABLE
    DROP FOREIGN TABLE
    Prev UpSQL CommandsHome Next
    DROP FOREIGN TABLE
    DROP FOREIGN TABLE — remove a foreign table
    Synopsis
     DROP FOREIGN TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP FOREIGN TABLE removes a foreign table.
@@ -27,4 +27,4 @@
    standard only allows one foreign table to be dropped per command, and apart
    from the IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP FOREIGN DATA WRAPPER Home DROP FUNCTION
    
\ No newline at end of file
+
    Prev Up Next
    DROP FOREIGN DATA WRAPPER Home DROP FUNCTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropfunction.html postgresql-13-13.12/doc/src/sgml/html/sql-dropfunction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropfunction.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropfunction.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP FUNCTION
    DROP FUNCTION
    Prev UpSQL CommandsHome Next

    DROP FUNCTION

    DROP FUNCTION — remove a function

    Synopsis

    +DROP FUNCTION
    DROP FUNCTION
    Prev UpSQL CommandsHome Next
    DROP FUNCTION
    DROP FUNCTION — remove a function
    Synopsis
     DROP FUNCTION [ IF EXISTS ] name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ] [, ...]
     [ CASCADE | RESTRICT ]
 
    Description
    
@@ -64,4 +64,4 @@
   
    Compatibility
    
    This command conforms to the SQL standard, with
    these PostgreSQL extensions:
-   
    • The standard only allows one function to be dropped per command.
    • The IF EXISTS option
    • The ability to specify argument modes and names
    Prev Up Next
    DROP FOREIGN TABLE Home DROP GROUP
    
\ No newline at end of file
+   
    • The standard only allows one function to be dropped per command.
    • The IF EXISTS option
    • The ability to specify argument modes and names
    Prev Up Next
    DROP FOREIGN TABLE Home DROP GROUP
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropgroup.html postgresql-13-13.12/doc/src/sgml/html/sql-dropgroup.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropgroup.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropgroup.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,9 +1,9 @@ -DROP GROUP
    DROP GROUP
    Prev UpSQL CommandsHome Next

    DROP GROUP

    DROP GROUP — remove a database role

    Synopsis

    +DROP GROUP
    DROP GROUP
    Prev UpSQL CommandsHome Next
    DROP GROUP
    DROP GROUP — remove a database role
    Synopsis
     DROP GROUP [ IF EXISTS ] name [, ...]
 
    Description
    
    DROP GROUP is now an alias for
    DROP ROLE.
   
    Compatibility
    
    There is no DROP GROUP statement in the SQL standard.
-  
    See Also
    DROP ROLE
    Prev Up Next
    DROP FUNCTION Home DROP INDEX
    
\ No newline at end of file
+

    See Also

    DROP ROLE
    Prev Up Next
    DROP FUNCTION Home DROP INDEX
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropindex.html postgresql-13-13.12/doc/src/sgml/html/sql-dropindex.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropindex.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropindex.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP INDEX
    DROP INDEX
    Prev UpSQL CommandsHome Next

    DROP INDEX

    DROP INDEX — remove an index

    Synopsis

    +DROP INDEX
    DROP INDEX
    Prev UpSQL CommandsHome Next
    DROP INDEX
    DROP INDEX — remove an index
    Synopsis
     DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP INDEX drops an existing index from the database
@@ -47,4 +47,4 @@
    DROP INDEX is a
    PostgreSQL language extension.  There
    are no provisions for indexes in the SQL standard.
-  
    See Also
    CREATE INDEX
    Prev Up Next
    DROP GROUP Home DROP LANGUAGE
    
\ No newline at end of file
+

    See Also

    CREATE INDEX
    Prev Up Next
    DROP GROUP Home DROP LANGUAGE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droplanguage.html postgresql-13-13.12/doc/src/sgml/html/sql-droplanguage.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droplanguage.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droplanguage.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP LANGUAGE
    DROP LANGUAGE
    Prev UpSQL CommandsHome Next

    DROP LANGUAGE

    DROP LANGUAGE — remove a procedural language

    Synopsis

    +DROP LANGUAGE
    DROP LANGUAGE
    Prev UpSQL CommandsHome Next
    DROP LANGUAGE
    DROP LANGUAGE — remove a procedural language
    Synopsis
     DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP LANGUAGE removes the definition of a
@@ -33,4 +33,4 @@

    Compatibility

    There is no DROP LANGUAGE statement in the SQL standard. -

    Prev Up Next
    DROP INDEX Home DROP MATERIALIZED VIEW
    \ No newline at end of file +

    Prev Up Next
    DROP INDEX Home DROP MATERIALIZED VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropmaterializedview.html postgresql-13-13.12/doc/src/sgml/html/sql-dropmaterializedview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropmaterializedview.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropmaterializedview.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP MATERIALIZED VIEW
    DROP MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next

    DROP MATERIALIZED VIEW

    DROP MATERIALIZED VIEW — remove a materialized view

    Synopsis

    +DROP MATERIALIZED VIEW
    DROP MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next
    DROP MATERIALIZED VIEW
    DROP MATERIALIZED VIEW — remove a materialized view
    Synopsis
     DROP MATERIALIZED VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP MATERIALIZED VIEW drops an existing materialized
@@ -27,4 +27,4 @@

    Compatibility

    DROP MATERIALIZED VIEW is a PostgreSQL extension. -

    Prev Up Next
    DROP LANGUAGE Home DROP OPERATOR
    \ No newline at end of file +

    Prev Up Next
    DROP LANGUAGE Home DROP OPERATOR
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropopclass.html postgresql-13-13.12/doc/src/sgml/html/sql-dropopclass.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropopclass.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropopclass.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP OPERATOR CLASS
    DROP OPERATOR CLASS
    Prev UpSQL CommandsHome Next

    DROP OPERATOR CLASS

    DROP OPERATOR CLASS — remove an operator class

    Synopsis

    +DROP OPERATOR CLASS
    DROP OPERATOR CLASS
    Prev UpSQL CommandsHome Next
    DROP OPERATOR CLASS
    DROP OPERATOR CLASS — remove an operator class
    Synopsis
     DROP OPERATOR CLASS [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]
 
    Description
    
    DROP OPERATOR CLASS drops an existing operator class.
@@ -44,4 +44,4 @@
   
    Compatibility
    
    There is no DROP OPERATOR CLASS statement in the
    SQL standard.
-  
    Prev Up Next
    DROP OPERATOR Home DROP OPERATOR FAMILY
    
\ No newline at end of file
+
    Prev Up Next
    DROP OPERATOR Home DROP OPERATOR FAMILY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropoperator.html postgresql-13-13.12/doc/src/sgml/html/sql-dropoperator.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropoperator.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropoperator.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP OPERATOR
    DROP OPERATOR
    Prev UpSQL CommandsHome Next

    DROP OPERATOR

    DROP OPERATOR — remove an operator

    Synopsis

    +DROP OPERATOR
    DROP OPERATOR
    Prev UpSQL CommandsHome Next
    DROP OPERATOR
    DROP OPERATOR — remove an operator
    Synopsis
     DROP OPERATOR [ IF EXISTS ] name ( { left_type | NONE } , { right_type | NONE } ) [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP OPERATOR drops an existing operator from
@@ -45,4 +45,4 @@
 DROP OPERATOR ~ (none, bit), ! (bigint, none);

    Compatibility

    There is no DROP OPERATOR statement in the SQL standard. -

    Prev Up Next
    DROP MATERIALIZED VIEW Home DROP OPERATOR CLASS
    \ No newline at end of file +

    Prev Up Next
    DROP MATERIALIZED VIEW Home DROP OPERATOR CLASS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropopfamily.html postgresql-13-13.12/doc/src/sgml/html/sql-dropopfamily.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropopfamily.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropopfamily.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP OPERATOR FAMILY
    DROP OPERATOR FAMILY
    Prev UpSQL CommandsHome Next

    DROP OPERATOR FAMILY

    DROP OPERATOR FAMILY — remove an operator family

    Synopsis

    +DROP OPERATOR FAMILY
    DROP OPERATOR FAMILY
    Prev UpSQL CommandsHome Next
    DROP OPERATOR FAMILY
    DROP OPERATOR FAMILY — remove an operator family
    Synopsis
     DROP OPERATOR FAMILY [ IF EXISTS ] name USING index_method [ CASCADE | RESTRICT ]
 
    Description
    
    DROP OPERATOR FAMILY drops an existing operator family.
@@ -37,4 +37,4 @@
   
    Compatibility
    
    There is no DROP OPERATOR FAMILY statement in the
    SQL standard.
-  
    Prev Up Next
    DROP OPERATOR CLASS Home DROP OWNED
    
\ No newline at end of file
+
    Prev Up Next
    DROP OPERATOR CLASS Home DROP OWNED
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droppolicy.html postgresql-13-13.12/doc/src/sgml/html/sql-droppolicy.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droppolicy.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droppolicy.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP POLICY
    DROP POLICY
    Prev UpSQL CommandsHome Next

    DROP POLICY

    DROP POLICY — remove a row level security policy from a table

    Synopsis

    +DROP POLICY
    DROP POLICY
    Prev UpSQL CommandsHome Next
    DROP POLICY
    DROP POLICY — remove a row level security policy from a table
    Synopsis
     DROP POLICY [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP POLICY removes the specified policy from the table.
@@ -27,4 +27,4 @@
 DROP POLICY p1 ON my_table;

    Compatibility

    DROP POLICY is a PostgreSQL extension. -

    Prev Up Next
    DROP OWNED Home DROP PROCEDURE
    \ No newline at end of file +

    Prev Up Next
    DROP OWNED Home DROP PROCEDURE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropprocedure.html postgresql-13-13.12/doc/src/sgml/html/sql-dropprocedure.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropprocedure.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropprocedure.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP PROCEDURE
    DROP PROCEDURE
    Prev UpSQL CommandsHome Next

    DROP PROCEDURE

    DROP PROCEDURE — remove a procedure

    Synopsis

    +DROP PROCEDURE
    DROP PROCEDURE
    Prev UpSQL CommandsHome Next
    DROP PROCEDURE
    DROP PROCEDURE — remove a procedure
    Synopsis
     DROP PROCEDURE [ IF EXISTS ] name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ] [, ...]
     [ CASCADE | RESTRICT ]
 
    Description
    
@@ -37,4 +37,4 @@

    Compatibility

    This command conforms to the SQL standard, with these PostgreSQL extensions: -

    • The standard only allows one procedure to be dropped per command.

    • The IF EXISTS option

    • The ability to specify argument modes and names

    Prev Up Next
    DROP POLICY Home DROP PUBLICATION
    \ No newline at end of file +

    • The standard only allows one procedure to be dropped per command.

    • The IF EXISTS option

    • The ability to specify argument modes and names

    Prev Up Next
    DROP POLICY Home DROP PUBLICATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droppublication.html postgresql-13-13.12/doc/src/sgml/html/sql-droppublication.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droppublication.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droppublication.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP PUBLICATION
    DROP PUBLICATION
    Prev UpSQL CommandsHome Next

    DROP PUBLICATION

    DROP PUBLICATION — remove a publication

    Synopsis

    +DROP PUBLICATION
    DROP PUBLICATION
    Prev UpSQL CommandsHome Next
    DROP PUBLICATION
    DROP PUBLICATION — remove a publication
    Synopsis
     DROP PUBLICATION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP PUBLICATION removes an existing publication from
@@ -21,4 +21,4 @@

    Compatibility

    DROP PUBLICATION is a PostgreSQL extension. -

    Prev Up Next
    DROP PROCEDURE Home DROP ROLE
    \ No newline at end of file +

    Prev Up Next
    DROP PROCEDURE Home DROP ROLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droprole.html postgresql-13-13.12/doc/src/sgml/html/sql-droprole.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droprole.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droprole.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP ROLE
    DROP ROLE
    Prev UpSQL CommandsHome Next

    DROP ROLE

    DROP ROLE — remove a database role

    Synopsis

    +DROP ROLE
    DROP ROLE
    Prev UpSQL CommandsHome Next
    DROP ROLE
    DROP ROLE — remove a database role
    Synopsis
     DROP ROLE [ IF EXISTS ] name [, ...]
 
    Description
    
    DROP ROLE removes the specified role(s).
@@ -36,4 +36,4 @@
    The SQL standard defines DROP ROLE, but it allows
    only one role to be dropped at a time, and it specifies different
    privilege requirements than PostgreSQL uses.
-  
    Prev Up Next
    DROP PUBLICATION Home DROP ROUTINE
    
\ No newline at end of file
+
    Prev Up Next
    DROP PUBLICATION Home DROP ROUTINE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droproutine.html postgresql-13-13.12/doc/src/sgml/html/sql-droproutine.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droproutine.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droproutine.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP ROUTINE
    DROP ROUTINE
    Prev UpSQL CommandsHome Next

    DROP ROUTINE

    DROP ROUTINE — remove a routine

    Synopsis

    +DROP ROUTINE
    DROP ROUTINE
    Prev UpSQL CommandsHome Next
    DROP ROUTINE
    DROP ROUTINE — remove a routine
    Synopsis
     DROP ROUTINE [ IF EXISTS ] name [ ( [ [ argmode ] [ argname ] argtype [, ...] ] ) ] [, ...]
     [ CASCADE | RESTRICT ]
 
    Description
    
@@ -22,4 +22,4 @@
    these PostgreSQL extensions:
    
    • The standard only allows one routine to be dropped per command.
    • The IF EXISTS option
    • The ability to specify argument modes and names
    • Aggregate functions are an extension.
    See Also
    DROP AGGREGATE, DROP FUNCTION, DROP PROCEDURE, ALTER ROUTINE
    
    Note that there is no CREATE ROUTINE command.
-  
    Prev Up Next
    DROP ROLE Home DROP RULE
    
\ No newline at end of file
+
    Prev Up Next
    DROP ROLE Home DROP RULE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droprule.html postgresql-13-13.12/doc/src/sgml/html/sql-droprule.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droprule.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droprule.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP RULE
    DROP RULE
    Prev UpSQL CommandsHome Next

    DROP RULE

    DROP RULE — remove a rewrite rule

    Synopsis

    +DROP RULE
    DROP RULE
    Prev UpSQL CommandsHome Next
    DROP RULE
    DROP RULE — remove a rewrite rule
    Synopsis
     DROP RULE [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP RULE drops a rewrite rule.
@@ -27,4 +27,4 @@
    DROP RULE is a
    PostgreSQL language extension, as is the
    entire query rewrite system.
-  
    Prev Up Next
    DROP ROUTINE Home DROP SCHEMA
    
\ No newline at end of file
+
    Prev Up Next
    DROP ROUTINE Home DROP SCHEMA
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropschema.html postgresql-13-13.12/doc/src/sgml/html/sql-dropschema.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropschema.html 2023-05-08 21:34:05.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropschema.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP SCHEMA
    DROP SCHEMA
    Prev UpSQL CommandsHome Next

    DROP SCHEMA

    DROP SCHEMA — remove a schema

    Synopsis

    +DROP SCHEMA
    DROP SCHEMA
    Prev UpSQL CommandsHome Next
    DROP SCHEMA
    DROP SCHEMA — remove a schema
    Synopsis
     DROP SCHEMA [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP SCHEMA removes schemas from the database.
@@ -35,4 +35,4 @@
    dropped per command, and apart from the
    IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP RULE Home DROP SEQUENCE
    
\ No newline at end of file
+
    Prev Up Next
    DROP RULE Home DROP SEQUENCE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropsequence.html postgresql-13-13.12/doc/src/sgml/html/sql-dropsequence.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropsequence.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropsequence.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP SEQUENCE
    DROP SEQUENCE
    Prev UpSQL CommandsHome Next

    DROP SEQUENCE

    DROP SEQUENCE — remove a sequence

    Synopsis

    +DROP SEQUENCE
    DROP SEQUENCE
    Prev UpSQL CommandsHome Next
    DROP SEQUENCE
    DROP SEQUENCE — remove a sequence
    Synopsis
     DROP SEQUENCE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP SEQUENCE removes sequence number
@@ -27,4 +27,4 @@
    sequence to be dropped per command, and apart from the
    IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP SCHEMA Home DROP SERVER
    
\ No newline at end of file
+
    Prev Up Next
    DROP SCHEMA Home DROP SERVER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropserver.html postgresql-13-13.12/doc/src/sgml/html/sql-dropserver.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropserver.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropserver.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP SERVER
    DROP SERVER
    Prev UpSQL CommandsHome Next

    DROP SERVER

    DROP SERVER — remove a foreign server descriptor

    Synopsis

    +DROP SERVER
    DROP SERVER
    Prev UpSQL CommandsHome Next
    DROP SERVER
    DROP SERVER — remove a foreign server descriptor
    Synopsis
     DROP SERVER [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP SERVER removes an existing foreign server
@@ -26,4 +26,4 @@
    DROP SERVER conforms to ISO/IEC 9075-9
    (SQL/MED).  The IF EXISTS clause is
    a PostgreSQL extension.
-  
    Prev Up Next
    DROP SEQUENCE Home DROP STATISTICS
    
\ No newline at end of file
+
    Prev Up Next
    DROP SEQUENCE Home DROP STATISTICS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropstatistics.html postgresql-13-13.12/doc/src/sgml/html/sql-dropstatistics.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropstatistics.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropstatistics.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP STATISTICS
    DROP STATISTICS
    Prev UpSQL CommandsHome Next

    DROP STATISTICS

    DROP STATISTICS — remove extended statistics

    Synopsis

    +DROP STATISTICS
    DROP STATISTICS
    Prev UpSQL CommandsHome Next
    DROP STATISTICS
    DROP STATISTICS — remove extended statistics
    Synopsis
     DROP STATISTICS [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP STATISTICS removes statistics object(s) from the
@@ -23,4 +23,4 @@
     public.grants_user_role;

    Compatibility

    There is no DROP STATISTICS command in the SQL standard. -

    Prev Up Next
    DROP SERVER Home DROP SUBSCRIPTION
    \ No newline at end of file +

    Prev Up Next
    DROP SERVER Home DROP SUBSCRIPTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropsubscription.html postgresql-13-13.12/doc/src/sgml/html/sql-dropsubscription.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropsubscription.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropsubscription.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP SUBSCRIPTION
    DROP SUBSCRIPTION
    Prev UpSQL CommandsHome Next

    DROP SUBSCRIPTION

    DROP SUBSCRIPTION — remove a subscription

    Synopsis

    +DROP SUBSCRIPTION
    DROP SUBSCRIPTION
    Prev UpSQL CommandsHome Next
    DROP SUBSCRIPTION
    DROP SUBSCRIPTION — remove a subscription
    Synopsis
     DROP SUBSCRIPTION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP SUBSCRIPTION removes a subscription from the
@@ -24,9 +24,11 @@
    for the subscription on the remote host are released.  If this fails,
    either because the remote host is not reachable or because the remote
    replication slot cannot be dropped or does not exist or never existed,
-   the DROP SUBSCRIPTION command will fail.  To proceed in
-   this situation, disassociate the subscription from the replication slot by
-   executing ALTER SUBSCRIPTION ... SET (slot_name = NONE).
+   the DROP SUBSCRIPTION command will fail.  To proceed
+   in this situation, first disable the subscription by executing
+   ALTER SUBSCRIPTION ... DISABLE, and then disassociate
+   it from the replication slot by executing
+   ALTER SUBSCRIPTION ... SET (slot_name = NONE).
    After that, DROP SUBSCRIPTION will no longer attempt any
    actions on a remote host.  Note that if the remote replication slot still
    exists, it should then be dropped manually; otherwise it will continue to
@@ -42,4 +44,4 @@

    Compatibility

    DROP SUBSCRIPTION is a PostgreSQL extension. -

    Prev Up Next
    DROP STATISTICS Home DROP TABLE
    \ No newline at end of file +

    Prev Up Next
    DROP STATISTICS Home DROP TABLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptable.html postgresql-13-13.12/doc/src/sgml/html/sql-droptable.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptable.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptable.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TABLE
    DROP TABLE
    Prev UpSQL CommandsHome Next

    DROP TABLE

    DROP TABLE — remove a table

    Synopsis

    +DROP TABLE
    DROP TABLE
    Prev UpSQL CommandsHome Next
    DROP TABLE
    DROP TABLE — remove a table
    Synopsis
     DROP TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TABLE removes tables from the database.
@@ -39,4 +39,4 @@
    allows one table to be dropped per command, and apart from the
    IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP SUBSCRIPTION Home DROP TABLESPACE
    
\ No newline at end of file
+
    Prev Up Next
    DROP SUBSCRIPTION Home DROP TABLESPACE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptablespace.html postgresql-13-13.12/doc/src/sgml/html/sql-droptablespace.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptablespace.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptablespace.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TABLESPACE
    DROP TABLESPACE
    Prev UpSQL CommandsHome Next

    DROP TABLESPACE

    DROP TABLESPACE — remove a tablespace

    Synopsis

    +DROP TABLESPACE
    DROP TABLESPACE
    Prev UpSQL CommandsHome Next
    DROP TABLESPACE
    DROP TABLESPACE — remove a tablespace
    Synopsis
     DROP TABLESPACE [ IF EXISTS ] name
 
    Description
    
    DROP TABLESPACE removes a tablespace from the system.
@@ -25,4 +25,4 @@

    Compatibility

    DROP TABLESPACE is a PostgreSQL extension. -

    Prev Up Next
    DROP TABLE Home DROP TEXT SEARCH CONFIGURATION
    \ No newline at end of file +

    Prev Up Next
    DROP TABLE Home DROP TEXT SEARCH CONFIGURATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptransform.html postgresql-13-13.12/doc/src/sgml/html/sql-droptransform.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptransform.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptransform.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TRANSFORM
    DROP TRANSFORM
    Prev UpSQL CommandsHome Next

    DROP TRANSFORM

    DROP TRANSFORM — remove a transform

    Synopsis

    +DROP TRANSFORM
    DROP TRANSFORM
    Prev UpSQL CommandsHome Next
    DROP TRANSFORM
    DROP TRANSFORM — remove a transform
    Synopsis
     DROP TRANSFORM [ IF EXISTS ] FOR type_name LANGUAGE lang_name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TRANSFORM removes a previously defined transform.
@@ -28,4 +28,4 @@

    Compatibility

    This form of DROP TRANSFORM is a PostgreSQL extension. See CREATE TRANSFORM for details. -

    Prev Up Next
    DROP TEXT SEARCH TEMPLATE Home DROP TRIGGER
    \ No newline at end of file +

    Prev Up Next
    DROP TEXT SEARCH TEMPLATE Home DROP TRIGGER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptrigger.html postgresql-13-13.12/doc/src/sgml/html/sql-droptrigger.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptrigger.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptrigger.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TRIGGER
    DROP TRIGGER
    Prev UpSQL CommandsHome Next

    DROP TRIGGER

    DROP TRIGGER — remove a trigger

    Synopsis

    +DROP TRIGGER
    DROP TRIGGER
    Prev UpSQL CommandsHome Next
    DROP TRIGGER
    DROP TRIGGER — remove a trigger
    Synopsis
     DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TRIGGER removes an existing
@@ -32,4 +32,4 @@
    standard.  In the SQL standard, trigger names are not local to
    tables, so the command is simply DROP TRIGGER
    name.
-  
    Prev Up Next
    DROP TRANSFORM Home DROP TYPE
    
\ No newline at end of file
+
    Prev Up Next
    DROP TRANSFORM Home DROP TYPE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptsconfig.html postgresql-13-13.12/doc/src/sgml/html/sql-droptsconfig.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptsconfig.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptsconfig.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TEXT SEARCH CONFIGURATION
    DROP TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next

    DROP TEXT SEARCH CONFIGURATION

    DROP TEXT SEARCH CONFIGURATION — remove a text search configuration

    Synopsis

    +DROP TEXT SEARCH CONFIGURATION
    DROP TEXT SEARCH CONFIGURATION
    Prev UpSQL CommandsHome Next
    DROP TEXT SEARCH CONFIGURATION
    DROP TEXT SEARCH CONFIGURATION — remove a text search configuration
    Synopsis
     DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TEXT SEARCH CONFIGURATION drops an existing text
@@ -32,4 +32,4 @@
   
    Compatibility
    
    There is no DROP TEXT SEARCH CONFIGURATION statement in
    the SQL standard.
-  
    Prev Up Next
    DROP TABLESPACE Home DROP TEXT SEARCH DICTIONARY
    
\ No newline at end of file
+
    Prev Up Next
    DROP TABLESPACE Home DROP TEXT SEARCH DICTIONARY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptsdictionary.html postgresql-13-13.12/doc/src/sgml/html/sql-droptsdictionary.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptsdictionary.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptsdictionary.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TEXT SEARCH DICTIONARY
    DROP TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next

    DROP TEXT SEARCH DICTIONARY

    DROP TEXT SEARCH DICTIONARY — remove a text search dictionary

    Synopsis

    +DROP TEXT SEARCH DICTIONARY
    DROP TEXT SEARCH DICTIONARY
    Prev UpSQL CommandsHome Next
    DROP TEXT SEARCH DICTIONARY
    DROP TEXT SEARCH DICTIONARY — remove a text search dictionary
    Synopsis
     DROP TEXT SEARCH DICTIONARY [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TEXT SEARCH DICTIONARY drops an existing text
@@ -31,4 +31,4 @@
   
    Compatibility
    
    There is no DROP TEXT SEARCH DICTIONARY statement in the
    SQL standard.
-  
    Prev Up Next
    DROP TEXT SEARCH CONFIGURATION Home DROP TEXT SEARCH PARSER
    
\ No newline at end of file
+
    Prev Up Next
    DROP TEXT SEARCH CONFIGURATION Home DROP TEXT SEARCH PARSER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptsparser.html postgresql-13-13.12/doc/src/sgml/html/sql-droptsparser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptsparser.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptsparser.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TEXT SEARCH PARSER
    DROP TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next

    DROP TEXT SEARCH PARSER

    DROP TEXT SEARCH PARSER — remove a text search parser

    Synopsis

    +DROP TEXT SEARCH PARSER
    DROP TEXT SEARCH PARSER
    Prev UpSQL CommandsHome Next
    DROP TEXT SEARCH PARSER
    DROP TEXT SEARCH PARSER — remove a text search parser
    Synopsis
     DROP TEXT SEARCH PARSER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TEXT SEARCH PARSER drops an existing text search
@@ -29,4 +29,4 @@
   
    Compatibility
    
    There is no DROP TEXT SEARCH PARSER statement in the
    SQL standard.
-  
    Prev Up Next
    DROP TEXT SEARCH DICTIONARY Home DROP TEXT SEARCH TEMPLATE
    
\ No newline at end of file
+
    Prev Up Next
    DROP TEXT SEARCH DICTIONARY Home DROP TEXT SEARCH TEMPLATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptstemplate.html postgresql-13-13.12/doc/src/sgml/html/sql-droptstemplate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptstemplate.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptstemplate.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TEXT SEARCH TEMPLATE
    DROP TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next

    DROP TEXT SEARCH TEMPLATE

    DROP TEXT SEARCH TEMPLATE — remove a text search template

    Synopsis

    +DROP TEXT SEARCH TEMPLATE
    DROP TEXT SEARCH TEMPLATE
    Prev UpSQL CommandsHome Next
    DROP TEXT SEARCH TEMPLATE
    DROP TEXT SEARCH TEMPLATE — remove a text search template
    Synopsis
     DROP TEXT SEARCH TEMPLATE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TEXT SEARCH TEMPLATE drops an existing text search
@@ -30,4 +30,4 @@
   
    Compatibility
    
    There is no DROP TEXT SEARCH TEMPLATE statement in the
    SQL standard.
-  
    Prev Up Next
    DROP TEXT SEARCH PARSER Home DROP TRANSFORM
    
\ No newline at end of file
+
    Prev Up Next
    DROP TEXT SEARCH PARSER Home DROP TRANSFORM
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-droptype.html postgresql-13-13.12/doc/src/sgml/html/sql-droptype.html --- postgresql-13-13.11/doc/src/sgml/html/sql-droptype.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-droptype.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP TYPE
    DROP TYPE
    Prev UpSQL CommandsHome Next

    DROP TYPE

    DROP TYPE — remove a data type

    Synopsis

    +DROP TYPE
    DROP TYPE
    Prev UpSQL CommandsHome Next
    DROP TYPE
    DROP TYPE — remove a data type
    Synopsis
     DROP TYPE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP TYPE removes a user-defined data type.
@@ -28,4 +28,4 @@
    But note that much of the CREATE TYPE command
    and the data type extension mechanisms in
    PostgreSQL differ from the SQL standard.
-  
    Prev Up Next
    DROP TRIGGER Home DROP USER
    
\ No newline at end of file
+
    Prev Up Next
    DROP TRIGGER Home DROP USER
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropuser.html postgresql-13-13.12/doc/src/sgml/html/sql-dropuser.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropuser.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropuser.html 2023-08-07 20:32:25.000000000 +0000 @@ -1,5 +1,5 @@ -DROP USER
    DROP USER
    Prev UpSQL CommandsHome Next

    DROP USER

    DROP USER — remove a database role

    Synopsis

    +DROP USER
    DROP USER
    Prev UpSQL CommandsHome Next
    DROP USER
    DROP USER — remove a database role
    Synopsis
     DROP USER [ IF EXISTS ] name [, ...]
 
    Description
    
    DROP USER is simply an alternate spelling of
@@ -8,4 +8,4 @@
    The DROP USER statement is a
    PostgreSQL extension.  The SQL standard
    leaves the definition of users to the implementation.
-  
    See Also
    DROP ROLE
    Prev Up Next
    DROP TYPE Home DROP USER MAPPING
    
\ No newline at end of file
+

    See Also

    DROP ROLE
    Prev Up Next
    DROP TYPE Home DROP USER MAPPING
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropusermapping.html postgresql-13-13.12/doc/src/sgml/html/sql-dropusermapping.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropusermapping.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropusermapping.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -DROP USER MAPPING
    DROP USER MAPPING
    Prev UpSQL CommandsHome Next

    DROP USER MAPPING

    DROP USER MAPPING — remove a user mapping for a foreign server

    Synopsis

    +DROP USER MAPPING
    DROP USER MAPPING
    Prev UpSQL CommandsHome Next
    DROP USER MAPPING
    DROP USER MAPPING — remove a user mapping for a foreign server
    Synopsis
     DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC } SERVER server_name
 
    Description
    
    DROP USER MAPPING removes an existing user
@@ -27,4 +27,4 @@
    DROP USER MAPPING conforms to ISO/IEC 9075-9
    (SQL/MED).  The IF EXISTS clause is
    a PostgreSQL extension.
-  
    Prev Up Next
    DROP USER Home DROP VIEW
    
\ No newline at end of file
+
    Prev Up Next
    DROP USER Home DROP VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-dropview.html postgresql-13-13.12/doc/src/sgml/html/sql-dropview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-dropview.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-dropview.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -DROP VIEW
    DROP VIEW
    Prev UpSQL CommandsHome Next

    DROP VIEW

    DROP VIEW — remove a view

    Synopsis

    +DROP VIEW
    DROP VIEW
    Prev UpSQL CommandsHome Next
    DROP VIEW
    DROP VIEW — remove a view
    Synopsis
     DROP VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
 
    Description
    
    DROP VIEW drops an existing view.  To execute
@@ -26,4 +26,4 @@
    allows one view to be dropped per command, and apart from the
    IF EXISTS option, which is a PostgreSQL
    extension.
-  
    Prev Up Next
    DROP USER MAPPING Home END
    
\ No newline at end of file
+
    Prev Up Next
    DROP USER MAPPING Home END
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-end.html postgresql-13-13.12/doc/src/sgml/html/sql-end.html --- postgresql-13-13.11/doc/src/sgml/html/sql-end.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-end.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -END
    END
    Prev UpSQL CommandsHome Next

    END

    END — commit the current transaction

    Synopsis

    +END
    END
    Prev UpSQL CommandsHome Next
    END
    END — commit the current transaction
    Synopsis
     END [ WORK | TRANSACTION ] [ AND [ NO ] CHAIN ]
 
    Description
    
    END commits the current transaction. All changes
@@ -27,4 +27,4 @@
    END is a PostgreSQL
    extension that provides functionality equivalent to COMMIT, which is
    specified in the SQL standard.
-  
    Prev Up Next
    DROP VIEW Home EXECUTE
    
\ No newline at end of file
+
    Prev Up Next
    DROP VIEW Home EXECUTE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-execute.html postgresql-13-13.12/doc/src/sgml/html/sql-execute.html --- postgresql-13-13.11/doc/src/sgml/html/sql-execute.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-execute.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -EXECUTE
    EXECUTE
    Prev UpSQL CommandsHome Next

    EXECUTE

    EXECUTE — execute a prepared statement

    Synopsis

    +EXECUTE
    EXECUTE
    Prev UpSQL CommandsHome Next
    EXECUTE
    EXECUTE — execute a prepared statement
    Synopsis
     EXECUTE name [ ( parameter [, ...] ) ]
 
    Description
    
    EXECUTE is used to execute a previously prepared
@@ -35,4 +35,4 @@
    but it is only for use in embedded SQL.  This version of the
    EXECUTE statement also uses a somewhat different
    syntax.
-  
    Prev Up Next
    END Home EXPLAIN
    
\ No newline at end of file
+
    Prev Up Next
    END Home EXPLAIN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-explain.html postgresql-13-13.12/doc/src/sgml/html/sql-explain.html --- postgresql-13-13.11/doc/src/sgml/html/sql-explain.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-explain.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -EXPLAIN
    EXPLAIN
    Prev UpSQL CommandsHome Next

    EXPLAIN

    EXPLAIN — show the execution plan of a statement

    Synopsis

    +EXPLAIN
    EXPLAIN
    Prev UpSQL CommandsHome Next
    EXPLAIN
    EXPLAIN — show the execution plan of a statement
    Synopsis
     EXPLAIN [ ( option [, ...] ) ] statement
 EXPLAIN [ ANALYZE ] [ VERBOSE ] statement
 
@@ -299,4 +299,4 @@
    in the table has not changed.
   
    Compatibility
    
    There is no EXPLAIN statement defined in the SQL standard.
-  
    See Also
    ANALYZE
    Prev Up Next
    EXECUTE Home FETCH
    
\ No newline at end of file
+

    See Also

    ANALYZE
    Prev Up Next
    EXECUTE Home FETCH
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-expressions.html postgresql-13-13.12/doc/src/sgml/html/sql-expressions.html --- postgresql-13-13.11/doc/src/sgml/html/sql-expressions.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-expressions.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -4.2. Value Expressions
    4.2. Value Expressions
    Prev UpChapter 4. SQL SyntaxHome Next
    Prev Up Next
    4.1. Lexical Structure Home 4.3. Calling Functions
    \ No newline at end of file +

    Prev Up Next
    4.1. Lexical Structure Home 4.3. Calling Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-fetch.html postgresql-13-13.12/doc/src/sgml/html/sql-fetch.html --- postgresql-13-13.11/doc/src/sgml/html/sql-fetch.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-fetch.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -FETCH
    FETCH
    Prev UpSQL CommandsHome Next

    FETCH

    FETCH — retrieve rows from a query using a cursor

    Synopsis

    +FETCH
    FETCH
    Prev UpSQL CommandsHome Next
    FETCH
    FETCH — retrieve rows from a query using a cursor
    Synopsis
     FETCH [ direction ] [ FROM | IN ] cursor_name
 
 where direction can be one of:
@@ -187,4 +187,4 @@
    The SQL standard allows only FROM preceding the cursor
    name; the option to use IN, or to leave them out altogether, is
    an extension.
-  
    See Also
    CLOSE, DECLARE, MOVE
    Prev Up Next
    EXPLAIN Home GRANT
    
\ No newline at end of file
+

    See Also

    CLOSE, DECLARE, MOVE
    Prev Up Next
    EXPLAIN Home GRANT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-grant.html postgresql-13-13.12/doc/src/sgml/html/sql-grant.html --- postgresql-13-13.11/doc/src/sgml/html/sql-grant.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-grant.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -GRANT
    GRANT
    Prev UpSQL CommandsHome Next

    GRANT

    GRANT — define access privileges

    Synopsis

    +GRANT
    GRANT
    Prev UpSQL CommandsHome Next
    GRANT
    GRANT — define access privileges
    Synopsis
     GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
     [, ...] | ALL [ PRIVILEGES ] }
     ON { [ TABLE ] table_name [, ...]
@@ -291,4 +291,4 @@
    
    
     Privileges on databases, tablespaces, schemas, and languages are
     PostgreSQL extensions.
-   
    Prev Up Next
    FETCH Home IMPORT FOREIGN SCHEMA
    
\ No newline at end of file
+
    Prev Up Next
    FETCH Home IMPORT FOREIGN SCHEMA
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-importforeignschema.html postgresql-13-13.12/doc/src/sgml/html/sql-importforeignschema.html --- postgresql-13-13.11/doc/src/sgml/html/sql-importforeignschema.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-importforeignschema.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -IMPORT FOREIGN SCHEMA
    IMPORT FOREIGN SCHEMA
    Prev UpSQL CommandsHome Next

    IMPORT FOREIGN SCHEMA

    IMPORT FOREIGN SCHEMA — import table definitions from a foreign server

    Synopsis

    +IMPORT FOREIGN SCHEMA
    IMPORT FOREIGN SCHEMA
    Prev UpSQL CommandsHome Next
    IMPORT FOREIGN SCHEMA
    IMPORT FOREIGN SCHEMA — import table definitions from a foreign server
    Synopsis
     IMPORT FOREIGN SCHEMA remote_schema
     [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ]
     FROM SERVER server_name
@@ -57,4 +57,4 @@
    The IMPORT FOREIGN SCHEMA command conforms to the
    SQL standard, except that the OPTIONS
    clause is a PostgreSQL extension.
-  
    Prev Up Next
    GRANT Home INSERT
    
\ No newline at end of file
+
    Prev Up Next
    GRANT Home INSERT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-insert.html postgresql-13-13.12/doc/src/sgml/html/sql-insert.html --- postgresql-13-13.11/doc/src/sgml/html/sql-insert.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-insert.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -INSERT
    INSERT
    Prev UpSQL CommandsHome Next

    INSERT

    INSERT — create new rows in a table

    Synopsis

    +INSERT
    INSERT
    Prev UpSQL CommandsHome Next
    INSERT
    INSERT — create new rows in a table
    Synopsis
     [ WITH [ RECURSIVE ] with_query [, ...] ]
 INSERT INTO table_name [ AS alias ] [ ( column_name [, ...] ) ]
     [ OVERRIDING { SYSTEM | USER } VALUE ]
@@ -478,4 +478,4 @@
   
    
    Possible limitations of the query clause are documented under
    SELECT.
-  
    Prev Up Next
    IMPORT FOREIGN SCHEMA Home LISTEN
    
\ No newline at end of file
+
    Prev Up Next
    IMPORT FOREIGN SCHEMA Home LISTEN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-keywords-appendix.html postgresql-13-13.12/doc/src/sgml/html/sql-keywords-appendix.html --- postgresql-13-13.11/doc/src/sgml/html/sql-keywords-appendix.html 2023-05-08 21:34:14.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-keywords-appendix.html 2023-08-07 20:32:35.000000000 +0000 @@ -1,8 +1,8 @@ -Appendix C. SQL Key Words
    Appendix C. SQL Key Words
    Prev UpPart VIII. AppendixesHome Next

    Appendix C. SQL Key Words

    +Appendix C. SQL Key Words

    Appendix C. SQL Key Words
    Prev UpPart VIII. AppendixesHome Next

    Appendix C. SQL Key Words

    Table C.1 lists all tokens that are key words in the SQL standard and in PostgreSQL - 13.11. Background information can be found in Section 4.1.1. + 13.12. Background information can be found in Section 4.1.1. (For space reasons, only the latest two versions of the SQL standard, and SQL-92 for historical comparison, are included. The differences between those and the other intermediate standard versions are small.) @@ -52,4 +52,4 @@ reserved in PostgreSQL does not mean that the feature related to the word is not implemented. Conversely, the presence of a key word does not indicate the existence of a feature. -

    Table C.1. SQL Key Words

    Key WordPostgreSQLSQL:2016SQL:2011SQL-92
    A non-reservednon-reserved 
    ABORTnon-reserved   
    ABS reservedreserved 
    ABSENT non-reservednon-reserved 
    ABSOLUTEnon-reservednon-reservednon-reservedreserved
    ACCESSnon-reserved   
    ACCORDING non-reservednon-reserved 
    ACOS reserved  
    ACTIONnon-reservednon-reservednon-reservedreserved
    ADA non-reservednon-reservednon-reserved
    ADDnon-reservednon-reservednon-reservedreserved
    ADMINnon-reservednon-reservednon-reserved 
    AFTERnon-reservednon-reservednon-reserved 
    AGGREGATEnon-reserved   
    ALLreservedreservedreservedreserved
    ALLOCATE reservedreservedreserved
    ALSOnon-reserved   
    ALTERnon-reservedreservedreservedreserved
    ALWAYSnon-reservednon-reservednon-reserved 
    ANALYSEreserved   
    ANALYZEreserved   
    ANDreservedreservedreservedreserved
    ANYreservedreservedreservedreserved
    ARE reservedreservedreserved
    ARRAYreservedreservedreserved 
    ARRAY_AGG reservedreserved 
    ARRAY_​MAX_​CARDINALITY reservedreserved 
    ASreservedreservedreservedreserved
    ASCreservednon-reservednon-reservedreserved
    ASENSITIVE reservedreserved 
    ASIN reserved  
    ASSERTIONnon-reservednon-reservednon-reservedreserved
    ASSIGNMENTnon-reservednon-reservednon-reserved 
    ASYMMETRICreservedreservedreserved 
    ATnon-reservedreservedreservedreserved
    ATAN reserved  
    ATOMIC reservedreserved 
    ATTACHnon-reserved   
    ATTRIBUTEnon-reservednon-reservednon-reserved 
    ATTRIBUTES non-reservednon-reserved 
    AUTHORIZATIONreserved (can be function or type)reservedreservedreserved
    AVG reservedreservedreserved
    BACKWARDnon-reserved   
    BASE64 non-reservednon-reserved 
    BEFOREnon-reservednon-reservednon-reserved 
    BEGINnon-reservedreservedreservedreserved
    BEGIN_FRAME reservedreserved 
    BEGIN_PARTITION reservedreserved 
    BERNOULLI non-reservednon-reserved 
    BETWEENnon-reserved (cannot be function or type)reservedreservedreserved
    BIGINTnon-reserved (cannot be function or type)reservedreserved 
    BINARYreserved (can be function or type)reservedreserved 
    BITnon-reserved (cannot be function or type)  reserved
    BIT_LENGTH   reserved
    BLOB reservedreserved 
    BLOCKED non-reservednon-reserved 
    BOM non-reservednon-reserved 
    BOOLEANnon-reserved (cannot be function or type)reservedreserved 
    BOTHreservedreservedreservedreserved
    BREADTH non-reservednon-reserved 
    BYnon-reservedreservedreservedreserved
    C non-reservednon-reservednon-reserved
    CACHEnon-reserved   
    CALLnon-reservedreservedreserved 
    CALLEDnon-reservedreservedreserved 
    CARDINALITY reservedreserved 
    CASCADEnon-reservednon-reservednon-reservedreserved
    CASCADEDnon-reservedreservedreservedreserved
    CASEreservedreservedreservedreserved
    CASTreservedreservedreservedreserved
    CATALOGnon-reservednon-reservednon-reservedreserved
    CATALOG_NAME non-reservednon-reservednon-reserved
    CEIL reservedreserved 
    CEILING reservedreserved 
    CHAINnon-reservednon-reservednon-reserved 
    CHAINING non-reserved  
    CHARnon-reserved (cannot be function or type)reservedreservedreserved
    CHARACTERnon-reserved (cannot be function or type)reservedreservedreserved
    CHARACTERISTICSnon-reservednon-reservednon-reserved 
    CHARACTERS non-reservednon-reserved 
    CHARACTER_LENGTH reservedreservedreserved
    CHARACTER_​SET_​CATALOG non-reservednon-reservednon-reserved
    CHARACTER_SET_NAME non-reservednon-reservednon-reserved
    CHARACTER_SET_SCHEMA non-reservednon-reservednon-reserved
    CHAR_LENGTH reservedreservedreserved
    CHECKreservedreservedreservedreserved
    CHECKPOINTnon-reserved   
    CLASSnon-reserved   
    CLASSIFIER reserved  
    CLASS_ORIGIN non-reservednon-reservednon-reserved
    CLOB reservedreserved 
    CLOSEnon-reservedreservedreservedreserved
    CLUSTERnon-reserved   
    COALESCEnon-reserved (cannot be function or type)reservedreservedreserved
    COBOL non-reservednon-reservednon-reserved
    COLLATEreservedreservedreservedreserved
    COLLATIONreserved (can be function or type)non-reservednon-reservedreserved
    COLLATION_CATALOG non-reservednon-reservednon-reserved
    COLLATION_NAME non-reservednon-reservednon-reserved
    COLLATION_SCHEMA non-reservednon-reservednon-reserved
    COLLECT reservedreserved 
    COLUMNreservedreservedreservedreserved
    COLUMNSnon-reservednon-reservednon-reserved 
    COLUMN_NAME non-reservednon-reservednon-reserved
    COMMAND_FUNCTION non-reservednon-reservednon-reserved
    COMMAND_​FUNCTION_​CODE non-reservednon-reserved 
    COMMENTnon-reserved   
    COMMENTSnon-reserved   
    COMMITnon-reservedreservedreservedreserved
    COMMITTEDnon-reservednon-reservednon-reservednon-reserved
    CONCURRENTLYreserved (can be function or type)   
    CONDITION reservedreserved 
    CONDITIONAL non-reserved  
    CONDITION_NUMBER non-reservednon-reservednon-reserved
    CONFIGURATIONnon-reserved   
    CONFLICTnon-reserved   
    CONNECT reservedreservedreserved
    CONNECTIONnon-reservednon-reservednon-reservedreserved
    CONNECTION_NAME non-reservednon-reservednon-reserved
    CONSTRAINTreservedreservedreservedreserved
    CONSTRAINTSnon-reservednon-reservednon-reservedreserved
    CONSTRAINT_CATALOG non-reservednon-reservednon-reserved
    CONSTRAINT_NAME non-reservednon-reservednon-reserved
    CONSTRAINT_SCHEMA non-reservednon-reservednon-reserved
    CONSTRUCTOR non-reservednon-reserved 
    CONTAINS reservedreserved 
    CONTENTnon-reservednon-reservednon-reserved 
    CONTINUEnon-reservednon-reservednon-reservedreserved
    CONTROL non-reservednon-reserved 
    CONVERSIONnon-reserved   
    CONVERT reservedreservedreserved
    COPYnon-reservedreserved  
    CORR reservedreserved 
    CORRESPONDING reservedreservedreserved
    COS reserved  
    COSH reserved  
    COSTnon-reserved   
    COUNT reservedreservedreserved
    COVAR_POP reservedreserved 
    COVAR_SAMP reservedreserved 
    CREATEreservedreservedreservedreserved
    CROSSreserved (can be function or type)reservedreservedreserved
    CSVnon-reserved   
    CUBEnon-reservedreservedreserved 
    CUME_DIST reservedreserved 
    CURRENTnon-reservedreservedreservedreserved
    CURRENT_CATALOGreservedreservedreserved 
    CURRENT_DATEreservedreservedreservedreserved
    CURRENT_​DEFAULT_​TRANSFORM_​GROUP reservedreserved 
    CURRENT_PATH reservedreserved 
    CURRENT_ROLEreservedreservedreserved 
    CURRENT_ROW reservedreserved 
    CURRENT_SCHEMAreserved (can be function or type)reservedreserved 
    CURRENT_TIMEreservedreservedreservedreserved
    CURRENT_TIMESTAMPreservedreservedreservedreserved
    CURRENT_​TRANSFORM_​GROUP_​FOR_​TYPE reservedreserved 
    CURRENT_USERreservedreservedreservedreserved
    CURSORnon-reservedreservedreservedreserved
    CURSOR_NAME non-reservednon-reservednon-reserved
    CYCLEnon-reservedreservedreserved 
    DATAnon-reservednon-reservednon-reservednon-reserved
    DATABASEnon-reserved   
    DATALINK reservedreserved 
    DATE reservedreservedreserved
    DATETIME_​INTERVAL_​CODE non-reservednon-reservednon-reserved
    DATETIME_​INTERVAL_​PRECISION non-reservednon-reservednon-reserved
    DAYnon-reservedreservedreservedreserved
    DB non-reservednon-reserved 
    DEALLOCATEnon-reservedreservedreservedreserved
    DECnon-reserved (cannot be function or type)reservedreservedreserved
    DECFLOAT reserved  
    DECIMALnon-reserved (cannot be function or type)reservedreservedreserved
    DECLAREnon-reservedreservedreservedreserved
    DEFAULTreservedreservedreservedreserved
    DEFAULTSnon-reservednon-reservednon-reserved 
    DEFERRABLEreservednon-reservednon-reservedreserved
    DEFERREDnon-reservednon-reservednon-reservedreserved
    DEFINE reserved  
    DEFINED non-reservednon-reserved 
    DEFINERnon-reservednon-reservednon-reserved 
    DEGREE non-reservednon-reserved 
    DELETEnon-reservedreservedreservedreserved
    DELIMITERnon-reserved   
    DELIMITERSnon-reserved   
    DENSE_RANK reservedreserved 
    DEPENDSnon-reserved   
    DEPTH non-reservednon-reserved 
    DEREF reservedreserved 
    DERIVED non-reservednon-reserved 
    DESCreservednon-reservednon-reservedreserved
    DESCRIBE reservedreservedreserved
    DESCRIPTOR non-reservednon-reservedreserved
    DETACHnon-reserved   
    DETERMINISTIC reservedreserved 
    DIAGNOSTICS non-reservednon-reservedreserved
    DICTIONARYnon-reserved   
    DISABLEnon-reserved   
    DISCARDnon-reserved   
    DISCONNECT reservedreservedreserved
    DISPATCH non-reservednon-reserved 
    DISTINCTreservedreservedreservedreserved
    DLNEWCOPY reservedreserved 
    DLPREVIOUSCOPY reservedreserved 
    DLURLCOMPLETE reservedreserved 
    DLURLCOMPLETEONLY reservedreserved 
    DLURLCOMPLETEWRITE reservedreserved 
    DLURLPATH reservedreserved 
    DLURLPATHONLY reservedreserved 
    DLURLPATHWRITE reservedreserved 
    DLURLSCHEME reservedreserved 
    DLURLSERVER reservedreserved 
    DLVALUE reservedreserved 
    DOreserved   
    DOCUMENTnon-reservednon-reservednon-reserved 
    DOMAINnon-reservednon-reservednon-reservedreserved
    DOUBLEnon-reservedreservedreservedreserved
    DROPnon-reservedreservedreservedreserved
    DYNAMIC reservedreserved 
    DYNAMIC_FUNCTION non-reservednon-reservednon-reserved
    DYNAMIC_​FUNCTION_​CODE non-reservednon-reserved 
    EACHnon-reservedreservedreserved 
    ELEMENT reservedreserved 
    ELSEreservedreservedreservedreserved
    EMPTY reservednon-reserved 
    ENABLEnon-reserved   
    ENCODINGnon-reservednon-reservednon-reserved 
    ENCRYPTEDnon-reserved   
    ENDreservedreservedreservedreserved
    END-EXEC reservedreservedreserved
    END_FRAME reservedreserved 
    END_PARTITION reservedreserved 
    ENFORCED non-reservednon-reserved 
    ENUMnon-reserved   
    EQUALS reservedreserved 
    ERROR non-reserved  
    ESCAPEnon-reservedreservedreservedreserved
    EVENTnon-reserved   
    EVERY reservedreserved 
    EXCEPTreservedreservedreservedreserved
    EXCEPTION   reserved
    EXCLUDEnon-reservednon-reservednon-reserved 
    EXCLUDINGnon-reservednon-reservednon-reserved 
    EXCLUSIVEnon-reserved   
    EXEC reservedreservedreserved
    EXECUTEnon-reservedreservedreservedreserved
    EXISTSnon-reserved (cannot be function or type)reservedreservedreserved
    EXP reservedreserved 
    EXPLAINnon-reserved   
    EXPRESSIONnon-reservednon-reservednon-reserved 
    EXTENSIONnon-reserved   
    EXTERNALnon-reservedreservedreservedreserved
    EXTRACTnon-reserved (cannot be function or type)reservedreservedreserved
    FALSEreservedreservedreservedreserved
    FAMILYnon-reserved   
    FETCHreservedreservedreservedreserved
    FILE non-reservednon-reserved 
    FILTERnon-reservedreservedreserved 
    FINAL non-reservednon-reserved 
    FINISH non-reserved  
    FIRSTnon-reservednon-reservednon-reservedreserved
    FIRST_VALUE reservedreserved 
    FLAG non-reservednon-reserved 
    FLOATnon-reserved (cannot be function or type)reservedreservedreserved
    FLOOR reservedreserved 
    FOLLOWINGnon-reservednon-reservednon-reserved 
    FORreservedreservedreservedreserved
    FORCEnon-reserved   
    FOREIGNreservedreservedreservedreserved
    FORMAT non-reserved  
    FORTRAN non-reservednon-reservednon-reserved
    FORWARDnon-reserved   
    FOUND non-reservednon-reservedreserved
    FRAME_ROW reservedreserved 
    FREE reservedreserved 
    FREEZEreserved (can be function or type)   
    FROMreservedreservedreservedreserved
    FS non-reservednon-reserved 
    FULFILL non-reserved  
    FULLreserved (can be function or type)reservedreservedreserved
    FUNCTIONnon-reservedreservedreserved 
    FUNCTIONSnon-reserved   
    FUSION reservedreserved 
    G non-reservednon-reserved 
    GENERAL non-reservednon-reserved 
    GENERATEDnon-reservednon-reservednon-reserved 
    GET reservedreservedreserved
    GLOBALnon-reservedreservedreservedreserved
    GO non-reservednon-reservedreserved
    GOTO non-reservednon-reservedreserved
    GRANTreservedreservedreservedreserved
    GRANTEDnon-reservednon-reservednon-reserved 
    GREATESTnon-reserved (cannot be function or type)   
    GROUPreservedreservedreservedreserved
    GROUPINGnon-reserved (cannot be function or type)reservedreserved 
    GROUPSnon-reservedreservedreserved 
    HANDLERnon-reserved   
    HAVINGreservedreservedreservedreserved
    HEADERnon-reserved   
    HEX non-reservednon-reserved 
    HIERARCHY non-reservednon-reserved 
    HOLDnon-reservedreservedreserved 
    HOURnon-reservedreservedreservedreserved
    ID non-reservednon-reserved 
    IDENTITYnon-reservedreservedreservedreserved
    IFnon-reserved   
    IGNORE non-reservednon-reserved 
    ILIKEreserved (can be function or type)   
    IMMEDIATEnon-reservednon-reservednon-reservedreserved
    IMMEDIATELY non-reservednon-reserved 
    IMMUTABLEnon-reserved   
    IMPLEMENTATION non-reservednon-reserved 
    IMPLICITnon-reserved   
    IMPORTnon-reservedreservedreserved 
    INreservedreservedreservedreserved
    INCLUDEnon-reserved   
    INCLUDINGnon-reservednon-reservednon-reserved 
    INCREMENTnon-reservednon-reservednon-reserved 
    INDENT non-reservednon-reserved 
    INDEXnon-reserved   
    INDEXESnon-reserved   
    INDICATOR reservedreservedreserved
    INHERITnon-reserved   
    INHERITSnon-reserved   
    INITIAL reserved  
    INITIALLYreservednon-reservednon-reservedreserved
    INLINEnon-reserved   
    INNERreserved (can be function or type)reservedreservedreserved
    INOUTnon-reserved (cannot be function or type)reservedreserved 
    INPUTnon-reservednon-reservednon-reservedreserved
    INSENSITIVEnon-reservedreservedreservedreserved
    INSERTnon-reservedreservedreservedreserved
    INSTANCE non-reservednon-reserved 
    INSTANTIABLE non-reservednon-reserved 
    INSTEADnon-reservednon-reservednon-reserved 
    INTnon-reserved (cannot be function or type)reservedreservedreserved
    INTEGERnon-reserved (cannot be function or type)reservedreservedreserved
    INTEGRITY non-reservednon-reserved 
    INTERSECTreservedreservedreservedreserved
    INTERSECTION reservedreserved 
    INTERVALnon-reserved (cannot be function or type)reservedreservedreserved
    INTOreservedreservedreservedreserved
    INVOKERnon-reservednon-reservednon-reserved 
    ISreserved (can be function or type)reservedreservedreserved
    ISNULLreserved (can be function or type)   
    ISOLATIONnon-reservednon-reservednon-reservedreserved
    JOINreserved (can be function or type)reservedreservedreserved
    JSON non-reserved  
    JSON_ARRAY reserved  
    JSON_ARRAYAGG reserved  
    JSON_EXISTS reserved  
    JSON_OBJECT reserved  
    JSON_OBJECTAGG reserved  
    JSON_QUERY reserved  
    JSON_TABLE reserved  
    JSON_TABLE_PRIMITIVE reserved  
    JSON_VALUE reserved  
    K non-reservednon-reserved 
    KEEP non-reserved  
    KEYnon-reservednon-reservednon-reservedreserved
    KEYS non-reserved  
    KEY_MEMBER non-reservednon-reserved 
    KEY_TYPE non-reservednon-reserved 
    LABELnon-reserved   
    LAG reservedreserved 
    LANGUAGEnon-reservedreservedreservedreserved
    LARGEnon-reservedreservedreserved 
    LASTnon-reservednon-reservednon-reservedreserved
    LAST_VALUE reservedreserved 
    LATERALreservedreservedreserved 
    LEAD reservedreserved 
    LEADINGreservedreservedreservedreserved
    LEAKPROOFnon-reserved   
    LEASTnon-reserved (cannot be function or type)   
    LEFTreserved (can be function or type)reservedreservedreserved
    LENGTH non-reservednon-reservednon-reserved
    LEVELnon-reservednon-reservednon-reservedreserved
    LIBRARY non-reservednon-reserved 
    LIKEreserved (can be function or type)reservedreservedreserved
    LIKE_REGEX reservedreserved 
    LIMITreservednon-reservednon-reserved 
    LINK non-reservednon-reserved 
    LISTAGG reserved  
    LISTENnon-reserved   
    LN reservedreserved 
    LOADnon-reserved   
    LOCALnon-reservedreservedreservedreserved
    LOCALTIMEreservedreservedreserved 
    LOCALTIMESTAMPreservedreservedreserved 
    LOCATIONnon-reservednon-reservednon-reserved 
    LOCATOR non-reservednon-reserved 
    LOCKnon-reserved   
    LOCKEDnon-reserved   
    LOG reserved  
    LOG10 reserved  
    LOGGEDnon-reserved   
    LOWER reservedreservedreserved
    M non-reservednon-reserved 
    MAP non-reservednon-reserved 
    MAPPINGnon-reservednon-reservednon-reserved 
    MATCHnon-reservedreservedreservedreserved
    MATCHED non-reservednon-reserved 
    MATCHES reserved  
    MATCH_NUMBER reserved  
    MATCH_RECOGNIZE reserved  
    MATERIALIZEDnon-reserved   
    MAX reservedreservedreserved
    MAXVALUEnon-reservednon-reservednon-reserved 
    MEASURES reserved  
    MEMBER reservedreserved 
    MERGE reservedreserved 
    MESSAGE_LENGTH non-reservednon-reservednon-reserved
    MESSAGE_OCTET_LENGTH non-reservednon-reservednon-reserved
    MESSAGE_TEXT non-reservednon-reservednon-reserved
    METHODnon-reservedreservedreserved 
    MIN reservedreservedreserved
    MINUTEnon-reservedreservedreservedreserved
    MINVALUEnon-reservednon-reservednon-reserved 
    MOD reservedreserved 
    MODEnon-reserved   
    MODIFIES reservedreserved 
    MODULE reservedreservedreserved
    MONTHnon-reservedreservedreservedreserved
    MORE non-reservednon-reservednon-reserved
    MOVEnon-reserved   
    MULTISET reservedreserved 
    MUMPS non-reservednon-reservednon-reserved
    NAMEnon-reservednon-reservednon-reservednon-reserved
    NAMESnon-reservednon-reservednon-reservedreserved
    NAMESPACE non-reservednon-reserved 
    NATIONALnon-reserved (cannot be function or type)reservedreservedreserved
    NATURALreserved (can be function or type)reservedreservedreserved
    NCHARnon-reserved (cannot be function or type)reservedreservedreserved
    NCLOB reservedreserved 
    NESTED non-reserved  
    NESTING non-reservednon-reserved 
    NEWnon-reservedreservedreserved 
    NEXTnon-reservednon-reservednon-reservedreserved
    NFCnon-reservednon-reservednon-reserved 
    NFDnon-reservednon-reservednon-reserved 
    NFKCnon-reservednon-reservednon-reserved 
    NFKDnon-reservednon-reservednon-reserved 
    NIL non-reservednon-reserved 
    NOnon-reservedreservedreservedreserved
    NONEnon-reserved (cannot be function or type)reservedreserved 
    NORMALIZEnon-reserved (cannot be function or type)reservedreserved 
    NORMALIZEDnon-reservednon-reservednon-reserved 
    NOTreservedreservedreservedreserved
    NOTHINGnon-reserved   
    NOTIFYnon-reserved   
    NOTNULLreserved (can be function or type)   
    NOWAITnon-reserved   
    NTH_VALUE reservedreserved 
    NTILE reservedreserved 
    NULLreservedreservedreservedreserved
    NULLABLE non-reservednon-reservednon-reserved
    NULLIFnon-reserved (cannot be function or type)reservedreservedreserved
    NULLSnon-reservednon-reservednon-reserved 
    NUMBER non-reservednon-reservednon-reserved
    NUMERICnon-reserved (cannot be function or type)reservedreservedreserved
    OBJECTnon-reservednon-reservednon-reserved 
    OCCURRENCES_REGEX reservedreserved 
    OCTETS non-reservednon-reserved 
    OCTET_LENGTH reservedreservedreserved
    OFnon-reservedreservedreservedreserved
    OFFnon-reservednon-reservednon-reserved 
    OFFSETreservedreservedreserved 
    OIDSnon-reserved   
    OLDnon-reservedreservedreserved 
    OMIT reserved  
    ONreservedreservedreservedreserved
    ONE reserved  
    ONLYreservedreservedreservedreserved
    OPEN reservedreservedreserved
    OPERATORnon-reserved   
    OPTIONnon-reservednon-reservednon-reservedreserved
    OPTIONSnon-reservednon-reservednon-reserved 
    ORreservedreservedreservedreserved
    ORDERreservedreservedreservedreserved
    ORDERING non-reservednon-reserved 
    ORDINALITYnon-reservednon-reservednon-reserved 
    OTHERSnon-reservednon-reservednon-reserved 
    OUTnon-reserved (cannot be function or type)reservedreserved 
    OUTERreserved (can be function or type)reservedreservedreserved
    OUTPUT non-reservednon-reservedreserved
    OVERnon-reservedreservedreserved 
    OVERFLOW non-reserved  
    OVERLAPSreserved (can be function or type)reservedreservedreserved
    OVERLAYnon-reserved (cannot be function or type)reservedreserved 
    OVERRIDINGnon-reservednon-reservednon-reserved 
    OWNEDnon-reserved   
    OWNERnon-reserved   
    P non-reservednon-reserved 
    PAD non-reservednon-reservedreserved
    PARALLELnon-reserved   
    PARAMETER reservedreserved 
    PARAMETER_MODE non-reservednon-reserved 
    PARAMETER_NAME non-reservednon-reserved 
    PARAMETER_​ORDINAL_​POSITION non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​CATALOG non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​NAME non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​SCHEMA non-reservednon-reserved 
    PARSERnon-reserved   
    PARTIALnon-reservednon-reservednon-reservedreserved
    PARTITIONnon-reservedreservedreserved 
    PASCAL non-reservednon-reservednon-reserved
    PASS non-reserved  
    PASSINGnon-reservednon-reservednon-reserved 
    PASSTHROUGH non-reservednon-reserved 
    PASSWORDnon-reserved   
    PAST non-reserved  
    PATH non-reservednon-reserved 
    PATTERN reserved  
    PER reserved  
    PERCENT reservedreserved 
    PERCENTILE_CONT reservedreserved 
    PERCENTILE_DISC reservedreserved 
    PERCENT_RANK reservedreserved 
    PERIOD reservedreserved 
    PERMISSION non-reservednon-reserved 
    PERMUTE reserved  
    PLACINGreservednon-reservednon-reserved 
    PLAN non-reserved  
    PLANSnon-reserved   
    PLI non-reservednon-reservednon-reserved
    POLICYnon-reserved   
    PORTION reservedreserved 
    POSITIONnon-reserved (cannot be function or type)reservedreservedreserved
    POSITION_REGEX reservedreserved 
    POWER reservedreserved 
    PRECEDES reservedreserved 
    PRECEDINGnon-reservednon-reservednon-reserved 
    PRECISIONnon-reserved (cannot be function or type)reservedreservedreserved
    PREPAREnon-reservedreservedreservedreserved
    PREPAREDnon-reserved   
    PRESERVEnon-reservednon-reservednon-reservedreserved
    PRIMARYreservedreservedreservedreserved
    PRIORnon-reservednon-reservednon-reservedreserved
    PRIVATE non-reserved  
    PRIVILEGESnon-reservednon-reservednon-reservedreserved
    PROCEDURALnon-reserved   
    PROCEDUREnon-reservedreservedreservedreserved
    PROCEDURESnon-reserved   
    PROGRAMnon-reserved   
    PRUNE non-reserved  
    PTF reserved  
    PUBLIC non-reservednon-reservedreserved
    PUBLICATIONnon-reserved   
    QUOTEnon-reserved   
    QUOTES non-reserved  
    RANGEnon-reservedreservedreserved 
    RANK reservedreserved 
    READnon-reservednon-reservednon-reservedreserved
    READS reservedreserved 
    REALnon-reserved (cannot be function or type)reservedreservedreserved
    REASSIGNnon-reserved   
    RECHECKnon-reserved   
    RECOVERY non-reservednon-reserved 
    RECURSIVEnon-reservedreservedreserved 
    REFnon-reservedreservedreserved 
    REFERENCESreservedreservedreservedreserved
    REFERENCINGnon-reservedreservedreserved 
    REFRESHnon-reserved   
    REGR_AVGX reservedreserved 
    REGR_AVGY reservedreserved 
    REGR_COUNT reservedreserved 
    REGR_INTERCEPT reservedreserved 
    REGR_R2 reservedreserved 
    REGR_SLOPE reservedreserved 
    REGR_SXX reservedreserved 
    REGR_SXY reservedreserved 
    REGR_SYY reservedreserved 
    REINDEXnon-reserved   
    RELATIVEnon-reservednon-reservednon-reservedreserved
    RELEASEnon-reservedreservedreserved 
    RENAMEnon-reserved   
    REPEATABLEnon-reservednon-reservednon-reservednon-reserved
    REPLACEnon-reserved   
    REPLICAnon-reserved   
    REQUIRING non-reservednon-reserved 
    RESETnon-reserved   
    RESPECT non-reservednon-reserved 
    RESTARTnon-reservednon-reservednon-reserved 
    RESTORE non-reservednon-reserved 
    RESTRICTnon-reservednon-reservednon-reservedreserved
    RESULT reservedreserved 
    RETURN reservedreserved 
    RETURNED_CARDINALITY non-reservednon-reserved 
    RETURNED_LENGTH non-reservednon-reservednon-reserved
    RETURNED_​OCTET_​LENGTH non-reservednon-reservednon-reserved
    RETURNED_SQLSTATE non-reservednon-reservednon-reserved
    RETURNINGreservednon-reservednon-reserved 
    RETURNSnon-reservedreservedreserved 
    REVOKEnon-reservedreservedreservedreserved
    RIGHTreserved (can be function or type)reservedreservedreserved
    ROLEnon-reservednon-reservednon-reserved 
    ROLLBACKnon-reservedreservedreservedreserved
    ROLLUPnon-reservedreservedreserved 
    ROUTINEnon-reservednon-reservednon-reserved 
    ROUTINESnon-reserved   
    ROUTINE_CATALOG non-reservednon-reserved 
    ROUTINE_NAME non-reservednon-reserved 
    ROUTINE_SCHEMA non-reservednon-reserved 
    ROWnon-reserved (cannot be function or type)reservedreserved 
    ROWSnon-reservedreservedreservedreserved
    ROW_COUNT non-reservednon-reservednon-reserved
    ROW_NUMBER reservedreserved 
    RULEnon-reserved   
    RUNNING reserved  
    SAVEPOINTnon-reservedreservedreserved 
    SCALAR non-reserved  
    SCALE non-reservednon-reservednon-reserved
    SCHEMAnon-reservednon-reservednon-reservedreserved
    SCHEMASnon-reserved   
    SCHEMA_NAME non-reservednon-reservednon-reserved
    SCOPE reservedreserved 
    SCOPE_CATALOG non-reservednon-reserved 
    SCOPE_NAME non-reservednon-reserved 
    SCOPE_SCHEMA non-reservednon-reserved 
    SCROLLnon-reservedreservedreservedreserved
    SEARCHnon-reservedreservedreserved 
    SECONDnon-reservedreservedreservedreserved
    SECTION non-reservednon-reservedreserved
    SECURITYnon-reservednon-reservednon-reserved 
    SEEK reserved  
    SELECTreservedreservedreservedreserved
    SELECTIVE non-reservednon-reserved 
    SELF non-reservednon-reserved 
    SENSITIVE reservedreserved 
    SEQUENCEnon-reservednon-reservednon-reserved 
    SEQUENCESnon-reserved   
    SERIALIZABLEnon-reservednon-reservednon-reservednon-reserved
    SERVERnon-reservednon-reservednon-reserved 
    SERVER_NAME non-reservednon-reservednon-reserved
    SESSIONnon-reservednon-reservednon-reservedreserved
    SESSION_USERreservedreservedreservedreserved
    SETnon-reservedreservedreservedreserved
    SETOFnon-reserved (cannot be function or type)   
    SETSnon-reservednon-reservednon-reserved 
    SHAREnon-reserved   
    SHOWnon-reservedreserved  
    SIMILARreserved (can be function or type)reservedreserved 
    SIMPLEnon-reservednon-reservednon-reserved 
    SIN reserved  
    SINH reserved  
    SIZE non-reservednon-reservedreserved
    SKIPnon-reservedreserved  
    SMALLINTnon-reserved (cannot be function or type)reservedreservedreserved
    SNAPSHOTnon-reserved   
    SOMEreservedreservedreservedreserved
    SOURCE non-reservednon-reserved 
    SPACE non-reservednon-reservedreserved
    SPECIFIC reservedreserved 
    SPECIFICTYPE reservedreserved 
    SPECIFIC_NAME non-reservednon-reserved 
    SQLnon-reservedreservedreservedreserved
    SQLCODE   reserved
    SQLERROR   reserved
    SQLEXCEPTION reservedreserved 
    SQLSTATE reservedreservedreserved
    SQLWARNING reservedreserved 
    SQRT reservedreserved 
    STABLEnon-reserved   
    STANDALONEnon-reservednon-reservednon-reserved 
    STARTnon-reservedreservedreserved 
    STATE non-reservednon-reserved 
    STATEMENTnon-reservednon-reservednon-reserved 
    STATIC reservedreserved 
    STATISTICSnon-reserved   
    STDDEV_POP reservedreserved 
    STDDEV_SAMP reservedreserved 
    STDINnon-reserved   
    STDOUTnon-reserved   
    STORAGEnon-reserved   
    STOREDnon-reserved   
    STRICTnon-reserved   
    STRING non-reserved  
    STRIPnon-reservednon-reservednon-reserved 
    STRUCTURE non-reservednon-reserved 
    STYLE non-reservednon-reserved 
    SUBCLASS_ORIGIN non-reservednon-reservednon-reserved
    SUBMULTISET reservedreserved 
    SUBSCRIPTIONnon-reserved   
    SUBSET reserved  
    SUBSTRINGnon-reserved (cannot be function or type)reservedreservedreserved
    SUBSTRING_REGEX reservedreserved 
    SUCCEEDS reservedreserved 
    SUM reservedreservedreserved
    SUPPORTnon-reserved   
    SYMMETRICreservedreservedreserved 
    SYSIDnon-reserved   
    SYSTEMnon-reservedreservedreserved 
    SYSTEM_TIME reservedreserved 
    SYSTEM_USER reservedreservedreserved
    T non-reservednon-reserved 
    TABLEreservedreservedreservedreserved
    TABLESnon-reserved   
    TABLESAMPLEreserved (can be function or type)reservedreserved 
    TABLESPACEnon-reserved   
    TABLE_NAME non-reservednon-reservednon-reserved
    TAN reserved  
    TANH reserved  
    TEMPnon-reserved   
    TEMPLATEnon-reserved   
    TEMPORARYnon-reservednon-reservednon-reservedreserved
    TEXTnon-reserved   
    THENreservedreservedreservedreserved
    THROUGH non-reserved  
    TIESnon-reservednon-reservednon-reserved 
    TIMEnon-reserved (cannot be function or type)reservedreservedreserved
    TIMESTAMPnon-reserved (cannot be function or type)reservedreservedreserved
    TIMEZONE_HOUR reservedreservedreserved
    TIMEZONE_MINUTE reservedreservedreserved
    TOreservedreservedreservedreserved
    TOKEN non-reservednon-reserved 
    TOP_LEVEL_COUNT non-reservednon-reserved 
    TRAILINGreservedreservedreservedreserved
    TRANSACTIONnon-reservednon-reservednon-reservedreserved
    TRANSACTIONS_​COMMITTED non-reservednon-reserved 
    TRANSACTIONS_​ROLLED_​BACK non-reservednon-reserved 
    TRANSACTION_ACTIVE non-reservednon-reserved 
    TRANSFORMnon-reservednon-reservednon-reserved 
    TRANSFORMS non-reservednon-reserved 
    TRANSLATE reservedreservedreserved
    TRANSLATE_REGEX reservedreserved 
    TRANSLATION reservedreservedreserved
    TREATnon-reserved (cannot be function or type)reservedreserved 
    TRIGGERnon-reservedreservedreserved 
    TRIGGER_CATALOG non-reservednon-reserved 
    TRIGGER_NAME non-reservednon-reserved 
    TRIGGER_SCHEMA non-reservednon-reserved 
    TRIMnon-reserved (cannot be function or type)reservedreservedreserved
    TRIM_ARRAY reservedreserved 
    TRUEreservedreservedreservedreserved
    TRUNCATEnon-reservedreservedreserved 
    TRUSTEDnon-reserved   
    TYPEnon-reservednon-reservednon-reservednon-reserved
    TYPESnon-reserved   
    UESCAPEnon-reservedreservedreserved 
    UNBOUNDEDnon-reservednon-reservednon-reserved 
    UNCOMMITTEDnon-reservednon-reservednon-reservednon-reserved
    UNCONDITIONAL non-reserved  
    UNDER non-reservednon-reserved 
    UNENCRYPTEDnon-reserved   
    UNIONreservedreservedreservedreserved
    UNIQUEreservedreservedreservedreserved
    UNKNOWNnon-reservedreservedreservedreserved
    UNLINK non-reservednon-reserved 
    UNLISTENnon-reserved   
    UNLOGGEDnon-reserved   
    UNMATCHED reserved  
    UNNAMED non-reservednon-reservednon-reserved
    UNNEST reservedreserved 
    UNTILnon-reserved   
    UNTYPED non-reservednon-reserved 
    UPDATEnon-reservedreservedreservedreserved
    UPPER reservedreservedreserved
    URI non-reservednon-reserved 
    USAGE non-reservednon-reservedreserved
    USERreservedreservedreservedreserved
    USER_​DEFINED_​TYPE_​CATALOG non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​CODE non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​NAME non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​SCHEMA non-reservednon-reserved 
    USINGreservedreservedreservedreserved
    UTF16 non-reserved  
    UTF32 non-reserved  
    UTF8 non-reserved  
    VACUUMnon-reserved   
    VALIDnon-reservednon-reservednon-reserved 
    VALIDATEnon-reserved   
    VALIDATORnon-reserved   
    VALUEnon-reservedreservedreservedreserved
    VALUESnon-reserved (cannot be function or type)reservedreservedreserved
    VALUE_OF reservedreserved 
    VARBINARY reservedreserved 
    VARCHARnon-reserved (cannot be function or type)reservedreservedreserved
    VARIADICreserved   
    VARYINGnon-reservedreservedreservedreserved
    VAR_POP reservedreserved 
    VAR_SAMP reservedreserved 
    VERBOSEreserved (can be function or type)   
    VERSIONnon-reservednon-reservednon-reserved 
    VERSIONING reservedreserved 
    VIEWnon-reservednon-reservednon-reservedreserved
    VIEWSnon-reserved   
    VOLATILEnon-reserved   
    WHENreservedreservedreservedreserved
    WHENEVER reservedreservedreserved
    WHEREreservedreservedreservedreserved
    WHITESPACEnon-reservednon-reservednon-reserved 
    WIDTH_BUCKET reservedreserved 
    WINDOWreservedreservedreserved 
    WITHreservedreservedreservedreserved
    WITHINnon-reservedreservedreserved 
    WITHOUTnon-reservedreservedreserved 
    WORKnon-reservednon-reservednon-reservedreserved
    WRAPPERnon-reservednon-reservednon-reserved 
    WRITEnon-reservednon-reservednon-reservedreserved
    XMLnon-reservedreservedreserved 
    XMLAGG reservedreserved 
    XMLATTRIBUTESnon-reserved (cannot be function or type)reservedreserved 
    XMLBINARY reservedreserved 
    XMLCAST reservedreserved 
    XMLCOMMENT reservedreserved 
    XMLCONCATnon-reserved (cannot be function or type)reservedreserved 
    XMLDECLARATION non-reservednon-reserved 
    XMLDOCUMENT reservedreserved 
    XMLELEMENTnon-reserved (cannot be function or type)reservedreserved 
    XMLEXISTSnon-reserved (cannot be function or type)reservedreserved 
    XMLFORESTnon-reserved (cannot be function or type)reservedreserved 
    XMLITERATE reservedreserved 
    XMLNAMESPACESnon-reserved (cannot be function or type)reservedreserved 
    XMLPARSEnon-reserved (cannot be function or type)reservedreserved 
    XMLPInon-reserved (cannot be function or type)reservedreserved 
    XMLQUERY reservedreserved 
    XMLROOTnon-reserved (cannot be function or type)   
    XMLSCHEMA non-reservednon-reserved 
    XMLSERIALIZEnon-reserved (cannot be function or type)reservedreserved 
    XMLTABLEnon-reserved (cannot be function or type)reservedreserved 
    XMLTEXT reservedreserved 
    XMLVALIDATE reservedreserved 
    YEARnon-reservedreservedreservedreserved
    YESnon-reservednon-reservednon-reserved 
    ZONEnon-reservednon-reservednon-reservedreserved

    Prev Up Next
    B.7. Julian Dates Home Appendix D. SQL Conformance
    \ No newline at end of file +

    Table C.1. SQL Key Words

    Key WordPostgreSQLSQL:2016SQL:2011SQL-92
    A non-reservednon-reserved 
    ABORTnon-reserved   
    ABS reservedreserved 
    ABSENT non-reservednon-reserved 
    ABSOLUTEnon-reservednon-reservednon-reservedreserved
    ACCESSnon-reserved   
    ACCORDING non-reservednon-reserved 
    ACOS reserved  
    ACTIONnon-reservednon-reservednon-reservedreserved
    ADA non-reservednon-reservednon-reserved
    ADDnon-reservednon-reservednon-reservedreserved
    ADMINnon-reservednon-reservednon-reserved 
    AFTERnon-reservednon-reservednon-reserved 
    AGGREGATEnon-reserved   
    ALLreservedreservedreservedreserved
    ALLOCATE reservedreservedreserved
    ALSOnon-reserved   
    ALTERnon-reservedreservedreservedreserved
    ALWAYSnon-reservednon-reservednon-reserved 
    ANALYSEreserved   
    ANALYZEreserved   
    ANDreservedreservedreservedreserved
    ANYreservedreservedreservedreserved
    ARE reservedreservedreserved
    ARRAYreservedreservedreserved 
    ARRAY_AGG reservedreserved 
    ARRAY_​MAX_​CARDINALITY reservedreserved 
    ASreservedreservedreservedreserved
    ASCreservednon-reservednon-reservedreserved
    ASENSITIVE reservedreserved 
    ASIN reserved  
    ASSERTIONnon-reservednon-reservednon-reservedreserved
    ASSIGNMENTnon-reservednon-reservednon-reserved 
    ASYMMETRICreservedreservedreserved 
    ATnon-reservedreservedreservedreserved
    ATAN reserved  
    ATOMIC reservedreserved 
    ATTACHnon-reserved   
    ATTRIBUTEnon-reservednon-reservednon-reserved 
    ATTRIBUTES non-reservednon-reserved 
    AUTHORIZATIONreserved (can be function or type)reservedreservedreserved
    AVG reservedreservedreserved
    BACKWARDnon-reserved   
    BASE64 non-reservednon-reserved 
    BEFOREnon-reservednon-reservednon-reserved 
    BEGINnon-reservedreservedreservedreserved
    BEGIN_FRAME reservedreserved 
    BEGIN_PARTITION reservedreserved 
    BERNOULLI non-reservednon-reserved 
    BETWEENnon-reserved (cannot be function or type)reservedreservedreserved
    BIGINTnon-reserved (cannot be function or type)reservedreserved 
    BINARYreserved (can be function or type)reservedreserved 
    BITnon-reserved (cannot be function or type)  reserved
    BIT_LENGTH   reserved
    BLOB reservedreserved 
    BLOCKED non-reservednon-reserved 
    BOM non-reservednon-reserved 
    BOOLEANnon-reserved (cannot be function or type)reservedreserved 
    BOTHreservedreservedreservedreserved
    BREADTH non-reservednon-reserved 
    BYnon-reservedreservedreservedreserved
    C non-reservednon-reservednon-reserved
    CACHEnon-reserved   
    CALLnon-reservedreservedreserved 
    CALLEDnon-reservedreservedreserved 
    CARDINALITY reservedreserved 
    CASCADEnon-reservednon-reservednon-reservedreserved
    CASCADEDnon-reservedreservedreservedreserved
    CASEreservedreservedreservedreserved
    CASTreservedreservedreservedreserved
    CATALOGnon-reservednon-reservednon-reservedreserved
    CATALOG_NAME non-reservednon-reservednon-reserved
    CEIL reservedreserved 
    CEILING reservedreserved 
    CHAINnon-reservednon-reservednon-reserved 
    CHAINING non-reserved  
    CHARnon-reserved (cannot be function or type)reservedreservedreserved
    CHARACTERnon-reserved (cannot be function or type)reservedreservedreserved
    CHARACTERISTICSnon-reservednon-reservednon-reserved 
    CHARACTERS non-reservednon-reserved 
    CHARACTER_LENGTH reservedreservedreserved
    CHARACTER_​SET_​CATALOG non-reservednon-reservednon-reserved
    CHARACTER_SET_NAME non-reservednon-reservednon-reserved
    CHARACTER_SET_SCHEMA non-reservednon-reservednon-reserved
    CHAR_LENGTH reservedreservedreserved
    CHECKreservedreservedreservedreserved
    CHECKPOINTnon-reserved   
    CLASSnon-reserved   
    CLASSIFIER reserved  
    CLASS_ORIGIN non-reservednon-reservednon-reserved
    CLOB reservedreserved 
    CLOSEnon-reservedreservedreservedreserved
    CLUSTERnon-reserved   
    COALESCEnon-reserved (cannot be function or type)reservedreservedreserved
    COBOL non-reservednon-reservednon-reserved
    COLLATEreservedreservedreservedreserved
    COLLATIONreserved (can be function or type)non-reservednon-reservedreserved
    COLLATION_CATALOG non-reservednon-reservednon-reserved
    COLLATION_NAME non-reservednon-reservednon-reserved
    COLLATION_SCHEMA non-reservednon-reservednon-reserved
    COLLECT reservedreserved 
    COLUMNreservedreservedreservedreserved
    COLUMNSnon-reservednon-reservednon-reserved 
    COLUMN_NAME non-reservednon-reservednon-reserved
    COMMAND_FUNCTION non-reservednon-reservednon-reserved
    COMMAND_​FUNCTION_​CODE non-reservednon-reserved 
    COMMENTnon-reserved   
    COMMENTSnon-reserved   
    COMMITnon-reservedreservedreservedreserved
    COMMITTEDnon-reservednon-reservednon-reservednon-reserved
    CONCURRENTLYreserved (can be function or type)   
    CONDITION reservedreserved 
    CONDITIONAL non-reserved  
    CONDITION_NUMBER non-reservednon-reservednon-reserved
    CONFIGURATIONnon-reserved   
    CONFLICTnon-reserved   
    CONNECT reservedreservedreserved
    CONNECTIONnon-reservednon-reservednon-reservedreserved
    CONNECTION_NAME non-reservednon-reservednon-reserved
    CONSTRAINTreservedreservedreservedreserved
    CONSTRAINTSnon-reservednon-reservednon-reservedreserved
    CONSTRAINT_CATALOG non-reservednon-reservednon-reserved
    CONSTRAINT_NAME non-reservednon-reservednon-reserved
    CONSTRAINT_SCHEMA non-reservednon-reservednon-reserved
    CONSTRUCTOR non-reservednon-reserved 
    CONTAINS reservedreserved 
    CONTENTnon-reservednon-reservednon-reserved 
    CONTINUEnon-reservednon-reservednon-reservedreserved
    CONTROL non-reservednon-reserved 
    CONVERSIONnon-reserved   
    CONVERT reservedreservedreserved
    COPYnon-reservedreserved  
    CORR reservedreserved 
    CORRESPONDING reservedreservedreserved
    COS reserved  
    COSH reserved  
    COSTnon-reserved   
    COUNT reservedreservedreserved
    COVAR_POP reservedreserved 
    COVAR_SAMP reservedreserved 
    CREATEreservedreservedreservedreserved
    CROSSreserved (can be function or type)reservedreservedreserved
    CSVnon-reserved   
    CUBEnon-reservedreservedreserved 
    CUME_DIST reservedreserved 
    CURRENTnon-reservedreservedreservedreserved
    CURRENT_CATALOGreservedreservedreserved 
    CURRENT_DATEreservedreservedreservedreserved
    CURRENT_​DEFAULT_​TRANSFORM_​GROUP reservedreserved 
    CURRENT_PATH reservedreserved 
    CURRENT_ROLEreservedreservedreserved 
    CURRENT_ROW reservedreserved 
    CURRENT_SCHEMAreserved (can be function or type)reservedreserved 
    CURRENT_TIMEreservedreservedreservedreserved
    CURRENT_TIMESTAMPreservedreservedreservedreserved
    CURRENT_​TRANSFORM_​GROUP_​FOR_​TYPE reservedreserved 
    CURRENT_USERreservedreservedreservedreserved
    CURSORnon-reservedreservedreservedreserved
    CURSOR_NAME non-reservednon-reservednon-reserved
    CYCLEnon-reservedreservedreserved 
    DATAnon-reservednon-reservednon-reservednon-reserved
    DATABASEnon-reserved   
    DATALINK reservedreserved 
    DATE reservedreservedreserved
    DATETIME_​INTERVAL_​CODE non-reservednon-reservednon-reserved
    DATETIME_​INTERVAL_​PRECISION non-reservednon-reservednon-reserved
    DAYnon-reservedreservedreservedreserved
    DB non-reservednon-reserved 
    DEALLOCATEnon-reservedreservedreservedreserved
    DECnon-reserved (cannot be function or type)reservedreservedreserved
    DECFLOAT reserved  
    DECIMALnon-reserved (cannot be function or type)reservedreservedreserved
    DECLAREnon-reservedreservedreservedreserved
    DEFAULTreservedreservedreservedreserved
    DEFAULTSnon-reservednon-reservednon-reserved 
    DEFERRABLEreservednon-reservednon-reservedreserved
    DEFERREDnon-reservednon-reservednon-reservedreserved
    DEFINE reserved  
    DEFINED non-reservednon-reserved 
    DEFINERnon-reservednon-reservednon-reserved 
    DEGREE non-reservednon-reserved 
    DELETEnon-reservedreservedreservedreserved
    DELIMITERnon-reserved   
    DELIMITERSnon-reserved   
    DENSE_RANK reservedreserved 
    DEPENDSnon-reserved   
    DEPTH non-reservednon-reserved 
    DEREF reservedreserved 
    DERIVED non-reservednon-reserved 
    DESCreservednon-reservednon-reservedreserved
    DESCRIBE reservedreservedreserved
    DESCRIPTOR non-reservednon-reservedreserved
    DETACHnon-reserved   
    DETERMINISTIC reservedreserved 
    DIAGNOSTICS non-reservednon-reservedreserved
    DICTIONARYnon-reserved   
    DISABLEnon-reserved   
    DISCARDnon-reserved   
    DISCONNECT reservedreservedreserved
    DISPATCH non-reservednon-reserved 
    DISTINCTreservedreservedreservedreserved
    DLNEWCOPY reservedreserved 
    DLPREVIOUSCOPY reservedreserved 
    DLURLCOMPLETE reservedreserved 
    DLURLCOMPLETEONLY reservedreserved 
    DLURLCOMPLETEWRITE reservedreserved 
    DLURLPATH reservedreserved 
    DLURLPATHONLY reservedreserved 
    DLURLPATHWRITE reservedreserved 
    DLURLSCHEME reservedreserved 
    DLURLSERVER reservedreserved 
    DLVALUE reservedreserved 
    DOreserved   
    DOCUMENTnon-reservednon-reservednon-reserved 
    DOMAINnon-reservednon-reservednon-reservedreserved
    DOUBLEnon-reservedreservedreservedreserved
    DROPnon-reservedreservedreservedreserved
    DYNAMIC reservedreserved 
    DYNAMIC_FUNCTION non-reservednon-reservednon-reserved
    DYNAMIC_​FUNCTION_​CODE non-reservednon-reserved 
    EACHnon-reservedreservedreserved 
    ELEMENT reservedreserved 
    ELSEreservedreservedreservedreserved
    EMPTY reservednon-reserved 
    ENABLEnon-reserved   
    ENCODINGnon-reservednon-reservednon-reserved 
    ENCRYPTEDnon-reserved   
    ENDreservedreservedreservedreserved
    END-EXEC reservedreservedreserved
    END_FRAME reservedreserved 
    END_PARTITION reservedreserved 
    ENFORCED non-reservednon-reserved 
    ENUMnon-reserved   
    EQUALS reservedreserved 
    ERROR non-reserved  
    ESCAPEnon-reservedreservedreservedreserved
    EVENTnon-reserved   
    EVERY reservedreserved 
    EXCEPTreservedreservedreservedreserved
    EXCEPTION   reserved
    EXCLUDEnon-reservednon-reservednon-reserved 
    EXCLUDINGnon-reservednon-reservednon-reserved 
    EXCLUSIVEnon-reserved   
    EXEC reservedreservedreserved
    EXECUTEnon-reservedreservedreservedreserved
    EXISTSnon-reserved (cannot be function or type)reservedreservedreserved
    EXP reservedreserved 
    EXPLAINnon-reserved   
    EXPRESSIONnon-reservednon-reservednon-reserved 
    EXTENSIONnon-reserved   
    EXTERNALnon-reservedreservedreservedreserved
    EXTRACTnon-reserved (cannot be function or type)reservedreservedreserved
    FALSEreservedreservedreservedreserved
    FAMILYnon-reserved   
    FETCHreservedreservedreservedreserved
    FILE non-reservednon-reserved 
    FILTERnon-reservedreservedreserved 
    FINAL non-reservednon-reserved 
    FINISH non-reserved  
    FIRSTnon-reservednon-reservednon-reservedreserved
    FIRST_VALUE reservedreserved 
    FLAG non-reservednon-reserved 
    FLOATnon-reserved (cannot be function or type)reservedreservedreserved
    FLOOR reservedreserved 
    FOLLOWINGnon-reservednon-reservednon-reserved 
    FORreservedreservedreservedreserved
    FORCEnon-reserved   
    FOREIGNreservedreservedreservedreserved
    FORMAT non-reserved  
    FORTRAN non-reservednon-reservednon-reserved
    FORWARDnon-reserved   
    FOUND non-reservednon-reservedreserved
    FRAME_ROW reservedreserved 
    FREE reservedreserved 
    FREEZEreserved (can be function or type)   
    FROMreservedreservedreservedreserved
    FS non-reservednon-reserved 
    FULFILL non-reserved  
    FULLreserved (can be function or type)reservedreservedreserved
    FUNCTIONnon-reservedreservedreserved 
    FUNCTIONSnon-reserved   
    FUSION reservedreserved 
    G non-reservednon-reserved 
    GENERAL non-reservednon-reserved 
    GENERATEDnon-reservednon-reservednon-reserved 
    GET reservedreservedreserved
    GLOBALnon-reservedreservedreservedreserved
    GO non-reservednon-reservedreserved
    GOTO non-reservednon-reservedreserved
    GRANTreservedreservedreservedreserved
    GRANTEDnon-reservednon-reservednon-reserved 
    GREATESTnon-reserved (cannot be function or type)   
    GROUPreservedreservedreservedreserved
    GROUPINGnon-reserved (cannot be function or type)reservedreserved 
    GROUPSnon-reservedreservedreserved 
    HANDLERnon-reserved   
    HAVINGreservedreservedreservedreserved
    HEADERnon-reserved   
    HEX non-reservednon-reserved 
    HIERARCHY non-reservednon-reserved 
    HOLDnon-reservedreservedreserved 
    HOURnon-reservedreservedreservedreserved
    ID non-reservednon-reserved 
    IDENTITYnon-reservedreservedreservedreserved
    IFnon-reserved   
    IGNORE non-reservednon-reserved 
    ILIKEreserved (can be function or type)   
    IMMEDIATEnon-reservednon-reservednon-reservedreserved
    IMMEDIATELY non-reservednon-reserved 
    IMMUTABLEnon-reserved   
    IMPLEMENTATION non-reservednon-reserved 
    IMPLICITnon-reserved   
    IMPORTnon-reservedreservedreserved 
    INreservedreservedreservedreserved
    INCLUDEnon-reserved   
    INCLUDINGnon-reservednon-reservednon-reserved 
    INCREMENTnon-reservednon-reservednon-reserved 
    INDENT non-reservednon-reserved 
    INDEXnon-reserved   
    INDEXESnon-reserved   
    INDICATOR reservedreservedreserved
    INHERITnon-reserved   
    INHERITSnon-reserved   
    INITIAL reserved  
    INITIALLYreservednon-reservednon-reservedreserved
    INLINEnon-reserved   
    INNERreserved (can be function or type)reservedreservedreserved
    INOUTnon-reserved (cannot be function or type)reservedreserved 
    INPUTnon-reservednon-reservednon-reservedreserved
    INSENSITIVEnon-reservedreservedreservedreserved
    INSERTnon-reservedreservedreservedreserved
    INSTANCE non-reservednon-reserved 
    INSTANTIABLE non-reservednon-reserved 
    INSTEADnon-reservednon-reservednon-reserved 
    INTnon-reserved (cannot be function or type)reservedreservedreserved
    INTEGERnon-reserved (cannot be function or type)reservedreservedreserved
    INTEGRITY non-reservednon-reserved 
    INTERSECTreservedreservedreservedreserved
    INTERSECTION reservedreserved 
    INTERVALnon-reserved (cannot be function or type)reservedreservedreserved
    INTOreservedreservedreservedreserved
    INVOKERnon-reservednon-reservednon-reserved 
    ISreserved (can be function or type)reservedreservedreserved
    ISNULLreserved (can be function or type)   
    ISOLATIONnon-reservednon-reservednon-reservedreserved
    JOINreserved (can be function or type)reservedreservedreserved
    JSON non-reserved  
    JSON_ARRAY reserved  
    JSON_ARRAYAGG reserved  
    JSON_EXISTS reserved  
    JSON_OBJECT reserved  
    JSON_OBJECTAGG reserved  
    JSON_QUERY reserved  
    JSON_TABLE reserved  
    JSON_TABLE_PRIMITIVE reserved  
    JSON_VALUE reserved  
    K non-reservednon-reserved 
    KEEP non-reserved  
    KEYnon-reservednon-reservednon-reservedreserved
    KEYS non-reserved  
    KEY_MEMBER non-reservednon-reserved 
    KEY_TYPE non-reservednon-reserved 
    LABELnon-reserved   
    LAG reservedreserved 
    LANGUAGEnon-reservedreservedreservedreserved
    LARGEnon-reservedreservedreserved 
    LASTnon-reservednon-reservednon-reservedreserved
    LAST_VALUE reservedreserved 
    LATERALreservedreservedreserved 
    LEAD reservedreserved 
    LEADINGreservedreservedreservedreserved
    LEAKPROOFnon-reserved   
    LEASTnon-reserved (cannot be function or type)   
    LEFTreserved (can be function or type)reservedreservedreserved
    LENGTH non-reservednon-reservednon-reserved
    LEVELnon-reservednon-reservednon-reservedreserved
    LIBRARY non-reservednon-reserved 
    LIKEreserved (can be function or type)reservedreservedreserved
    LIKE_REGEX reservedreserved 
    LIMITreservednon-reservednon-reserved 
    LINK non-reservednon-reserved 
    LISTAGG reserved  
    LISTENnon-reserved   
    LN reservedreserved 
    LOADnon-reserved   
    LOCALnon-reservedreservedreservedreserved
    LOCALTIMEreservedreservedreserved 
    LOCALTIMESTAMPreservedreservedreserved 
    LOCATIONnon-reservednon-reservednon-reserved 
    LOCATOR non-reservednon-reserved 
    LOCKnon-reserved   
    LOCKEDnon-reserved   
    LOG reserved  
    LOG10 reserved  
    LOGGEDnon-reserved   
    LOWER reservedreservedreserved
    M non-reservednon-reserved 
    MAP non-reservednon-reserved 
    MAPPINGnon-reservednon-reservednon-reserved 
    MATCHnon-reservedreservedreservedreserved
    MATCHED non-reservednon-reserved 
    MATCHES reserved  
    MATCH_NUMBER reserved  
    MATCH_RECOGNIZE reserved  
    MATERIALIZEDnon-reserved   
    MAX reservedreservedreserved
    MAXVALUEnon-reservednon-reservednon-reserved 
    MEASURES reserved  
    MEMBER reservedreserved 
    MERGE reservedreserved 
    MESSAGE_LENGTH non-reservednon-reservednon-reserved
    MESSAGE_OCTET_LENGTH non-reservednon-reservednon-reserved
    MESSAGE_TEXT non-reservednon-reservednon-reserved
    METHODnon-reservedreservedreserved 
    MIN reservedreservedreserved
    MINUTEnon-reservedreservedreservedreserved
    MINVALUEnon-reservednon-reservednon-reserved 
    MOD reservedreserved 
    MODEnon-reserved   
    MODIFIES reservedreserved 
    MODULE reservedreservedreserved
    MONTHnon-reservedreservedreservedreserved
    MORE non-reservednon-reservednon-reserved
    MOVEnon-reserved   
    MULTISET reservedreserved 
    MUMPS non-reservednon-reservednon-reserved
    NAMEnon-reservednon-reservednon-reservednon-reserved
    NAMESnon-reservednon-reservednon-reservedreserved
    NAMESPACE non-reservednon-reserved 
    NATIONALnon-reserved (cannot be function or type)reservedreservedreserved
    NATURALreserved (can be function or type)reservedreservedreserved
    NCHARnon-reserved (cannot be function or type)reservedreservedreserved
    NCLOB reservedreserved 
    NESTED non-reserved  
    NESTING non-reservednon-reserved 
    NEWnon-reservedreservedreserved 
    NEXTnon-reservednon-reservednon-reservedreserved
    NFCnon-reservednon-reservednon-reserved 
    NFDnon-reservednon-reservednon-reserved 
    NFKCnon-reservednon-reservednon-reserved 
    NFKDnon-reservednon-reservednon-reserved 
    NIL non-reservednon-reserved 
    NOnon-reservedreservedreservedreserved
    NONEnon-reserved (cannot be function or type)reservedreserved 
    NORMALIZEnon-reserved (cannot be function or type)reservedreserved 
    NORMALIZEDnon-reservednon-reservednon-reserved 
    NOTreservedreservedreservedreserved
    NOTHINGnon-reserved   
    NOTIFYnon-reserved   
    NOTNULLreserved (can be function or type)   
    NOWAITnon-reserved   
    NTH_VALUE reservedreserved 
    NTILE reservedreserved 
    NULLreservedreservedreservedreserved
    NULLABLE non-reservednon-reservednon-reserved
    NULLIFnon-reserved (cannot be function or type)reservedreservedreserved
    NULLSnon-reservednon-reservednon-reserved 
    NUMBER non-reservednon-reservednon-reserved
    NUMERICnon-reserved (cannot be function or type)reservedreservedreserved
    OBJECTnon-reservednon-reservednon-reserved 
    OCCURRENCES_REGEX reservedreserved 
    OCTETS non-reservednon-reserved 
    OCTET_LENGTH reservedreservedreserved
    OFnon-reservedreservedreservedreserved
    OFFnon-reservednon-reservednon-reserved 
    OFFSETreservedreservedreserved 
    OIDSnon-reserved   
    OLDnon-reservedreservedreserved 
    OMIT reserved  
    ONreservedreservedreservedreserved
    ONE reserved  
    ONLYreservedreservedreservedreserved
    OPEN reservedreservedreserved
    OPERATORnon-reserved   
    OPTIONnon-reservednon-reservednon-reservedreserved
    OPTIONSnon-reservednon-reservednon-reserved 
    ORreservedreservedreservedreserved
    ORDERreservedreservedreservedreserved
    ORDERING non-reservednon-reserved 
    ORDINALITYnon-reservednon-reservednon-reserved 
    OTHERSnon-reservednon-reservednon-reserved 
    OUTnon-reserved (cannot be function or type)reservedreserved 
    OUTERreserved (can be function or type)reservedreservedreserved
    OUTPUT non-reservednon-reservedreserved
    OVERnon-reservedreservedreserved 
    OVERFLOW non-reserved  
    OVERLAPSreserved (can be function or type)reservedreservedreserved
    OVERLAYnon-reserved (cannot be function or type)reservedreserved 
    OVERRIDINGnon-reservednon-reservednon-reserved 
    OWNEDnon-reserved   
    OWNERnon-reserved   
    P non-reservednon-reserved 
    PAD non-reservednon-reservedreserved
    PARALLELnon-reserved   
    PARAMETER reservedreserved 
    PARAMETER_MODE non-reservednon-reserved 
    PARAMETER_NAME non-reservednon-reserved 
    PARAMETER_​ORDINAL_​POSITION non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​CATALOG non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​NAME non-reservednon-reserved 
    PARAMETER_​SPECIFIC_​SCHEMA non-reservednon-reserved 
    PARSERnon-reserved   
    PARTIALnon-reservednon-reservednon-reservedreserved
    PARTITIONnon-reservedreservedreserved 
    PASCAL non-reservednon-reservednon-reserved
    PASS non-reserved  
    PASSINGnon-reservednon-reservednon-reserved 
    PASSTHROUGH non-reservednon-reserved 
    PASSWORDnon-reserved   
    PAST non-reserved  
    PATH non-reservednon-reserved 
    PATTERN reserved  
    PER reserved  
    PERCENT reservedreserved 
    PERCENTILE_CONT reservedreserved 
    PERCENTILE_DISC reservedreserved 
    PERCENT_RANK reservedreserved 
    PERIOD reservedreserved 
    PERMISSION non-reservednon-reserved 
    PERMUTE reserved  
    PLACINGreservednon-reservednon-reserved 
    PLAN non-reserved  
    PLANSnon-reserved   
    PLI non-reservednon-reservednon-reserved
    POLICYnon-reserved   
    PORTION reservedreserved 
    POSITIONnon-reserved (cannot be function or type)reservedreservedreserved
    POSITION_REGEX reservedreserved 
    POWER reservedreserved 
    PRECEDES reservedreserved 
    PRECEDINGnon-reservednon-reservednon-reserved 
    PRECISIONnon-reserved (cannot be function or type)reservedreservedreserved
    PREPAREnon-reservedreservedreservedreserved
    PREPAREDnon-reserved   
    PRESERVEnon-reservednon-reservednon-reservedreserved
    PRIMARYreservedreservedreservedreserved
    PRIORnon-reservednon-reservednon-reservedreserved
    PRIVATE non-reserved  
    PRIVILEGESnon-reservednon-reservednon-reservedreserved
    PROCEDURALnon-reserved   
    PROCEDUREnon-reservedreservedreservedreserved
    PROCEDURESnon-reserved   
    PROGRAMnon-reserved   
    PRUNE non-reserved  
    PTF reserved  
    PUBLIC non-reservednon-reservedreserved
    PUBLICATIONnon-reserved   
    QUOTEnon-reserved   
    QUOTES non-reserved  
    RANGEnon-reservedreservedreserved 
    RANK reservedreserved 
    READnon-reservednon-reservednon-reservedreserved
    READS reservedreserved 
    REALnon-reserved (cannot be function or type)reservedreservedreserved
    REASSIGNnon-reserved   
    RECHECKnon-reserved   
    RECOVERY non-reservednon-reserved 
    RECURSIVEnon-reservedreservedreserved 
    REFnon-reservedreservedreserved 
    REFERENCESreservedreservedreservedreserved
    REFERENCINGnon-reservedreservedreserved 
    REFRESHnon-reserved   
    REGR_AVGX reservedreserved 
    REGR_AVGY reservedreserved 
    REGR_COUNT reservedreserved 
    REGR_INTERCEPT reservedreserved 
    REGR_R2 reservedreserved 
    REGR_SLOPE reservedreserved 
    REGR_SXX reservedreserved 
    REGR_SXY reservedreserved 
    REGR_SYY reservedreserved 
    REINDEXnon-reserved   
    RELATIVEnon-reservednon-reservednon-reservedreserved
    RELEASEnon-reservedreservedreserved 
    RENAMEnon-reserved   
    REPEATABLEnon-reservednon-reservednon-reservednon-reserved
    REPLACEnon-reserved   
    REPLICAnon-reserved   
    REQUIRING non-reservednon-reserved 
    RESETnon-reserved   
    RESPECT non-reservednon-reserved 
    RESTARTnon-reservednon-reservednon-reserved 
    RESTORE non-reservednon-reserved 
    RESTRICTnon-reservednon-reservednon-reservedreserved
    RESULT reservedreserved 
    RETURN reservedreserved 
    RETURNED_CARDINALITY non-reservednon-reserved 
    RETURNED_LENGTH non-reservednon-reservednon-reserved
    RETURNED_​OCTET_​LENGTH non-reservednon-reservednon-reserved
    RETURNED_SQLSTATE non-reservednon-reservednon-reserved
    RETURNINGreservednon-reservednon-reserved 
    RETURNSnon-reservedreservedreserved 
    REVOKEnon-reservedreservedreservedreserved
    RIGHTreserved (can be function or type)reservedreservedreserved
    ROLEnon-reservednon-reservednon-reserved 
    ROLLBACKnon-reservedreservedreservedreserved
    ROLLUPnon-reservedreservedreserved 
    ROUTINEnon-reservednon-reservednon-reserved 
    ROUTINESnon-reserved   
    ROUTINE_CATALOG non-reservednon-reserved 
    ROUTINE_NAME non-reservednon-reserved 
    ROUTINE_SCHEMA non-reservednon-reserved 
    ROWnon-reserved (cannot be function or type)reservedreserved 
    ROWSnon-reservedreservedreservedreserved
    ROW_COUNT non-reservednon-reservednon-reserved
    ROW_NUMBER reservedreserved 
    RULEnon-reserved   
    RUNNING reserved  
    SAVEPOINTnon-reservedreservedreserved 
    SCALAR non-reserved  
    SCALE non-reservednon-reservednon-reserved
    SCHEMAnon-reservednon-reservednon-reservedreserved
    SCHEMASnon-reserved   
    SCHEMA_NAME non-reservednon-reservednon-reserved
    SCOPE reservedreserved 
    SCOPE_CATALOG non-reservednon-reserved 
    SCOPE_NAME non-reservednon-reserved 
    SCOPE_SCHEMA non-reservednon-reserved 
    SCROLLnon-reservedreservedreservedreserved
    SEARCHnon-reservedreservedreserved 
    SECONDnon-reservedreservedreservedreserved
    SECTION non-reservednon-reservedreserved
    SECURITYnon-reservednon-reservednon-reserved 
    SEEK reserved  
    SELECTreservedreservedreservedreserved
    SELECTIVE non-reservednon-reserved 
    SELF non-reservednon-reserved 
    SENSITIVE reservedreserved 
    SEQUENCEnon-reservednon-reservednon-reserved 
    SEQUENCESnon-reserved   
    SERIALIZABLEnon-reservednon-reservednon-reservednon-reserved
    SERVERnon-reservednon-reservednon-reserved 
    SERVER_NAME non-reservednon-reservednon-reserved
    SESSIONnon-reservednon-reservednon-reservedreserved
    SESSION_USERreservedreservedreservedreserved
    SETnon-reservedreservedreservedreserved
    SETOFnon-reserved (cannot be function or type)   
    SETSnon-reservednon-reservednon-reserved 
    SHAREnon-reserved   
    SHOWnon-reservedreserved  
    SIMILARreserved (can be function or type)reservedreserved 
    SIMPLEnon-reservednon-reservednon-reserved 
    SIN reserved  
    SINH reserved  
    SIZE non-reservednon-reservedreserved
    SKIPnon-reservedreserved  
    SMALLINTnon-reserved (cannot be function or type)reservedreservedreserved
    SNAPSHOTnon-reserved   
    SOMEreservedreservedreservedreserved
    SOURCE non-reservednon-reserved 
    SPACE non-reservednon-reservedreserved
    SPECIFIC reservedreserved 
    SPECIFICTYPE reservedreserved 
    SPECIFIC_NAME non-reservednon-reserved 
    SQLnon-reservedreservedreservedreserved
    SQLCODE   reserved
    SQLERROR   reserved
    SQLEXCEPTION reservedreserved 
    SQLSTATE reservedreservedreserved
    SQLWARNING reservedreserved 
    SQRT reservedreserved 
    STABLEnon-reserved   
    STANDALONEnon-reservednon-reservednon-reserved 
    STARTnon-reservedreservedreserved 
    STATE non-reservednon-reserved 
    STATEMENTnon-reservednon-reservednon-reserved 
    STATIC reservedreserved 
    STATISTICSnon-reserved   
    STDDEV_POP reservedreserved 
    STDDEV_SAMP reservedreserved 
    STDINnon-reserved   
    STDOUTnon-reserved   
    STORAGEnon-reserved   
    STOREDnon-reserved   
    STRICTnon-reserved   
    STRING non-reserved  
    STRIPnon-reservednon-reservednon-reserved 
    STRUCTURE non-reservednon-reserved 
    STYLE non-reservednon-reserved 
    SUBCLASS_ORIGIN non-reservednon-reservednon-reserved
    SUBMULTISET reservedreserved 
    SUBSCRIPTIONnon-reserved   
    SUBSET reserved  
    SUBSTRINGnon-reserved (cannot be function or type)reservedreservedreserved
    SUBSTRING_REGEX reservedreserved 
    SUCCEEDS reservedreserved 
    SUM reservedreservedreserved
    SUPPORTnon-reserved   
    SYMMETRICreservedreservedreserved 
    SYSIDnon-reserved   
    SYSTEMnon-reservedreservedreserved 
    SYSTEM_TIME reservedreserved 
    SYSTEM_USER reservedreservedreserved
    T non-reservednon-reserved 
    TABLEreservedreservedreservedreserved
    TABLESnon-reserved   
    TABLESAMPLEreserved (can be function or type)reservedreserved 
    TABLESPACEnon-reserved   
    TABLE_NAME non-reservednon-reservednon-reserved
    TAN reserved  
    TANH reserved  
    TEMPnon-reserved   
    TEMPLATEnon-reserved   
    TEMPORARYnon-reservednon-reservednon-reservedreserved
    TEXTnon-reserved   
    THENreservedreservedreservedreserved
    THROUGH non-reserved  
    TIESnon-reservednon-reservednon-reserved 
    TIMEnon-reserved (cannot be function or type)reservedreservedreserved
    TIMESTAMPnon-reserved (cannot be function or type)reservedreservedreserved
    TIMEZONE_HOUR reservedreservedreserved
    TIMEZONE_MINUTE reservedreservedreserved
    TOreservedreservedreservedreserved
    TOKEN non-reservednon-reserved 
    TOP_LEVEL_COUNT non-reservednon-reserved 
    TRAILINGreservedreservedreservedreserved
    TRANSACTIONnon-reservednon-reservednon-reservedreserved
    TRANSACTIONS_​COMMITTED non-reservednon-reserved 
    TRANSACTIONS_​ROLLED_​BACK non-reservednon-reserved 
    TRANSACTION_ACTIVE non-reservednon-reserved 
    TRANSFORMnon-reservednon-reservednon-reserved 
    TRANSFORMS non-reservednon-reserved 
    TRANSLATE reservedreservedreserved
    TRANSLATE_REGEX reservedreserved 
    TRANSLATION reservedreservedreserved
    TREATnon-reserved (cannot be function or type)reservedreserved 
    TRIGGERnon-reservedreservedreserved 
    TRIGGER_CATALOG non-reservednon-reserved 
    TRIGGER_NAME non-reservednon-reserved 
    TRIGGER_SCHEMA non-reservednon-reserved 
    TRIMnon-reserved (cannot be function or type)reservedreservedreserved
    TRIM_ARRAY reservedreserved 
    TRUEreservedreservedreservedreserved
    TRUNCATEnon-reservedreservedreserved 
    TRUSTEDnon-reserved   
    TYPEnon-reservednon-reservednon-reservednon-reserved
    TYPESnon-reserved   
    UESCAPEnon-reservedreservedreserved 
    UNBOUNDEDnon-reservednon-reservednon-reserved 
    UNCOMMITTEDnon-reservednon-reservednon-reservednon-reserved
    UNCONDITIONAL non-reserved  
    UNDER non-reservednon-reserved 
    UNENCRYPTEDnon-reserved   
    UNIONreservedreservedreservedreserved
    UNIQUEreservedreservedreservedreserved
    UNKNOWNnon-reservedreservedreservedreserved
    UNLINK non-reservednon-reserved 
    UNLISTENnon-reserved   
    UNLOGGEDnon-reserved   
    UNMATCHED reserved  
    UNNAMED non-reservednon-reservednon-reserved
    UNNEST reservedreserved 
    UNTILnon-reserved   
    UNTYPED non-reservednon-reserved 
    UPDATEnon-reservedreservedreservedreserved
    UPPER reservedreservedreserved
    URI non-reservednon-reserved 
    USAGE non-reservednon-reservedreserved
    USERreservedreservedreservedreserved
    USER_​DEFINED_​TYPE_​CATALOG non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​CODE non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​NAME non-reservednon-reserved 
    USER_​DEFINED_​TYPE_​SCHEMA non-reservednon-reserved 
    USINGreservedreservedreservedreserved
    UTF16 non-reserved  
    UTF32 non-reserved  
    UTF8 non-reserved  
    VACUUMnon-reserved   
    VALIDnon-reservednon-reservednon-reserved 
    VALIDATEnon-reserved   
    VALIDATORnon-reserved   
    VALUEnon-reservedreservedreservedreserved
    VALUESnon-reserved (cannot be function or type)reservedreservedreserved
    VALUE_OF reservedreserved 
    VARBINARY reservedreserved 
    VARCHARnon-reserved (cannot be function or type)reservedreservedreserved
    VARIADICreserved   
    VARYINGnon-reservedreservedreservedreserved
    VAR_POP reservedreserved 
    VAR_SAMP reservedreserved 
    VERBOSEreserved (can be function or type)   
    VERSIONnon-reservednon-reservednon-reserved 
    VERSIONING reservedreserved 
    VIEWnon-reservednon-reservednon-reservedreserved
    VIEWSnon-reserved   
    VOLATILEnon-reserved   
    WHENreservedreservedreservedreserved
    WHENEVER reservedreservedreserved
    WHEREreservedreservedreservedreserved
    WHITESPACEnon-reservednon-reservednon-reserved 
    WIDTH_BUCKET reservedreserved 
    WINDOWreservedreservedreserved 
    WITHreservedreservedreservedreserved
    WITHINnon-reservedreservedreserved 
    WITHOUTnon-reservedreservedreserved 
    WORKnon-reservednon-reservednon-reservedreserved
    WRAPPERnon-reservednon-reservednon-reserved 
    WRITEnon-reservednon-reservednon-reservedreserved
    XMLnon-reservedreservedreserved 
    XMLAGG reservedreserved 
    XMLATTRIBUTESnon-reserved (cannot be function or type)reservedreserved 
    XMLBINARY reservedreserved 
    XMLCAST reservedreserved 
    XMLCOMMENT reservedreserved 
    XMLCONCATnon-reserved (cannot be function or type)reservedreserved 
    XMLDECLARATION non-reservednon-reserved 
    XMLDOCUMENT reservedreserved 
    XMLELEMENTnon-reserved (cannot be function or type)reservedreserved 
    XMLEXISTSnon-reserved (cannot be function or type)reservedreserved 
    XMLFORESTnon-reserved (cannot be function or type)reservedreserved 
    XMLITERATE reservedreserved 
    XMLNAMESPACESnon-reserved (cannot be function or type)reservedreserved 
    XMLPARSEnon-reserved (cannot be function or type)reservedreserved 
    XMLPInon-reserved (cannot be function or type)reservedreserved 
    XMLQUERY reservedreserved 
    XMLROOTnon-reserved (cannot be function or type)   
    XMLSCHEMA non-reservednon-reserved 
    XMLSERIALIZEnon-reserved (cannot be function or type)reservedreserved 
    XMLTABLEnon-reserved (cannot be function or type)reservedreserved 
    XMLTEXT reservedreserved 
    XMLVALIDATE reservedreserved 
    YEARnon-reservedreservedreservedreserved
    YESnon-reservednon-reservednon-reserved 
    ZONEnon-reservednon-reservednon-reservedreserved

    Prev Up Next
    B.7. Julian Dates Home Appendix D. SQL Conformance
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-listen.html postgresql-13-13.12/doc/src/sgml/html/sql-listen.html --- postgresql-13-13.11/doc/src/sgml/html/sql-listen.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-listen.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -LISTEN
    LISTEN
    Prev UpSQL CommandsHome Next

    LISTEN

    LISTEN — listen for a notification

    Synopsis

    +LISTEN
    LISTEN
    Prev UpSQL CommandsHome Next
    LISTEN
    LISTEN — listen for a notification
    Synopsis
     LISTEN channel
 
    Description
    
    LISTEN registers the current session as a
@@ -67,4 +67,4 @@

    Compatibility

    There is no LISTEN statement in the SQL standard. -

    See Also

    NOTIFY, UNLISTEN
    Prev Up Next
    INSERT Home LOAD
    \ No newline at end of file +

    See Also

    NOTIFY, UNLISTEN
    Prev Up Next
    INSERT Home LOAD
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-load.html postgresql-13-13.12/doc/src/sgml/html/sql-load.html --- postgresql-13-13.11/doc/src/sgml/html/sql-load.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-load.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -LOAD
    LOAD
    Prev UpSQL CommandsHome Next

    LOAD

    LOAD — load a shared library file

    Synopsis

    +LOAD
    LOAD
    Prev UpSQL CommandsHome Next
    LOAD
    LOAD — load a shared library file
    Synopsis
     LOAD 'filename'
 
    Description
    
    This command loads a shared library file into the PostgreSQL
@@ -28,4 +28,4 @@
    extension.
   
    See Also
    
    CREATE FUNCTION
-  
    Prev Up Next
    LISTEN Home LOCK
    
\ No newline at end of file
+
    Prev Up Next
    LISTEN Home LOCK
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-lock.html postgresql-13-13.12/doc/src/sgml/html/sql-lock.html --- postgresql-13-13.11/doc/src/sgml/html/sql-lock.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-lock.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -LOCK
    LOCK
    Prev UpSQL CommandsHome Next

    LOCK

    LOCK — lock a table

    Synopsis

    +LOCK
    LOCK
    Prev UpSQL CommandsHome Next
    LOCK
    LOCK — lock a table
    Synopsis
     LOCK [ TABLE ] [ ONLY ] name [ * ] [, ...] [ IN lockmode MODE ] [ NOWAIT ]
 
 where lockmode is one of:
@@ -159,4 +159,4 @@
    PostgreSQL lock modes and the
    LOCK TABLE syntax are compatible with those
    present in Oracle.
-  
    Prev Up Next
    LOAD Home MOVE
    
\ No newline at end of file
+
    Prev Up Next
    LOAD Home MOVE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-move.html postgresql-13-13.12/doc/src/sgml/html/sql-move.html --- postgresql-13-13.11/doc/src/sgml/html/sql-move.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-move.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -MOVE
    MOVE
    Prev UpSQL CommandsHome Next

    MOVE

    MOVE — position a cursor

    Synopsis

    +MOVE
    MOVE
    Prev UpSQL CommandsHome Next
    MOVE
    MOVE — position a cursor
    Synopsis
     MOVE [ direction ] [ FROM | IN ] cursor_name
 
 where direction can be one of:
@@ -56,4 +56,4 @@
 COMMIT WORK;
 
    Compatibility
    
    There is no MOVE statement in the SQL standard.
-  
    See Also
    CLOSE, DECLARE, FETCH
    Prev Up Next
    LOCK Home NOTIFY
    
\ No newline at end of file
+

    See Also

    CLOSE, DECLARE, FETCH
    Prev Up Next
    LOCK Home NOTIFY
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-notify.html postgresql-13-13.12/doc/src/sgml/html/sql-notify.html --- postgresql-13-13.11/doc/src/sgml/html/sql-notify.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-notify.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -NOTIFY
    NOTIFY
    Prev UpSQL CommandsHome Next

    NOTIFY

    NOTIFY — generate a notification

    Synopsis

    +NOTIFY
    NOTIFY
    Prev UpSQL CommandsHome Next
    NOTIFY
    NOTIFY — generate a notification
    Synopsis
     NOTIFY channel [ , payload ]
 
    Description
    
    The NOTIFY command sends a notification event together
@@ -129,4 +129,4 @@

    Compatibility

    There is no NOTIFY statement in the SQL standard. -

    See Also

    LISTEN, UNLISTEN
    Prev Up Next
    MOVE Home PREPARE
    \ No newline at end of file +

    See Also

    LISTEN, UNLISTEN
    Prev Up Next
    MOVE Home PREPARE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-prepare-transaction.html postgresql-13-13.12/doc/src/sgml/html/sql-prepare-transaction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-prepare-transaction.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-prepare-transaction.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -PREPARE TRANSACTION
    PREPARE TRANSACTION
    Prev UpSQL CommandsHome Next

    PREPARE TRANSACTION

    PREPARE TRANSACTION — prepare the current transaction for two-phase commit

    Synopsis

    +PREPARE TRANSACTION
    PREPARE TRANSACTION
    Prev UpSQL CommandsHome Next
    PREPARE TRANSACTION
    PREPARE TRANSACTION — prepare the current transaction for two-phase commit
    Synopsis
     PREPARE TRANSACTION transaction_id
 
    Description
    
    PREPARE TRANSACTION prepares the current transaction
@@ -87,4 +87,4 @@
    external transaction management systems, some of which are covered by
    standards (such as X/Open XA), but the SQL side of those systems is not
    standardized.
-  
    Prev Up Next
    PREPARE Home REASSIGN OWNED
    
\ No newline at end of file
+
    Prev Up Next
    PREPARE Home REASSIGN OWNED
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-prepare.html postgresql-13-13.12/doc/src/sgml/html/sql-prepare.html --- postgresql-13-13.11/doc/src/sgml/html/sql-prepare.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-prepare.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -PREPARE
    PREPARE
    Prev UpSQL CommandsHome Next

    PREPARE

    PREPARE — prepare a statement for execution

    Synopsis

    +PREPARE
    PREPARE
    Prev UpSQL CommandsHome Next
    PREPARE
    PREPARE — prepare a statement for execution
    Synopsis
     PREPARE name [ ( data_type [, ...] ) ] AS statement
 
    Description
    
    PREPARE creates a prepared statement. A prepared
@@ -146,4 +146,4 @@
    but it is only for use in embedded SQL. This version of the
    PREPARE statement also uses a somewhat different
    syntax.
-  
    Prev Up Next
    NOTIFY Home PREPARE TRANSACTION
    
\ No newline at end of file
+
    Prev Up Next
    NOTIFY Home PREPARE TRANSACTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-reassign-owned.html postgresql-13-13.12/doc/src/sgml/html/sql-reassign-owned.html --- postgresql-13-13.11/doc/src/sgml/html/sql-reassign-owned.html 2023-05-08 21:34:06.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-reassign-owned.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -REASSIGN OWNED
    REASSIGN OWNED
    Prev UpSQL CommandsHome Next

    REASSIGN OWNED

    REASSIGN OWNED — change the ownership of database objects owned by a database role

    Synopsis

    +REASSIGN OWNED
    REASSIGN OWNED
    Prev UpSQL CommandsHome Next
    REASSIGN OWNED
    REASSIGN OWNED — change the ownership of database objects owned by a database role
    Synopsis
     REASSIGN OWNED BY { old_role | CURRENT_USER | SESSION_USER } [, ...]
                TO { new_role | CURRENT_USER | SESSION_USER }
 
    Description
    
@@ -39,4 +39,4 @@
   
    Compatibility
    
    The REASSIGN OWNED command is a
    PostgreSQL extension.
-  
    Prev Up Next
    PREPARE TRANSACTION Home REFRESH MATERIALIZED VIEW
    
\ No newline at end of file
+
    Prev Up Next
    PREPARE TRANSACTION Home REFRESH MATERIALIZED VIEW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-refreshmaterializedview.html postgresql-13-13.12/doc/src/sgml/html/sql-refreshmaterializedview.html --- postgresql-13-13.11/doc/src/sgml/html/sql-refreshmaterializedview.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-refreshmaterializedview.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -REFRESH MATERIALIZED VIEW
    REFRESH MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next

    REFRESH MATERIALIZED VIEW

    REFRESH MATERIALIZED VIEW — replace the contents of a materialized view

    Synopsis

    +REFRESH MATERIALIZED VIEW
    REFRESH MATERIALIZED VIEW
    Prev UpSQL CommandsHome Next
    REFRESH MATERIALIZED VIEW
    REFRESH MATERIALIZED VIEW — replace the contents of a materialized view
    Synopsis
     REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] name
     [ WITH [ NO ] DATA ]
 
    Description
    
@@ -56,4 +56,4 @@

    Compatibility

    REFRESH MATERIALIZED VIEW is a PostgreSQL extension. -

    Prev Up Next
    REASSIGN OWNED Home REINDEX
    \ No newline at end of file +

    Prev Up Next
    REASSIGN OWNED Home REINDEX
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-reindex.html postgresql-13-13.12/doc/src/sgml/html/sql-reindex.html --- postgresql-13-13.11/doc/src/sgml/html/sql-reindex.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-reindex.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -REINDEX
    REINDEX
    Prev UpSQL CommandsHome Next

    REINDEX

    REINDEX — rebuild indexes

    Synopsis

    +REINDEX
    REINDEX
    Prev UpSQL CommandsHome Next
    REINDEX
    REINDEX — rebuild indexes
    Synopsis
     REINDEX [ ( option [, ...] ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURRENTLY ] name
 
 where option can be one of:
@@ -279,4 +279,4 @@
 REINDEX TABLE CONCURRENTLY my_broken_table;
 
    Compatibility
    
    There is no REINDEX command in the SQL standard.
-  
    Prev Up Next
    REFRESH MATERIALIZED VIEW Home RELEASE SAVEPOINT
    
\ No newline at end of file
+
    Prev Up Next
    REFRESH MATERIALIZED VIEW Home RELEASE SAVEPOINT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-release-savepoint.html postgresql-13-13.12/doc/src/sgml/html/sql-release-savepoint.html --- postgresql-13-13.11/doc/src/sgml/html/sql-release-savepoint.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-release-savepoint.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -RELEASE SAVEPOINT
    RELEASE SAVEPOINT
    Prev UpSQL CommandsHome Next

    RELEASE SAVEPOINT

    RELEASE SAVEPOINT — destroy a previously defined savepoint

    Synopsis

    +RELEASE SAVEPOINT
    RELEASE SAVEPOINT
    Prev UpSQL CommandsHome Next
    RELEASE SAVEPOINT
    RELEASE SAVEPOINT — destroy a previously defined savepoint
    Synopsis
     RELEASE [ SAVEPOINT ] savepoint_name
 
    Description
    
    RELEASE SAVEPOINT destroys a savepoint previously defined
@@ -42,4 +42,4 @@
    specifies that the key word SAVEPOINT is
    mandatory, but PostgreSQL allows it to
    be omitted.
-  
    Prev Up Next
    REINDEX Home RESET
    
\ No newline at end of file
+
    Prev Up Next
    REINDEX Home RESET
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-reset.html postgresql-13-13.12/doc/src/sgml/html/sql-reset.html --- postgresql-13-13.11/doc/src/sgml/html/sql-reset.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-reset.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -RESET
    RESET
    Prev UpSQL CommandsHome Next

    RESET

    RESET — restore the value of a run-time parameter to the default value

    Synopsis

    +RESET
    RESET
    Prev UpSQL CommandsHome Next
    RESET
    RESET — restore the value of a run-time parameter to the default value
    Synopsis
     RESET configuration_parameter
 RESET ALL
 
    Description
    
@@ -36,4 +36,4 @@
 RESET timezone;

    Compatibility

    RESET is a PostgreSQL extension. -

    See Also

    SET, SHOW
    Prev Up Next
    RELEASE SAVEPOINT Home REVOKE
    \ No newline at end of file +

    See Also

    SET, SHOW
    Prev Up Next
    RELEASE SAVEPOINT Home REVOKE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-revoke.html postgresql-13-13.12/doc/src/sgml/html/sql-revoke.html --- postgresql-13-13.11/doc/src/sgml/html/sql-revoke.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-revoke.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -REVOKE
    REVOKE
    Prev UpSQL CommandsHome Next

    REVOKE

    REVOKE — remove access privileges

    Synopsis

    +REVOKE
    REVOKE
    Prev UpSQL CommandsHome Next
    REVOKE
    REVOKE — remove access privileges
    Synopsis
     REVOKE [ GRANT OPTION FOR ]
     { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER }
     [, ...] | ALL [ PRIVILEGES ] }
@@ -225,4 +225,4 @@
     The keyword RESTRICT or CASCADE
     is required according to the standard, but PostgreSQL
     assumes RESTRICT by default.
-   
    Prev Up Next
    RESET Home ROLLBACK
    
\ No newline at end of file
+
    Prev Up Next
    RESET Home ROLLBACK
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-rollback-prepared.html postgresql-13-13.12/doc/src/sgml/html/sql-rollback-prepared.html --- postgresql-13-13.11/doc/src/sgml/html/sql-rollback-prepared.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-rollback-prepared.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -ROLLBACK PREPARED
    ROLLBACK PREPARED
    Prev UpSQL CommandsHome Next

    ROLLBACK PREPARED

    ROLLBACK PREPARED — cancel a transaction that was earlier prepared for two-phase commit

    Synopsis

    +ROLLBACK PREPARED
    ROLLBACK PREPARED
    Prev UpSQL CommandsHome Next
    ROLLBACK PREPARED
    ROLLBACK PREPARED — cancel a transaction that was earlier prepared for two-phase commit
    Synopsis
     ROLLBACK PREPARED transaction_id
 
    Description
    
    ROLLBACK PREPARED rolls back a transaction that is in
@@ -30,4 +30,4 @@
    external transaction management systems, some of which are covered by
    standards (such as X/Open XA), but the SQL side of those systems is not
    standardized.
-  
    Prev Up Next
    ROLLBACK Home ROLLBACK TO SAVEPOINT
    
\ No newline at end of file
+
    Prev Up Next
    ROLLBACK Home ROLLBACK TO SAVEPOINT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-rollback-to.html postgresql-13-13.12/doc/src/sgml/html/sql-rollback-to.html --- postgresql-13-13.11/doc/src/sgml/html/sql-rollback-to.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-rollback-to.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -ROLLBACK TO SAVEPOINT
    ROLLBACK TO SAVEPOINT
    Prev UpSQL CommandsHome Next

    ROLLBACK TO SAVEPOINT

    ROLLBACK TO SAVEPOINT — roll back to a savepoint

    Synopsis

    +ROLLBACK TO SAVEPOINT
    ROLLBACK TO SAVEPOINT
    Prev UpSQL CommandsHome Next
    ROLLBACK TO SAVEPOINT
    ROLLBACK TO SAVEPOINT — roll back to a savepoint
    Synopsis
     ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name
 
    Description
    
    Roll back all commands that were executed after the savepoint was
@@ -68,4 +68,4 @@
    AND [ NO ] CHAIN which is not currently supported by
    PostgreSQL.  Otherwise, this command conforms to
    the SQL standard.
-  
    Prev Up Next
    ROLLBACK PREPARED Home SAVEPOINT
    
\ No newline at end of file
+
    Prev Up Next
    ROLLBACK PREPARED Home SAVEPOINT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-rollback.html postgresql-13-13.12/doc/src/sgml/html/sql-rollback.html --- postgresql-13-13.11/doc/src/sgml/html/sql-rollback.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-rollback.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -ROLLBACK
    ROLLBACK
    Prev UpSQL CommandsHome Next

    ROLLBACK

    ROLLBACK — abort the current transaction

    Synopsis

    +ROLLBACK
    ROLLBACK
    Prev UpSQL CommandsHome Next
    ROLLBACK
    ROLLBACK — abort the current transaction
    Synopsis
     ROLLBACK [ WORK | TRANSACTION ] [ AND [ NO ] CHAIN ]
 
    Description
    
    ROLLBACK rolls back the current transaction and causes
@@ -24,4 +24,4 @@

    Compatibility

    The command ROLLBACK conforms to the SQL standard. The form ROLLBACK TRANSACTION is a PostgreSQL extension. -

    Prev Up Next
    REVOKE Home ROLLBACK PREPARED
    \ No newline at end of file +

    Prev Up Next
    REVOKE Home ROLLBACK PREPARED
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-savepoint.html postgresql-13-13.12/doc/src/sgml/html/sql-savepoint.html --- postgresql-13-13.11/doc/src/sgml/html/sql-savepoint.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-savepoint.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -SAVEPOINT
    SAVEPOINT
    Prev UpSQL CommandsHome Next

    SAVEPOINT

    SAVEPOINT — define a new savepoint within the current transaction

    Synopsis

    +SAVEPOINT
    SAVEPOINT
    Prev UpSQL CommandsHome Next
    SAVEPOINT
    SAVEPOINT — define a new savepoint within the current transaction
    Synopsis
     SAVEPOINT savepoint_name
 
    Description
    
    SAVEPOINT establishes a new savepoint within
@@ -76,4 +76,4 @@
    to again become accessible to ROLLBACK TO SAVEPOINT and
    RELEASE SAVEPOINT.) Otherwise, SAVEPOINT is
    fully SQL conforming.
-  
    Prev Up Next
    ROLLBACK TO SAVEPOINT Home SECURITY LABEL
    
\ No newline at end of file
+
    Prev Up Next
    ROLLBACK TO SAVEPOINT Home SECURITY LABEL
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-security-label.html postgresql-13-13.12/doc/src/sgml/html/sql-security-label.html --- postgresql-13-13.11/doc/src/sgml/html/sql-security-label.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-security-label.html 2023-08-07 20:32:26.000000000 +0000 @@ -1,5 +1,5 @@ -SECURITY LABEL
    SECURITY LABEL
    Prev UpSQL CommandsHome Next

    SECURITY LABEL

    SECURITY LABEL — define or change a security label applied to an object

    Synopsis

    +SECURITY LABEL
    SECURITY LABEL
    Prev UpSQL CommandsHome Next
    SECURITY LABEL
    SECURITY LABEL — define or change a security label applied to an object
    Synopsis
     SECURITY LABEL [ FOR provider ] ON
 {
   TABLE object_name |
@@ -99,4 +99,4 @@
 
    
   
    Compatibility
    
    There is no SECURITY LABEL command in the SQL standard.
-  
    See Also
    sepgsql, src/test/modules/dummy_seclabel
    Prev Up Next
    SAVEPOINT Home SELECT
    
\ No newline at end of file
+

    See Also

    sepgsql, src/test/modules/dummy_seclabel
    Prev Up Next
    SAVEPOINT Home SELECT
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-select.html postgresql-13-13.12/doc/src/sgml/html/sql-select.html --- postgresql-13-13.11/doc/src/sgml/html/sql-select.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-select.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SELECT
    SELECT
    Prev UpSQL CommandsHome Next

    SELECT

    SELECT, TABLE, WITH — retrieve rows from a table or view

    Synopsis

    +SELECT
    SELECT
    Prev UpSQL CommandsHome Next
    SELECT
    SELECT, TABLE, WITH — retrieve rows from a table or view
    Synopsis
     [ WITH [ RECURSIVE ] with_query [, ...] ]
 SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
     [ * | expression [ [ AS ] output_name ] [, ...] ]
@@ -1559,4 +1559,4 @@
     The MATERIALIZED and NOT
     MATERIALIZED options of WITH are extensions
     of the SQL standard.
-
    Prev Up Next
    SECURITY LABEL Home SELECT INTO
    \ No newline at end of file +

    Prev Up Next
    SECURITY LABEL Home SELECT INTO
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-selectinto.html postgresql-13-13.12/doc/src/sgml/html/sql-selectinto.html --- postgresql-13-13.11/doc/src/sgml/html/sql-selectinto.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-selectinto.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SELECT INTO
    SELECT INTO
    Prev UpSQL CommandsHome Next

    SELECT INTO

    SELECT INTO — define a new table from the results of a query

    Synopsis

    +SELECT INTO
    SELECT INTO
    Prev UpSQL CommandsHome Next
    SELECT INTO
    SELECT INTO — define a new table from the results of a query
    Synopsis
     [ WITH [ RECURSIVE ] with_query [, ...] ]
 SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
     * | expression [ [ AS ] output_name ] [, ...]
@@ -62,4 +62,4 @@
    INTO to represent table creation is historical.  It is
    best to use CREATE TABLE AS for this purpose in
    new code.
-  
    Prev Up Next
    SELECT Home SET
    
\ No newline at end of file
+
    Prev Up Next
    SELECT Home SET
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-set-constraints.html postgresql-13-13.12/doc/src/sgml/html/sql-set-constraints.html --- postgresql-13-13.11/doc/src/sgml/html/sql-set-constraints.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-set-constraints.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SET CONSTRAINTS
    SET CONSTRAINTS
    Prev UpSQL CommandsHome Next

    SET CONSTRAINTS

    SET CONSTRAINTS — set constraint check timing for the current transaction

    Synopsis

    +SET CONSTRAINTS
    SET CONSTRAINTS
    Prev UpSQL CommandsHome Next
    SET CONSTRAINTS
    SET CONSTRAINTS — set constraint check timing for the current transaction
    Synopsis
     SET CONSTRAINTS { ALL | name [, ...] } { DEFERRED | IMMEDIATE }
 
    Description
    
    SET CONSTRAINTS sets the behavior of constraint
@@ -68,4 +68,4 @@
    Also, PostgreSQL checks non-deferrable
    uniqueness constraints immediately, not at end of statement as the
    standard would suggest.
-  
    Prev Up Next
    SET Home SET ROLE
    
\ No newline at end of file
+
    Prev Up Next
    SET Home SET ROLE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-set-role.html postgresql-13-13.12/doc/src/sgml/html/sql-set-role.html --- postgresql-13-13.11/doc/src/sgml/html/sql-set-role.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-set-role.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SET ROLE
    SET ROLE
    Prev UpSQL CommandsHome Next

    SET ROLE

    SET ROLE — set the current user identifier of the current session

    Synopsis

    +SET ROLE
    SET ROLE
    Prev UpSQL CommandsHome Next
    SET ROLE
    SET ROLE — set the current user identifier of the current session
    Synopsis
     SET [ SESSION | LOCAL ] ROLE role_name
 SET [ SESSION | LOCAL ] ROLE NONE
 RESET ROLE
@@ -82,4 +82,4 @@
    The SESSION and LOCAL modifiers are a
    PostgreSQL extension, as is the
    RESET syntax.
-  
    Prev Up Next
    SET CONSTRAINTS Home SET SESSION AUTHORIZATION
    
\ No newline at end of file
+
    Prev Up Next
    SET CONSTRAINTS Home SET SESSION AUTHORIZATION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-set-session-authorization.html postgresql-13-13.12/doc/src/sgml/html/sql-set-session-authorization.html --- postgresql-13-13.11/doc/src/sgml/html/sql-set-session-authorization.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-set-session-authorization.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SET SESSION AUTHORIZATION
    SET SESSION AUTHORIZATION
    Prev UpSQL CommandsHome Next

    SET SESSION AUTHORIZATION

    SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session

    Synopsis

    +SET SESSION AUTHORIZATION
    SET SESSION AUTHORIZATION
    Prev UpSQL CommandsHome Next
    SET SESSION AUTHORIZATION
    SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session
    Synopsis
     SET [ SESSION | LOCAL ] SESSION AUTHORIZATION user_name
 SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
 RESET SESSION AUTHORIZATION
@@ -61,4 +61,4 @@
   
    
    The privileges necessary to execute this command are left
    implementation-defined by the standard.
-  
    See Also
    SET ROLE
    Prev Up Next
    SET ROLE Home SET TRANSACTION
    
\ No newline at end of file
+

    See Also

    SET ROLE
    Prev Up Next
    SET ROLE Home SET TRANSACTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-set-transaction.html postgresql-13-13.12/doc/src/sgml/html/sql-set-transaction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-set-transaction.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-set-transaction.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SET TRANSACTION
    SET TRANSACTION
    Prev UpSQL CommandsHome Next

    SET TRANSACTION

    SET TRANSACTION — set the characteristics of the current transaction

    Synopsis

    +SET TRANSACTION
    SET TRANSACTION
    Prev UpSQL CommandsHome Next
    SET TRANSACTION
    SET TRANSACTION — set the characteristics of the current transaction
    Synopsis
     SET TRANSACTION transaction_mode [, ...]
 SET TRANSACTION SNAPSHOT snapshot_id
 SET SESSION CHARACTERISTICS AS TRANSACTION transaction_mode [, ...]
@@ -173,4 +173,4 @@
    The SQL standard requires commas between successive transaction_modes, but for historical
    reasons PostgreSQL allows the commas to be
    omitted.
-  
    Prev Up Next
    SET SESSION AUTHORIZATION Home SHOW
    
\ No newline at end of file
+
    Prev Up Next
    SET SESSION AUTHORIZATION Home SHOW
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-set.html postgresql-13-13.12/doc/src/sgml/html/sql-set.html --- postgresql-13-13.11/doc/src/sgml/html/sql-set.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-set.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SET
    SET
    Prev UpSQL CommandsHome Next

    SET

    SET — change a run-time parameter

    Synopsis

    +SET
    SET
    Prev UpSQL CommandsHome Next
    SET
    SET — change a run-time parameter
    Synopsis
     SET [ SESSION | LOCAL ] configuration_parameter { TO | = } { value | 'value' | DEFAULT }
 SET [ SESSION | LOCAL ] TIME ZONE { value | 'value' | LOCAL | DEFAULT }
 
    Description
    
@@ -150,4 +150,4 @@
    PostgreSQL allows more flexible
    time-zone specifications.  All other SET
    features are PostgreSQL extensions.
-  
    See Also
    RESET, SHOW
    Prev Up Next
    SELECT INTO Home SET CONSTRAINTS
    
\ No newline at end of file
+

    See Also

    RESET, SHOW
    Prev Up Next
    SELECT INTO Home SET CONSTRAINTS
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-show.html postgresql-13-13.12/doc/src/sgml/html/sql-show.html --- postgresql-13-13.11/doc/src/sgml/html/sql-show.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-show.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -SHOW
    SHOW
    Prev UpSQL CommandsHome Next

    SHOW

    SHOW — show the value of a run-time parameter

    Synopsis

    +SHOW
    SHOW
    Prev UpSQL CommandsHome Next
    SHOW
    SHOW — show the value of a run-time parameter
    Synopsis
     SHOW name
 SHOW ALL
 
    Description
    
@@ -79,4 +79,4 @@

    Compatibility

    The SHOW command is a PostgreSQL extension. -

    See Also

    SET, RESET
    Prev Up Next
    SET TRANSACTION Home START TRANSACTION
    \ No newline at end of file +

    See Also

    SET, RESET
    Prev Up Next
    SET TRANSACTION Home START TRANSACTION
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-start-transaction.html postgresql-13-13.12/doc/src/sgml/html/sql-start-transaction.html --- postgresql-13-13.11/doc/src/sgml/html/sql-start-transaction.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-start-transaction.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -START TRANSACTION
    START TRANSACTION
    Prev UpSQL CommandsHome Next

    START TRANSACTION

    START TRANSACTION — start a transaction block

    Synopsis

    +START TRANSACTION
    START TRANSACTION
    Prev UpSQL CommandsHome Next
    START TRANSACTION
    START TRANSACTION — start a transaction block
    Synopsis
     START TRANSACTION [ transaction_mode [, ...] ]
 
 where transaction_mode is one of:
@@ -34,4 +34,4 @@
    omitted.
   
    
    See also the compatibility section of SET TRANSACTION.
-  
    Prev Up Next
    SHOW Home TRUNCATE
    
\ No newline at end of file
+
    Prev Up Next
    SHOW Home TRUNCATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-syntax-calling-funcs.html postgresql-13-13.12/doc/src/sgml/html/sql-syntax-calling-funcs.html --- postgresql-13-13.11/doc/src/sgml/html/sql-syntax-calling-funcs.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-syntax-calling-funcs.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -4.3. Calling Functions
    4.3. Calling Functions
    Prev UpChapter 4. SQL SyntaxHome Next

    4.3. Calling Functions

    4.3.1. Using Positional Notation
    4.3.2. Using Named Notation
    4.3.3. Using Mixed Notation

    +4.3. Calling Functions

    4.3. Calling Functions
    Prev UpChapter 4. SQL SyntaxHome Next

    4.3. Calling Functions

    4.3.1. Using Positional Notation
    4.3.2. Using Named Notation
    4.3.3. Using Mixed Notation

    PostgreSQL allows functions that have named parameters to be called using either positional or named notation. Named notation is especially @@ -129,4 +129,4 @@ Named and mixed call notations currently cannot be used when calling an aggregate function (but they do work when an aggregate function is used as a window function). -

    Prev Up Next
    4.2. Value Expressions Home Chapter 5. Data Definition
    \ No newline at end of file +

    Prev Up Next
    4.2. Value Expressions Home Chapter 5. Data Definition
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-syntax-lexical.html postgresql-13-13.12/doc/src/sgml/html/sql-syntax-lexical.html --- postgresql-13-13.11/doc/src/sgml/html/sql-syntax-lexical.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-syntax-lexical.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -4.1. Lexical Structure
    4.1. Lexical Structure
    Prev UpChapter 4. SQL SyntaxHome Next

    4.1. Lexical Structure

    4.1.1. Identifiers and Key Words
    4.1.2. Constants
    4.1.3. Operators
    4.1.4. Special Characters
    4.1.5. Comments
    4.1.6. Operator Precedence

    +4.1. Lexical Structure

    4.1. Lexical Structure
    Prev UpChapter 4. SQL SyntaxHome Next

    4.1. Lexical Structure

    4.1.1. Identifiers and Key Words
    4.1.2. Constants
    4.1.3. Operators
    4.1.4. Special Characters
    4.1.5. Comments
    4.1.6. Operator Precedence

    SQL input consists of a sequence of commands. A command is composed of a sequence of tokens, terminated by a @@ -648,4 +648,4 @@ you can test your application with the configuration parameter operator_precedence_warning turned on to see if any warnings are logged. -

    Prev Up Next
    Chapter 4. SQL Syntax Home 4.2. Value Expressions
    \ No newline at end of file +

    Prev Up Next
    Chapter 4. SQL Syntax Home 4.2. Value Expressions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-syntax.html postgresql-13-13.12/doc/src/sgml/html/sql-syntax.html --- postgresql-13-13.11/doc/src/sgml/html/sql-syntax.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-syntax.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 4. SQL Syntax
    Chapter 4. SQL Syntax
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 4. SQL Syntax

    Table of Contents

    4.1. Lexical Structure
    4.1.1. Identifiers and Key Words
    4.1.2. Constants
    4.1.3. Operators
    4.1.4. Special Characters
    4.1.5. Comments
    4.1.6. Operator Precedence
    4.2. Value Expressions
    4.2.1. Column References
    4.2.2. Positional Parameters
    4.2.3. Subscripts
    4.2.4. Field Selection
    4.2.5. Operator Invocations
    4.2.6. Function Calls
    4.2.7. Aggregate Expressions
    4.2.8. Window Function Calls
    4.2.9. Type Casts
    4.2.10. Collation Expressions
    4.2.11. Scalar Subqueries
    4.2.12. Array Constructors
    4.2.13. Row Constructors
    4.2.14. Expression Evaluation Rules
    4.3. Calling Functions
    4.3.1. Using Positional Notation
    4.3.2. Using Named Notation
    4.3.3. Using Mixed Notation

    +Chapter 4. SQL Syntax

    Chapter 4. SQL Syntax
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    Part II. The SQL Language Home 4.1. Lexical Structure
    \ No newline at end of file +

    Prev Up Next
    Part II. The SQL Language Home 4.1. Lexical Structure
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-truncate.html postgresql-13-13.12/doc/src/sgml/html/sql-truncate.html --- postgresql-13-13.11/doc/src/sgml/html/sql-truncate.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-truncate.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -TRUNCATE
    TRUNCATE
    Prev UpSQL CommandsHome Next

    TRUNCATE

    TRUNCATE — empty a table or set of tables

    Synopsis

    +TRUNCATE
    TRUNCATE
    Prev UpSQL CommandsHome Next
    TRUNCATE
    TRUNCATE — empty a table or set of tables
    Synopsis
     TRUNCATE [ TABLE ] [ ONLY ] name [ * ] [, ... ]
     [ RESTART IDENTITY | CONTINUE IDENTITY ] [ CASCADE | RESTRICT ]
 
    Description
    
@@ -116,4 +116,4 @@
    meanings.  Some of the concurrency behavior of this command is left
    implementation-defined by the standard, so the above notes should be
    considered and compared with other implementations if necessary.
-  
    See Also
    DELETE
    Prev Up Next
    START TRANSACTION Home UNLISTEN
    
\ No newline at end of file
+

    See Also

    DELETE
    Prev Up Next
    START TRANSACTION Home UNLISTEN
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-unlisten.html postgresql-13-13.12/doc/src/sgml/html/sql-unlisten.html --- postgresql-13-13.11/doc/src/sgml/html/sql-unlisten.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-unlisten.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -UNLISTEN
    UNLISTEN
    Prev UpSQL CommandsHome Next

    UNLISTEN

    UNLISTEN — stop listening for a notification

    Synopsis

    +UNLISTEN
    UNLISTEN
    Prev UpSQL CommandsHome Next
    UNLISTEN
    UNLISTEN — stop listening for a notification
    Synopsis
     UNLISTEN { channel | * }
 
    Description
    
    UNLISTEN is used to remove an existing
@@ -45,4 +45,4 @@
 -- no NOTIFY event is received

    Compatibility

    There is no UNLISTEN command in the SQL standard. -

    See Also

    LISTEN, NOTIFY
    Prev Up Next
    TRUNCATE Home UPDATE
    \ No newline at end of file +

    See Also

    LISTEN, NOTIFY
    Prev Up Next
    TRUNCATE Home UPDATE
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-update.html postgresql-13-13.12/doc/src/sgml/html/sql-update.html --- postgresql-13-13.11/doc/src/sgml/html/sql-update.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-update.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -UPDATE
    UPDATE
    Prev UpSQL CommandsHome Next

    UPDATE

    UPDATE — update rows of a table

    Synopsis

    +UPDATE
    UPDATE
    Prev UpSQL CommandsHome Next
    UPDATE
    UPDATE — update rows of a table
    Synopsis
     [ WITH [ RECURSIVE ] with_query [, ...] ]
 UPDATE [ ONLY ] table_name [ * ] [ [ AS ] alias ]
     SET { column_name = { expression | DEFAULT } |
@@ -282,4 +282,4 @@
    constructor or a sub-SELECT.  An individual column's
    updated value can be specified as DEFAULT in the
    row-constructor case, but not inside a sub-SELECT.
-  
    Prev Up Next
    UNLISTEN Home VACUUM
    
\ No newline at end of file
+
    Prev Up Next
    UNLISTEN Home VACUUM
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-vacuum.html postgresql-13-13.12/doc/src/sgml/html/sql-vacuum.html --- postgresql-13-13.11/doc/src/sgml/html/sql-vacuum.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-vacuum.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -VACUUM
    VACUUM
    Prev UpSQL CommandsHome Next

    VACUUM

    VACUUM — garbage-collect and optionally analyze a database

    Synopsis

    +VACUUM
    VACUUM
    Prev UpSQL CommandsHome Next
    VACUUM
    VACUUM — garbage-collect and optionally analyze a database
    Synopsis
     VACUUM [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
 VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ table_and_columns [, ...] ]
 
@@ -226,4 +226,4 @@
 VACUUM (VERBOSE, ANALYZE) onek;
 
    Compatibility
    
    There is no VACUUM statement in the SQL standard.
-  
    Prev Up Next
    UPDATE Home VALUES
    
\ No newline at end of file
+
    Prev Up Next
    UPDATE Home VALUES
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql-values.html postgresql-13-13.12/doc/src/sgml/html/sql-values.html --- postgresql-13-13.11/doc/src/sgml/html/sql-values.html 2023-05-08 21:34:07.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql-values.html 2023-08-07 20:32:27.000000000 +0000 @@ -1,5 +1,5 @@ -VALUES
    VALUES
    Prev UpSQL CommandsHome Next

    VALUES

    VALUES — compute a set of rows

    Synopsis

    +VALUES
    VALUES
    Prev UpSQL CommandsHome Next
    VALUES
    VALUES — compute a set of rows
    Synopsis
     VALUES ( expression [, ...] ) [, ...]
     [ ORDER BY sort_expression [ ASC | DESC | USING operator ] [, ...] ]
     [ LIMIT { count | ALL } ]
@@ -135,4 +135,4 @@
    LIMIT and OFFSET are
    PostgreSQL extensions; see also
    under SELECT.
-  
    See Also
    INSERT, SELECT
    Prev Up Next
    VACUUM Home PostgreSQL Client Applications
    
\ No newline at end of file
+

    See Also

    INSERT, SELECT
    Prev Up Next
    VACUUM Home PostgreSQL Client Applications
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sql.html postgresql-13-13.12/doc/src/sgml/html/sql.html --- postgresql-13-13.11/doc/src/sgml/html/sql.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sql.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -Part II. The SQL Language
    Part II. The SQL Language
    Prev UpPostgreSQL 13.11 DocumentationHome Next

    Part II. The SQL Language

    +Part II. The SQL Language

    Part II. The SQL Language
    Prev UpPostgreSQL 13.12 DocumentationHome Next

    Part II. The SQL Language

    This part describes the use of the SQL language in PostgreSQL. We start with describing the general syntax of SQL, then @@ -27,4 +27,4 @@ using the PostgreSQL interactive terminal psql, but other programs that have similar functionality can be used as well. -

    Table of Contents

    4. SQL Syntax
    4.1. Lexical Structure
    4.2. Value Expressions
    4.3. Calling Functions
    5. Data Definition
    5.1. Table Basics
    5.2. Default Values
    5.3. Generated Columns
    5.4. Constraints
    5.5. System Columns
    5.6. Modifying Tables
    5.7. Privileges
    5.8. Row Security Policies
    5.9. Schemas
    5.10. Inheritance
    5.11. Table Partitioning
    5.12. Foreign Data
    5.13. Other Database Objects
    5.14. Dependency Tracking
    6. Data Manipulation
    6.1. Inserting Data
    6.2. Updating Data
    6.3. Deleting Data
    6.4. Returning Data from Modified Rows
    7. Queries
    7.1. Overview
    7.2. Table Expressions
    7.3. Select Lists
    7.4. Combining Queries
    7.5. Sorting Rows
    7.6. LIMIT and OFFSET
    7.7. VALUES Lists
    7.8. WITH Queries (Common Table Expressions)
    8. Data Types
    8.1. Numeric Types
    8.2. Monetary Types
    8.3. Character Types
    8.4. Binary Data Types
    8.5. Date/Time Types
    8.6. Boolean Type
    8.7. Enumerated Types
    8.8. Geometric Types
    8.9. Network Address Types
    8.10. Bit String Types
    8.11. Text Search Types
    8.12. UUID Type
    8.13. XML Type
    8.14. JSON Types
    8.15. Arrays
    8.16. Composite Types
    8.17. Range Types
    8.18. Domain Types
    8.19. Object Identifier Types
    8.20. pg_lsn Type
    8.21. Pseudo-Types
    9. Functions and Operators
    9.1. Logical Operators
    9.2. Comparison Functions and Operators
    9.3. Mathematical Functions and Operators
    9.4. String Functions and Operators
    9.5. Binary String Functions and Operators
    9.6. Bit String Functions and Operators
    9.7. Pattern Matching
    9.8. Data Type Formatting Functions
    9.9. Date/Time Functions and Operators
    9.10. Enum Support Functions
    9.11. Geometric Functions and Operators
    9.12. Network Address Functions and Operators
    9.13. Text Search Functions and Operators
    9.14. UUID Functions
    9.15. XML Functions
    9.16. JSON Functions and Operators
    9.17. Sequence Manipulation Functions
    9.18. Conditional Expressions
    9.19. Array Functions and Operators
    9.20. Range Functions and Operators
    9.21. Aggregate Functions
    9.22. Window Functions
    9.23. Subquery Expressions
    9.24. Row and Array Comparisons
    9.25. Set Returning Functions
    9.26. System Information Functions and Operators
    9.27. System Administration Functions
    9.28. Trigger Functions
    9.29. Event Trigger Functions
    9.30. Statistics Information Functions
    10. Type Conversion
    10.1. Overview
    10.2. Operators
    10.3. Functions
    10.4. Value Storage
    10.5. UNION, CASE, and Related Constructs
    10.6. SELECT Output Columns
    11. Indexes
    11.1. Introduction
    11.2. Index Types
    11.3. Multicolumn Indexes
    11.4. Indexes and ORDER BY
    11.5. Combining Multiple Indexes
    11.6. Unique Indexes
    11.7. Indexes on Expressions
    11.8. Partial Indexes
    11.9. Index-Only Scans and Covering Indexes
    11.10. Operator Classes and Operator Families
    11.11. Indexes and Collations
    11.12. Examining Index Usage
    12. Full Text Search
    12.1. Introduction
    12.2. Tables and Indexes
    12.3. Controlling Text Search
    12.4. Additional Features
    12.5. Parsers
    12.6. Dictionaries
    12.7. Configuration Example
    12.8. Testing and Debugging Text Search
    12.9. Preferred Index Types for Text Search
    12.10. psql Support
    12.11. Limitations
    13. Concurrency Control
    13.1. Introduction
    13.2. Transaction Isolation
    13.3. Explicit Locking
    13.4. Data Consistency Checks at the Application Level
    13.5. Caveats
    13.6. Locking and Indexes
    14. Performance Tips
    14.1. Using EXPLAIN
    14.2. Statistics Used by the Planner
    14.3. Controlling the Planner with Explicit JOIN Clauses
    14.4. Populating a Database
    14.5. Non-Durable Settings
    15. Parallel Query
    15.1. How Parallel Query Works
    15.2. When Can Parallel Query Be Used?
    15.3. Parallel Plans
    15.4. Parallel Safety
    Prev Up Next
    3.7. Conclusion Home Chapter 4. SQL Syntax
    \ No newline at end of file +

    Table of Contents

    4. SQL Syntax
    4.1. Lexical Structure
    4.2. Value Expressions
    4.3. Calling Functions
    5. Data Definition
    5.1. Table Basics
    5.2. Default Values
    5.3. Generated Columns
    5.4. Constraints
    5.5. System Columns
    5.6. Modifying Tables
    5.7. Privileges
    5.8. Row Security Policies
    5.9. Schemas
    5.10. Inheritance
    5.11. Table Partitioning
    5.12. Foreign Data
    5.13. Other Database Objects
    5.14. Dependency Tracking
    6. Data Manipulation
    6.1. Inserting Data
    6.2. Updating Data
    6.3. Deleting Data
    6.4. Returning Data from Modified Rows
    7. Queries
    7.1. Overview
    7.2. Table Expressions
    7.3. Select Lists
    7.4. Combining Queries
    7.5. Sorting Rows
    7.6. LIMIT and OFFSET
    7.7. VALUES Lists
    7.8. WITH Queries (Common Table Expressions)
    8. Data Types
    8.1. Numeric Types
    8.2. Monetary Types
    8.3. Character Types
    8.4. Binary Data Types
    8.5. Date/Time Types
    8.6. Boolean Type
    8.7. Enumerated Types
    8.8. Geometric Types
    8.9. Network Address Types
    8.10. Bit String Types
    8.11. Text Search Types
    8.12. UUID Type
    8.13. XML Type
    8.14. JSON Types
    8.15. Arrays
    8.16. Composite Types
    8.17. Range Types
    8.18. Domain Types
    8.19. Object Identifier Types
    8.20. pg_lsn Type
    8.21. Pseudo-Types
    9. Functions and Operators
    9.1. Logical Operators
    9.2. Comparison Functions and Operators
    9.3. Mathematical Functions and Operators
    9.4. String Functions and Operators
    9.5. Binary String Functions and Operators
    9.6. Bit String Functions and Operators
    9.7. Pattern Matching
    9.8. Data Type Formatting Functions
    9.9. Date/Time Functions and Operators
    9.10. Enum Support Functions
    9.11. Geometric Functions and Operators
    9.12. Network Address Functions and Operators
    9.13. Text Search Functions and Operators
    9.14. UUID Functions
    9.15. XML Functions
    9.16. JSON Functions and Operators
    9.17. Sequence Manipulation Functions
    9.18. Conditional Expressions
    9.19. Array Functions and Operators
    9.20. Range Functions and Operators
    9.21. Aggregate Functions
    9.22. Window Functions
    9.23. Subquery Expressions
    9.24. Row and Array Comparisons
    9.25. Set Returning Functions
    9.26. System Information Functions and Operators
    9.27. System Administration Functions
    9.28. Trigger Functions
    9.29. Event Trigger Functions
    9.30. Statistics Information Functions
    10. Type Conversion
    10.1. Overview
    10.2. Operators
    10.3. Functions
    10.4. Value Storage
    10.5. UNION, CASE, and Related Constructs
    10.6. SELECT Output Columns
    11. Indexes
    11.1. Introduction
    11.2. Index Types
    11.3. Multicolumn Indexes
    11.4. Indexes and ORDER BY
    11.5. Combining Multiple Indexes
    11.6. Unique Indexes
    11.7. Indexes on Expressions
    11.8. Partial Indexes
    11.9. Index-Only Scans and Covering Indexes
    11.10. Operator Classes and Operator Families
    11.11. Indexes and Collations
    11.12. Examining Index Usage
    12. Full Text Search
    12.1. Introduction
    12.2. Tables and Indexes
    12.3. Controlling Text Search
    12.4. Additional Features
    12.5. Parsers
    12.6. Dictionaries
    12.7. Configuration Example
    12.8. Testing and Debugging Text Search
    12.9. Preferred Index Types for Text Search
    12.10. psql Support
    12.11. Limitations
    13. Concurrency Control
    13.1. Introduction
    13.2. Transaction Isolation
    13.3. Explicit Locking
    13.4. Data Consistency Checks at the Application Level
    13.5. Caveats
    13.6. Locking and Indexes
    14. Performance Tips
    14.1. Using EXPLAIN
    14.2. Statistics Used by the Planner
    14.3. Controlling the Planner with Explicit JOIN Clauses
    14.4. Populating a Database
    14.5. Non-Durable Settings
    15. Parallel Query
    15.1. How Parallel Query Works
    15.2. When Can Parallel Query Be Used?
    15.3. Parallel Plans
    15.4. Parallel Safety
    Prev Up Next
    3.7. Conclusion Home Chapter 4. SQL Syntax
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ssh-tunnels.html postgresql-13-13.12/doc/src/sgml/html/ssh-tunnels.html --- postgresql-13-13.11/doc/src/sgml/html/ssh-tunnels.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ssh-tunnels.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.11. Secure TCP/IP Connections with SSH Tunnels
    18.11. Secure TCP/IP Connections with SSH Tunnels
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.11. Secure TCP/IP Connections with SSH Tunnels

    +18.11. Secure TCP/IP Connections with SSH Tunnels

    18.11. Secure TCP/IP Connections with SSH Tunnels
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.11. Secure TCP/IP Connections with SSH Tunnels

    It is possible to use SSH to encrypt the network connection between clients and a PostgreSQL server. Done properly, this @@ -73,4 +73,4 @@

    Tip

    Several other applications exist that can provide secure tunnels using a procedure similar in concept to the one just described. -

    Prev Up Next
    18.10. Secure TCP/IP Connections with GSSAPI Encryption Home 18.12. Registering Event Log on Windows
    \ No newline at end of file +

    Prev Up Next
    18.10. Secure TCP/IP Connections with GSSAPI Encryption Home 18.12. Registering Event Log on Windows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/ssl-tcp.html postgresql-13-13.12/doc/src/sgml/html/ssl-tcp.html --- postgresql-13-13.11/doc/src/sgml/html/ssl-tcp.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/ssl-tcp.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.9. Secure TCP/IP Connections with SSL
    18.9. Secure TCP/IP Connections with SSL
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.9. Secure TCP/IP Connections with SSL

    18.9.1. Basic Setup
    18.9.2. OpenSSL Configuration
    18.9.3. Using Client Certificates
    18.9.4. SSL Server File Usage
    18.9.5. Creating Certificates

    +18.9. Secure TCP/IP Connections with SSL

    18.9. Secure TCP/IP Connections with SSL
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.9. Secure TCP/IP Connections with SSL

    18.9.1. Basic Setup
    18.9.2. OpenSSL Configuration
    18.9.3. Using Client Certificates
    18.9.4. SSL Server File Usage
    18.9.5. Creating Certificates

    PostgreSQL has native support for using SSL connections to encrypt client/server communications for increased security. This requires that @@ -250,4 +250,4 @@ by a chain of certificates linked to its trusted root certificate. root.key and intermediate.key should be stored offline for use in creating future certificates. -

    Prev Up Next
    18.8. Encryption Options Home 18.10. Secure TCP/IP Connections with GSSAPI Encryption
    \ No newline at end of file +

    Prev Up Next
    18.8. Encryption Options Home 18.10. Secure TCP/IP Connections with GSSAPI Encryption
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sslinfo.html postgresql-13-13.12/doc/src/sgml/html/sslinfo.html --- postgresql-13-13.11/doc/src/sgml/html/sslinfo.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sslinfo.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.37. sslinfo
    F.37. sslinfo
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.37. sslinfo

    F.37.1. Functions Provided
    F.37.2. Author

    +F.37. sslinfo

    F.37. sslinfo
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.37. sslinfo

    F.37.1. Functions Provided
    F.37.2. Author

    The sslinfo module provides information about the SSL certificate that the current client provided when connecting to PostgreSQL. The module is useless (most functions @@ -132,4 +132,4 @@

    E-Mail of Cryptocom OpenSSL development group: -

    Prev Up Next
    F.36. spi Home F.38. tablefunc
    \ No newline at end of file +

    Prev Up Next
    F.36. spi Home F.38. tablefunc
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/sspi-auth.html postgresql-13-13.12/doc/src/sgml/html/sspi-auth.html --- postgresql-13-13.11/doc/src/sgml/html/sspi-auth.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/sspi-auth.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -20.7. SSPI Authentication
    20.7. SSPI Authentication
    Prev UpChapter 20. Client AuthenticationHome Next

    20.7. SSPI Authentication

    +20.7. SSPI Authentication

    20.7. SSPI Authentication
    Prev UpChapter 20. Client AuthenticationHome Next

    20.7. SSPI Authentication

    SSPI is a Windows technology for secure authentication with single sign-on. PostgreSQL will use SSPI in @@ -65,4 +65,4 @@ users of any realm can connect, subject to whatever user name mapping is done.

    -

    Prev Up Next
    20.6. GSSAPI Authentication Home 20.8. Ident Authentication
    \ No newline at end of file +

    Prev Up Next
    20.6. GSSAPI Authentication Home 20.8. Ident Authentication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-file-layout.html postgresql-13-13.12/doc/src/sgml/html/storage-file-layout.html --- postgresql-13-13.11/doc/src/sgml/html/storage-file-layout.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-file-layout.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.1. Database File Layout
    69.1. Database File Layout
    Prev UpChapter 69. Database Physical StorageHome Next

    69.1. Database File Layout

    +69.1. Database File Layout

    69.1. Database File Layout
    Prev UpChapter 69. Database Physical StorageHome Next

    69.1. Database File Layout

    This section describes the storage format at the level of files and directories.

    @@ -130,4 +130,4 @@ pgsql_tmpPPP.NNN, where PPP is the PID of the owning backend and NNN distinguishes different temporary files of that backend. -

    Prev Up Next
    Chapter 69. Database Physical Storage Home 69.2. TOAST
    \ No newline at end of file +

    Prev Up Next
    Chapter 69. Database Physical Storage Home 69.2. TOAST
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-fsm.html postgresql-13-13.12/doc/src/sgml/html/storage-fsm.html --- postgresql-13-13.11/doc/src/sgml/html/storage-fsm.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-fsm.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.3. Free Space Map
    69.3. Free Space Map
    Prev UpChapter 69. Database Physical StorageHome Next

    69.3. Free Space Map

    +69.3. Free Space Map

    69.3. Free Space Map
    Prev UpChapter 69. Database Physical StorageHome Next

    69.3. Free Space Map

    Each heap and index relation, except for hash indexes, has a Free Space Map (FSM) to keep track of available space in the relation. It's stored alongside the main relation data in a separate relation fork, named after the @@ -22,4 +22,4 @@ how the FSM is structured, and how it's updated and searched. The pg_freespacemap module can be used to examine the information stored in free space maps. -

    Prev Up Next
    69.2. TOAST Home 69.4. Visibility Map
    \ No newline at end of file +

    Prev Up Next
    69.2. TOAST Home 69.4. Visibility Map
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-hot.html postgresql-13-13.12/doc/src/sgml/html/storage-hot.html --- postgresql-13-13.11/doc/src/sgml/html/storage-hot.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-hot.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.7. Heap-Only Tuples (HOT)
    69.7. Heap-Only Tuples (HOT)
    Prev UpChapter 69. Database Physical StorageHome Next

    69.7. Heap-Only Tuples (HOT)

    +69.7. Heap-Only Tuples (HOT)

    69.7. Heap-Only Tuples (HOT)
    Prev UpChapter 69. Database Physical StorageHome Next

    69.7. Heap-Only Tuples (HOT)

    To allow for high concurrency, PostgreSQL uses multiversion concurrency control (MVCC) to store rows. However, @@ -37,9 +37,9 @@ In summary, heap-only tuple updates can only be created if columns used by indexes are not updated. You can increase the likelihood of sufficient page space for - HOT updates by decreasing a table's fillfactor. + HOT updates by decreasing a table's fillfactor. If you don't, HOT updates will still happen because new rows will naturally migrate to new pages and existing pages with sufficient free space for new row versions. The system view pg_stat_all_tables allows monitoring of the occurrence of HOT and non-HOT updates. -

    Prev Up Next
    69.6. Database Page Layout Home Chapter 70. System Catalog Declarations and Initial Contents
    \ No newline at end of file +

    Prev Up Next
    69.6. Database Page Layout Home Chapter 70. System Catalog Declarations and Initial Contents
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-init.html postgresql-13-13.12/doc/src/sgml/html/storage-init.html --- postgresql-13-13.11/doc/src/sgml/html/storage-init.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-init.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,8 +1,8 @@ -69.5. The Initialization Fork
    69.5. The Initialization Fork
    Prev UpChapter 69. Database Physical StorageHome Next

    69.5. The Initialization Fork

    +69.5. The Initialization Fork

    69.5. The Initialization Fork
    Prev UpChapter 69. Database Physical StorageHome Next

    69.5. The Initialization Fork

    Each unlogged table, and each index on an unlogged table, has an initialization fork. The initialization fork is an empty table or index of the appropriate type. When an unlogged table must be reset to empty due to a crash, the initialization fork is copied over the main fork, and any other forks are erased (they will be recreated automatically as needed). -

    Prev Up Next
    69.4. Visibility Map Home 69.6. Database Page Layout
    \ No newline at end of file +

    Prev Up Next
    69.4. Visibility Map Home 69.6. Database Page Layout
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-page-layout.html postgresql-13-13.12/doc/src/sgml/html/storage-page-layout.html --- postgresql-13-13.11/doc/src/sgml/html/storage-page-layout.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-page-layout.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.6. Database Page Layout
    69.6. Database Page Layout
    Prev UpChapter 69. Database Physical StorageHome Next

    69.6. Database Page Layout

    69.6.1. Table Row Layout

    +69.6. Database Page Layout

    69.6. Database Page Layout
    Prev UpChapter 69. Database Physical StorageHome Next

    69.6. Database Page Layout

    69.6.1. Table Row Layout

    This section provides an overview of the page format used within PostgreSQL tables and indexes.[15] Sequences and TOAST tables are formatted just like a regular table. @@ -154,4 +154,4 @@ always uses this format. All the existing index methods also use the basic format, but the data kept on index metapages usually doesn't follow the item layout rules. -

    Prev Up Next
    69.5. The Initialization Fork Home 69.7. Heap-Only Tuples (HOT)
    \ No newline at end of file +

    Prev Up Next
    69.5. The Initialization Fork Home 69.7. Heap-Only Tuples (HOT)
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-toast.html postgresql-13-13.12/doc/src/sgml/html/storage-toast.html --- postgresql-13-13.11/doc/src/sgml/html/storage-toast.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-toast.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.2. TOAST
    69.2. TOAST
    Prev UpChapter 69. Database Physical StorageHome Next

    69.2. TOAST

    69.2.1. Out-of-Line, On-Disk TOAST Storage
    69.2.2. Out-of-Line, In-Memory TOAST Storage

    +69.2. TOAST

    69.2. TOAST
    Prev UpChapter 69. Database Physical StorageHome Next

    69.2. TOAST

    69.2.1. Out-of-Line, On-Disk TOAST Storage
    69.2.2. Out-of-Line, In-Memory TOAST Storage

    This section provides an overview of TOAST (The Oversized-Attribute Storage Technique).

    @@ -218,4 +218,4 @@ expanded to normal in-line varlena values before storage — and then possibly converted to on-disk TOAST pointers, if the containing tuple would otherwise be too big. -

    Prev Up Next
    69.1. Database File Layout Home 69.3. Free Space Map
    \ No newline at end of file +

    Prev Up Next
    69.1. Database File Layout Home 69.3. Free Space Map
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage-vm.html postgresql-13-13.12/doc/src/sgml/html/storage-vm.html --- postgresql-13-13.11/doc/src/sgml/html/storage-vm.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage-vm.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -69.4. Visibility Map
    69.4. Visibility Map
    Prev UpChapter 69. Database Physical StorageHome Next

    69.4. Visibility Map

    +69.4. Visibility Map

    69.4. Visibility Map
    Prev UpChapter 69. Database Physical StorageHome Next

    69.4. Visibility Map

    Each heap relation has a Visibility Map (VM) to keep track of which pages contain only tuples that are known to be visible to all active transactions; it also keeps track of which pages contain @@ -26,4 +26,4 @@

    The pg_visibility module can be used to examine the information stored in the visibility map. -

    Prev Up Next
    69.3. Free Space Map Home 69.5. The Initialization Fork
    \ No newline at end of file +

    Prev Up Next
    69.3. Free Space Map Home 69.5. The Initialization Fork
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/storage.html postgresql-13-13.12/doc/src/sgml/html/storage.html --- postgresql-13-13.11/doc/src/sgml/html/storage.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/storage.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 69. Database Physical Storage
    Chapter 69. Database Physical Storage
    Prev UpPart VII. InternalsHome Next

    Chapter 69. Database Physical Storage

    Table of Contents

    69.1. Database File Layout
    69.2. TOAST
    69.2.1. Out-of-Line, On-Disk TOAST Storage
    69.2.2. Out-of-Line, In-Memory TOAST Storage
    69.3. Free Space Map
    69.4. Visibility Map
    69.5. The Initialization Fork
    69.6. Database Page Layout
    69.6.1. Table Row Layout
    69.7. Heap-Only Tuples (HOT)

    +Chapter 69. Database Physical Storage

    Chapter 69. Database Physical Storage
    Prev UpPart VII. InternalsHome Next
    Prev Up Next
    68.2. Implementation Home 69.1. Database File Layout
    \ No newline at end of file +

    Prev Up Next
    68.2. Implementation Home 69.1. Database File Layout
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/supported-platforms.html postgresql-13-13.12/doc/src/sgml/html/supported-platforms.html --- postgresql-13-13.11/doc/src/sgml/html/supported-platforms.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/supported-platforms.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -16.6. Supported Platforms
    16.6. Supported Platforms
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.6. Supported Platforms

    +16.6. Supported Platforms

    16.6. Supported Platforms
    Prev UpChapter 16. Installation from Source CodeHome Next

    16.6. Supported Platforms

    A platform (that is, a CPU architecture and operating system combination) is considered supported by the PostgreSQL development community if the code contains provisions to work on that platform and @@ -36,4 +36,4 @@ in porting PostgreSQL to a new platform, is the appropriate place to discuss that. -

    Prev Up Next
    16.5. Post-Installation Setup Home 16.7. Platform-Specific Notes
    \ No newline at end of file +

    Prev Up Next
    16.5. Post-Installation Setup Home 16.7. Platform-Specific Notes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/system-catalog-declarations.html postgresql-13-13.12/doc/src/sgml/html/system-catalog-declarations.html --- postgresql-13-13.11/doc/src/sgml/html/system-catalog-declarations.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/system-catalog-declarations.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.1. System Catalog Declaration Rules
    70.1. System Catalog Declaration Rules
    Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

    70.1. System Catalog Declaration Rules

    +70.1. System Catalog Declaration Rules

    70.1. System Catalog Declaration Rules
    Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

    70.1. System Catalog Declaration Rules

    The key part of a catalog header file is a C structure definition describing the layout of each row of the catalog. This begins with a CATALOG macro, which so far as the C compiler is @@ -70,4 +70,4 @@ in pg_attribute, but fortunately genbki.pl handles that chore nowadays.) Avoid making new catalogs be bootstrap catalogs if at all possible. -

    Prev Up Next
    Chapter 70. System Catalog Declarations and Initial Contents Home 70.2. System Catalog Initial Data
    \ No newline at end of file +

    Prev Up Next
    Chapter 70. System Catalog Declarations and Initial Contents Home 70.2. System Catalog Initial Data
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/system-catalog-initial-data.html postgresql-13-13.12/doc/src/sgml/html/system-catalog-initial-data.html --- postgresql-13-13.11/doc/src/sgml/html/system-catalog-initial-data.html 2023-05-08 21:34:13.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/system-catalog-initial-data.html 2023-08-07 20:32:33.000000000 +0000 @@ -1,5 +1,5 @@ -70.2. System Catalog Initial Data
    70.2. System Catalog Initial Data
    Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

    70.2. System Catalog Initial Data

    70.2.1. Data File Format
    70.2.2. OID Assignment
    70.2.3. OID Reference Lookup
    70.2.4. Automatic Creation of Array Types
    70.2.5. Recipes for Editing Data Files

    +70.2. System Catalog Initial Data

    70.2. System Catalog Initial Data
    Prev UpChapter 70. System Catalog Declarations and Initial ContentsHome Next

    70.2. System Catalog Initial Data

    70.2.1. Data File Format
    70.2.2. OID Assignment
    70.2.3. OID Reference Lookup
    70.2.4. Automatic Creation of Array Types
    70.2.5. Recipes for Editing Data Files

    Each catalog that has any manually-created initial data (some do not) has a corresponding .dat file that contains its initial data in an editable format. @@ -376,4 +376,4 @@ and remove_pg_type_oid_symbols.pl attached to this message: https://www.postgresql.org/message-id/CAJVSVGVX8gXnPm+Xa=DxR7kFYprcQ1tNcCT5D0O3ShfnM6jehA@mail.gmail.com -

    Prev Up Next
    70.1. System Catalog Declaration Rules Home 70.3. BKI File Format
    \ No newline at end of file +

    Prev Up Next
    70.1. System Catalog Declaration Rules Home 70.3. BKI File Format
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tableam.html postgresql-13-13.12/doc/src/sgml/html/tableam.html --- postgresql-13-13.11/doc/src/sgml/html/tableam.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tableam.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 60. Table Access Method Interface Definition
    Chapter 60. Table Access Method Interface Definition
    Prev UpPart VII. InternalsHome Next

    Chapter 60. Table Access Method Interface Definition

    +Chapter 60. Table Access Method Interface Definition

    Chapter 60. Table Access Method Interface Definition
    Prev UpPart VII. InternalsHome Next

    Chapter 60. Table Access Method Interface Definition

    This chapter explains the interface between the core PostgreSQL system and table access methods, which manage the storage for tables. The core system @@ -72,4 +72,4 @@ the existing heap implementation present in src/backend/access/heap/heapam_handler.c for details of its implementation. -

    Prev Up Next
    59.4. Further Reading Home Chapter 61. Index Access Method Interface Definition
    \ No newline at end of file +

    Prev Up Next
    59.4. Further Reading Home Chapter 61. Index Access Method Interface Definition
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tablefunc.html postgresql-13-13.12/doc/src/sgml/html/tablefunc.html --- postgresql-13-13.11/doc/src/sgml/html/tablefunc.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tablefunc.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.38. tablefunc
    F.38. tablefunc
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.38. tablefunc

    F.38.1. Functions Provided
    F.38.2. Author

    +F.38. tablefunc

    F.38. tablefunc
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.38. tablefunc

    F.38.1. Functions Provided
    F.38.2. Author

    The tablefunc module includes various functions that return tables (that is, multiple rows). These functions are useful both in their own right and as examples of how to write C functions that return @@ -610,4 +610,4 @@

    F.38.2. Author

    Joe Conway -

    Prev Up Next
    F.37. sslinfo Home F.39. tcn
    \ No newline at end of file +

    Prev Up Next
    F.37. sslinfo Home F.39. tcn
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tablesample-method.html postgresql-13-13.12/doc/src/sgml/html/tablesample-method.html --- postgresql-13-13.11/doc/src/sgml/html/tablesample-method.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tablesample-method.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 57. Writing a Table Sampling Method
    Chapter 57. Writing a Table Sampling Method
    Prev UpPart VII. InternalsHome Next

    Chapter 57. Writing a Table Sampling Method

    Table of Contents

    57.1. Sampling Method Support Functions

    +Chapter 57. Writing a Table Sampling Method

    Chapter 57. Writing a Table Sampling Method
    Prev UpPart VII. InternalsHome Next

    Chapter 57. Writing a Table Sampling Method

    Table of Contents

    57.1. Sampling Method Support Functions

    PostgreSQL's implementation of the TABLESAMPLE clause supports custom table sampling methods, in addition to the BERNOULLI and SYSTEM methods that are required @@ -54,4 +54,4 @@ the src/backend/access/tablesample subdirectory of the source tree for the built-in sampling methods, and into the contrib subdirectory for add-on methods. -

    Prev Up Next
    56.5. Row Locking in Foreign Data Wrappers Home 57.1. Sampling Method Support Functions
    \ No newline at end of file +

    Prev Up Next
    56.5. Row Locking in Foreign Data Wrappers Home 57.1. Sampling Method Support Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tablesample-support-functions.html postgresql-13-13.12/doc/src/sgml/html/tablesample-support-functions.html --- postgresql-13-13.11/doc/src/sgml/html/tablesample-support-functions.html 2023-05-08 21:34:12.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tablesample-support-functions.html 2023-08-07 20:32:32.000000000 +0000 @@ -1,5 +1,5 @@ -57.1. Sampling Method Support Functions
    57.1. Sampling Method Support Functions
    Prev UpChapter 57. Writing a Table Sampling MethodHome Next

    57.1. Sampling Method Support Functions

    +57.1. Sampling Method Support Functions

    57.1. Sampling Method Support Functions
    Prev UpChapter 57. Writing a Table Sampling MethodHome Next

    57.1. Sampling Method Support Functions

    The TSM handler function returns a palloc'd TsmRoutine struct containing pointers to the support functions described below. Most of the functions are required, but some are optional, and those pointers can @@ -160,4 +160,4 @@ should be cleaned up. This function can be omitted (set the pointer to NULL) in the common case where no such resources exist. -

    Prev Up Next
    Chapter 57. Writing a Table Sampling Method Home Chapter 58. Writing a Custom Scan Provider
    \ No newline at end of file +

    Prev Up Next
    Chapter 57. Writing a Table Sampling Method Home Chapter 58. Writing a Custom Scan Provider
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tcn.html postgresql-13-13.12/doc/src/sgml/html/tcn.html --- postgresql-13-13.11/doc/src/sgml/html/tcn.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tcn.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.39. tcn
    F.39. tcn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.39. tcn

    +F.39. tcn

    F.39. tcn
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.39. tcn

    The tcn module provides a trigger function that notifies listeners of changes to any table on which it is attached. It must be used as an AFTER trigger FOR EACH ROW. @@ -52,4 +52,4 @@ DELETE 1 Asynchronous notification "tcn" with payload ""tcndata",D,"a"='1',"b"='2012-12-22'" received from server process with PID 22770.

    -

    Prev Up Next
    F.38. tablefunc Home F.40. test_decoding
    \ No newline at end of file +

    Prev Up Next
    F.38. tablefunc Home F.40. test_decoding
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/test-decoding.html postgresql-13-13.12/doc/src/sgml/html/test-decoding.html --- postgresql-13-13.11/doc/src/sgml/html/test-decoding.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/test-decoding.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.40. test_decoding
    F.40. test_decoding
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.40. test_decoding

    +F.40. test_decoding

    F.40. test_decoding
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.40. test_decoding

    test_decoding is an example of a logical decoding output plugin. It doesn't do anything especially useful, but can serve as a starting point for developing your own output plugin. @@ -25,4 +25,4 @@ 0/16D3398 | 692 | COMMIT (8 rows)

    -

    Prev Up Next
    F.39. tcn Home F.41. tsm_system_rows
    \ No newline at end of file +

    Prev Up Next
    F.39. tcn Home F.41. tsm_system_rows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-configuration.html postgresql-13-13.12/doc/src/sgml/html/textsearch-configuration.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-configuration.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-configuration.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.7. Configuration Example
    12.7. Configuration Example
    Prev UpChapter 12. Full Text SearchHome Next

    12.7. Configuration Example

    +12.7. Configuration Example

    12.7. Configuration Example
    Prev UpChapter 12. Full Text SearchHome Next

    12.7. Configuration Example

    A text search configuration specifies all options necessary to transform a document into a tsvector: the parser to use to break text into tokens, and the dictionaries to use to transform each token into a @@ -105,4 +105,4 @@ ---------------------------- public.pg

    -

    Prev Up Next
    12.6. Dictionaries Home 12.8. Testing and Debugging Text Search
    \ No newline at end of file +

    Prev Up Next
    12.6. Dictionaries Home 12.8. Testing and Debugging Text Search
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-controls.html postgresql-13-13.12/doc/src/sgml/html/textsearch-controls.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-controls.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-controls.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.3. Controlling Text Search
    12.3. Controlling Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.3. Controlling Text Search

    12.3.1. Parsing Documents
    12.3.2. Parsing Queries
    12.3.3. Ranking Search Results
    12.3.4. Highlighting Results

    +12.3. Controlling Text Search

    12.3. Controlling Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.3. Controlling Text Search

    12.3.1. Parsing Documents
    12.3.2. Parsing Queries
    12.3.3. Ranking Search Results
    12.3.4. Highlighting Results

    To implement full text searching there must be a function to create a tsvector from a document and a tsquery from a user query. Also, we need to return results in a useful order, so we need @@ -547,4 +547,4 @@ ts_headline uses the original document, not a tsvector summary, so it can be slow and should be used with care. -

    Prev Up Next
    12.2. Tables and Indexes Home 12.4. Additional Features
    \ No newline at end of file +

    Prev Up Next
    12.2. Tables and Indexes Home 12.4. Additional Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-debugging.html postgresql-13-13.12/doc/src/sgml/html/textsearch-debugging.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-debugging.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-debugging.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.8. Testing and Debugging Text Search
    12.8. Testing and Debugging Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.8. Testing and Debugging Text Search

    12.8.1. Configuration Testing
    12.8.2. Parser Testing
    12.8.3. Dictionary Testing

    +12.8. Testing and Debugging Text Search

    12.8. Testing and Debugging Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.8. Testing and Debugging Text Search

    12.8.1. Configuration Testing
    12.8.2. Parser Testing
    12.8.3. Dictionary Testing

    The behavior of a custom text search configuration can easily become confusing. The functions described in this section are useful for testing text search objects. You can @@ -250,4 +250,4 @@ ----------------- 'sn'

    -

    Prev Up Next
    12.7. Configuration Example Home 12.9. Preferred Index Types for Text Search
    \ No newline at end of file +

    Prev Up Next
    12.7. Configuration Example Home 12.9. Preferred Index Types for Text Search
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-dictionaries.html postgresql-13-13.12/doc/src/sgml/html/textsearch-dictionaries.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-dictionaries.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-dictionaries.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.6. Dictionaries
    12.6. Dictionaries
    Prev UpChapter 12. Full Text SearchHome Next

    12.6. Dictionaries

    12.6.1. Stop Words
    12.6.2. Simple Dictionary
    12.6.3. Synonym Dictionary
    12.6.4. Thesaurus Dictionary
    12.6.5. Ispell Dictionary
    12.6.6. Snowball Dictionary

    +12.6. Dictionaries

    12.6. Dictionaries
    Prev UpChapter 12. Full Text SearchHome Next

    12.6. Dictionaries

    12.6.1. Stop Words
    12.6.2. Simple Dictionary
    12.6.3. Synonym Dictionary
    12.6.4. Thesaurus Dictionary
    12.6.5. Ispell Dictionary
    12.6.6. Snowball Dictionary

    Dictionaries are used to eliminate words that should not be considered in a search (stop words), and to normalize words so that different derived forms of the same word will match. A successfully @@ -658,4 +658,4 @@ at the end of the dictionary list. It is useless to have it before any other dictionary because a token will never pass through it to the next dictionary. -

    Prev Up Next
    12.5. Parsers Home 12.7. Configuration Example
    \ No newline at end of file +

    Prev Up Next
    12.5. Parsers Home 12.7. Configuration Example
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-features.html postgresql-13-13.12/doc/src/sgml/html/textsearch-features.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-features.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-features.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.4. Additional Features
    12.4. Additional Features
    Prev UpChapter 12. Full Text SearchHome Next

    12.4. Additional Features

    12.4.1. Manipulating Documents
    12.4.2. Manipulating Queries
    12.4.3. Triggers for Automatic Updates
    12.4.4. Gathering Document Statistics

    +12.4. Additional Features

    12.4. Additional Features
    Prev UpChapter 12. Full Text SearchHome Next

    12.4. Additional Features

    12.4.1. Manipulating Documents
    12.4.2. Manipulating Queries
    12.4.3. Triggers for Automatic Updates
    12.4.4. Gathering Document Statistics

    This section describes additional functions and operators that are useful in connection with text search.

    12.4.1. Manipulating Documents

    @@ -389,4 +389,4 @@ ORDER BY nentry DESC, ndoc DESC, word LIMIT 10;

    -

    Prev Up Next
    12.3. Controlling Text Search Home 12.5. Parsers
    \ No newline at end of file +

    Prev Up Next
    12.3. Controlling Text Search Home 12.5. Parsers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-indexes.html postgresql-13-13.12/doc/src/sgml/html/textsearch-indexes.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-indexes.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-indexes.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.9. Preferred Index Types for Text Search
    12.9. Preferred Index Types for Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.9. Preferred Index Types for Text Search

    +12.9. Preferred Index Types for Text Search

    12.9. Preferred Index Types for Text Search
    Prev UpChapter 12. Full Text SearchHome Next

    12.9. Preferred Index Types for Text Search

    There are two kinds of indexes that can be used to speed up full text searches: GIN and @@ -77,4 +77,4 @@ servers and collecting external search results, e.g., via Foreign Data access. The latter is possible because ranking functions use only local information. -

    Prev Up Next
    12.8. Testing and Debugging Text Search Home 12.10. psql Support
    \ No newline at end of file +

    Prev Up Next
    12.8. Testing and Debugging Text Search Home 12.10. psql Support
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-intro.html postgresql-13-13.12/doc/src/sgml/html/textsearch-intro.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-intro.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-intro.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.1. Introduction
    12.1. Introduction
    Prev UpChapter 12. Full Text SearchHome Next

    12.1. Introduction

    12.1.1. What Is a Document?
    12.1.2. Basic Text Matching
    12.1.3. Configurations

    +12.1. Introduction

    12.1. Introduction
    Prev UpChapter 12. Full Text SearchHome Next

    12.1. Introduction

    12.1.1. What Is a Document?
    12.1.2. Basic Text Matching
    12.1.3. Configurations

    Full Text Searching (or just text search) provides the capability to identify natural-language documents that satisfy a query, and optionally to sort them by @@ -336,4 +336,4 @@ parsers and templates, no special privilege is needed to create a new dictionary or configuration. Examples of creating custom dictionaries and configurations appear later in this chapter. -

    Prev Up Next
    Chapter 12. Full Text Search Home 12.2. Tables and Indexes
    \ No newline at end of file +

    Prev Up Next
    Chapter 12. Full Text Search Home 12.2. Tables and Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-limitations.html postgresql-13-13.12/doc/src/sgml/html/textsearch-limitations.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-limitations.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-limitations.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.11. Limitations
    12.11. Limitations
    Prev UpChapter 12. Full Text SearchHome Next

    12.11. Limitations

    +12.11. Limitations

    12.11. Limitations
    Prev UpChapter 12. Full Text SearchHome Next

    12.11. Limitations

    The current limitations of PostgreSQL's text search features are:

    • The length of each lexeme must be less than 2 kilobytes

    • The length of a tsvector (lexemes + positions) must be @@ -18,4 +18,4 @@ Another example — the PostgreSQL mailing list archives contained 910,989 unique words with 57,491,343 lexemes in 461,020 messages. -

    Prev Up Next
    12.10. psql Support Home Chapter 13. Concurrency Control
    \ No newline at end of file +

    Prev Up Next
    12.10. psql Support Home Chapter 13. Concurrency Control
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-parsers.html postgresql-13-13.12/doc/src/sgml/html/textsearch-parsers.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-parsers.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-parsers.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.5. Parsers
    12.5. Parsers
    Prev UpChapter 12. Full Text SearchHome Next

    12.5. Parsers

    +12.5. Parsers

    12.5. Parsers
    Prev UpChapter 12. Full Text SearchHome Next

    12.5. Parsers

    Text search parsers are responsible for splitting raw document text into tokens and identifying each token's type, where the set of possible types is defined by the parser itself. @@ -56,4 +56,4 @@ host | Host | example.com url_path | URL path | /stuff/index.html

    -

    Prev Up Next
    12.4. Additional Features Home 12.6. Dictionaries
    \ No newline at end of file +

    Prev Up Next
    12.4. Additional Features Home 12.6. Dictionaries
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-psql.html postgresql-13-13.12/doc/src/sgml/html/textsearch-psql.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-psql.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-psql.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.10. psql Support
    12.10. psql Support
    Prev UpChapter 12. Full Text SearchHome Next

    12.10. psql Support

    +12.10. psql Support

    12.10. psql Support
    Prev UpChapter 12. Full Text SearchHome Next

    12.10. psql Support

    Information about text search configuration objects can be obtained in psql using a set of commands: 

    @@ -156,4 +156,4 @@
  pg_catalog | synonym   | synonym dictionary: replace word by its synonym
  pg_catalog | thesaurus | thesaurus dictionary: phrase by phrase substitution

    -

    Prev Up Next
    12.9. Preferred Index Types for Text Search Home 12.11. Limitations
    \ No newline at end of file +

    Prev Up Next
    12.9. Preferred Index Types for Text Search Home 12.11. Limitations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch-tables.html postgresql-13-13.12/doc/src/sgml/html/textsearch-tables.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch-tables.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch-tables.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -12.2. Tables and Indexes
    12.2. Tables and Indexes
    Prev UpChapter 12. Full Text SearchHome Next

    12.2. Tables and Indexes

    12.2.1. Searching a Table
    12.2.2. Creating Indexes

    +12.2. Tables and Indexes

    12.2. Tables and Indexes
    Prev UpChapter 12. Full Text SearchHome Next

    12.2. Tables and Indexes

    12.2.1. Searching a Table
    12.2.2. Creating Indexes

    The examples in the previous section illustrated full text matching using simple constant strings. This section shows how to search table data, optionally using indexes. @@ -136,4 +136,4 @@ important when using a GiST index than a GIN index; see Section 12.9.) The expression-index approach is simpler to set up, however, and it requires less disk space since the tsvector representation is not stored explicitly. -

    Prev Up Next
    12.1. Introduction Home 12.3. Controlling Text Search
    \ No newline at end of file +

    Prev Up Next
    12.1. Introduction Home 12.3. Controlling Text Search
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/textsearch.html postgresql-13-13.12/doc/src/sgml/html/textsearch.html --- postgresql-13-13.11/doc/src/sgml/html/textsearch.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/textsearch.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 12. Full Text Search
    Chapter 12. Full Text Search
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    11.12. Examining Index Usage Home 12.1. Introduction
    \ No newline at end of file +Chapter 12. Full Text Search
    Chapter 12. Full Text Search
    Prev UpPart II. The SQL LanguageHome Next
    Prev Up Next
    11.12. Examining Index Usage Home 12.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/transaction-iso.html postgresql-13-13.12/doc/src/sgml/html/transaction-iso.html --- postgresql-13-13.11/doc/src/sgml/html/transaction-iso.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/transaction-iso.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -13.2. Transaction Isolation
    13.2. Transaction Isolation
    Prev UpChapter 13. Concurrency ControlHome Next

    13.2. Transaction Isolation

    13.2.1. Read Committed Isolation Level
    13.2.2. Repeatable Read Isolation Level
    13.2.3. Serializable Isolation Level

    +13.2. Transaction Isolation

    13.2. Transaction Isolation
    Prev UpChapter 13. Concurrency ControlHome Next

    13.2. Transaction Isolation

    13.2.1. Read Committed Isolation Level
    13.2.2. Repeatable Read Isolation Level
    13.2.3. Serializable Isolation Level

    The SQL standard defines four levels of transaction isolation. The most strict is Serializable, which is defined by the standard in a paragraph which says that any @@ -506,4 +506,4 @@ Some differences in behavior and performance may be observed when compared with other systems that use a traditional locking technique. Please see [ports12] for detailed information. -

    Prev Up Next
    13.1. Introduction Home 13.3. Explicit Locking
    \ No newline at end of file +

    Prev Up Next
    13.1. Introduction Home 13.3. Explicit Locking
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/trigger-datachanges.html postgresql-13-13.12/doc/src/sgml/html/trigger-datachanges.html --- postgresql-13-13.11/doc/src/sgml/html/trigger-datachanges.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/trigger-datachanges.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -38.2. Visibility of Data Changes
    38.2. Visibility of Data Changes
    Prev UpChapter 38. TriggersHome Next

    38.2. Visibility of Data Changes

    +38.2. Visibility of Data Changes

    38.2. Visibility of Data Changes
    Prev UpChapter 38. TriggersHome Next

    38.2. Visibility of Data Changes

    If you execute SQL commands in your trigger function, and these commands access the table that the trigger is for, then you need to be aware of the data visibility rules, because they determine @@ -43,4 +43,4 @@

    Further information about data visibility rules can be found in Section 46.5. The example in Section 38.4 contains a demonstration of these rules. -

    Prev Up Next
    38.1. Overview of Trigger Behavior Home 38.3. Writing Trigger Functions in C
    \ No newline at end of file +

    Prev Up Next
    38.1. Overview of Trigger Behavior Home 38.3. Writing Trigger Functions in C
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/trigger-definition.html postgresql-13-13.12/doc/src/sgml/html/trigger-definition.html --- postgresql-13-13.11/doc/src/sgml/html/trigger-definition.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/trigger-definition.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -38.1. Overview of Trigger Behavior
    38.1. Overview of Trigger Behavior
    Prev UpChapter 38. TriggersHome Next

    38.1. Overview of Trigger Behavior

    +38.1. Overview of Trigger Behavior

    38.1. Overview of Trigger Behavior
    Prev UpChapter 38. TriggersHome Next

    38.1. Overview of Trigger Behavior

    A trigger is a specification that the database should automatically execute a particular function whenever a certain type of operation is performed. Triggers can be attached to tables (partitioned or not), @@ -287,4 +287,4 @@ that is being used, but the typical approach is to make the transition tables act like read-only temporary tables that can be accessed by SQL commands issued within the trigger function. -

    Prev Up Next
    Chapter 38. Triggers Home 38.2. Visibility of Data Changes
    \ No newline at end of file +

    Prev Up Next
    Chapter 38. Triggers Home 38.2. Visibility of Data Changes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/trigger-example.html postgresql-13-13.12/doc/src/sgml/html/trigger-example.html --- postgresql-13-13.11/doc/src/sgml/html/trigger-example.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/trigger-example.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -38.4. A Complete Trigger Example
    38.4. A Complete Trigger Example
    Prev UpChapter 38. TriggersHome Next

    38.4. A Complete Trigger Example

    +38.4. A Complete Trigger Example

    38.4. A Complete Trigger Example
    Prev UpChapter 38. TriggersHome Next

    38.4. A Complete Trigger Example

    Here is a very simple example of a trigger function written in C. (Examples of triggers written in procedural languages can be found in the documentation of the procedural languages.) @@ -177,4 +177,4 @@ There are more complex examples in src/test/regress/regress.c and in spi. -

    Prev Up Next
    38.3. Writing Trigger Functions in C Home Chapter 39. Event Triggers
    \ No newline at end of file +

    Prev Up Next
    38.3. Writing Trigger Functions in C Home Chapter 39. Event Triggers
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/trigger-interface.html postgresql-13-13.12/doc/src/sgml/html/trigger-interface.html --- postgresql-13-13.11/doc/src/sgml/html/trigger-interface.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/trigger-interface.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -38.3. Writing Trigger Functions in C
    38.3. Writing Trigger Functions in C
    Prev UpChapter 38. TriggersHome Next

    38.3. Writing Trigger Functions in C

    +38.3. Writing Trigger Functions in C

    38.3. Writing Trigger Functions in C
    Prev UpChapter 38. TriggersHome Next

    38.3. Writing Trigger Functions in C

    This section describes the low-level details of the interface to a trigger function. This information is only needed when writing trigger functions in C. If you are using a higher-level language then @@ -181,4 +181,4 @@ Be careful to return either tg_trigtuple or tg_newtuple, as appropriate, if you don't want to modify the row being operated on. -

    Prev Up Next
    38.2. Visibility of Data Changes Home 38.4. A Complete Trigger Example
    \ No newline at end of file +

    Prev Up Next
    38.2. Visibility of Data Changes Home 38.4. A Complete Trigger Example
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/triggers.html postgresql-13-13.12/doc/src/sgml/html/triggers.html --- postgresql-13-13.11/doc/src/sgml/html/triggers.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/triggers.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 38. Triggers
    Chapter 38. Triggers
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 38. Triggers

    Table of Contents

    38.1. Overview of Trigger Behavior
    38.2. Visibility of Data Changes
    38.3. Writing Trigger Functions in C
    38.4. A Complete Trigger Example

    +Chapter 38. Triggers

    Chapter 38. Triggers
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 38. Triggers

    Table of Contents

    38.1. Overview of Trigger Behavior
    38.2. Visibility of Data Changes
    38.3. Writing Trigger Functions in C
    38.4. A Complete Trigger Example

    This chapter provides general information about writing trigger functions. Trigger functions can be written in most of the available procedural languages, including @@ -15,4 +15,4 @@ most people find it easier to use one of the procedural languages. It is not currently possible to write a trigger function in the plain SQL function language. -

    Prev Up Next
    37.18. Extension Building Infrastructure Home 38.1. Overview of Trigger Behavior
    \ No newline at end of file +

    Prev Up Next
    37.18. Extension Building Infrastructure Home 38.1. Overview of Trigger Behavior
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tsm-system-rows.html postgresql-13-13.12/doc/src/sgml/html/tsm-system-rows.html --- postgresql-13-13.11/doc/src/sgml/html/tsm-system-rows.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tsm-system-rows.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.41. tsm_system_rows
    F.41. tsm_system_rows
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.41. tsm_system_rows

    F.41.1. Examples

    +F.41. tsm_system_rows

    F.41. tsm_system_rows
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.41. tsm_system_rows

    F.41.1. Examples

    The tsm_system_rows module provides the table sampling method SYSTEM_ROWS, which can be used in the TABLESAMPLE clause of a SELECT @@ -36,4 +36,4 @@ This command will return a sample of 100 rows from the table my_table (unless the table does not have 100 visible rows, in which case all its rows are returned). -

    Prev Up Next
    F.40. test_decoding Home F.42. tsm_system_time
    \ No newline at end of file +

    Prev Up Next
    F.40. test_decoding Home F.42. tsm_system_time
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tsm-system-time.html postgresql-13-13.12/doc/src/sgml/html/tsm-system-time.html --- postgresql-13-13.11/doc/src/sgml/html/tsm-system-time.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tsm-system-time.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.42. tsm_system_time
    F.42. tsm_system_time
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.42. tsm_system_time

    F.42.1. Examples

    +F.42. tsm_system_time

    F.42. tsm_system_time
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.42. tsm_system_time

    F.42.1. Examples

    The tsm_system_time module provides the table sampling method SYSTEM_TIME, which can be used in the TABLESAMPLE clause of a SELECT @@ -38,4 +38,4 @@ This command will return as large a sample of my_table as it can read in 1 second (1000 milliseconds). Of course, if the whole table can be read in under 1 second, all its rows will be returned. -

    Prev Up Next
    F.41. tsm_system_rows Home F.43. unaccent
    \ No newline at end of file +

    Prev Up Next
    F.41. tsm_system_rows Home F.43. unaccent
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-accessdb.html postgresql-13-13.12/doc/src/sgml/html/tutorial-accessdb.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-accessdb.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-accessdb.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -1.4. Accessing a Database
    1.4. Accessing a Database
    Prev UpChapter 1. Getting StartedHome Next

    1.4. Accessing a Database

    +1.4. Accessing a Database

    1.4. Accessing a Database
    Prev UpChapter 1. Getting StartedHome Next

    1.4. Accessing a Database

    Once you have created a database, you can access it by:

    • @@ -32,7 +32,7 @@ In psql, you will be greeted with the following message: 

      -psql (13.11)
+psql (13.12)
 Type "help" for help.
 
 mydb=>
@@ -63,7 +63,7 @@
 mydb=> SELECT version();
                                          version
 -------------------------------------------------------------------​-----------------------
- PostgreSQL 13.11 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
+ PostgreSQL 13.12 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
 (1 row)
 
 mydb=> SELECT current_date;
@@ -100,4 +100,4 @@
     full capabilities of psql are documented in
     psql.  In this tutorial we will not use these
     features explicitly, but you can use them yourself when it is helpful.
-
    Prev Up Next
    1.3. Creating a Database Home Chapter 2. The SQL Language
    \ No newline at end of file +

    Prev Up Next
    1.3. Creating a Database Home Chapter 2. The SQL Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-advanced-intro.html postgresql-13-13.12/doc/src/sgml/html/tutorial-advanced-intro.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-advanced-intro.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-advanced-intro.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.1. Introduction
    3.1. Introduction
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.1. Introduction

    +3.1. Introduction

    3.1. Introduction
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.1. Introduction

    In the previous chapter we have covered the basics of using SQL to store and access your data in PostgreSQL. We will now discuss some @@ -15,4 +15,4 @@ file also contains some sample data to load, which is not repeated here. (Refer to Section 2.1 for how to use the file.) -

    Prev Up Next
    Chapter 3. Advanced Features Home 3.2. Views
    \ No newline at end of file +

    Prev Up Next
    Chapter 3. Advanced Features Home 3.2. Views
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-advanced.html postgresql-13-13.12/doc/src/sgml/html/tutorial-advanced.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-advanced.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-advanced.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 3. Advanced Features
    Chapter 3. Advanced Features
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    2.9. Deletions Home 3.1. Introduction
    \ No newline at end of file +Chapter 3. Advanced Features
    Chapter 3. Advanced Features
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    2.9. Deletions Home 3.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-agg.html postgresql-13-13.12/doc/src/sgml/html/tutorial-agg.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-agg.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-agg.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -2.7. Aggregate Functions
    2.7. Aggregate Functions
    Prev UpChapter 2. The SQL LanguageHome Next

    2.7. Aggregate Functions

    +2.7. Aggregate Functions

    2.7. Aggregate Functions
    Prev UpChapter 2. The SQL LanguageHome Next

    2.7. Aggregate Functions

    Like most other relational database products, PostgreSQL supports aggregate functions. @@ -169,4 +169,4 @@ rows with temp_lo below 45; but the max aggregate is still applied to all rows, so it still finds the reading of 46. -

    Prev Up Next
    2.6. Joins Between Tables Home 2.8. Updates
    \ No newline at end of file +

    Prev Up Next
    2.6. Joins Between Tables Home 2.8. Updates
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-arch.html postgresql-13-13.12/doc/src/sgml/html/tutorial-arch.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-arch.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-arch.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -1.2. Architectural Fundamentals
    1.2. Architectural Fundamentals
    Prev UpChapter 1. Getting StartedHome Next

    1.2. Architectural Fundamentals

    +1.2. Architectural Fundamentals

    1.2. Architectural Fundamentals
    Prev UpChapter 1. Getting StartedHome Next

    1.2. Architectural Fundamentals

    Before we proceed, you should understand the basic PostgreSQL system architecture. Understanding how the parts of @@ -46,4 +46,4 @@ client connections, whereas client and associated server processes come and go. (All of this is of course invisible to the user. We only mention it here for completeness.) -

    Prev Up Next
    1.1. Installation Home 1.3. Creating a Database
    \ No newline at end of file +

    Prev Up Next
    1.1. Installation Home 1.3. Creating a Database
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-concepts.html postgresql-13-13.12/doc/src/sgml/html/tutorial-concepts.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-concepts.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-concepts.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -2.2. Concepts
    2.2. Concepts
    Prev UpChapter 2. The SQL LanguageHome Next

    2.2. Concepts

    +2.2. Concepts

    2.2. Concepts
    Prev UpChapter 2. The SQL LanguageHome Next

    2.2. Concepts

    @@ -34,4 +34,4 @@ Tables are grouped into databases, and a collection of databases managed by a single PostgreSQL server instance constitutes a database cluster. -

    Prev Up Next
    2.1. Introduction Home 2.3. Creating a New Table
    \ No newline at end of file +

    Prev Up Next
    2.1. Introduction Home 2.3. Creating a New Table
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-conclusion.html postgresql-13-13.12/doc/src/sgml/html/tutorial-conclusion.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-conclusion.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-conclusion.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.7. Conclusion
    3.7. Conclusion
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.7. Conclusion

    +3.7. Conclusion

    3.7. Conclusion
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.7. Conclusion

    PostgreSQL has many features not touched upon in this tutorial introduction, which has been oriented toward newer users of SQL. These @@ -9,4 +9,4 @@ If you feel you need more introductory material, please visit the PostgreSQL web site for links to more resources. -

    Prev Up Next
    3.6. Inheritance Home Part II. The SQL Language
    \ No newline at end of file +

    Prev Up Next
    3.6. Inheritance Home Part II. The SQL Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-createdb.html postgresql-13-13.12/doc/src/sgml/html/tutorial-createdb.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-createdb.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-createdb.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -1.3. Creating a Database
    1.3. Creating a Database
    Prev UpChapter 1. Getting StartedHome Next

    1.3. Creating a Database

    +1.3. Creating a Database

    1.3. Creating a Database
    Prev UpChapter 1. Getting StartedHome Next

    1.3. Creating a Database

    The first test to see whether you can access the database server is to try to create a database. A running PostgreSQL server can manage many @@ -116,4 +116,4 @@ create databases. Instead of logging in as that user you can also specify the -U option everywhere to select a PostgreSQL user name to connect as. -

    Prev Up Next
    1.2. Architectural Fundamentals Home 1.4. Accessing a Database
    \ No newline at end of file +

    Prev Up Next
    1.2. Architectural Fundamentals Home 1.4. Accessing a Database
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-delete.html postgresql-13-13.12/doc/src/sgml/html/tutorial-delete.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-delete.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-delete.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -2.9. Deletions
    2.9. Deletions
    Prev UpChapter 2. The SQL LanguageHome Next

    2.9. Deletions

    +2.9. Deletions

    2.9. Deletions
    Prev UpChapter 2. The SQL LanguageHome Next

    2.9. Deletions

    Rows can be removed from a table using the DELETE command. Suppose you are no longer interested in the weather of Hayward. @@ -31,4 +31,4 @@ remove all rows from the given table, leaving it empty. The system will not request confirmation before doing this! -

    Prev Up Next
    2.8. Updates Home Chapter 3. Advanced Features
    \ No newline at end of file +

    Prev Up Next
    2.8. Updates Home Chapter 3. Advanced Features
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-fk.html postgresql-13-13.12/doc/src/sgml/html/tutorial-fk.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-fk.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-fk.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.3. Foreign Keys
    3.3. Foreign Keys
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.3. Foreign Keys

    +3.3. Foreign Keys

    3.3. Foreign Keys
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.3. Foreign Keys

    Recall the weather and cities tables from Chapter 2. Consider the following problem: You want to make sure that no one can insert rows in the @@ -48,4 +48,4 @@ for more information. Making correct use of foreign keys will definitely improve the quality of your database applications, so you are strongly encouraged to learn about them. -

    Prev Up Next
    3.2. Views Home 3.4. Transactions
    \ No newline at end of file +

    Prev Up Next
    3.2. Views Home 3.4. Transactions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-inheritance.html postgresql-13-13.12/doc/src/sgml/html/tutorial-inheritance.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-inheritance.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-inheritance.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.6. Inheritance
    3.6. Inheritance
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.6. Inheritance

    +3.6. Inheritance

    3.6. Inheritance
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.6. Inheritance

    Inheritance is a concept from object-oriented databases. It opens up interesting new possibilities of database design.

    @@ -110,4 +110,4 @@ Although inheritance is frequently useful, it has not been integrated with unique constraints or foreign keys, which limits its usefulness. See Section 5.10 for more detail. -

    Prev Up Next
    3.5. Window Functions Home 3.7. Conclusion
    \ No newline at end of file +

    Prev Up Next
    3.5. Window Functions Home 3.7. Conclusion
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-install.html postgresql-13-13.12/doc/src/sgml/html/tutorial-install.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-install.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-install.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -1.1. Installation
    1.1. Installation
    Prev UpChapter 1. Getting StartedHome Next

    1.1. Installation

    +1.1. Installation

    1.1. Installation
    Prev UpChapter 1. Getting StartedHome Next

    1.1. Installation

    Before you can use PostgreSQL you need to install it, of course. It is possible that PostgreSQL is already installed at your @@ -35,4 +35,4 @@ site administrator or, if that is you, the documentation to make sure that your environment is properly set up. If you did not understand the preceding paragraph then read the next section. -

    Prev Up Next
    Chapter 1. Getting Started Home 1.2. Architectural Fundamentals
    \ No newline at end of file +

    Prev Up Next
    Chapter 1. Getting Started Home 1.2. Architectural Fundamentals
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-join.html postgresql-13-13.12/doc/src/sgml/html/tutorial-join.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-join.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-join.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -2.6. Joins Between Tables
    2.6. Joins Between Tables
    Prev UpChapter 2. The SQL LanguageHome Next

    2.6. Joins Between Tables

    +2.6. Joins Between Tables

    2.6. Joins Between Tables
    Prev UpChapter 2. The SQL LanguageHome Next

    2.6. Joins Between Tables

    Thus far, our queries have only accessed one table at a time. Queries can access multiple tables at once, or access the same table in such a way that multiple rows of the table are being @@ -159,4 +159,4 @@ WHERE w.city = c.name;

    You will encounter this style of abbreviating quite frequently. -

    Prev Up Next
    2.5. Querying a Table Home 2.7. Aggregate Functions
    \ No newline at end of file +

    Prev Up Next
    2.5. Querying a Table Home 2.7. Aggregate Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-populate.html postgresql-13-13.12/doc/src/sgml/html/tutorial-populate.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-populate.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-populate.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -2.4. Populating a Table With Rows
    2.4. Populating a Table With Rows
    Prev UpChapter 2. The SQL LanguageHome Next

    2.4. Populating a Table With Rows

    +2.4. Populating a Table With Rows

    2.4. Populating a Table With Rows
    Prev UpChapter 2. The SQL LanguageHome Next

    2.4. Populating a Table With Rows

    The INSERT statement is used to populate a table with rows: @@ -56,4 +56,4 @@ machine running the backend process, not the client, since the backend process reads the file directly. You can read more about the COPY command in COPY. -

    Prev Up Next
    2.3. Creating a New Table Home 2.5. Querying a Table
    \ No newline at end of file +

    Prev Up Next
    2.3. Creating a New Table Home 2.5. Querying a Table
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-select.html postgresql-13-13.12/doc/src/sgml/html/tutorial-select.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-select.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-select.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -2.5. Querying a Table
    2.5. Querying a Table
    Prev UpChapter 2. The SQL LanguageHome Next

    2.5. Querying a Table

    +2.5. Querying a Table

    2.5. Querying a Table
    Prev UpChapter 2. The SQL LanguageHome Next

    2.5. Querying a Table

    @@ -139,4 +139,4 @@ required by the SQL standard, and current PostgreSQL does not guarantee that DISTINCT causes the rows to be ordered. -

    Prev Up Next
    2.4. Populating a Table With Rows Home 2.6. Joins Between Tables
    \ No newline at end of file +

    Prev Up Next
    2.4. Populating a Table With Rows Home 2.6. Joins Between Tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-sql-intro.html postgresql-13-13.12/doc/src/sgml/html/tutorial-sql-intro.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-sql-intro.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-sql-intro.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -2.1. Introduction
    2.1. Introduction
    Prev UpChapter 2. The SQL LanguageHome Next

    2.1. Introduction

    +2.1. Introduction

    2.1. Introduction
    Prev UpChapter 2. The SQL LanguageHome Next

    2.1. Introduction

    This chapter provides an overview of how to use SQL to perform simple operations. This tutorial is only intended to give you an introduction and is in no @@ -40,4 +40,4 @@ single step mode which pauses before sending each statement to the server. The commands used in this section are in the file basics.sql. -

    Prev Up Next
    Chapter 2. The SQL Language Home 2.2. Concepts
    \ No newline at end of file +

    Prev Up Next
    Chapter 2. The SQL Language Home 2.2. Concepts
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-sql.html postgresql-13-13.12/doc/src/sgml/html/tutorial-sql.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-sql.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-sql.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 2. The SQL Language
    Chapter 2. The SQL Language
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    1.4. Accessing a Database Home 2.1. Introduction
    \ No newline at end of file +Chapter 2. The SQL Language
    Chapter 2. The SQL Language
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    1.4. Accessing a Database Home 2.1. Introduction
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-start.html postgresql-13-13.12/doc/src/sgml/html/tutorial-start.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-start.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-start.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,2 +1,2 @@ -Chapter 1. Getting Started
    Chapter 1. Getting Started
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    Part I. Tutorial Home 1.1. Installation
    \ No newline at end of file +Chapter 1. Getting Started
    Chapter 1. Getting Started
    Prev UpPart I. TutorialHome Next
    Prev Up Next
    Part I. Tutorial Home 1.1. Installation
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-table.html postgresql-13-13.12/doc/src/sgml/html/tutorial-table.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-table.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-table.html 2023-08-07 20:32:06.000000000 +0000 @@ -1,5 +1,5 @@ -2.3. Creating a New Table
    2.3. Creating a New Table
    Prev UpChapter 2. The SQL LanguageHome Next

    2.3. Creating a New Table

    +2.3. Creating a New Table

    2.3. Creating a New Table
    Prev UpChapter 2. The SQL LanguageHome Next

    2.3. Creating a New Table

    You can create a new table by specifying the table name, along with all column names and their types: @@ -66,4 +66,4 @@ 

     DROP TABLE tablename;

    -

    Prev Up Next
    2.2. Concepts Home 2.4. Populating a Table With Rows
    \ No newline at end of file +

    Prev Up Next
    2.2. Concepts Home 2.4. Populating a Table With Rows
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-transactions.html postgresql-13-13.12/doc/src/sgml/html/tutorial-transactions.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-transactions.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-transactions.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.4. Transactions
    3.4. Transactions
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.4. Transactions

    +3.4. Transactions

    3.4. Transactions
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.4. Transactions

    Transactions are a fundamental concept of all database systems. The essential point of a transaction is that it bundles multiple steps into a single, all-or-nothing operation. The intermediate @@ -139,4 +139,4 @@ transaction block that was put in aborted state by the system due to an error, short of rolling it back completely and starting again. -

    Prev Up Next
    3.3. Foreign Keys Home 3.5. Window Functions
    \ No newline at end of file +

    Prev Up Next
    3.3. Foreign Keys Home 3.5. Window Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-update.html postgresql-13-13.12/doc/src/sgml/html/tutorial-update.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-update.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-update.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -2.8. Updates
    2.8. Updates
    Prev UpChapter 2. The SQL LanguageHome Next

    2.8. Updates

    +2.8. Updates

    2.8. Updates
    Prev UpChapter 2. The SQL LanguageHome Next

    2.8. Updates

    You can update existing rows using the UPDATE command. Suppose you discover the temperature readings are @@ -23,4 +23,4 @@ Hayward | 35 | 52 | | 1994-11-29 (3 rows)

    -

    Prev Up Next
    2.7. Aggregate Functions Home 2.9. Deletions
    \ No newline at end of file +

    Prev Up Next
    2.7. Aggregate Functions Home 2.9. Deletions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-views.html postgresql-13-13.12/doc/src/sgml/html/tutorial-views.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-views.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-views.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.2. Views
    3.2. Views
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.2. Views

    +3.2. Views

    3.2. Views
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.2. Views

    Refer back to the queries in Section 2.6. Suppose the combined listing of weather records and city location is of particular interest to your application, but you do not want @@ -23,4 +23,4 @@

    Views can be used in almost any place a real table can be used. Building views upon other views is not uncommon. -

    Prev Up Next
    3.1. Introduction Home 3.3. Foreign Keys
    \ No newline at end of file +

    Prev Up Next
    3.1. Introduction Home 3.3. Foreign Keys
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial-window.html postgresql-13-13.12/doc/src/sgml/html/tutorial-window.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial-window.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial-window.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -3.5. Window Functions
    3.5. Window Functions
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.5. Window Functions

    +3.5. Window Functions

    3.5. Window Functions
    Prev UpChapter 3. Advanced FeaturesHome Next

    3.5. Window Functions

    A window function performs a calculation across a set of table rows that are somehow related to the current row. This is comparable to the type of calculation that can be done with an aggregate function. @@ -199,4 +199,4 @@ There are options to define the window frame in other ways, but this tutorial does not cover them. See Section 4.2.8 for details. -

    Prev Up Next
    3.4. Transactions Home 3.6. Inheritance
    \ No newline at end of file +

    Prev Up Next
    3.4. Transactions Home 3.6. Inheritance
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/tutorial.html postgresql-13-13.12/doc/src/sgml/html/tutorial.html --- postgresql-13-13.11/doc/src/sgml/html/tutorial.html 2023-05-08 21:33:48.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/tutorial.html 2023-08-07 20:32:07.000000000 +0000 @@ -1,5 +1,5 @@ -Part I. Tutorial
    Part I. Tutorial
    Prev UpPostgreSQL 13.11 DocumentationHome Next
    Prev Up Next
    5. Bug Reporting Guidelines Home Chapter 1. Getting Started
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-func.html postgresql-13-13.12/doc/src/sgml/html/typeconv-func.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-func.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-func.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.3. Functions
    10.3. Functions
    Prev UpChapter 10. Type ConversionHome Next

    10.3. Functions

    +10.3. Functions

    10.3. Functions
    Prev UpChapter 10. Type ConversionHome Next

    10.3. Functions

    The specific function that is referenced by a function call is determined using the following procedure.

    Function Type Resolution

    1. @@ -265,4 +265,4 @@ is no need to have a special case. See CREATE CAST for additional commentary. -

    Prev Up Next
    10.2. Operators Home 10.4. Value Storage
    \ No newline at end of file +

    Prev Up Next
    10.2. Operators Home 10.4. Value Storage
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-oper.html postgresql-13-13.12/doc/src/sgml/html/typeconv-oper.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-oper.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-oper.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.2. Operators
    10.2. Operators
    Prev UpChapter 10. Type ConversionHome Next

    10.2. Operators

    +10.2. Operators

    10.2. Operators
    Prev UpChapter 10. Type ConversionHome Next

    10.2. Operators

    The specific operator that is referenced by an operator expression is determined using the following procedure. Note that this procedure is indirectly affected @@ -244,4 +244,4 @@ search path containing schemas that permit untrusted users to create objects is not a secure schema usage pattern. -

    Prev Up Next
    10.1. Overview Home 10.3. Functions
    \ No newline at end of file +

    Prev Up Next
    10.1. Overview Home 10.3. Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-overview.html postgresql-13-13.12/doc/src/sgml/html/typeconv-overview.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-overview.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-overview.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.1. Overview
    10.1. Overview
    Prev UpChapter 10. Type ConversionHome Next

    10.1. Overview

    +10.1. Overview

    10.1. Overview
    Prev UpChapter 10. Type ConversionHome Next

    10.1. Overview

    SQL is a strongly typed language. That is, every data item has an associated data type which determines its behavior and allowed usage. PostgreSQL has an extensible type system that is @@ -110,4 +110,4 @@ if then the user defines a new function with the correct argument types, the parser should use this new function and no longer do implicit conversion to use the old function.

    -

    Prev Up Next
    Chapter 10. Type Conversion Home 10.2. Operators
    \ No newline at end of file +

    Prev Up Next
    Chapter 10. Type Conversion Home 10.2. Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-query.html postgresql-13-13.12/doc/src/sgml/html/typeconv-query.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-query.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-query.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.4. Value Storage
    10.4. Value Storage
    Prev UpChapter 10. Type ConversionHome Next

    10.4. Value Storage

    +10.4. Value Storage

    10.4. Value Storage
    Prev UpChapter 10. Type ConversionHome Next

    10.4. Value Storage

    Values to be inserted into a table are converted to the destination column's data type according to the following steps. @@ -52,4 +52,4 @@ and applied to the operator's result and the stored column length. This type-specific function performs the required length check and addition of padding spaces. -


    Prev Up Next
    10.3. Functions Home 10.5. UNION, CASE, and Related Constructs
    \ No newline at end of file +


    Prev Up Next
    10.3. Functions Home 10.5. UNION, CASE, and Related Constructs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-select.html postgresql-13-13.12/doc/src/sgml/html/typeconv-select.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-select.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-select.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.6. SELECT Output Columns
    10.6. SELECT Output Columns
    Prev UpChapter 10. Type ConversionHome Next

    10.6. SELECT Output Columns

    +10.6. SELECT Output Columns

    10.6. SELECT Output Columns
    Prev UpChapter 10. Type ConversionHome Next

    10.6. SELECT Output Columns

    The rules given in the preceding sections will result in assignment of non-unknown data types to all expressions in a SQL query, except for unspecified-type literals that appear as simple output @@ -27,4 +27,4 @@ unspecified-type literals in a SELECT output list were left as type unknown. That had assorted bad consequences, so it's been changed. -

    Prev Up Next
    10.5. UNION, CASE, and Related Constructs Home Chapter 11. Indexes
    \ No newline at end of file +

    Prev Up Next
    10.5. UNION, CASE, and Related Constructs Home Chapter 11. Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv-union-case.html postgresql-13-13.12/doc/src/sgml/html/typeconv-union-case.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv-union-case.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv-union-case.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -10.5. UNION, CASE, and Related Constructs
    10.5. UNION, CASE, and Related Constructs
    Prev UpChapter 10. Type ConversionHome Next

    10.5. UNION, CASE, and Related Constructs

    +10.5. UNION, CASE, and Related Constructs

    10.5. UNION, CASE, and Related Constructs
    Prev UpChapter 10. Type ConversionHome Next

    10.5. UNION, CASE, and Related Constructs

    SQL UNION constructs must match up possibly dissimilar types to become a single result set. The resolution algorithm is applied separately to each output column of a union query. The @@ -111,4 +111,4 @@ input, with the THEN clauses(s) considered after that. In all other cases, “left to right” means the order in which the expressions appear in the query text. -

    Prev Up Next
    10.4. Value Storage Home 10.6. SELECT Output Columns
    \ No newline at end of file +

    Prev Up Next
    10.4. Value Storage Home 10.6. SELECT Output Columns
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/typeconv.html postgresql-13-13.12/doc/src/sgml/html/typeconv.html --- postgresql-13-13.11/doc/src/sgml/html/typeconv.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/typeconv.html 2023-08-07 20:32:11.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 10. Type Conversion
    Chapter 10. Type Conversion
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 10. Type Conversion

    Table of Contents

    10.1. Overview
    10.2. Operators
    10.3. Functions
    10.4. Value Storage
    10.5. UNION, CASE, and Related Constructs
    10.6. SELECT Output Columns

    +Chapter 10. Type Conversion

    Chapter 10. Type Conversion
    Prev UpPart II. The SQL LanguageHome Next

    Chapter 10. Type Conversion

    Table of Contents

    10.1. Overview
    10.2. Operators
    10.3. Functions
    10.4. Value Storage
    10.5. UNION, CASE, and Related Constructs
    10.6. SELECT Output Columns

    SQL statements can, intentionally or not, require the mixing of different data types in the same expression. PostgreSQL has extensive facilities for @@ -16,4 +16,4 @@ Refer to the relevant sections in Chapter 8 and Chapter 9 for more information on specific data types and allowed functions and operators. -

    Prev Up Next
    9.30. Statistics Information Functions Home 10.1. Overview
    \ No newline at end of file +

    Prev Up Next
    9.30. Statistics Information Functions Home 10.1. Overview
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/unaccent.html postgresql-13-13.12/doc/src/sgml/html/unaccent.html --- postgresql-13-13.11/doc/src/sgml/html/unaccent.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/unaccent.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.43. unaccent
    F.43. unaccent
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.43. unaccent

    F.43.1. Configuration
    F.43.2. Usage
    F.43.3. Functions

    +F.43. unaccent

    F.43. unaccent
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.43. unaccent

    F.43.1. Configuration
    F.43.2. Usage
    F.43.3. Functions

    unaccent is a text search dictionary that removes accents (diacritic signs) from lexemes. It's a filtering dictionary, which means its output is @@ -128,4 +128,4 @@ SELECT unaccent('unaccent', 'Hôtel'); SELECT unaccent('Hôtel');

    -

    Prev Up Next
    F.42. tsm_system_time Home F.44. uuid-ossp
    \ No newline at end of file +

    Prev Up Next
    F.42. tsm_system_time Home F.44. uuid-ossp
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/unsupported-features-sql-standard.html postgresql-13-13.12/doc/src/sgml/html/unsupported-features-sql-standard.html --- postgresql-13-13.11/doc/src/sgml/html/unsupported-features-sql-standard.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/unsupported-features-sql-standard.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,9 +1,9 @@ -D.2. Unsupported Features
    D.2. Unsupported Features
    Prev UpAppendix D. SQL ConformanceHome Next

    D.2. Unsupported Features

    +D.2. Unsupported Features

    D.2. Unsupported Features
    Prev UpAppendix D. SQL ConformanceHome Next

    D.2. Unsupported Features

    The following features defined in SQL:2016 are not implemented in this release of PostgreSQL. In a few cases, equivalent functionality is available.

    IdentifierCore?DescriptionComment
    B011 Embedded Ada 
    B013 Embedded COBOL 
    B014 Embedded Fortran 
    B015 Embedded MUMPS 
    B016 Embedded Pascal 
    B017 Embedded PL/I 
    B031 Basic dynamic SQL 
    B032 Extended dynamic SQL 
    B032-01 <describe input statement> 
    B033 Untyped SQL-invoked function arguments 
    B034 Dynamic specification of cursor attributes 
    B035 Non-extended descriptor names 
    B041 Extensions to embedded SQL exception declarations 
    B051 Enhanced execution rights 
    B111 Module language Ada 
    B112 Module language C 
    B113 Module language COBOL 
    B114 Module language Fortran 
    B115 Module language MUMPS 
    B116 Module language Pascal 
    B117 Module language PL/I 
    B121 Routine language Ada 
    B122 Routine language C 
    B123 Routine language COBOL 
    B124 Routine language Fortran 
    B125 Routine language MUMPS 
    B126 Routine language Pascal 
    B127 Routine language PL/I 
    B128 Routine language SQL 
    B200 Polymorphic table functions 
    B201 More than one PTF generic table parameter 
    B202 PTF Copartitioning 
    B203 More than one copartition specification 
    B204 PRUNE WHEN EMPTY 
    B205 Pass-through columns 
    B206 PTF descriptor parameters 
    B207 Cross products of partitionings 
    B208 PTF component procedure interface 
    B209 PTF extended names 
    B211 Module language Ada: VARCHAR and NUMERIC support 
    B221 Routine language Ada: VARCHAR and NUMERIC support 
    F054 TIMESTAMP in DATE type precedence list 
    F121 Basic diagnostics management 
    F121-01 GET DIAGNOSTICS statement 
    F121-02 SET TRANSACTION statement: DIAGNOSTICS SIZE clause 
    F122 Enhanced diagnostics management 
    F123 All diagnostics 
    F263 Comma-separated predicates in simple CASE expression 
    F291 UNIQUE predicate 
    F301 CORRESPONDING in query expressions 
    F312 MERGE statementconsider INSERT ... ON CONFLICT DO UPDATE
    F313 Enhanced MERGE statement 
    F314 MERGE statement with DELETE branch 
    F341 Usage tablesno ROUTINE_*_USAGE tables
    F403 Partitioned joined tables 
    F404 Range variable for common column names 
    F451 Character set definition 
    F461 Named character sets 
    F492 Optional table constraint enforcement 
    F521 Assertions 
    F671 Subqueries in CHECKintentionally omitted
    F673 Reads SQL-data routine invocations in CHECK constraints 
    F693 SQL-session and client module collations 
    F695 Translation support 
    F696 Additional translation documentation 
    F721 Deferrable constraintsforeign and unique keys only
    F741 Referential MATCH typesno partial match yet
    F812CoreBasic flagging 
    F813 Extended flagging 
    F821 Local table references 
    F831 Full cursor update 
    F831-01 Updatable scrollable cursors 
    F831-02 Updatable ordered cursors 
    F841 LIKE_REGEX predicate 
    F842 OCCURRENCES_REGEX function 
    F843 POSITION_REGEX function 
    F844 SUBSTRING_REGEX function 
    F845 TRANSLATE_REGEX function 
    F846 Octet support in regular expression operators 
    F847 Nonconstant regular expressions 
    F866 FETCH FIRST clause: PERCENT option 
    R010 Row pattern recognition: FROM clause 
    R020 Row pattern recognition: WINDOW clause 
    R030 Row pattern recognition: full aggregate support 
    S011CoreDistinct data types 
    S011-01CoreUSER_DEFINED_TYPES view 
    S023 Basic structured types 
    S024 Enhanced structured types 
    S025 Final structured types 
    S026 Self-referencing structured types 
    S027 Create method by specific method name 
    S028 Permutable UDT options list 
    S041 Basic reference types 
    S043 Enhanced reference types 
    S051 Create table of typepartially supported
    S081 Subtables 
    S091 Basic array supportpartially supported
    S091-01 Arrays of built-in data types 
    S091-02 Arrays of distinct types 
    S091-03 Array expressions 
    S094 Arrays of reference types 
    S097 Array element assignment 
    S151 Type predicate 
    S161 Subtype treatment 
    S162 Subtype treatment for references 
    S202 SQL-invoked routines on multisets 
    S231 Structured type locators 
    S232 Array locators 
    S233 Multiset locators 
    S241 Transform functions 
    S242 Alter transform statement 
    S251 User-defined orderings 
    S261 Specific type method 
    S271 Basic multiset support 
    S272 Multisets of user-defined types 
    S274 Multisets of reference types 
    S275 Advanced multiset support 
    S281 Nested collection types 
    S291 Unique constraint on entire row 
    S401 Distinct types based on array types 
    S402 Distinct types based on distinct types 
    S403 ARRAY_MAX_CARDINALITY 
    S404 TRIM_ARRAY 
    T011 Timestamp in Information Schema 
    T021 BINARY and VARBINARY data types 
    T022 Advanced support for BINARY and VARBINARY data types 
    T023 Compound binary literal 
    T024 Spaces in binary literals 
    T041 Basic LOB data type support 
    T041-01 BLOB data type 
    T041-02 CLOB data type 
    T041-03 POSITION, LENGTH, LOWER, TRIM, UPPER, and SUBSTRING functions for LOB data types 
    T041-04 Concatenation of LOB data types 
    T041-05 LOB locator: non-holdable 
    T042 Extended LOB data type support 
    T043 Multiplier T 
    T044 Multiplier P 
    T051 Row types 
    T053 Explicit aliases for all-fields reference 
    T061 UCS support 
    T076 DECFLOAT data type 
    T101 Enhanced nullability determination 
    T111 Updatable joins, unions, and columns 
    T175 Generated columnsmostly supported
    T176 Sequence generator supportsupported except for NEXT VALUE FOR
    T180 System-versioned tables 
    T181 Application-time period tables 
    T211 Basic trigger capability 
    T211-06 Support for run-time rules for the interaction of triggers and constraints 
    T211-08 Multiple triggers for the same event are executed in the order in which they were created in the catalogintentionally omitted
    T251 SET TRANSACTION statement: LOCAL option 
    T272 Enhanced savepoint management 
    T301 Functional dependenciespartially supported
    T321CoreBasic SQL-invoked routines 
    T321-05CoreRETURN statement 
    T322 Declared data type attributes 
    T324 Explicit security for SQL routines 
    T326 Table functions 
    T332 Extended rolesmostly supported
    T434 GROUP BY DISTINCT 
    T471 Result sets return value 
    T472 DESCRIBE CURSOR 
    T495 Combined data change and retrievaldifferent syntax
    T502 Period predicates 
    T511 Transaction counts 
    T522 Default values for IN parameters of SQL-invoked proceduressupported except DEFAULT key word in invocation
    T561 Holdable locators 
    T571 Array-returning external SQL-invoked functions 
    T572 Multiset-returning external SQL-invoked functions 
    T601 Local cursor references 
    T616 Null treatment option for LEAD and LAG functions 
    T618 NTH_VALUE functionfunction exists, but some options missing
    T619 Nested window functions 
    T625 LISTAGG 
    T641 Multiple column assignmentonly some syntax variants supported
    T652 SQL-dynamic statements in SQL routines 
    T654 SQL-dynamic statements in external routines 
    T811 Basic SQL/JSON constructor functions 
    T812 SQL/JSON: JSON_OBJECTAGG 
    T813 SQL/JSON: JSON_ARRAYAGG with ORDER BY 
    T814 Colon in JSON_OBJECT or JSON_OBJECTAGG 
    T821 Basic SQL/JSON query operators 
    T822 SQL/JSON: IS JSON WITH UNIQUE KEYS predicate 
    T823 SQL/JSON: PASSING clause 
    T824 JSON_TABLE: specific PLAN clause 
    T825 SQL/JSON: ON EMPTY and ON ERROR clauses 
    T826 General value expression in ON ERROR or ON EMPTY clauses 
    T827 JSON_TABLE: sibling NESTED COLUMNS clauses 
    T828 JSON_QUERY 
    T829 JSON_QUERY: array wrapper options 
    T830 Enforcing unique keys in SQL/JSON constructor functions 
    T838 JSON_TABLE: PLAN DEFAULT clause 
    T839 Formatted cast of datetimes to/from character strings 
    M001 Datalinks 
    M002 Datalinks via SQL/CLI 
    M003 Datalinks via Embedded SQL 
    M004 Foreign data supportpartially supported
    M005 Foreign schema support 
    M006 GetSQLString routine 
    M007 TransmitRequest 
    M009 GetOpts and GetStatistics routines 
    M010 Foreign data wrapper supportdifferent API
    M011 Datalinks via Ada 
    M012 Datalinks via C 
    M013 Datalinks via COBOL 
    M014 Datalinks via Fortran 
    M015 Datalinks via M 
    M016 Datalinks via Pascal 
    M017 Datalinks via PL/I 
    M018 Foreign data wrapper interface routines in Ada 
    M019 Foreign data wrapper interface routines in Cdifferent API
    M020 Foreign data wrapper interface routines in COBOL 
    M021 Foreign data wrapper interface routines in Fortran 
    M022 Foreign data wrapper interface routines in MUMPS 
    M023 Foreign data wrapper interface routines in Pascal 
    M024 Foreign data wrapper interface routines in PL/I 
    M030 SQL-server foreign data support 
    M031 Foreign data wrapper general routines 
    X012 Multisets of XML type 
    X013 Distinct types of XML type 
    X015 Fields of XML type 
    X025 XMLCast 
    X030 XMLDocument 
    X038 XMLText 
    X065 XMLParse: BLOB input and CONTENT option 
    X066 XMLParse: BLOB input and DOCUMENT option 
    X068 XMLSerialize: BOM 
    X069 XMLSerialize: INDENT 
    X073 XMLSerialize: BLOB serialization and CONTENT option 
    X074 XMLSerialize: BLOB serialization and DOCUMENT option 
    X075 XMLSerialize: BLOB serialization 
    X076 XMLSerialize: VERSION 
    X077 XMLSerialize: explicit ENCODING option 
    X078 XMLSerialize: explicit XML declaration 
    X080 Namespaces in XML publishing 
    X081 Query-level XML namespace declarations 
    X082 XML namespace declarations in DML 
    X083 XML namespace declarations in DDL 
    X084 XML namespace declarations in compound statements 
    X085 Predefined namespace prefixes 
    X086 XML namespace declarations in XMLTable 
    X091 XML content predicate 
    X096 XMLExistsXPath 1.0 only
    X100 Host language support for XML: CONTENT option 
    X101 Host language support for XML: DOCUMENT option 
    X110 Host language support for XML: VARCHAR mapping 
    X111 Host language support for XML: CLOB mapping 
    X112 Host language support for XML: BLOB mapping 
    X113 Host language support for XML: STRIP WHITESPACE option 
    X114 Host language support for XML: PRESERVE WHITESPACE option 
    X131 Query-level XMLBINARY clause 
    X132 XMLBINARY clause in DML 
    X133 XMLBINARY clause in DDL 
    X134 XMLBINARY clause in compound statements 
    X135 XMLBINARY clause in subqueries 
    X141 IS VALID predicate: data-driven case 
    X142 IS VALID predicate: ACCORDING TO clause 
    X143 IS VALID predicate: ELEMENT clause 
    X144 IS VALID predicate: schema location 
    X145 IS VALID predicate outside check constraints 
    X151 IS VALID predicate with DOCUMENT option 
    X152 IS VALID predicate with CONTENT option 
    X153 IS VALID predicate with SEQUENCE option 
    X155 IS VALID predicate: NAMESPACE without ELEMENT clause 
    X157 IS VALID predicate: NO NAMESPACE with ELEMENT clause 
    X160 Basic Information Schema for registered XML Schemas 
    X161 Advanced Information Schema for registered XML Schemas 
    X170 XML null handling options 
    X171 NIL ON NO CONTENT option 
    X181 XML(DOCUMENT(UNTYPED)) type 
    X182 XML(DOCUMENT(ANY)) type 
    X190 XML(SEQUENCE) type 
    X191 XML(DOCUMENT(XMLSCHEMA)) type 
    X192 XML(CONTENT(XMLSCHEMA)) type 
    X200 XMLQuery 
    X201 XMLQuery: RETURNING CONTENT 
    X202 XMLQuery: RETURNING SEQUENCE 
    X203 XMLQuery: passing a context item 
    X204 XMLQuery: initializing an XQuery variable 
    X205 XMLQuery: EMPTY ON EMPTY option 
    X206 XMLQuery: NULL ON EMPTY option 
    X211 XML 1.1 support 
    X222 XML passing mechanism BY REFparser accepts BY REF but ignores it; passing is always BY VALUE
    X231 XML(CONTENT(UNTYPED)) type 
    X232 XML(CONTENT(ANY)) type 
    X241 RETURNING CONTENT in XML publishing 
    X242 RETURNING SEQUENCE in XML publishing 
    X251 Persistent XML values of XML(DOCUMENT(UNTYPED)) type 
    X252 Persistent XML values of XML(DOCUMENT(ANY)) type 
    X253 Persistent XML values of XML(CONTENT(UNTYPED)) type 
    X254 Persistent XML values of XML(CONTENT(ANY)) type 
    X255 Persistent XML values of XML(SEQUENCE) type 
    X256 Persistent XML values of XML(DOCUMENT(XMLSCHEMA)) type 
    X257 Persistent XML values of XML(CONTENT(XMLSCHEMA)) type 
    X260 XML type: ELEMENT clause 
    X261 XML type: NAMESPACE without ELEMENT clause 
    X263 XML type: NO NAMESPACE with ELEMENT clause 
    X264 XML type: schema location 
    X271 XMLValidate: data-driven case 
    X272 XMLValidate: ACCORDING TO clause 
    X273 XMLValidate: ELEMENT clause 
    X274 XMLValidate: schema location 
    X281 XMLValidate with DOCUMENT option 
    X282 XMLValidate with CONTENT option 
    X283 XMLValidate with SEQUENCE option 
    X284 XMLValidate: NAMESPACE without ELEMENT clause 
    X286 XMLValidate: NO NAMESPACE with ELEMENT clause 
    X300 XMLTableXPath 1.0 only
    X305 XMLTable: initializing an XQuery variable 

    -

    Prev Up Next
    D.1. Supported Features Home D.3. XML Limits and Conformance to SQL/XML
    \ No newline at end of file +

    Prev Up Next
    D.1. Supported Features Home D.3. XML Limits and Conformance to SQL/XML
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/upgrading.html postgresql-13-13.12/doc/src/sgml/html/upgrading.html --- postgresql-13-13.11/doc/src/sgml/html/upgrading.html 2023-05-08 21:33:53.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/upgrading.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -18.6. Upgrading a PostgreSQL Cluster
    18.6. Upgrading a PostgreSQL Cluster
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.6. Upgrading a PostgreSQL Cluster

    18.6.1. Upgrading Data via pg_dumpall
    18.6.2. Upgrading Data via pg_upgrade
    18.6.3. Upgrading Data via Replication

    +18.6. Upgrading a PostgreSQL Cluster

    18.6. Upgrading a PostgreSQL Cluster
    Prev UpChapter 18. Server Setup and OperationHome Next

    18.6. Upgrading a PostgreSQL Cluster

    18.6.1. Upgrading Data via pg_dumpall
    18.6.2. Upgrading Data via pg_upgrade
    18.6.3. Upgrading Data via Replication

    This section discusses how to upgrade your database data from one PostgreSQL release to a newer one.

    @@ -100,7 +100,7 @@ To make the backup, you can use the pg_dumpall command from the version you are currently running; see Section 25.1.2 for more details. For best results, however, try to use the pg_dumpall - command from PostgreSQL 13.11, + command from PostgreSQL 13.12, since this version contains bug fixes and improvements over older versions. While this advice might seem idiosyncratic since you haven't installed the new version yet, it is advisable to follow @@ -192,4 +192,4 @@ systems such as pglogical, Slony, Londiste, and Bucardo. -

    Prev Up Next
    18.5. Shutting Down the Server Home 18.7. Preventing Server Spoofing
    \ No newline at end of file +

    Prev Up Next
    18.5. Shutting Down the Server Home 18.7. Preventing Server Spoofing
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/user-manag.html postgresql-13-13.12/doc/src/sgml/html/user-manag.html --- postgresql-13-13.11/doc/src/sgml/html/user-manag.html 2023-05-08 21:33:54.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/user-manag.html 2023-08-07 20:32:13.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 21. Database Roles
    Chapter 21. Database Roles
    Prev UpPart III. Server AdministrationHome Next

    Chapter 21. Database Roles

    Table of Contents

    21.1. Database Roles
    21.2. Role Attributes
    21.3. Role Membership
    21.4. Dropping Roles
    21.5. Default Roles
    21.6. Function Security

    +Chapter 21. Database Roles

    Chapter 21. Database Roles
    Prev UpPart III. Server AdministrationHome Next

    Chapter 21. Database Roles

    Table of Contents

    21.1. Database Roles
    21.2. Role Attributes
    21.3. Role Membership
    21.4. Dropping Roles
    21.5. Default Roles
    21.6. Function Security

    PostgreSQL manages database access permissions using the concept of roles. A role can be thought of as either a database user, or a group of database users, depending on how @@ -17,4 +17,4 @@ This chapter describes how to create and manage roles. More information about the effects of role privileges on various database objects can be found in Section 5.7. -

    Prev Up Next
    20.15. Authentication Problems Home 21.1. Database Roles
    \ No newline at end of file +

    Prev Up Next
    20.15. Authentication Problems Home 21.1. Database Roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/using-explain.html postgresql-13-13.12/doc/src/sgml/html/using-explain.html --- postgresql-13-13.11/doc/src/sgml/html/using-explain.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/using-explain.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -14.1. Using EXPLAIN
    14.1. Using EXPLAIN
    Prev UpChapter 14. Performance TipsHome Next

    14.1. Using EXPLAIN

    14.1.1. EXPLAIN Basics
    14.1.2. EXPLAIN ANALYZE
    14.1.3. Caveats

    +14.1. Using EXPLAIN

    14.1. Using EXPLAIN
    Prev UpChapter 14. Performance TipsHome Next

    14.1. Using EXPLAIN

    14.1.1. EXPLAIN Basics
    14.1.2. EXPLAIN ANALYZE
    14.1.3. Caveats

    PostgreSQL devises a query plan for each query it receives. Choosing the right plan to match the query structure and the properties of the data @@ -798,4 +798,4 @@ the EXPLAIN output and a Subplans Removed: N annotation appears instead. -

    Prev Up Next
    Chapter 14. Performance Tips Home 14.2. Statistics Used by the Planner
    \ No newline at end of file +

    Prev Up Next
    Chapter 14. Performance Tips Home 14.2. Statistics Used by the Planner
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/uuid-ossp.html postgresql-13-13.12/doc/src/sgml/html/uuid-ossp.html --- postgresql-13-13.11/doc/src/sgml/html/uuid-ossp.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/uuid-ossp.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.44. uuid-ossp
    F.44. uuid-ossp
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.44. uuid-ossp

    F.44.1. uuid-ossp Functions
    F.44.2. Building uuid-ossp
    F.44.3. Author

    +F.44. uuid-ossp

    F.44. uuid-ossp
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.44. uuid-ossp

    F.44.1. uuid-ossp Functions
    F.44.2. Building uuid-ossp
    F.44.3. Author

    The uuid-ossp module provides functions to generate universally unique identifiers (UUIDs) using one of several standard algorithms. There are also functions to produce certain special UUID constants. @@ -140,4 +140,4 @@ machine, so configure does not automatically choose one.

    F.44.3. Author

    Peter Eisentraut -

    Prev Up Next
    F.43. unaccent Home F.45. xml2
    \ No newline at end of file +

    Prev Up Next
    F.43. unaccent Home F.45. xml2
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/vacuumlo.html postgresql-13-13.12/doc/src/sgml/html/vacuumlo.html --- postgresql-13-13.11/doc/src/sgml/html/vacuumlo.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/vacuumlo.html 2023-08-07 20:32:38.000000000 +0000 @@ -1,5 +1,5 @@ -vacuumlo
    vacuumlo
    Prev UpG.1. Client ApplicationsHome Next

    vacuumlo

    vacuumlo — remove orphaned large objects from a PostgreSQL database

    Synopsis

    vacuumlo [option...] dbname...

    Description

    +vacuumlo

    vacuumlo
    Prev UpG.1. Client ApplicationsHome Next

    vacuumlo

    vacuumlo — remove orphaned large objects from a PostgreSQL database

    Synopsis

    vacuumlo [option...] dbname...

    Description

    vacuumlo is a simple utility program that will remove any “orphaned” large objects from a PostgreSQL database. An orphaned large object (LO) is @@ -71,4 +71,4 @@ temporary table identify orphaned LOs. These are removed.

    Author

    Peter Mount -

    Prev Up Next
    oid2name Home G.2. Server Applications
    \ No newline at end of file +

    Prev Up Next
    oid2name Home G.2. Server Applications
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-available-extension-versions.html postgresql-13-13.12/doc/src/sgml/html/view-pg-available-extension-versions.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-available-extension-versions.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-available-extension-versions.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.66. pg_available_extension_versions
    51.66. pg_available_extension_versions
    Prev UpChapter 51. System CatalogsHome Next

    51.66. pg_available_extension_versions

    +51.66. pg_available_extension_versions

    51.66. pg_available_extension_versions
    Prev UpChapter 51. System CatalogsHome Next

    51.66. pg_available_extension_versions

    The pg_available_extension_versions view lists the specific extension versions that are available for installation. See also the pg_extension @@ -62,4 +62,4 @@


    The pg_available_extension_versions view is read only. -

    Prev Up Next
    51.65. pg_available_extensions Home 51.67. pg_config
    \ No newline at end of file +

    Prev Up Next
    51.65. pg_available_extensions Home 51.67. pg_config
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-available-extensions.html postgresql-13-13.12/doc/src/sgml/html/view-pg-available-extensions.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-available-extensions.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-available-extensions.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.65. pg_available_extensions
    51.65. pg_available_extensions
    Prev UpChapter 51. System CatalogsHome Next

    51.65. pg_available_extensions

    +51.65. pg_available_extensions

    51.65. pg_available_extensions
    Prev UpChapter 51. System CatalogsHome Next

    51.65. pg_available_extensions

    The pg_available_extensions view lists the extensions that are available for installation. See also the @@ -34,4 +34,4 @@ Comment string from the extension's control file


    The pg_available_extensions view is read only. -

    Prev Up Next
    51.64. System Views Home 51.66. pg_available_extension_versions
    \ No newline at end of file +

    Prev Up Next
    51.64. System Views Home 51.66. pg_available_extension_versions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-config.html postgresql-13-13.12/doc/src/sgml/html/view-pg-config.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-config.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-config.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.67. pg_config
    51.67. pg_config
    Prev UpChapter 51. System CatalogsHome Next

    51.67. pg_config

    +51.67. pg_config

    51.67. pg_config
    Prev UpChapter 51. System CatalogsHome Next

    51.67. pg_config

    The view pg_config describes the compile-time configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to @@ -26,4 +26,4 @@

    The parameter value -


    Prev Up Next
    51.66. pg_available_extension_versions Home 51.68. pg_cursors
    \ No newline at end of file +


    Prev Up Next
    51.66. pg_available_extension_versions Home 51.68. pg_cursors
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-cursors.html postgresql-13-13.12/doc/src/sgml/html/view-pg-cursors.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-cursors.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-cursors.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.68. pg_cursors
    51.68. pg_cursors
    Prev UpChapter 51. System CatalogsHome Next

    51.68. pg_cursors

    +51.68. pg_cursors

    51.68. pg_cursors
    Prev UpChapter 51. System CatalogsHome Next

    51.68. pg_cursors

    The pg_cursors view lists the cursors that are currently available. Cursors can be defined in several ways:

    • @@ -69,4 +69,4 @@ The time at which the cursor was declared


    The pg_cursors view is read only. -

    Prev Up Next
    51.67. pg_config Home 51.69. pg_file_settings
    \ No newline at end of file +

    Prev Up Next
    51.67. pg_config Home 51.69. pg_file_settings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-file-settings.html postgresql-13-13.12/doc/src/sgml/html/view-pg-file-settings.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-file-settings.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-file-settings.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.69. pg_file_settings
    51.69. pg_file_settings
    Prev UpChapter 51. System CatalogsHome Next

    51.69. pg_file_settings

    +51.69. pg_file_settings

    51.69. pg_file_settings
    Prev UpChapter 51. System CatalogsHome Next

    51.69. pg_file_settings

    The view pg_file_settings provides a summary of the contents of the server's configuration file(s). A row appears in this view for each “name = value” entry appearing in the files, @@ -74,4 +74,4 @@

    See Section 19.1 for more information about the various ways to change run-time parameters. -

    Prev Up Next
    51.68. pg_cursors Home 51.70. pg_group
    \ No newline at end of file +

    Prev Up Next
    51.68. pg_cursors Home 51.70. pg_group
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-group.html postgresql-13-13.12/doc/src/sgml/html/view-pg-group.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-group.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-group.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.70. pg_group
    51.70. pg_group
    Prev UpChapter 51. System CatalogsHome Next

    51.70. pg_group

    +51.70. pg_group

    51.70. pg_group
    Prev UpChapter 51. System CatalogsHome Next

    51.70. pg_group

    The view pg_group exists for backwards compatibility: it emulates a catalog that existed in PostgreSQL before version 8.1. @@ -29,4 +29,4 @@

    An array containing the IDs of the roles in this group -


    Prev Up Next
    51.69. pg_file_settings Home 51.71. pg_hba_file_rules
    \ No newline at end of file +


    Prev Up Next
    51.69. pg_file_settings Home 51.71. pg_hba_file_rules
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-hba-file-rules.html postgresql-13-13.12/doc/src/sgml/html/view-pg-hba-file-rules.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-hba-file-rules.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-hba-file-rules.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.71. pg_hba_file_rules
    51.71. pg_hba_file_rules
    Prev UpChapter 51. System CatalogsHome Next

    51.71. pg_hba_file_rules

    +51.71. pg_hba_file_rules

    51.71. pg_hba_file_rules
    Prev UpChapter 51. System CatalogsHome Next

    51.71. pg_hba_file_rules

    The view pg_hba_file_rules provides a summary of the contents of the client authentication configuration file, pg_hba.conf. A row appears in this view for each @@ -72,4 +72,4 @@

    See Chapter 20 for more information about client authentication configuration. -

    Prev Up Next
    51.70. pg_group Home 51.72. pg_indexes
    \ No newline at end of file +

    Prev Up Next
    51.70. pg_group Home 51.72. pg_indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-indexes.html postgresql-13-13.12/doc/src/sgml/html/view-pg-indexes.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-indexes.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-indexes.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.72. pg_indexes
    51.72. pg_indexes
    Prev UpChapter 51. System CatalogsHome Next

    51.72. pg_indexes

    +51.72. pg_indexes

    51.72. pg_indexes
    Prev UpChapter 51. System CatalogsHome Next

    51.72. pg_indexes

    The view pg_indexes provides access to useful information about each index in the database.

    Table 51.73. pg_indexes Columns

    @@ -37,4 +37,4 @@

    Index definition (a reconstructed CREATE INDEX command) -


    Prev Up Next
    51.71. pg_hba_file_rules Home 51.73. pg_locks
    \ No newline at end of file +


    Prev Up Next
    51.71. pg_hba_file_rules Home 51.73. pg_locks
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-locks.html postgresql-13-13.12/doc/src/sgml/html/view-pg-locks.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-locks.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-locks.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.73. pg_locks
    51.73. pg_locks
    Prev UpChapter 51. System CatalogsHome Next

    51.73. pg_locks

    +51.73. pg_locks

    51.73. pg_locks
    Prev UpChapter 51. System CatalogsHome Next

    51.73. pg_locks

    The view pg_locks provides access to information about the locks held by active processes within the database server. See Chapter 13 for more discussion @@ -243,4 +243,4 @@ The locks are held only for the minimum amount of time necessary to obtain data from the lock managers, but this does not completely eliminate the possibility of a performance impact. -

    Prev Up Next
    51.72. pg_indexes Home 51.74. pg_matviews
    \ No newline at end of file +

    Prev Up Next
    51.72. pg_indexes Home 51.74. pg_matviews
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-matviews.html postgresql-13-13.12/doc/src/sgml/html/view-pg-matviews.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-matviews.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-matviews.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.74. pg_matviews
    51.74. pg_matviews
    Prev UpChapter 51. System CatalogsHome Next

    51.74. pg_matviews

    +51.74. pg_matviews

    51.74. pg_matviews
    Prev UpChapter 51. System CatalogsHome Next

    51.74. pg_matviews

    The view pg_matviews provides access to useful information about each materialized view in the database.

    Table 51.75. pg_matviews Columns

    @@ -46,4 +46,4 @@

    Materialized view definition (a reconstructed SELECT query) -


    Prev Up Next
    51.73. pg_locks Home 51.75. pg_policies
    \ No newline at end of file +


    Prev Up Next
    51.73. pg_locks Home 51.75. pg_policies
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-policies.html postgresql-13-13.12/doc/src/sgml/html/view-pg-policies.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-policies.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-policies.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.75. pg_policies
    51.75. pg_policies
    Prev UpChapter 51. System CatalogsHome Next

    51.75. pg_policies

    +51.75. pg_policies

    51.75. pg_policies
    Prev UpChapter 51. System CatalogsHome Next

    51.75. pg_policies

    The view pg_policies provides access to useful information about each row-level security policy in the database.

    Table 51.76. pg_policies Columns

    @@ -52,4 +52,4 @@

    The expression added to the WITH CHECK qualifications for queries that attempt to add rows to this table -


    Prev Up Next
    51.74. pg_matviews Home 51.76. pg_prepared_statements
    \ No newline at end of file +


    Prev Up Next
    51.74. pg_matviews Home 51.76. pg_prepared_statements
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-prepared-statements.html postgresql-13-13.12/doc/src/sgml/html/view-pg-prepared-statements.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-prepared-statements.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-prepared-statements.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.76. pg_prepared_statements
    51.76. pg_prepared_statements
    Prev UpChapter 51. System CatalogsHome Next

    51.76. pg_prepared_statements

    +51.76. pg_prepared_statements

    51.76. pg_prepared_statements
    Prev UpChapter 51. System CatalogsHome Next

    51.76. pg_prepared_statements

    The pg_prepared_statements view displays all the prepared statements that are available in the current session. See PREPARE for more information about prepared @@ -52,4 +52,4 @@ frontend/backend protocol


    The pg_prepared_statements view is read only. -

    Prev Up Next
    51.75. pg_policies Home 51.77. pg_prepared_xacts
    \ No newline at end of file +

    Prev Up Next
    51.75. pg_policies Home 51.77. pg_prepared_xacts
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-prepared-xacts.html postgresql-13-13.12/doc/src/sgml/html/view-pg-prepared-xacts.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-prepared-xacts.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-prepared-xacts.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.77. pg_prepared_xacts
    51.77. pg_prepared_xacts
    Prev UpChapter 51. System CatalogsHome Next

    51.77. pg_prepared_xacts

    +51.77. pg_prepared_xacts

    51.77. pg_prepared_xacts
    Prev UpChapter 51. System CatalogsHome Next

    51.77. pg_prepared_xacts

    The view pg_prepared_xacts displays information about transactions that are currently prepared for two-phase commit (see PREPARE TRANSACTION for details). @@ -47,4 +47,4 @@ normal operations longer than necessary. Nonetheless there could be some impact on database performance if this view is frequently accessed. -

    Prev Up Next
    51.76. pg_prepared_statements Home 51.78. pg_publication_tables
    \ No newline at end of file +

    Prev Up Next
    51.76. pg_prepared_statements Home 51.78. pg_publication_tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-publication-tables.html postgresql-13-13.12/doc/src/sgml/html/view-pg-publication-tables.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-publication-tables.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-publication-tables.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.78. pg_publication_tables
    51.78. pg_publication_tables
    Prev UpChapter 51. System CatalogsHome Next

    51.78. pg_publication_tables

    +51.78. pg_publication_tables

    51.78. pg_publication_tables
    Prev UpChapter 51. System CatalogsHome Next

    51.78. pg_publication_tables

    The view pg_publication_tables provides information about the mapping between publications and the tables they contain. Unlike the underlying @@ -29,4 +29,4 @@

    Name of table -


    Prev Up Next
    51.77. pg_prepared_xacts Home 51.79. pg_replication_origin_status
    \ No newline at end of file +


    Prev Up Next
    51.77. pg_prepared_xacts Home 51.79. pg_replication_origin_status
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-replication-origin-status.html postgresql-13-13.12/doc/src/sgml/html/view-pg-replication-origin-status.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-replication-origin-status.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-replication-origin-status.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.79. pg_replication_origin_status
    51.79. pg_replication_origin_status
    Prev UpChapter 51. System CatalogsHome Next

    51.79. pg_replication_origin_status

    +51.79. pg_replication_origin_status

    51.79. pg_replication_origin_status
    Prev UpChapter 51. System CatalogsHome Next

    51.79. pg_replication_origin_status

    The pg_replication_origin_status view contains information about how far replay for a certain origin has progressed. For more on replication origins @@ -33,4 +33,4 @@ This node's LSN at which remote_lsn has been replicated. Used to flush commit records before persisting data to disk when using asynchronous commits. -


    Prev Up Next
    51.78. pg_publication_tables Home 51.80. pg_replication_slots
    \ No newline at end of file +


    Prev Up Next
    51.78. pg_publication_tables Home 51.80. pg_replication_slots
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-replication-slots.html postgresql-13-13.12/doc/src/sgml/html/view-pg-replication-slots.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-replication-slots.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-replication-slots.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.80. pg_replication_slots
    51.80. pg_replication_slots
    Prev UpChapter 51. System CatalogsHome Next

    51.80. pg_replication_slots

    +51.80. pg_replication_slots

    51.80. pg_replication_slots
    Prev UpChapter 51. System CatalogsHome Next

    51.80. pg_replication_slots

    The pg_replication_slots view provides a listing of all replication slots that currently exist on the database cluster, along with their current state. @@ -122,4 +122,4 @@ is not in danger of getting in state "lost". It is NULL for lost slots, as well as if max_slot_wal_keep_size is -1. -


    Prev Up Next
    51.79. pg_replication_origin_status Home 51.81. pg_roles
    \ No newline at end of file +


    Prev Up Next
    51.79. pg_replication_origin_status Home 51.81. pg_roles
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-roles.html postgresql-13-13.12/doc/src/sgml/html/view-pg-roles.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-roles.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-roles.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.81. pg_roles
    51.81. pg_roles
    Prev UpChapter 51. System CatalogsHome Next

    51.81. pg_roles

    +51.81. pg_roles

    51.81. pg_roles
    Prev UpChapter 51. System CatalogsHome Next

    51.81. pg_roles

    The view pg_roles provides access to information about database roles. This is simply a publicly readable view of @@ -82,4 +82,4 @@

    ID of role -


    Prev Up Next
    51.80. pg_replication_slots Home 51.82. pg_rules
    \ No newline at end of file +


    Prev Up Next
    51.80. pg_replication_slots Home 51.82. pg_rules
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-rules.html postgresql-13-13.12/doc/src/sgml/html/view-pg-rules.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-rules.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-rules.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.82. pg_rules
    51.82. pg_rules
    Prev UpChapter 51. System CatalogsHome Next

    51.82. pg_rules

    +51.82. pg_rules

    51.82. pg_rules
    Prev UpChapter 51. System CatalogsHome Next

    51.82. pg_rules

    The view pg_rules provides access to useful information about query rewrite rules.

    Table 51.83. pg_rules Columns

    @@ -34,4 +34,4 @@ The pg_rules view excludes the ON SELECT rules of views and materialized views; those can be seen in pg_views and pg_matviews. -

    Prev Up Next
    51.81. pg_roles Home 51.83. pg_seclabels
    \ No newline at end of file +

    Prev Up Next
    51.81. pg_roles Home 51.83. pg_seclabels
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-seclabels.html postgresql-13-13.12/doc/src/sgml/html/view-pg-seclabels.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-seclabels.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-seclabels.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.83. pg_seclabels
    51.83. pg_seclabels
    Prev UpChapter 51. System CatalogsHome Next

    51.83. pg_seclabels

    +51.83. pg_seclabels

    51.83. pg_seclabels
    Prev UpChapter 51. System CatalogsHome Next

    51.83. pg_seclabels

    The view pg_seclabels provides information about security labels. It as an easier-to-query version of the pg_seclabel catalog. @@ -57,4 +57,4 @@

    The security label applied to this object. -


    Prev Up Next
    51.82. pg_rules Home 51.84. pg_sequences
    \ No newline at end of file +


    Prev Up Next
    51.82. pg_rules Home 51.84. pg_sequences
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-sequences.html postgresql-13-13.12/doc/src/sgml/html/view-pg-sequences.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-sequences.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-sequences.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.84. pg_sequences
    51.84. pg_sequences
    Prev UpChapter 51. System CatalogsHome Next

    51.84. pg_sequences

    +51.84. pg_sequences

    51.84. pg_sequences
    Prev UpChapter 51. System CatalogsHome Next

    51.84. pg_sequences

    The view pg_sequences provides access to useful information about each sequence in the database.

    Table 51.85. pg_sequences Columns

    @@ -71,4 +71,4 @@ the current user does not have USAGE or SELECT privilege on the sequence, the value is null. -


    Prev Up Next
    51.83. pg_seclabels Home 51.85. pg_settings
    \ No newline at end of file +


    Prev Up Next
    51.83. pg_seclabels Home 51.85. pg_settings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-settings.html postgresql-13-13.12/doc/src/sgml/html/view-pg-settings.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-settings.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-settings.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.85. pg_settings
    51.85. pg_settings
    Prev UpChapter 51. System CatalogsHome Next

    51.85. pg_settings

    +51.85. pg_settings

    51.85. pg_settings
    Prev UpChapter 51. System CatalogsHome Next

    51.85. pg_settings

    The view pg_settings provides access to run-time parameters of the server. It is essentially an alternative interface to the SHOW @@ -184,4 +184,4 @@ transaction is committed, the effects will persist until the end of the session, unless overridden by another UPDATE or SET. -

    Prev Up Next
    51.84. pg_sequences Home 51.86. pg_shadow
    \ No newline at end of file +

    Prev Up Next
    51.84. pg_sequences Home 51.86. pg_shadow
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-shadow.html postgresql-13-13.12/doc/src/sgml/html/view-pg-shadow.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-shadow.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-shadow.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.86. pg_shadow
    51.86. pg_shadow
    Prev UpChapter 51. System CatalogsHome Next

    51.86. pg_shadow

    +51.86. pg_shadow

    51.86. pg_shadow
    Prev UpChapter 51. System CatalogsHome Next

    51.86. pg_shadow

    The view pg_shadow exists for backwards compatibility: it emulates a catalog that existed in PostgreSQL before version 8.1. @@ -68,4 +68,4 @@

    Session defaults for run-time configuration variables -


    Prev Up Next
    51.85. pg_settings Home 51.87. pg_shmem_allocations
    \ No newline at end of file +


    Prev Up Next
    51.85. pg_settings Home 51.87. pg_shmem_allocations
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-shmem-allocations.html postgresql-13-13.12/doc/src/sgml/html/view-pg-shmem-allocations.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-shmem-allocations.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-shmem-allocations.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.87. pg_shmem_allocations
    51.87. pg_shmem_allocations
    Prev UpChapter 51. System CatalogsHome Next

    51.87. pg_shmem_allocations

    +51.87. pg_shmem_allocations

    51.87. pg_shmem_allocations
    Prev UpChapter 51. System CatalogsHome Next

    51.87. pg_shmem_allocations

    The pg_shmem_allocations view shows allocations made from the server's main shared memory segment. This includes both memory allocated by postgres itself and memory @@ -48,4 +48,4 @@

    By default, the pg_shmem_allocations view can be read only by superusers. -

    Prev Up Next
    51.86. pg_shadow Home 51.88. pg_stats
    \ No newline at end of file +

    Prev Up Next
    51.86. pg_shadow Home 51.88. pg_stats
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-stats-ext.html postgresql-13-13.12/doc/src/sgml/html/view-pg-stats-ext.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-stats-ext.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-stats-ext.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.89. pg_stats_ext
    51.89. pg_stats_ext
    Prev UpChapter 51. System CatalogsHome Next

    51.89. pg_stats_ext

    +51.89. pg_stats_ext

    51.89. pg_stats_ext
    Prev UpChapter 51. System CatalogsHome Next

    51.89. pg_stats_ext

    The view pg_stats_ext provides access to the information stored in the pg_statistic_ext and pg_statistic_ext_data @@ -108,4 +108,4 @@ column-by-column basis using the ALTER TABLE SET STATISTICS command, or globally by setting the default_statistics_target run-time parameter. -

    Prev Up Next
    51.88. pg_stats Home 51.90. pg_tables
    \ No newline at end of file +

    Prev Up Next
    51.88. pg_stats Home 51.90. pg_tables
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-stats.html postgresql-13-13.12/doc/src/sgml/html/view-pg-stats.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-stats.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-stats.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.88. pg_stats
    51.88. pg_stats
    Prev UpChapter 51. System CatalogsHome Next

    51.88. pg_stats

    +51.88. pg_stats

    51.88. pg_stats
    Prev UpChapter 51. System CatalogsHome Next

    51.88. pg_stats

    The view pg_stats provides access to the information stored in the pg_statistic catalog. This view allows access only to rows of @@ -124,4 +124,4 @@ column-by-column basis using the ALTER TABLE SET STATISTICS command, or globally by setting the default_statistics_target run-time parameter. -

    Prev Up Next
    51.87. pg_shmem_allocations Home 51.89. pg_stats_ext
    \ No newline at end of file +

    Prev Up Next
    51.87. pg_shmem_allocations Home 51.89. pg_stats_ext
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-tables.html postgresql-13-13.12/doc/src/sgml/html/view-pg-tables.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-tables.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-tables.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.90. pg_tables
    51.90. pg_tables
    Prev UpChapter 51. System CatalogsHome Next

    51.90. pg_tables

    +51.90. pg_tables

    51.90. pg_tables
    Prev UpChapter 51. System CatalogsHome Next

    51.90. pg_tables

    The view pg_tables provides access to useful information about each table in the database.

    Table 51.91. pg_tables Columns

    @@ -55,4 +55,4 @@

    True if row security is enabled on the table -


    Prev Up Next
    51.89. pg_stats_ext Home 51.91. pg_timezone_abbrevs
    \ No newline at end of file +


    Prev Up Next
    51.89. pg_stats_ext Home 51.91. pg_timezone_abbrevs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-timezone-abbrevs.html postgresql-13-13.12/doc/src/sgml/html/view-pg-timezone-abbrevs.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-timezone-abbrevs.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-timezone-abbrevs.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.91. pg_timezone_abbrevs
    51.91. pg_timezone_abbrevs
    Prev UpChapter 51. System CatalogsHome Next

    51.91. pg_timezone_abbrevs

    +51.91. pg_timezone_abbrevs

    51.91. pg_timezone_abbrevs
    Prev UpChapter 51. System CatalogsHome Next

    51.91. pg_timezone_abbrevs

    The view pg_timezone_abbrevs provides a list of time zone abbreviations that are currently recognized by the datetime input routines. The contents of this view change when the @@ -29,4 +29,4 @@ there are some that have historically varied in value (see Section B.4 for more information). In such cases this view presents their current meaning. -

    Prev Up Next
    51.90. pg_tables Home 51.92. pg_timezone_names
    \ No newline at end of file +

    Prev Up Next
    51.90. pg_tables Home 51.92. pg_timezone_names
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-timezone-names.html postgresql-13-13.12/doc/src/sgml/html/view-pg-timezone-names.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-timezone-names.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-timezone-names.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.92. pg_timezone_names
    51.92. pg_timezone_names
    Prev UpChapter 51. System CatalogsHome Next

    51.92. pg_timezone_names

    +51.92. pg_timezone_names

    51.92. pg_timezone_names
    Prev UpChapter 51. System CatalogsHome Next

    51.92. pg_timezone_names

    The view pg_timezone_names provides a list of time zone names that are recognized by SET TIMEZONE, along with their associated abbreviations, UTC offsets, @@ -35,4 +35,4 @@

    True if currently observing daylight savings -


    Prev Up Next
    51.91. pg_timezone_abbrevs Home 51.93. pg_user
    \ No newline at end of file +


    Prev Up Next
    51.91. pg_timezone_abbrevs Home 51.93. pg_user
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-user-mappings.html postgresql-13-13.12/doc/src/sgml/html/view-pg-user-mappings.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-user-mappings.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-user-mappings.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.94. pg_user_mappings
    51.94. pg_user_mappings
    Prev UpChapter 51. System CatalogsHome Next

    51.94. pg_user_mappings

    +51.94. pg_user_mappings

    51.94. pg_user_mappings
    Prev UpChapter 51. System CatalogsHome Next

    51.94. pg_user_mappings

    The view pg_user_mappings provides access to information about user mappings. This is essentially a publicly readable view of @@ -57,4 +57,4 @@

  • current user is a superuser

    • -

    Prev Up Next
    51.93. pg_user Home 51.95. pg_views
    \ No newline at end of file +

    Prev Up Next
    51.93. pg_user Home 51.95. pg_views
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-user.html postgresql-13-13.12/doc/src/sgml/html/view-pg-user.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-user.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-user.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.93. pg_user
    51.93. pg_user
    Prev UpChapter 51. System CatalogsHome Next

    51.93. pg_user

    +51.93. pg_user

    51.93. pg_user
    Prev UpChapter 51. System CatalogsHome Next

    51.93. pg_user

    The view pg_user provides access to information about database users. This is simply a publicly readable view of @@ -57,4 +57,4 @@

    Session defaults for run-time configuration variables -


    Prev Up Next
    51.92. pg_timezone_names Home 51.94. pg_user_mappings
    \ No newline at end of file +


    Prev Up Next
    51.92. pg_timezone_names Home 51.94. pg_user_mappings
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/view-pg-views.html postgresql-13-13.12/doc/src/sgml/html/view-pg-views.html --- postgresql-13-13.11/doc/src/sgml/html/view-pg-views.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/view-pg-views.html 2023-08-07 20:32:31.000000000 +0000 @@ -1,5 +1,5 @@ -51.95. pg_views
    51.95. pg_views
    Prev UpChapter 51. System CatalogsHome Next

    51.95. pg_views

    +51.95. pg_views

    51.95. pg_views
    Prev UpChapter 51. System CatalogsHome Next

    51.95. pg_views

    The view pg_views provides access to useful information about each view in the database.

    Table 51.96. pg_views Columns

    @@ -30,4 +30,4 @@

    View definition (a reconstructed SELECT query) -


    Prev Up Next
    51.94. pg_user_mappings Home Chapter 52. Frontend/Backend Protocol
    \ No newline at end of file +


    Prev Up Next
    51.94. pg_user_mappings Home Chapter 52. Frontend/Backend Protocol
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/views-overview.html postgresql-13-13.12/doc/src/sgml/html/views-overview.html --- postgresql-13-13.11/doc/src/sgml/html/views-overview.html 2023-05-08 21:34:11.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/views-overview.html 2023-08-07 20:32:30.000000000 +0000 @@ -1,5 +1,5 @@ -51.64. System Views
    51.64. System Views
    Prev UpChapter 51. System CatalogsHome Next

    51.64. System Views

    +51.64. System Views

    51.64. System Views
    Prev UpChapter 51. System CatalogsHome Next

    51.64. System Views

    In addition to the system catalogs, PostgreSQL provides a number of built-in views. Some system views provide convenient access to some commonly used queries on the system catalogs. Other views @@ -18,4 +18,4 @@ the statistics collector; they are described in Table 27.2.

    Except where noted, all the views described here are read-only. -

    Table 51.65. System Views

    View NamePurpose
    pg_available_extensionsavailable extensions
    pg_available_extension_versionsavailable versions of extensions
    pg_configcompile-time configuration parameters
    pg_cursorsopen cursors
    pg_file_settingssummary of configuration file contents
    pg_groupgroups of database users
    pg_hba_file_rulessummary of client authentication configuration file contents
    pg_indexesindexes
    pg_lockslocks currently held or awaited
    pg_matviewsmaterialized views
    pg_policiespolicies
    pg_prepared_statementsprepared statements
    pg_prepared_xactsprepared transactions
    pg_publication_tablespublications and their associated tables
    pg_replication_origin_statusinformation about replication origins, including replication progress
    pg_replication_slotsreplication slot information
    pg_rolesdatabase roles
    pg_rulesrules
    pg_seclabelssecurity labels
    pg_sequencessequences
    pg_settingsparameter settings
    pg_shadowdatabase users
    pg_shmem_allocationsshared memory allocations
    pg_statsplanner statistics
    pg_stats_extextended planner statistics
    pg_tablestables
    pg_timezone_abbrevstime zone abbreviations
    pg_timezone_namestime zone names
    pg_userdatabase users
    pg_user_mappingsuser mappings
    pg_viewsviews

    Prev Up Next
    51.63. pg_user_mapping Home 51.65. pg_available_extensions
    \ No newline at end of file +

    Table 51.65. System Views

    View NamePurpose
    pg_available_extensionsavailable extensions
    pg_available_extension_versionsavailable versions of extensions
    pg_configcompile-time configuration parameters
    pg_cursorsopen cursors
    pg_file_settingssummary of configuration file contents
    pg_groupgroups of database users
    pg_hba_file_rulessummary of client authentication configuration file contents
    pg_indexesindexes
    pg_lockslocks currently held or awaited
    pg_matviewsmaterialized views
    pg_policiespolicies
    pg_prepared_statementsprepared statements
    pg_prepared_xactsprepared transactions
    pg_publication_tablespublications and their associated tables
    pg_replication_origin_statusinformation about replication origins, including replication progress
    pg_replication_slotsreplication slot information
    pg_rolesdatabase roles
    pg_rulesrules
    pg_seclabelssecurity labels
    pg_sequencessequences
    pg_settingsparameter settings
    pg_shadowdatabase users
    pg_shmem_allocationsshared memory allocations
    pg_statsplanner statistics
    pg_stats_extextended planner statistics
    pg_tablestables
    pg_timezone_abbrevstime zone abbreviations
    pg_timezone_namestime zone names
    pg_userdatabase users
    pg_user_mappingsuser mappings
    pg_viewsviews

    Prev Up Next
    51.63. pg_user_mapping Home 51.65. pg_available_extensions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal-async-commit.html postgresql-13-13.12/doc/src/sgml/html/wal-async-commit.html --- postgresql-13-13.11/doc/src/sgml/html/wal-async-commit.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal-async-commit.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -29.3. Asynchronous Commit
    29.3. Asynchronous Commit
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.3. Asynchronous Commit

    +29.3. Asynchronous Commit

    29.3. Asynchronous Commit
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.3. Asynchronous Commit

    Asynchronous commit is an option that allows transactions to complete more quickly, at the cost that the most recent transactions may be lost if the database should crash. In many applications this is an @@ -96,4 +96,4 @@ setting can be thought of as a way of increasing the time window in which transactions can join a group about to participate in a single flush, to amortize the cost of the flush among multiple transactions. -

    Prev Up Next
    29.2. Write-Ahead Logging (WAL) Home 29.4. WAL Configuration
    \ No newline at end of file +

    Prev Up Next
    29.2. Write-Ahead Logging (WAL) Home 29.4. WAL Configuration
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal-configuration.html postgresql-13-13.12/doc/src/sgml/html/wal-configuration.html --- postgresql-13-13.11/doc/src/sgml/html/wal-configuration.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal-configuration.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -29.4. WAL Configuration
    29.4. WAL Configuration
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.4. WAL Configuration

    +29.4. WAL Configuration

    29.4. WAL Configuration
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.4. WAL Configuration

    There are several WAL-related configuration parameters that affect database performance. This section explains their use. Consult Chapter 19 for general information about @@ -247,4 +247,4 @@ XLogInsertRecord and XLogFlush WAL call being logged to the server log. This option might be replaced by a more general mechanism in the future. -

    Prev Up Next
    29.3. Asynchronous Commit Home 29.5. WAL Internals
    \ No newline at end of file +

    Prev Up Next
    29.3. Asynchronous Commit Home 29.5. WAL Internals
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal-internals.html postgresql-13-13.12/doc/src/sgml/html/wal-internals.html --- postgresql-13-13.11/doc/src/sgml/html/wal-internals.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal-internals.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -29.5. WAL Internals
    29.5. WAL Internals
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.5. WAL Internals

    +29.5. WAL Internals

    29.5. WAL Internals
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.5. WAL Internals

    WAL is automatically enabled; no action is required from the administrator except ensuring that the disk-space requirements for the WAL logs are met, @@ -67,4 +67,4 @@ to read pg_control itself. So while it is theoretically a weak spot, pg_control does not seem to be a problem in practice. -

    Prev Up Next
    29.4. WAL Configuration Home Chapter 30. Logical Replication
    \ No newline at end of file +

    Prev Up Next
    29.4. WAL Configuration Home Chapter 30. Logical Replication
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal-intro.html postgresql-13-13.12/doc/src/sgml/html/wal-intro.html --- postgresql-13-13.11/doc/src/sgml/html/wal-intro.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal-intro.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -29.2. Write-Ahead Logging (WAL)
    29.2. Write-Ahead Logging (WAL)
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.2. Write-Ahead Logging (WAL)

    +29.2. Write-Ahead Logging (WAL)

    29.2. Write-Ahead Logging (WAL)
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.2. Write-Ahead Logging (WAL)

    Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about @@ -45,4 +45,4 @@ of the database state — if it is made over some period of time, then replaying the WAL log for that period will fix any internal inconsistencies. -

    Prev Up Next
    29.1. Reliability Home 29.3. Asynchronous Commit
    \ No newline at end of file +

    Prev Up Next
    29.1. Reliability Home 29.3. Asynchronous Commit
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal-reliability.html postgresql-13-13.12/doc/src/sgml/html/wal-reliability.html --- postgresql-13-13.11/doc/src/sgml/html/wal-reliability.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal-reliability.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -29.1. Reliability
    29.1. Reliability
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.1. Reliability

    +29.1. Reliability

    29.1. Reliability
    Prev UpChapter 29. Reliability and the Write-Ahead LogHome Next

    29.1. Reliability

    Reliability is an important property of any serious database system, and PostgreSQL does everything possible to guarantee reliable operation. One aspect of reliable operation is @@ -158,4 +158,4 @@ PostgreSQL does not protect against correctable memory errors and it is assumed you will operate using RAM that uses industry standard Error Correcting Codes (ECC) or better protection. -

    Prev Up Next
    Chapter 29. Reliability and the Write-Ahead Log Home 29.2. Write-Ahead Logging (WAL)
    \ No newline at end of file +

    Prev Up Next
    Chapter 29. Reliability and the Write-Ahead Log Home 29.2. Write-Ahead Logging (WAL)
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/wal.html postgresql-13-13.12/doc/src/sgml/html/wal.html --- postgresql-13-13.11/doc/src/sgml/html/wal.html 2023-05-08 21:33:56.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/wal.html 2023-08-07 20:32:15.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 29. Reliability and the Write-Ahead Log
    Chapter 29. Reliability and the Write-Ahead Log
    Prev UpPart III. Server AdministrationHome Next

    Chapter 29. Reliability and the Write-Ahead Log

    Table of Contents

    29.1. Reliability
    29.2. Write-Ahead Logging (WAL)
    29.3. Asynchronous Commit
    29.4. WAL Configuration
    29.5. WAL Internals

    +Chapter 29. Reliability and the Write-Ahead Log

    Chapter 29. Reliability and the Write-Ahead Log
    Prev UpPart III. Server AdministrationHome Next

    Chapter 29. Reliability and the Write-Ahead Log

    Table of Contents

    29.1. Reliability
    29.2. Write-Ahead Logging (WAL)
    29.3. Asynchronous Commit
    29.4. WAL Configuration
    29.5. WAL Internals

    This chapter explains how the Write-Ahead Log is used to obtain efficient, reliable operation. -

    Prev Up Next
    28.2. Disk Full Failure Home 29.1. Reliability
    \ No newline at end of file +

    Prev Up Next
    28.2. Disk Full Failure Home 29.1. Reliability
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/warm-standby-failover.html postgresql-13-13.12/doc/src/sgml/html/warm-standby-failover.html --- postgresql-13-13.11/doc/src/sgml/html/warm-standby-failover.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/warm-standby-failover.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -26.3. Failover
    26.3. Failover
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.3. Failover

    +26.3. Failover

    26.3. Failover
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.3. Failover

    If the primary server fails then the standby server should begin failover procedures.

    @@ -62,4 +62,4 @@ setting up the reporting servers that are only used to offload read-only queries from the primary, not for high availability purposes, you don't need to promote it. -

    Prev Up Next
    26.2. Log-Shipping Standby Servers Home 26.4. Alternative Method for Log Shipping
    \ No newline at end of file +

    Prev Up Next
    26.2. Log-Shipping Standby Servers Home 26.4. Alternative Method for Log Shipping
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/warm-standby.html postgresql-13-13.12/doc/src/sgml/html/warm-standby.html --- postgresql-13-13.11/doc/src/sgml/html/warm-standby.html 2023-05-08 21:33:55.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/warm-standby.html 2023-08-07 20:32:14.000000000 +0000 @@ -1,5 +1,5 @@ -26.2. Log-Shipping Standby Servers
    26.2. Log-Shipping Standby Servers
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.2. Log-Shipping Standby Servers

    26.2.1. Planning
    26.2.2. Standby Server Operation
    26.2.3. Preparing the Master for Standby Servers
    26.2.4. Setting Up a Standby Server
    26.2.5. Streaming Replication
    26.2.6. Replication Slots
    26.2.7. Cascading Replication
    26.2.8. Synchronous Replication
    26.2.9. Continuous Archiving in Standby

    +26.2. Log-Shipping Standby Servers

    26.2. Log-Shipping Standby Servers
    Prev UpChapter 26. High Availability, Load Balancing, and ReplicationHome Next

    26.2. Log-Shipping Standby Servers

    26.2.1. Planning
    26.2.2. Standby Server Operation
    26.2.3. Preparing the Master for Standby Servers
    26.2.4. Setting Up a Standby Server
    26.2.5. Streaming Replication
    26.2.6. Replication Slots
    26.2.7. Cascading Replication
    26.2.8. Synchronous Replication
    26.2.9. Continuous Archiving in Standby

    Continuous archiving can be used to create a high availability (HA) cluster configuration with one or more standby servers ready to take over operations if the @@ -657,4 +657,4 @@ are found in the archive, but not if streaming replication is enabled. When a server is not in recovery mode, there is no difference between on and always modes. -

    Prev Up Next
    26.1. Comparison of Different Solutions Home 26.3. Failover
    \ No newline at end of file +

    Prev Up Next
    26.1. Comparison of Different Solutions Home 26.3. Failover
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/when-can-parallel-query-be-used.html postgresql-13-13.12/doc/src/sgml/html/when-can-parallel-query-be-used.html --- postgresql-13-13.11/doc/src/sgml/html/when-can-parallel-query-be-used.html 2023-05-08 21:33:52.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/when-can-parallel-query-be-used.html 2023-08-07 20:32:12.000000000 +0000 @@ -1,5 +1,5 @@ -15.2. When Can Parallel Query Be Used?
    15.2. When Can Parallel Query Be Used?
    Prev UpChapter 15. Parallel QueryHome Next

    15.2. When Can Parallel Query Be Used?

    +15.2. When Can Parallel Query Be Used?

    15.2. When Can Parallel Query Be Used?
    Prev UpChapter 15. Parallel QueryHome Next

    15.2. When Can Parallel Query Be Used?

    There are several settings that can cause the query planner not to generate a parallel query plan under any circumstances. In order for any parallel query plans whatsoever to be generated, the following @@ -73,4 +73,4 @@ max_parallel_workers_per_gather to zero in sessions where it is likely, so as to avoid generating query plans that may be suboptimal when run serially. -

    Prev Up Next
    15.1. How Parallel Query Works Home 15.3. Parallel Plans
    \ No newline at end of file +

    Prev Up Next
    15.1. How Parallel Query Works Home 15.3. Parallel Plans
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xaggr.html postgresql-13-13.12/doc/src/sgml/html/xaggr.html --- postgresql-13-13.11/doc/src/sgml/html/xaggr.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xaggr.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.12. User-Defined Aggregates
    37.12. User-Defined Aggregates
    Prev UpChapter 37. Extending SQLHome Next

    37.12. User-Defined Aggregates

    37.12.1. Moving-Aggregate Mode
    37.12.2. Polymorphic and Variadic Aggregates
    37.12.3. Ordered-Set Aggregates
    37.12.4. Partial Aggregation
    37.12.5. Support Functions for Aggregates

    +37.12. User-Defined Aggregates

    37.12. User-Defined Aggregates
    Prev UpChapter 37. Extending SQLHome Next

    37.12. User-Defined Aggregates

    37.12.1. Moving-Aggregate Mode
    37.12.2. Polymorphic and Variadic Aggregates
    37.12.3. Ordered-Set Aggregates
    37.12.4. Partial Aggregation
    37.12.5. Support Functions for Aggregates

    Aggregate functions in PostgreSQL are defined in terms of state values and state transition functions. @@ -525,4 +525,4 @@ supposed to implement. Examples can be found in orderedsetaggs.c in the PostgreSQL source code. -

    Prev Up Next
    37.11. Function Optimization Information Home 37.13. User-Defined Types
    \ No newline at end of file +

    Prev Up Next
    37.11. Function Optimization Information Home 37.13. User-Defined Types
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-c.html postgresql-13-13.12/doc/src/sgml/html/xfunc-c.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-c.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-c.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.10. C-Language Functions
    37.10. C-Language Functions
    Prev UpChapter 37. Extending SQLHome Next
    Prev Up Next
    37.9. Internal Functions Home 37.11. Function Optimization Information
    \ No newline at end of file +

    Prev Up Next
    37.9. Internal Functions Home 37.11. Function Optimization Information
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-internal.html postgresql-13-13.12/doc/src/sgml/html/xfunc-internal.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-internal.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-internal.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.9. Internal Functions
    37.9. Internal Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.9. Internal Functions

    +37.9. Internal Functions

    37.9. Internal Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.9. Internal Functions

    Internal functions are functions written in C that have been statically linked into the PostgreSQL server. The “body” of the function definition @@ -28,4 +28,4 @@ Not all “predefined” functions are “internal” in the above sense. Some predefined functions are written in SQL. -

    Prev Up Next
    37.8. Procedural Language Functions Home 37.10. C-Language Functions
    \ No newline at end of file +

    Prev Up Next
    37.8. Procedural Language Functions Home 37.10. C-Language Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-optimization.html postgresql-13-13.12/doc/src/sgml/html/xfunc-optimization.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-optimization.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-optimization.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.11. Function Optimization Information
    37.11. Function Optimization Information
    Prev UpChapter 37. Extending SQLHome Next

    37.11. Function Optimization Information

    +37.11. Function Optimization Information

    37.11. Function Optimization Information
    Prev UpChapter 37. Extending SQLHome Next

    37.11. Function Optimization Information

    By default, a function is just a “black box” that the database system knows very little about the behavior of. However, that means that queries using the function may be executed much less @@ -91,4 +91,4 @@ the index to see if it really passes the WHERE condition or not. To create such conditions, the support function must implement the SupportRequestIndexCondition request type. -

    Prev Up Next
    37.10. C-Language Functions Home 37.12. User-Defined Aggregates
    \ No newline at end of file +

    Prev Up Next
    37.10. C-Language Functions Home 37.12. User-Defined Aggregates
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-overload.html postgresql-13-13.12/doc/src/sgml/html/xfunc-overload.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-overload.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-overload.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.6. Function Overloading
    37.6. Function Overloading
    Prev UpChapter 37. Extending SQLHome Next

    37.6. Function Overloading

    +37.6. Function Overloading

    37.6. Function Overloading
    Prev UpChapter 37. Extending SQLHome Next

    37.6. Function Overloading

    More than one function can be defined with the same SQL name, so long as the arguments they take are different. In other words, function names can be overloaded. Whether or not @@ -64,4 +64,4 @@ LANGUAGE C;

    The names of the C functions here reflect one of many possible conventions. -

    Prev Up Next
    37.5. Query Language (SQL) Functions Home 37.7. Function Volatility Categories
    \ No newline at end of file +

    Prev Up Next
    37.5. Query Language (SQL) Functions Home 37.7. Function Volatility Categories
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-pl.html postgresql-13-13.12/doc/src/sgml/html/xfunc-pl.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-pl.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-pl.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.8. Procedural Language Functions
    37.8. Procedural Language Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.8. Procedural Language Functions

    +37.8. Procedural Language Functions

    37.8. Procedural Language Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.8. Procedural Language Functions

    PostgreSQL allows user-defined functions to be written in other languages besides SQL and C. These other languages are generically called procedural @@ -9,4 +9,4 @@ by loadable modules. See Chapter 41 and following chapters for more information. -

    Prev Up Next
    37.7. Function Volatility Categories Home 37.9. Internal Functions
    \ No newline at end of file +

    Prev Up Next
    37.7. Function Volatility Categories Home 37.9. Internal Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-sql.html postgresql-13-13.12/doc/src/sgml/html/xfunc-sql.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-sql.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-sql.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.5. Query Language (SQL) Functions
    37.5. Query Language (SQL) Functions
    Prev UpChapter 37. Extending SQLHome Next
    Prev Up Next
    37.4. User-Defined Procedures Home 37.6. Function Overloading
    \ No newline at end of file +

    Prev Up Next
    37.4. User-Defined Procedures Home 37.6. Function Overloading
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc-volatility.html postgresql-13-13.12/doc/src/sgml/html/xfunc-volatility.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc-volatility.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc-volatility.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.7. Function Volatility Categories
    37.7. Function Volatility Categories
    Prev UpChapter 37. Extending SQLHome Next

    37.7. Function Volatility Categories

    +37.7. Function Volatility Categories

    37.7. Function Volatility Categories
    Prev UpChapter 37. Extending SQLHome Next

    37.7. Function Volatility Categories

    Every function has a volatility classification, with the possibilities being VOLATILE, STABLE, or IMMUTABLE. VOLATILE is the default if the @@ -104,4 +104,4 @@ If you do that, you will find that the STABLE or IMMUTABLE function does not notice the database changes applied by the called function, since they are hidden from its snapshot.) -

    Prev Up Next
    37.6. Function Overloading Home 37.8. Procedural Language Functions
    \ No newline at end of file +

    Prev Up Next
    37.6. Function Overloading Home 37.8. Procedural Language Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xfunc.html postgresql-13-13.12/doc/src/sgml/html/xfunc.html --- postgresql-13-13.11/doc/src/sgml/html/xfunc.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xfunc.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.3. User-Defined Functions
    37.3. User-Defined Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.3. User-Defined Functions

    +37.3. User-Defined Functions

    37.3. User-Defined Functions
    Prev UpChapter 37. Extending SQLHome Next

    37.3. User-Defined Functions

    PostgreSQL provides four kinds of functions: @@ -39,4 +39,4 @@ funcs.c in the src/tutorial directory in the PostgreSQL source distribution. -

    Prev Up Next
    37.2. The PostgreSQL Type System Home 37.4. User-Defined Procedures
    \ No newline at end of file +

    Prev Up Next
    37.2. The PostgreSQL Type System Home 37.4. User-Defined Procedures
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xindex.html postgresql-13-13.12/doc/src/sgml/html/xindex.html --- postgresql-13-13.11/doc/src/sgml/html/xindex.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xindex.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.16. Interfacing Extensions to Indexes
    37.16. Interfacing Extensions to Indexes
    Prev UpChapter 37. Extending SQLHome Next

    37.16. Interfacing Extensions to Indexes

    37.16.1. Index Methods and Operator Classes
    37.16.2. Index Method Strategies
    37.16.3. Index Method Support Routines
    37.16.4. An Example
    37.16.5. Operator Classes and Operator Families
    37.16.6. System Dependencies on Operator Classes
    37.16.7. Ordering Operators
    37.16.8. Special Features of Operator Classes

    +37.16. Interfacing Extensions to Indexes

    37.16. Interfacing Extensions to Indexes
    Prev UpChapter 37. Extending SQLHome Next

    37.16. Interfacing Extensions to Indexes

    37.16.1. Index Methods and Operator Classes
    37.16.2. Index Method Strategies
    37.16.3. Index Method Support Routines
    37.16.4. An Example
    37.16.5. Operator Classes and Operator Families
    37.16.6. System Dependencies on Operator Classes
    37.16.7. Ordering Operators
    37.16.8. Special Features of Operator Classes

    The procedures described thus far let you define new types, new functions, and new operators. However, we cannot yet define an index on a column of a new data type. To do this, we must define an @@ -768,4 +768,4 @@ type of the stored summary values, and operator classes' support procedures are responsible for interpreting the summary values correctly. -

    Prev Up Next
    37.15. Operator Optimization Information Home 37.17. Packaging Related Objects into an Extension
    \ No newline at end of file +

    Prev Up Next
    37.15. Operator Optimization Information Home 37.17. Packaging Related Objects into an Extension
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xml-limits-conformance.html postgresql-13-13.12/doc/src/sgml/html/xml-limits-conformance.html --- postgresql-13-13.11/doc/src/sgml/html/xml-limits-conformance.html 2023-05-08 21:34:15.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xml-limits-conformance.html 2023-08-07 20:32:36.000000000 +0000 @@ -1,5 +1,5 @@ -D.3. XML Limits and Conformance to SQL/XML
    D.3. XML Limits and Conformance to SQL/XML
    Prev UpAppendix D. SQL ConformanceHome Next

    D.3. XML Limits and Conformance to SQL/XML

    D.3.1. Queries Are Restricted to XPath 1.0
    D.3.2. Incidental Limits of the Implementation

    +D.3. XML Limits and Conformance to SQL/XML

    D.3. XML Limits and Conformance to SQL/XML
    Prev UpAppendix D. SQL ConformanceHome Next

    D.3. XML Limits and Conformance to SQL/XML

    D.3.1. Queries Are Restricted to XPath 1.0
    D.3.2. Incidental Limits of the Implementation

    Significant revisions to the XML-related specifications in ISO/IEC 9075-14 (SQL/XML) were introduced with SQL:2006. PostgreSQL's implementation of the XML data @@ -201,4 +201,4 @@ well-formed DOCUMENT is the only form of XML value that PostgreSQL can supply as an XPath context item. -

    Prev Up Next
    D.2. Unsupported Features Home Appendix E. Release Notes
    \ No newline at end of file +

    Prev Up Next
    D.2. Unsupported Features Home Appendix E. Release Notes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xml2.html postgresql-13-13.12/doc/src/sgml/html/xml2.html --- postgresql-13-13.11/doc/src/sgml/html/xml2.html 2023-05-08 21:34:17.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xml2.html 2023-08-07 20:32:37.000000000 +0000 @@ -1,5 +1,5 @@ -F.45. xml2
    F.45. xml2
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.45. xml2

    F.45.1. Deprecation Notice
    F.45.2. Description of Functions
    F.45.3. xpath_table
    F.45.4. XSLT Functions
    F.45.5. Author

    +F.45. xml2

    F.45. xml2
    Prev UpAppendix F. Additional Supplied ModulesHome Next

    F.45. xml2

    F.45.1. Deprecation Notice
    F.45.2. Description of Functions
    F.45.3. xpath_table
    F.45.4. XSLT Functions
    F.45.5. Author

    The xml2 module provides XPath querying and XSLT functionality.

    F.45.1. Deprecation Notice

    @@ -271,4 +271,4 @@

    Development of this module was sponsored by Torchbox Ltd. (www.torchbox.com). It has the same BSD license as PostgreSQL. -

    Prev Up Next
    F.44. uuid-ossp Home Appendix G. Additional Supplied Programs
    \ No newline at end of file +

    Prev Up Next
    F.44. uuid-ossp Home Appendix G. Additional Supplied Programs
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xoper-optimization.html postgresql-13-13.12/doc/src/sgml/html/xoper-optimization.html --- postgresql-13-13.11/doc/src/sgml/html/xoper-optimization.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xoper-optimization.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.15. Operator Optimization Information
    37.15. Operator Optimization Information
    Prev UpChapter 37. Extending SQLHome Next

    37.15. Operator Optimization Information

    37.15.1. COMMUTATOR
    37.15.2. NEGATOR
    37.15.3. RESTRICT
    37.15.4. JOIN
    37.15.5. HASHES
    37.15.6. MERGES

    +37.15. Operator Optimization Information

    37.15. Operator Optimization Information
    Prev UpChapter 37. Extending SQLHome Next

    37.15. Operator Optimization Information

    37.15.1. COMMUTATOR
    37.15.2. NEGATOR
    37.15.3. RESTRICT
    37.15.4. JOIN
    37.15.5. HASHES
    37.15.6. MERGES

    A PostgreSQL operator definition can include several optional clauses that tell the system useful things about how the operator behaves. These clauses should be provided whenever @@ -13,7 +13,7 @@

    Additional optimization clauses might be added in future versions of PostgreSQL. The ones described here are all - the ones that release 13.11 understands. + the ones that release 13.12 understands.

    It is also possible to attach a planner support function to the function that underlies an operator, providing another way of telling the system @@ -278,4 +278,4 @@ The function underlying a merge-joinable operator must be marked immutable or stable. If it is volatile, the system will never attempt to use the operator for a merge join. -

    Prev Up Next
    37.14. User-Defined Operators Home 37.16. Interfacing Extensions to Indexes
    \ No newline at end of file +

    Prev Up Next
    37.14. User-Defined Operators Home 37.16. Interfacing Extensions to Indexes
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xoper.html postgresql-13-13.12/doc/src/sgml/html/xoper.html --- postgresql-13-13.11/doc/src/sgml/html/xoper.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xoper.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.14. User-Defined Operators
    37.14. User-Defined Operators
    Prev UpChapter 37. Extending SQLHome Next

    37.14. User-Defined Operators

    +37.14. User-Defined Operators

    37.14. User-Defined Operators
    Prev UpChapter 37. Extending SQLHome Next

    37.14. User-Defined Operators

    Every operator is “syntactic sugar” for a call to an underlying function that does the real work; so you must first create the underlying function before you can create @@ -55,4 +55,4 @@ clause shown in the example is an optional hint to the query optimizer. Further details about commutator and other optimizer hints appear in the next section. -

    Prev Up Next
    37.13. User-Defined Types Home 37.15. Operator Optimization Information
    \ No newline at end of file +

    Prev Up Next
    37.13. User-Defined Types Home 37.15. Operator Optimization Information
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xplang-install.html postgresql-13-13.12/doc/src/sgml/html/xplang-install.html --- postgresql-13-13.11/doc/src/sgml/html/xplang-install.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xplang-install.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -41.1. Installing Procedural Languages
    41.1. Installing Procedural Languages
    Prev UpChapter 41. Procedural LanguagesHome Next

    41.1. Installing Procedural Languages

    +41.1. Installing Procedural Languages

    41.1. Installing Procedural Languages
    Prev UpChapter 41. Procedural LanguagesHome Next

    41.1. Installing Procedural Languages

    A procedural language must be “installed” into each database where it is to be used. But procedural languages installed in the database template1 are automatically available in all @@ -139,4 +139,4 @@ handlers are built and installed if Perl support is configured, and the PL/PythonU handler is installed if Python support is configured, but these languages are not installed by default. -

    Prev Up Next
    Chapter 41. Procedural Languages Home Chapter 42. PL/pgSQL — SQL Procedural Language
    \ No newline at end of file +

    Prev Up Next
    Chapter 41. Procedural Languages Home Chapter 42. PL/pgSQL — SQL Procedural Language
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xplang.html postgresql-13-13.12/doc/src/sgml/html/xplang.html --- postgresql-13-13.11/doc/src/sgml/html/xplang.html 2023-05-08 21:33:59.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xplang.html 2023-08-07 20:32:19.000000000 +0000 @@ -1,5 +1,5 @@ -Chapter 41. Procedural Languages
    Chapter 41. Procedural Languages
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 41. Procedural Languages

    Table of Contents

    41.1. Installing Procedural Languages

    +Chapter 41. Procedural Languages

    Chapter 41. Procedural Languages
    Prev UpPart V. Server ProgrammingHome Next

    Chapter 41. Procedural Languages

    Table of Contents

    41.1. Installing Procedural Languages

    PostgreSQL allows user-defined functions to be written in other languages besides SQL and C. These other languages are generically called procedural @@ -26,4 +26,4 @@ has information about finding them. In addition other languages can be defined by users; the basics of developing a new procedural language are covered in Chapter 55. -

    Prev Up Next
    40.7. Rules Versus Triggers Home 41.1. Installing Procedural Languages
    \ No newline at end of file +

    Prev Up Next
    40.7. Rules Versus Triggers Home 41.1. Installing Procedural Languages
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xproc.html postgresql-13-13.12/doc/src/sgml/html/xproc.html --- postgresql-13-13.11/doc/src/sgml/html/xproc.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xproc.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.4. User-Defined Procedures
    37.4. User-Defined Procedures
    Prev UpChapter 37. Extending SQLHome Next

    37.4. User-Defined Procedures

    +37.4. User-Defined Procedures

    37.4. User-Defined Procedures
    Prev UpChapter 37. Extending SQLHome Next

    37.4. User-Defined Procedures

    A procedure is a database object similar to a function. The key differences are: @@ -36,4 +36,4 @@ and DROP ROUTINE that can operate on functions and procedures without having to know which kind it is. Note, however, that there is no CREATE ROUTINE command. -

    Prev Up Next
    37.3. User-Defined Functions Home 37.5. Query Language (SQL) Functions
    \ No newline at end of file +

    Prev Up Next
    37.3. User-Defined Functions Home 37.5. Query Language (SQL) Functions
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/html/xtypes.html postgresql-13-13.12/doc/src/sgml/html/xtypes.html --- postgresql-13-13.11/doc/src/sgml/html/xtypes.html 2023-05-08 21:33:58.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/html/xtypes.html 2023-08-07 20:32:18.000000000 +0000 @@ -1,5 +1,5 @@ -37.13. User-Defined Types
    37.13. User-Defined Types
    Prev UpChapter 37. Extending SQLHome Next

    37.13. User-Defined Types

    37.13.1. TOAST Considerations

    +37.13. User-Defined Types

    37.13. User-Defined Types
    Prev UpChapter 37. Extending SQLHome Next

    37.13. User-Defined Types

    37.13.1. TOAST Considerations

    As described in Section 37.2, PostgreSQL can be extended to support new data types. This section describes how to define new base types, @@ -299,4 +299,4 @@ For examples of working with expanded values, see the standard array infrastructure, particularly src/backend/utils/adt/array_expanded.c. -

    Prev Up Next
    37.12. User-Defined Aggregates Home 37.14. User-Defined Operators
    \ No newline at end of file +

    Prev Up Next
    37.12. User-Defined Aggregates Home 37.14. User-Defined Operators
    \ No newline at end of file diff -Nru postgresql-13-13.11/doc/src/sgml/logical-replication.sgml postgresql-13-13.12/doc/src/sgml/logical-replication.sgml --- postgresql-13-13.11/doc/src/sgml/logical-replication.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/logical-replication.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -453,9 +453,13 @@ The apply process on the subscriber database always runs with - session_replication_role set - to replica, which produces the usual effects on triggers - and constraints. + session_replication_role + set to replica. This means that, by default, + triggers and rules will not fire on a subscriber. Users can optionally choose to + enable triggers and rules on a table using the + ALTER TABLE command + and the ENABLE TRIGGER and ENABLE RULE + clauses. diff -Nru postgresql-13-13.11/doc/src/sgml/man1/clusterdb.1 postgresql-13-13.12/doc/src/sgml/man1/clusterdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/clusterdb.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/clusterdb.1 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CLUSTERDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CLUSTERDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/createdb.1 postgresql-13-13.12/doc/src/sgml/man1/createdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/createdb.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/createdb.1 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATEDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATEDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/createuser.1 postgresql-13-13.12/doc/src/sgml/man1/createuser.1 --- postgresql-13-13.11/doc/src/sgml/man1/createuser.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/createuser.1 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATEUSER" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATEUSER" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/dropdb.1 postgresql-13-13.12/doc/src/sgml/man1/dropdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/dropdb.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/dropdb.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROPDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROPDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/dropuser.1 postgresql-13-13.12/doc/src/sgml/man1/dropuser.1 --- postgresql-13-13.11/doc/src/sgml/man1/dropuser.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/dropuser.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROPUSER" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROPUSER" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/ecpg.1 postgresql-13-13.12/doc/src/sgml/man1/ecpg.1 --- postgresql-13-13.11/doc/src/sgml/man1/ecpg.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/ecpg.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ECPG" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ECPG" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/initdb.1 postgresql-13-13.12/doc/src/sgml/man1/initdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/initdb.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/initdb.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "INITDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "INITDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/oid2name.1 postgresql-13-13.12/doc/src/sgml/man1/oid2name.1 --- postgresql-13-13.11/doc/src/sgml/man1/oid2name.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/oid2name.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "OID2NAME" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "OID2NAME" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_archivecleanup.1 postgresql-13-13.12/doc/src/sgml/man1/pg_archivecleanup.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_archivecleanup.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_archivecleanup.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_ARCHIVECLEANUP" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_ARCHIVECLEANUP" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_basebackup.1 postgresql-13-13.12/doc/src/sgml/man1/pg_basebackup.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_basebackup.1 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_basebackup.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_BASEBACKUP" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_BASEBACKUP" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_checksums.1 postgresql-13-13.12/doc/src/sgml/man1/pg_checksums.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_checksums.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_checksums.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_CHECKSUMS" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_CHECKSUMS" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_config.1 postgresql-13-13.12/doc/src/sgml/man1/pg_config.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_config.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_config.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_CONFIG" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_CONFIG" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_controldata.1 postgresql-13-13.12/doc/src/sgml/man1/pg_controldata.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_controldata.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_controldata.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_CONTROLDATA" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_CONTROLDATA" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_ctl.1 postgresql-13-13.12/doc/src/sgml/man1/pg_ctl.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_ctl.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_ctl.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_CTL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_CTL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_dump.1 postgresql-13-13.12/doc/src/sgml/man1/pg_dump.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_dump.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_dump.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_DUMP" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_DUMP" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_dumpall.1 postgresql-13-13.12/doc/src/sgml/man1/pg_dumpall.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_dumpall.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_dumpall.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_DUMPALL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_DUMPALL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_isready.1 postgresql-13-13.12/doc/src/sgml/man1/pg_isready.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_isready.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_isready.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_ISREADY" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_ISREADY" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_receivewal.1 postgresql-13-13.12/doc/src/sgml/man1/pg_receivewal.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_receivewal.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_receivewal.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_RECEIVEWAL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_RECEIVEWAL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_recvlogical.1 postgresql-13-13.12/doc/src/sgml/man1/pg_recvlogical.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_recvlogical.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_recvlogical.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_RECVLOGICAL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_RECVLOGICAL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_resetwal.1 postgresql-13-13.12/doc/src/sgml/man1/pg_resetwal.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_resetwal.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_resetwal.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_RESETWAL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_RESETWAL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_restore.1 postgresql-13-13.12/doc/src/sgml/man1/pg_restore.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_restore.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_restore.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_RESTORE" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_RESTORE" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_rewind.1 postgresql-13-13.12/doc/src/sgml/man1/pg_rewind.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_rewind.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_rewind.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_REWIND" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_REWIND" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_standby.1 postgresql-13-13.12/doc/src/sgml/man1/pg_standby.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_standby.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_standby.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_STANDBY" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_STANDBY" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_test_fsync.1 postgresql-13-13.12/doc/src/sgml/man1/pg_test_fsync.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_test_fsync.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_test_fsync.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_TEST_FSYNC" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_TEST_FSYNC" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_test_timing.1 postgresql-13-13.12/doc/src/sgml/man1/pg_test_timing.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_test_timing.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_test_timing.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_TEST_TIMING" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_TEST_TIMING" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_upgrade.1 postgresql-13-13.12/doc/src/sgml/man1/pg_upgrade.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_upgrade.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_upgrade.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_UPGRADE" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_UPGRADE" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_verifybackup.1 postgresql-13-13.12/doc/src/sgml/man1/pg_verifybackup.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_verifybackup.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_verifybackup.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_VERIFYBACKUP" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_VERIFYBACKUP" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pg_waldump.1 postgresql-13-13.12/doc/src/sgml/man1/pg_waldump.1 --- postgresql-13-13.11/doc/src/sgml/man1/pg_waldump.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pg_waldump.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PG_WALDUMP" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PG_WALDUMP" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/pgbench.1 postgresql-13-13.12/doc/src/sgml/man1/pgbench.1 --- postgresql-13-13.11/doc/src/sgml/man1/pgbench.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/pgbench.1 2023-08-07 20:32:47.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PGBENCH" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PGBENCH" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/postgres.1 postgresql-13-13.12/doc/src/sgml/man1/postgres.1 --- postgresql-13-13.11/doc/src/sgml/man1/postgres.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/postgres.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "POSTGRES" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "POSTGRES" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/postmaster.1 postgresql-13-13.12/doc/src/sgml/man1/postmaster.1 --- postgresql-13-13.11/doc/src/sgml/man1/postmaster.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/postmaster.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "POSTMASTER" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "POSTMASTER" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/psql.1 postgresql-13-13.12/doc/src/sgml/man1/psql.1 --- postgresql-13-13.11/doc/src/sgml/man1/psql.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/psql.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PSQL" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PSQL" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -655,7 +655,7 @@ .\} .nf $ \fBpsql testdb\fR -psql (13\&.11) +psql (13\&.12) Type "help" for help\&. testdb=> diff -Nru postgresql-13-13.11/doc/src/sgml/man1/reindexdb.1 postgresql-13-13.12/doc/src/sgml/man1/reindexdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/reindexdb.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/reindexdb.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "REINDEXDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "REINDEXDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/vacuumdb.1 postgresql-13-13.12/doc/src/sgml/man1/vacuumdb.1 --- postgresql-13-13.11/doc/src/sgml/man1/vacuumdb.1 2023-05-08 21:34:27.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/vacuumdb.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "VACUUMDB" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "VACUUMDB" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man1/vacuumlo.1 postgresql-13-13.12/doc/src/sgml/man1/vacuumlo.1 --- postgresql-13-13.11/doc/src/sgml/man1/vacuumlo.1 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man1/vacuumlo.1 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "VACUUMLO" "1" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "VACUUMLO" "1" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_commit.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_commit.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_commit.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_commit.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_COMMIT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_COMMIT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_connect.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_connect.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_connect.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_connect.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CONNECT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CONNECT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_copytuple.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_copytuple.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_copytuple.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_copytuple.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_COPYTUPLE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_COPYTUPLE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_close.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_close.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_close.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_close.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_CLOSE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_CLOSE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_fetch.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_fetch.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_fetch.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_fetch.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_find.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_find.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_find.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_find.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_FIND" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_FIND" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_move.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_move.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_move.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_move.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_OPEN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open_with_args.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open_with_args.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open_with_args.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open_with_args.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN_WITH_ARGS" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_OPEN_WITH_ARGS" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_CURSOR_OPEN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_exec.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_exec.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_exec.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_exec.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXEC" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXEC" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_execp.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_execp.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_execp.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_execp.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXECP" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXECP" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_execute.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_execute.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_execute.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_execute.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXECUTE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXECUTE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_plan.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_plan.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_plan.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_plan.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXECUTE_PLAN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXECUTE_PLAN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXECUTE_PLAN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXECUTE_PLAN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_with_args.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_with_args.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_execute_with_args.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_execute_with_args.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_EXECUTE_WITH_ARGS" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_EXECUTE_WITH_ARGS" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_finish.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_finish.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_finish.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_finish.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FINISH" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FINISH" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_fname.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_fname.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_fname.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_fname.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FNAME" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FNAME" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_fnumber.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_fnumber.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_fnumber.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_fnumber.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FNUMBER" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FNUMBER" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_freeplan.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_freeplan.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_freeplan.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_freeplan.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FREEPLAN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FREEPLAN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_freetuple.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_freetuple.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_freetuple.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_freetuple.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FREETUPLE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FREETUPLE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_freetuptable.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_freetuptable.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_freetuptable.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_freetuptable.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_FREETUPTABLE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_FREETUPTABLE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getargcount.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getargcount.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getargcount.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getargcount.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETARGCOUNT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETARGCOUNT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getargtypeid.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getargtypeid.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getargtypeid.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getargtypeid.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETARGTYPEID" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETARGTYPEID" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getbinval.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getbinval.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getbinval.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getbinval.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETBINVAL" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETBINVAL" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getnspname.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getnspname.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getnspname.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getnspname.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETNSPNAME" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETNSPNAME" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getrelname.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getrelname.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getrelname.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getrelname.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETRELNAME" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETRELNAME" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_gettype.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_gettype.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_gettype.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_gettype.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETTYPE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETTYPE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_gettypeid.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_gettypeid.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_gettypeid.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_gettypeid.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETTYPEID" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETTYPEID" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_getvalue.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_getvalue.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_getvalue.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_getvalue.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_GETVALUE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_GETVALUE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_is_cursor_plan.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_is_cursor_plan.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_is_cursor_plan.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_is_cursor_plan.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_IS_CURSOR_PLAN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_IS_CURSOR_PLAN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_keepplan.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_keepplan.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_keepplan.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_keepplan.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_KEEPPLAN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_KEEPPLAN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_modifytuple.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_modifytuple.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_modifytuple.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_modifytuple.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_MODIFYTUPLE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_MODIFYTUPLE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_palloc.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_palloc.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_palloc.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_palloc.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_PALLOC" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_PALLOC" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_pfree.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_pfree.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_pfree.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_pfree.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_PFREE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_PFREE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_PREPARE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_PREPARE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare_cursor.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare_cursor.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare_cursor.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare_cursor.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_PREPARE_CURSOR" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_PREPARE_CURSOR" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare_params.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare_params.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_prepare_params.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_prepare_params.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_PREPARE_PARAMS" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_PREPARE_PARAMS" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_register_relation.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_register_relation.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_register_relation.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_register_relation.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_REGISTER_RELATION" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_REGISTER_RELATION" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_register_trigger_data.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_register_trigger_data.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_register_trigger_data.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_register_trigger_data.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_REGISTER_TRIGGER_DATA" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_REGISTER_TRIGGER_DATA" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_repalloc.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_repalloc.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_repalloc.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_repalloc.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_REPALLOC" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_REPALLOC" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_result_code_string.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_result_code_string.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_result_code_string.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_result_code_string.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_RESULT_CODE_STRING" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_RESULT_CODE_STRING" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_returntuple.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_returntuple.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_returntuple.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_returntuple.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_RETURNTUPLE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_RETURNTUPLE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_rollback.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_rollback.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_rollback.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_rollback.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_ROLLBACK" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_ROLLBACK" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_saveplan.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_saveplan.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_saveplan.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_saveplan.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_SAVEPLAN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_SAVEPLAN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_SCROLL_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_SCROLL_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_scroll_cursor_move.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_scroll_cursor_move.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_scroll_cursor_move.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_scroll_cursor_move.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_SCROLL_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_SCROLL_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_start_transaction.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_start_transaction.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_start_transaction.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_start_transaction.3 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_START_TRANSACTION" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_START_TRANSACTION" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/SPI_unregister_relation.3 postgresql-13-13.12/doc/src/sgml/man3/SPI_unregister_relation.3 --- postgresql-13-13.11/doc/src/sgml/man3/SPI_unregister_relation.3 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/SPI_unregister_relation.3 2023-08-07 20:32:43.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SPI_UNREGISTER_RELATION" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SPI_UNREGISTER_RELATION" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink.3 postgresql-13-13.12/doc/src/sgml/man3/dblink.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_delete.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_delete.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_delete.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_delete.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_DELETE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_BUILD_SQL_DELETE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_insert.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_insert.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_insert.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_insert.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_INSERT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_BUILD_SQL_INSERT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_update.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_update.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_build_sql_update.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_build_sql_update.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_UPDATE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_BUILD_SQL_UPDATE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_cancel_query.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_cancel_query.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_cancel_query.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_cancel_query.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_CANCEL_QUERY" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_CANCEL_QUERY" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_close.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_close.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_close.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_close.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_CLOSE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_CLOSE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_connect.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_connect.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_connect.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_connect.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_CONNECT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_CONNECT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_connect_u.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_connect_u.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_connect_u.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_connect_u.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_CONNECT_U" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_CONNECT_U" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_disconnect.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_disconnect.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_disconnect.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_disconnect.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_DISCONNECT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_DISCONNECT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_error_message.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_error_message.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_error_message.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_error_message.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_ERROR_MESSAGE" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_ERROR_MESSAGE" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_exec.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_exec.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_exec.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_exec.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_EXEC" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_EXEC" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_fetch.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_fetch.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_fetch.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_fetch.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_FETCH" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_FETCH" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_get_connections.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_get_connections.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_get_connections.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_get_connections.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_GET_CONNECTIONS" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_GET_CONNECTIONS" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_get_notify.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_get_notify.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_get_notify.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_get_notify.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_GET_NOTIFY" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_GET_NOTIFY" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_get_pkey.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_get_pkey.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_get_pkey.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_get_pkey.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_GET_PKEY" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_GET_PKEY" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_get_result.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_get_result.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_get_result.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_get_result.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_GET_RESULT" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_GET_RESULT" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_is_busy.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_is_busy.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_is_busy.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_is_busy.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_IS_BUSY" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_IS_BUSY" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_open.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_open.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_open.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_open.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_OPEN" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_OPEN" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man3/dblink_send_query.3 postgresql-13-13.12/doc/src/sgml/man3/dblink_send_query.3 --- postgresql-13-13.11/doc/src/sgml/man3/dblink_send_query.3 2023-05-08 21:34:28.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man3/dblink_send_query.3 2023-08-07 20:32:48.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DBLINK_SEND_QUERY" "3" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DBLINK_SEND_QUERY" "3" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ABORT.7 postgresql-13-13.12/doc/src/sgml/man7/ABORT.7 --- postgresql-13-13.11/doc/src/sgml/man7/ABORT.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ABORT.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ABORT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ABORT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_AGGREGATE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_AGGREGATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_AGGREGATE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_AGGREGATE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER AGGREGATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER AGGREGATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_COLLATION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_COLLATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_COLLATION.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_COLLATION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER COLLATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER COLLATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_CONVERSION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_CONVERSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_CONVERSION.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_CONVERSION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER CONVERSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER CONVERSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_DATABASE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_DATABASE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_DATABASE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_DATABASE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER DATABASE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER DATABASE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER DEFAULT PRIVILEGES" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER DEFAULT PRIVILEGES" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_DOMAIN.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_DOMAIN.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_DOMAIN.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_DOMAIN.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER DOMAIN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER DOMAIN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER EVENT TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER EVENT TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_EXTENSION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_EXTENSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_EXTENSION.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_EXTENSION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER EXTENSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER EXTENSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER FOREIGN TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER FOREIGN TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -354,7 +354,7 @@ .RS 4 .\} .nf -ALTER FOREIGN TABLE myschema\&.distributors OPTIONS (ADD opt1 \*(Aqvalue\*(Aq, SET opt2 \*(Aqvalue2\*(Aq, DROP opt3 \*(Aqvalue3\*(Aq); +ALTER FOREIGN TABLE myschema\&.distributors OPTIONS (ADD opt1 \*(Aqvalue\*(Aq, SET opt2 \*(Aqvalue2\*(Aq, DROP opt3); .fi .if n \{\ .RE diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_FUNCTION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_FUNCTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_FUNCTION.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_FUNCTION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER FUNCTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER FUNCTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_GROUP.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_GROUP.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_GROUP.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_GROUP.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER GROUP" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER GROUP" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_INDEX.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_INDEX.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_INDEX.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_INDEX.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER INDEX" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER INDEX" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_LANGUAGE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_LANGUAGE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_LANGUAGE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_LANGUAGE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER LANGUAGE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER LANGUAGE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER LARGE OBJECT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER LARGE OBJECT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER OPERATOR" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER OPERATOR" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER OPERATOR CLASS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER OPERATOR CLASS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_POLICY.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_POLICY.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_POLICY.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_POLICY.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER POLICY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER POLICY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_PROCEDURE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_PROCEDURE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_PROCEDURE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_PROCEDURE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER PROCEDURE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER PROCEDURE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_PUBLICATION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_PUBLICATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_PUBLICATION.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_PUBLICATION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER PUBLICATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER PUBLICATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_ROLE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_ROLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_ROLE.7 2023-05-08 21:34:23.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_ROLE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER ROLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER ROLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_ROUTINE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_ROUTINE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_ROUTINE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_ROUTINE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER ROUTINE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER ROUTINE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_RULE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_RULE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_RULE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_RULE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER RULE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER RULE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_SCHEMA.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_SCHEMA.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_SCHEMA.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_SCHEMA.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER SCHEMA" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER SCHEMA" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_SEQUENCE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_SEQUENCE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_SEQUENCE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_SEQUENCE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER SEQUENCE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER SEQUENCE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_SERVER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_SERVER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_SERVER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_SERVER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER SERVER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER SERVER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_STATISTICS.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_STATISTICS.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_STATISTICS.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_STATISTICS.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER STATISTICS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER STATISTICS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER SUBSCRIPTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER SUBSCRIPTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_SYSTEM.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_SYSTEM.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_SYSTEM.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_SYSTEM.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER SYSTEM" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER SYSTEM" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TABLE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TABLE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TABLESPACE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TABLESPACE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TABLESPACE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TABLESPACE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TABLESPACE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TABLESPACE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TRIGGER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TRIGGER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_TYPE.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_TYPE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_TYPE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_TYPE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER TYPE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER TYPE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_USER.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_USER.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_USER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_USER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER USER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER USER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_USER_MAPPING.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_USER_MAPPING.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_USER_MAPPING.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_USER_MAPPING.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER USER MAPPING" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER USER MAPPING" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ALTER_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/ALTER_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/ALTER_VIEW.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ALTER_VIEW.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ALTER VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ALTER VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ANALYZE.7 postgresql-13-13.12/doc/src/sgml/man7/ANALYZE.7 --- postgresql-13-13.11/doc/src/sgml/man7/ANALYZE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ANALYZE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ANALYZE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ANALYZE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/BEGIN.7 postgresql-13-13.12/doc/src/sgml/man7/BEGIN.7 --- postgresql-13-13.11/doc/src/sgml/man7/BEGIN.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/BEGIN.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "BEGIN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "BEGIN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CALL.7 postgresql-13-13.12/doc/src/sgml/man7/CALL.7 --- postgresql-13-13.11/doc/src/sgml/man7/CALL.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CALL.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CALL" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CALL" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CHECKPOINT.7 postgresql-13-13.12/doc/src/sgml/man7/CHECKPOINT.7 --- postgresql-13-13.11/doc/src/sgml/man7/CHECKPOINT.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CHECKPOINT.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CHECKPOINT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CHECKPOINT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CLOSE.7 postgresql-13-13.12/doc/src/sgml/man7/CLOSE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CLOSE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CLOSE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CLOSE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CLOSE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CLUSTER.7 postgresql-13-13.12/doc/src/sgml/man7/CLUSTER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CLUSTER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CLUSTER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CLUSTER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CLUSTER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/COMMENT.7 postgresql-13-13.12/doc/src/sgml/man7/COMMENT.7 --- postgresql-13-13.11/doc/src/sgml/man7/COMMENT.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/COMMENT.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "COMMENT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "COMMENT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/COMMIT.7 postgresql-13-13.12/doc/src/sgml/man7/COMMIT.7 --- postgresql-13-13.11/doc/src/sgml/man7/COMMIT.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/COMMIT.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "COMMIT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "COMMIT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/COMMIT_PREPARED.7 postgresql-13-13.12/doc/src/sgml/man7/COMMIT_PREPARED.7 --- postgresql-13-13.11/doc/src/sgml/man7/COMMIT_PREPARED.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/COMMIT_PREPARED.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "COMMIT PREPARED" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "COMMIT PREPARED" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/COPY.7 postgresql-13-13.12/doc/src/sgml/man7/COPY.7 --- postgresql-13-13.11/doc/src/sgml/man7/COPY.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/COPY.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "COPY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "COPY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE ACCESS METHOD" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE ACCESS METHOD" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_AGGREGATE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_AGGREGATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_AGGREGATE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_AGGREGATE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE AGGREGATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE AGGREGATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_CAST.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_CAST.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_CAST.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_CAST.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE CAST" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE CAST" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_COLLATION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_COLLATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_COLLATION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_COLLATION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE COLLATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE COLLATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_CONVERSION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_CONVERSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_CONVERSION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_CONVERSION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE CONVERSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE CONVERSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_DATABASE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_DATABASE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_DATABASE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_DATABASE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE DATABASE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE DATABASE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_DOMAIN.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_DOMAIN.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_DOMAIN.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_DOMAIN.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE DOMAIN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE DOMAIN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE EVENT TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE EVENT TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_EXTENSION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_EXTENSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_EXTENSION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_EXTENSION.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE EXTENSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE EXTENSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 2023-08-07 20:32:44.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE FOREIGN TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE FOREIGN TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_FUNCTION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_FUNCTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_FUNCTION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_FUNCTION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE FUNCTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE FUNCTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_GROUP.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_GROUP.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_GROUP.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_GROUP.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE GROUP" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE GROUP" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_INDEX.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_INDEX.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_INDEX.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_INDEX.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE INDEX" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE INDEX" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_LANGUAGE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_LANGUAGE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_LANGUAGE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_LANGUAGE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE LANGUAGE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE LANGUAGE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE OPERATOR" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE OPERATOR" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE OPERATOR CLASS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE OPERATOR CLASS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_POLICY.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_POLICY.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_POLICY.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_POLICY.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE POLICY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE POLICY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_PROCEDURE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_PROCEDURE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_PROCEDURE.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_PROCEDURE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE PROCEDURE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE PROCEDURE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_PUBLICATION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_PUBLICATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_PUBLICATION.7 2023-05-08 21:34:24.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_PUBLICATION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE PUBLICATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE PUBLICATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_ROLE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_ROLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_ROLE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_ROLE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE ROLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE ROLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_RULE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_RULE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_RULE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_RULE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE RULE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE RULE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_SCHEMA.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_SCHEMA.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_SCHEMA.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_SCHEMA.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE SCHEMA" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE SCHEMA" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_SEQUENCE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_SEQUENCE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_SEQUENCE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_SEQUENCE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE SEQUENCE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE SEQUENCE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_SERVER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_SERVER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_SERVER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_SERVER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE SERVER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE SERVER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_STATISTICS.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_STATISTICS.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_STATISTICS.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_STATISTICS.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE STATISTICS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE STATISTICS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -82,6 +82,9 @@ .SH "NOTES" .PP You must be the owner of a table to create a statistics object reading it\&. Once created, however, the ownership of the statistics object is independent of the underlying table(s)\&. +.PP +Extended statistics are not currently used by the planner for selectivity estimations made for table joins\&. This limitation will likely be removed in a future version of +PostgreSQL\&. .SH "EXAMPLES" .PP Create table diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE SUBSCRIPTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE SUBSCRIPTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLESPACE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLESPACE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLESPACE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLESPACE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TABLESPACE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TABLESPACE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLE_AS.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLE_AS.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TABLE_AS.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TABLE_AS.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TABLE AS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TABLE AS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TRANSFORM.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TRANSFORM.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TRANSFORM.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TRANSFORM.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TRANSFORM" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TRANSFORM" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TRIGGER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TRIGGER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_TYPE.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_TYPE.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_TYPE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_TYPE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE TYPE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE TYPE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_USER.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_USER.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_USER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_USER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE USER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE USER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_USER_MAPPING.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_USER_MAPPING.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_USER_MAPPING.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_USER_MAPPING.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE USER MAPPING" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE USER MAPPING" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/CREATE_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/CREATE_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/CREATE_VIEW.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/CREATE_VIEW.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "CREATE VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "CREATE VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DEALLOCATE.7 postgresql-13-13.12/doc/src/sgml/man7/DEALLOCATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DEALLOCATE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DEALLOCATE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DEALLOCATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DEALLOCATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DECLARE.7 postgresql-13-13.12/doc/src/sgml/man7/DECLARE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DECLARE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DECLARE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DECLARE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DECLARE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DELETE.7 postgresql-13-13.12/doc/src/sgml/man7/DELETE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DELETE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DELETE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DELETE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DELETE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DISCARD.7 postgresql-13-13.12/doc/src/sgml/man7/DISCARD.7 --- postgresql-13-13.11/doc/src/sgml/man7/DISCARD.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DISCARD.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DISCARD" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DISCARD" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DO.7 postgresql-13-13.12/doc/src/sgml/man7/DO.7 --- postgresql-13-13.11/doc/src/sgml/man7/DO.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DO.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DO" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DO" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP ACCESS METHOD" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP ACCESS METHOD" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_AGGREGATE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_AGGREGATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_AGGREGATE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_AGGREGATE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP AGGREGATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP AGGREGATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_CAST.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_CAST.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_CAST.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_CAST.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP CAST" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP CAST" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_COLLATION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_COLLATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_COLLATION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_COLLATION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP COLLATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP COLLATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_CONVERSION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_CONVERSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_CONVERSION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_CONVERSION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP CONVERSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP CONVERSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_DATABASE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_DATABASE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_DATABASE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_DATABASE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP DATABASE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP DATABASE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_DOMAIN.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_DOMAIN.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_DOMAIN.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_DOMAIN.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP DOMAIN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP DOMAIN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP EVENT TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP EVENT TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_EXTENSION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_EXTENSION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_EXTENSION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_EXTENSION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP EXTENSION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP EXTENSION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP FOREIGN TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP FOREIGN TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_FUNCTION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_FUNCTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_FUNCTION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_FUNCTION.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP FUNCTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP FUNCTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_GROUP.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_GROUP.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_GROUP.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_GROUP.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP GROUP" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP GROUP" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_INDEX.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_INDEX.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_INDEX.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_INDEX.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP INDEX" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP INDEX" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_LANGUAGE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_LANGUAGE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_LANGUAGE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_LANGUAGE.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP LANGUAGE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP LANGUAGE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 2023-08-07 20:32:45.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP OPERATOR" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP OPERATOR" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP OPERATOR CLASS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP OPERATOR CLASS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_OWNED.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_OWNED.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_OWNED.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_OWNED.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP OWNED" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP OWNED" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_POLICY.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_POLICY.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_POLICY.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_POLICY.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP POLICY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP POLICY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_PROCEDURE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_PROCEDURE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_PROCEDURE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_PROCEDURE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP PROCEDURE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP PROCEDURE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_PUBLICATION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_PUBLICATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_PUBLICATION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_PUBLICATION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP PUBLICATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP PUBLICATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_ROLE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_ROLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_ROLE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_ROLE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP ROLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP ROLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_ROUTINE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_ROUTINE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_ROUTINE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_ROUTINE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP ROUTINE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP ROUTINE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_RULE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_RULE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_RULE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_RULE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP RULE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP RULE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_SCHEMA.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_SCHEMA.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_SCHEMA.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_SCHEMA.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP SCHEMA" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP SCHEMA" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_SEQUENCE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_SEQUENCE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_SEQUENCE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_SEQUENCE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP SEQUENCE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP SEQUENCE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_SERVER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_SERVER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_SERVER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_SERVER.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP SERVER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP SERVER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_STATISTICS.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_STATISTICS.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_STATISTICS.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_STATISTICS.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP STATISTICS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP STATISTICS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP SUBSCRIPTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP SUBSCRIPTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -64,7 +64,8 @@ \fBDROP SUBSCRIPTION\fR will connect to the remote host and try to drop the replication slot as part of its operation\&. This is necessary so that the resources allocated for the subscription on the remote host are released\&. If this fails, either because the remote host is not reachable or because the remote replication slot cannot be dropped or does not exist or never existed, the \fBDROP SUBSCRIPTION\fR -command will fail\&. To proceed in this situation, disassociate the subscription from the replication slot by executing +command will fail\&. To proceed in this situation, first disable the subscription by executing +ALTER SUBSCRIPTION \&.\&.\&. DISABLE, and then disassociate it from the replication slot by executing ALTER SUBSCRIPTION \&.\&.\&. SET (slot_name = NONE)\&. After that, \fBDROP SUBSCRIPTION\fR will no longer attempt any actions on a remote host\&. Note that if the remote replication slot still exists, it should then be dropped manually; otherwise it will continue to reserve WAL and might eventually cause the disk to fill up\&. See also diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TABLE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TABLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TABLE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TABLE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TABLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TABLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TABLESPACE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TABLESPACE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TABLESPACE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TABLESPACE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TABLESPACE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TABLESPACE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TRANSFORM.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TRANSFORM.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TRANSFORM.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TRANSFORM.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TRANSFORM" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TRANSFORM" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TRIGGER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TRIGGER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TRIGGER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TRIGGER.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TRIGGER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TRIGGER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_TYPE.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_TYPE.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_TYPE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_TYPE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP TYPE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP TYPE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_USER.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_USER.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_USER.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_USER.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP USER" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP USER" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_USER_MAPPING.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_USER_MAPPING.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_USER_MAPPING.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_USER_MAPPING.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP USER MAPPING" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP USER MAPPING" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/DROP_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/DROP_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/DROP_VIEW.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/DROP_VIEW.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "DROP VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "DROP VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/END.7 postgresql-13-13.12/doc/src/sgml/man7/END.7 --- postgresql-13-13.11/doc/src/sgml/man7/END.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/END.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "END" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "END" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/EXECUTE.7 postgresql-13-13.12/doc/src/sgml/man7/EXECUTE.7 --- postgresql-13-13.11/doc/src/sgml/man7/EXECUTE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/EXECUTE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "EXECUTE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "EXECUTE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/EXPLAIN.7 postgresql-13-13.12/doc/src/sgml/man7/EXPLAIN.7 --- postgresql-13-13.11/doc/src/sgml/man7/EXPLAIN.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/EXPLAIN.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "EXPLAIN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "EXPLAIN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/FETCH.7 postgresql-13-13.12/doc/src/sgml/man7/FETCH.7 --- postgresql-13-13.11/doc/src/sgml/man7/FETCH.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/FETCH.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "FETCH" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "FETCH" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/GRANT.7 postgresql-13-13.12/doc/src/sgml/man7/GRANT.7 --- postgresql-13-13.11/doc/src/sgml/man7/GRANT.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/GRANT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "GRANT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "GRANT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 postgresql-13-13.12/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 --- postgresql-13-13.11/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "IMPORT FOREIGN SCHEMA" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "IMPORT FOREIGN SCHEMA" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/INSERT.7 postgresql-13-13.12/doc/src/sgml/man7/INSERT.7 --- postgresql-13-13.11/doc/src/sgml/man7/INSERT.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/INSERT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "INSERT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "INSERT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/LISTEN.7 postgresql-13-13.12/doc/src/sgml/man7/LISTEN.7 --- postgresql-13-13.11/doc/src/sgml/man7/LISTEN.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/LISTEN.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "LISTEN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "LISTEN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/LOAD.7 postgresql-13-13.12/doc/src/sgml/man7/LOAD.7 --- postgresql-13-13.11/doc/src/sgml/man7/LOAD.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/LOAD.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "LOAD" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "LOAD" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/LOCK.7 postgresql-13-13.12/doc/src/sgml/man7/LOCK.7 --- postgresql-13-13.11/doc/src/sgml/man7/LOCK.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/LOCK.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "LOCK" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "LOCK" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/MOVE.7 postgresql-13-13.12/doc/src/sgml/man7/MOVE.7 --- postgresql-13-13.11/doc/src/sgml/man7/MOVE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/MOVE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "MOVE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "MOVE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/NOTIFY.7 postgresql-13-13.12/doc/src/sgml/man7/NOTIFY.7 --- postgresql-13-13.11/doc/src/sgml/man7/NOTIFY.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/NOTIFY.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "NOTIFY" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "NOTIFY" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/PREPARE.7 postgresql-13-13.12/doc/src/sgml/man7/PREPARE.7 --- postgresql-13-13.11/doc/src/sgml/man7/PREPARE.7 2023-05-08 21:34:25.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/PREPARE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PREPARE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PREPARE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/PREPARE_TRANSACTION.7 postgresql-13-13.12/doc/src/sgml/man7/PREPARE_TRANSACTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/PREPARE_TRANSACTION.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/PREPARE_TRANSACTION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "PREPARE TRANSACTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "PREPARE TRANSACTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/REASSIGN_OWNED.7 postgresql-13-13.12/doc/src/sgml/man7/REASSIGN_OWNED.7 --- postgresql-13-13.11/doc/src/sgml/man7/REASSIGN_OWNED.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/REASSIGN_OWNED.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "REASSIGN OWNED" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "REASSIGN OWNED" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 postgresql-13-13.12/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 --- postgresql-13-13.11/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "REFRESH MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "REFRESH MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/REINDEX.7 postgresql-13-13.12/doc/src/sgml/man7/REINDEX.7 --- postgresql-13-13.11/doc/src/sgml/man7/REINDEX.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/REINDEX.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "REINDEX" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "REINDEX" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 postgresql-13-13.12/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 --- postgresql-13-13.11/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "RELEASE SAVEPOINT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "RELEASE SAVEPOINT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/RESET.7 postgresql-13-13.12/doc/src/sgml/man7/RESET.7 --- postgresql-13-13.11/doc/src/sgml/man7/RESET.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/RESET.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "RESET" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "RESET" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/REVOKE.7 postgresql-13-13.12/doc/src/sgml/man7/REVOKE.7 --- postgresql-13-13.11/doc/src/sgml/man7/REVOKE.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/REVOKE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "REVOKE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "REVOKE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK.7 postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK.7 --- postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ROLLBACK" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ROLLBACK" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK_PREPARED.7 postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK_PREPARED.7 --- postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK_PREPARED.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK_PREPARED.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ROLLBACK PREPARED" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ROLLBACK PREPARED" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 --- postgresql-13-13.11/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "ROLLBACK TO SAVEPOINT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "ROLLBACK TO SAVEPOINT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SAVEPOINT.7 postgresql-13-13.12/doc/src/sgml/man7/SAVEPOINT.7 --- postgresql-13-13.11/doc/src/sgml/man7/SAVEPOINT.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SAVEPOINT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SAVEPOINT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SAVEPOINT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SECURITY_LABEL.7 postgresql-13-13.12/doc/src/sgml/man7/SECURITY_LABEL.7 --- postgresql-13-13.11/doc/src/sgml/man7/SECURITY_LABEL.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SECURITY_LABEL.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SECURITY LABEL" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SECURITY LABEL" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SELECT.7 postgresql-13-13.12/doc/src/sgml/man7/SELECT.7 --- postgresql-13-13.11/doc/src/sgml/man7/SELECT.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SELECT.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SELECT" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SELECT" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SELECT_INTO.7 postgresql-13-13.12/doc/src/sgml/man7/SELECT_INTO.7 --- postgresql-13-13.11/doc/src/sgml/man7/SELECT_INTO.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SELECT_INTO.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SELECT INTO" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SELECT INTO" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SET.7 postgresql-13-13.12/doc/src/sgml/man7/SET.7 --- postgresql-13-13.11/doc/src/sgml/man7/SET.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SET.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SET" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SET" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SET_CONSTRAINTS.7 postgresql-13-13.12/doc/src/sgml/man7/SET_CONSTRAINTS.7 --- postgresql-13-13.11/doc/src/sgml/man7/SET_CONSTRAINTS.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SET_CONSTRAINTS.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SET CONSTRAINTS" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SET CONSTRAINTS" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SET_ROLE.7 postgresql-13-13.12/doc/src/sgml/man7/SET_ROLE.7 --- postgresql-13-13.11/doc/src/sgml/man7/SET_ROLE.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SET_ROLE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SET ROLE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SET ROLE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 postgresql-13-13.12/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 --- postgresql-13-13.11/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SET SESSION AUTHORIZATION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SET SESSION AUTHORIZATION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SET_TRANSACTION.7 postgresql-13-13.12/doc/src/sgml/man7/SET_TRANSACTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/SET_TRANSACTION.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SET_TRANSACTION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SET TRANSACTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SET TRANSACTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/SHOW.7 postgresql-13-13.12/doc/src/sgml/man7/SHOW.7 --- postgresql-13-13.11/doc/src/sgml/man7/SHOW.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/SHOW.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "SHOW" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "SHOW" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/START_TRANSACTION.7 postgresql-13-13.12/doc/src/sgml/man7/START_TRANSACTION.7 --- postgresql-13-13.11/doc/src/sgml/man7/START_TRANSACTION.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/START_TRANSACTION.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "START TRANSACTION" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "START TRANSACTION" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/TRUNCATE.7 postgresql-13-13.12/doc/src/sgml/man7/TRUNCATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/TRUNCATE.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/TRUNCATE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "TRUNCATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "TRUNCATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/UNLISTEN.7 postgresql-13-13.12/doc/src/sgml/man7/UNLISTEN.7 --- postgresql-13-13.11/doc/src/sgml/man7/UNLISTEN.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/UNLISTEN.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "UNLISTEN" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "UNLISTEN" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/UPDATE.7 postgresql-13-13.12/doc/src/sgml/man7/UPDATE.7 --- postgresql-13-13.11/doc/src/sgml/man7/UPDATE.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/UPDATE.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "UPDATE" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "UPDATE" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/VACUUM.7 postgresql-13-13.12/doc/src/sgml/man7/VACUUM.7 --- postgresql-13-13.11/doc/src/sgml/man7/VACUUM.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/VACUUM.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "VACUUM" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "VACUUM" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/man7/VALUES.7 postgresql-13-13.12/doc/src/sgml/man7/VALUES.7 --- postgresql-13-13.11/doc/src/sgml/man7/VALUES.7 2023-05-08 21:34:26.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/man7/VALUES.7 2023-08-07 20:32:46.000000000 +0000 @@ -3,11 +3,11 @@ .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot .\" Date: 2023 -.\" Manual: PostgreSQL 13.11 Documentation -.\" Source: PostgreSQL 13.11 +.\" Manual: PostgreSQL 13.12 Documentation +.\" Source: PostgreSQL 13.12 .\" Language: English .\" -.TH "VALUES" "7" "2023" "PostgreSQL 13.11" "PostgreSQL 13.11 Documentation" +.TH "VALUES" "7" "2023" "PostgreSQL 13.12" "PostgreSQL 13.12 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.11/doc/src/sgml/queries.sgml postgresql-13-13.12/doc/src/sgml/queries.sgml --- postgresql-13-13.11/doc/src/sgml/queries.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/queries.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -858,7 +858,7 @@ - A LATERAL item can appear at top level in the + A LATERAL item can appear at the top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that are on the left-hand side of a JOIN that it is on the right-hand side of. diff -Nru postgresql-13-13.11/doc/src/sgml/ref/alter_foreign_table.sgml postgresql-13-13.12/doc/src/sgml/ref/alter_foreign_table.sgml --- postgresql-13-13.11/doc/src/sgml/ref/alter_foreign_table.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/ref/alter_foreign_table.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -521,7 +521,7 @@ To change options of a foreign table: -ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2 'value2', DROP opt3 'value3'); +ALTER FOREIGN TABLE myschema.distributors OPTIONS (ADD opt1 'value', SET opt2 'value2', DROP opt3); diff -Nru postgresql-13-13.11/doc/src/sgml/ref/create_statistics.sgml postgresql-13-13.12/doc/src/sgml/ref/create_statistics.sgml --- postgresql-13-13.11/doc/src/sgml/ref/create_statistics.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/ref/create_statistics.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -127,6 +127,12 @@ reading it. Once created, however, the ownership of the statistics object is independent of the underlying table(s). + + + Extended statistics are not currently used by the planner for selectivity + estimations made for table joins. This limitation will likely be removed + in a future version of PostgreSQL. + diff -Nru postgresql-13-13.11/doc/src/sgml/ref/drop_subscription.sgml postgresql-13-13.12/doc/src/sgml/ref/drop_subscription.sgml --- postgresql-13-13.11/doc/src/sgml/ref/drop_subscription.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/ref/drop_subscription.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -84,9 +84,11 @@ for the subscription on the remote host are released. If this fails, either because the remote host is not reachable or because the remote replication slot cannot be dropped or does not exist or never existed, - the DROP SUBSCRIPTION command will fail. To proceed in - this situation, disassociate the subscription from the replication slot by - executing ALTER SUBSCRIPTION ... SET (slot_name = NONE). + the DROP SUBSCRIPTION command will fail. To proceed + in this situation, first disable the subscription by executing + ALTER SUBSCRIPTION ... DISABLE, and then disassociate + it from the replication slot by executing + ALTER SUBSCRIPTION ... SET (slot_name = NONE). After that, DROP SUBSCRIPTION will no longer attempt any actions on a remote host. Note that if the remote replication slot still exists, it should then be dropped manually; otherwise it will continue to diff -Nru postgresql-13-13.11/doc/src/sgml/release-13.sgml postgresql-13-13.12/doc/src/sgml/release-13.sgml --- postgresql-13-13.11/doc/src/sgml/release-13.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/release-13.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -1,6 +1,866 @@ + + Release 13.12 + + + Release date: + 2023-08-10 + + + + This release contains a variety of fixes from 13.11. + For information about new features in major release 13, see + . + + + + Migration to Version 13.12 + + + A dump/restore is not required for those running 13.X. + + + + However, if you use BRIN indexes, it may be advisable to reindex them; + see the second changelog entry below. + + + + Also, if you are upgrading from a version earlier than 13.7, + see . + + + + + Changes + + + + + + + Disallow substituting a schema or owner name into an extension script + if the name contains a quote, backslash, or dollar sign (Noah Misch) + + + + This restriction guards against SQL-injection hazards for trusted + extensions. + + + + The PostgreSQL Project thanks Micah Gate, + Valerie Woolard, Tim Carey-Smith, and Christoph Berg for reporting + this problem. + (CVE-2023-39417) + + + + + + + Fix confusion between empty (no rows) ranges and all-NULL ranges in + BRIN indexes, as well as incorrect merging of all-NULL summaries + (Tomas Vondra) + + + + Each of these oversights could result in forgetting that a BRIN + index range contains any NULL values, potentially allowing + subsequent queries that should return NULL values to miss doing so. + + + + This fix will not in itself correct faulty BRIN entries. + It's recommended to REINDEX any BRIN indexes that + may be used to search for nulls. + + + + + + + Avoid leaving a corrupted database behind when DROP + DATABASE is interrupted (Andres Freund) + + + + If DROP DATABASE was interrupted after it had + already begun taking irreversible steps, the target database + remained accessible (because the removal of + its pg_database row would roll back), + but it would have corrupt contents. Fix by marking the database + as inaccessible before we begin to perform irreversible operations. + A failure after that will leave the database still partially + present, but nothing can be done with it except to issue + another DROP DATABASE. + + + + + + + Ensure that partitioned indexes are correctly marked as valid or not + at creation (Michael Paquier) + + + + If a new partitioned index matches an existing but invalid index on + one of the partitions, the partitioned index could end up being + marked valid prematurely. This could lead to misbehavior or + assertion failures in subsequent queries on the partitioned table. + + + + + + + Ignore invalid child indexes when matching partitioned indexes to + child indexes during ALTER TABLE ATTACH PARTITION + (Michael Paquier) + + + + Such an index will now be ignored, and a new child index created + instead. + + + + + + + Fix possible failure when marking a partitioned index valid after + all of its partitions have been attached (Michael Paquier) + + + + The update of the index's pg_index entry + could use stale data for other columns. One reported symptom is + an attempted to update invisible tuple error. + + + + + + + Fix ALTER EXTENSION SET SCHEMA to complain if the + extension contains any objects outside the extension's schema + (Michael Paquier, Heikki Linnakangas) + + + + Erroring out if the extension contains objects in multiple schemas + was always intended; but the check was mis-coded so that it would + fail to detect some cases, leading to surprising behavior. + + + + + + + Don't use partial unique indexes for uniqueness proofs in the + planner (David Rowley) + + + + This could give rise to incorrect plans, since the presumed + uniqueness of rows read from a table might not hold if the index in + question isn't used to scan the table. + + + + + + + Avoid producing incorrect plans for foreign joins with + pseudoconstant join clauses (Etsuro Fujita) + + + + The planner currently lacks support for attaching pseudoconstant + join clauses to a pushed-down remote join, so disable generation + of remote joins in such cases. (A better solution will require + ABI-breaking changes of planner data structures, so it will have to + wait for a future major release.) + + + + + + + Correctly handle sub-SELECTs in RLS policy expressions and + security-barrier views when expanding rule actions (Tom Lane) + + + + + + + Fix race conditions in conflict detection + for SERIALIZABLE isolation mode + (Thomas Munro) + + + + Conflicts could be missed when using bitmap heap scans, when using + GIN indexes, and when examining an initially-empty btree index. + All these cases could lead to serializability failures due to + improperly allowing conflicting transactions to commit. + + + + + + + Fix hash join with an inner-side hash key that contains Params + coming from an outer nested loop (Tom Lane) + + + + When rescanning the join after the values of such Params have + changed, we must rebuild the hash table, but neglected to do so. + This could result in missing join output rows. + + + + + + + Fix intermittent failures when trying to update a field of a + composite column (Tom Lane) + + + + If the overall value of the composite column is wide enough to + require out-of-line toasting, then an unluckily-timed cache flush + could cause errors or server crashes. + + + + + + + Prevent query-lifespan memory leaks in some UPDATE + queries with triggers (Tomas Vondra) + + + + + + + Prevent query-lifespan memory leaks when an Incremental Sort plan + node is rescanned (James Coleman, Laurenz Albe, Tom Lane) + + + + + + + Accept fractional seconds in the input to jsonpath's + datetime() method (Tom Lane) + + + + + + + Prevent stack-overflow crashes with very complex text search + patterns (Tom Lane) + + + + + + + Allow tokens up to 10240 bytes long + in pg_hba.conf + and pg_ident.conf (Tom Lane) + + + + The previous limit of 256 bytes has been found insufficient for some + use-cases. + + + + + + + Fix mishandling of C++ out-of-memory conditions (Heikki Linnakangas) + + + + If JIT is in use, running out of memory in a + C++ new call would lead to + a PostgreSQL FATAL error, instead of the + expected C++ exception. + + + + + + + Fix rare null-pointer crash in plancache.c + (Tom Lane) + + + + + + + Avoid losing track of possibly-useful shared memory segments when a + page free results in coalescing ranges of free space (Dongming Liu) + + + + Ensure that the segment is moved into the + appropriate bin for its new amount of free space, so + that it will be found by subsequent searches. + + + + + + + Allow VACUUM to continue after detecting certain + types of b-tree index corruption (Peter Geoghegan) + + + + If an invalid sibling-page link is detected, log the issue and press + on, rather than throwing an error as before. Nothing short + of REINDEX will fix the broken index, but + preventing VACUUM from completing until that is + done risks making matters far worse. + + + + + + + Ensure that WrapLimitsVacuumLock is released + after VACUUM detects invalid data + in pg_database.datfrozenxid + or pg_database.datminmxid + (Andres Freund) + + + + Failure to release this lock could lead to a deadlock later, + although the lock would be cleaned up if the session exits or + encounters some other error. + + + + + + + Avoid double replay of prepared transactions during crash + recovery (suyu.cmj, Michael Paquier) + + + + After a crash partway through a checkpoint with some two-phase + transaction state data already flushed to disk by this checkpoint, + crash recovery could attempt to replay the prepared transaction(s) + twice, leading to a fatal error such as lock is already + held in the startup process. + + + + + + + Fix possible failure while promoting a standby server, if archiving + is enabled and two-phase transactions need to be recovered (Julian + Markwort) + + + + If any required two-phase transactions were logged in the most + recent (partial) log segment, promotion would fail with an incorrect + complaint about requested WAL segment has already been + removed. + + + + + + + Ensure that a newly created, but still empty table + is fsync'ed at the next checkpoint (Heikki + Linnakangas) + + + + Without this, if there is an operating system crash causing the + empty file to disappear, subsequent operations on the table might + fail with could not open file errors. + + + + + + + Ensure that creation of the init fork of an unlogged index is + WAL-logged (Heikki Linnakangas) + + + + While an unlogged index's main data fork is not WAL-logged, its init + fork should be, to ensure that we have a consistent state to restore + the index to after a crash. This step was missed if the init fork + contains no data, which is a case not used by any standard index AM; + but perhaps some extension behaves that way. + + + + + + + Fix missing reinitializations of delay-checkpoint-end flags + (suyu.cmj) + + + + This could result in unnecessary delays of checkpoints, or in + assertion failures in assert-enabled builds. + + + + + + + Fix overly strict assertion in jsonpath code + (David Rowley) + + + + This assertion failed if a query applied + the .type() operator to + a like_regex result. + There was no bug in non-assert builds. + + + + + + + Avoid assertion failure when processing an empty statement via the + extended query protocol in an already-aborted transaction (Tom Lane) + + + + + + + Fix contrib/fuzzystrmatch's + Soundex difference() function to handle empty + input sanely (Alexander Lakhin, Tom Lane) + + + + An input string containing no alphabetic characters resulted in + unpredictable output. + + + + + + + Tighten whitespace checks in contrib/hstore + input (Evan Jones) + + + + In some cases, characters would be falsely recognized as whitespace + and hence discarded. + + + + + + + Disallow oversize input arrays + with contrib/intarray's + gist__int_ops index opclass (Ankit Kumar Pandey, + Alexander Lakhin) + + + + Previously this code would report a NOTICE but + press on anyway, creating an invalid index entry that presents a + risk of crashes when the index is read. + + + + + + + Avoid useless double decompression of GiST index entries + in contrib/intarray (Konstantin Knizhnik, + Matthias van de Meent, Tom Lane) + + + + + + + Ensure + that pg_index.indisreplident + is kept up-to-date in relation cache entries (Shruthi Gowda) + + + + This value could be stale in some cases. There is no core code that + relies on the relation cache's copy, so this is only a latent bug as + far as Postgres itself is concerned; but there may be extensions for + which it is a live bug. + + + + + + + Silence deprecation warnings when compiling with OpenSSL 3.0.0 or + later (Peter Eisentraut) + + + + + + + + Release 13.11 diff -Nru postgresql-13-13.11/doc/src/sgml/spi.sgml postgresql-13-13.12/doc/src/sgml/spi.sgml --- postgresql-13-13.11/doc/src/sgml/spi.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/spi.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -4679,15 +4679,16 @@ => INSERT INTO a VALUES (execq('INSERT INTO a VALUES (0)', 0)); INSERT 0 1 => SELECT execq('SELECT * FROM a', 0); -INFO: EXECQ: 0 -- inserted by execq -INFO: EXECQ: 1 -- returned by execq and inserted by upper INSERT +INFO: EXECQ: 0 -- inserted by execq +INFO: EXECQ: 1 -- returned by execq and inserted by upper INSERT execq ------- 2 (1 row) -=> SELECT execq('INSERT INTO a SELECT x + 2 FROM a', 1); +=> SELECT execq('INSERT INTO a SELECT x + 2 FROM a RETURNING *', 1); +INFO: EXECQ: 2 -- 0 + 2, then execution was stopped by count execq ------- 1 @@ -4696,21 +4697,38 @@ => SELECT execq('SELECT * FROM a', 10); INFO: EXECQ: 0 INFO: EXECQ: 1 -INFO: EXECQ: 2 -- 0 + 2, only one row inserted - as specified +INFO: EXECQ: 2 + + execq +------- + 3 -- 10 is the max value only, 3 is the real number of rows +(1 row) +=> SELECT execq('INSERT INTO a SELECT x + 10 FROM a', 1); execq ------- - 3 -- 10 is the max value only, 3 is the real number of rows + 3 -- all rows processed; count does not stop it, because nothing is returned (1 row) +=> SELECT * FROM a; + x +---- + 0 + 1 + 2 + 10 + 11 + 12 +(6 rows) + => DELETE FROM a; -DELETE 3 +DELETE 6 => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1); INSERT 0 1 => SELECT * FROM a; x --- - 1 -- no rows in a (0) + 1 + 1 -- 0 (no rows in a) + 1 (1 row) => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1); @@ -4720,15 +4738,16 @@ x --- 1 - 2 -- there was one row in a + 1 + 2 -- 1 (there was one row in a) + 1 (2 rows) --- This demonstrates the data changes visibility rule: +-- This demonstrates the data changes visibility rule. +-- execq is called twice and sees different numbers of rows each time: => INSERT INTO a SELECT execq('SELECT * FROM a', 0) * x FROM a; -INFO: EXECQ: 1 +INFO: EXECQ: 1 -- results from first execq INFO: EXECQ: 2 -INFO: EXECQ: 1 +INFO: EXECQ: 1 -- results from second execq INFO: EXECQ: 2 INFO: EXECQ: 2 INSERT 0 2 @@ -4737,10 +4756,9 @@ --- 1 2 - 2 -- 2 rows * 1 (x in first row) - 6 -- 3 rows (2 + 1 just inserted) * 2 (x in second row) -(4 rows) ^^^^^^ - rows visible to execq() in different invocations + 2 -- 2 rows * 1 (x in first row) + 6 -- 3 rows (2 + 1 just inserted) * 2 (x in second row) +(4 rows)     diff -Nru postgresql-13-13.11/doc/src/sgml/storage.sgml postgresql-13-13.12/doc/src/sgml/storage.sgml --- postgresql-13-13.11/doc/src/sgml/storage.sgml 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/doc/src/sgml/storage.sgml 2023-08-07 20:11:34.000000000 +0000 @@ -1131,7 +1131,7 @@ if columns used by indexes are not updated. You can increase the likelihood of sufficient page space for HOT updates by decreasing a table's fillfactor. + linkend="reloption-fillfactor">fillfactor. If you don't, HOT updates will still happen because new rows will naturally migrate to new pages and existing pages with sufficient free space for new row versions. The system view bt_empty_range; + /* * Compare the key values of the new tuple to the stored index values; * our deformed tuple will get updated if the new tuple doesn't fit @@ -253,8 +257,20 @@ Datum result; BrinValues *bval; FmgrInfo *addValue; + bool has_nulls; bval = &dtup->bt_columns[keyno]; + + /* + * Does the range have actual NULL values? Either of the flags can + * be set, but we ignore the state before adding first row. + * + * We have to remember this, because we'll modify the flags and we + * need to know if the range started as empty. + */ + has_nulls = ((!dtup->bt_empty_range) && + (bval->bv_hasnulls || bval->bv_allnulls)); + addValue = index_getprocinfo(idxRel, keyno + 1, BRIN_PROCNUM_ADDVALUE); result = FunctionCall4Coll(addValue, @@ -265,8 +281,33 @@ nulls[keyno]); /* if that returned true, we need to insert the updated tuple */ need_insert |= DatumGetBool(result); + + /* + * If the range was had actual NULL values (i.e. did not start empty), + * make sure we don't forget about the NULL values. Either the allnulls + * flag is still set to true, or (if the opclass cleared it) we need to + * set hasnulls=true. + * + * XXX This can only happen when the opclass modified the tuple, so the + * modified flag should be set. + */ + if (has_nulls && !(bval->bv_hasnulls || bval->bv_allnulls)) + { + Assert(need_insert); + bval->bv_hasnulls = true; + } } + /* + * After updating summaries for all the keys, mark it as not empty. + * + * If we're actually changing the flag value (i.e. tuple started as + * empty), we should have modified the tuple. So we should not see + * empty range that was not modified. + */ + Assert(!dtup->bt_empty_range || need_insert); + dtup->bt_empty_range = false; + if (!need_insert) { /* @@ -509,6 +550,17 @@ } /* + * If the BRIN tuple indicates that this range is empty, + * we can skip it: there's nothing to match. We don't + * need to examine the next columns. + */ + if (dtup->bt_empty_range) + { + addrange = false; + break; + } + + /* * Check whether the scan key is consistent with the page * range values; if so, have the pages in the range added * to the output bitmap. @@ -645,8 +697,24 @@ FmgrInfo *addValue; BrinValues *col; Form_pg_attribute attr = TupleDescAttr(state->bs_bdesc->bd_tupdesc, i); + bool has_nulls; col = &state->bs_dtuple->bt_columns[i]; + + /* + * Does the range have actual NULL values? Either of the flags can + * be set, but we ignore the state before adding first row. + * + * We have to remember this, because we'll modify the flags and we + * need to know if the range started as empty. + */ + has_nulls = ((!state->bs_dtuple->bt_empty_range) && + (col->bv_hasnulls || col->bv_allnulls)); + + /* + * Call the BRIN_PROCNUM_ADDVALUE procedure. We do this even for NULL + * values, because who knows what the opclass is doing. + */ addValue = index_getprocinfo(index, i + 1, BRIN_PROCNUM_ADDVALUE); @@ -658,7 +726,25 @@ PointerGetDatum(state->bs_bdesc), PointerGetDatum(col), values[i], isnull[i]); + + /* + * If the range was had actual NULL values (i.e. did not start empty), + * make sure we don't forget about the NULL values. Either the allnulls + * flag is still set to true, or (if the opclass cleared it) we need to + * set hasnulls=true. + */ + if (has_nulls && !(col->bv_hasnulls || col->bv_allnulls)) + col->bv_hasnulls = true; } + + /* + * After updating summaries for all the keys, mark it as not empty. + * + * If we're actually changing the flag value (i.e. tuple started as + * empty), we should have modified the tuple. So we should not see + * empty range that was not modified. + */ + state->bs_dtuple->bt_empty_range = false; } /* @@ -1465,6 +1551,64 @@ db = brin_deform_tuple(bdesc, b, NULL); MemoryContextSwitchTo(oldcxt); + /* + * Check if the ranges are empty. + * + * If at least one of them is empty, we don't need to call per-key union + * functions at all. If "b" is empty, we just use "a" as the result (it + * might be empty fine, but that's fine). If "a" is empty but "b" is not, + * we use "b" as the result (but we have to copy the data into "a" first). + * + * Only when both ranges are non-empty, we actually do the per-key merge. + */ + + /* If "b" is empty - ignore it and just use "a" (even if it's empty etc.). */ + if (db->bt_empty_range) + { + /* skip the per-key merge */ + MemoryContextDelete(cxt); + return; + } + + /* + * Now we know "b" is not empty. If "a" is empty, then "b" is the result. + * But we need to copy the data from "b" to "a" first, because that's how + * we pass result out. + * + * We have to copy all the global/per-key flags etc. too. + */ + if (a->bt_empty_range) + { + for (keyno = 0; keyno < bdesc->bd_tupdesc->natts; keyno++) + { + int i; + BrinValues *col_a = &a->bt_columns[keyno]; + BrinValues *col_b = &db->bt_columns[keyno]; + BrinOpcInfo *opcinfo = bdesc->bd_info[keyno]; + + col_a->bv_allnulls = col_b->bv_allnulls; + col_a->bv_hasnulls = col_b->bv_hasnulls; + + /* If "b" has no data, we're done. */ + if (col_b->bv_allnulls) + continue; + + for (i = 0; i < opcinfo->oi_nstored; i++) + col_a->bv_values[i] = + datumCopy(col_b->bv_values[i], + opcinfo->oi_typcache[i]->typbyval, + opcinfo->oi_typcache[i]->typlen); + } + + /* "a" started empty, but "b" was not empty, so remember that */ + a->bt_empty_range = false; + + /* skip the per-key merge */ + MemoryContextDelete(cxt); + return; + } + + /* Neither range is empty, so call the union proc. */ for (keyno = 0; keyno < bdesc->bd_tupdesc->natts; keyno++) { FmgrInfo *unionFn; diff -Nru postgresql-13-13.11/src/backend/access/brin/brin_inclusion.c postgresql-13-13.12/src/backend/access/brin/brin_inclusion.c --- postgresql-13-13.11/src/backend/access/brin/brin_inclusion.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/brin/brin_inclusion.c 2023-08-07 20:11:34.000000000 +0000 @@ -515,10 +515,13 @@ FmgrInfo *finfo; Datum result; + /* Does the "b" summary represent any NULL values? */ + bool b_has_nulls = (col_b->bv_hasnulls || col_b->bv_allnulls); + Assert(col_a->bv_attno == col_b->bv_attno); /* Adjust "hasnulls". */ - if (!col_a->bv_hasnulls && col_b->bv_hasnulls) + if (!col_a->bv_allnulls && b_has_nulls) col_a->bv_hasnulls = true; /* If there are no values in B, there's nothing left to do. */ @@ -533,10 +536,15 @@ * B into A, and we're done. We cannot run the operators in this case, * because values in A might contain garbage. Note we already established * that B contains values. + * + * Also adjust "hasnulls" in order not to forget the summary represents NULL + * values. This is not redundant with the earlier update, because that only + * happens when allnulls=false. */ if (col_a->bv_allnulls) { col_a->bv_allnulls = false; + col_a->bv_hasnulls = true; col_a->bv_values[INCLUSION_UNION] = datumCopy(col_b->bv_values[INCLUSION_UNION], attr->attbyval, attr->attlen); diff -Nru postgresql-13-13.11/src/backend/access/brin/brin_minmax.c postgresql-13-13.12/src/backend/access/brin/brin_minmax.c --- postgresql-13-13.11/src/backend/access/brin/brin_minmax.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/brin/brin_minmax.c 2023-08-07 20:11:34.000000000 +0000 @@ -248,10 +248,13 @@ FmgrInfo *finfo; bool needsadj; + /* Does the "b" summary represent any NULL values? */ + bool b_has_nulls = (col_b->bv_hasnulls || col_b->bv_allnulls); + Assert(col_a->bv_attno == col_b->bv_attno); /* Adjust "hasnulls" */ - if (!col_a->bv_hasnulls && col_b->bv_hasnulls) + if (!col_a->bv_allnulls && b_has_nulls) col_a->bv_hasnulls = true; /* If there are no values in B, there's nothing left to do */ @@ -266,10 +269,15 @@ * B into A, and we're done. We cannot run the operators in this case, * because values in A might contain garbage. Note we already established * that B contains values. + * + * Also adjust "hasnulls" in order not to forget the summary represents NULL + * values. This is not redundant with the earlier update, because that only + * happens when allnulls=false. */ if (col_a->bv_allnulls) { col_a->bv_allnulls = false; + col_a->bv_hasnulls = true; col_a->bv_values[0] = datumCopy(col_b->bv_values[0], attr->attbyval, attr->attlen); col_a->bv_values[1] = datumCopy(col_b->bv_values[1], diff -Nru postgresql-13-13.11/src/backend/access/brin/brin_tuple.c postgresql-13-13.12/src/backend/access/brin/brin_tuple.c --- postgresql-13-13.11/src/backend/access/brin/brin_tuple.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/brin/brin_tuple.c 2023-08-07 20:11:34.000000000 +0000 @@ -349,6 +349,9 @@ if (tuple->bt_placeholder) rettuple->bt_info |= BRIN_PLACEHOLDER_MASK; + if (tuple->bt_empty_range) + rettuple->bt_info |= BRIN_EMPTY_RANGE_MASK; + *size = len; return rettuple; } @@ -376,7 +379,7 @@ rettuple = palloc0(len); rettuple->bt_blkno = blkno; rettuple->bt_info = hoff; - rettuple->bt_info |= BRIN_NULLS_MASK | BRIN_PLACEHOLDER_MASK; + rettuple->bt_info |= BRIN_NULLS_MASK | BRIN_PLACEHOLDER_MASK | BRIN_EMPTY_RANGE_MASK; bitP = ((bits8 *) ((char *) rettuple + SizeOfBrinTuple)) - 1; bitmask = HIGHBIT; @@ -466,6 +469,8 @@ dtup->bt_allnulls = palloc(sizeof(bool) * brdesc->bd_tupdesc->natts); dtup->bt_hasnulls = palloc(sizeof(bool) * brdesc->bd_tupdesc->natts); + dtup->bt_empty_range = true; + dtup->bt_context = AllocSetContextCreate(CurrentMemoryContext, "brin dtuple", ALLOCSET_DEFAULT_SIZES); @@ -499,6 +504,8 @@ currdatum += sizeof(Datum) * brdesc->bd_info[i]->oi_nstored; } + dtuple->bt_empty_range = true; + return dtuple; } @@ -532,6 +539,11 @@ if (BrinTupleIsPlaceholder(tuple)) dtup->bt_placeholder = true; + + /* ranges start as empty, depends on the BrinTuple */ + if (!BrinTupleIsEmptyRange(tuple)) + dtup->bt_empty_range = false; + dtup->bt_blkno = tuple->bt_blkno; values = dtup->bt_values; diff -Nru postgresql-13-13.11/src/backend/access/gin/ginfast.c postgresql-13-13.12/src/backend/access/gin/ginfast.c --- postgresql-13-13.11/src/backend/access/gin/ginfast.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/gin/ginfast.c 2023-08-07 20:11:34.000000000 +0000 @@ -245,9 +245,10 @@ /* * An insertion to the pending list could logically belong anywhere in the * tree, so it conflicts with all serializable scans. All scans acquire a - * predicate lock on the metabuffer to represent that. + * predicate lock on the metabuffer to represent that. Therefore we'll + * check for conflicts in, but not until we have the page locked and are + * ready to modify the page. */ - CheckForSerializableConflictIn(index, NULL, GIN_METAPAGE_BLKNO); if (collector->sumsize + collector->ntuples * sizeof(ItemIdData) > GinListPageSize) { @@ -291,6 +292,8 @@ LockBuffer(metabuffer, GIN_EXCLUSIVE); metadata = GinPageGetMeta(metapage); + CheckForSerializableConflictIn(index, NULL, GIN_METAPAGE_BLKNO); + if (metadata->head == InvalidBlockNumber) { /* @@ -353,6 +356,8 @@ char *ptr; char *collectordata; + CheckForSerializableConflictIn(index, NULL, GIN_METAPAGE_BLKNO); + buffer = ReadBuffer(index, metadata->tail); LockBuffer(buffer, GIN_EXCLUSIVE); page = BufferGetPage(buffer); diff -Nru postgresql-13-13.11/src/backend/access/gin/ginget.c postgresql-13-13.12/src/backend/access/gin/ginget.c --- postgresql-13-13.11/src/backend/access/gin/ginget.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/gin/ginget.c 2023-08-07 20:11:34.000000000 +0000 @@ -139,7 +139,9 @@ * Predicate lock entry leaf page, following pages will be locked by * moveRightIfItNeeded() */ - PredicateLockPage(btree->index, stack->buffer, snapshot); + PredicateLockPage(btree->index, + BufferGetBlockNumber(stack->buffer), + snapshot); for (;;) { diff -Nru postgresql-13-13.11/src/backend/access/heap/heapam_handler.c postgresql-13-13.12/src/backend/access/heap/heapam_handler.c --- postgresql-13-13.11/src/backend/access/heap/heapam_handler.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/heap/heapam_handler.c 2023-08-07 20:11:34.000000000 +0000 @@ -2123,9 +2123,11 @@ * Ignore any claimed entries past what we think is the end of the * relation. It may have been extended after the start of our scan (we * only hold an AccessShareLock, and it could be inserts from this - * backend). + * backend). We don't take this optimization in SERIALIZABLE isolation + * though, as we need to examine all invisible tuples reachable by the + * index. */ - if (page >= hscan->rs_nblocks) + if (!IsolationIsSerializable() && page >= hscan->rs_nblocks) return false; /* diff -Nru postgresql-13-13.11/src/backend/access/nbtree/nbtpage.c postgresql-13-13.12/src/backend/access/nbtree/nbtpage.c --- postgresql-13-13.11/src/backend/access/nbtree/nbtpage.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/nbtree/nbtpage.c 2023-08-07 20:11:34.000000000 +0000 @@ -1772,12 +1772,6 @@ &topparent, &topparentrightsib)) return false; - /* - * Check that the parent-page index items we're about to delete/overwrite - * in subtree parent page contain what we expect. This can fail if the - * index has become corrupt for some reason. We want to throw any error - * before entering the critical section --- otherwise it'd be a PANIC. - */ page = BufferGetPage(subtreeparent); opaque = (BTPageOpaque) PageGetSpecialPointer(page); @@ -1795,8 +1789,17 @@ nextoffset = OffsetNumberNext(poffset); itemid = PageGetItemId(page, nextoffset); itup = (IndexTuple) PageGetItem(page, itemid); + + /* + * Check that the parent-page index items we're about to delete/overwrite + * in subtree parent page contain what we expect. This can fail if the + * index has become corrupt for some reason. When that happens we back + * out of deletion of the leafbuf subtree. (This is just like the case + * where _bt_lock_subtree_parent() cannot "re-find" leafbuf's downlink.) + */ if (BTreeTupleGetDownLink(itup) != topparentrightsib) - ereport(ERROR, + { + ereport(LOG, (errcode(ERRCODE_INDEX_CORRUPTED), errmsg_internal("right sibling %u of block %u is not next child %u of block %u in index \"%s\"", topparentrightsib, topparent, @@ -1804,6 +1807,11 @@ BufferGetBlockNumber(subtreeparent), RelationGetRelationName(rel)))); + _bt_relbuf(rel, subtreeparent); + Assert(false); + return false; + } + /* * Any insert which would have gone on the leaf block will now go to its * right sibling. In other words, the key space moves right. @@ -2032,13 +2040,6 @@ leftsib = opaque->btpo_next; _bt_relbuf(rel, lbuf); - /* - * It'd be good to check for interrupts here, but it's not easy to - * do so because a lock is always held. This block isn't - * frequently reached, so hopefully the consequences of not - * checking interrupts aren't too bad. - */ - if (leftsib == P_NONE) { elog(LOG, "no left sibling (concurrent deletion?) of block %u in \"%s\"", @@ -2057,6 +2058,9 @@ } return false; } + + CHECK_FOR_INTERRUPTS(); + lbuf = _bt_getbuf(rel, leftsib, BT_WRITE); page = BufferGetPage(lbuf); opaque = (BTPageOpaque) PageGetSpecialPointer(page); @@ -2118,13 +2122,40 @@ rbuf = _bt_getbuf(rel, rightsib, BT_WRITE); page = BufferGetPage(rbuf); opaque = (BTPageOpaque) PageGetSpecialPointer(page); + + /* + * Validate target's right sibling page. Its left link must point back to + * the target page. + */ if (opaque->btpo_prev != target) - ereport(ERROR, + { + /* + * This is known to fail in the field; sibling link corruption is + * relatively common. Press on with vacuuming rather than just + * throwing an ERROR (same approach used for left-sibling's-right-link + * validation check a moment ago). + */ + ereport(LOG, (errcode(ERRCODE_INDEX_CORRUPTED), errmsg_internal("right sibling's left-link doesn't match: " - "block %u links to %u instead of expected %u in index \"%s\"", - rightsib, opaque->btpo_prev, target, - RelationGetRelationName(rel)))); + "right sibling %u of target %u with leafblkno %u " + "and scanblkno %u spuriously links to non-target %u " + "on level %u of index \"%s\"", + rightsib, target, leafblkno, + scanblkno, opaque->btpo_prev, + targetlevel, RelationGetRelationName(rel)))); + + /* Must release all pins and locks on failure exit */ + if (BufferIsValid(lbuf)) + _bt_relbuf(rel, lbuf); + _bt_relbuf(rel, rbuf); + _bt_relbuf(rel, buf); + if (target != leafblkno) + _bt_relbuf(rel, leafbuf); + + return false; + } + rightsib_is_rightmost = P_RIGHTMOST(opaque); *rightsib_empty = (P_FIRSTDATAKEY(opaque) > PageGetMaxOffsetNumber(page)); @@ -2405,6 +2436,7 @@ (errcode(ERRCODE_INDEX_CORRUPTED), errmsg_internal("failed to re-find parent key in index \"%s\" for deletion target page %u", RelationGetRelationName(rel), child))); + Assert(false); return false; } diff -Nru postgresql-13-13.11/src/backend/access/nbtree/nbtree.c postgresql-13-13.12/src/backend/access/nbtree/nbtree.c --- postgresql-13-13.11/src/backend/access/nbtree/nbtree.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/nbtree/nbtree.c 2023-08-07 20:11:34.000000000 +0000 @@ -1141,8 +1141,7 @@ * can't be half-dead because only an interrupted VACUUM process can * leave pages in that state, so we'd definitely have dealt with it * back when the page was the scanblkno page (half-dead pages are - * always marked fully deleted by _bt_pagedel()). This assumes that - * there can be only one vacuum process running at a time. + * always marked fully deleted by _bt_pagedel(), barring corruption). */ if (!opaque || !P_ISLEAF(opaque) || P_ISHALFDEAD(opaque)) { diff -Nru postgresql-13-13.11/src/backend/access/nbtree/nbtsearch.c postgresql-13-13.12/src/backend/access/nbtree/nbtsearch.c --- postgresql-13-13.11/src/backend/access/nbtree/nbtsearch.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/nbtree/nbtsearch.c 2023-08-07 20:11:34.000000000 +0000 @@ -17,6 +17,7 @@ #include "access/nbtree.h" #include "access/relscan.h" +#include "access/xact.h" #include "miscadmin.h" #include "pgstat.h" #include "storage/predicate.h" @@ -1381,22 +1382,34 @@ { /* * We only get here if the index is completely empty. Lock relation - * because nothing finer to lock exists. + * because nothing finer to lock exists. Without a buffer lock, it's + * possible for another transaction to insert data between + * _bt_search() and PredicateLockRelation(). We have to try again + * after taking the relation-level predicate lock, to close a narrow + * window where we wouldn't scan concurrently inserted tuples, but the + * writer wouldn't see our predicate lock. */ - PredicateLockRelation(rel, scan->xs_snapshot); - - /* - * mark parallel scan as done, so that all the workers can finish - * their scan - */ - _bt_parallel_done(scan); - BTScanPosInvalidate(so->currPos); + if (IsolationIsSerializable()) + { + PredicateLockRelation(rel, scan->xs_snapshot); + stack = _bt_search(rel, &inskey, &buf, BT_READ, + scan->xs_snapshot); + _bt_freestack(stack); + } - return false; + if (!BufferIsValid(buf)) + { + /* + * Mark parallel scan as done, so that all the workers can finish + * their scan. + */ + _bt_parallel_done(scan); + BTScanPosInvalidate(so->currPos); + return false; + } } - else - PredicateLockPage(rel, BufferGetBlockNumber(buf), - scan->xs_snapshot); + + PredicateLockPage(rel, BufferGetBlockNumber(buf), scan->xs_snapshot); _bt_initialize_more_data(so, dir); diff -Nru postgresql-13-13.11/src/backend/access/transam/twophase.c postgresql-13-13.12/src/backend/access/transam/twophase.c --- postgresql-13-13.11/src/backend/access/transam/twophase.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/transam/twophase.c 2023-08-07 20:11:34.000000000 +0000 @@ -2443,6 +2443,39 @@ * that it got added in the redo phase */ + /* + * In the event of a crash while a checkpoint was running, it may be + * possible that some two-phase data found its way to disk while its + * corresponding record needs to be replayed in the follow-up recovery. As + * the 2PC data was on disk, it has already been restored at the beginning + * of recovery with restoreTwoPhaseData(), so skip this record to avoid + * duplicates in TwoPhaseState. If a consistent state has been reached, + * the record is added to TwoPhaseState and it should have no + * corresponding file in pg_twophase. + */ + if (!XLogRecPtrIsInvalid(start_lsn)) + { + char path[MAXPGPATH]; + + TwoPhaseFilePath(path, hdr->xid); + + if (access(path, F_OK) == 0) + { + ereport(reachedConsistency ? ERROR : WARNING, + (errmsg("could not recover two-phase state file for transaction %u", + hdr->xid), + errdetail("Two-phase state file has been found in WAL record %X/%X, but this transaction has already been restored from disk.", + (uint32) (start_lsn >> 32), + (uint32) start_lsn))); + return; + } + + if (errno != ENOENT) + ereport(ERROR, + (errcode_for_file_access(), + errmsg("could not access file \"%s\": %m", path))); + } + /* Get a free gxact from the freelist */ if (TwoPhaseState->freeGXacts == NULL) ereport(ERROR, diff -Nru postgresql-13-13.11/src/backend/access/transam/xlog.c postgresql-13-13.12/src/backend/access/transam/xlog.c --- postgresql-13-13.11/src/backend/access/transam/xlog.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/access/transam/xlog.c 2023-08-07 20:11:34.000000000 +0000 @@ -5891,7 +5891,7 @@ uint8 info; uint8 xact_info; uint8 rmid; - TimestampTz recordXtime; + TimestampTz recordXtime = 0; /* * Ignore recovery target settings when not in archive recovery (meaning @@ -7863,6 +7863,64 @@ CreateCheckPoint(CHECKPOINT_END_OF_RECOVERY | CHECKPOINT_IMMEDIATE); } + /* + * Preallocate additional log files, if wanted. + */ + PreallocXlogFiles(EndOfLog); + + /* + * Okay, we're officially UP. + */ + InRecovery = false; + + /* start the archive_timeout timer and LSN running */ + XLogCtl->lastSegSwitchTime = (pg_time_t) time(NULL); + XLogCtl->lastSegSwitchLSN = EndOfLog; + + /* also initialize latestCompletedXid, to nextXid - 1 */ + LWLockAcquire(ProcArrayLock, LW_EXCLUSIVE); + ShmemVariableCache->latestCompletedXid = XidFromFullTransactionId(ShmemVariableCache->nextFullXid); + TransactionIdRetreat(ShmemVariableCache->latestCompletedXid); + LWLockRelease(ProcArrayLock); + + /* + * Start up the commit log and subtrans, if not already done for hot + * standby. (commit timestamps are started below, if necessary.) + */ + if (standbyState == STANDBY_DISABLED) + { + StartupCLOG(); + StartupSUBTRANS(oldestActiveXID); + } + + /* + * Perform end of recovery actions for any SLRUs that need it. + */ + TrimCLOG(); + TrimMultiXact(); + + /* + * Reload shared-memory state for prepared transactions. This needs to + * happen before renaming the last partial segment of the old timeline as + * it may be possible that we have to recovery some transactions from it. + */ + RecoverPreparedTransactions(); + + /* Shut down xlogreader */ + if (readFile >= 0) + { + close(readFile); + readFile = -1; + } + XLogReaderFree(xlogreader); + + /* + * If any of the critical GUCs have changed, log them before we allow + * backends to write WAL. + */ + LocalSetXLogInsertAllowed(); + XLogReportParameters(); + if (ArchiveRecoveryRequested) { /* @@ -7945,60 +8003,6 @@ } /* - * Preallocate additional log files, if wanted. - */ - PreallocXlogFiles(EndOfLog); - - /* - * Okay, we're officially UP. - */ - InRecovery = false; - - /* start the archive_timeout timer and LSN running */ - XLogCtl->lastSegSwitchTime = (pg_time_t) time(NULL); - XLogCtl->lastSegSwitchLSN = EndOfLog; - - /* also initialize latestCompletedXid, to nextXid - 1 */ - LWLockAcquire(ProcArrayLock, LW_EXCLUSIVE); - ShmemVariableCache->latestCompletedXid = XidFromFullTransactionId(ShmemVariableCache->nextFullXid); - TransactionIdRetreat(ShmemVariableCache->latestCompletedXid); - LWLockRelease(ProcArrayLock); - - /* - * Start up the commit log and subtrans, if not already done for hot - * standby. (commit timestamps are started below, if necessary.) - */ - if (standbyState == STANDBY_DISABLED) - { - StartupCLOG(); - StartupSUBTRANS(oldestActiveXID); - } - - /* - * Perform end of recovery actions for any SLRUs that need it. - */ - TrimCLOG(); - TrimMultiXact(); - - /* Reload shared-memory state for prepared transactions */ - RecoverPreparedTransactions(); - - /* Shut down xlogreader */ - if (readFile >= 0) - { - close(readFile); - readFile = -1; - } - XLogReaderFree(xlogreader); - - /* - * If any of the critical GUCs have changed, log them before we allow - * backends to write WAL. - */ - LocalSetXLogInsertAllowed(); - XLogReportParameters(); - - /* * Local WAL inserts enabled, so it's time to finish initialization of * commit timestamp. */ diff -Nru postgresql-13-13.11/src/backend/catalog/index.c postgresql-13-13.12/src/backend/catalog/index.c --- postgresql-13-13.11/src/backend/catalog/index.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/catalog/index.c 2023-08-07 20:11:34.000000000 +0000 @@ -53,6 +53,7 @@ #include "catalog/pg_trigger.h" #include "catalog/pg_type.h" #include "catalog/storage.h" +#include "catalog/storage_xlog.h" #include "commands/event_trigger.h" #include "commands/progress.h" #include "commands/tablecmds.h" @@ -3013,6 +3014,7 @@ !smgrexists(RelationGetSmgr(indexRelation), INIT_FORKNUM)) { smgrcreate(RelationGetSmgr(indexRelation), INIT_FORKNUM, false); + log_smgrcreate(&indexRelation->rd_node, INIT_FORKNUM); indexRelation->rd_indam->ambuildempty(indexRelation); } diff -Nru postgresql-13-13.11/src/backend/commands/dbcommands.c postgresql-13-13.12/src/backend/commands/dbcommands.c --- postgresql-13-13.11/src/backend/commands/dbcommands.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/dbcommands.c 2023-08-07 20:11:34.000000000 +0000 @@ -140,7 +140,7 @@ int encoding = -1; bool dbistemplate = false; bool dballowconnections = true; - int dbconnlimit = -1; + int dbconnlimit = DATCONNLIMIT_UNLIMITED; int notherbackends; int npreparedxacts; createdb_failure_params fparms; @@ -309,7 +309,7 @@ if (dconnlimit && dconnlimit->arg) { dbconnlimit = defGetInt32(dconnlimit); - if (dbconnlimit < -1) + if (dbconnlimit < DATCONNLIMIT_UNLIMITED) ereport(ERROR, (errcode(ERRCODE_INVALID_PARAMETER_VALUE), errmsg("invalid connection limit: %d", dbconnlimit))); @@ -358,6 +358,16 @@ dbtemplate))); /* + * If the source database was in the process of being dropped, we can't + * use it as a template. + */ + if (database_is_invalid_oid(src_dboid)) + ereport(ERROR, + errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), + errmsg("cannot use invalid database \"%s\" as template", dbtemplate), + errhint("Use DROP DATABASE to drop invalid databases.")); + + /* * Permission check: to copy a DB that's not marked datistemplate, you * must be superuser or the owner thereof. */ @@ -817,6 +827,7 @@ bool db_istemplate; Relation pgdbrel; HeapTuple tup; + Form_pg_database datform; int notherbackends; int npreparedxacts; int nslots, @@ -933,17 +944,6 @@ errdetail_busy_db(notherbackends, npreparedxacts))); /* - * Remove the database's tuple from pg_database. - */ - tup = SearchSysCache1(DATABASEOID, ObjectIdGetDatum(db_id)); - if (!HeapTupleIsValid(tup)) - elog(ERROR, "cache lookup failed for database %u", db_id); - - CatalogTupleDelete(pgdbrel, &tup->t_self); - - ReleaseSysCache(tup); - - /* * Delete any comments or security labels associated with the database. */ DeleteSharedComments(db_id, DatabaseRelationId); @@ -959,6 +959,32 @@ */ dropDatabaseDependencies(db_id); + tup = SearchSysCacheCopy1(DATABASEOID, ObjectIdGetDatum(db_id)); + if (!HeapTupleIsValid(tup)) + elog(ERROR, "cache lookup failed for database %u", db_id); + datform = (Form_pg_database) GETSTRUCT(tup); + + /* + * Except for the deletion of the catalog row, subsequent actions are not + * transactional (consider DropDatabaseBuffers() discarding modified + * buffers). But we might crash or get interrupted below. To prevent + * accesses to a database with invalid contents, mark the database as + * invalid using an in-place update. + * + * We need to flush the WAL before continuing, to guarantee the + * modification is durable before performing irreversible filesystem + * operations. + */ + datform->datconnlimit = DATCONNLIMIT_INVALID_DB; + heap_inplace_update(pgdbrel, tup); + XLogFlush(XactLastRecEnd); + + /* + * Also delete the tuple - transactionally. If this transaction commits, + * the row will be gone, but if we fail, dropdb() can be invoked again. + */ + CatalogTupleDelete(pgdbrel, &tup->t_self); + /* * Drop db-specific replication slots. */ @@ -1481,7 +1507,7 @@ ListCell *option; bool dbistemplate = false; bool dballowconnections = true; - int dbconnlimit = -1; + int dbconnlimit = DATCONNLIMIT_UNLIMITED; DefElem *distemplate = NULL; DefElem *dallowconnections = NULL; DefElem *dconnlimit = NULL; @@ -1564,7 +1590,7 @@ if (dconnlimit && dconnlimit->arg) { dbconnlimit = defGetInt32(dconnlimit); - if (dbconnlimit < -1) + if (dbconnlimit < DATCONNLIMIT_UNLIMITED) ereport(ERROR, (errcode(ERRCODE_INVALID_PARAMETER_VALUE), errmsg("invalid connection limit: %d", dbconnlimit))); @@ -1591,6 +1617,14 @@ datform = (Form_pg_database) GETSTRUCT(tuple); dboid = datform->oid; + if (database_is_invalid_form(datform)) + { + ereport(FATAL, + errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), + errmsg("cannot alter invalid database \"%s\"", stmt->dbname), + errhint("Use DROP DATABASE to drop invalid databases.")); + } + if (!pg_database_ownercheck(dboid, GetUserId())) aclcheck_error(ACLCHECK_NOT_OWNER, OBJECT_DATABASE, stmt->dbname); @@ -2170,6 +2204,42 @@ return result; } + +/* + * While dropping a database the pg_database row is marked invalid, but the + * catalog contents still exist. Connections to such a database are not + * allowed. + */ +bool +database_is_invalid_form(Form_pg_database datform) +{ + return datform->datconnlimit == DATCONNLIMIT_INVALID_DB; +} + + +/* + * Convenience wrapper around database_is_invalid_form() + */ +bool +database_is_invalid_oid(Oid dboid) +{ + HeapTuple dbtup; + Form_pg_database dbform; + bool invalid; + + dbtup = SearchSysCache1(DATABASEOID, ObjectIdGetDatum(dboid)); + if (!HeapTupleIsValid(dbtup)) + elog(ERROR, "cache lookup failed for database %u", dboid); + dbform = (Form_pg_database) GETSTRUCT(dbtup); + + invalid = database_is_invalid_form(dbform); + + ReleaseSysCache(dbtup); + + return invalid; +} + + /* * recovery_create_dbdir() * diff -Nru postgresql-13-13.11/src/backend/commands/extension.c postgresql-13-13.12/src/backend/commands/extension.c --- postgresql-13-13.11/src/backend/commands/extension.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/extension.c 2023-08-07 20:11:34.000000000 +0000 @@ -957,6 +957,16 @@ char *c_sql = read_extension_script_file(control, filename); Datum t_sql; + /* + * We filter each substitution through quote_identifier(). When the + * arg contains one of the following characters, no one collection of + * quoting can work inside $$dollar-quoted string literals$$, + * 'single-quoted string literals', and outside of any literal. To + * avoid a security snare for extension authors, error on substitution + * for arguments containing these. + */ + const char *quoting_relevant_chars = "\"$'\\"; + /* We use various functions that want to operate on text datums */ t_sql = CStringGetTextDatum(c_sql); @@ -986,6 +996,11 @@ t_sql, CStringGetTextDatum("@extowner@"), CStringGetTextDatum(qUserName)); + if (strpbrk(userName, quoting_relevant_chars)) + ereport(ERROR, + (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION), + errmsg("invalid character in extension owner: must not contain any of \"%s\"", + quoting_relevant_chars))); } /* @@ -997,6 +1012,7 @@ */ if (!control->relocatable) { + Datum old = t_sql; const char *qSchemaName = quote_identifier(schemaName); t_sql = DirectFunctionCall3Coll(replace_text, @@ -1004,6 +1020,11 @@ t_sql, CStringGetTextDatum("@extschema@"), CStringGetTextDatum(qSchemaName)); + if (t_sql != old && strpbrk(schemaName, quoting_relevant_chars)) + ereport(ERROR, + (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION), + errmsg("invalid character in extension \"%s\" schema: must not contain any of \"%s\"", + control->name, quoting_relevant_chars))); } /* @@ -2788,7 +2809,7 @@ { Oid extensionOid; Oid nspOid; - Oid oldNspOid = InvalidOid; + Oid oldNspOid; AclResult aclresult; Relation extRel; ScanKeyData key[2]; @@ -2871,6 +2892,9 @@ objsMoved = new_object_addresses(); + /* store the OID of the namespace to-be-changed */ + oldNspOid = extForm->extnamespace; + /* * Scan pg_depend to find objects that depend directly on the extension, * and alter each one's schema. @@ -2917,12 +2941,6 @@ objsMoved); /* - * Remember previous namespace of first object that has one - */ - if (oldNspOid == InvalidOid && dep_oldNspOid != InvalidOid) - oldNspOid = dep_oldNspOid; - - /* * If not all the objects had the same old namespace (ignoring any * that are not in namespaces), complain. */ diff -Nru postgresql-13-13.11/src/backend/commands/indexcmds.c postgresql-13-13.12/src/backend/commands/indexcmds.c --- postgresql-13-13.11/src/backend/commands/indexcmds.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/indexcmds.c 2023-08-07 20:11:34.000000000 +0000 @@ -1342,6 +1342,7 @@ IndexStmt *childStmt = copyObject(stmt); bool found_whole_row; ListCell *lc; + ObjectAddress childAddr; /* * We can't use the same index name for the child index, @@ -1395,14 +1396,24 @@ Assert(GetUserId() == child_save_userid); SetUserIdAndSecContext(root_save_userid, root_save_sec_context); - DefineIndex(childRelid, childStmt, - InvalidOid, /* no predefined OID */ - indexRelationId, /* this is our child */ - createdConstraintId, - is_alter_table, check_rights, check_not_in_use, - skip_build, quiet); + childAddr = + DefineIndex(childRelid, childStmt, + InvalidOid, /* no predefined OID */ + indexRelationId, /* this is our child */ + createdConstraintId, + is_alter_table, check_rights, + check_not_in_use, + skip_build, quiet); SetUserIdAndSecContext(child_save_userid, child_save_sec_context); + + /* + * Check if the index just created is valid or not, as it + * could be possible that it has been switched as invalid + * when recursing across multiple partition levels. + */ + if (!get_index_isvalid(childAddr.objectId)) + invalidate_parent = true; } pgstat_progress_update_param(PROGRESS_CREATEIDX_PARTITIONS_DONE, @@ -1434,6 +1445,12 @@ ReleaseSysCache(tup); table_close(pg_index, RowExclusiveLock); heap_freetuple(newtup); + + /* + * CCI here to make this update visible, in case this recurses + * across multiple partition levels. + */ + CommandCounterIncrement(); } } diff -Nru postgresql-13-13.11/src/backend/commands/subscriptioncmds.c postgresql-13-13.12/src/backend/commands/subscriptioncmds.c --- postgresql-13-13.11/src/backend/commands/subscriptioncmds.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/subscriptioncmds.c 2023-08-07 20:11:34.000000000 +0000 @@ -992,7 +992,8 @@ "drop the replication slot \"%s\"", slotname), errdetail("The error was: %s", err), /* translator: %s is an SQL ALTER command */ - errhint("Use %s to disassociate the subscription from the slot.", + errhint("Use %s to disable the subscription, and then use %s to disassociate it from the slot.", + "ALTER SUBSCRIPTION ... DISABLE", "ALTER SUBSCRIPTION ... SET (slot_name = NONE)"))); PG_TRY(); diff -Nru postgresql-13-13.11/src/backend/commands/tablecmds.c postgresql-13-13.12/src/backend/commands/tablecmds.c --- postgresql-13-13.11/src/backend/commands/tablecmds.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/tablecmds.c 2023-08-07 20:11:34.000000000 +0000 @@ -17080,8 +17080,8 @@ /* * Scan the list of existing indexes in the partition-to-be, and mark - * the first matching, unattached one we find, if any, as partition of - * the parent index. If we find one, we're done. + * the first matching, valid, unattached one we find, if any, as + * partition of the parent index. If we find one, we're done. */ for (i = 0; i < list_length(attachRelIdxs); i++) { @@ -17092,6 +17092,10 @@ if (attachrelIdxRels[i]->rd_rel->relispartition) continue; + /* If this index is invalid, can't use it */ + if (!attachrelIdxRels[i]->rd_index->indisvalid) + continue; + if (CompareIndexInfo(attachInfos[i], info, attachrelIdxRels[i]->rd_indcollation, idxRel->rd_indcollation, @@ -17880,17 +17884,24 @@ if (tuples == RelationGetPartitionDesc(partedTbl)->nparts) { Relation idxRel; - HeapTuple newtup; + HeapTuple indTup; + Form_pg_index indexForm; idxRel = table_open(IndexRelationId, RowExclusiveLock); + indTup = SearchSysCacheCopy1(INDEXRELID, + ObjectIdGetDatum(RelationGetRelid(partedIdx))); + if (!HeapTupleIsValid(indTup)) + elog(ERROR, "cache lookup failed for index %u", + RelationGetRelid(partedIdx)); + indexForm = (Form_pg_index) GETSTRUCT(indTup); - newtup = heap_copytuple(partedIdx->rd_indextuple); - ((Form_pg_index) GETSTRUCT(newtup))->indisvalid = true; + indexForm->indisvalid = true; updated = true; - CatalogTupleUpdate(idxRel, &partedIdx->rd_indextuple->t_self, newtup); + CatalogTupleUpdate(idxRel, &indTup->t_self, indTup); table_close(idxRel, RowExclusiveLock); + heap_freetuple(indTup); } /* diff -Nru postgresql-13-13.11/src/backend/commands/trigger.c postgresql-13-13.12/src/backend/commands/trigger.c --- postgresql-13-13.11/src/backend/commands/trigger.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/trigger.c 2023-08-07 20:11:34.000000000 +0000 @@ -3610,6 +3610,37 @@ return ((evtshared->ats_event & AFTER_TRIGGER_INITDEFERRED) != 0); } +/* ---------- + * afterTriggerCopyBitmap() + * + * Copy bitmap into AfterTriggerEvents memory context, which is where the after + * trigger events are kept. + * ---------- + */ +static Bitmapset * +afterTriggerCopyBitmap(Bitmapset *src) +{ + Bitmapset *dst; + MemoryContext oldcxt; + + if (src == NULL) + return NULL; + + /* Create event context if we didn't already */ + if (afterTriggers.event_cxt == NULL) + afterTriggers.event_cxt = + AllocSetContextCreate(TopTransactionContext, + "AfterTriggerEvents", + ALLOCSET_DEFAULT_SIZES); + + oldcxt = MemoryContextSwitchTo(afterTriggers.event_cxt); + + dst = bms_copy(src); + + MemoryContextSwitchTo(oldcxt); + + return dst; +} /* ---------- * afterTriggerAddEvent() @@ -5726,7 +5757,7 @@ new_shared.ats_table = transition_capture->tcs_private; else new_shared.ats_table = NULL; - new_shared.ats_modifiedcols = modifiedCols; + new_shared.ats_modifiedcols = afterTriggerCopyBitmap(modifiedCols); afterTriggerAddEvent(&afterTriggers.query_stack[afterTriggers.query_depth].events, &new_event, &new_shared); diff -Nru postgresql-13-13.11/src/backend/commands/vacuum.c postgresql-13-13.12/src/backend/commands/vacuum.c --- postgresql-13-13.11/src/backend/commands/vacuum.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/commands/vacuum.c 2023-08-07 20:11:34.000000000 +0000 @@ -1597,6 +1597,20 @@ Assert(MultiXactIdIsValid(datminmxid)); /* + * If database is in the process of getting dropped, or has been + * interrupted while doing so, no connections to it are possible + * anymore. Therefore we don't need to take it into account here. + * Which is good, because it can't be processed by autovacuum either. + */ + if (database_is_invalid_form((Form_pg_database) dbform)) + { + elog(DEBUG2, + "skipping invalid database \"%s\" while computing relfrozenxid", + NameStr(dbform->datname)); + continue; + } + + /* * If things are working properly, no database should have a * datfrozenxid or datminmxid that is "in the future". However, such * cases have been known to arise due to bugs in pg_upgrade. If we @@ -1639,12 +1653,16 @@ ereport(WARNING, (errmsg("some databases have not been vacuumed in over 2 billion transactions"), errdetail("You might have already suffered transaction-wraparound data loss."))); + LWLockRelease(WrapLimitsVacuumLock); return; } /* chicken out if data is bogus in any other way */ if (bogus) + { + LWLockRelease(WrapLimitsVacuumLock); return; + } /* * Advance the oldest value for commit timestamps before truncating, so diff -Nru postgresql-13-13.11/src/backend/executor/execExprInterp.c postgresql-13-13.12/src/backend/executor/execExprInterp.c --- postgresql-13-13.11/src/backend/executor/execExprInterp.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/executor/execExprInterp.c 2023-08-07 20:11:34.000000000 +0000 @@ -1952,7 +1952,8 @@ * changed: if not NULL, *changed is set to true on any update * * The returned TupleDesc is not guaranteed pinned; caller must pin it - * to use it across any operation that might incur cache invalidation. + * to use it across any operation that might incur cache invalidation, + * including for example detoasting of input tuples. * (The TupleDesc is always refcounted, so just use IncrTupleDescRefCount.) * * NOTE: because composite types can change contents, we must be prepared @@ -3111,17 +3112,6 @@ void ExecEvalFieldStoreDeForm(ExprState *state, ExprEvalStep *op, ExprContext *econtext) { - TupleDesc tupDesc; - - /* Lookup tupdesc if first time through or if type changes */ - tupDesc = get_cached_rowtype(op->d.fieldstore.fstore->resulttype, -1, - op->d.fieldstore.rowcache, NULL); - - /* Check that current tupdesc doesn't have more fields than we allocated */ - if (unlikely(tupDesc->natts > op->d.fieldstore.ncolumns)) - elog(ERROR, "too many columns in composite type %u", - op->d.fieldstore.fstore->resulttype); - if (*op->resnull) { /* Convert null input tuple into an all-nulls row */ @@ -3137,6 +3127,7 @@ Datum tupDatum = *op->resvalue; HeapTupleHeader tuphdr; HeapTupleData tmptup; + TupleDesc tupDesc; tuphdr = DatumGetHeapTupleHeader(tupDatum); tmptup.t_len = HeapTupleHeaderGetDatumLength(tuphdr); @@ -3144,6 +3135,20 @@ tmptup.t_tableOid = InvalidOid; tmptup.t_data = tuphdr; + /* + * Lookup tupdesc if first time through or if type changes. Because + * we don't pin the tupdesc, we must not do this lookup until after + * doing DatumGetHeapTupleHeader: that could do database access while + * detoasting the datum. + */ + tupDesc = get_cached_rowtype(op->d.fieldstore.fstore->resulttype, -1, + op->d.fieldstore.rowcache, NULL); + + /* Check that current tupdesc doesn't have more fields than allocated */ + if (unlikely(tupDesc->natts > op->d.fieldstore.ncolumns)) + elog(ERROR, "too many columns in composite type %u", + op->d.fieldstore.fstore->resulttype); + heap_deform_tuple(&tmptup, tupDesc, op->d.fieldstore.values, op->d.fieldstore.nulls); diff -Nru postgresql-13-13.11/src/backend/executor/execUtils.c postgresql-13-13.12/src/backend/executor/execUtils.c --- postgresql-13-13.11/src/backend/executor/execUtils.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/executor/execUtils.c 2023-08-07 20:11:34.000000000 +0000 @@ -1301,10 +1301,25 @@ return NULL; } -/* Return columns being updated, including generated columns */ +/* + * Return columns being updated, including generated columns + * + * The bitmap is allocated in per-tuple memory context. It's up to the caller to + * copy it into a different context with the appropriate lifespan, if needed. + */ Bitmapset * ExecGetAllUpdatedCols(ResultRelInfo *relinfo, EState *estate) { - return bms_union(ExecGetUpdatedCols(relinfo, estate), - ExecGetExtraUpdatedCols(relinfo, estate)); + + Bitmapset *ret; + MemoryContext oldcxt; + + oldcxt = MemoryContextSwitchTo(GetPerTupleMemoryContext(estate)); + + ret = bms_union(ExecGetUpdatedCols(relinfo, estate), + ExecGetExtraUpdatedCols(relinfo, estate)); + + MemoryContextSwitchTo(oldcxt); + + return ret; } diff -Nru postgresql-13-13.11/src/backend/executor/nodeIncrementalSort.c postgresql-13-13.12/src/backend/executor/nodeIncrementalSort.c --- postgresql-13-13.11/src/backend/executor/nodeIncrementalSort.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/executor/nodeIncrementalSort.c 2023-08-07 20:11:34.000000000 +0000 @@ -1138,7 +1138,6 @@ node->outerNodeDone = false; node->n_fullsort_remaining = 0; node->bound_Done = 0; - node->presorted_keys = NULL; node->execution_status = INCSORT_LOADFULLSORT; @@ -1151,15 +1150,9 @@ * cause a leak. */ if (node->fullsort_state != NULL) - { tuplesort_reset(node->fullsort_state); - node->fullsort_state = NULL; - } if (node->prefixsort_state != NULL) - { tuplesort_reset(node->prefixsort_state); - node->prefixsort_state = NULL; - } /* * If chgParam of subnode is not null, theni the plan will be re-scanned diff -Nru postgresql-13-13.11/src/backend/jit/llvm/llvmjit.c postgresql-13-13.12/src/backend/jit/llvm/llvmjit.c --- postgresql-13-13.11/src/backend/jit/llvm/llvmjit.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/jit/llvm/llvmjit.c 2023-08-07 20:11:34.000000000 +0000 @@ -221,6 +221,8 @@ } list_free(llvm_context->handles); llvm_context->handles = NIL; + + llvm_leave_fatal_on_oom(); } /* diff -Nru postgresql-13-13.11/src/backend/libpq/hba.c postgresql-13-13.12/src/backend/libpq/hba.c --- postgresql-13-13.11/src/backend/libpq/hba.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/libpq/hba.c 2023-08-07 20:11:34.000000000 +0000 @@ -53,8 +53,8 @@ #endif -#define MAX_TOKEN 256 -#define MAX_LINE 8192 +#define MAX_TOKEN 10240 +#define MAX_LINE 20480 /* callback data for check_network_callback */ typedef struct check_network_data diff -Nru postgresql-13-13.11/src/backend/optimizer/path/indxpath.c postgresql-13-13.12/src/backend/optimizer/path/indxpath.c --- postgresql-13-13.11/src/backend/optimizer/path/indxpath.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/path/indxpath.c 2023-08-07 20:11:34.000000000 +0000 @@ -3574,10 +3574,13 @@ /* * If the index is not unique, or not immediately enforced, or if it's - * a partial index that doesn't match the query, it's useless here. + * a partial index, it's useless here. We're unable to make use of + * predOK partial unique indexes due to the fact that + * check_index_predicates() also makes use of join predicates to + * determine if the partial index is usable. Here we need proofs that + * hold true before any joins are evaluated. */ - if (!ind->unique || !ind->immediate || - (ind->indpred != NIL && !ind->predOK)) + if (!ind->unique || !ind->immediate || ind->indpred != NIL) continue; /* diff -Nru postgresql-13-13.11/src/backend/optimizer/path/joinpath.c postgresql-13-13.12/src/backend/optimizer/path/joinpath.c --- postgresql-13-13.11/src/backend/optimizer/path/joinpath.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/path/joinpath.c 2023-08-07 20:11:34.000000000 +0000 @@ -22,6 +22,7 @@ #include "optimizer/pathnode.h" #include "optimizer/paths.h" #include "optimizer/planmain.h" +#include "optimizer/restrictinfo.h" /* Hook for plugins to get control in add_paths_to_joinrel() */ set_join_pathlist_hook_type set_join_pathlist_hook = NULL; @@ -124,6 +125,7 @@ { JoinPathExtraData extra; bool mergejoin_allowed = true; + bool consider_join_pushdown = false; ListCell *lc; Relids joinrelids; @@ -308,12 +310,24 @@ jointype, &extra); /* + * createplan.c does not currently support handling of pseudoconstant + * clauses assigned to joins pushed down by extensions; check if the + * restrictlist has such clauses, and if so, disallow pushing down joins. + */ + if ((joinrel->fdwroutine && + joinrel->fdwroutine->GetForeignJoinPaths) || + set_join_pathlist_hook) + consider_join_pushdown = !has_pseudoconstant_clauses(root, + restrictlist); + + /* * 5. If inner and outer relations are foreign tables (or joins) belonging * to the same server and assigned to the same user to check access * permissions as, give the FDW a chance to push down joins. */ if (joinrel->fdwroutine && - joinrel->fdwroutine->GetForeignJoinPaths) + joinrel->fdwroutine->GetForeignJoinPaths && + consider_join_pushdown) joinrel->fdwroutine->GetForeignJoinPaths(root, joinrel, outerrel, innerrel, jointype, &extra); @@ -321,7 +335,8 @@ /* * 6. Finally, give extensions a chance to manipulate the path list. */ - if (set_join_pathlist_hook) + if (set_join_pathlist_hook && + consider_join_pushdown) set_join_pathlist_hook(root, joinrel, outerrel, innerrel, jointype, &extra); } diff -Nru postgresql-13-13.11/src/backend/optimizer/plan/analyzejoins.c postgresql-13-13.12/src/backend/optimizer/plan/analyzejoins.c --- postgresql-13-13.11/src/backend/optimizer/plan/analyzejoins.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/plan/analyzejoins.c 2023-08-07 20:11:34.000000000 +0000 @@ -595,9 +595,9 @@ /* * For a plain relation, we only know how to prove uniqueness by * reference to unique indexes. Make sure there's at least one - * suitable unique index. It must be immediately enforced, and if - * it's a partial index, it must match the query. (Keep these - * conditions in sync with relation_has_unique_index_for!) + * suitable unique index. It must be immediately enforced, and not a + * partial index. (Keep these conditions in sync with + * relation_has_unique_index_for!) */ ListCell *lc; @@ -605,8 +605,7 @@ { IndexOptInfo *ind = (IndexOptInfo *) lfirst(lc); - if (ind->unique && ind->immediate && - (ind->indpred == NIL || ind->predOK)) + if (ind->unique && ind->immediate && ind->indpred == NIL) return true; } } diff -Nru postgresql-13-13.11/src/backend/optimizer/plan/planner.c postgresql-13-13.12/src/backend/optimizer/plan/planner.c --- postgresql-13-13.11/src/backend/optimizer/plan/planner.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/plan/planner.c 2023-08-07 20:11:34.000000000 +0000 @@ -324,11 +324,13 @@ * functions are present in the query tree. * * (Note that we do allow CREATE TABLE AS, SELECT INTO, and CREATE - * MATERIALIZED VIEW to use parallel plans, but as of now, only the leader - * backend writes into a completely new table. In the future, we can - * extend it to allow workers to write into the table. However, to allow - * parallel updates and deletes, we have to solve other problems, - * especially around combo CIDs.) + * MATERIALIZED VIEW to use parallel plans, but this is safe only because + * the command is writing into a completely new table which workers won't + * be able to see. If the workers could see the table, the fact that + * group locking would cause them to ignore the leader's heavyweight + * GIN page locks would make this unsafe. We'll have to fix that somehow + * if we want to allow parallel inserts in general; updates and deletes + * have additional problems especially around combo CIDs.) * * For now, we don't try to use parallel mode if we're running inside a * parallel worker. We might eventually be able to relax this diff -Nru postgresql-13-13.11/src/backend/optimizer/plan/subselect.c postgresql-13-13.12/src/backend/optimizer/plan/subselect.c --- postgresql-13-13.11/src/backend/optimizer/plan/subselect.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/plan/subselect.c 2023-08-07 20:11:34.000000000 +0000 @@ -2632,6 +2632,11 @@ &context); break; + case T_Hash: + finalize_primnode((Node *) ((Hash *) plan)->hashkeys, + &context); + break; + case T_Limit: finalize_primnode(((Limit *) plan)->limitOffset, &context); @@ -2727,7 +2732,6 @@ break; case T_ProjectSet: - case T_Hash: case T_Material: case T_Sort: case T_IncrementalSort: diff -Nru postgresql-13-13.11/src/backend/optimizer/util/restrictinfo.c postgresql-13-13.12/src/backend/optimizer/util/restrictinfo.c --- postgresql-13-13.11/src/backend/optimizer/util/restrictinfo.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/optimizer/util/restrictinfo.c 2023-08-07 20:11:34.000000000 +0000 @@ -509,6 +509,35 @@ } } +/* + * has_pseudoconstant_clauses + * + * Returns true if 'restrictinfo_list' includes pseudoconstant clauses. + * + * This is used when we determine whether to allow extensions to consider + * pushing down joins in add_paths_to_joinrel(). + */ +bool +has_pseudoconstant_clauses(PlannerInfo *root, + List *restrictinfo_list) +{ + ListCell *l; + + /* No need to look if we know there are no pseudoconstants */ + if (!root->hasPseudoConstantQuals) + return false; + + /* See if there are pseudoconstants in the RestrictInfo list */ + foreach(l, restrictinfo_list) + { + RestrictInfo *rinfo = lfirst_node(RestrictInfo, l); + + if (rinfo->pseudoconstant) + return true; + } + return false; +} + /* * join_clause_is_movable_to diff -Nru postgresql-13-13.11/src/backend/po/de.po postgresql-13-13.12/src/backend/po/de.po --- postgresql-13-13.11/src/backend/po/de.po 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/po/de.po 2023-08-07 20:11:34.000000000 +0000 @@ -7,7 +7,7 @@ msgstr "" "Project-Id-Version: PostgreSQL 13\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2023-05-05 06:57+0000\n" +"POT-Creation-Date: 2023-08-03 09:24+0000\n" "PO-Revision-Date: 2021-11-06 10:46+0100\n" "Last-Translator: Peter Eisentraut \n" "Language-Team: German \n" @@ -25,7 +25,7 @@ msgstr "nicht aufgezeichnet" #: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 -#: commands/copy.c:3499 commands/extension.c:3444 utils/adt/genfile.c:125 +#: commands/copy.c:3499 commands/extension.c:3441 utils/adt/genfile.c:125 #, c-format msgid "could not open file \"%s\" for reading: %m" msgstr "konnte Datei »%s« nicht zum Lesen öffnen: %m" @@ -33,11 +33,11 @@ #: ../common/controldata_utils.c:86 ../common/controldata_utils.c:89 #: access/transam/timeline.c:143 access/transam/timeline.c:362 #: access/transam/twophase.c:1334 access/transam/xlog.c:3528 -#: access/transam/xlog.c:4772 access/transam/xlog.c:11414 -#: access/transam/xlog.c:11427 access/transam/xlog.c:11882 -#: access/transam/xlog.c:11962 access/transam/xlog.c:12001 -#: access/transam/xlog.c:12044 access/transam/xlogfuncs.c:662 -#: access/transam/xlogfuncs.c:681 commands/extension.c:3454 libpq/hba.c:499 +#: access/transam/xlog.c:4772 access/transam/xlog.c:11418 +#: access/transam/xlog.c:11431 access/transam/xlog.c:11886 +#: access/transam/xlog.c:11966 access/transam/xlog.c:12005 +#: access/transam/xlog.c:12048 access/transam/xlogfuncs.c:662 +#: access/transam/xlogfuncs.c:681 commands/extension.c:3451 libpq/hba.c:499 #: replication/logical/origin.c:717 replication/logical/origin.c:753 #: replication/logical/reorderbuffer.c:3661 #: replication/logical/snapbuild.c:1862 replication/logical/snapbuild.c:1904 @@ -118,7 +118,7 @@ #: replication/slot.c:1688 replication/walsender.c:521 #: replication/walsender.c:2552 storage/file/copydir.c:161 #: storage/file/fd.c:679 storage/file/fd.c:3432 storage/file/fd.c:3519 -#: storage/smgr/md.c:514 utils/cache/relmapper.c:724 +#: storage/smgr/md.c:517 utils/cache/relmapper.c:724 #: utils/cache/relmapper.c:842 utils/error/elog.c:1858 #: utils/init/miscinit.c:1321 utils/init/miscinit.c:1455 #: utils/init/miscinit.c:1532 utils/misc/guc.c:8292 utils/misc/guc.c:8324 @@ -128,8 +128,8 @@ #: ../common/controldata_utils.c:221 ../common/controldata_utils.c:224 #: access/transam/twophase.c:1730 access/transam/twophase.c:1739 -#: access/transam/xlog.c:11171 access/transam/xlog.c:11209 -#: access/transam/xlog.c:11622 access/transam/xlogfuncs.c:741 +#: access/transam/xlog.c:11175 access/transam/xlog.c:11213 +#: access/transam/xlog.c:11626 access/transam/xlogfuncs.c:741 #: postmaster/syslogger.c:1499 postmaster/syslogger.c:1512 #: utils/cache/relmapper.c:876 #, c-format @@ -142,10 +142,10 @@ #: access/heap/rewriteheap.c:1275 access/transam/timeline.c:432 #: access/transam/timeline.c:510 access/transam/twophase.c:1751 #: access/transam/xlog.c:3390 access/transam/xlog.c:3562 -#: access/transam/xlog.c:4735 access/transam/xlog.c:10659 -#: access/transam/xlog.c:10686 replication/logical/snapbuild.c:1764 +#: access/transam/xlog.c:4735 access/transam/xlog.c:10663 +#: access/transam/xlog.c:10690 replication/logical/snapbuild.c:1764 #: replication/slot.c:1593 replication/slot.c:1698 storage/file/fd.c:696 -#: storage/file/fd.c:3540 storage/smgr/md.c:960 storage/smgr/md.c:1001 +#: storage/file/fd.c:3540 storage/smgr/md.c:963 storage/smgr/md.c:1004 #: storage/sync/sync.c:433 utils/cache/relmapper.c:891 utils/misc/guc.c:8075 #, c-format msgid "could not fsync file \"%s\": %m" @@ -176,7 +176,7 @@ msgid "could not change directory to \"%s\": %m" msgstr "konnte nicht in Verzeichnis »%s« wechseln: %m" -#: ../common/exec.c:300 access/transam/xlog.c:11043 +#: ../common/exec.c:300 access/transam/xlog.c:11047 #: replication/basebackup.c:1424 utils/adt/misc.c:366 #, c-format msgid "could not read symbolic link \"%s\": %m" @@ -198,9 +198,9 @@ #: replication/libpqwalreceiver/libpqwalreceiver.c:286 #: replication/logical/logical.c:176 replication/walsender.c:595 #: storage/buffer/localbuf.c:442 storage/file/fd.c:854 storage/file/fd.c:1324 -#: storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1079 -#: storage/ipc/procarray.c:1580 storage/ipc/procarray.c:1587 -#: storage/ipc/procarray.c:2024 storage/ipc/procarray.c:2702 +#: storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1080 +#: storage/ipc/procarray.c:1581 storage/ipc/procarray.c:1588 +#: storage/ipc/procarray.c:2025 storage/ipc/procarray.c:2703 #: utils/adt/cryptohashes.c:45 utils/adt/cryptohashes.c:65 #: utils/adt/formatting.c:1700 utils/adt/formatting.c:1824 #: utils/adt/formatting.c:1949 utils/adt/pg_locale.c:484 @@ -209,8 +209,8 @@ #: utils/hash/dynahash.c:1071 utils/mb/mbutils.c:401 utils/mb/mbutils.c:428 #: utils/mb/mbutils.c:757 utils/mb/mbutils.c:783 utils/misc/guc.c:4858 #: utils/misc/guc.c:4874 utils/misc/guc.c:4887 utils/misc/guc.c:8053 -#: utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:701 -#: utils/mmgr/dsa.c:723 utils/mmgr/dsa.c:804 utils/mmgr/generation.c:233 +#: utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:702 +#: utils/mmgr/dsa.c:724 utils/mmgr/dsa.c:805 utils/mmgr/generation.c:233 #: utils/mmgr/mcxt.c:821 utils/mmgr/mcxt.c:857 utils/mmgr/mcxt.c:895 #: utils/mmgr/mcxt.c:933 utils/mmgr/mcxt.c:969 utils/mmgr/mcxt.c:1000 #: utils/mmgr/mcxt.c:1036 utils/mmgr/mcxt.c:1088 utils/mmgr/mcxt.c:1123 @@ -234,11 +234,11 @@ msgstr "kann NULL-Zeiger nicht kopieren (interner Fehler)\n" #: ../common/file_utils.c:79 ../common/file_utils.c:181 -#: access/transam/twophase.c:1302 access/transam/xlog.c:8100 -#: access/transam/xlog.c:11030 access/transam/xlog.c:11147 -#: access/transam/xlog.c:11185 access/transam/xlog.c:11402 +#: access/transam/twophase.c:1302 access/transam/xlog.c:8104 +#: access/transam/xlog.c:11034 access/transam/xlog.c:11151 +#: access/transam/xlog.c:11189 access/transam/xlog.c:11406 #: access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 -#: commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3433 +#: commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3430 #: commands/tablespace.c:806 commands/tablespace.c:897 guc-file.l:1063 #: replication/basebackup.c:444 replication/basebackup.c:627 #: replication/basebackup.c:700 replication/logical/snapbuild.c:1640 @@ -578,13 +578,13 @@ msgid "could not check access token membership: error code %lu\n" msgstr "konnte Access-Token-Mitgliedschaft nicht prüfen: Fehlercode %lu\n" -#: access/brin/brin.c:210 +#: access/brin/brin.c:211 #, c-format msgid "request for BRIN range summarization for index \"%s\" page %u was not recorded" msgstr "Aufforderung für BRIN-Range-Summarization für Index »%s« Seite %u wurde nicht aufgezeichnet" -#: access/brin/brin.c:876 access/brin/brin.c:980 access/gin/ginfast.c:1038 -#: access/transam/xlog.c:10795 access/transam/xlog.c:11353 +#: access/brin/brin.c:962 access/brin/brin.c:1066 access/gin/ginfast.c:1043 +#: access/transam/xlog.c:10799 access/transam/xlog.c:11357 #: access/transam/xlogfuncs.c:274 access/transam/xlogfuncs.c:301 #: access/transam/xlogfuncs.c:340 access/transam/xlogfuncs.c:361 #: access/transam/xlogfuncs.c:382 access/transam/xlogfuncs.c:452 @@ -593,22 +593,22 @@ msgid "recovery is in progress" msgstr "Wiederherstellung läuft" -#: access/brin/brin.c:877 access/brin/brin.c:981 +#: access/brin/brin.c:963 access/brin/brin.c:1067 #, c-format msgid "BRIN control functions cannot be executed during recovery." msgstr "Während der Wiederherstellung können keine BRIN-Kontrollfunktionen ausgeführt werden." -#: access/brin/brin.c:885 access/brin/brin.c:989 +#: access/brin/brin.c:971 access/brin/brin.c:1075 #, c-format msgid "block number out of range: %s" msgstr "Blocknummer ist außerhalb des gültigen Bereichs: %s" -#: access/brin/brin.c:929 access/brin/brin.c:1015 +#: access/brin/brin.c:1015 access/brin/brin.c:1101 #, c-format msgid "\"%s\" is not a BRIN index" msgstr "»%s« ist kein BRIN-Index" -#: access/brin/brin.c:945 access/brin/brin.c:1031 +#: access/brin/brin.c:1031 access/brin/brin.c:1117 #, c-format msgid "could not open parent table of index %s" msgstr "konnte Basistabelle von Index %s nicht öffnen" @@ -824,22 +824,22 @@ msgid "Reduce maintenance_work_mem." msgstr "Reduzieren Sie maintenance_work_mem." -#: access/gin/ginfast.c:1039 +#: access/gin/ginfast.c:1044 #, c-format msgid "GIN pending list cannot be cleaned up during recovery." msgstr "GIN-Pending-Liste kann nicht während der Wiederherstellung aufgeräumt werden." -#: access/gin/ginfast.c:1046 +#: access/gin/ginfast.c:1051 #, c-format msgid "\"%s\" is not a GIN index" msgstr "»%s« ist kein GIN-Index" -#: access/gin/ginfast.c:1057 +#: access/gin/ginfast.c:1062 #, c-format msgid "cannot access temporary indexes of other sessions" msgstr "auf temporäre Indexe anderer Sitzungen kann nicht zugegriffen werden" -#: access/gin/ginget.c:270 access/nbtree/nbtinsert.c:745 +#: access/gin/ginget.c:272 access/nbtree/nbtinsert.c:745 #, c-format msgid "failed to re-find tuple within index \"%s\"" msgstr "konnte Tupel mit Index »%s« nicht erneut finden" @@ -931,7 +931,7 @@ #: access/hash/hashfunc.c:279 access/hash/hashfunc.c:336 catalog/heap.c:709 #: catalog/heap.c:715 commands/createas.c:206 commands/createas.c:501 -#: commands/indexcmds.c:1918 commands/tablecmds.c:16444 commands/view.c:86 +#: commands/indexcmds.c:1935 commands/tablecmds.c:16444 commands/view.c:86 #: parser/parse_utilcmd.c:4252 regex/regc_pg_locale.c:263 #: utils/adt/formatting.c:1667 utils/adt/formatting.c:1791 #: utils/adt/formatting.c:1916 utils/adt/like.c:194 @@ -1036,8 +1036,8 @@ #: access/heap/rewriteheap.c:1012 access/heap/rewriteheap.c:1131 #: access/transam/timeline.c:329 access/transam/timeline.c:485 #: access/transam/xlog.c:3322 access/transam/xlog.c:3497 -#: access/transam/xlog.c:4714 access/transam/xlog.c:11162 -#: access/transam/xlog.c:11200 access/transam/xlog.c:11605 +#: access/transam/xlog.c:4714 access/transam/xlog.c:11166 +#: access/transam/xlog.c:11204 access/transam/xlog.c:11609 #: access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4650 #: replication/logical/origin.c:575 replication/slot.c:1540 #: storage/file/copydir.c:167 storage/smgr/md.c:218 utils/time/snapmgr.c:1358 @@ -1073,7 +1073,7 @@ #: replication/logical/snapbuild.c:1682 replication/logical/snapbuild.c:2127 #: replication/slot.c:1672 storage/file/fd.c:754 storage/file/fd.c:3136 #: storage/file/fd.c:3198 storage/file/reinit.c:255 storage/ipc/dsm.c:302 -#: storage/smgr/md.c:355 storage/smgr/md.c:405 storage/sync/sync.c:229 +#: storage/smgr/md.c:358 storage/smgr/md.c:408 storage/sync/sync.c:229 #: utils/time/snapmgr.c:1703 #, c-format msgid "could not remove file \"%s\": %m" @@ -1180,8 +1180,8 @@ msgstr[0] "%u Seite ist vollkommen leer.\n" msgstr[1] "%u Seiten sind vollkommen leer.\n" -#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3639 -#: commands/indexcmds.c:3657 +#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3656 +#: commands/indexcmds.c:3674 #, c-format msgid "%s." msgstr "%s." @@ -1292,8 +1292,8 @@ msgstr "Indexzugriffsmethode »%s« hat keinen Handler" #: access/index/indexam.c:142 catalog/objectaddress.c:1260 -#: commands/indexcmds.c:2647 commands/tablecmds.c:254 commands/tablecmds.c:278 -#: commands/tablecmds.c:16142 commands/tablecmds.c:17642 +#: commands/indexcmds.c:2664 commands/tablecmds.c:254 commands/tablecmds.c:278 +#: commands/tablecmds.c:16142 commands/tablecmds.c:17646 #, c-format msgid "\"%s\" is not an index" msgstr "»%s« ist kein Index" @@ -1721,12 +1721,12 @@ msgid "transaction identifier \"%s\" is already in use" msgstr "Transaktionsbezeichner »%s« wird bereits verwendet" -#: access/transam/twophase.c:417 access/transam/twophase.c:2450 +#: access/transam/twophase.c:417 access/transam/twophase.c:2483 #, c-format msgid "maximum number of prepared transactions reached" msgstr "maximale Anzahl vorbereiteter Transaktionen erreicht" -#: access/transam/twophase.c:418 access/transam/twophase.c:2451 +#: access/transam/twophase.c:418 access/transam/twophase.c:2484 #, c-format msgid "Increase max_prepared_transactions (currently %d)." msgstr "Erhöhen Sie max_prepared_transactions (aktuell %d)." @@ -1860,6 +1860,22 @@ msgid "corrupted two-phase state in memory for transaction %u" msgstr "verfälschter Zweiphasen-Status im Speicher für Transaktion %u" +#: access/transam/twophase.c:2465 +#, c-format +msgid "could not recover two-phase state file for transaction %u" +msgstr "konnte Zweiphasen-Statusdatei für Transaktion %u nicht wiederherstellen" + +#: access/transam/twophase.c:2467 +#, c-format +msgid "Two-phase state file has been found in WAL record %X/%X, but this transaction has already been restored from disk." +msgstr "Zweiphasen-Statusdatei wurde in WAL-Eintrag %X/%X gefunden, aber diese Transaktion wurde schon von der Festplatte wiederhergestellt." + +#: access/transam/twophase.c:2476 jit/jit.c:205 utils/fmgr/dfmgr.c:209 +#: utils/fmgr/dfmgr.c:417 utils/fmgr/dfmgr.c:465 +#, c-format +msgid "could not access file \"%s\": %m" +msgstr "konnte nicht auf Datei »%s« zugreifen: %m" + #: access/transam/varsup.c:127 #, c-format msgid "database is not accepting commands to avoid wraparound data loss in database \"%s\"" @@ -2060,7 +2076,7 @@ msgid "creating missing WAL directory \"%s\"" msgstr "erzeuge fehlendes WAL-Verzeichnis »%s«" -#: access/transam/xlog.c:4305 commands/dbcommands.c:2208 +#: access/transam/xlog.c:4305 commands/dbcommands.c:2278 #, c-format msgid "could not create missing directory \"%s\": %m" msgstr "konnte fehlendes Verzeichnis »%s« nicht erzeugen: %m" @@ -2470,7 +2486,7 @@ msgid "ignoring file \"%s\" because no file \"%s\" exists" msgstr "ignoriere Datei »%s«, weil keine Datei »%s« existiert" -#: access/transam/xlog.c:6671 access/transam/xlog.c:12123 +#: access/transam/xlog.c:6671 access/transam/xlog.c:12127 #, c-format msgid "File \"%s\" was renamed to \"%s\"." msgstr "Datei »%s« wurde in »%s« umbenannt." @@ -2595,158 +2611,158 @@ msgid "selected new timeline ID: %u" msgstr "gewählte neue Zeitleisten-ID: %u" -#: access/transam/xlog.c:8108 +#: access/transam/xlog.c:8112 #, c-format msgid "unexpected directory entry \"%s\" found in %s" msgstr "unerwarteter Verzeichniseintrag »%s« in %s gefunden" -#: access/transam/xlog.c:8110 +#: access/transam/xlog.c:8114 #, c-format msgid "All directory entries in pg_tblspc/ should be symbolic links." msgstr "Alle Verzeichniseinträge in pg_tblspc/ sollten symbolische Verknüpfungen sein." -#: access/transam/xlog.c:8111 +#: access/transam/xlog.c:8115 #, c-format msgid "Remove those directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete." msgstr "Entfernen Sie diese Verzeichnisse oder setzen Sie allow_in_place_tablespaces vorrübergehend auf ON, damit die Wiederherstellung abschließen kann." -#: access/transam/xlog.c:8195 +#: access/transam/xlog.c:8199 #, c-format msgid "consistent recovery state reached at %X/%X" msgstr "konsistenter Wiederherstellungszustand erreicht bei %X/%X" -#: access/transam/xlog.c:8405 +#: access/transam/xlog.c:8409 #, c-format msgid "invalid primary checkpoint link in control file" msgstr "ungültige primäre Checkpoint-Verknüpfung in Kontrolldatei" -#: access/transam/xlog.c:8409 +#: access/transam/xlog.c:8413 #, c-format msgid "invalid checkpoint link in backup_label file" msgstr "ungültige Checkpoint-Verknüpfung in backup_label-Datei" -#: access/transam/xlog.c:8427 +#: access/transam/xlog.c:8431 #, c-format msgid "invalid primary checkpoint record" msgstr "ungültiger primärer Checkpoint-Datensatz" -#: access/transam/xlog.c:8431 +#: access/transam/xlog.c:8435 #, c-format msgid "invalid checkpoint record" msgstr "ungültiger Checkpoint-Datensatz" -#: access/transam/xlog.c:8442 +#: access/transam/xlog.c:8446 #, c-format msgid "invalid resource manager ID in primary checkpoint record" msgstr "ungültige Resource-Manager-ID im primären Checkpoint-Datensatz" -#: access/transam/xlog.c:8446 +#: access/transam/xlog.c:8450 #, c-format msgid "invalid resource manager ID in checkpoint record" msgstr "ungültige Resource-Manager-ID im Checkpoint-Datensatz" -#: access/transam/xlog.c:8459 +#: access/transam/xlog.c:8463 #, c-format msgid "invalid xl_info in primary checkpoint record" msgstr "ungültige xl_info im primären Checkpoint-Datensatz" -#: access/transam/xlog.c:8463 +#: access/transam/xlog.c:8467 #, c-format msgid "invalid xl_info in checkpoint record" msgstr "ungültige xl_info im Checkpoint-Datensatz" -#: access/transam/xlog.c:8474 +#: access/transam/xlog.c:8478 #, c-format msgid "invalid length of primary checkpoint record" msgstr "ungültige Länge des primären Checkpoint-Datensatzes" -#: access/transam/xlog.c:8478 +#: access/transam/xlog.c:8482 #, c-format msgid "invalid length of checkpoint record" msgstr "ungültige Länge des Checkpoint-Datensatzes" -#: access/transam/xlog.c:8658 +#: access/transam/xlog.c:8662 #, c-format msgid "shutting down" msgstr "fahre herunter" -#: access/transam/xlog.c:8965 +#: access/transam/xlog.c:8969 #, c-format msgid "checkpoint skipped because system is idle" msgstr "Checkpoint übersprungen weil das System inaktiv ist" -#: access/transam/xlog.c:9175 +#: access/transam/xlog.c:9179 #, c-format msgid "concurrent write-ahead log activity while database system is shutting down" msgstr "gleichzeitige Write-Ahead-Log-Aktivität während das Datenbanksystem herunterfährt" -#: access/transam/xlog.c:9487 +#: access/transam/xlog.c:9491 #, c-format msgid "skipping restartpoint, recovery has already ended" msgstr "Restart-Punkt übersprungen, Wiederherstellung ist bereits beendet" -#: access/transam/xlog.c:9510 +#: access/transam/xlog.c:9514 #, c-format msgid "skipping restartpoint, already performed at %X/%X" msgstr "Restart-Punkt wird übersprungen, schon bei %X/%X erledigt" -#: access/transam/xlog.c:9700 +#: access/transam/xlog.c:9704 #, c-format msgid "recovery restart point at %X/%X" msgstr "Recovery-Restart-Punkt bei %X/%X" -#: access/transam/xlog.c:9702 +#: access/transam/xlog.c:9706 #, c-format msgid "Last completed transaction was at log time %s." msgstr "Die letzte vollständige Transaktion war bei Logzeit %s." -#: access/transam/xlog.c:9950 +#: access/transam/xlog.c:9954 #, c-format msgid "restore point \"%s\" created at %X/%X" msgstr "Restore-Punkt »%s« erzeugt bei %X/%X" -#: access/transam/xlog.c:10095 +#: access/transam/xlog.c:10099 #, c-format msgid "unexpected previous timeline ID %u (current timeline ID %u) in checkpoint record" msgstr "unerwartete vorherige Zeitleisten-ID %u (aktuelle Zeitleisten-ID %u) im Checkpoint-Datensatz" -#: access/transam/xlog.c:10104 +#: access/transam/xlog.c:10108 #, c-format msgid "unexpected timeline ID %u (after %u) in checkpoint record" msgstr "unerwartete Zeitleisten-ID %u (nach %u) im Checkpoint-Datensatz" -#: access/transam/xlog.c:10120 +#: access/transam/xlog.c:10124 #, c-format msgid "unexpected timeline ID %u in checkpoint record, before reaching minimum recovery point %X/%X on timeline %u" msgstr "unerwartete Zeitleisten-ID %u in Checkpoint-Datensatz, bevor der minimale Wiederherstellungspunkt %X/%X auf Zeitleiste %u erreicht wurde" -#: access/transam/xlog.c:10196 +#: access/transam/xlog.c:10200 #, c-format msgid "online backup was canceled, recovery cannot continue" msgstr "Online-Sicherung wurde storniert, Wiederherstellung kann nicht fortgesetzt werden" -#: access/transam/xlog.c:10252 access/transam/xlog.c:10308 -#: access/transam/xlog.c:10338 +#: access/transam/xlog.c:10256 access/transam/xlog.c:10312 +#: access/transam/xlog.c:10342 #, c-format msgid "unexpected timeline ID %u (should be %u) in checkpoint record" msgstr "unerwartete Zeitleisten-ID %u (sollte %u sein) im Checkpoint-Datensatz" -#: access/transam/xlog.c:10498 +#: access/transam/xlog.c:10502 #, c-format msgid "successfully skipped missing contrecord at %X/%X, overwritten at %s" msgstr "fehlender Contrecord bei %X/%X erfolgreich übersprungen, überschrieben am %s" -#: access/transam/xlog.c:10691 +#: access/transam/xlog.c:10695 #, c-format msgid "could not fsync write-through file \"%s\": %m" msgstr "konnte Write-Through-Logdatei »%s« nicht fsyncen: %m" -#: access/transam/xlog.c:10697 +#: access/transam/xlog.c:10701 #, c-format msgid "could not fdatasync file \"%s\": %m" msgstr "konnte Datei »%s« nicht fdatasyncen: %m" -#: access/transam/xlog.c:10796 access/transam/xlog.c:11354 +#: access/transam/xlog.c:10800 access/transam/xlog.c:11358 #: access/transam/xlogfuncs.c:275 access/transam/xlogfuncs.c:302 #: access/transam/xlogfuncs.c:341 access/transam/xlogfuncs.c:362 #: access/transam/xlogfuncs.c:383 @@ -2754,201 +2770,201 @@ msgid "WAL control functions cannot be executed during recovery." msgstr "Während der Wiederherstellung können keine WAL-Kontrollfunktionen ausgeführt werden." -#: access/transam/xlog.c:10805 access/transam/xlog.c:11363 +#: access/transam/xlog.c:10809 access/transam/xlog.c:11367 #, c-format msgid "WAL level not sufficient for making an online backup" msgstr "WAL-Level nicht ausreichend, um Online-Sicherung durchzuführen" -#: access/transam/xlog.c:10806 access/transam/xlog.c:11364 +#: access/transam/xlog.c:10810 access/transam/xlog.c:11368 #: access/transam/xlogfuncs.c:308 #, c-format msgid "wal_level must be set to \"replica\" or \"logical\" at server start." msgstr "wal_level muss beim Serverstart auf »replica« oder »logical« gesetzt werden." -#: access/transam/xlog.c:10811 +#: access/transam/xlog.c:10815 #, c-format msgid "backup label too long (max %d bytes)" msgstr "Backup-Label zu lang (maximal %d Bytes)" -#: access/transam/xlog.c:10848 access/transam/xlog.c:11153 -#: access/transam/xlog.c:11191 +#: access/transam/xlog.c:10852 access/transam/xlog.c:11157 +#: access/transam/xlog.c:11195 #, c-format msgid "a backup is already in progress" msgstr "ein Backup läuft bereits" -#: access/transam/xlog.c:10849 +#: access/transam/xlog.c:10853 #, c-format msgid "Run pg_stop_backup() and try again." msgstr "Führen Sie pg_stop_backup() aus und versuchen Sie es nochmal." -#: access/transam/xlog.c:10945 +#: access/transam/xlog.c:10949 #, c-format msgid "WAL generated with full_page_writes=off was replayed since last restartpoint" msgstr "mit full_page_writes=off erzeugtes WAL wurde seit dem letzten Restart-Punkt zurückgespielt" -#: access/transam/xlog.c:10947 access/transam/xlog.c:11559 +#: access/transam/xlog.c:10951 access/transam/xlog.c:11563 #, c-format msgid "This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master, and then try an online backup again." msgstr "Das bedeutet, dass die aktuelle Datensicherung auf dem Standby-Server verfälscht ist und nicht verwendet werden sollte. Schalten Sie full_page_writes ein, führen Sie CHECKPOINT aus und versuchen Sie dann die Online-Sicherung erneut." -#: access/transam/xlog.c:11050 replication/basebackup.c:1429 +#: access/transam/xlog.c:11054 replication/basebackup.c:1429 #: utils/adt/misc.c:371 #, c-format msgid "symbolic link \"%s\" target is too long" msgstr "Ziel für symbolische Verknüpfung »%s« ist zu lang" -#: access/transam/xlog.c:11103 commands/tablespace.c:385 +#: access/transam/xlog.c:11107 commands/tablespace.c:385 #: commands/tablespace.c:561 replication/basebackup.c:1444 utils/adt/misc.c:379 #, c-format msgid "tablespaces are not supported on this platform" msgstr "Tablespaces werden auf dieser Plattform nicht unterstützt" -#: access/transam/xlog.c:11154 access/transam/xlog.c:11192 +#: access/transam/xlog.c:11158 access/transam/xlog.c:11196 #, c-format msgid "If you're sure there is no backup in progress, remove file \"%s\" and try again." msgstr "Wenn Sie sicher sind, dass noch kein Backup läuft, entfernen Sie die Datei »%s« und versuchen Sie es noch einmal." -#: access/transam/xlog.c:11379 +#: access/transam/xlog.c:11383 #, c-format msgid "exclusive backup not in progress" msgstr "es läuft kein exklusives Backup" -#: access/transam/xlog.c:11406 +#: access/transam/xlog.c:11410 #, c-format msgid "a backup is not in progress" msgstr "es läuft kein Backup" -#: access/transam/xlog.c:11492 access/transam/xlog.c:11505 -#: access/transam/xlog.c:11896 access/transam/xlog.c:11902 -#: access/transam/xlog.c:11950 access/transam/xlog.c:12023 +#: access/transam/xlog.c:11496 access/transam/xlog.c:11509 +#: access/transam/xlog.c:11900 access/transam/xlog.c:11906 +#: access/transam/xlog.c:11954 access/transam/xlog.c:12027 #: access/transam/xlogfuncs.c:692 #, c-format msgid "invalid data in file \"%s\"" msgstr "ungültige Daten in Datei »%s«" -#: access/transam/xlog.c:11509 replication/basebackup.c:1277 +#: access/transam/xlog.c:11513 replication/basebackup.c:1277 #, c-format msgid "the standby was promoted during online backup" msgstr "der Standby-Server wurde während der Online-Sicherung zum Primärserver befördert" -#: access/transam/xlog.c:11510 replication/basebackup.c:1278 +#: access/transam/xlog.c:11514 replication/basebackup.c:1278 #, c-format msgid "This means that the backup being taken is corrupt and should not be used. Try taking another online backup." msgstr "Das bedeutet, dass die aktuelle Online-Sicherung verfälscht ist und nicht verwendet werden sollte. Versuchen Sie, eine neue Online-Sicherung durchzuführen." -#: access/transam/xlog.c:11557 +#: access/transam/xlog.c:11561 #, c-format msgid "WAL generated with full_page_writes=off was replayed during online backup" msgstr "mit full_page_writes=off erzeugtes WAL wurde während der Online-Sicherung zurückgespielt" -#: access/transam/xlog.c:11677 +#: access/transam/xlog.c:11681 #, c-format msgid "base backup done, waiting for required WAL segments to be archived" msgstr "Basissicherung beendet, warte bis die benötigten WAL-Segmente archiviert sind" -#: access/transam/xlog.c:11689 +#: access/transam/xlog.c:11693 #, c-format msgid "still waiting for all required WAL segments to be archived (%d seconds elapsed)" msgstr "warte immer noch, bis alle benötigten WAL-Segmente archiviert sind (%d Sekunden abgelaufen)" -#: access/transam/xlog.c:11691 +#: access/transam/xlog.c:11695 #, c-format msgid "Check that your archive_command is executing properly. You can safely cancel this backup, but the database backup will not be usable without all the WAL segments." msgstr "Prüfen Sie, ob das archive_command korrekt ausgeführt wird. Dieser Sicherungsvorgang kann gefahrlos abgebrochen werden, aber die Datenbanksicherung wird ohne die fehlenden WAL-Segmente nicht benutzbar sein." -#: access/transam/xlog.c:11698 +#: access/transam/xlog.c:11702 #, c-format msgid "all required WAL segments have been archived" msgstr "alle benötigten WAL-Segmente wurden archiviert" -#: access/transam/xlog.c:11702 +#: access/transam/xlog.c:11706 #, c-format msgid "WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backup" msgstr "WAL-Archivierung ist nicht eingeschaltet; Sie müssen dafür sorgen, dass alle benötigten WAL-Segmente auf andere Art kopiert werden, um die Sicherung abzuschließen" -#: access/transam/xlog.c:11757 +#: access/transam/xlog.c:11761 #, c-format msgid "aborting backup due to backend exiting before pg_stop_backup was called" msgstr "Backup wird abgebrochen, weil Backend-Prozess beendete, bevor pg_stop_backup aufgerufen wurde" -#: access/transam/xlog.c:11933 +#: access/transam/xlog.c:11937 #, c-format msgid "backup time %s in file \"%s\"" msgstr "Backup-Zeit %s in Datei »%s«" -#: access/transam/xlog.c:11938 +#: access/transam/xlog.c:11942 #, c-format msgid "backup label %s in file \"%s\"" msgstr "Backup-Label %s in Datei »%s«" -#: access/transam/xlog.c:11951 +#: access/transam/xlog.c:11955 #, c-format msgid "Timeline ID parsed is %u, but expected %u." msgstr "Gelesene Zeitleisten-ID ist %u, aber %u wurde erwartet." -#: access/transam/xlog.c:11955 +#: access/transam/xlog.c:11959 #, c-format msgid "backup timeline %u in file \"%s\"" msgstr "Backup-Zeitleiste %u in Datei »%s«" #. translator: %s is a WAL record description -#: access/transam/xlog.c:12063 +#: access/transam/xlog.c:12067 #, c-format msgid "WAL redo at %X/%X for %s" msgstr "WAL-Redo bei %X/%X für %s" -#: access/transam/xlog.c:12112 +#: access/transam/xlog.c:12116 #, c-format msgid "online backup mode was not canceled" msgstr "Online-Sicherungsmodus wurde nicht storniert" -#: access/transam/xlog.c:12113 +#: access/transam/xlog.c:12117 #, c-format msgid "File \"%s\" could not be renamed to \"%s\": %m." msgstr "Konnte Datei »%s« nicht in »%s« umbenennen: %m." -#: access/transam/xlog.c:12122 access/transam/xlog.c:12134 -#: access/transam/xlog.c:12144 +#: access/transam/xlog.c:12126 access/transam/xlog.c:12138 +#: access/transam/xlog.c:12148 #, c-format msgid "online backup mode canceled" msgstr "Online-Sicherungsmodus storniert" -#: access/transam/xlog.c:12135 +#: access/transam/xlog.c:12139 #, c-format msgid "Files \"%s\" and \"%s\" were renamed to \"%s\" and \"%s\", respectively." msgstr "Dateien »%s« und »%s« wurden in »%s« und »%s« umbenannt." -#: access/transam/xlog.c:12145 +#: access/transam/xlog.c:12149 #, c-format msgid "File \"%s\" was renamed to \"%s\", but file \"%s\" could not be renamed to \"%s\": %m." msgstr "Datei »%s« wurde in »%s« umbenannt, aber Datei »%s« konnte nicht in »%s« umbenannt werden: %m." -#: access/transam/xlog.c:12278 access/transam/xlogutils.c:971 +#: access/transam/xlog.c:12282 access/transam/xlogutils.c:971 #, c-format msgid "could not read from log segment %s, offset %u: %m" msgstr "konnte nicht aus Logsegment %s, Position %u lesen: %m" -#: access/transam/xlog.c:12284 access/transam/xlogutils.c:978 +#: access/transam/xlog.c:12288 access/transam/xlogutils.c:978 #, c-format msgid "could not read from log segment %s, offset %u: read %d of %zu" msgstr "konnte nicht aus Logsegment %s bei Position %u lesen: %d von %zu gelesen" -#: access/transam/xlog.c:12827 +#: access/transam/xlog.c:12831 #, c-format msgid "WAL receiver process shutdown requested" msgstr "Herunterfahren des WAL-Receiver-Prozesses verlangt" -#: access/transam/xlog.c:12933 +#: access/transam/xlog.c:12937 #, c-format msgid "received promote request" msgstr "Anforderung zum Befördern empfangen" -#: access/transam/xlog.c:12946 +#: access/transam/xlog.c:12950 #, c-format msgid "promote trigger file found: %s" msgstr "Promote-Triggerdatei gefunden: %s" -#: access/transam/xlog.c:12955 +#: access/transam/xlog.c:12959 #, c-format msgid "could not stat promote trigger file \"%s\": %m" msgstr "konnte »stat« für Promote-Triggerdatei »%s« nicht ausführen: %m" @@ -3393,11 +3409,11 @@ #: commands/dbcommands.c:194 commands/dbcommands.c:203 #: commands/dbcommands.c:212 commands/dbcommands.c:221 #: commands/dbcommands.c:230 commands/dbcommands.c:239 -#: commands/dbcommands.c:261 commands/dbcommands.c:1503 -#: commands/dbcommands.c:1512 commands/dbcommands.c:1521 -#: commands/dbcommands.c:1530 commands/extension.c:1735 +#: commands/dbcommands.c:261 commands/dbcommands.c:1529 +#: commands/dbcommands.c:1538 commands/dbcommands.c:1547 +#: commands/dbcommands.c:1556 commands/extension.c:1735 #: commands/extension.c:1745 commands/extension.c:1755 -#: commands/extension.c:3055 commands/foreigncmds.c:539 +#: commands/extension.c:3052 commands/foreigncmds.c:539 #: commands/foreigncmds.c:548 commands/functioncmds.c:572 #: commands/functioncmds.c:738 commands/functioncmds.c:747 #: commands/functioncmds.c:756 commands/functioncmds.c:765 @@ -3948,7 +3964,7 @@ msgid "publication with OID %u does not exist" msgstr "Publikation mit OID %u existiert nicht" -#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1116 +#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1117 #, c-format msgid "subscription with OID %u does not exist" msgstr "Subskription mit OID %u existiert nicht" @@ -4037,7 +4053,7 @@ #: catalog/dependency.c:1222 commands/tablecmds.c:1259 #: commands/tablecmds.c:13374 commands/tablespace.c:464 commands/user.c:1095 #: commands/view.c:509 libpq/auth.c:334 replication/syncrep.c:1032 -#: storage/lmgr/deadlock.c:1154 storage/lmgr/proc.c:1354 utils/misc/guc.c:6783 +#: storage/lmgr/deadlock.c:1153 storage/lmgr/proc.c:1356 utils/misc/guc.c:6783 #: utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11004 #: utils/misc/guc.c:11038 utils/misc/guc.c:11072 utils/misc/guc.c:11115 #: utils/misc/guc.c:11157 @@ -4121,7 +4137,7 @@ msgid "no collation was derived for column \"%s\" with collatable type %s" msgstr "für Spalte »%s« mit sortierbarem Typ %s wurde keine Sortierfolge abgeleitet" -#: catalog/heap.c:1162 catalog/index.c:866 commands/tablecmds.c:3573 +#: catalog/heap.c:1162 catalog/index.c:867 commands/tablecmds.c:3573 #, c-format msgid "relation \"%s\" already exists" msgstr "Relation »%s« existiert bereits" @@ -4153,7 +4169,7 @@ msgid "check constraint \"%s\" already exists" msgstr "Check-Constraint »%s« existiert bereits" -#: catalog/heap.c:2855 catalog/index.c:880 catalog/pg_constraint.c:668 +#: catalog/heap.c:2855 catalog/index.c:881 catalog/pg_constraint.c:668 #: commands/tablecmds.c:8318 #, c-format msgid "constraint \"%s\" for relation \"%s\" already exists" @@ -4204,14 +4220,14 @@ msgid "generation expression is not immutable" msgstr "Generierungsausdruck ist nicht »immutable«" -#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1236 +#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1238 #, c-format msgid "column \"%s\" is of type %s but default expression is of type %s" msgstr "Spalte »%s« hat Typ %s, aber der Vorgabeausdruck hat Typ %s" #: catalog/heap.c:3088 commands/prepare.c:371 parser/parse_node.c:412 #: parser/parse_target.c:588 parser/parse_target.c:868 -#: parser/parse_target.c:878 rewrite/rewriteHandler.c:1241 +#: parser/parse_target.c:878 rewrite/rewriteHandler.c:1243 #, c-format msgid "You will need to rewrite or cast the expression." msgstr "Sie müssen den Ausdruck umschreiben oder eine Typumwandlung vornehmen." @@ -4246,101 +4262,101 @@ msgid "Truncate table \"%s\" at the same time, or use TRUNCATE ... CASCADE." msgstr "Leeren Sie die Tabelle »%s« gleichzeitig oder verwenden Sie TRUNCATE ... CASCADE." -#: catalog/index.c:220 parser/parse_utilcmd.c:2142 +#: catalog/index.c:221 parser/parse_utilcmd.c:2142 #, c-format msgid "multiple primary keys for table \"%s\" are not allowed" msgstr "mehrere Primärschlüssel für Tabelle »%s« nicht erlaubt" -#: catalog/index.c:238 +#: catalog/index.c:239 #, c-format msgid "primary keys cannot be expressions" msgstr "Primärschlüssel können keine Ausdrücke sein" -#: catalog/index.c:255 +#: catalog/index.c:256 #, c-format msgid "primary key column \"%s\" is not marked NOT NULL" msgstr "Primärschlüsselspalte »%s« ist nicht als NOT NULL markiert" -#: catalog/index.c:765 catalog/index.c:1930 +#: catalog/index.c:766 catalog/index.c:1931 #, c-format msgid "user-defined indexes on system catalog tables are not supported" msgstr "benutzerdefinierte Indexe für Systemkatalogtabellen werden nicht unterstützt" -#: catalog/index.c:805 +#: catalog/index.c:806 #, c-format msgid "nondeterministic collations are not supported for operator class \"%s\"" msgstr "nichtdeterministische Sortierfolgen werden von Operatorklasse »%s« nicht unterstützt" -#: catalog/index.c:820 +#: catalog/index.c:821 #, c-format msgid "concurrent index creation on system catalog tables is not supported" msgstr "nebenläufige Indexerzeugung für Systemkatalogtabellen wird nicht unterstützt" -#: catalog/index.c:829 catalog/index.c:1282 +#: catalog/index.c:830 catalog/index.c:1283 #, c-format msgid "concurrent index creation for exclusion constraints is not supported" msgstr "nebenläufige Indexerzeugung für Exclusion-Constraints wird nicht unterstützt" -#: catalog/index.c:838 +#: catalog/index.c:839 #, c-format msgid "shared indexes cannot be created after initdb" msgstr "Cluster-globale Indexe können nicht nach initdb erzeugt werden" -#: catalog/index.c:858 commands/createas.c:264 commands/sequence.c:162 +#: catalog/index.c:859 commands/createas.c:264 commands/sequence.c:162 #: parser/parse_utilcmd.c:219 #, c-format msgid "relation \"%s\" already exists, skipping" msgstr "Relation »%s« existiert bereits, wird übersprungen" -#: catalog/index.c:908 +#: catalog/index.c:909 #, c-format msgid "pg_class index OID value not set when in binary upgrade mode" msgstr "Index-OID-Wert für pg_class ist im Binary-Upgrade-Modus nicht gesetzt" -#: catalog/index.c:2226 +#: catalog/index.c:2227 #, c-format msgid "DROP INDEX CONCURRENTLY must be first action in transaction" msgstr "DROP INDEX CONCURRENTLY muss die erste Aktion in einer Transaktion sein" -#: catalog/index.c:2957 +#: catalog/index.c:2958 #, c-format msgid "building index \"%s\" on table \"%s\" serially" msgstr "baue Index »%s« von Tabelle »%s« seriell" -#: catalog/index.c:2962 +#: catalog/index.c:2963 #, c-format msgid "building index \"%s\" on table \"%s\" with request for %d parallel worker" msgid_plural "building index \"%s\" on table \"%s\" with request for %d parallel workers" msgstr[0] "baue Index »%s« von Tabelle »%s« mit angefordertem %d parallelen Arbeitsprozess" msgstr[1] "baue Index »%s« von Tabelle »%s« mit angeforderten %d parallelen Arbeitsprozessen" -#: catalog/index.c:3595 +#: catalog/index.c:3597 #, c-format msgid "cannot reindex temporary tables of other sessions" msgstr "kann temporäre Tabellen anderer Sitzungen nicht reindizieren" -#: catalog/index.c:3606 commands/indexcmds.c:3134 +#: catalog/index.c:3608 commands/indexcmds.c:3151 #, c-format msgid "cannot reindex invalid index on TOAST table" msgstr "ungültiger Index einer TOAST-Tabelle kann nicht reindiziert werden" -#: catalog/index.c:3728 +#: catalog/index.c:3730 #, c-format msgid "index \"%s\" was reindexed" msgstr "Index »%s« wurde neu indiziert" -#: catalog/index.c:3810 commands/indexcmds.c:3155 +#: catalog/index.c:3812 commands/indexcmds.c:3172 #, c-format msgid "REINDEX of partitioned tables is not yet implemented, skipping \"%s\"" msgstr "REINDEX von partitionierten Tabellen ist noch nicht implementiert, »%s« wird übersprungen" -#: catalog/index.c:3865 +#: catalog/index.c:3867 #, c-format msgid "cannot reindex invalid index \"%s.%s\" on TOAST table, skipping" msgstr "ungültiger Index »%s.%s« einer TOAST-Tabelle kann nicht reindizert werden, wird übersprungen" #: catalog/namespace.c:258 catalog/namespace.c:462 catalog/namespace.c:554 -#: commands/trigger.c:5122 +#: commands/trigger.c:5153 #, c-format msgid "cross-database references are not implemented: \"%s.%s.%s\"" msgstr "Verweise auf andere Datenbanken sind nicht implementiert: »%s.%s.%s«" @@ -4439,7 +4455,7 @@ msgid "cannot move objects into or out of TOAST schema" msgstr "Objekte können nicht in oder aus TOAST-Schemas verschoben werden" -#: catalog/namespace.c:3053 commands/schemacmds.c:268 commands/schemacmds.c:348 +#: catalog/namespace.c:3053 commands/schemacmds.c:285 commands/schemacmds.c:365 #: commands/tablecmds.c:1204 #, c-format msgid "schema \"%s\" does not exist" @@ -4450,32 +4466,32 @@ msgid "improper relation name (too many dotted names): %s" msgstr "falscher Relationsname (zu viele Namensteile): %s" -#: catalog/namespace.c:3647 +#: catalog/namespace.c:3651 #, c-format msgid "collation \"%s\" for encoding \"%s\" does not exist" msgstr "Sortierfolge »%s« für Kodierung »%s« existiert nicht" -#: catalog/namespace.c:3702 +#: catalog/namespace.c:3706 #, c-format msgid "conversion \"%s\" does not exist" msgstr "Konversion »%s« existiert nicht" -#: catalog/namespace.c:3966 +#: catalog/namespace.c:3970 #, c-format msgid "permission denied to create temporary tables in database \"%s\"" msgstr "keine Berechtigung, um temporäre Tabellen in Datenbank »%s« zu erzeugen" -#: catalog/namespace.c:3982 +#: catalog/namespace.c:3986 #, c-format msgid "cannot create temporary tables during recovery" msgstr "während der Wiederherstellung können keine temporären Tabellen erzeugt werden" -#: catalog/namespace.c:3988 +#: catalog/namespace.c:3992 #, c-format msgid "cannot create temporary tables during a parallel operation" msgstr "während einer parallelen Operation können keine temporären Tabellen erzeugt werden" -#: catalog/namespace.c:4289 commands/tablespace.c:1216 commands/variable.c:64 +#: catalog/namespace.c:4293 commands/tablespace.c:1216 commands/variable.c:64 #: utils/misc/guc.c:11189 utils/misc/guc.c:11267 #, c-format msgid "List syntax is invalid." @@ -5128,12 +5144,12 @@ msgid "default conversion for %s to %s already exists" msgstr "Standardumwandlung von %s nach %s existiert bereits" -#: catalog/pg_depend.c:176 commands/extension.c:3332 +#: catalog/pg_depend.c:176 commands/extension.c:3329 #, c-format msgid "%s is already a member of extension \"%s\"" msgstr "%s ist schon Mitglied der Erweiterung »%s«" -#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3372 +#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3369 #, c-format msgid "%s is not a member of extension \"%s\"" msgstr "%s ist kein Mitglied der Erweiterung »%s«" @@ -5188,7 +5204,7 @@ msgid "ALTER TYPE ADD BEFORE/AFTER is incompatible with binary upgrade" msgstr "ALTER TYPE ADD BEFORE/AFTER ist mit Binary Upgrade inkompatibel" -#: catalog/pg_namespace.c:64 commands/schemacmds.c:277 +#: catalog/pg_namespace.c:64 commands/schemacmds.c:294 #, c-format msgid "schema \"%s\" already exists" msgstr "Schema »%s« existiert bereits" @@ -5450,7 +5466,7 @@ msgstr "kann den Eigentümer von den Objekten, die %s gehören, nicht ändern, weil die Objekte vom Datenbanksystem benötigt werden" #: catalog/pg_subscription.c:171 commands/subscriptioncmds.c:648 -#: commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1084 +#: commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1085 #, c-format msgid "subscription \"%s\" does not exist" msgstr "Subskription »%s« existiert nicht" @@ -5940,11 +5956,11 @@ msgid "no usable system locales were found" msgstr "keine brauchbaren System-Locales gefunden" -#: commands/comment.c:61 commands/dbcommands.c:842 commands/dbcommands.c:1038 -#: commands/dbcommands.c:1151 commands/dbcommands.c:1341 -#: commands/dbcommands.c:1589 commands/dbcommands.c:1703 -#: commands/dbcommands.c:2143 utils/init/postinit.c:877 -#: utils/init/postinit.c:982 utils/init/postinit.c:999 +#: commands/comment.c:61 commands/dbcommands.c:853 commands/dbcommands.c:1064 +#: commands/dbcommands.c:1177 commands/dbcommands.c:1367 +#: commands/dbcommands.c:1615 commands/dbcommands.c:1737 +#: commands/dbcommands.c:2177 utils/init/postinit.c:877 +#: utils/init/postinit.c:983 utils/init/postinit.c:1009 #, c-format msgid "database \"%s\" does not exist" msgstr "Datenbank »%s« existiert nicht" @@ -6076,7 +6092,7 @@ msgid "argument to option \"%s\" must be a valid encoding name" msgstr "Argument von Option »%s« muss ein gültiger Kodierungsname sein" -#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1537 +#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1563 #, c-format msgid "option \"%s\" not recognized" msgstr "Option »%s« nicht erkannt" @@ -6497,7 +6513,7 @@ msgid "Generated columns cannot be used in COPY." msgstr "Generierte Spalten können nicht in COPY verwendet werden." -#: commands/copy.c:5096 commands/indexcmds.c:1789 commands/statscmds.c:228 +#: commands/copy.c:5096 commands/indexcmds.c:1806 commands/statscmds.c:228 #: commands/tablecmds.c:2205 commands/tablecmds.c:2824 #: commands/tablecmds.c:3211 parser/parse_relation.c:3557 #: parser/parse_relation.c:3577 utils/adt/tsvector_op.c:2683 @@ -6546,7 +6562,7 @@ msgid "%s is not a valid encoding name" msgstr "%s ist kein gültiger Kodierungsname" -#: commands/dbcommands.c:315 commands/dbcommands.c:1570 commands/user.c:275 +#: commands/dbcommands.c:315 commands/dbcommands.c:1596 commands/user.c:275 #: commands/user.c:691 #, c-format msgid "invalid connection limit: %d" @@ -6562,212 +6578,228 @@ msgid "template database \"%s\" does not exist" msgstr "Template-Datenbank »%s« existiert nicht" -#: commands/dbcommands.c:369 +#: commands/dbcommands.c:367 +#, c-format +msgid "cannot use invalid database \"%s\" as template" +msgstr "ungültige Datenbank »%s« kann nicht als Template verwendet werden" + +#: commands/dbcommands.c:368 commands/dbcommands.c:1625 +#: utils/init/postinit.c:992 +#, c-format +msgid "Use DROP DATABASE to drop invalid databases." +msgstr "Verwenden Sie DROP DATABASE, um ungültige Datenbanken zu löschen." + +#: commands/dbcommands.c:379 #, c-format msgid "permission denied to copy database \"%s\"" msgstr "keine Berechtigung, um Datenbank »%s« zu kopieren" -#: commands/dbcommands.c:385 +#: commands/dbcommands.c:395 #, c-format msgid "invalid server encoding %d" msgstr "ungültige Serverkodierung %d" -#: commands/dbcommands.c:391 commands/dbcommands.c:396 +#: commands/dbcommands.c:401 commands/dbcommands.c:406 #, c-format msgid "invalid locale name: \"%s\"" msgstr "ungültiger Locale-Name: »%s«" -#: commands/dbcommands.c:416 +#: commands/dbcommands.c:426 #, c-format msgid "new encoding (%s) is incompatible with the encoding of the template database (%s)" msgstr "neue Kodierung (%s) ist inkompatibel mit der Kodierung der Template-Datenbank (%s)" -#: commands/dbcommands.c:419 +#: commands/dbcommands.c:429 #, c-format msgid "Use the same encoding as in the template database, or use template0 as template." msgstr "Verwenden Sie die gleiche Kodierung wie die Template-Datenbank oder verwenden Sie template0 als Template." -#: commands/dbcommands.c:424 +#: commands/dbcommands.c:434 #, c-format msgid "new collation (%s) is incompatible with the collation of the template database (%s)" msgstr "neue Sortierreihenfolge (%s) ist inkompatibel mit der Sortierreihenfolge der Template-Datenbank (%s)" -#: commands/dbcommands.c:426 +#: commands/dbcommands.c:436 #, c-format msgid "Use the same collation as in the template database, or use template0 as template." msgstr "Verwenden Sie die gleiche Sortierreihenfolge wie die Template-Datenbank oder verwenden Sie template0 als Template." -#: commands/dbcommands.c:431 +#: commands/dbcommands.c:441 #, c-format msgid "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)" msgstr "neues LC_CTYPE (%s) ist inkompatibel mit dem LC_CTYPE der Template-Datenbank (%s)" -#: commands/dbcommands.c:433 +#: commands/dbcommands.c:443 #, c-format msgid "Use the same LC_CTYPE as in the template database, or use template0 as template." msgstr "Verwenden Sie das gleiche LC_CTYPE wie die Template-Datenbank oder verwenden Sie template0 als Template." -#: commands/dbcommands.c:455 commands/dbcommands.c:1197 +#: commands/dbcommands.c:465 commands/dbcommands.c:1223 #, c-format msgid "pg_global cannot be used as default tablespace" msgstr "pg_global kann nicht als Standard-Tablespace verwendet werden" -#: commands/dbcommands.c:481 +#: commands/dbcommands.c:491 #, c-format msgid "cannot assign new default tablespace \"%s\"" msgstr "kann neuen Standard-Tablespace »%s« nicht setzen" -#: commands/dbcommands.c:483 +#: commands/dbcommands.c:493 #, c-format msgid "There is a conflict because database \"%s\" already has some tables in this tablespace." msgstr "Es gibt einen Konflikt, weil Datenbank »%s« schon einige Tabellen in diesem Tablespace hat." -#: commands/dbcommands.c:513 commands/dbcommands.c:1067 +#: commands/dbcommands.c:523 commands/dbcommands.c:1093 #, c-format msgid "database \"%s\" already exists" msgstr "Datenbank »%s« existiert bereits" -#: commands/dbcommands.c:527 +#: commands/dbcommands.c:537 #, c-format msgid "source database \"%s\" is being accessed by other users" msgstr "auf Quelldatenbank »%s« wird gerade von anderen Benutzern zugegriffen" -#: commands/dbcommands.c:770 commands/dbcommands.c:785 +#: commands/dbcommands.c:780 commands/dbcommands.c:795 #, c-format msgid "encoding \"%s\" does not match locale \"%s\"" msgstr "Kodierung »%s« stimmt nicht mit Locale »%s« überein" -#: commands/dbcommands.c:773 +#: commands/dbcommands.c:783 #, c-format msgid "The chosen LC_CTYPE setting requires encoding \"%s\"." msgstr "Die gewählte LC_CTYPE-Einstellung verlangt die Kodierung »%s«." -#: commands/dbcommands.c:788 +#: commands/dbcommands.c:798 #, c-format msgid "The chosen LC_COLLATE setting requires encoding \"%s\"." msgstr "Die gewählte LC_COLLATE-Einstellung verlangt die Kodierung »%s«." -#: commands/dbcommands.c:849 +#: commands/dbcommands.c:860 #, c-format msgid "database \"%s\" does not exist, skipping" msgstr "Datenbank »%s« existiert nicht, wird übersprungen" -#: commands/dbcommands.c:873 +#: commands/dbcommands.c:884 #, c-format msgid "cannot drop a template database" msgstr "Template-Datenbank kann nicht gelöscht werden" -#: commands/dbcommands.c:879 +#: commands/dbcommands.c:890 #, c-format msgid "cannot drop the currently open database" msgstr "kann aktuell geöffnete Datenbank nicht löschen" -#: commands/dbcommands.c:892 +#: commands/dbcommands.c:903 #, c-format msgid "database \"%s\" is used by an active logical replication slot" msgstr "Datenbank »%s« wird von einem aktiven logischen Replikations-Slot verwendet" -#: commands/dbcommands.c:894 +#: commands/dbcommands.c:905 #, c-format msgid "There is %d active slot." msgid_plural "There are %d active slots." msgstr[0] "%d Slot ist vorhanden." msgstr[1] "%d Slots sind vorhanden." -#: commands/dbcommands.c:908 +#: commands/dbcommands.c:919 #, c-format msgid "database \"%s\" is being used by logical replication subscription" msgstr "Datenbank »%s« wird von einer Subskription für logische Replikation verwendet" -#: commands/dbcommands.c:910 +#: commands/dbcommands.c:921 #, c-format msgid "There is %d subscription." msgid_plural "There are %d subscriptions." msgstr[0] "%d Subskription ist vorhanden." msgstr[1] "%d Subskriptionen sind vorhanden." -#: commands/dbcommands.c:931 commands/dbcommands.c:1089 -#: commands/dbcommands.c:1219 +#: commands/dbcommands.c:942 commands/dbcommands.c:1115 +#: commands/dbcommands.c:1245 #, c-format msgid "database \"%s\" is being accessed by other users" msgstr "auf Datenbank »%s« wird von anderen Benutzern zugegriffen" -#: commands/dbcommands.c:1049 +#: commands/dbcommands.c:1075 #, c-format msgid "permission denied to rename database" msgstr "keine Berechtigung, um Datenbank umzubenennen" -#: commands/dbcommands.c:1078 +#: commands/dbcommands.c:1104 #, c-format msgid "current database cannot be renamed" msgstr "aktuelle Datenbank kann nicht umbenannt werden" -#: commands/dbcommands.c:1175 +#: commands/dbcommands.c:1201 #, c-format msgid "cannot change the tablespace of the currently open database" msgstr "kann den Tablespace der aktuell geöffneten Datenbank nicht ändern" -#: commands/dbcommands.c:1278 +#: commands/dbcommands.c:1304 #, c-format msgid "some relations of database \"%s\" are already in tablespace \"%s\"" msgstr "einige Relationen von Datenbank »%s« ist bereits in Tablespace »%s«" -#: commands/dbcommands.c:1280 +#: commands/dbcommands.c:1306 #, c-format msgid "You must move them back to the database's default tablespace before using this command." msgstr "Sie müssen sie zurück in den Standard-Tablespace der Datenbank verschieben, bevor Sie diesen Befehl verwenden können." -#: commands/dbcommands.c:1405 commands/dbcommands.c:1981 -#: commands/dbcommands.c:2244 commands/dbcommands.c:2330 +#: commands/dbcommands.c:1431 commands/dbcommands.c:2015 +#: commands/dbcommands.c:2314 commands/dbcommands.c:2400 #, c-format msgid "some useless files may be left behind in old database directory \"%s\"" msgstr "einige nutzlose Dateien wurde möglicherweise im alten Datenbankverzeichnis »%s« zurückgelassen" -#: commands/dbcommands.c:1461 +#: commands/dbcommands.c:1487 #, c-format msgid "unrecognized DROP DATABASE option \"%s\"" msgstr "unbekannte DROP-DATABASE-Option »%s«" -#: commands/dbcommands.c:1551 +#: commands/dbcommands.c:1577 #, c-format msgid "option \"%s\" cannot be specified with other options" msgstr "Option »%s« kann nicht mit anderen Optionen angegeben werden" -#: commands/dbcommands.c:1607 +#: commands/dbcommands.c:1624 +#, c-format +msgid "cannot alter invalid database \"%s\"" +msgstr "ungültige Datenbank »%s« kann nicht geändert werden" + +#: commands/dbcommands.c:1641 #, c-format msgid "cannot disallow connections for current database" msgstr "Verbindungen mit der aktuellen Datenbank können nicht verboten werden" -#: commands/dbcommands.c:1743 +#: commands/dbcommands.c:1777 #, c-format msgid "permission denied to change owner of database" msgstr "keine Berechtigung, um Eigentümer der Datenbank zu ändern" -#: commands/dbcommands.c:2087 +#: commands/dbcommands.c:2121 #, c-format msgid "There are %d other session(s) and %d prepared transaction(s) using the database." msgstr "%d andere Sitzung(en) und %d vorbereitete Transaktion(en) verwenden die Datenbank." -#: commands/dbcommands.c:2090 +#: commands/dbcommands.c:2124 #, c-format msgid "There is %d other session using the database." msgid_plural "There are %d other sessions using the database." msgstr[0] "%d andere Sitzung verwendet die Datenbank." msgstr[1] "%d andere Sitzungen verwenden die Datenbank." -#: commands/dbcommands.c:2095 storage/ipc/procarray.c:3128 +#: commands/dbcommands.c:2129 storage/ipc/procarray.c:3129 #, c-format msgid "There is %d prepared transaction using the database." msgid_plural "There are %d prepared transactions using the database." msgstr[0] "%d vorbereitete Transaktion verwendet die Datenbank." msgstr[1] "%d vorbereitete Transaktionen verwenden die Datenbank." -#: commands/dbcommands.c:2201 +#: commands/dbcommands.c:2271 #, c-format msgid "missing directory \"%s\"" msgstr "Verzeichnis »%s« fehlt" -#: commands/dbcommands.c:2260 commands/tablespace.c:188 +#: commands/dbcommands.c:2330 commands/tablespace.c:188 #: commands/tablespace.c:634 #, c-format msgid "could not stat directory \"%s\": %m" @@ -7055,7 +7087,7 @@ msgid "EXPLAIN option TIMING requires ANALYZE" msgstr "EXPLAIN-Option TIMING erfordert ANALYZE" -#: commands/extension.c:173 commands/extension.c:3013 +#: commands/extension.c:173 commands/extension.c:3010 #, c-format msgid "extension \"%s\" does not exist" msgstr "Erweiterung »%s« existiert nicht" @@ -7188,7 +7220,7 @@ msgid "extension \"%s\" has no update path from version \"%s\" to version \"%s\"" msgstr "Erweiterung »%s« hat keinen Aktualisierungspfad von Version »%s« auf Version »%s«" -#: commands/extension.c:1408 commands/extension.c:3074 +#: commands/extension.c:1408 commands/extension.c:3071 #, c-format msgid "version to install must be specified" msgstr "die zu installierende Version muss angegeben werden" @@ -7263,32 +7295,32 @@ msgid "cannot move extension \"%s\" into schema \"%s\" because the extension contains the schema" msgstr "kann Erweiterung »%s« nicht in Schema »%s« verschieben, weil die Erweiterung das Schema enthält" -#: commands/extension.c:2869 commands/extension.c:2932 +#: commands/extension.c:2869 commands/extension.c:2929 #, c-format msgid "extension \"%s\" does not support SET SCHEMA" msgstr "Erweiterung »%s« unterstützt SET SCHEMA nicht" -#: commands/extension.c:2934 +#: commands/extension.c:2931 #, c-format msgid "%s is not in the extension's schema \"%s\"" msgstr "%s ist nicht im Schema der Erweiterung (»%s«)" -#: commands/extension.c:2993 +#: commands/extension.c:2990 #, c-format msgid "nested ALTER EXTENSION is not supported" msgstr "geschachteltes ALTER EXTENSION wird nicht unterstützt" -#: commands/extension.c:3085 +#: commands/extension.c:3082 #, c-format msgid "version \"%s\" of extension \"%s\" is already installed" msgstr "Version »%s« von Erweiterung »%s« ist bereits installiert" -#: commands/extension.c:3344 +#: commands/extension.c:3341 #, c-format msgid "cannot add schema \"%s\" to extension \"%s\" because the schema contains the extension" msgstr "kann Schema »%s« nicht zu Erweiterung »%s« hinzufügen, weil das Schema die Erweiterung enthält" -#: commands/extension.c:3438 +#: commands/extension.c:3435 #, c-format msgid "file \"%s\" is too large" msgstr "Datei »%s« ist zu groß" @@ -7847,168 +7879,168 @@ msgid "Table \"%s\" contains partitions that are foreign tables." msgstr "Tabelle »%s« enthält Partitionen, die Fremdtabellen sind." -#: commands/indexcmds.c:1706 +#: commands/indexcmds.c:1723 #, c-format msgid "functions in index predicate must be marked IMMUTABLE" msgstr "Funktionen im Indexprädikat müssen als IMMUTABLE markiert sein" -#: commands/indexcmds.c:1784 parser/parse_utilcmd.c:2485 +#: commands/indexcmds.c:1801 parser/parse_utilcmd.c:2485 #: parser/parse_utilcmd.c:2620 #, c-format msgid "column \"%s\" named in key does not exist" msgstr "Spalte »%s«, die im Schlüssel verwendet wird, existiert nicht" -#: commands/indexcmds.c:1808 parser/parse_utilcmd.c:1821 +#: commands/indexcmds.c:1825 parser/parse_utilcmd.c:1821 #, c-format msgid "expressions are not supported in included columns" msgstr "in eingeschlossenen Spalten werden keine Ausdrücke unterstützt" -#: commands/indexcmds.c:1849 +#: commands/indexcmds.c:1866 #, c-format msgid "functions in index expression must be marked IMMUTABLE" msgstr "Funktionen im Indexausdruck müssen als IMMUTABLE markiert sein" -#: commands/indexcmds.c:1864 +#: commands/indexcmds.c:1881 #, c-format msgid "including column does not support a collation" msgstr "inkludierte Spalte unterstützt keine Sortierfolge" -#: commands/indexcmds.c:1868 +#: commands/indexcmds.c:1885 #, c-format msgid "including column does not support an operator class" msgstr "inkludierte Spalte unterstützt keine Operatorklasse" -#: commands/indexcmds.c:1872 +#: commands/indexcmds.c:1889 #, c-format msgid "including column does not support ASC/DESC options" msgstr "inkludierte Spalte unterstützt die Optionen ASC/DESC nicht" -#: commands/indexcmds.c:1876 +#: commands/indexcmds.c:1893 #, c-format msgid "including column does not support NULLS FIRST/LAST options" msgstr "inkludierte Spalte unterstützt die Optionen NULLS FIRST/LAST nicht" -#: commands/indexcmds.c:1917 +#: commands/indexcmds.c:1934 #, c-format msgid "could not determine which collation to use for index expression" msgstr "konnte die für den Indexausdruck zu verwendende Sortierfolge nicht bestimmen" -#: commands/indexcmds.c:1925 commands/tablecmds.c:16451 commands/typecmds.c:771 +#: commands/indexcmds.c:1942 commands/tablecmds.c:16451 commands/typecmds.c:771 #: parser/parse_expr.c:2863 parser/parse_type.c:566 parser/parse_utilcmd.c:3696 #: parser/parse_utilcmd.c:4259 utils/adt/misc.c:532 #, c-format msgid "collations are not supported by type %s" msgstr "Sortierfolgen werden von Typ %s nicht unterstützt" -#: commands/indexcmds.c:1990 +#: commands/indexcmds.c:2007 #, c-format msgid "operator %s is not commutative" msgstr "Operator %s ist nicht kommutativ" -#: commands/indexcmds.c:1992 +#: commands/indexcmds.c:2009 #, c-format msgid "Only commutative operators can be used in exclusion constraints." msgstr "In Exclusion-Constraints können nur kommutative Operatoren verwendet werden." -#: commands/indexcmds.c:2018 +#: commands/indexcmds.c:2035 #, c-format msgid "operator %s is not a member of operator family \"%s\"" msgstr "Operator %s ist kein Mitglied der Operatorfamilie »%s«" -#: commands/indexcmds.c:2021 +#: commands/indexcmds.c:2038 #, c-format msgid "The exclusion operator must be related to the index operator class for the constraint." msgstr "Der Exklusionsoperator muss in Beziehung zur Indexoperatorklasse des Constraints stehen." -#: commands/indexcmds.c:2056 +#: commands/indexcmds.c:2073 #, c-format msgid "access method \"%s\" does not support ASC/DESC options" msgstr "Zugriffsmethode »%s« unterstützt die Optionen ASC/DESC nicht" -#: commands/indexcmds.c:2061 +#: commands/indexcmds.c:2078 #, c-format msgid "access method \"%s\" does not support NULLS FIRST/LAST options" msgstr "Zugriffsmethode »%s« unterstützt die Optionen NULLS FIRST/LAST nicht" -#: commands/indexcmds.c:2107 commands/tablecmds.c:16476 +#: commands/indexcmds.c:2124 commands/tablecmds.c:16476 #: commands/tablecmds.c:16482 commands/typecmds.c:1947 #, c-format msgid "data type %s has no default operator class for access method \"%s\"" msgstr "Datentyp %s hat keine Standardoperatorklasse für Zugriffsmethode »%s«" -#: commands/indexcmds.c:2109 +#: commands/indexcmds.c:2126 #, c-format msgid "You must specify an operator class for the index or define a default operator class for the data type." msgstr "Sie müssen für den Index eine Operatorklasse angeben oder eine Standardoperatorklasse für den Datentyp definieren." -#: commands/indexcmds.c:2138 commands/indexcmds.c:2146 +#: commands/indexcmds.c:2155 commands/indexcmds.c:2163 #: commands/opclasscmds.c:208 #, c-format msgid "operator class \"%s\" does not exist for access method \"%s\"" msgstr "Operatorklasse »%s« existiert nicht für Zugriffsmethode »%s«" -#: commands/indexcmds.c:2160 commands/typecmds.c:1935 +#: commands/indexcmds.c:2177 commands/typecmds.c:1935 #, c-format msgid "operator class \"%s\" does not accept data type %s" msgstr "Operatorklasse »%s« akzeptiert Datentyp %s nicht" -#: commands/indexcmds.c:2250 +#: commands/indexcmds.c:2267 #, c-format msgid "there are multiple default operator classes for data type %s" msgstr "es gibt mehrere Standardoperatorklassen für Datentyp %s" -#: commands/indexcmds.c:2699 +#: commands/indexcmds.c:2716 #, c-format msgid "table \"%s\" has no indexes that can be reindexed concurrently" msgstr "Tabelle »%s« hat keine Indexe, die nebenläufig reindiziert werden können" -#: commands/indexcmds.c:2710 +#: commands/indexcmds.c:2727 #, c-format msgid "table \"%s\" has no indexes to reindex" msgstr "Tabelle »%s« hat keine zu reindizierenden Indexe" -#: commands/indexcmds.c:2749 commands/indexcmds.c:3030 -#: commands/indexcmds.c:3123 +#: commands/indexcmds.c:2766 commands/indexcmds.c:3047 +#: commands/indexcmds.c:3140 #, c-format msgid "cannot reindex system catalogs concurrently" msgstr "Systemkataloge können nicht nebenläufig reindiziert werden" -#: commands/indexcmds.c:2772 +#: commands/indexcmds.c:2789 #, c-format msgid "can only reindex the currently open database" msgstr "nur die aktuell geöffnete Datenbank kann reindiziert werden" -#: commands/indexcmds.c:2863 +#: commands/indexcmds.c:2880 #, c-format msgid "cannot reindex system catalogs concurrently, skipping all" msgstr "Systemkataloge können nicht nebenläufig reindiziert werden, werden alle übersprungen" -#: commands/indexcmds.c:2915 commands/indexcmds.c:3655 +#: commands/indexcmds.c:2932 commands/indexcmds.c:3672 #, c-format msgid "table \"%s.%s\" was reindexed" msgstr "Tabelle »%s.%s« wurde neu indiziert" -#: commands/indexcmds.c:3045 commands/indexcmds.c:3091 +#: commands/indexcmds.c:3062 commands/indexcmds.c:3108 #, c-format msgid "cannot reindex invalid index \"%s.%s\" concurrently, skipping" msgstr "ungültiger Index »%s.%s« kann nicht nebenläufig reindizert werden, wird übersprungen" -#: commands/indexcmds.c:3051 +#: commands/indexcmds.c:3068 #, c-format msgid "cannot reindex exclusion constraint index \"%s.%s\" concurrently, skipping" msgstr "Exclusion-Constraint-Index »%s.%s« kann nicht nebenläufig reindizert werden, wird übersprungen" -#: commands/indexcmds.c:3162 +#: commands/indexcmds.c:3179 #, c-format msgid "cannot reindex this type of relation concurrently" msgstr "diese Art Relation kann nicht nebenläufig reindiziert werden" -#: commands/indexcmds.c:3637 commands/indexcmds.c:3648 +#: commands/indexcmds.c:3654 commands/indexcmds.c:3665 #, c-format msgid "index \"%s.%s\" was reindexed" msgstr "Index »%s.%s« wurde neu indiziert" -#: commands/indexcmds.c:3680 +#: commands/indexcmds.c:3697 #, c-format msgid "REINDEX is not yet implemented for partitioned indexes" msgstr "REINDEX ist für partitionierte Indexe noch nicht implementiert" @@ -8478,17 +8510,17 @@ msgid "The owner of a FOR ALL TABLES publication must be a superuser." msgstr "Der Eigentümer einer FOR-ALL-TABLES-Publikation muss ein Superuser sein." -#: commands/schemacmds.c:105 commands/schemacmds.c:293 +#: commands/schemacmds.c:108 commands/schemacmds.c:310 #, c-format msgid "unacceptable schema name \"%s\"" msgstr "inakzeptabler Schemaname »%s«" -#: commands/schemacmds.c:106 commands/schemacmds.c:294 +#: commands/schemacmds.c:109 commands/schemacmds.c:311 #, c-format msgid "The prefix \"pg_\" is reserved for system schemas." msgstr "Der Präfix »pg_« ist für Systemschemas reserviert." -#: commands/schemacmds.c:130 +#: commands/schemacmds.c:133 #, c-format msgid "schema \"%s\" already exists, skipping" msgstr "Schema »%s« existiert bereits, wird übersprungen" @@ -8795,7 +8827,7 @@ msgid "could not connect to publisher when attempting to drop the replication slot \"%s\"" msgstr "konnte beim Versuch den Replikations-Slot »%s« zu löschen nicht mit dem Publikationsserver verbinden" -#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1008 +#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1009 #: replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 #, c-format msgid "The error was: %s" @@ -8804,30 +8836,30 @@ #. translator: %s is an SQL ALTER command #: commands/subscriptioncmds.c:995 #, c-format -msgid "Use %s to disassociate the subscription from the slot." -msgstr "Verwenden Sie %s, um die Subskription vom Slot zu trennen." +msgid "Use %s to disable the subscription, and then use %s to disassociate it from the slot." +msgstr "Verwenden Sie %s, um die Subskription zu deaktivieren, und dann %s, um sie vom Slot zu trennen." -#: commands/subscriptioncmds.c:1006 +#: commands/subscriptioncmds.c:1007 #, c-format msgid "could not drop the replication slot \"%s\" on publisher" msgstr "konnte Replikations-Slot »%s« auf dem Publikationsserver nicht löschen" -#: commands/subscriptioncmds.c:1011 +#: commands/subscriptioncmds.c:1012 #, c-format msgid "dropped replication slot \"%s\" on publisher" msgstr "Replikations-Slot »%s« auf dem Publikationsserver wurde gelöscht" -#: commands/subscriptioncmds.c:1048 +#: commands/subscriptioncmds.c:1049 #, c-format msgid "permission denied to change owner of subscription \"%s\"" msgstr "keine Berechtigung, um Eigentümer der Subskription »%s« zu ändern" -#: commands/subscriptioncmds.c:1050 +#: commands/subscriptioncmds.c:1051 #, c-format msgid "The owner of a subscription must be a superuser." msgstr "Der Eigentümer einer Subskription muss ein Superuser sein." -#: commands/subscriptioncmds.c:1165 +#: commands/subscriptioncmds.c:1166 #, c-format msgid "could not receive list of replicated tables from the publisher: %s" msgstr "konnte Liste der replizierten Tabellen nicht vom Publikationsserver empfangen: %s" @@ -8888,7 +8920,7 @@ msgid "Use DROP MATERIALIZED VIEW to remove a materialized view." msgstr "Verwenden Sie DROP MATERIALIZED VIEW, um eine materialisierte Sicht zu löschen." -#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17685 +#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17689 #: parser/parse_utilcmd.c:2217 #, c-format msgid "index \"%s\" does not exist" @@ -10130,7 +10162,7 @@ msgstr "generierte Spalte kann nicht im Partitionierungsschlüssel verwendet werden" #: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 -#: rewrite/rewriteHandler.c:873 rewrite/rewriteHandler.c:890 +#: rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 #, c-format msgid "Column \"%s\" is a generated column." msgstr "Spalte »%s« ist eine generierte Spalte." @@ -10246,34 +10278,34 @@ msgid "Table \"%s\" contains unique indexes." msgstr "Tabelle »%s« enthält Unique-Indexe." -#: commands/tablecmds.c:17719 commands/tablecmds.c:17739 -#: commands/tablecmds.c:17759 commands/tablecmds.c:17778 -#: commands/tablecmds.c:17820 +#: commands/tablecmds.c:17723 commands/tablecmds.c:17743 +#: commands/tablecmds.c:17763 commands/tablecmds.c:17782 +#: commands/tablecmds.c:17824 #, c-format msgid "cannot attach index \"%s\" as a partition of index \"%s\"" msgstr "kann Index »%s« nicht als Partition an Index »%s« anfügen" -#: commands/tablecmds.c:17722 +#: commands/tablecmds.c:17726 #, c-format msgid "Index \"%s\" is already attached to another index." msgstr "Index »%s« ist bereits an einen anderen Index angefügt." -#: commands/tablecmds.c:17742 +#: commands/tablecmds.c:17746 #, c-format msgid "Index \"%s\" is not an index on any partition of table \"%s\"." msgstr "Index »%s« ist kein Index irgendeiner Partition von Tabelle »%s«." -#: commands/tablecmds.c:17762 +#: commands/tablecmds.c:17766 #, c-format msgid "The index definitions do not match." msgstr "Die Indexdefinitionen stimmen nicht überein." -#: commands/tablecmds.c:17781 +#: commands/tablecmds.c:17785 #, c-format msgid "The index \"%s\" belongs to a constraint in table \"%s\" but no constraint exists for index \"%s\"." msgstr "Der Index »%s« gehört zu einem Constraint in Tabelle »%s«, aber kein Constraint existiert für Index »%s«." -#: commands/tablecmds.c:17823 +#: commands/tablecmds.c:17827 #, c-format msgid "Another index is already attached for partition \"%s\"." msgstr "Ein anderer Index ist bereits für Partition »%s« angefügt." @@ -10648,17 +10680,17 @@ msgid "could not serialize access due to concurrent delete" msgstr "konnte Zugriff nicht serialisieren wegen gleichzeitigem Löschen" -#: commands/trigger.c:4124 +#: commands/trigger.c:4155 #, c-format msgid "cannot fire deferred trigger within security-restricted operation" msgstr "aufgeschobener Trigger kann nicht in einer sicherheitsbeschränkten Operation ausgelöst werden" -#: commands/trigger.c:5173 +#: commands/trigger.c:5204 #, c-format msgid "constraint \"%s\" is not deferrable" msgstr "Constraint »%s« ist nicht aufschiebbar" -#: commands/trigger.c:5196 +#: commands/trigger.c:5227 #, c-format msgid "constraint \"%s\" does not exist" msgstr "Constraint »%s« existiert nicht" @@ -11372,17 +11404,17 @@ msgid "Close open transactions with multixacts soon to avoid wraparound problems." msgstr "Schließen Sie bald alle offenen Transaktionen mit Multixacts, um Überlaufprobleme zu vermeiden." -#: commands/vacuum.c:1640 +#: commands/vacuum.c:1654 #, c-format msgid "some databases have not been vacuumed in over 2 billion transactions" msgstr "einige Datenbanken sind seit über 2 Milliarden Transaktionen nicht gevacuumt worden" -#: commands/vacuum.c:1641 +#: commands/vacuum.c:1655 #, c-format msgid "You might have already suffered transaction-wraparound data loss." msgstr "Sie haben möglicherweise bereits Daten wegen Transaktionsnummernüberlauf verloren." -#: commands/vacuum.c:1801 +#: commands/vacuum.c:1819 #, c-format msgid "skipping \"%s\" --- cannot vacuum non-tables or special system tables" msgstr "überspringe »%s« --- kann Nicht-Tabellen oder besondere Systemtabellen nicht vacuumen" @@ -11573,12 +11605,12 @@ msgid "cursor \"%s\" is not a simply updatable scan of table \"%s\"" msgstr "Cursor »%s« ist kein einfach aktualisierbarer Scan der Tabelle »%s«" -#: executor/execCurrent.c:280 executor/execExprInterp.c:2434 +#: executor/execCurrent.c:280 executor/execExprInterp.c:2435 #, c-format msgid "type of parameter %d (%s) does not match that when preparing the plan (%s)" msgstr "Typ von Parameter %d (%s) stimmt nicht mit dem überein, als der Plan vorbereitet worden ist (%s)" -#: executor/execCurrent.c:292 executor/execExprInterp.c:2446 +#: executor/execCurrent.c:292 executor/execExprInterp.c:2447 #, c-format msgid "no value found for parameter %d" msgstr "kein Wert für Parameter %d gefunden" @@ -11607,7 +11639,7 @@ msgstr[1] "kann nicht mehr als %d Argumente an eine Funktion übergeben" #: executor/execExpr.c:2690 executor/execExpr.c:2696 -#: executor/execExprInterp.c:2759 utils/adt/arrayfuncs.c:262 +#: executor/execExprInterp.c:2760 utils/adt/arrayfuncs.c:262 #: utils/adt/arrayfuncs.c:562 utils/adt/arrayfuncs.c:1304 #: utils/adt/arrayfuncs.c:3346 utils/adt/arrayfuncs.c:5308 #: utils/adt/arrayfuncs.c:5825 @@ -11625,13 +11657,13 @@ msgid "attribute %d of type %s has wrong type" msgstr "Attribut %d von Typ %s hat falschen Typ" -#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3040 -#: executor/execExprInterp.c:3086 +#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3041 +#: executor/execExprInterp.c:3087 #, c-format msgid "Table has type %s, but query expects %s." msgstr "Tabelle hat Typ %s, aber Anfrage erwartet %s." -#: executor/execExprInterp.c:1986 utils/adt/expandedrecord.c:99 +#: executor/execExprInterp.c:1987 utils/adt/expandedrecord.c:99 #: utils/adt/expandedrecord.c:231 utils/cache/typcache.c:1632 #: utils/cache/typcache.c:1788 utils/cache/typcache.c:1936 #: utils/fmgr/funcapi.c:456 @@ -11639,27 +11671,27 @@ msgid "type %s is not composite" msgstr "Typ %s ist kein zusammengesetzter Typ" -#: executor/execExprInterp.c:2524 +#: executor/execExprInterp.c:2525 #, c-format msgid "WHERE CURRENT OF is not supported for this table type" msgstr "WHERE CURRENT OF wird für diesen Tabellentyp nicht unterstützt" -#: executor/execExprInterp.c:2737 +#: executor/execExprInterp.c:2738 #, c-format msgid "cannot merge incompatible arrays" msgstr "kann inkompatible Arrays nicht verschmelzen" -#: executor/execExprInterp.c:2738 +#: executor/execExprInterp.c:2739 #, c-format msgid "Array with element type %s cannot be included in ARRAY construct with element type %s." msgstr "Arrayelement mit Typ %s kann nicht in ARRAY-Konstrukt mit Elementtyp %s verwendet werden." -#: executor/execExprInterp.c:2779 executor/execExprInterp.c:2814 +#: executor/execExprInterp.c:2780 executor/execExprInterp.c:2815 #, c-format msgid "multidimensional arrays must have array expressions with matching dimensions" msgstr "mehrdimensionale Arrays müssen Arraysausdrücke mit gleicher Anzahl Dimensionen haben" -#: executor/execExprInterp.c:2791 utils/adt/array_expanded.c:274 +#: executor/execExprInterp.c:2792 utils/adt/array_expanded.c:274 #: utils/adt/arrayfuncs.c:935 utils/adt/arrayfuncs.c:1522 #: utils/adt/arrayfuncs.c:3234 utils/adt/arrayfuncs.c:3376 #: utils/adt/arrayfuncs.c:5917 utils/adt/arrayfuncs.c:6258 @@ -11669,47 +11701,47 @@ msgid "array size exceeds the maximum allowed (%d)" msgstr "Arraygröße überschreitet erlaubtes Maximum (%d)" -#: executor/execExprInterp.c:3039 executor/execExprInterp.c:3085 +#: executor/execExprInterp.c:3040 executor/execExprInterp.c:3086 #, c-format msgid "attribute %d has wrong type" msgstr "Attribut %d hat falschen Typ" -#: executor/execExprInterp.c:3199 +#: executor/execExprInterp.c:3204 #, c-format msgid "array subscript in assignment must not be null" msgstr "Arrayindex in Zuweisung darf nicht NULL sein" -#: executor/execExprInterp.c:3626 utils/adt/domains.c:149 +#: executor/execExprInterp.c:3631 utils/adt/domains.c:149 #, c-format msgid "domain %s does not allow null values" msgstr "Domäne %s erlaubt keine NULL-Werte" -#: executor/execExprInterp.c:3641 utils/adt/domains.c:184 +#: executor/execExprInterp.c:3646 utils/adt/domains.c:184 #, c-format msgid "value for domain %s violates check constraint \"%s\"" msgstr "Wert für Domäne %s verletzt Check-Constraint »%s«" -#: executor/execExprInterp.c:4011 executor/execExprInterp.c:4028 -#: executor/execExprInterp.c:4127 executor/nodeModifyTable.c:110 +#: executor/execExprInterp.c:4016 executor/execExprInterp.c:4033 +#: executor/execExprInterp.c:4132 executor/nodeModifyTable.c:110 #: executor/nodeModifyTable.c:121 executor/nodeModifyTable.c:138 #: executor/nodeModifyTable.c:146 #, c-format msgid "table row type and query-specified row type do not match" msgstr "Zeilentyp der Tabelle und der von der Anfrage angegebene Zeilentyp stimmen nicht überein" -#: executor/execExprInterp.c:4012 +#: executor/execExprInterp.c:4017 #, c-format msgid "Table row contains %d attribute, but query expects %d." msgid_plural "Table row contains %d attributes, but query expects %d." msgstr[0] "Tabellenzeile enthält %d Attribut, aber Anfrage erwartet %d." msgstr[1] "Tabellenzeile enthält %d Attribute, aber Anfrage erwartet %d." -#: executor/execExprInterp.c:4029 executor/nodeModifyTable.c:122 +#: executor/execExprInterp.c:4034 executor/nodeModifyTable.c:122 #, c-format msgid "Table has type %s at ordinal position %d, but query expects %s." msgstr "Tabelle hat Typ %s auf Position %d, aber Anfrage erwartet %s." -#: executor/execExprInterp.c:4128 executor/execSRF.c:967 +#: executor/execExprInterp.c:4133 executor/execSRF.c:967 #, c-format msgid "Physical storage mismatch on dropped attribute at ordinal position %d." msgstr "Physischer Speicher stimmt nicht überein mit gelöschtem Attribut auf Position %d." @@ -11759,38 +11791,38 @@ msgid "cannot change TOAST relation \"%s\"" msgstr "kann TOAST-Relation »%s« nicht ändern" -#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3025 -#: rewrite/rewriteHandler.c:3851 +#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3027 +#: rewrite/rewriteHandler.c:3853 #, c-format msgid "cannot insert into view \"%s\"" msgstr "kann nicht in Sicht »%s« einfügen" -#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3028 -#: rewrite/rewriteHandler.c:3854 +#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3030 +#: rewrite/rewriteHandler.c:3856 #, c-format msgid "To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule." msgstr "Um Einfügen in die Sicht zu ermöglichen, richten Sie einen INSTEAD OF INSERT Trigger oder eine ON INSERT DO INSTEAD Regel ohne Bedingung ein." -#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3033 -#: rewrite/rewriteHandler.c:3859 +#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3035 +#: rewrite/rewriteHandler.c:3861 #, c-format msgid "cannot update view \"%s\"" msgstr "kann Sicht »%s« nicht aktualisieren" -#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3036 -#: rewrite/rewriteHandler.c:3862 +#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3038 +#: rewrite/rewriteHandler.c:3864 #, c-format msgid "To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule." msgstr "Um Aktualisieren der Sicht zu ermöglichen, richten Sie einen INSTEAD OF UPDATE Trigger oder eine ON UPDATE DO INSTEAD Regel ohne Bedingung ein." -#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3041 -#: rewrite/rewriteHandler.c:3867 +#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3043 +#: rewrite/rewriteHandler.c:3869 #, c-format msgid "cannot delete from view \"%s\"" msgstr "kann nicht aus Sicht »%s« löschen" -#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3044 -#: rewrite/rewriteHandler.c:3870 +#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3046 +#: rewrite/rewriteHandler.c:3872 #, c-format msgid "To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule." msgstr "Um Löschen aus der Sicht zu ermöglichen, richten Sie einen INSTEAD OF DELETE Trigger oder eine ON DELETE DO INSTEAD Regel ohne Bedingung ein." @@ -12798,13 +12830,7 @@ msgid "could not open configuration directory \"%s\": %m" msgstr "konnte Konfigurationsverzeichnis »%s« nicht öffnen: %m" -#: jit/jit.c:205 utils/fmgr/dfmgr.c:209 utils/fmgr/dfmgr.c:417 -#: utils/fmgr/dfmgr.c:465 -#, c-format -msgid "could not access file \"%s\": %m" -msgstr "konnte nicht auf Datei »%s« zugreifen: %m" - -#: jit/llvm/llvmjit.c:730 +#: jit/llvm/llvmjit.c:732 #, c-format msgid "time to inline: %.3fs, opt: %.3fs, emit: %.3fs" msgstr "Zeit für Inlining: %.3fs, Opt: %.3fs, Ausgabe: %.3fs" @@ -12844,8 +12870,8 @@ msgid "unsupported Unicode escape sequence" msgstr "nicht unterstützte Unicode-Escape-Sequenz" -#: lib/dshash.c:246 utils/mmgr/dsa.c:702 utils/mmgr/dsa.c:724 -#: utils/mmgr/dsa.c:805 +#: lib/dshash.c:246 utils/mmgr/dsa.c:703 utils/mmgr/dsa.c:725 +#: utils/mmgr/dsa.c:806 #, c-format msgid "Failed on DSA request of size %zu." msgstr "Fehler bei DSA-Anfrage mit Größe %zu." @@ -14388,7 +14414,7 @@ msgid "could not receive data from client: %m" msgstr "konnte Daten vom Client nicht empfangen: %m" -#: libpq/pqcomm.c:1215 tcop/postgres.c:4186 +#: libpq/pqcomm.c:1215 tcop/postgres.c:4187 #, c-format msgid "terminating connection because protocol synchronization was lost" msgstr "Verbindung wird abgebrochen, weil Protokollsynchronisierung verloren wurde" @@ -14769,44 +14795,44 @@ msgstr "%s kann nicht auf die nullbare Seite eines äußeren Verbundes angewendet werden" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: optimizer/plan/planner.c:1921 parser/analyze.c:1632 parser/analyze.c:1848 +#: optimizer/plan/planner.c:1923 parser/analyze.c:1632 parser/analyze.c:1848 #: parser/analyze.c:2675 #, c-format msgid "%s is not allowed with UNION/INTERSECT/EXCEPT" msgstr "%s ist nicht in UNION/INTERSECT/EXCEPT erlaubt" -#: optimizer/plan/planner.c:2508 optimizer/plan/planner.c:4161 +#: optimizer/plan/planner.c:2510 optimizer/plan/planner.c:4163 #, c-format msgid "could not implement GROUP BY" msgstr "konnte GROUP BY nicht implementieren" -#: optimizer/plan/planner.c:2509 optimizer/plan/planner.c:4162 -#: optimizer/plan/planner.c:4889 optimizer/prep/prepunion.c:1045 +#: optimizer/plan/planner.c:2511 optimizer/plan/planner.c:4164 +#: optimizer/plan/planner.c:4891 optimizer/prep/prepunion.c:1045 #, c-format msgid "Some of the datatypes only support hashing, while others only support sorting." msgstr "Einige Datentypen unterstützen nur Hashing, während andere nur Sortieren unterstützen." -#: optimizer/plan/planner.c:4888 +#: optimizer/plan/planner.c:4890 #, c-format msgid "could not implement DISTINCT" msgstr "konnte DISTINCT nicht implementieren" -#: optimizer/plan/planner.c:5736 +#: optimizer/plan/planner.c:5738 #, c-format msgid "could not implement window PARTITION BY" msgstr "konnte PARTITION BY für Fenster nicht implementieren" -#: optimizer/plan/planner.c:5737 +#: optimizer/plan/planner.c:5739 #, c-format msgid "Window partitioning columns must be of sortable datatypes." msgstr "Fensterpartitionierungsspalten müssen sortierbare Datentypen haben." -#: optimizer/plan/planner.c:5741 +#: optimizer/plan/planner.c:5743 #, c-format msgid "could not implement window ORDER BY" msgstr "konnte ORDER BY für Fenster nicht implementieren" -#: optimizer/plan/planner.c:5742 +#: optimizer/plan/planner.c:5744 #, c-format msgid "Window ordering columns must be of sortable datatypes." msgstr "Fenstersortierspalten müssen sortierbare Datentypen haben." @@ -16946,7 +16972,7 @@ msgstr "Regeln mit WHERE-Bedingungen können als Aktion nur SELECT, INSERT, UPDATE oder DELETE haben" #: parser/parse_utilcmd.c:3057 parser/parse_utilcmd.c:3158 -#: rewrite/rewriteHandler.c:525 rewrite/rewriteManip.c:1021 +#: rewrite/rewriteHandler.c:527 rewrite/rewriteManip.c:1021 #, c-format msgid "conditional UNION/INTERSECT/EXCEPT statements are not implemented" msgstr "UNION/INTERSECTION/EXCEPT mit Bedingung sind nicht implementiert" @@ -17425,32 +17451,32 @@ msgid "autovacuum: processing database \"%s\"" msgstr "Autovacuum: bearbeite Datenbank »%s«" -#: postmaster/autovacuum.c:2259 +#: postmaster/autovacuum.c:2271 #, c-format msgid "autovacuum: dropping orphan temp table \"%s.%s.%s\"" msgstr "Autovacuum: lösche verwaiste temporäre Tabelle »%s.%s.%s«" -#: postmaster/autovacuum.c:2488 +#: postmaster/autovacuum.c:2500 #, c-format msgid "automatic vacuum of table \"%s.%s.%s\"" msgstr "automatisches Vacuum der Tabelle »%s.%s.%s«" -#: postmaster/autovacuum.c:2491 +#: postmaster/autovacuum.c:2503 #, c-format msgid "automatic analyze of table \"%s.%s.%s\"" msgstr "automatisches Analysieren der Tabelle »%s.%s.%s«" -#: postmaster/autovacuum.c:2684 +#: postmaster/autovacuum.c:2696 #, c-format msgid "processing work entry for relation \"%s.%s.%s\"" msgstr "verarbeite Arbeitseintrag für Relation »%s.%s.%s«" -#: postmaster/autovacuum.c:3288 +#: postmaster/autovacuum.c:3300 #, c-format msgid "autovacuum not started because of misconfiguration" msgstr "Autovacuum wegen Fehlkonfiguration nicht gestartet" -#: postmaster/autovacuum.c:3289 +#: postmaster/autovacuum.c:3301 #, c-format msgid "Enable the \"track_counts\" option." msgstr "Schalten Sie die Option »track_counts« ein." @@ -19377,7 +19403,7 @@ msgid "could not write to log segment %s at offset %u, length %lu: %m" msgstr "konnte nicht in Logsegment %s bei Position %u, Länge %lu schreiben: %m" -#: replication/walsender.c:528 storage/smgr/md.c:1330 +#: replication/walsender.c:528 storage/smgr/md.c:1333 #, c-format msgid "could not seek to end of file \"%s\": %m" msgstr "konnte Positionszeiger nicht ans Ende der Datei »%s« setzen: %m" @@ -19720,198 +19746,198 @@ msgid "renaming an ON SELECT rule is not allowed" msgstr "Umbenennen einer ON-SELECT-Regel ist nicht erlaubt" -#: rewrite/rewriteHandler.c:569 +#: rewrite/rewriteHandler.c:571 #, c-format msgid "WITH query name \"%s\" appears in both a rule action and the query being rewritten" msgstr "WITH-Anfragename »%s« erscheint sowohl in der Regelaktion als auch in der umzuschreibenden Anfrage" -#: rewrite/rewriteHandler.c:596 +#: rewrite/rewriteHandler.c:598 #, c-format msgid "INSERT...SELECT rule actions are not supported for queries having data-modifying statements in WITH" msgstr "INSTEAD...SELECT-Regelaktionen werden für Anfrangen mit datenmodifizierenden Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:649 +#: rewrite/rewriteHandler.c:651 #, c-format msgid "cannot have RETURNING lists in multiple rules" msgstr "RETURNING-Listen können nicht in mehreren Regeln auftreten" -#: rewrite/rewriteHandler.c:860 rewrite/rewriteHandler.c:872 +#: rewrite/rewriteHandler.c:862 rewrite/rewriteHandler.c:874 #, c-format msgid "cannot insert into column \"%s\"" msgstr "kann nicht in Spalte »%s« einfügen" -#: rewrite/rewriteHandler.c:861 rewrite/rewriteHandler.c:883 +#: rewrite/rewriteHandler.c:863 rewrite/rewriteHandler.c:885 #, c-format msgid "Column \"%s\" is an identity column defined as GENERATED ALWAYS." msgstr "Spalte »%s« ist eine Identitätsspalte, die als GENERATED ALWAYS definiert ist." -#: rewrite/rewriteHandler.c:863 +#: rewrite/rewriteHandler.c:865 #, c-format msgid "Use OVERRIDING SYSTEM VALUE to override." msgstr "Verwenden Sie OVERRIDING SYSTEM VALUE, um diese Einschränkung außer Kraft zu setzen." -#: rewrite/rewriteHandler.c:882 rewrite/rewriteHandler.c:889 +#: rewrite/rewriteHandler.c:884 rewrite/rewriteHandler.c:891 #, c-format msgid "column \"%s\" can only be updated to DEFAULT" msgstr "Spalte »%s« kann nur auf DEFAULT aktualisiert werden" -#: rewrite/rewriteHandler.c:1058 rewrite/rewriteHandler.c:1076 +#: rewrite/rewriteHandler.c:1060 rewrite/rewriteHandler.c:1078 #, c-format msgid "multiple assignments to same column \"%s\"" msgstr "mehrere Zuweisungen zur selben Spalte »%s«" -#: rewrite/rewriteHandler.c:2068 rewrite/rewriteHandler.c:3925 +#: rewrite/rewriteHandler.c:2070 rewrite/rewriteHandler.c:3927 #, c-format msgid "infinite recursion detected in rules for relation \"%s\"" msgstr "unendliche Rekursion entdeckt in Regeln für Relation »%s«" -#: rewrite/rewriteHandler.c:2153 +#: rewrite/rewriteHandler.c:2155 #, c-format msgid "infinite recursion detected in policy for relation \"%s\"" msgstr "unendliche Rekursion entdeckt in Policys für Relation »%s«" -#: rewrite/rewriteHandler.c:2473 +#: rewrite/rewriteHandler.c:2475 msgid "Junk view columns are not updatable." msgstr "Junk-Sichtspalten sind nicht aktualisierbar." -#: rewrite/rewriteHandler.c:2478 +#: rewrite/rewriteHandler.c:2480 msgid "View columns that are not columns of their base relation are not updatable." msgstr "Sichtspalten, die nicht Spalten ihrer Basisrelation sind, sind nicht aktualisierbar." -#: rewrite/rewriteHandler.c:2481 +#: rewrite/rewriteHandler.c:2483 msgid "View columns that refer to system columns are not updatable." msgstr "Sichtspalten, die auf Systemspalten verweisen, sind nicht aktualisierbar." -#: rewrite/rewriteHandler.c:2484 +#: rewrite/rewriteHandler.c:2486 msgid "View columns that return whole-row references are not updatable." msgstr "Sichtspalten, die Verweise auf ganze Zeilen zurückgeben, sind nicht aktualisierbar." -#: rewrite/rewriteHandler.c:2545 +#: rewrite/rewriteHandler.c:2547 msgid "Views containing DISTINCT are not automatically updatable." msgstr "Sichten, die DISTINCT enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2548 +#: rewrite/rewriteHandler.c:2550 msgid "Views containing GROUP BY are not automatically updatable." msgstr "Sichten, die GROUP BY enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2551 +#: rewrite/rewriteHandler.c:2553 msgid "Views containing HAVING are not automatically updatable." msgstr "Sichten, die HAVING enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2554 +#: rewrite/rewriteHandler.c:2556 msgid "Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable." msgstr "Sichten, die UNION, INTERSECT oder EXCEPT enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2557 +#: rewrite/rewriteHandler.c:2559 msgid "Views containing WITH are not automatically updatable." msgstr "Sichten, die WITH enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2560 +#: rewrite/rewriteHandler.c:2562 msgid "Views containing LIMIT or OFFSET are not automatically updatable." msgstr "Sichten, die LIMIT oder OFFSET enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2572 +#: rewrite/rewriteHandler.c:2574 msgid "Views that return aggregate functions are not automatically updatable." msgstr "Sichten, die Aggregatfunktionen zurückgeben, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2575 +#: rewrite/rewriteHandler.c:2577 msgid "Views that return window functions are not automatically updatable." msgstr "Sichten, die Fensterfunktionen zurückgeben, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2578 +#: rewrite/rewriteHandler.c:2580 msgid "Views that return set-returning functions are not automatically updatable." msgstr "Sichten, die Funktionen mit Ergebnismenge zurückgeben, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2585 rewrite/rewriteHandler.c:2589 -#: rewrite/rewriteHandler.c:2597 +#: rewrite/rewriteHandler.c:2587 rewrite/rewriteHandler.c:2591 +#: rewrite/rewriteHandler.c:2599 msgid "Views that do not select from a single table or view are not automatically updatable." msgstr "Sichten, die nicht aus einer einzigen Tabelle oder Sicht lesen, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2600 +#: rewrite/rewriteHandler.c:2602 msgid "Views containing TABLESAMPLE are not automatically updatable." msgstr "Sichten, die TABLESAMPLE enthalten, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:2624 +#: rewrite/rewriteHandler.c:2626 msgid "Views that have no updatable columns are not automatically updatable." msgstr "Sichten, die keine aktualisierbaren Spalten haben, sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:3101 +#: rewrite/rewriteHandler.c:3103 #, c-format msgid "cannot insert into column \"%s\" of view \"%s\"" msgstr "kann nicht in Spalte »%s« von Sicht »%s« einfügen" -#: rewrite/rewriteHandler.c:3109 +#: rewrite/rewriteHandler.c:3111 #, c-format msgid "cannot update column \"%s\" of view \"%s\"" msgstr "kann Spalte »%s« von Sicht »%s« nicht aktualisieren" -#: rewrite/rewriteHandler.c:3594 +#: rewrite/rewriteHandler.c:3596 #, c-format msgid "DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH" msgstr "DO-INSTEAD-NOTIFY-Regeln werden für datenmodifizierende Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:3605 +#: rewrite/rewriteHandler.c:3607 #, c-format msgid "DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH" msgstr "DO-INSTEAD-NOTHING-Regeln werden für datenmodifizierende Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:3619 +#: rewrite/rewriteHandler.c:3621 #, c-format msgid "conditional DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "DO-INSTEAD-Regeln mit Bedingung werden für datenmodifizierende Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:3623 +#: rewrite/rewriteHandler.c:3625 #, c-format msgid "DO ALSO rules are not supported for data-modifying statements in WITH" msgstr "DO-ALSO-Regeln werden für datenmodifizierende Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:3628 +#: rewrite/rewriteHandler.c:3630 #, c-format msgid "multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "DO-INSTEAD-Regeln mit mehreren Anweisungen werden für datenmodifizierende Anweisungen in WITH nicht unterstützt" -#: rewrite/rewriteHandler.c:3853 rewrite/rewriteHandler.c:3861 -#: rewrite/rewriteHandler.c:3869 +#: rewrite/rewriteHandler.c:3855 rewrite/rewriteHandler.c:3863 +#: rewrite/rewriteHandler.c:3871 #, c-format msgid "Views with conditional DO INSTEAD rules are not automatically updatable." msgstr "Sichten mit DO-INSTEAD-Regeln mit Bedingung sind nicht automatisch aktualisierbar." -#: rewrite/rewriteHandler.c:3974 +#: rewrite/rewriteHandler.c:3976 #, c-format msgid "cannot perform INSERT RETURNING on relation \"%s\"" msgstr "INSERT RETURNING kann in Relation »%s« nicht ausgeführt werden" -#: rewrite/rewriteHandler.c:3976 +#: rewrite/rewriteHandler.c:3978 #, c-format msgid "You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause." msgstr "Sie benötigen eine ON INSERT DO INSTEAD Regel ohne Bedingung, mit RETURNING-Klausel." -#: rewrite/rewriteHandler.c:3981 +#: rewrite/rewriteHandler.c:3983 #, c-format msgid "cannot perform UPDATE RETURNING on relation \"%s\"" msgstr "UPDATE RETURNING kann in Relation »%s« nicht ausgeführt werden" -#: rewrite/rewriteHandler.c:3983 +#: rewrite/rewriteHandler.c:3985 #, c-format msgid "You need an unconditional ON UPDATE DO INSTEAD rule with a RETURNING clause." msgstr "Sie benötigen eine ON UPDATE DO INSTEAD Regel ohne Bedingung, mit RETURNING-Klausel." -#: rewrite/rewriteHandler.c:3988 +#: rewrite/rewriteHandler.c:3990 #, c-format msgid "cannot perform DELETE RETURNING on relation \"%s\"" msgstr "DELETE RETURNING kann in Relation »%s« nicht ausgeführt werden" -#: rewrite/rewriteHandler.c:3990 +#: rewrite/rewriteHandler.c:3992 #, c-format msgid "You need an unconditional ON DELETE DO INSTEAD rule with a RETURNING clause." msgstr "Sie benötigen eine ON DELETE DO INSTEAD Regel ohne Bedingung, mit RETURNING-Klausel." -#: rewrite/rewriteHandler.c:4008 +#: rewrite/rewriteHandler.c:4010 #, c-format msgid "INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules" msgstr "INSERT mit ON-CONFLICT-Klausel kann nicht mit Tabelle verwendet werden, die INSERT- oder UPDATE-Regeln hat" -#: rewrite/rewriteHandler.c:4065 +#: rewrite/rewriteHandler.c:4067 #, c-format msgid "WITH cannot be used in a query that is rewritten by rules into multiple queries" msgstr "WITH kann nicht in einer Anfrage verwendet werden, die durch Regeln in mehrere Anfragen umgeschrieben wird" @@ -20317,17 +20343,17 @@ msgid "%s failed: %m" msgstr "%s fehlgeschlagen: %m" -#: storage/ipc/procarray.c:3126 +#: storage/ipc/procarray.c:3127 #, c-format msgid "database \"%s\" is being used by prepared transactions" msgstr "Datenbank »%s« wird von vorbereiteten Transaktionen verwendet" -#: storage/ipc/procarray.c:3158 storage/ipc/signalfuncs.c:142 +#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:142 #, c-format msgid "must be a superuser to terminate superuser process" msgstr "nur Superuser können Prozesse eines Superusers beenden" -#: storage/ipc/procarray.c:3165 storage/ipc/signalfuncs.c:147 +#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:147 #, c-format msgid "must be a member of the role whose process is being terminated or member of pg_signal_backend" msgstr "muss Mitglied der Rolle sein, deren Prozess beendet wird, oder Mitglied von pg_signal_backend" @@ -20342,9 +20368,9 @@ msgid "invalid message size %zu in shared memory queue" msgstr "ungültige Nachrichtengröße %zu in Shared-Memory-Queue" -#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:982 -#: storage/lmgr/lock.c:1020 storage/lmgr/lock.c:2845 storage/lmgr/lock.c:4252 -#: storage/lmgr/lock.c:4317 storage/lmgr/lock.c:4667 +#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:963 +#: storage/lmgr/lock.c:1001 storage/lmgr/lock.c:2821 storage/lmgr/lock.c:4228 +#: storage/lmgr/lock.c:4293 storage/lmgr/lock.c:4643 #: storage/lmgr/predicate.c:2489 storage/lmgr/predicate.c:2504 #: storage/lmgr/predicate.c:3994 storage/lmgr/predicate.c:5109 #: utils/hash/dynahash.c:1067 @@ -20382,7 +20408,7 @@ msgid "PID %d is not a PostgreSQL server process" msgstr "PID %d ist kein PostgreSQL-Serverprozess" -#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1370 +#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1372 #, c-format msgid "could not send signal to process %d: %m" msgstr "konnte Signal nicht an Prozess %d senden: %m" @@ -20443,22 +20469,22 @@ msgid "invalid large object write request size: %d" msgstr "ungültige Größe der Large-Object-Schreibaufforderung: %d" -#: storage/lmgr/deadlock.c:1124 +#: storage/lmgr/deadlock.c:1123 #, c-format msgid "Process %d waits for %s on %s; blocked by process %d." msgstr "Prozess %d wartet auf %s-Sperre auf %s; blockiert von Prozess %d." -#: storage/lmgr/deadlock.c:1143 +#: storage/lmgr/deadlock.c:1142 #, c-format msgid "Process %d: %s" msgstr "Prozess %d: %s" -#: storage/lmgr/deadlock.c:1152 +#: storage/lmgr/deadlock.c:1151 #, c-format msgid "deadlock detected" msgstr "Verklemmung (Deadlock) entdeckt" -#: storage/lmgr/deadlock.c:1155 +#: storage/lmgr/deadlock.c:1154 #, c-format msgid "See server log for query details." msgstr "Einzelheiten zur Anfrage finden Sie im Serverlog." @@ -20563,23 +20589,23 @@ msgid "unrecognized locktag type %d" msgstr "unbekannter Locktag-Typ %d" -#: storage/lmgr/lock.c:803 +#: storage/lmgr/lock.c:791 #, c-format msgid "cannot acquire lock mode %s on database objects while recovery is in progress" msgstr "Sperrmodus %s kann während der Wiederherstellung nicht auf Datenbankobjekte gesetzt werden" -#: storage/lmgr/lock.c:805 +#: storage/lmgr/lock.c:793 #, c-format msgid "Only RowExclusiveLock or less can be acquired on database objects during recovery." msgstr "Nur Sperren gleich oder unter RowExclusiveLock können während der Wiederherstellung auf Datenbankobjekte gesetzt werden." -#: storage/lmgr/lock.c:983 storage/lmgr/lock.c:1021 storage/lmgr/lock.c:2846 -#: storage/lmgr/lock.c:4253 storage/lmgr/lock.c:4318 storage/lmgr/lock.c:4668 +#: storage/lmgr/lock.c:964 storage/lmgr/lock.c:1002 storage/lmgr/lock.c:2822 +#: storage/lmgr/lock.c:4229 storage/lmgr/lock.c:4294 storage/lmgr/lock.c:4644 #, c-format msgid "You might need to increase max_locks_per_transaction." msgstr "Sie müssen möglicherweise max_locks_per_transaction erhöhen." -#: storage/lmgr/lock.c:3301 storage/lmgr/lock.c:3369 storage/lmgr/lock.c:3485 +#: storage/lmgr/lock.c:3277 storage/lmgr/lock.c:3345 storage/lmgr/lock.c:3461 #, c-format msgid "cannot PREPARE while holding both session-level and transaction-level locks on the same object" msgstr "PREPARE kann nicht ausgeführt werden, wenn für das selbe Objekt Sperren auf Sitzungsebene und auf Transaktionsebene gehalten werden" @@ -20659,37 +20685,37 @@ msgid "number of requested standby connections exceeds max_wal_senders (currently %d)" msgstr "Anzahl angeforderter Standby-Verbindungen überschreitet max_wal_senders (aktuell %d)" -#: storage/lmgr/proc.c:1341 +#: storage/lmgr/proc.c:1343 #, c-format msgid "Process %d waits for %s on %s." msgstr "Prozess %d wartet auf %s-Sperre auf %s." -#: storage/lmgr/proc.c:1352 +#: storage/lmgr/proc.c:1354 #, c-format msgid "sending cancel to blocking autovacuum PID %d" msgstr "sende Stornierung an blockierende Autovacuum-PID %d" -#: storage/lmgr/proc.c:1472 +#: storage/lmgr/proc.c:1474 #, c-format msgid "process %d avoided deadlock for %s on %s by rearranging queue order after %ld.%03d ms" msgstr "Prozess %d vermied Verklemmung wegen %s-Sperre auf %s durch Umordnen der Queue nach %ld,%03d ms" -#: storage/lmgr/proc.c:1487 +#: storage/lmgr/proc.c:1489 #, c-format msgid "process %d detected deadlock while waiting for %s on %s after %ld.%03d ms" msgstr "Prozess %d hat Verklemmung festgestellt beim Warten auf %s-Sperre auf %s nach %ld,%03d ms" -#: storage/lmgr/proc.c:1496 +#: storage/lmgr/proc.c:1498 #, c-format msgid "process %d still waiting for %s on %s after %ld.%03d ms" msgstr "Prozess %d wartet immer noch auf %s-Sperre auf %s nach %ld,%03d ms" -#: storage/lmgr/proc.c:1503 +#: storage/lmgr/proc.c:1505 #, c-format msgid "process %d acquired %s on %s after %ld.%03d ms" msgstr "Prozess %d erlangte %s-Sperre auf %s nach %ld,%03d ms" -#: storage/lmgr/proc.c:1519 +#: storage/lmgr/proc.c:1521 #, c-format msgid "process %d failed to acquire %s on %s after %ld.%03d ms" msgstr "Prozess %d konnte %s-Sperre auf %s nach %ld,%03d ms nicht erlangen" @@ -20722,72 +20748,72 @@ msgid "corrupted line pointer: offset = %u, size = %u" msgstr "verfälschter Line-Pointer: offset = %u, size = %u" -#: storage/smgr/md.c:317 storage/smgr/md.c:875 +#: storage/smgr/md.c:320 storage/smgr/md.c:878 #, c-format msgid "could not truncate file \"%s\": %m" msgstr "kann Datei »%s« nicht kürzen: %m" -#: storage/smgr/md.c:446 +#: storage/smgr/md.c:449 #, c-format msgid "cannot extend file \"%s\" beyond %u blocks" msgstr "kann Datei »%s« nicht auf über %u Blöcke erweitern" -#: storage/smgr/md.c:461 +#: storage/smgr/md.c:464 #, c-format msgid "could not extend file \"%s\": %m" msgstr "konnte Datei »%s« nicht erweitern: %m" -#: storage/smgr/md.c:463 storage/smgr/md.c:470 storage/smgr/md.c:758 +#: storage/smgr/md.c:466 storage/smgr/md.c:473 storage/smgr/md.c:761 #, c-format msgid "Check free disk space." msgstr "Prüfen Sie den freien Festplattenplatz." -#: storage/smgr/md.c:467 +#: storage/smgr/md.c:470 #, c-format msgid "could not extend file \"%s\": wrote only %d of %d bytes at block %u" msgstr "konnte Datei »%s« nicht erweitern: es wurden nur %d von %d Bytes bei Block %u geschrieben" -#: storage/smgr/md.c:679 +#: storage/smgr/md.c:682 #, c-format msgid "could not read block %u in file \"%s\": %m" msgstr "konnte Block %u in Datei »%s« nicht lesen: %m" -#: storage/smgr/md.c:695 +#: storage/smgr/md.c:698 #, c-format msgid "could not read block %u in file \"%s\": read only %d of %d bytes" msgstr "konnte Block %u in Datei »%s« nicht lesen: es wurden nur %d von %d Bytes gelesen" -#: storage/smgr/md.c:749 +#: storage/smgr/md.c:752 #, c-format msgid "could not write block %u in file \"%s\": %m" msgstr "konnte Block %u in Datei »%s« nicht schreiben: %m" -#: storage/smgr/md.c:754 +#: storage/smgr/md.c:757 #, c-format msgid "could not write block %u in file \"%s\": wrote only %d of %d bytes" msgstr "konnte Block %u in Datei »%s« nicht schreiben: es wurden nur %d von %d Bytes geschrieben" -#: storage/smgr/md.c:846 +#: storage/smgr/md.c:849 #, c-format msgid "could not truncate file \"%s\" to %u blocks: it's only %u blocks now" msgstr "konnte Datei »%s« nicht auf %u Blöcke kürzen: es sind jetzt nur %u Blöcke" -#: storage/smgr/md.c:901 +#: storage/smgr/md.c:904 #, c-format msgid "could not truncate file \"%s\" to %u blocks: %m" msgstr "konnte Datei »%s« nicht auf %u Blöcke kürzen: %m" -#: storage/smgr/md.c:996 +#: storage/smgr/md.c:999 #, c-format msgid "could not forward fsync request because request queue is full" msgstr "konnte fsync-Anfrage nicht weiterleiten, weil Anfrageschlange voll ist" -#: storage/smgr/md.c:1295 +#: storage/smgr/md.c:1298 #, c-format msgid "could not open file \"%s\" (target block %u): previous segment is only %u blocks" msgstr "konnte Datei »%s« nicht öffnen (Zielblock %u): vorhergehendes Segment hat nur %u Blöcke" -#: storage/smgr/md.c:1309 +#: storage/smgr/md.c:1312 #, c-format msgid "could not open file \"%s\" (target block %u): %m" msgstr "konnte Datei »%s« nicht öffnen (Zielblock %u): %m" @@ -20844,7 +20870,7 @@ msgstr "unerwartetes EOF auf Client-Verbindung" #: tcop/postgres.c:440 tcop/postgres.c:452 tcop/postgres.c:463 -#: tcop/postgres.c:475 tcop/postgres.c:4583 +#: tcop/postgres.c:475 tcop/postgres.c:4587 #, c-format msgid "invalid frontend message type %d" msgstr "ungültiger Frontend-Message-Typ %d" @@ -21092,27 +21118,27 @@ msgid "%s: no database nor user name specified" msgstr "%s: weder Datenbankname noch Benutzername angegeben" -#: tcop/postgres.c:4491 +#: tcop/postgres.c:4495 #, c-format msgid "invalid CLOSE message subtype %d" msgstr "ungültiger Subtyp %d von CLOSE-Message" -#: tcop/postgres.c:4526 +#: tcop/postgres.c:4530 #, c-format msgid "invalid DESCRIBE message subtype %d" msgstr "ungültiger Subtyp %d von DESCRIBE-Message" -#: tcop/postgres.c:4604 +#: tcop/postgres.c:4608 #, c-format msgid "fastpath function calls not supported in a replication connection" msgstr "Fastpath-Funktionsaufrufe werden auf einer Replikationsverbindung nicht unterstützt" -#: tcop/postgres.c:4608 +#: tcop/postgres.c:4612 #, c-format msgid "extended query protocol not supported in a replication connection" msgstr "erweitertes Anfrageprotokoll wird nicht auf einer Replikationsverbindung unterstützt" -#: tcop/postgres.c:4785 +#: tcop/postgres.c:4789 #, c-format msgid "disconnection: session time: %d:%02d:%02d.%03d user=%s database=%s host=%s%s%s" msgstr "Verbindungsende: Sitzungszeit: %d:%02d:%02d.%03d Benutzer=%s Datenbank=%s Host=%s%s%s" @@ -21391,27 +21417,27 @@ msgid "text search parser does not support headline creation" msgstr "Textsucheparser unterstützt das Erzeugen von Headlines nicht" -#: tsearch/wparser_def.c:2585 +#: tsearch/wparser_def.c:2600 #, c-format msgid "unrecognized headline parameter: \"%s\"" msgstr "unbekannter Headline-Parameter: »%s«" -#: tsearch/wparser_def.c:2604 +#: tsearch/wparser_def.c:2619 #, c-format msgid "MinWords should be less than MaxWords" msgstr "»MinWords« sollte kleiner als »MaxWords« sein" -#: tsearch/wparser_def.c:2608 +#: tsearch/wparser_def.c:2623 #, c-format msgid "MinWords should be positive" msgstr "»MinWords« sollte positiv sein" -#: tsearch/wparser_def.c:2612 +#: tsearch/wparser_def.c:2627 #, c-format msgid "ShortWord should be >= 0" msgstr "»ShortWord« sollte >= 0 sein" -#: tsearch/wparser_def.c:2616 +#: tsearch/wparser_def.c:2631 #, c-format msgid "MaxFragments should be >= 0" msgstr "»MaxFragments« sollte >= 0 sein" @@ -23088,42 +23114,42 @@ msgid "jsonpath item method .%s() can only be applied to a string" msgstr "JSON-Path-Item-Methode .%s() kann nur auf eine Zeichenkette angewendet werden" -#: utils/adt/jsonpath_exec.c:1894 +#: utils/adt/jsonpath_exec.c:1903 #, c-format msgid "datetime format is not recognized: \"%s\"" msgstr "Datum-/Zeitformat nicht erkannt: »%s«" -#: utils/adt/jsonpath_exec.c:1896 +#: utils/adt/jsonpath_exec.c:1905 #, c-format msgid "Use a datetime template argument to specify the input data format." msgstr "Verwenden Sie das Template-Argument für .datetime(), um das Eingabeformat anzugeben." -#: utils/adt/jsonpath_exec.c:1964 +#: utils/adt/jsonpath_exec.c:1973 #, c-format msgid "jsonpath item method .%s() can only be applied to an object" msgstr "JSON-Path-Item-Methode .%s() kann nur auf ein Objekt angewendet werden" -#: utils/adt/jsonpath_exec.c:2147 +#: utils/adt/jsonpath_exec.c:2156 #, c-format msgid "could not find jsonpath variable \"%s\"" msgstr "konnte JSON-Path-Variable »%s« nicht finden" -#: utils/adt/jsonpath_exec.c:2411 +#: utils/adt/jsonpath_exec.c:2420 #, c-format msgid "jsonpath array subscript is not a single numeric value" msgstr "JSON-Path-Arrayindex ist kein einzelner numerischer Wert" -#: utils/adt/jsonpath_exec.c:2423 +#: utils/adt/jsonpath_exec.c:2432 #, c-format msgid "jsonpath array subscript is out of integer range" msgstr "JSON-Path-Arrayindex außerhalb des gültigen Bereichs für ganze Zahlen" -#: utils/adt/jsonpath_exec.c:2600 +#: utils/adt/jsonpath_exec.c:2609 #, c-format msgid "cannot convert value from %s to %s without time zone usage" msgstr "Wert kann nicht von %s nach %s konvertiert werden ohne Verwendung von Zeitzonen" -#: utils/adt/jsonpath_exec.c:2602 +#: utils/adt/jsonpath_exec.c:2611 #, c-format msgid "Use *_tz() function for time zone support." msgstr "Verwenden Sie die *_tz()-Funktion für Zeitzonenunterstützung." @@ -24534,22 +24560,22 @@ msgid "operator class \"%s\" of access method %s is missing support function %d for type %s" msgstr "in Operatorklasse »%s« für Zugriffsmethode %s fehlt Support-Funktion %d für Typ %s" -#: utils/cache/plancache.c:718 +#: utils/cache/plancache.c:720 #, c-format msgid "cached plan must not change result type" msgstr "gecachter Plan darf den Ergebnistyp nicht ändern" -#: utils/cache/relcache.c:6200 +#: utils/cache/relcache.c:6201 #, c-format msgid "could not create relation-cache initialization file \"%s\": %m" msgstr "konnte Initialisierungsdatei für Relationscache »%s« nicht erzeugen: %m" -#: utils/cache/relcache.c:6202 +#: utils/cache/relcache.c:6203 #, c-format msgid "Continuing anyway, but there's something wrong." msgstr "Setze trotzdem fort, aber irgendwas stimmt nicht." -#: utils/cache/relcache.c:6524 +#: utils/cache/relcache.c:6525 #, c-format msgid "could not remove cache file \"%s\": %m" msgstr "konnte Cache-Datei »%s« nicht löschen: %m" @@ -25132,17 +25158,22 @@ msgid "database %u does not exist" msgstr "Datenbank %u existiert nicht" -#: utils/init/postinit.c:983 +#: utils/init/postinit.c:984 #, c-format msgid "It seems to have just been dropped or renamed." msgstr "Sie wurde anscheinend gerade gelöscht oder umbenannt." -#: utils/init/postinit.c:1001 +#: utils/init/postinit.c:991 +#, c-format +msgid "cannot connect to invalid database \"%s\"" +msgstr "mit ungültiger Datenbank »%s« kann nicht verbunden werden" + +#: utils/init/postinit.c:1011 #, c-format msgid "The database subdirectory \"%s\" is missing." msgstr "Das Datenbankunterverzeichnis »%s« fehlt." -#: utils/init/postinit.c:1006 +#: utils/init/postinit.c:1016 #, c-format msgid "could not access directory \"%s\": %m" msgstr "konnte nicht auf Verzeichnis »%s« zugreifen: %m" @@ -27401,7 +27432,7 @@ msgid "Failed while creating memory context \"%s\"." msgstr "Fehler während der Erzeugung des Speicherkontexts »%s«." -#: utils/mmgr/dsa.c:519 utils/mmgr/dsa.c:1332 +#: utils/mmgr/dsa.c:520 utils/mmgr/dsa.c:1337 #, c-format msgid "could not attach to dynamic shared area" msgstr "konnte nicht an dynamische Shared Area anbinden" diff -Nru postgresql-13-13.11/src/backend/po/fr.po postgresql-13-13.12/src/backend/po/fr.po --- postgresql-13-13.11/src/backend/po/fr.po 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/po/fr.po 2023-08-07 20:11:34.000000000 +0000 @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: PostgreSQL 12\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2023-05-05 13:26+0000\n" -"PO-Revision-Date: 2023-05-07 17:04+0200\n" +"POT-Creation-Date: 2023-07-25 06:25+0000\n" +"PO-Revision-Date: 2023-07-27 11:17+0200\n" "Last-Translator: Christophe Courtois \n" "Language-Team: French \n" "Language: fr\n" @@ -17,18 +17,18 @@ "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" -"X-Generator: Poedit 3.2.2\n" +"X-Generator: Poedit 3.3.2\n" #: ../common/config_info.c:134 ../common/config_info.c:142 ../common/config_info.c:150 ../common/config_info.c:158 ../common/config_info.c:166 ../common/config_info.c:174 ../common/config_info.c:182 ../common/config_info.c:190 msgid "not recorded" msgstr "non enregistré" -#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 commands/copy.c:3499 commands/extension.c:3444 utils/adt/genfile.c:125 +#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 commands/copy.c:3499 commands/extension.c:3441 utils/adt/genfile.c:125 #, c-format msgid "could not open file \"%s\" for reading: %m" msgstr "n'a pas pu ouvrir le fichier « %s » pour une lecture : %m" -#: ../common/controldata_utils.c:86 ../common/controldata_utils.c:89 access/transam/timeline.c:143 access/transam/timeline.c:362 access/transam/twophase.c:1334 access/transam/xlog.c:3528 access/transam/xlog.c:4772 access/transam/xlog.c:11414 access/transam/xlog.c:11427 access/transam/xlog.c:11882 access/transam/xlog.c:11962 access/transam/xlog.c:12001 access/transam/xlog.c:12044 access/transam/xlogfuncs.c:662 access/transam/xlogfuncs.c:681 commands/extension.c:3454 libpq/hba.c:499 replication/logical/origin.c:717 replication/logical/origin.c:753 replication/logical/reorderbuffer.c:3661 replication/logical/snapbuild.c:1862 replication/logical/snapbuild.c:1904 +#: ../common/controldata_utils.c:86 ../common/controldata_utils.c:89 access/transam/timeline.c:143 access/transam/timeline.c:362 access/transam/twophase.c:1334 access/transam/xlog.c:3528 access/transam/xlog.c:4772 access/transam/xlog.c:11418 access/transam/xlog.c:11431 access/transam/xlog.c:11886 access/transam/xlog.c:11966 access/transam/xlog.c:12005 access/transam/xlog.c:12048 access/transam/xlogfuncs.c:662 access/transam/xlogfuncs.c:681 commands/extension.c:3451 libpq/hba.c:499 replication/logical/origin.c:717 replication/logical/origin.c:753 replication/logical/reorderbuffer.c:3661 replication/logical/snapbuild.c:1862 replication/logical/snapbuild.c:1904 #: replication/logical/snapbuild.c:1932 replication/logical/snapbuild.c:1959 replication/slot.c:1716 replication/slot.c:1757 replication/walsender.c:548 storage/file/buffile.c:441 storage/file/copydir.c:195 utils/adt/genfile.c:200 utils/adt/misc.c:792 utils/cache/relmapper.c:744 #, c-format msgid "could not read file \"%s\": %m" @@ -64,17 +64,17 @@ "est incompatible avec ce répertoire des données." #: ../common/controldata_utils.c:197 ../common/controldata_utils.c:203 ../common/file_utils.c:224 ../common/file_utils.c:283 ../common/file_utils.c:357 access/heap/rewriteheap.c:1264 access/transam/timeline.c:111 access/transam/timeline.c:251 access/transam/timeline.c:348 access/transam/twophase.c:1290 access/transam/xlog.c:3299 access/transam/xlog.c:3439 access/transam/xlog.c:3483 access/transam/xlog.c:3681 access/transam/xlog.c:3766 access/transam/xlog.c:3869 access/transam/xlog.c:4762 access/transam/xlogutils.c:807 postmaster/syslogger.c:1488 replication/basebackup.c:621 replication/basebackup.c:1599 replication/logical/origin.c:707 replication/logical/reorderbuffer.c:2512 -#: replication/logical/reorderbuffer.c:2876 replication/logical/reorderbuffer.c:3641 replication/logical/snapbuild.c:1726 replication/logical/snapbuild.c:1833 replication/slot.c:1688 replication/walsender.c:521 replication/walsender.c:2552 storage/file/copydir.c:161 storage/file/fd.c:679 storage/file/fd.c:3432 storage/file/fd.c:3519 storage/smgr/md.c:514 utils/cache/relmapper.c:724 utils/cache/relmapper.c:842 utils/error/elog.c:1858 utils/init/miscinit.c:1321 utils/init/miscinit.c:1455 utils/init/miscinit.c:1532 utils/misc/guc.c:8292 utils/misc/guc.c:8324 +#: replication/logical/reorderbuffer.c:2876 replication/logical/reorderbuffer.c:3641 replication/logical/snapbuild.c:1726 replication/logical/snapbuild.c:1833 replication/slot.c:1688 replication/walsender.c:521 replication/walsender.c:2552 storage/file/copydir.c:161 storage/file/fd.c:679 storage/file/fd.c:3432 storage/file/fd.c:3519 storage/smgr/md.c:517 utils/cache/relmapper.c:724 utils/cache/relmapper.c:842 utils/error/elog.c:1858 utils/init/miscinit.c:1321 utils/init/miscinit.c:1455 utils/init/miscinit.c:1532 utils/misc/guc.c:8292 utils/misc/guc.c:8324 #, c-format msgid "could not open file \"%s\": %m" msgstr "n'a pas pu ouvrir le fichier « %s » : %m" -#: ../common/controldata_utils.c:221 ../common/controldata_utils.c:224 access/transam/twophase.c:1730 access/transam/twophase.c:1739 access/transam/xlog.c:11171 access/transam/xlog.c:11209 access/transam/xlog.c:11622 access/transam/xlogfuncs.c:741 postmaster/syslogger.c:1499 postmaster/syslogger.c:1512 utils/cache/relmapper.c:876 +#: ../common/controldata_utils.c:221 ../common/controldata_utils.c:224 access/transam/twophase.c:1730 access/transam/twophase.c:1739 access/transam/xlog.c:11175 access/transam/xlog.c:11213 access/transam/xlog.c:11626 access/transam/xlogfuncs.c:741 postmaster/syslogger.c:1499 postmaster/syslogger.c:1512 utils/cache/relmapper.c:876 #, c-format msgid "could not write file \"%s\": %m" msgstr "impossible d'écrire le fichier « %s » : %m" -#: ../common/controldata_utils.c:239 ../common/controldata_utils.c:245 ../common/file_utils.c:295 ../common/file_utils.c:365 access/heap/rewriteheap.c:958 access/heap/rewriteheap.c:1172 access/heap/rewriteheap.c:1275 access/transam/timeline.c:432 access/transam/timeline.c:510 access/transam/twophase.c:1751 access/transam/xlog.c:3390 access/transam/xlog.c:3562 access/transam/xlog.c:4735 access/transam/xlog.c:10659 access/transam/xlog.c:10686 replication/logical/snapbuild.c:1764 replication/slot.c:1593 replication/slot.c:1698 storage/file/fd.c:696 storage/file/fd.c:3540 storage/smgr/md.c:960 storage/smgr/md.c:1001 storage/sync/sync.c:433 utils/cache/relmapper.c:891 +#: ../common/controldata_utils.c:239 ../common/controldata_utils.c:245 ../common/file_utils.c:295 ../common/file_utils.c:365 access/heap/rewriteheap.c:958 access/heap/rewriteheap.c:1172 access/heap/rewriteheap.c:1275 access/transam/timeline.c:432 access/transam/timeline.c:510 access/transam/twophase.c:1751 access/transam/xlog.c:3390 access/transam/xlog.c:3562 access/transam/xlog.c:4735 access/transam/xlog.c:10663 access/transam/xlog.c:10690 replication/logical/snapbuild.c:1764 replication/slot.c:1593 replication/slot.c:1698 storage/file/fd.c:696 storage/file/fd.c:3540 storage/smgr/md.c:963 storage/smgr/md.c:1004 storage/sync/sync.c:433 utils/cache/relmapper.c:891 #: utils/misc/guc.c:8075 #, c-format msgid "could not fsync file \"%s\": %m" @@ -105,7 +105,7 @@ msgid "could not change directory to \"%s\": %m" msgstr "n'a pas pu modifier le répertoire par « %s » : %m" -#: ../common/exec.c:300 access/transam/xlog.c:11043 replication/basebackup.c:1424 utils/adt/misc.c:366 +#: ../common/exec.c:300 access/transam/xlog.c:11047 replication/basebackup.c:1424 utils/adt/misc.c:366 #, c-format msgid "could not read symbolic link \"%s\": %m" msgstr "n'a pas pu lire le lien symbolique « %s » : %m" @@ -116,8 +116,8 @@ msgstr "échec de pclose : %m" #: ../common/exec.c:577 ../common/exec.c:622 ../common/exec.c:714 ../common/psprintf.c:143 ../common/stringinfo.c:305 ../port/path.c:630 ../port/path.c:668 ../port/path.c:685 access/transam/twophase.c:1404 access/transam/xlog.c:6545 lib/dshash.c:245 libpq/auth.c:1478 libpq/auth.c:1546 libpq/auth.c:2076 libpq/be-secure-gssapi.c:520 postmaster/bgworker.c:349 postmaster/bgworker.c:963 postmaster/postmaster.c:2550 postmaster/postmaster.c:4187 postmaster/postmaster.c:5638 postmaster/postmaster.c:5998 replication/libpqwalreceiver/libpqwalreceiver.c:286 replication/logical/logical.c:176 replication/walsender.c:595 storage/buffer/localbuf.c:442 storage/file/fd.c:854 storage/file/fd.c:1324 -#: storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1079 storage/ipc/procarray.c:1580 storage/ipc/procarray.c:1587 storage/ipc/procarray.c:2024 storage/ipc/procarray.c:2702 utils/adt/cryptohashes.c:45 utils/adt/cryptohashes.c:65 utils/adt/formatting.c:1700 utils/adt/formatting.c:1824 utils/adt/formatting.c:1949 utils/adt/pg_locale.c:484 utils/adt/pg_locale.c:648 utils/adt/regexp.c:223 utils/fmgr/dfmgr.c:229 utils/hash/dynahash.c:450 utils/hash/dynahash.c:559 utils/hash/dynahash.c:1071 utils/mb/mbutils.c:401 utils/mb/mbutils.c:428 utils/mb/mbutils.c:757 utils/mb/mbutils.c:783 utils/misc/guc.c:4858 utils/misc/guc.c:4874 utils/misc/guc.c:4887 utils/misc/guc.c:8053 -#: utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:701 utils/mmgr/dsa.c:723 utils/mmgr/dsa.c:804 utils/mmgr/generation.c:233 utils/mmgr/mcxt.c:821 utils/mmgr/mcxt.c:857 utils/mmgr/mcxt.c:895 utils/mmgr/mcxt.c:933 utils/mmgr/mcxt.c:969 utils/mmgr/mcxt.c:1000 utils/mmgr/mcxt.c:1036 utils/mmgr/mcxt.c:1088 utils/mmgr/mcxt.c:1123 utils/mmgr/mcxt.c:1158 utils/mmgr/slab.c:237 +#: storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1080 storage/ipc/procarray.c:1581 storage/ipc/procarray.c:1588 storage/ipc/procarray.c:2025 storage/ipc/procarray.c:2703 utils/adt/cryptohashes.c:45 utils/adt/cryptohashes.c:65 utils/adt/formatting.c:1700 utils/adt/formatting.c:1824 utils/adt/formatting.c:1949 utils/adt/pg_locale.c:484 utils/adt/pg_locale.c:648 utils/adt/regexp.c:223 utils/fmgr/dfmgr.c:229 utils/hash/dynahash.c:450 utils/hash/dynahash.c:559 utils/hash/dynahash.c:1071 utils/mb/mbutils.c:401 utils/mb/mbutils.c:428 utils/mb/mbutils.c:757 utils/mb/mbutils.c:783 utils/misc/guc.c:4858 utils/misc/guc.c:4874 utils/misc/guc.c:4887 utils/misc/guc.c:8053 +#: utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:702 utils/mmgr/dsa.c:724 utils/mmgr/dsa.c:805 utils/mmgr/generation.c:233 utils/mmgr/mcxt.c:821 utils/mmgr/mcxt.c:857 utils/mmgr/mcxt.c:895 utils/mmgr/mcxt.c:933 utils/mmgr/mcxt.c:969 utils/mmgr/mcxt.c:1000 utils/mmgr/mcxt.c:1036 utils/mmgr/mcxt.c:1088 utils/mmgr/mcxt.c:1123 utils/mmgr/mcxt.c:1158 utils/mmgr/slab.c:237 #, c-format msgid "out of memory" msgstr "mémoire épuisée" @@ -132,7 +132,7 @@ msgid "cannot duplicate null pointer (internal error)\n" msgstr "ne peut pas dupliquer un pointeur nul (erreur interne)\n" -#: ../common/file_utils.c:79 ../common/file_utils.c:181 access/transam/twophase.c:1302 access/transam/xlog.c:8100 access/transam/xlog.c:11030 access/transam/xlog.c:11147 access/transam/xlog.c:11185 access/transam/xlog.c:11402 access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3433 commands/tablespace.c:806 commands/tablespace.c:897 guc-file.l:1063 replication/basebackup.c:444 replication/basebackup.c:627 replication/basebackup.c:700 replication/logical/snapbuild.c:1640 storage/file/copydir.c:68 storage/file/copydir.c:107 storage/file/fd.c:1836 storage/file/fd.c:3116 storage/file/fd.c:3298 +#: ../common/file_utils.c:79 ../common/file_utils.c:181 access/transam/twophase.c:1302 access/transam/xlog.c:8104 access/transam/xlog.c:11034 access/transam/xlog.c:11151 access/transam/xlog.c:11189 access/transam/xlog.c:11406 access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3430 commands/tablespace.c:806 commands/tablespace.c:897 guc-file.l:1063 replication/basebackup.c:444 replication/basebackup.c:627 replication/basebackup.c:700 replication/logical/snapbuild.c:1640 storage/file/copydir.c:68 storage/file/copydir.c:107 storage/file/fd.c:1836 storage/file/fd.c:3116 storage/file/fd.c:3298 #: storage/file/fd.c:3384 utils/adt/dbsize.c:70 utils/adt/dbsize.c:222 utils/adt/dbsize.c:302 utils/adt/genfile.c:416 utils/adt/genfile.c:642 utils/adt/misc.c:351 #, c-format msgid "could not stat file \"%s\": %m" @@ -464,32 +464,32 @@ msgid "could not check access token membership: error code %lu\n" msgstr "n'a pas pu vérifier l'appartenance du jeton d'accès : code d'erreur %lu\n" -#: access/brin/brin.c:210 +#: access/brin/brin.c:211 #, c-format msgid "request for BRIN range summarization for index \"%s\" page %u was not recorded" msgstr "requête de résumé d'intervalle BRIN pour la page « %s » de l'index « %u » n'a pas été enregistrée" -#: access/brin/brin.c:876 access/brin/brin.c:980 access/gin/ginfast.c:1038 access/transam/xlog.c:10795 access/transam/xlog.c:11353 access/transam/xlogfuncs.c:274 access/transam/xlogfuncs.c:301 access/transam/xlogfuncs.c:340 access/transam/xlogfuncs.c:361 access/transam/xlogfuncs.c:382 access/transam/xlogfuncs.c:452 access/transam/xlogfuncs.c:509 +#: access/brin/brin.c:962 access/brin/brin.c:1066 access/gin/ginfast.c:1043 access/transam/xlog.c:10799 access/transam/xlog.c:11357 access/transam/xlogfuncs.c:274 access/transam/xlogfuncs.c:301 access/transam/xlogfuncs.c:340 access/transam/xlogfuncs.c:361 access/transam/xlogfuncs.c:382 access/transam/xlogfuncs.c:452 access/transam/xlogfuncs.c:509 #, c-format msgid "recovery is in progress" msgstr "restauration en cours" -#: access/brin/brin.c:877 access/brin/brin.c:981 +#: access/brin/brin.c:963 access/brin/brin.c:1067 #, c-format msgid "BRIN control functions cannot be executed during recovery." msgstr "Les fonctions de contrôle BRIN ne peuvent pas être exécutées pendant la restauration." -#: access/brin/brin.c:885 access/brin/brin.c:989 +#: access/brin/brin.c:971 access/brin/brin.c:1075 #, c-format msgid "block number out of range: %s" msgstr "numéro de bloc en dehors des limites : %s" -#: access/brin/brin.c:929 access/brin/brin.c:1015 +#: access/brin/brin.c:1015 access/brin/brin.c:1101 #, c-format msgid "\"%s\" is not a BRIN index" msgstr "« %s » n'est pas un index BRIN" -#: access/brin/brin.c:945 access/brin/brin.c:1031 +#: access/brin/brin.c:1031 access/brin/brin.c:1117 #, c-format msgid "could not open parent table of index %s" msgstr "n'a pas pu ouvrir la table parent de l'index %s" @@ -701,22 +701,22 @@ msgid "Reduce maintenance_work_mem." msgstr "Réduisez le maintenance_work_mem." -#: access/gin/ginfast.c:1039 +#: access/gin/ginfast.c:1044 #, c-format msgid "GIN pending list cannot be cleaned up during recovery." msgstr "la pending list GIN ne peut pas être nettoyée lors de la restauration." -#: access/gin/ginfast.c:1046 +#: access/gin/ginfast.c:1051 #, c-format msgid "\"%s\" is not a GIN index" msgstr "« %s » n'est pas un index GIN" -#: access/gin/ginfast.c:1057 +#: access/gin/ginfast.c:1062 #, c-format msgid "cannot access temporary indexes of other sessions" msgstr "ne peut pas accéder aux index temporaires d'autres sessions" -#: access/gin/ginget.c:270 access/nbtree/nbtinsert.c:745 +#: access/gin/ginget.c:272 access/nbtree/nbtinsert.c:745 #, c-format msgid "failed to re-find tuple within index \"%s\"" msgstr "échec pour retrouver la ligne dans l'index « %s »" @@ -809,10 +809,10 @@ msgid "could not determine which collation to use for string hashing" msgstr "n'a pas pu déterminer le collationnement à utiliser pour le hachage de chaîne" -#: access/hash/hashfunc.c:279 access/hash/hashfunc.c:336 catalog/heap.c:709 catalog/heap.c:715 commands/createas.c:206 commands/createas.c:501 commands/indexcmds.c:1918 commands/tablecmds.c:16444 commands/view.c:86 parser/parse_utilcmd.c:4252 regex/regc_pg_locale.c:263 utils/adt/formatting.c:1667 utils/adt/formatting.c:1791 utils/adt/formatting.c:1916 utils/adt/like.c:194 utils/adt/like_support.c:1004 utils/adt/varchar.c:733 utils/adt/varchar.c:994 utils/adt/varchar.c:1055 utils/adt/varlena.c:1486 +#: access/hash/hashfunc.c:279 access/hash/hashfunc.c:336 catalog/heap.c:709 catalog/heap.c:715 commands/createas.c:206 commands/createas.c:501 commands/indexcmds.c:1935 commands/tablecmds.c:16444 commands/view.c:86 parser/parse_utilcmd.c:4252 regex/regc_pg_locale.c:263 utils/adt/formatting.c:1667 utils/adt/formatting.c:1791 utils/adt/formatting.c:1916 utils/adt/like.c:194 utils/adt/like_support.c:1004 utils/adt/varchar.c:733 utils/adt/varchar.c:994 utils/adt/varchar.c:1055 utils/adt/varlena.c:1486 #, c-format msgid "Use the COLLATE clause to set the collation explicitly." -msgstr "Utilisez la clause COLLARE pour configurer explicitement le collationnement." +msgstr "Utilisez la clause COLLATE pour configurer explicitement le collationnement." #: access/hash/hashinsert.c:82 #, c-format @@ -906,7 +906,7 @@ msgid "could not write to file \"%s\", wrote %d of %d: %m" msgstr "n'a pas pu écrire le fichier « %s », a écrit %d de %d : %m" -#: access/heap/rewriteheap.c:1012 access/heap/rewriteheap.c:1131 access/transam/timeline.c:329 access/transam/timeline.c:485 access/transam/xlog.c:3322 access/transam/xlog.c:3497 access/transam/xlog.c:4714 access/transam/xlog.c:11162 access/transam/xlog.c:11200 access/transam/xlog.c:11605 access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4650 replication/logical/origin.c:575 replication/slot.c:1540 storage/file/copydir.c:167 storage/smgr/md.c:218 utils/time/snapmgr.c:1358 +#: access/heap/rewriteheap.c:1012 access/heap/rewriteheap.c:1131 access/transam/timeline.c:329 access/transam/timeline.c:485 access/transam/xlog.c:3322 access/transam/xlog.c:3497 access/transam/xlog.c:4714 access/transam/xlog.c:11166 access/transam/xlog.c:11204 access/transam/xlog.c:11609 access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4650 replication/logical/origin.c:575 replication/slot.c:1540 storage/file/copydir.c:167 storage/smgr/md.c:218 utils/time/snapmgr.c:1358 #, c-format msgid "could not create file \"%s\": %m" msgstr "n'a pas pu créer le fichier « %s » : %m" @@ -922,7 +922,7 @@ msgid "could not write to file \"%s\": %m" msgstr "n'a pas pu écrire dans le fichier « %s » : %m" -#: access/heap/rewriteheap.c:1249 access/transam/twophase.c:1690 access/transam/xlogarchive.c:118 access/transam/xlogarchive.c:421 postmaster/postmaster.c:1092 postmaster/syslogger.c:1465 replication/logical/origin.c:563 replication/logical/reorderbuffer.c:3132 replication/logical/snapbuild.c:1682 replication/logical/snapbuild.c:2127 replication/slot.c:1672 storage/file/fd.c:754 storage/file/fd.c:3136 storage/file/fd.c:3198 storage/file/reinit.c:255 storage/ipc/dsm.c:302 storage/smgr/md.c:355 storage/smgr/md.c:405 storage/sync/sync.c:229 utils/time/snapmgr.c:1703 +#: access/heap/rewriteheap.c:1249 access/transam/twophase.c:1690 access/transam/xlogarchive.c:118 access/transam/xlogarchive.c:421 postmaster/postmaster.c:1092 postmaster/syslogger.c:1465 replication/logical/origin.c:563 replication/logical/reorderbuffer.c:3132 replication/logical/snapbuild.c:1682 replication/logical/snapbuild.c:2127 replication/slot.c:1672 storage/file/fd.c:754 storage/file/fd.c:3136 storage/file/fd.c:3198 storage/file/reinit.c:255 storage/ipc/dsm.c:302 storage/smgr/md.c:358 storage/smgr/md.c:408 storage/sync/sync.c:229 utils/time/snapmgr.c:1703 #, c-format msgid "could not remove file \"%s\": %m" msgstr "n'a pas pu supprimer le fichier « %s » : %m" @@ -1028,7 +1028,7 @@ msgstr[0] "%u page est entièrement vide.\n" msgstr[1] "%u pages sont entièrement vides.\n" -#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3639 commands/indexcmds.c:3657 +#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3656 commands/indexcmds.c:3674 #, c-format msgid "%s." msgstr "%s." @@ -1138,7 +1138,7 @@ msgid "index access method \"%s\" does not have a handler" msgstr "la méthode d'accès « %s » n'a pas de handler" -#: access/index/indexam.c:142 catalog/objectaddress.c:1260 commands/indexcmds.c:2647 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16142 commands/tablecmds.c:17642 +#: access/index/indexam.c:142 catalog/objectaddress.c:1260 commands/indexcmds.c:2664 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16142 commands/tablecmds.c:17646 #, c-format msgid "\"%s\" is not an index" msgstr "« %s » n'est pas un index" @@ -1568,12 +1568,12 @@ msgid "transaction identifier \"%s\" is already in use" msgstr "l'identifiant de la transaction « %s » est déjà utilisé" -#: access/transam/twophase.c:417 access/transam/twophase.c:2450 +#: access/transam/twophase.c:417 access/transam/twophase.c:2483 #, c-format msgid "maximum number of prepared transactions reached" msgstr "nombre maximum de transactions préparées obtenu" -#: access/transam/twophase.c:418 access/transam/twophase.c:2451 +#: access/transam/twophase.c:418 access/transam/twophase.c:2484 #, c-format msgid "Increase max_prepared_transactions (currently %d)." msgstr "Augmentez max_prepared_transactions (actuellement %d)." @@ -1713,6 +1713,21 @@ msgid "corrupted two-phase state in memory for transaction %u" msgstr "mémoire d'état de la validation en deux phases pour la transaction %u corrompue" +#: access/transam/twophase.c:2465 +#, c-format +msgid "could not recover two-phase state file for transaction %u" +msgstr "n'a pas pu récupérer le fichier d'état de validation en deux phases pour la transaction %u" + +#: access/transam/twophase.c:2467 +#, c-format +msgid "Two-phase state file has been found in WAL record %X/%X, but this transaction has already been restored from disk." +msgstr "Le fichier d'état de validation en deux phases a été trouvé dans l'enregistrement %X/%X des journaux de transactions, mais cette transaction a déjà été restaurée du disque." + +#: access/transam/twophase.c:2476 jit/jit.c:205 utils/fmgr/dfmgr.c:209 utils/fmgr/dfmgr.c:417 utils/fmgr/dfmgr.c:465 +#, c-format +msgid "could not access file \"%s\": %m" +msgstr "n'a pas pu accéder au fichier « %s » : %m" + #: access/transam/varsup.c:127 #, c-format msgid "database is not accepting commands to avoid wraparound data loss in database \"%s\"" @@ -1925,7 +1940,7 @@ msgid "creating missing WAL directory \"%s\"" msgstr "création du répertoire manquant pour les journaux de transactions « %s »" -#: access/transam/xlog.c:4305 commands/dbcommands.c:2208 +#: access/transam/xlog.c:4305 commands/dbcommands.c:2278 #, c-format msgid "could not create missing directory \"%s\": %m" msgstr "n'a pas pu créer le répertoire « %s » manquant : %m" @@ -2378,7 +2393,7 @@ msgid "ignoring file \"%s\" because no file \"%s\" exists" msgstr "ignore le fichier « %s » car le fichier « %s » n'existe pas" -#: access/transam/xlog.c:6671 access/transam/xlog.c:12123 +#: access/transam/xlog.c:6671 access/transam/xlog.c:12127 #, c-format msgid "File \"%s\" was renamed to \"%s\"." msgstr "Le fichier « %s » a été renommé en « %s »." @@ -2512,190 +2527,190 @@ msgid "selected new timeline ID: %u" msgstr "identifiant d'un timeline nouvellement sélectionné : %u" -#: access/transam/xlog.c:8108 +#: access/transam/xlog.c:8112 #, c-format msgid "unexpected directory entry \"%s\" found in %s" msgstr "entrée « %s » du répertoire inattendu trouvé dans %s" -#: access/transam/xlog.c:8110 +#: access/transam/xlog.c:8114 #, c-format msgid "All directory entries in pg_tblspc/ should be symbolic links." msgstr "Toutes les entrées du répertoire pg_tblspc devraient être des liens symboliques." -#: access/transam/xlog.c:8111 +#: access/transam/xlog.c:8115 #, c-format msgid "Remove those directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete." msgstr "Supprimer ces répertoires, ou configurer allow_in_place_tablespaces à ON pour que la restauration se termine." -#: access/transam/xlog.c:8195 +#: access/transam/xlog.c:8199 #, c-format msgid "consistent recovery state reached at %X/%X" msgstr "état de restauration cohérent atteint à %X/%X" -#: access/transam/xlog.c:8405 +#: access/transam/xlog.c:8409 #, c-format msgid "invalid primary checkpoint link in control file" msgstr "lien du point de vérification primaire invalide dans le fichier de contrôle" -#: access/transam/xlog.c:8409 +#: access/transam/xlog.c:8413 #, c-format msgid "invalid checkpoint link in backup_label file" msgstr "lien du point de vérification invalide dans le fichier backup_label" -#: access/transam/xlog.c:8427 +#: access/transam/xlog.c:8431 #, c-format msgid "invalid primary checkpoint record" msgstr "enregistrement du point de vérification primaire invalide" -#: access/transam/xlog.c:8431 +#: access/transam/xlog.c:8435 #, c-format msgid "invalid checkpoint record" msgstr "enregistrement du point de vérification invalide" -#: access/transam/xlog.c:8442 +#: access/transam/xlog.c:8446 #, c-format msgid "invalid resource manager ID in primary checkpoint record" msgstr "identifiant du gestionnaire de ressource invalide dans l'enregistrement primaire du point de vérification" -#: access/transam/xlog.c:8446 +#: access/transam/xlog.c:8450 #, c-format msgid "invalid resource manager ID in checkpoint record" msgstr "identifiant du gestionnaire de ressource invalide dans l'enregistrement du point de vérification" -#: access/transam/xlog.c:8459 +#: access/transam/xlog.c:8463 #, c-format msgid "invalid xl_info in primary checkpoint record" msgstr "xl_info invalide dans l'enregistrement du point de vérification primaire" -#: access/transam/xlog.c:8463 +#: access/transam/xlog.c:8467 #, c-format msgid "invalid xl_info in checkpoint record" msgstr "xl_info invalide dans l'enregistrement du point de vérification" -#: access/transam/xlog.c:8474 +#: access/transam/xlog.c:8478 #, c-format msgid "invalid length of primary checkpoint record" msgstr "longueur invalide de l'enregistrement primaire du point de vérification" -#: access/transam/xlog.c:8478 +#: access/transam/xlog.c:8482 #, c-format msgid "invalid length of checkpoint record" msgstr "longueur invalide de l'enregistrement du point de vérification" -#: access/transam/xlog.c:8658 +#: access/transam/xlog.c:8662 #, c-format msgid "shutting down" msgstr "arrêt en cours" -#: access/transam/xlog.c:8965 +#: access/transam/xlog.c:8969 #, c-format msgid "checkpoint skipped because system is idle" msgstr "checkpoint ignoré car le système est inactif" -#: access/transam/xlog.c:9175 +#: access/transam/xlog.c:9179 #, c-format msgid "concurrent write-ahead log activity while database system is shutting down" msgstr "" "activité en cours du journal de transactions alors que le système de bases\n" "de données est en cours d'arrêt" -#: access/transam/xlog.c:9487 +#: access/transam/xlog.c:9491 #, c-format msgid "skipping restartpoint, recovery has already ended" msgstr "restartpoint ignoré, la récupération est déjà terminée" -#: access/transam/xlog.c:9510 +#: access/transam/xlog.c:9514 #, c-format msgid "skipping restartpoint, already performed at %X/%X" msgstr "ignore le point de redémarrage, déjà réalisé à %X/%X" -#: access/transam/xlog.c:9700 +#: access/transam/xlog.c:9704 #, c-format msgid "recovery restart point at %X/%X" msgstr "la ré-exécution en restauration commence à %X/%X" -#: access/transam/xlog.c:9702 +#: access/transam/xlog.c:9706 #, c-format msgid "Last completed transaction was at log time %s." msgstr "La dernière transaction a eu lieu à %s (moment de la journalisation)." -#: access/transam/xlog.c:9950 +#: access/transam/xlog.c:9954 #, c-format msgid "restore point \"%s\" created at %X/%X" msgstr "point de restauration « %s » créé à %X/%X" -#: access/transam/xlog.c:10095 +#: access/transam/xlog.c:10099 #, c-format msgid "unexpected previous timeline ID %u (current timeline ID %u) in checkpoint record" msgstr "identifiant de timeline précédent %u inattendu (identifiant de la timeline courante %u) dans l'enregistrement du point de vérification" -#: access/transam/xlog.c:10104 +#: access/transam/xlog.c:10108 #, c-format msgid "unexpected timeline ID %u (after %u) in checkpoint record" msgstr "" "identifiant timeline %u inattendu (après %u) dans l'enregistrement du point\n" "de vérification" -#: access/transam/xlog.c:10120 +#: access/transam/xlog.c:10124 #, c-format msgid "unexpected timeline ID %u in checkpoint record, before reaching minimum recovery point %X/%X on timeline %u" msgstr "identifiant timeline %u inattendu dans l'enregistrement du checkpoint, avant d'atteindre le point de restauration minimum %X/%X sur la timeline %u" -#: access/transam/xlog.c:10196 +#: access/transam/xlog.c:10200 #, c-format msgid "online backup was canceled, recovery cannot continue" msgstr "la sauvegarde en ligne a été annulée, la restauration ne peut pas continuer" -#: access/transam/xlog.c:10252 access/transam/xlog.c:10308 access/transam/xlog.c:10338 +#: access/transam/xlog.c:10256 access/transam/xlog.c:10312 access/transam/xlog.c:10342 #, c-format msgid "unexpected timeline ID %u (should be %u) in checkpoint record" msgstr "" "identifiant timeline %u inattendu (devrait être %u) dans l'enregistrement du\n" "point de vérification" -#: access/transam/xlog.c:10498 +#: access/transam/xlog.c:10502 #, c-format msgid "successfully skipped missing contrecord at %X/%X, overwritten at %s" msgstr "a ignoré avec succès le contrecord manquant à %X/%X, surchargé à %s" -#: access/transam/xlog.c:10691 +#: access/transam/xlog.c:10695 #, c-format msgid "could not fsync write-through file \"%s\": %m" msgstr "n'a pas pu synchroniser sur disque (fsync) le fichier %s : %m" -#: access/transam/xlog.c:10697 +#: access/transam/xlog.c:10701 #, c-format msgid "could not fdatasync file \"%s\": %m" msgstr "n'a pas pu synchroniser sur disque (fdatasync) le fichier « %s » : %m" -#: access/transam/xlog.c:10796 access/transam/xlog.c:11354 access/transam/xlogfuncs.c:275 access/transam/xlogfuncs.c:302 access/transam/xlogfuncs.c:341 access/transam/xlogfuncs.c:362 access/transam/xlogfuncs.c:383 +#: access/transam/xlog.c:10800 access/transam/xlog.c:11358 access/transam/xlogfuncs.c:275 access/transam/xlogfuncs.c:302 access/transam/xlogfuncs.c:341 access/transam/xlogfuncs.c:362 access/transam/xlogfuncs.c:383 #, c-format msgid "WAL control functions cannot be executed during recovery." msgstr "les fonctions de contrôle des journaux de transactions ne peuvent pas être exécutées lors de la restauration." -#: access/transam/xlog.c:10805 access/transam/xlog.c:11363 +#: access/transam/xlog.c:10809 access/transam/xlog.c:11367 #, c-format msgid "WAL level not sufficient for making an online backup" msgstr "Le niveau de journalisation n'est pas suffisant pour faire une sauvegarde en ligne" -#: access/transam/xlog.c:10806 access/transam/xlog.c:11364 access/transam/xlogfuncs.c:308 +#: access/transam/xlog.c:10810 access/transam/xlog.c:11368 access/transam/xlogfuncs.c:308 #, c-format msgid "wal_level must be set to \"replica\" or \"logical\" at server start." msgstr "" "wal_level doit être configuré à « replica » ou « logical »\n" "au démarrage du serveur." -#: access/transam/xlog.c:10811 +#: access/transam/xlog.c:10815 #, c-format msgid "backup label too long (max %d bytes)" msgstr "label de sauvegarde trop long (%d octets maximum)" -#: access/transam/xlog.c:10848 access/transam/xlog.c:11153 access/transam/xlog.c:11191 +#: access/transam/xlog.c:10852 access/transam/xlog.c:11157 access/transam/xlog.c:11195 #, c-format msgid "a backup is already in progress" msgstr "une sauvegarde est déjà en cours" -#: access/transam/xlog.c:10849 +#: access/transam/xlog.c:10853 #, c-format msgid "Run pg_stop_backup() and try again." msgstr "Exécutez pg_stop_backup() et tentez de nouveau." @@ -2705,12 +2720,12 @@ # * (i.e., since last restartpoint used as backup starting # * checkpoint) contain full-page writes. # */ -#: access/transam/xlog.c:10945 +#: access/transam/xlog.c:10949 #, c-format msgid "WAL generated with full_page_writes=off was replayed since last restartpoint" msgstr "Un journal de transaction généré avec full_page_writes=off a été rejoué depuis le dernier point de reprise (restartpoint)" -#: access/transam/xlog.c:10947 access/transam/xlog.c:11559 +#: access/transam/xlog.c:10951 access/transam/xlog.c:11563 #, c-format msgid "This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master, and then try an online backup again." msgstr "" @@ -2718,162 +2733,162 @@ "corrompue et ne doit pas être utilisée. Activez full_page_writes et lancez\n" "CHECKPOINT sur le maître, puis recommencez la sauvegarde." -#: access/transam/xlog.c:11050 replication/basebackup.c:1429 utils/adt/misc.c:371 +#: access/transam/xlog.c:11054 replication/basebackup.c:1429 utils/adt/misc.c:371 #, c-format msgid "symbolic link \"%s\" target is too long" msgstr "la cible du lien symbolique « %s » est trop long" -#: access/transam/xlog.c:11103 commands/tablespace.c:385 commands/tablespace.c:561 replication/basebackup.c:1444 utils/adt/misc.c:379 +#: access/transam/xlog.c:11107 commands/tablespace.c:385 commands/tablespace.c:561 replication/basebackup.c:1444 utils/adt/misc.c:379 #, c-format msgid "tablespaces are not supported on this platform" msgstr "les tablespaces ne sont pas supportés sur cette plateforme" -#: access/transam/xlog.c:11154 access/transam/xlog.c:11192 +#: access/transam/xlog.c:11158 access/transam/xlog.c:11196 #, c-format msgid "If you're sure there is no backup in progress, remove file \"%s\" and try again." msgstr "" "Si vous êtes certain qu'aucune sauvegarde n'est en cours, supprimez le\n" "fichier « %s » et recommencez de nouveau." -#: access/transam/xlog.c:11379 +#: access/transam/xlog.c:11383 #, c-format msgid "exclusive backup not in progress" msgstr "une sauvegarde exclusive n'est pas en cours" -#: access/transam/xlog.c:11406 +#: access/transam/xlog.c:11410 #, c-format msgid "a backup is not in progress" msgstr "aucune sauvegarde n'est en cours" -#: access/transam/xlog.c:11492 access/transam/xlog.c:11505 access/transam/xlog.c:11896 access/transam/xlog.c:11902 access/transam/xlog.c:11950 access/transam/xlog.c:12023 access/transam/xlogfuncs.c:692 +#: access/transam/xlog.c:11496 access/transam/xlog.c:11509 access/transam/xlog.c:11900 access/transam/xlog.c:11906 access/transam/xlog.c:11954 access/transam/xlog.c:12027 access/transam/xlogfuncs.c:692 #, c-format msgid "invalid data in file \"%s\"" msgstr "données invalides dans le fichier « %s »" -#: access/transam/xlog.c:11509 replication/basebackup.c:1277 +#: access/transam/xlog.c:11513 replication/basebackup.c:1277 #, c-format msgid "the standby was promoted during online backup" msgstr "le standby a été promu lors de la sauvegarde en ligne" -#: access/transam/xlog.c:11510 replication/basebackup.c:1278 +#: access/transam/xlog.c:11514 replication/basebackup.c:1278 #, c-format msgid "This means that the backup being taken is corrupt and should not be used. Try taking another online backup." msgstr "" "Cela signifie que la sauvegarde en cours de réalisation est corrompue et ne\n" "doit pas être utilisée. Recommencez la sauvegarde." -#: access/transam/xlog.c:11557 +#: access/transam/xlog.c:11561 #, c-format msgid "WAL generated with full_page_writes=off was replayed during online backup" msgstr "Un journal de transaction généré avec full_page_writes=off a été rejoué pendant la sauvegarde en ligne" -#: access/transam/xlog.c:11677 +#: access/transam/xlog.c:11681 #, c-format msgid "base backup done, waiting for required WAL segments to be archived" msgstr "backup de base terminé, en attente de l'archivage des journaux de transactions nécessaires" -#: access/transam/xlog.c:11689 +#: access/transam/xlog.c:11693 #, c-format msgid "still waiting for all required WAL segments to be archived (%d seconds elapsed)" msgstr "toujours en attente de la fin de l'archivage de tous les segments de journaux de transactions requis (%d secondes passées)" -#: access/transam/xlog.c:11691 +#: access/transam/xlog.c:11695 #, c-format msgid "Check that your archive_command is executing properly. You can safely cancel this backup, but the database backup will not be usable without all the WAL segments." msgstr "Vérifiez que votre archive_command s'exécute correctement. Vous pouvez annuler cette sauvegarde sans souci, mais elle ne sera pas utilisable sans tous les segments WAL." -#: access/transam/xlog.c:11698 +#: access/transam/xlog.c:11702 #, c-format msgid "all required WAL segments have been archived" msgstr "tous les journaux de transactions requis ont été archivés" -#: access/transam/xlog.c:11702 +#: access/transam/xlog.c:11706 #, c-format msgid "WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backup" msgstr "L'archivage des journaux de transactions n'est pas activé ; vous devez vous assurer que tous les des journaux de transactions requis sont copiés par d'autres moyens pour terminer la sauvegarde" -#: access/transam/xlog.c:11757 +#: access/transam/xlog.c:11761 #, c-format msgid "aborting backup due to backend exiting before pg_stop_backup was called" msgstr "annulation de la sauvegarde due à la déconnexion du processus serveur avant que pg_stop_backup ne soit appelé" -#: access/transam/xlog.c:11933 +#: access/transam/xlog.c:11937 #, c-format msgid "backup time %s in file \"%s\"" msgstr "heure de sauvegarde %s dans le fichier « %s »" -#: access/transam/xlog.c:11938 +#: access/transam/xlog.c:11942 #, c-format msgid "backup label %s in file \"%s\"" msgstr "label de sauvegarde %s dans le fichier « %s »" -#: access/transam/xlog.c:11951 +#: access/transam/xlog.c:11955 #, c-format msgid "Timeline ID parsed is %u, but expected %u." msgstr "L'identifiant de timeline parsé est %u, mais %u était attendu." -#: access/transam/xlog.c:11955 +#: access/transam/xlog.c:11959 #, c-format msgid "backup timeline %u in file \"%s\"" msgstr "timeline de sauvegarde %u dans le fichier « %s »" #. translator: %s is a WAL record description -#: access/transam/xlog.c:12063 +#: access/transam/xlog.c:12067 #, c-format msgid "WAL redo at %X/%X for %s" msgstr "rejeu des WAL à %X/%X pour %s" -#: access/transam/xlog.c:12112 +#: access/transam/xlog.c:12116 #, c-format msgid "online backup mode was not canceled" msgstr "le mode de sauvegarde en ligne n'a pas été annulé" -#: access/transam/xlog.c:12113 +#: access/transam/xlog.c:12117 #, c-format msgid "File \"%s\" could not be renamed to \"%s\": %m." msgstr "Le fichier « %s » n'a pas pu être renommé en « %s » : %m." -#: access/transam/xlog.c:12122 access/transam/xlog.c:12134 access/transam/xlog.c:12144 +#: access/transam/xlog.c:12126 access/transam/xlog.c:12138 access/transam/xlog.c:12148 #, c-format msgid "online backup mode canceled" msgstr "mode de sauvegarde en ligne annulé" -#: access/transam/xlog.c:12135 +#: access/transam/xlog.c:12139 #, c-format msgid "Files \"%s\" and \"%s\" were renamed to \"%s\" and \"%s\", respectively." msgstr "Les fichiers « %s » et « %s » sont renommés respectivement « %s » et « %s »." -#: access/transam/xlog.c:12145 +#: access/transam/xlog.c:12149 #, c-format msgid "File \"%s\" was renamed to \"%s\", but file \"%s\" could not be renamed to \"%s\": %m." msgstr "Le fichier « %s » a été renommé en « %s », mais le fichier « %s » n'a pas pu être renommé en « %s » : %m." -#: access/transam/xlog.c:12278 access/transam/xlogutils.c:971 +#: access/transam/xlog.c:12282 access/transam/xlogutils.c:971 #, c-format msgid "could not read from log segment %s, offset %u: %m" msgstr "n'a pas pu lire le journal de transactions %s, décalage %u : %m" -#: access/transam/xlog.c:12284 access/transam/xlogutils.c:978 +#: access/transam/xlog.c:12288 access/transam/xlogutils.c:978 #, c-format msgid "could not read from log segment %s, offset %u: read %d of %zu" msgstr "n'a pas pu lire à partir du segment %s du journal de transactions, décalage %u: lu %d sur %zu" -#: access/transam/xlog.c:12827 +#: access/transam/xlog.c:12831 #, c-format msgid "WAL receiver process shutdown requested" msgstr "le processus wal receiver a reçu une demande d'arrêt" -#: access/transam/xlog.c:12933 +#: access/transam/xlog.c:12937 #, c-format msgid "received promote request" msgstr "a reçu une demande de promotion" -#: access/transam/xlog.c:12946 +#: access/transam/xlog.c:12950 #, c-format msgid "promote trigger file found: %s" msgstr "fichier trigger de promotion trouvé : %s" -#: access/transam/xlog.c:12955 +#: access/transam/xlog.c:12959 #, c-format msgid "could not stat promote trigger file \"%s\": %m" msgstr "n'a pas pu récupérer les propriétés du fichier trigger pour la promotion « %s » : %m" @@ -3288,8 +3303,8 @@ msgid "large object %u does not exist" msgstr "le « Large Object » %u n'existe pas" -#: catalog/aclchk.c:910 catalog/aclchk.c:919 commands/collationcmds.c:118 commands/copy.c:1137 commands/copy.c:1157 commands/copy.c:1166 commands/copy.c:1175 commands/copy.c:1184 commands/copy.c:1193 commands/copy.c:1202 commands/copy.c:1211 commands/copy.c:1229 commands/copy.c:1245 commands/copy.c:1265 commands/copy.c:1282 commands/dbcommands.c:158 commands/dbcommands.c:167 commands/dbcommands.c:176 commands/dbcommands.c:185 commands/dbcommands.c:194 commands/dbcommands.c:203 commands/dbcommands.c:212 commands/dbcommands.c:221 commands/dbcommands.c:230 commands/dbcommands.c:239 commands/dbcommands.c:261 commands/dbcommands.c:1503 commands/dbcommands.c:1512 -#: commands/dbcommands.c:1521 commands/dbcommands.c:1530 commands/extension.c:1735 commands/extension.c:1745 commands/extension.c:1755 commands/extension.c:3055 commands/foreigncmds.c:539 commands/foreigncmds.c:548 commands/functioncmds.c:572 commands/functioncmds.c:738 commands/functioncmds.c:747 commands/functioncmds.c:756 commands/functioncmds.c:765 commands/functioncmds.c:2017 commands/functioncmds.c:2025 commands/publicationcmds.c:87 commands/publicationcmds.c:130 commands/sequence.c:1275 commands/sequence.c:1285 commands/sequence.c:1295 commands/sequence.c:1305 commands/sequence.c:1315 commands/sequence.c:1325 commands/sequence.c:1335 commands/sequence.c:1345 +#: catalog/aclchk.c:910 catalog/aclchk.c:919 commands/collationcmds.c:118 commands/copy.c:1137 commands/copy.c:1157 commands/copy.c:1166 commands/copy.c:1175 commands/copy.c:1184 commands/copy.c:1193 commands/copy.c:1202 commands/copy.c:1211 commands/copy.c:1229 commands/copy.c:1245 commands/copy.c:1265 commands/copy.c:1282 commands/dbcommands.c:158 commands/dbcommands.c:167 commands/dbcommands.c:176 commands/dbcommands.c:185 commands/dbcommands.c:194 commands/dbcommands.c:203 commands/dbcommands.c:212 commands/dbcommands.c:221 commands/dbcommands.c:230 commands/dbcommands.c:239 commands/dbcommands.c:261 commands/dbcommands.c:1529 commands/dbcommands.c:1538 +#: commands/dbcommands.c:1547 commands/dbcommands.c:1556 commands/extension.c:1735 commands/extension.c:1745 commands/extension.c:1755 commands/extension.c:3052 commands/foreigncmds.c:539 commands/foreigncmds.c:548 commands/functioncmds.c:572 commands/functioncmds.c:738 commands/functioncmds.c:747 commands/functioncmds.c:756 commands/functioncmds.c:765 commands/functioncmds.c:2017 commands/functioncmds.c:2025 commands/publicationcmds.c:87 commands/publicationcmds.c:130 commands/sequence.c:1275 commands/sequence.c:1285 commands/sequence.c:1295 commands/sequence.c:1305 commands/sequence.c:1315 commands/sequence.c:1325 commands/sequence.c:1335 commands/sequence.c:1345 #: commands/sequence.c:1355 commands/subscriptioncmds.c:105 commands/subscriptioncmds.c:115 commands/subscriptioncmds.c:125 commands/subscriptioncmds.c:135 commands/subscriptioncmds.c:151 commands/subscriptioncmds.c:162 commands/subscriptioncmds.c:176 commands/tablecmds.c:7287 commands/typecmds.c:322 commands/typecmds.c:1357 commands/typecmds.c:1366 commands/typecmds.c:1374 commands/typecmds.c:1382 commands/typecmds.c:1390 commands/user.c:133 commands/user.c:147 commands/user.c:156 commands/user.c:165 commands/user.c:174 commands/user.c:183 commands/user.c:192 commands/user.c:201 commands/user.c:210 commands/user.c:219 commands/user.c:228 commands/user.c:237 commands/user.c:246 #: commands/user.c:582 commands/user.c:590 commands/user.c:598 commands/user.c:606 commands/user.c:614 commands/user.c:622 commands/user.c:630 commands/user.c:638 commands/user.c:647 commands/user.c:655 commands/user.c:663 parser/parse_utilcmd.c:414 replication/pgoutput/pgoutput.c:142 replication/pgoutput/pgoutput.c:163 replication/walsender.c:891 replication/walsender.c:902 replication/walsender.c:912 #, c-format @@ -3797,7 +3812,7 @@ msgid "publication with OID %u does not exist" msgstr "la publication d'OID %u n'existe pas" -#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1116 +#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1117 #, c-format msgid "subscription with OID %u does not exist" msgstr "la souscription d'OID %u n'existe pas" @@ -3882,7 +3897,7 @@ msgid "cannot drop %s because other objects depend on it" msgstr "n'a pas pu supprimer %s car d'autres objets en dépendent" -#: catalog/dependency.c:1203 catalog/dependency.c:1210 catalog/dependency.c:1222 commands/tablecmds.c:1259 commands/tablecmds.c:13374 commands/tablespace.c:464 commands/user.c:1095 commands/view.c:509 libpq/auth.c:334 replication/syncrep.c:1032 storage/lmgr/deadlock.c:1154 storage/lmgr/proc.c:1354 utils/misc/guc.c:6783 utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11004 utils/misc/guc.c:11038 utils/misc/guc.c:11072 utils/misc/guc.c:11115 utils/misc/guc.c:11157 +#: catalog/dependency.c:1203 catalog/dependency.c:1210 catalog/dependency.c:1222 commands/tablecmds.c:1259 commands/tablecmds.c:13374 commands/tablespace.c:464 commands/user.c:1095 commands/view.c:509 libpq/auth.c:334 replication/syncrep.c:1032 storage/lmgr/deadlock.c:1153 storage/lmgr/proc.c:1356 utils/misc/guc.c:6783 utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11004 utils/misc/guc.c:11038 utils/misc/guc.c:11072 utils/misc/guc.c:11115 utils/misc/guc.c:11157 #, c-format msgid "%s" msgstr "%s" @@ -3962,7 +3977,7 @@ msgid "no collation was derived for column \"%s\" with collatable type %s" msgstr "aucun collationnement n'a été dérivé pour la colonne « %s » de type collationnable %s" -#: catalog/heap.c:1162 catalog/index.c:866 commands/tablecmds.c:3573 +#: catalog/heap.c:1162 catalog/index.c:867 commands/tablecmds.c:3573 #, c-format msgid "relation \"%s\" already exists" msgstr "la relation « %s » existe déjà" @@ -3992,7 +4007,7 @@ msgid "check constraint \"%s\" already exists" msgstr "la contrainte de vérification « %s » existe déjà" -#: catalog/heap.c:2855 catalog/index.c:880 catalog/pg_constraint.c:668 commands/tablecmds.c:8318 +#: catalog/heap.c:2855 catalog/index.c:881 catalog/pg_constraint.c:668 commands/tablecmds.c:8318 #, c-format msgid "constraint \"%s\" for relation \"%s\" already exists" msgstr "la contrainte « %s » de la relation « %s » existe déjà" @@ -4042,12 +4057,12 @@ msgid "generation expression is not immutable" msgstr "l'expression de génération n'est pas immuable" -#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1236 +#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1238 #, c-format msgid "column \"%s\" is of type %s but default expression is of type %s" msgstr "la colonne « %s » est de type %s alors que l'expression par défaut est de type %s" -#: catalog/heap.c:3088 commands/prepare.c:371 parser/parse_node.c:412 parser/parse_target.c:588 parser/parse_target.c:868 parser/parse_target.c:878 rewrite/rewriteHandler.c:1241 +#: catalog/heap.c:3088 commands/prepare.c:371 parser/parse_node.c:412 parser/parse_target.c:588 parser/parse_target.c:868 parser/parse_target.c:878 rewrite/rewriteHandler.c:1243 #, c-format msgid "You will need to rewrite or cast the expression." msgstr "Vous devez réécrire l'expression ou lui appliquer une transformation de type." @@ -4084,101 +4099,101 @@ msgid "Truncate table \"%s\" at the same time, or use TRUNCATE ... CASCADE." msgstr "Tronquez la table « %s » en même temps, ou utilisez TRUNCATE ... CASCADE." -#: catalog/index.c:220 parser/parse_utilcmd.c:2142 +#: catalog/index.c:221 parser/parse_utilcmd.c:2142 #, c-format msgid "multiple primary keys for table \"%s\" are not allowed" msgstr "les clés primaires multiples ne sont pas autorisées pour la table « %s »" -#: catalog/index.c:238 +#: catalog/index.c:239 #, c-format msgid "primary keys cannot be expressions" msgstr "les clés primaires ne peuvent pas être des expressions" -#: catalog/index.c:255 +#: catalog/index.c:256 #, c-format msgid "primary key column \"%s\" is not marked NOT NULL" msgstr "la colonne de clé primaire « %s » n'est pas marquée NOT NULL" -#: catalog/index.c:765 catalog/index.c:1930 +#: catalog/index.c:766 catalog/index.c:1931 #, c-format msgid "user-defined indexes on system catalog tables are not supported" msgstr "les index définis par l'utilisateur sur les tables du catalogue système ne sont pas supportés" -#: catalog/index.c:805 +#: catalog/index.c:806 #, c-format msgid "nondeterministic collations are not supported for operator class \"%s\"" msgstr "les collationnements non-déterministes ne sont pas supportés pour la classe d'opérateurs « %s »" -#: catalog/index.c:820 +#: catalog/index.c:821 #, c-format msgid "concurrent index creation on system catalog tables is not supported" msgstr "" "la création en parallèle d'un index sur les tables du catalogue système\n" "n'est pas supportée" -#: catalog/index.c:829 catalog/index.c:1282 +#: catalog/index.c:830 catalog/index.c:1283 #, c-format msgid "concurrent index creation for exclusion constraints is not supported" msgstr "la création de manière concurrente d'un index pour les contraintes d'exclusion n'est pas supportée" -#: catalog/index.c:838 +#: catalog/index.c:839 #, c-format msgid "shared indexes cannot be created after initdb" msgstr "les index partagés ne peuvent pas être créés après initdb" -#: catalog/index.c:858 commands/createas.c:264 commands/sequence.c:162 parser/parse_utilcmd.c:219 +#: catalog/index.c:859 commands/createas.c:264 commands/sequence.c:162 parser/parse_utilcmd.c:219 #, c-format msgid "relation \"%s\" already exists, skipping" msgstr "la relation « %s » existe déjà, poursuite du traitement" -#: catalog/index.c:908 +#: catalog/index.c:909 #, c-format msgid "pg_class index OID value not set when in binary upgrade mode" msgstr "OID de l'index de pg_class non configuré en mode de mise à jour binaire" -#: catalog/index.c:2226 +#: catalog/index.c:2227 #, c-format msgid "DROP INDEX CONCURRENTLY must be first action in transaction" msgstr "DROP INDEX CONCURRENTLY doit être la première action dans une transaction" -#: catalog/index.c:2957 +#: catalog/index.c:2958 #, c-format msgid "building index \"%s\" on table \"%s\" serially" msgstr "construction de l'index « %s » sur la table « %s » séquentiellement" -#: catalog/index.c:2962 +#: catalog/index.c:2963 #, c-format msgid "building index \"%s\" on table \"%s\" with request for %d parallel worker" msgid_plural "building index \"%s\" on table \"%s\" with request for %d parallel workers" msgstr[0] "construction de l'index « %s » sur la table « %s » avec une demande de %d processus parallèle" msgstr[1] "construction de l'index « %s » sur la table « %s » avec une demande de %d processus parallèles" -#: catalog/index.c:3595 +#: catalog/index.c:3597 #, c-format msgid "cannot reindex temporary tables of other sessions" msgstr "ne peut pas ré-indexer les tables temporaires des autres sessions" -#: catalog/index.c:3606 commands/indexcmds.c:3134 +#: catalog/index.c:3608 commands/indexcmds.c:3151 #, c-format msgid "cannot reindex invalid index on TOAST table" msgstr "ne peut pas réindexer un index invalide sur une table TOAST" -#: catalog/index.c:3728 +#: catalog/index.c:3730 #, c-format msgid "index \"%s\" was reindexed" msgstr "l'index « %s » a été réindexée" -#: catalog/index.c:3810 commands/indexcmds.c:3155 +#: catalog/index.c:3812 commands/indexcmds.c:3172 #, c-format msgid "REINDEX of partitioned tables is not yet implemented, skipping \"%s\"" msgstr "REINDEX n'est pas encore implémenté pour les tables partitionnées, « %s » ignoré" -#: catalog/index.c:3865 +#: catalog/index.c:3867 #, c-format msgid "cannot reindex invalid index \"%s.%s\" on TOAST table, skipping" msgstr "ne peut pas réindexer l'index invalide « %s.%s » sur une table TOAST, ignoré" -#: catalog/namespace.c:258 catalog/namespace.c:462 catalog/namespace.c:554 commands/trigger.c:5122 +#: catalog/namespace.c:258 catalog/namespace.c:462 catalog/namespace.c:554 commands/trigger.c:5153 #, c-format msgid "cross-database references are not implemented: \"%s.%s.%s\"" msgstr "les références entre bases de données ne sont pas implémentées : « %s.%s.%s »" @@ -4273,7 +4288,7 @@ msgid "cannot move objects into or out of TOAST schema" msgstr "ne peut pas déplacer les objets dans ou à partir des schémas TOAST" -#: catalog/namespace.c:3053 commands/schemacmds.c:268 commands/schemacmds.c:348 commands/tablecmds.c:1204 +#: catalog/namespace.c:3053 commands/schemacmds.c:285 commands/schemacmds.c:365 commands/tablecmds.c:1204 #, c-format msgid "schema \"%s\" does not exist" msgstr "le schéma « %s » n'existe pas" @@ -4283,32 +4298,32 @@ msgid "improper relation name (too many dotted names): %s" msgstr "nom de relation incorrecte (trop de points entre les noms) : %s" -#: catalog/namespace.c:3647 +#: catalog/namespace.c:3651 #, c-format msgid "collation \"%s\" for encoding \"%s\" does not exist" msgstr "le collationnement « %s » pour l'encodage « %s » n'existe pas" -#: catalog/namespace.c:3702 +#: catalog/namespace.c:3706 #, c-format msgid "conversion \"%s\" does not exist" msgstr "la conversion « %s » n'existe pas" -#: catalog/namespace.c:3966 +#: catalog/namespace.c:3970 #, c-format msgid "permission denied to create temporary tables in database \"%s\"" msgstr "droit refusé pour la création de tables temporaires dans la base de données « %s »" -#: catalog/namespace.c:3982 +#: catalog/namespace.c:3986 #, c-format msgid "cannot create temporary tables during recovery" msgstr "ne peut pas créer des tables temporaires lors de la restauration" -#: catalog/namespace.c:3988 +#: catalog/namespace.c:3992 #, c-format msgid "cannot create temporary tables during a parallel operation" msgstr "ne peut pas créer de tables temporaires pendant une opération parallèle" -#: catalog/namespace.c:4289 commands/tablespace.c:1216 commands/variable.c:64 utils/misc/guc.c:11189 utils/misc/guc.c:11267 +#: catalog/namespace.c:4293 commands/tablespace.c:1216 commands/variable.c:64 utils/misc/guc.c:11189 utils/misc/guc.c:11267 #, c-format msgid "List syntax is invalid." msgstr "La syntaxe de la liste est invalide." @@ -4943,12 +4958,12 @@ msgid "default conversion for %s to %s already exists" msgstr "la conversion par défaut de %s vers %s existe déjà" -#: catalog/pg_depend.c:176 commands/extension.c:3332 +#: catalog/pg_depend.c:176 commands/extension.c:3329 #, c-format msgid "%s is already a member of extension \"%s\"" msgstr "%s est déjà un membre de l'extension « %s »" -#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3372 +#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3369 #, c-format msgid "%s is not a member of extension \"%s\"" msgstr "%s n'est pas un membre de l'extension « %s »" @@ -5003,7 +5018,7 @@ msgid "ALTER TYPE ADD BEFORE/AFTER is incompatible with binary upgrade" msgstr "ALTER TYPE ADD BEFORE/AFTER est incompatible avec la mise à jour binaire" -#: catalog/pg_namespace.c:64 commands/schemacmds.c:277 +#: catalog/pg_namespace.c:64 commands/schemacmds.c:294 #, c-format msgid "schema \"%s\" already exists" msgstr "le schéma « %s » existe déjà" @@ -5268,7 +5283,7 @@ "ne peut pas réaffecter les objets appartenant à %s car ils sont nécessaires au\n" "système de bases de données" -#: catalog/pg_subscription.c:171 commands/subscriptioncmds.c:648 commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1084 +#: catalog/pg_subscription.c:171 commands/subscriptioncmds.c:648 commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1085 #, c-format msgid "subscription \"%s\" does not exist" msgstr "la souscription « %s » n'existe pas" @@ -5762,7 +5777,7 @@ msgid "no usable system locales were found" msgstr "aucune locale système utilisable n'a été trouvée" -#: commands/comment.c:61 commands/dbcommands.c:842 commands/dbcommands.c:1038 commands/dbcommands.c:1151 commands/dbcommands.c:1341 commands/dbcommands.c:1589 commands/dbcommands.c:1703 commands/dbcommands.c:2143 utils/init/postinit.c:877 utils/init/postinit.c:982 utils/init/postinit.c:999 +#: commands/comment.c:61 commands/dbcommands.c:853 commands/dbcommands.c:1064 commands/dbcommands.c:1177 commands/dbcommands.c:1367 commands/dbcommands.c:1615 commands/dbcommands.c:1737 commands/dbcommands.c:2177 utils/init/postinit.c:877 utils/init/postinit.c:983 utils/init/postinit.c:1009 #, c-format msgid "database \"%s\" does not exist" msgstr "la base de données « %s » n'existe pas" @@ -5894,7 +5909,7 @@ msgid "argument to option \"%s\" must be a valid encoding name" msgstr "l'argument de l'option « %s » doit être un nom d'encodage valide" -#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1537 +#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1563 #, c-format msgid "option \"%s\" not recognized" msgstr "option « %s » non reconnu" @@ -6314,7 +6329,7 @@ msgid "Generated columns cannot be used in COPY." msgstr "Les colonnes générées ne peuvent pas être utilisées dans COPY." -#: commands/copy.c:5096 commands/indexcmds.c:1789 commands/statscmds.c:228 commands/tablecmds.c:2205 commands/tablecmds.c:2824 commands/tablecmds.c:3211 parser/parse_relation.c:3557 parser/parse_relation.c:3577 utils/adt/tsvector_op.c:2683 +#: commands/copy.c:5096 commands/indexcmds.c:1806 commands/statscmds.c:228 commands/tablecmds.c:2205 commands/tablecmds.c:2824 commands/tablecmds.c:3211 parser/parse_relation.c:3557 parser/parse_relation.c:3577 utils/adt/tsvector_op.c:2683 #, c-format msgid "column \"%s\" does not exist" msgstr "la colonne « %s » n'existe pas" @@ -6359,7 +6374,7 @@ msgid "%s is not a valid encoding name" msgstr "%s n'est pas un nom d'encodage valide" -#: commands/dbcommands.c:315 commands/dbcommands.c:1570 commands/user.c:275 commands/user.c:691 +#: commands/dbcommands.c:315 commands/dbcommands.c:1596 commands/user.c:275 commands/user.c:691 #, c-format msgid "invalid connection limit: %d" msgstr "limite de connexion invalide : %d" @@ -6374,230 +6389,245 @@ msgid "template database \"%s\" does not exist" msgstr "la base de données modèle « %s » n'existe pas" -#: commands/dbcommands.c:369 +#: commands/dbcommands.c:367 +#, c-format +msgid "cannot use invalid database \"%s\" as template" +msgstr "ne peut pas utiliser la base de données invalide « %s » comme modèle" + +#: commands/dbcommands.c:368 commands/dbcommands.c:1625 utils/init/postinit.c:992 +#, c-format +msgid "Use DROP DATABASE to drop invalid databases." +msgstr "Utilisez DROP DATABASE pour supprimer des bases invalides." + +#: commands/dbcommands.c:379 #, c-format msgid "permission denied to copy database \"%s\"" msgstr "droit refusé pour copier la base de données « %s »" -#: commands/dbcommands.c:385 +#: commands/dbcommands.c:395 #, c-format msgid "invalid server encoding %d" msgstr "encodage serveur %d invalide" -#: commands/dbcommands.c:391 commands/dbcommands.c:396 +#: commands/dbcommands.c:401 commands/dbcommands.c:406 #, c-format msgid "invalid locale name: \"%s\"" msgstr "nom de locale invalide : « %s »" -#: commands/dbcommands.c:416 +#: commands/dbcommands.c:426 #, c-format msgid "new encoding (%s) is incompatible with the encoding of the template database (%s)" msgstr "" "le nouvel encodage (%sà est incompatible avec l'encodage de la base de\n" "données modèle (%s)" -#: commands/dbcommands.c:419 +#: commands/dbcommands.c:429 #, c-format msgid "Use the same encoding as in the template database, or use template0 as template." msgstr "" "Utilisez le même encodage que celui de la base de données modèle,\n" "ou utilisez template0 comme modèle." -#: commands/dbcommands.c:424 +#: commands/dbcommands.c:434 #, c-format msgid "new collation (%s) is incompatible with the collation of the template database (%s)" msgstr "" "le nouveau tri (%s) est incompatible avec le tri de la base de\n" "données modèle (%s)" -#: commands/dbcommands.c:426 +#: commands/dbcommands.c:436 #, c-format msgid "Use the same collation as in the template database, or use template0 as template." msgstr "" "Utilisez le même tri que celui de la base de données modèle,\n" "ou utilisez template0 comme modèle." -#: commands/dbcommands.c:431 +#: commands/dbcommands.c:441 #, c-format msgid "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)" msgstr "" "le nouveau LC_CTYPE (%s) est incompatible avec le LC_CTYPE de la base de\n" "données modèle (%s)" -#: commands/dbcommands.c:433 +#: commands/dbcommands.c:443 #, c-format msgid "Use the same LC_CTYPE as in the template database, or use template0 as template." msgstr "" "Utilisez le même LC_CTYPE que celui de la base de données modèle,\n" "ou utilisez template0 comme modèle." -#: commands/dbcommands.c:455 commands/dbcommands.c:1197 +#: commands/dbcommands.c:465 commands/dbcommands.c:1223 #, c-format msgid "pg_global cannot be used as default tablespace" msgstr "pg_global ne peut pas être utilisé comme tablespace par défaut" -#: commands/dbcommands.c:481 +#: commands/dbcommands.c:491 #, c-format msgid "cannot assign new default tablespace \"%s\"" msgstr "ne peut pas affecter un nouveau tablespace par défaut « %s »" -#: commands/dbcommands.c:483 +#: commands/dbcommands.c:493 #, c-format msgid "There is a conflict because database \"%s\" already has some tables in this tablespace." msgstr "" "Il existe un conflit car la base de données « %s » a déjà quelques tables\n" "dans son tablespace." -#: commands/dbcommands.c:513 commands/dbcommands.c:1067 +#: commands/dbcommands.c:523 commands/dbcommands.c:1093 #, c-format msgid "database \"%s\" already exists" msgstr "la base de données « %s » existe déjà" -#: commands/dbcommands.c:527 +#: commands/dbcommands.c:537 #, c-format msgid "source database \"%s\" is being accessed by other users" msgstr "la base de données source « %s » est accédée par d'autres utilisateurs" -#: commands/dbcommands.c:770 commands/dbcommands.c:785 +#: commands/dbcommands.c:780 commands/dbcommands.c:795 #, c-format msgid "encoding \"%s\" does not match locale \"%s\"" msgstr "l'encodage « %s » ne correspond pas à la locale « %s »" -#: commands/dbcommands.c:773 +#: commands/dbcommands.c:783 #, c-format msgid "The chosen LC_CTYPE setting requires encoding \"%s\"." msgstr "Le paramètre LC_CTYPE choisi nécessite l'encodage « %s »." -#: commands/dbcommands.c:788 +#: commands/dbcommands.c:798 #, c-format msgid "The chosen LC_COLLATE setting requires encoding \"%s\"." msgstr "Le paramètre LC_COLLATE choisi nécessite l'encodage « %s »." -#: commands/dbcommands.c:849 +#: commands/dbcommands.c:860 #, c-format msgid "database \"%s\" does not exist, skipping" msgstr "la base de données « %s » n'existe pas, poursuite du traitement" -#: commands/dbcommands.c:873 +#: commands/dbcommands.c:884 #, c-format msgid "cannot drop a template database" msgstr "ne peut pas supprimer une base de données modèle" -#: commands/dbcommands.c:879 +#: commands/dbcommands.c:890 #, c-format msgid "cannot drop the currently open database" msgstr "ne peut pas supprimer la base de données actuellement ouverte" -#: commands/dbcommands.c:892 +#: commands/dbcommands.c:903 #, c-format msgid "database \"%s\" is used by an active logical replication slot" msgstr "la base de données « %s » est utilisée par un slot de réplication logique actif" -#: commands/dbcommands.c:894 +#: commands/dbcommands.c:905 #, c-format msgid "There is %d active slot." msgid_plural "There are %d active slots." msgstr[0] "Il existe %d slot actif." msgstr[1] "Il existe %d slots actifs." -#: commands/dbcommands.c:908 +#: commands/dbcommands.c:919 #, c-format msgid "database \"%s\" is being used by logical replication subscription" msgstr "la base de données « %s » est utilisée par une souscription de réplication logique" -#: commands/dbcommands.c:910 +#: commands/dbcommands.c:921 #, c-format msgid "There is %d subscription." msgid_plural "There are %d subscriptions." msgstr[0] "Il existe %d souscription." msgstr[1] "Il existe %d souscriptions." -#: commands/dbcommands.c:931 commands/dbcommands.c:1089 commands/dbcommands.c:1219 +#: commands/dbcommands.c:942 commands/dbcommands.c:1115 commands/dbcommands.c:1245 #, c-format msgid "database \"%s\" is being accessed by other users" msgstr "la base de données « %s » est en cours d'utilisation par d'autres utilisateurs" -#: commands/dbcommands.c:1049 +#: commands/dbcommands.c:1075 #, c-format msgid "permission denied to rename database" msgstr "droit refusé pour le renommage de la base de données" -#: commands/dbcommands.c:1078 +#: commands/dbcommands.c:1104 #, c-format msgid "current database cannot be renamed" msgstr "la base de données actuelle ne peut pas être renommée" -#: commands/dbcommands.c:1175 +#: commands/dbcommands.c:1201 #, c-format msgid "cannot change the tablespace of the currently open database" msgstr "ne peut pas modifier le tablespace de la base de données actuellement ouverte" -#: commands/dbcommands.c:1278 +#: commands/dbcommands.c:1304 #, c-format msgid "some relations of database \"%s\" are already in tablespace \"%s\"" msgstr "" "certaines relations de la base de données « %s » sont déjà dans le\n" "tablespace « %s »" -#: commands/dbcommands.c:1280 +#: commands/dbcommands.c:1306 #, c-format msgid "You must move them back to the database's default tablespace before using this command." msgstr "" "Vous devez d'abord les déplacer dans le tablespace par défaut de la base\n" "de données avant d'utiliser cette commande." -#: commands/dbcommands.c:1405 commands/dbcommands.c:1981 commands/dbcommands.c:2244 commands/dbcommands.c:2330 +#: commands/dbcommands.c:1431 commands/dbcommands.c:2015 commands/dbcommands.c:2314 commands/dbcommands.c:2400 #, c-format msgid "some useless files may be left behind in old database directory \"%s\"" msgstr "" "certains fichiers inutiles pourraient se trouver dans l'ancien répertoire\n" "de la base de données « %s »" -#: commands/dbcommands.c:1461 +#: commands/dbcommands.c:1487 #, c-format msgid "unrecognized DROP DATABASE option \"%s\"" msgstr "option de DROP DATABASE « %s » non reconnue" -#: commands/dbcommands.c:1551 +#: commands/dbcommands.c:1577 #, c-format msgid "option \"%s\" cannot be specified with other options" msgstr "l'option « %s » ne peut pas être spécifié avec d'autres options" -#: commands/dbcommands.c:1607 +#: commands/dbcommands.c:1624 +#, c-format +msgid "cannot alter invalid database \"%s\"" +msgstr "ne peut pas modifier la base de données invalide « %s »" + +#: commands/dbcommands.c:1641 #, c-format msgid "cannot disallow connections for current database" msgstr "ne peut pas désactiver les connexions pour la base de données courante" -#: commands/dbcommands.c:1743 +#: commands/dbcommands.c:1777 #, c-format msgid "permission denied to change owner of database" msgstr "droit refusé pour modifier le propriétaire de la base de données" -#: commands/dbcommands.c:2087 +#: commands/dbcommands.c:2121 #, c-format msgid "There are %d other session(s) and %d prepared transaction(s) using the database." msgstr "%d autres sessions et %d transactions préparées utilisent la base de données." -#: commands/dbcommands.c:2090 +#: commands/dbcommands.c:2124 #, c-format msgid "There is %d other session using the database." msgid_plural "There are %d other sessions using the database." msgstr[0] "%d autre session utilise la base de données." msgstr[1] "%d autres sessions utilisent la base de données." -#: commands/dbcommands.c:2095 storage/ipc/procarray.c:3128 +#: commands/dbcommands.c:2129 storage/ipc/procarray.c:3129 #, c-format msgid "There is %d prepared transaction using the database." msgid_plural "There are %d prepared transactions using the database." msgstr[0] "%d transaction préparée utilise la base de données." msgstr[1] "%d transactions préparées utilisent la base de données." -#: commands/dbcommands.c:2201 +#: commands/dbcommands.c:2271 #, c-format msgid "missing directory \"%s\"" msgstr "répertoire « %s » manquant" -#: commands/dbcommands.c:2260 commands/tablespace.c:188 commands/tablespace.c:634 +#: commands/dbcommands.c:2330 commands/tablespace.c:188 commands/tablespace.c:634 #, c-format msgid "could not stat directory \"%s\": %m" msgstr "n'a pas pu lire les informations sur le répertoire « %s » : %m" @@ -6884,7 +6914,7 @@ msgid "EXPLAIN option TIMING requires ANALYZE" msgstr "l'option TIMING d'EXPLAIN nécessite ANALYZE" -#: commands/extension.c:173 commands/extension.c:3013 +#: commands/extension.c:173 commands/extension.c:3010 #, c-format msgid "extension \"%s\" does not exist" msgstr "l'extension « %s » n'existe pas" @@ -7020,7 +7050,7 @@ msgid "extension \"%s\" has no update path from version \"%s\" to version \"%s\"" msgstr "l'extension « %s » n'a pas de chemin de mise à jour pour aller de la version « %s » à la version « %s »" -#: commands/extension.c:1408 commands/extension.c:3074 +#: commands/extension.c:1408 commands/extension.c:3071 #, c-format msgid "version to install must be specified" msgstr "la version à installer doit être précisée" @@ -7097,34 +7127,34 @@ "ne peut pas déplacer l'extension « %s » dans le schéma « %s » car l'extension\n" "contient le schéma" -#: commands/extension.c:2869 commands/extension.c:2932 +#: commands/extension.c:2869 commands/extension.c:2929 #, c-format msgid "extension \"%s\" does not support SET SCHEMA" msgstr "l'extension « %s » ne supporte pas SET SCHEMA" -#: commands/extension.c:2934 +#: commands/extension.c:2931 #, c-format msgid "%s is not in the extension's schema \"%s\"" msgstr "%s n'est pas dans le schéma de l'extension « %s »" -#: commands/extension.c:2993 +#: commands/extension.c:2990 #, c-format msgid "nested ALTER EXTENSION is not supported" msgstr "un ALTER EXTENSION imbriqué n'est pas supporté" -#: commands/extension.c:3085 +#: commands/extension.c:3082 #, c-format msgid "version \"%s\" of extension \"%s\" is already installed" msgstr "la version « %s » de l'extension « %s » est déjà installée" -#: commands/extension.c:3344 +#: commands/extension.c:3341 #, c-format msgid "cannot add schema \"%s\" to extension \"%s\" because the schema contains the extension" msgstr "" "ne peut pas ajouter le schéma « %s » à l'extension « %s » car le schéma\n" "contient l'extension" -#: commands/extension.c:3438 +#: commands/extension.c:3435 #, c-format msgid "file \"%s\" is too large" msgstr "le fichier « %s » est trop gros" @@ -7691,172 +7721,172 @@ msgid "Table \"%s\" contains partitions that are foreign tables." msgstr "La table « %s » contient des partitionso qui ne sont pas des tables distantes." -#: commands/indexcmds.c:1706 +#: commands/indexcmds.c:1723 #, c-format msgid "functions in index predicate must be marked IMMUTABLE" msgstr "les fonctions dans un prédicat d'index doivent être marquées comme IMMUTABLE" -#: commands/indexcmds.c:1784 parser/parse_utilcmd.c:2485 parser/parse_utilcmd.c:2620 +#: commands/indexcmds.c:1801 parser/parse_utilcmd.c:2485 parser/parse_utilcmd.c:2620 #, c-format msgid "column \"%s\" named in key does not exist" msgstr "la colonne « %s » nommée dans la clé n'existe pas" -#: commands/indexcmds.c:1808 parser/parse_utilcmd.c:1821 +#: commands/indexcmds.c:1825 parser/parse_utilcmd.c:1821 #, c-format msgid "expressions are not supported in included columns" msgstr "les expressions ne sont pas supportées dans les colonnes incluses" -#: commands/indexcmds.c:1849 +#: commands/indexcmds.c:1866 #, c-format msgid "functions in index expression must be marked IMMUTABLE" msgstr "" "les fonctions dans l'expression de l'index doivent être marquées comme\n" "IMMUTABLE" -#: commands/indexcmds.c:1864 +#: commands/indexcmds.c:1881 #, c-format msgid "including column does not support a collation" msgstr "une colonne incluse ne supporte pas de collationnement" -#: commands/indexcmds.c:1868 +#: commands/indexcmds.c:1885 #, c-format msgid "including column does not support an operator class" msgstr "une colonne incluse ne supporte pas de classe d'opérateur" -#: commands/indexcmds.c:1872 +#: commands/indexcmds.c:1889 #, c-format msgid "including column does not support ASC/DESC options" msgstr "une colonne incluse ne supporte pas d'options ASC/DESC" -#: commands/indexcmds.c:1876 +#: commands/indexcmds.c:1893 #, c-format msgid "including column does not support NULLS FIRST/LAST options" msgstr "une colonne incluse ne supporte pas d'options NULLS FIRST/LAST" -#: commands/indexcmds.c:1917 +#: commands/indexcmds.c:1934 #, c-format msgid "could not determine which collation to use for index expression" msgstr "n'a pas pu déterminer le collationnement à utiliser pour l'expression d'index" -#: commands/indexcmds.c:1925 commands/tablecmds.c:16451 commands/typecmds.c:771 parser/parse_expr.c:2863 parser/parse_type.c:566 parser/parse_utilcmd.c:3696 parser/parse_utilcmd.c:4259 utils/adt/misc.c:532 +#: commands/indexcmds.c:1942 commands/tablecmds.c:16451 commands/typecmds.c:771 parser/parse_expr.c:2863 parser/parse_type.c:566 parser/parse_utilcmd.c:3696 parser/parse_utilcmd.c:4259 utils/adt/misc.c:532 #, c-format msgid "collations are not supported by type %s" msgstr "les collationnements ne sont pas supportés par le type %s" -#: commands/indexcmds.c:1990 +#: commands/indexcmds.c:2007 #, c-format msgid "operator %s is not commutative" msgstr "l'opérateur %s n'est pas commutatif" -#: commands/indexcmds.c:1992 +#: commands/indexcmds.c:2009 #, c-format msgid "Only commutative operators can be used in exclusion constraints." msgstr "Seuls les opérateurs commutatifs peuvent être utilisés dans les contraintes d'exclusion." -#: commands/indexcmds.c:2018 +#: commands/indexcmds.c:2035 #, c-format msgid "operator %s is not a member of operator family \"%s\"" msgstr "l'opérateur %s n'est pas un membre de la famille d'opérateur « %s »" -#: commands/indexcmds.c:2021 +#: commands/indexcmds.c:2038 #, c-format msgid "The exclusion operator must be related to the index operator class for the constraint." msgstr "" "L'opérateur d'exclusion doit être en relation avec la classe d'opérateur de\n" "l'index pour la contrainte." -#: commands/indexcmds.c:2056 +#: commands/indexcmds.c:2073 #, c-format msgid "access method \"%s\" does not support ASC/DESC options" msgstr "la méthode d'accès « %s » ne supporte pas les options ASC/DESC" -#: commands/indexcmds.c:2061 +#: commands/indexcmds.c:2078 #, c-format msgid "access method \"%s\" does not support NULLS FIRST/LAST options" msgstr "la méthode d'accès « %s » ne supporte pas les options NULLS FIRST/LAST" -#: commands/indexcmds.c:2107 commands/tablecmds.c:16476 commands/tablecmds.c:16482 commands/typecmds.c:1947 +#: commands/indexcmds.c:2124 commands/tablecmds.c:16476 commands/tablecmds.c:16482 commands/typecmds.c:1947 #, c-format msgid "data type %s has no default operator class for access method \"%s\"" msgstr "" "le type de données %s n'a pas de classe d'opérateurs par défaut pour la\n" "méthode d'accès « %s »" -#: commands/indexcmds.c:2109 +#: commands/indexcmds.c:2126 #, c-format msgid "You must specify an operator class for the index or define a default operator class for the data type." msgstr "" "Vous devez spécifier une classe d'opérateur pour l'index ou définir une\n" "classe d'opérateur par défaut pour le type de données." -#: commands/indexcmds.c:2138 commands/indexcmds.c:2146 commands/opclasscmds.c:208 +#: commands/indexcmds.c:2155 commands/indexcmds.c:2163 commands/opclasscmds.c:208 #, c-format msgid "operator class \"%s\" does not exist for access method \"%s\"" msgstr "la classe d'opérateur « %s » n'existe pas pour la méthode d'accès « %s »" -#: commands/indexcmds.c:2160 commands/typecmds.c:1935 +#: commands/indexcmds.c:2177 commands/typecmds.c:1935 #, c-format msgid "operator class \"%s\" does not accept data type %s" msgstr "la classe d'opérateur « %s » n'accepte pas le type de données %s" -#: commands/indexcmds.c:2250 +#: commands/indexcmds.c:2267 #, c-format msgid "there are multiple default operator classes for data type %s" msgstr "" "il existe de nombreuses classes d'opérateur par défaut pour le type de\n" "données %s" -#: commands/indexcmds.c:2699 +#: commands/indexcmds.c:2716 #, c-format msgid "table \"%s\" has no indexes that can be reindexed concurrently" msgstr "la table « %s » n'a pas d'index qui puisse être réindexé concuremment" -#: commands/indexcmds.c:2710 +#: commands/indexcmds.c:2727 #, c-format msgid "table \"%s\" has no indexes to reindex" msgstr "la table « %s » n'a pas d'index à réindexer" -#: commands/indexcmds.c:2749 commands/indexcmds.c:3030 commands/indexcmds.c:3123 +#: commands/indexcmds.c:2766 commands/indexcmds.c:3047 commands/indexcmds.c:3140 #, c-format msgid "cannot reindex system catalogs concurrently" msgstr "ne peut pas réindexer les catalogues système de manière concurrente" -#: commands/indexcmds.c:2772 +#: commands/indexcmds.c:2789 #, c-format msgid "can only reindex the currently open database" msgstr "peut seulement réindexer la base de données en cours" -#: commands/indexcmds.c:2863 +#: commands/indexcmds.c:2880 #, c-format msgid "cannot reindex system catalogs concurrently, skipping all" msgstr "ne peut pas réindexer les catalogues système de manière concurrente, ignore tout" -#: commands/indexcmds.c:2915 commands/indexcmds.c:3655 +#: commands/indexcmds.c:2932 commands/indexcmds.c:3672 #, c-format msgid "table \"%s.%s\" was reindexed" msgstr "la table « %s.%s » a été réindexée" -#: commands/indexcmds.c:3045 commands/indexcmds.c:3091 +#: commands/indexcmds.c:3062 commands/indexcmds.c:3108 #, c-format msgid "cannot reindex invalid index \"%s.%s\" concurrently, skipping" msgstr "ne peut pas réindexer l'index invalide « %s.%s » de manière concurrente, ignoré" -#: commands/indexcmds.c:3051 +#: commands/indexcmds.c:3068 #, c-format msgid "cannot reindex exclusion constraint index \"%s.%s\" concurrently, skipping" msgstr "ne peut pas réindexer l'index de contrainte d'exclusion « %s.%s » de manière concurrente, ignoré" -#: commands/indexcmds.c:3162 +#: commands/indexcmds.c:3179 #, c-format msgid "cannot reindex this type of relation concurrently" msgstr "ne peut pas réindexer ce type de relation de manière concurrente" -#: commands/indexcmds.c:3637 commands/indexcmds.c:3648 +#: commands/indexcmds.c:3654 commands/indexcmds.c:3665 #, c-format msgid "index \"%s.%s\" was reindexed" msgstr "l'index « %s.%s » a été réindexé" -#: commands/indexcmds.c:3680 +#: commands/indexcmds.c:3697 #, c-format msgid "REINDEX is not yet implemented for partitioned indexes" msgstr "REINDEX n'est pas implémenté pour des index partitionnés" @@ -8330,17 +8360,17 @@ msgid "The owner of a FOR ALL TABLES publication must be a superuser." msgstr "Le propriétaire d'une publication FOR ALL TABLES doit être un super-utilisateur." -#: commands/schemacmds.c:105 commands/schemacmds.c:293 +#: commands/schemacmds.c:108 commands/schemacmds.c:310 #, c-format msgid "unacceptable schema name \"%s\"" msgstr "nom de schéma « %s » inacceptable" -#: commands/schemacmds.c:106 commands/schemacmds.c:294 +#: commands/schemacmds.c:109 commands/schemacmds.c:311 #, c-format msgid "The prefix \"pg_\" is reserved for system schemas." msgstr "Le préfixe « pg_ » est réservé pour les schémas système." -#: commands/schemacmds.c:130 +#: commands/schemacmds.c:133 #, c-format msgid "schema \"%s\" already exists, skipping" msgstr "la schéma « %s » existe déjà, poursuite du traitement" @@ -8645,7 +8675,7 @@ msgid "could not connect to publisher when attempting to drop the replication slot \"%s\"" msgstr "n'a pas pu se connecter au publieur pour supprimer le slot de réplication « %s »" -#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1008 replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 +#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1009 replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 #, c-format msgid "The error was: %s" msgstr "L'erreur était : %s" @@ -8653,30 +8683,30 @@ #. translator: %s is an SQL ALTER command #: commands/subscriptioncmds.c:995 #, c-format -msgid "Use %s to disassociate the subscription from the slot." -msgstr "Utilisez %s pour dissocier la souscription du slot." +msgid "Use %s to disable the subscription, and then use %s to disassociate it from the slot." +msgstr "Utilisez %s pour désactiver l'abonnement, puis utilisez %s pour le dissocier du slot" -#: commands/subscriptioncmds.c:1006 +#: commands/subscriptioncmds.c:1007 #, c-format msgid "could not drop the replication slot \"%s\" on publisher" msgstr "n'a pas pu supprimer le slot de réplication « %s » sur le publieur" -#: commands/subscriptioncmds.c:1011 +#: commands/subscriptioncmds.c:1012 #, c-format msgid "dropped replication slot \"%s\" on publisher" msgstr "slot de réplication « %s » supprimé sur le publieur" -#: commands/subscriptioncmds.c:1048 +#: commands/subscriptioncmds.c:1049 #, c-format msgid "permission denied to change owner of subscription \"%s\"" msgstr "droit refusé pour modifier le propriétaire de la souscription « %s »" -#: commands/subscriptioncmds.c:1050 +#: commands/subscriptioncmds.c:1051 #, c-format msgid "The owner of a subscription must be a superuser." msgstr "Le propriétaire d'une souscription doit être un super-utilisateur." -#: commands/subscriptioncmds.c:1165 +#: commands/subscriptioncmds.c:1166 #, c-format msgid "could not receive list of replicated tables from the publisher: %s" msgstr "n'a pas pu recevoir la liste des tables répliquées à partir du publieur : %s" @@ -8737,7 +8767,7 @@ msgid "Use DROP MATERIALIZED VIEW to remove a materialized view." msgstr "Utilisez DROP MATERIALIZED VIEW pour supprimer une vue matérialisée." -#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17685 parser/parse_utilcmd.c:2217 +#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17689 parser/parse_utilcmd.c:2217 #, c-format msgid "index \"%s\" does not exist" msgstr "l'index « %s » n'existe pas" @@ -9975,7 +10005,7 @@ msgid "cannot use generated column in partition key" msgstr "ne peut pas utiliser une colonne générée dans une clé de partitionnement" -#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 rewrite/rewriteHandler.c:873 rewrite/rewriteHandler.c:890 +#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 #, c-format msgid "Column \"%s\" is a generated column." msgstr "la colonne « %s » est une colonne générée." @@ -10096,32 +10126,32 @@ msgid "Table \"%s\" contains unique indexes." msgstr "La table « %s » contient des index uniques." -#: commands/tablecmds.c:17719 commands/tablecmds.c:17739 commands/tablecmds.c:17759 commands/tablecmds.c:17778 commands/tablecmds.c:17820 +#: commands/tablecmds.c:17723 commands/tablecmds.c:17743 commands/tablecmds.c:17763 commands/tablecmds.c:17782 commands/tablecmds.c:17824 #, c-format msgid "cannot attach index \"%s\" as a partition of index \"%s\"" msgstr "ne peut pas attacher l'index « %s » comme une partition de l'index « %s »" -#: commands/tablecmds.c:17722 +#: commands/tablecmds.c:17726 #, c-format msgid "Index \"%s\" is already attached to another index." msgstr "L'index « %s » est déjà attaché à un autre index." -#: commands/tablecmds.c:17742 +#: commands/tablecmds.c:17746 #, c-format msgid "Index \"%s\" is not an index on any partition of table \"%s\"." msgstr "L'index « %s » n'est un index sur aucune des partitions de la table « %s »." -#: commands/tablecmds.c:17762 +#: commands/tablecmds.c:17766 #, c-format msgid "The index definitions do not match." msgstr "La définition de l'index correspond pas." -#: commands/tablecmds.c:17781 +#: commands/tablecmds.c:17785 #, c-format msgid "The index \"%s\" belongs to a constraint in table \"%s\" but no constraint exists for index \"%s\"." msgstr "L'index « %s » appartient à une contrainte dans la table « %s » mais aucune contrainte n'existe pour l'index « %s »." -#: commands/tablecmds.c:17823 +#: commands/tablecmds.c:17827 #, c-format msgid "Another index is already attached for partition \"%s\"." msgstr "Un autre index est déjà attaché pour la partition « %s »." @@ -10483,17 +10513,17 @@ msgid "could not serialize access due to concurrent delete" msgstr "n'a pas pu sérialiser un accès à cause d'une suppression en parallèle" -#: commands/trigger.c:4124 +#: commands/trigger.c:4155 #, c-format msgid "cannot fire deferred trigger within security-restricted operation" msgstr "ne peut pas déclencher un trigger déferré à l'intérieur d'une opération restreinte pour sécurité" -#: commands/trigger.c:5173 +#: commands/trigger.c:5204 #, c-format msgid "constraint \"%s\" is not deferrable" msgstr "la contrainte « %s » n'est pas DEFERRABLE" -#: commands/trigger.c:5196 +#: commands/trigger.c:5227 #, c-format msgid "constraint \"%s\" does not exist" msgstr "la contrainte « %s » n'existe pas" @@ -11225,21 +11255,21 @@ "Fermez les transactions ouvertes avec multixacts rapidement pour éviter des problèmes de\n" "réinitialisation." -#: commands/vacuum.c:1640 +#: commands/vacuum.c:1654 #, c-format msgid "some databases have not been vacuumed in over 2 billion transactions" msgstr "" "certaines bases de données n'ont pas eu droit à l'opération de maintenance\n" "VACUUM depuis plus de 2 milliards de transactions" -#: commands/vacuum.c:1641 +#: commands/vacuum.c:1655 #, c-format msgid "You might have already suffered transaction-wraparound data loss." msgstr "" "Vous pouvez avoir déjà souffert de pertes de données suite à une\n" "réinitialisation de l'identifiant des transactions." -#: commands/vacuum.c:1801 +#: commands/vacuum.c:1819 #, c-format msgid "skipping \"%s\" --- cannot vacuum non-tables or special system tables" msgstr "" @@ -11441,12 +11471,12 @@ msgid "cursor \"%s\" is not a simply updatable scan of table \"%s\"" msgstr "le curseur « %s » n'est pas un parcours modifiable de la table « %s »" -#: executor/execCurrent.c:280 executor/execExprInterp.c:2434 +#: executor/execCurrent.c:280 executor/execExprInterp.c:2435 #, c-format msgid "type of parameter %d (%s) does not match that when preparing the plan (%s)" msgstr "le type de paramètre %d (%s) ne correspond pas à celui préparé dans le plan (%s)" -#: executor/execCurrent.c:292 executor/execExprInterp.c:2446 +#: executor/execCurrent.c:292 executor/execExprInterp.c:2447 #, c-format msgid "no value found for parameter %d" msgstr "aucune valeur trouvée pour le paramètre %d" @@ -11473,7 +11503,7 @@ msgstr[0] "ne peut pas passer plus de %d argument à une fonction" msgstr[1] "ne peut pas passer plus de %d arguments à une fonction" -#: executor/execExpr.c:2690 executor/execExpr.c:2696 executor/execExprInterp.c:2759 utils/adt/arrayfuncs.c:262 utils/adt/arrayfuncs.c:562 utils/adt/arrayfuncs.c:1304 utils/adt/arrayfuncs.c:3346 utils/adt/arrayfuncs.c:5308 utils/adt/arrayfuncs.c:5825 +#: executor/execExpr.c:2690 executor/execExpr.c:2696 executor/execExprInterp.c:2760 utils/adt/arrayfuncs.c:262 utils/adt/arrayfuncs.c:562 utils/adt/arrayfuncs.c:1304 utils/adt/arrayfuncs.c:3346 utils/adt/arrayfuncs.c:5308 utils/adt/arrayfuncs.c:5825 #, c-format msgid "number of array dimensions (%d) exceeds the maximum allowed (%d)" msgstr "le nombre de dimensions du tableau (%d) dépasse le maximum autorisé (%d)" @@ -11488,81 +11518,81 @@ msgid "attribute %d of type %s has wrong type" msgstr "l'attribut %d de type %s a un mauvais type" -#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3040 executor/execExprInterp.c:3086 +#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3041 executor/execExprInterp.c:3087 #, c-format msgid "Table has type %s, but query expects %s." msgstr "La table a le type %s alors que la requête attend %s." -#: executor/execExprInterp.c:1986 utils/adt/expandedrecord.c:99 utils/adt/expandedrecord.c:231 utils/cache/typcache.c:1632 utils/cache/typcache.c:1788 utils/cache/typcache.c:1936 utils/fmgr/funcapi.c:456 +#: executor/execExprInterp.c:1987 utils/adt/expandedrecord.c:99 utils/adt/expandedrecord.c:231 utils/cache/typcache.c:1632 utils/cache/typcache.c:1788 utils/cache/typcache.c:1936 utils/fmgr/funcapi.c:456 #, c-format msgid "type %s is not composite" msgstr "le type %s n'est pas un type composite" -#: executor/execExprInterp.c:2524 +#: executor/execExprInterp.c:2525 #, c-format msgid "WHERE CURRENT OF is not supported for this table type" msgstr "WHERE CURRENT OF n'est pas supporté pour ce type de table" -#: executor/execExprInterp.c:2737 +#: executor/execExprInterp.c:2738 #, c-format msgid "cannot merge incompatible arrays" msgstr "ne peut pas fusionner les tableaux incompatibles" -#: executor/execExprInterp.c:2738 +#: executor/execExprInterp.c:2739 #, c-format msgid "Array with element type %s cannot be included in ARRAY construct with element type %s." msgstr "Le tableau avec le type d'élément %s ne peut pas être inclus dans la construction ARRAY avec le type d'élément %s." -#: executor/execExprInterp.c:2779 executor/execExprInterp.c:2814 +#: executor/execExprInterp.c:2780 executor/execExprInterp.c:2815 #, c-format msgid "multidimensional arrays must have array expressions with matching dimensions" msgstr "" "les tableaux multidimensionnels doivent avoir des expressions de tableaux\n" "avec les dimensions correspondantes" -#: executor/execExprInterp.c:2791 utils/adt/array_expanded.c:274 utils/adt/arrayfuncs.c:935 utils/adt/arrayfuncs.c:1522 utils/adt/arrayfuncs.c:3234 utils/adt/arrayfuncs.c:3376 utils/adt/arrayfuncs.c:5917 utils/adt/arrayfuncs.c:6258 utils/adt/arrayutils.c:94 utils/adt/arrayutils.c:103 utils/adt/arrayutils.c:110 +#: executor/execExprInterp.c:2792 utils/adt/array_expanded.c:274 utils/adt/arrayfuncs.c:935 utils/adt/arrayfuncs.c:1522 utils/adt/arrayfuncs.c:3234 utils/adt/arrayfuncs.c:3376 utils/adt/arrayfuncs.c:5917 utils/adt/arrayfuncs.c:6258 utils/adt/arrayutils.c:94 utils/adt/arrayutils.c:103 utils/adt/arrayutils.c:110 #, c-format msgid "array size exceeds the maximum allowed (%d)" msgstr "la taille du tableau dépasse le maximum permis (%d)" -#: executor/execExprInterp.c:3039 executor/execExprInterp.c:3085 +#: executor/execExprInterp.c:3040 executor/execExprInterp.c:3086 #, c-format msgid "attribute %d has wrong type" msgstr "l'attribut %d a un mauvais type" -#: executor/execExprInterp.c:3199 +#: executor/execExprInterp.c:3204 #, c-format msgid "array subscript in assignment must not be null" msgstr "l'indice du tableau dans l'affectation ne doit pas être NULL" -#: executor/execExprInterp.c:3626 utils/adt/domains.c:149 +#: executor/execExprInterp.c:3631 utils/adt/domains.c:149 #, c-format msgid "domain %s does not allow null values" msgstr "le domaine %s n'autorise pas les valeurs NULL" -#: executor/execExprInterp.c:3641 utils/adt/domains.c:184 +#: executor/execExprInterp.c:3646 utils/adt/domains.c:184 #, c-format msgid "value for domain %s violates check constraint \"%s\"" msgstr "la valeur pour le domaine %s viole la contrainte de vérification « %s »" -#: executor/execExprInterp.c:4011 executor/execExprInterp.c:4028 executor/execExprInterp.c:4127 executor/nodeModifyTable.c:110 executor/nodeModifyTable.c:121 executor/nodeModifyTable.c:138 executor/nodeModifyTable.c:146 +#: executor/execExprInterp.c:4016 executor/execExprInterp.c:4033 executor/execExprInterp.c:4132 executor/nodeModifyTable.c:110 executor/nodeModifyTable.c:121 executor/nodeModifyTable.c:138 executor/nodeModifyTable.c:146 #, c-format msgid "table row type and query-specified row type do not match" msgstr "le type de ligne de la table et celui spécifié par la requête ne correspondent pas" -#: executor/execExprInterp.c:4012 +#: executor/execExprInterp.c:4017 #, c-format msgid "Table row contains %d attribute, but query expects %d." msgid_plural "Table row contains %d attributes, but query expects %d." msgstr[0] "La ligne de la table contient %d attribut alors que la requête en attend %d." msgstr[1] "La ligne de la table contient %d attributs alors que la requête en attend %d." -#: executor/execExprInterp.c:4029 executor/nodeModifyTable.c:122 +#: executor/execExprInterp.c:4034 executor/nodeModifyTable.c:122 #, c-format msgid "Table has type %s at ordinal position %d, but query expects %s." msgstr "La table a le type %s à la position ordinale %d alors que la requête attend %s." -#: executor/execExprInterp.c:4128 executor/execSRF.c:967 +#: executor/execExprInterp.c:4133 executor/execSRF.c:967 #, c-format msgid "Physical storage mismatch on dropped attribute at ordinal position %d." msgstr "" @@ -11614,32 +11644,32 @@ msgid "cannot change TOAST relation \"%s\"" msgstr "ne peut pas modifier la relation TOAST « %s »" -#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3025 rewrite/rewriteHandler.c:3851 +#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3027 rewrite/rewriteHandler.c:3853 #, c-format msgid "cannot insert into view \"%s\"" msgstr "ne peut pas insérer dans la vue « %s »" -#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3028 rewrite/rewriteHandler.c:3854 +#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3030 rewrite/rewriteHandler.c:3856 #, c-format msgid "To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule." msgstr "Pour activer l'insertion dans la vue, fournissez un trigger INSTEAD OF INSERT ou une règle ON INSERT DO INSTEAD sans condition." -#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3033 rewrite/rewriteHandler.c:3859 +#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3035 rewrite/rewriteHandler.c:3861 #, c-format msgid "cannot update view \"%s\"" msgstr "ne peut pas mettre à jour la vue « %s »" -#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3036 rewrite/rewriteHandler.c:3862 +#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3038 rewrite/rewriteHandler.c:3864 #, c-format msgid "To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule." msgstr "Pour activer la mise à jour dans la vue, fournissez un trigger INSTEAD OF UPDATE ou une règle ON UPDATE DO INSTEAD sans condition." -#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3041 rewrite/rewriteHandler.c:3867 +#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3043 rewrite/rewriteHandler.c:3869 #, c-format msgid "cannot delete from view \"%s\"" msgstr "ne peut pas supprimer à partir de la vue « %s »" -#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3044 rewrite/rewriteHandler.c:3870 +#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3046 rewrite/rewriteHandler.c:3872 #, c-format msgid "To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule." msgstr "Pour activer la suppression dans la vue, fournissez un trigger INSTEAD OF DELETE ou une règle ON DELETE DO INSTEAD sans condition." @@ -12645,12 +12675,7 @@ msgid "could not open configuration directory \"%s\": %m" msgstr "n'a pas pu ouvrir le répertoire de configuration « %s » : %m" -#: jit/jit.c:205 utils/fmgr/dfmgr.c:209 utils/fmgr/dfmgr.c:417 utils/fmgr/dfmgr.c:465 -#, c-format -msgid "could not access file \"%s\": %m" -msgstr "n'a pas pu accéder au fichier « %s » : %m" - -#: jit/llvm/llvmjit.c:730 +#: jit/llvm/llvmjit.c:732 #, c-format msgid "time to inline: %.3fs, opt: %.3fs, emit: %.3fs" msgstr "temps pour inliner: %.3fs, opt: %.3fs, emit: %.3fs" @@ -12687,7 +12712,7 @@ msgid "unsupported Unicode escape sequence" msgstr "séquence d'échappement Unicode non supportée" -#: lib/dshash.c:246 utils/mmgr/dsa.c:702 utils/mmgr/dsa.c:724 utils/mmgr/dsa.c:805 +#: lib/dshash.c:246 utils/mmgr/dsa.c:703 utils/mmgr/dsa.c:725 utils/mmgr/dsa.c:806 #, c-format msgid "Failed on DSA request of size %zu." msgstr "Échec d'une requête DSA de taille %zu." @@ -14249,7 +14274,7 @@ msgid "could not receive data from client: %m" msgstr "n'a pas pu recevoir les données du client : %m" -#: libpq/pqcomm.c:1215 tcop/postgres.c:4186 +#: libpq/pqcomm.c:1215 tcop/postgres.c:4187 #, c-format msgid "terminating connection because protocol synchronization was lost" msgstr "arrêt de la connexion à cause d'une perte de synchronisation du protocole" @@ -14638,46 +14663,46 @@ msgstr "%s ne peut être appliqué sur le côté possiblement NULL d'une jointure externe" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: optimizer/plan/planner.c:1921 parser/analyze.c:1632 parser/analyze.c:1848 parser/analyze.c:2675 +#: optimizer/plan/planner.c:1923 parser/analyze.c:1632 parser/analyze.c:1848 parser/analyze.c:2675 #, c-format msgid "%s is not allowed with UNION/INTERSECT/EXCEPT" msgstr "%s n'est pas autorisé avec UNION/INTERSECT/EXCEPT" -#: optimizer/plan/planner.c:2508 optimizer/plan/planner.c:4161 +#: optimizer/plan/planner.c:2510 optimizer/plan/planner.c:4163 #, c-format msgid "could not implement GROUP BY" msgstr "n'a pas pu implanter GROUP BY" -#: optimizer/plan/planner.c:2509 optimizer/plan/planner.c:4162 optimizer/plan/planner.c:4889 optimizer/prep/prepunion.c:1045 +#: optimizer/plan/planner.c:2511 optimizer/plan/planner.c:4164 optimizer/plan/planner.c:4891 optimizer/prep/prepunion.c:1045 #, c-format msgid "Some of the datatypes only support hashing, while others only support sorting." msgstr "" "Certains des types de données supportent seulement le hachage,\n" "alors que les autres supportent seulement le tri." -#: optimizer/plan/planner.c:4888 +#: optimizer/plan/planner.c:4890 #, c-format msgid "could not implement DISTINCT" msgstr "n'a pas pu implanter DISTINCT" -#: optimizer/plan/planner.c:5736 +#: optimizer/plan/planner.c:5738 #, c-format msgid "could not implement window PARTITION BY" msgstr "n'a pas pu implanter PARTITION BY de window" -#: optimizer/plan/planner.c:5737 +#: optimizer/plan/planner.c:5739 #, c-format msgid "Window partitioning columns must be of sortable datatypes." msgstr "" "Les colonnes de partitionnement de window doivent être d'un type de données\n" "triables." -#: optimizer/plan/planner.c:5741 +#: optimizer/plan/planner.c:5743 #, c-format msgid "could not implement window ORDER BY" msgstr "n'a pas pu implanter ORDER BY dans le window" -#: optimizer/plan/planner.c:5742 +#: optimizer/plan/planner.c:5744 #, c-format msgid "Window ordering columns must be of sortable datatypes." msgstr "Les colonnes de tri de la window doivent être d'un type de données triable." @@ -16876,7 +16901,7 @@ msgid "rules with WHERE conditions can only have SELECT, INSERT, UPDATE, or DELETE actions" msgstr "les règles avec des conditions WHERE ne peuvent contenir que des actions SELECT, INSERT, UPDATE ou DELETE " -#: parser/parse_utilcmd.c:3057 parser/parse_utilcmd.c:3158 rewrite/rewriteHandler.c:525 rewrite/rewriteManip.c:1021 +#: parser/parse_utilcmd.c:3057 parser/parse_utilcmd.c:3158 rewrite/rewriteHandler.c:527 rewrite/rewriteManip.c:1021 #, c-format msgid "conditional UNION/INTERSECT/EXCEPT statements are not implemented" msgstr "" @@ -17372,32 +17397,32 @@ msgid "autovacuum: processing database \"%s\"" msgstr "autovacuum : traitement de la base de données « %s »" -#: postmaster/autovacuum.c:2259 +#: postmaster/autovacuum.c:2271 #, c-format msgid "autovacuum: dropping orphan temp table \"%s.%s.%s\"" msgstr "autovacuum : suppression de la table temporaire orpheline « %s.%s.%s »" -#: postmaster/autovacuum.c:2488 +#: postmaster/autovacuum.c:2500 #, c-format msgid "automatic vacuum of table \"%s.%s.%s\"" msgstr "VACUUM automatique de la table « %s.%s.%s »" -#: postmaster/autovacuum.c:2491 +#: postmaster/autovacuum.c:2503 #, c-format msgid "automatic analyze of table \"%s.%s.%s\"" msgstr "ANALYZE automatique de la table « %s.%s.%s »" -#: postmaster/autovacuum.c:2684 +#: postmaster/autovacuum.c:2696 #, c-format msgid "processing work entry for relation \"%s.%s.%s\"" msgstr "traitement de l'enregistrement de travail pour la relation « %s.%s.%s »" -#: postmaster/autovacuum.c:3288 +#: postmaster/autovacuum.c:3300 #, c-format msgid "autovacuum not started because of misconfiguration" msgstr "autovacuum non démarré à cause d'une mauvaise configuration" -#: postmaster/autovacuum.c:3289 +#: postmaster/autovacuum.c:3301 #, c-format msgid "Enable the \"track_counts\" option." msgstr "Activez l'option « track_counts »." @@ -19355,7 +19380,7 @@ msgid "could not write to log segment %s at offset %u, length %lu: %m" msgstr "n'a pas pu écrire le journal de transactions %s au décalage %u, longueur %lu : %m" -#: replication/walsender.c:528 storage/smgr/md.c:1330 +#: replication/walsender.c:528 storage/smgr/md.c:1333 #, c-format msgid "could not seek to end of file \"%s\": %m" msgstr "n'a pas pu trouver la fin du fichier « %s » : %m" @@ -19703,206 +19728,206 @@ msgid "renaming an ON SELECT rule is not allowed" msgstr "le renommage d'une règle ON SELECT n'est pas autorisé" -#: rewrite/rewriteHandler.c:569 +#: rewrite/rewriteHandler.c:571 #, c-format msgid "WITH query name \"%s\" appears in both a rule action and the query being rewritten" msgstr "Le nom de la requête WITH « %s » apparaît à la fois dans l'action d'une règle et dans la requête en cours de ré-écriture" -#: rewrite/rewriteHandler.c:596 +#: rewrite/rewriteHandler.c:598 #, c-format msgid "INSERT...SELECT rule actions are not supported for queries having data-modifying statements in WITH" msgstr "les actions de règle INSERT...SELECT ne sont pas supportées par les requêtes de modification de données dans WITH" -#: rewrite/rewriteHandler.c:649 +#: rewrite/rewriteHandler.c:651 #, c-format msgid "cannot have RETURNING lists in multiple rules" msgstr "ne peut pas avoir des listes RETURNING dans plusieurs règles" -#: rewrite/rewriteHandler.c:860 rewrite/rewriteHandler.c:872 +#: rewrite/rewriteHandler.c:862 rewrite/rewriteHandler.c:874 #, c-format msgid "cannot insert into column \"%s\"" msgstr "ne peut pas insérer dans la colonne « %s »" -#: rewrite/rewriteHandler.c:861 rewrite/rewriteHandler.c:883 +#: rewrite/rewriteHandler.c:863 rewrite/rewriteHandler.c:885 #, c-format msgid "Column \"%s\" is an identity column defined as GENERATED ALWAYS." msgstr "La colonne « %s » est une colonne d'identité définie comme GENERATED ALWAYS." -#: rewrite/rewriteHandler.c:863 +#: rewrite/rewriteHandler.c:865 #, c-format msgid "Use OVERRIDING SYSTEM VALUE to override." msgstr "Utilisez OVERRIDING SYSTEM VALUE pour surcharger." -#: rewrite/rewriteHandler.c:882 rewrite/rewriteHandler.c:889 +#: rewrite/rewriteHandler.c:884 rewrite/rewriteHandler.c:891 #, c-format msgid "column \"%s\" can only be updated to DEFAULT" msgstr "la colonne « %s » peut seulement être mise à jour en DEFAULT" -#: rewrite/rewriteHandler.c:1058 rewrite/rewriteHandler.c:1076 +#: rewrite/rewriteHandler.c:1060 rewrite/rewriteHandler.c:1078 #, c-format msgid "multiple assignments to same column \"%s\"" msgstr "affectations multiples pour la même colonne « %s »" -#: rewrite/rewriteHandler.c:2068 rewrite/rewriteHandler.c:3925 +#: rewrite/rewriteHandler.c:2070 rewrite/rewriteHandler.c:3927 #, c-format msgid "infinite recursion detected in rules for relation \"%s\"" msgstr "récursion infinie détectée dans les règles de la relation « %s »" -#: rewrite/rewriteHandler.c:2153 +#: rewrite/rewriteHandler.c:2155 #, c-format msgid "infinite recursion detected in policy for relation \"%s\"" msgstr "récursion infinie détectée dans la politique pour la relation « %s »" -#: rewrite/rewriteHandler.c:2473 +#: rewrite/rewriteHandler.c:2475 msgid "Junk view columns are not updatable." msgstr "Les colonnes « junk » des vues ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2478 +#: rewrite/rewriteHandler.c:2480 msgid "View columns that are not columns of their base relation are not updatable." msgstr "Les colonnes des vues qui ne font pas référence à des colonnes de la relation de base ne sont pas automatiquement modifiables." -#: rewrite/rewriteHandler.c:2481 +#: rewrite/rewriteHandler.c:2483 msgid "View columns that refer to system columns are not updatable." msgstr "Les colonnes des vues qui font référence à des colonnes systèmes ne sont pas automatiquement modifiables." -#: rewrite/rewriteHandler.c:2484 +#: rewrite/rewriteHandler.c:2486 msgid "View columns that return whole-row references are not updatable." msgstr "Les colonnes de vue qui font références à des lignes complètes ne sont pas automatiquement modifiables." -#: rewrite/rewriteHandler.c:2545 +#: rewrite/rewriteHandler.c:2547 msgid "Views containing DISTINCT are not automatically updatable." msgstr "Les vues contenant DISTINCT ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2548 +#: rewrite/rewriteHandler.c:2550 msgid "Views containing GROUP BY are not automatically updatable." msgstr "Les vues contenant GROUP BY ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2551 +#: rewrite/rewriteHandler.c:2553 msgid "Views containing HAVING are not automatically updatable." msgstr "Les vues contenant HAVING ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2554 +#: rewrite/rewriteHandler.c:2556 msgid "Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable." msgstr "Les vues contenant UNION, INTERSECT ou EXCEPT ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2557 +#: rewrite/rewriteHandler.c:2559 msgid "Views containing WITH are not automatically updatable." msgstr "Les vues contenant WITH ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2560 +#: rewrite/rewriteHandler.c:2562 msgid "Views containing LIMIT or OFFSET are not automatically updatable." msgstr "Les vues contenant LIMIT ou OFFSET ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2572 +#: rewrite/rewriteHandler.c:2574 msgid "Views that return aggregate functions are not automatically updatable." msgstr "Les vues qui renvoient des fonctions d'agrégat ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2575 +#: rewrite/rewriteHandler.c:2577 msgid "Views that return window functions are not automatically updatable." msgstr "Les vues qui renvoient des fonctions de fenêtrage ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2578 +#: rewrite/rewriteHandler.c:2580 msgid "Views that return set-returning functions are not automatically updatable." msgstr "Les vues qui renvoient des fonctions à plusieurs lignes ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2585 rewrite/rewriteHandler.c:2589 rewrite/rewriteHandler.c:2597 +#: rewrite/rewriteHandler.c:2587 rewrite/rewriteHandler.c:2591 rewrite/rewriteHandler.c:2599 msgid "Views that do not select from a single table or view are not automatically updatable." msgstr "Les vues qui lisent plusieurs tables ou vues ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2600 +#: rewrite/rewriteHandler.c:2602 msgid "Views containing TABLESAMPLE are not automatically updatable." msgstr "Les vues contenant TABLESAMPLE ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:2624 +#: rewrite/rewriteHandler.c:2626 msgid "Views that have no updatable columns are not automatically updatable." msgstr "Les vues qui possèdent des colonnes non modifiables ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:3101 +#: rewrite/rewriteHandler.c:3103 #, c-format msgid "cannot insert into column \"%s\" of view \"%s\"" msgstr "ne peut pas insérer dans la colonne « %s » de la vue « %s »" -#: rewrite/rewriteHandler.c:3109 +#: rewrite/rewriteHandler.c:3111 #, c-format msgid "cannot update column \"%s\" of view \"%s\"" msgstr "ne peut pas mettre à jour la colonne « %s » de la vue « %s »" -#: rewrite/rewriteHandler.c:3594 +#: rewrite/rewriteHandler.c:3596 #, c-format msgid "DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH" msgstr "les règles DO INSTEAD NOTHING ne sont pas supportées par les instructions de modification de données dans WITH" -#: rewrite/rewriteHandler.c:3605 +#: rewrite/rewriteHandler.c:3607 #, c-format msgid "DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH" msgstr "les règles DO INSTEAD NOTHING ne sont pas supportées par les instructions de modification de données dans WITH" -#: rewrite/rewriteHandler.c:3619 +#: rewrite/rewriteHandler.c:3621 #, c-format msgid "conditional DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "" "les règles DO INSTEAD conditionnelles ne sont pas supportées par les\n" "instructions de modification de données dans WITH" -#: rewrite/rewriteHandler.c:3623 +#: rewrite/rewriteHandler.c:3625 #, c-format msgid "DO ALSO rules are not supported for data-modifying statements in WITH" msgstr "les règles DO ALSO ne sont pas supportées par les instructions de modification de données dans WITH" -#: rewrite/rewriteHandler.c:3628 +#: rewrite/rewriteHandler.c:3630 #, c-format msgid "multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "" "les règles DO INSTEAD multi-instructions ne sont pas supportées pour les\n" "instructions de modification de données dans WITH" -#: rewrite/rewriteHandler.c:3853 rewrite/rewriteHandler.c:3861 rewrite/rewriteHandler.c:3869 +#: rewrite/rewriteHandler.c:3855 rewrite/rewriteHandler.c:3863 rewrite/rewriteHandler.c:3871 #, c-format msgid "Views with conditional DO INSTEAD rules are not automatically updatable." msgstr "Les vues contenant des règles DO INSTEAD conditionnelles ne sont pas automatiquement disponibles en écriture." -#: rewrite/rewriteHandler.c:3974 +#: rewrite/rewriteHandler.c:3976 #, c-format msgid "cannot perform INSERT RETURNING on relation \"%s\"" msgstr "ne peut pas exécuter INSERT RETURNING sur la relation « %s »" -#: rewrite/rewriteHandler.c:3976 +#: rewrite/rewriteHandler.c:3978 #, c-format msgid "You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause." msgstr "" "Vous avez besoin d'une règle ON INSERT DO INSTEAD sans condition avec une\n" "clause RETURNING." -#: rewrite/rewriteHandler.c:3981 +#: rewrite/rewriteHandler.c:3983 #, c-format msgid "cannot perform UPDATE RETURNING on relation \"%s\"" msgstr "ne peut pas exécuter UPDATE RETURNING sur la relation « %s »" -#: rewrite/rewriteHandler.c:3983 +#: rewrite/rewriteHandler.c:3985 #, c-format msgid "You need an unconditional ON UPDATE DO INSTEAD rule with a RETURNING clause." msgstr "" "Vous avez besoin d'une règle ON UPDATE DO INSTEAD sans condition avec une\n" "clause RETURNING." -#: rewrite/rewriteHandler.c:3988 +#: rewrite/rewriteHandler.c:3990 #, c-format msgid "cannot perform DELETE RETURNING on relation \"%s\"" msgstr "ne peut pas exécuter DELETE RETURNING sur la relation « %s »" -#: rewrite/rewriteHandler.c:3990 +#: rewrite/rewriteHandler.c:3992 #, c-format msgid "You need an unconditional ON DELETE DO INSTEAD rule with a RETURNING clause." msgstr "" "Vous avez besoin d'une règle ON DELETE DO INSTEAD sans condition avec une\n" "clause RETURNING." -#: rewrite/rewriteHandler.c:4008 +#: rewrite/rewriteHandler.c:4010 #, c-format msgid "INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules" msgstr "INSERT avec une clause ON CONFLICT ne peut pas être utilisée avec une table qui a des règles pour INSERT ou UPDATE" -#: rewrite/rewriteHandler.c:4065 +#: rewrite/rewriteHandler.c:4067 #, c-format msgid "WITH cannot be used in a query that is rewritten by rules into multiple queries" msgstr "WITH ne peut pas être utilisé dans une requête réécrite par des règles en plusieurs requêtes" @@ -20311,17 +20336,17 @@ msgid "%s failed: %m" msgstr "échec de %s : %m" -#: storage/ipc/procarray.c:3126 +#: storage/ipc/procarray.c:3127 #, c-format msgid "database \"%s\" is being used by prepared transactions" msgstr "la base de données « %s » est utilisée par des transactions préparées." -#: storage/ipc/procarray.c:3158 storage/ipc/signalfuncs.c:142 +#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:142 #, c-format msgid "must be a superuser to terminate superuser process" msgstr "doit être super-utilisateur pour terminer le processus d'un super-utilisateur" -#: storage/ipc/procarray.c:3165 storage/ipc/signalfuncs.c:147 +#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:147 #, c-format msgid "must be a member of the role whose process is being terminated or member of pg_signal_backend" msgstr "doit être un membre du rôle dont le processus est en cours d'arrêt ou membre de pg_signal_backend" @@ -20336,7 +20361,7 @@ msgid "invalid message size %zu in shared memory queue" msgstr "taille %zu invalide pour le message dans la queue de mémoire partagée" -#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:982 storage/lmgr/lock.c:1020 storage/lmgr/lock.c:2845 storage/lmgr/lock.c:4252 storage/lmgr/lock.c:4317 storage/lmgr/lock.c:4667 storage/lmgr/predicate.c:2489 storage/lmgr/predicate.c:2504 storage/lmgr/predicate.c:3994 storage/lmgr/predicate.c:5109 utils/hash/dynahash.c:1067 +#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:963 storage/lmgr/lock.c:1001 storage/lmgr/lock.c:2821 storage/lmgr/lock.c:4228 storage/lmgr/lock.c:4293 storage/lmgr/lock.c:4643 storage/lmgr/predicate.c:2489 storage/lmgr/predicate.c:2504 storage/lmgr/predicate.c:3994 storage/lmgr/predicate.c:5109 utils/hash/dynahash.c:1067 #, c-format msgid "out of shared memory" msgstr "mémoire partagée épuisée" @@ -20371,7 +20396,7 @@ msgid "PID %d is not a PostgreSQL server process" msgstr "le PID %d n'est pas un processus du serveur PostgreSQL" -#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1370 +#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1372 #, c-format msgid "could not send signal to process %d: %m" msgstr "n'a pas pu envoyer le signal au processus %d : %m" @@ -20432,22 +20457,22 @@ msgid "invalid large object write request size: %d" msgstr "taille de la requête d'écriture du « Large Object » invalide : %d" -#: storage/lmgr/deadlock.c:1124 +#: storage/lmgr/deadlock.c:1123 #, c-format msgid "Process %d waits for %s on %s; blocked by process %d." msgstr "Le processus %d attend %s sur %s ; bloqué par le processus %d." -#: storage/lmgr/deadlock.c:1143 +#: storage/lmgr/deadlock.c:1142 #, c-format msgid "Process %d: %s" msgstr "Processus %d : %s" -#: storage/lmgr/deadlock.c:1152 +#: storage/lmgr/deadlock.c:1151 #, c-format msgid "deadlock detected" msgstr "interblocage (deadlock) détecté" -#: storage/lmgr/deadlock.c:1155 +#: storage/lmgr/deadlock.c:1154 #, c-format msgid "See server log for query details." msgstr "Voir les journaux applicatifs du serveur pour les détails sur la requête." @@ -20552,26 +20577,26 @@ msgid "unrecognized locktag type %d" msgstr "type locktag non reconnu %d" -#: storage/lmgr/lock.c:803 +#: storage/lmgr/lock.c:791 #, c-format msgid "cannot acquire lock mode %s on database objects while recovery is in progress" msgstr "" "ne peut pas acquérir le mode de verrou %s sur les objets de base de données\n" "alors que la restauration est en cours" -#: storage/lmgr/lock.c:805 +#: storage/lmgr/lock.c:793 #, c-format msgid "Only RowExclusiveLock or less can be acquired on database objects during recovery." msgstr "" "Seuls RowExclusiveLock et les verrous inférieurs peuvent être acquis sur les\n" "objets d'une base pendant une restauration." -#: storage/lmgr/lock.c:983 storage/lmgr/lock.c:1021 storage/lmgr/lock.c:2846 storage/lmgr/lock.c:4253 storage/lmgr/lock.c:4318 storage/lmgr/lock.c:4668 +#: storage/lmgr/lock.c:964 storage/lmgr/lock.c:1002 storage/lmgr/lock.c:2822 storage/lmgr/lock.c:4229 storage/lmgr/lock.c:4294 storage/lmgr/lock.c:4644 #, c-format msgid "You might need to increase max_locks_per_transaction." msgstr "Vous pourriez avoir besoin d'augmenter max_locks_per_transaction." -#: storage/lmgr/lock.c:3301 storage/lmgr/lock.c:3369 storage/lmgr/lock.c:3485 +#: storage/lmgr/lock.c:3277 storage/lmgr/lock.c:3345 storage/lmgr/lock.c:3461 #, c-format msgid "cannot PREPARE while holding both session-level and transaction-level locks on the same object" msgstr "ne peut pas utiliser PREPARE lorsque des verrous de niveau session et deniveau transaction sont détenus sur le même objet" @@ -20649,41 +20674,41 @@ "le nombre de connexions demandées par le serveur en attente dépasse\n" "max_wal_senders (actuellement %d)" -#: storage/lmgr/proc.c:1341 +#: storage/lmgr/proc.c:1343 #, c-format msgid "Process %d waits for %s on %s." msgstr "Le processus %d attend %s sur %s." -#: storage/lmgr/proc.c:1352 +#: storage/lmgr/proc.c:1354 #, c-format msgid "sending cancel to blocking autovacuum PID %d" msgstr "envoi de l'annulation pour bloquer le PID %d de l'autovacuum" -#: storage/lmgr/proc.c:1472 +#: storage/lmgr/proc.c:1474 #, c-format msgid "process %d avoided deadlock for %s on %s by rearranging queue order after %ld.%03d ms" msgstr "" "le processus %d a évité un verrou mortel pour %s sur %s en modifiant l'ordre\n" "de la queue après %ld.%03d ms" -#: storage/lmgr/proc.c:1487 +#: storage/lmgr/proc.c:1489 #, c-format msgid "process %d detected deadlock while waiting for %s on %s after %ld.%03d ms" msgstr "" "le processus %d a détecté un verrou mortel alors qu'il était en attente de\n" "%s sur %s après %ld.%03d ms" -#: storage/lmgr/proc.c:1496 +#: storage/lmgr/proc.c:1498 #, c-format msgid "process %d still waiting for %s on %s after %ld.%03d ms" msgstr "le processus %d est toujours en attente de %s sur %s après %ld.%03d ms" -#: storage/lmgr/proc.c:1503 +#: storage/lmgr/proc.c:1505 #, c-format msgid "process %d acquired %s on %s after %ld.%03d ms" msgstr "le processus %d a acquis %s sur %s après %ld.%03d ms" -#: storage/lmgr/proc.c:1519 +#: storage/lmgr/proc.c:1521 #, c-format msgid "process %d failed to acquire %s on %s after %ld.%03d ms" msgstr "le processus %d a échoué pour l'acquisition de %s sur %s après %ld.%03d ms" @@ -20713,78 +20738,78 @@ msgid "corrupted line pointer: offset = %u, size = %u" msgstr "pointeur de ligne corrompu : décalage = %u, taille = %u" -#: storage/smgr/md.c:317 storage/smgr/md.c:875 +#: storage/smgr/md.c:320 storage/smgr/md.c:878 #, c-format msgid "could not truncate file \"%s\": %m" msgstr "n'a pas pu tronquer le fichier « %s » : %m" -#: storage/smgr/md.c:446 +#: storage/smgr/md.c:449 #, c-format msgid "cannot extend file \"%s\" beyond %u blocks" msgstr "ne peut pas étendre le fichier « %s » de plus de %u blocs" -#: storage/smgr/md.c:461 +#: storage/smgr/md.c:464 #, c-format msgid "could not extend file \"%s\": %m" msgstr "n'a pas pu étendre le fichier « %s » : %m" -#: storage/smgr/md.c:463 storage/smgr/md.c:470 storage/smgr/md.c:758 +#: storage/smgr/md.c:466 storage/smgr/md.c:473 storage/smgr/md.c:761 #, c-format msgid "Check free disk space." msgstr "Vérifiez l'espace disque disponible." -#: storage/smgr/md.c:467 +#: storage/smgr/md.c:470 #, c-format msgid "could not extend file \"%s\": wrote only %d of %d bytes at block %u" msgstr "" "n'a pas pu étendre le fichier « %s » : a écrit seulement %d octets sur %d\n" "au bloc %u" -#: storage/smgr/md.c:679 +#: storage/smgr/md.c:682 #, c-format msgid "could not read block %u in file \"%s\": %m" msgstr "n'a pas pu lire le bloc %u dans le fichier « %s » : %m" -#: storage/smgr/md.c:695 +#: storage/smgr/md.c:698 #, c-format msgid "could not read block %u in file \"%s\": read only %d of %d bytes" msgstr "" "n'a pas pu lire le bloc %u du fichier « %s » : a lu seulement %d octets\n" "sur %d" -#: storage/smgr/md.c:749 +#: storage/smgr/md.c:752 #, c-format msgid "could not write block %u in file \"%s\": %m" msgstr "n'a pas pu écrire le bloc %u dans le fichier « %s » : %m" -#: storage/smgr/md.c:754 +#: storage/smgr/md.c:757 #, c-format msgid "could not write block %u in file \"%s\": wrote only %d of %d bytes" msgstr "" "n'a pas pu écrire le bloc %u du fichier « %s » : a seulement écrit %d\n" "octets sur %d" -#: storage/smgr/md.c:846 +#: storage/smgr/md.c:849 #, c-format msgid "could not truncate file \"%s\" to %u blocks: it's only %u blocks now" msgstr "n'a pas pu tronquer le fichier « %s » en %u blocs : il y a seulement %u blocs" -#: storage/smgr/md.c:901 +#: storage/smgr/md.c:904 #, c-format msgid "could not truncate file \"%s\" to %u blocks: %m" msgstr "n'a pas pu tronquer le fichier « %s » en %u blocs : %m" -#: storage/smgr/md.c:996 +#: storage/smgr/md.c:999 #, c-format msgid "could not forward fsync request because request queue is full" msgstr "n'a pas pu envoyer la requête fsync car la queue des requêtes est pleine" -#: storage/smgr/md.c:1295 +#: storage/smgr/md.c:1298 #, c-format msgid "could not open file \"%s\" (target block %u): previous segment is only %u blocks" msgstr "n'a pas pu ouvrir le fichier « %s » (bloc cible %u) : le segment précédent ne fait que %u blocs" -#: storage/smgr/md.c:1309 +#: storage/smgr/md.c:1312 #, c-format msgid "could not open file \"%s\" (target block %u): %m" msgstr "n'a pas pu ouvrir le fichier « %s » (bloc cible %u) : %m" @@ -20845,7 +20870,7 @@ msgid "unexpected EOF on client connection" msgstr "fin de fichier (EOF) inattendue de la connexion du client" -#: tcop/postgres.c:440 tcop/postgres.c:452 tcop/postgres.c:463 tcop/postgres.c:475 tcop/postgres.c:4583 +#: tcop/postgres.c:440 tcop/postgres.c:452 tcop/postgres.c:463 tcop/postgres.c:475 tcop/postgres.c:4587 #, c-format msgid "invalid frontend message type %d" msgstr "type %d du message de l'interface invalide" @@ -21105,27 +21130,27 @@ msgid "%s: no database nor user name specified" msgstr "%s : ni base de données ni utilisateur spécifié" -#: tcop/postgres.c:4491 +#: tcop/postgres.c:4495 #, c-format msgid "invalid CLOSE message subtype %d" msgstr "sous-type %d du message CLOSE invalide" -#: tcop/postgres.c:4526 +#: tcop/postgres.c:4530 #, c-format msgid "invalid DESCRIBE message subtype %d" msgstr "sous-type %d du message DESCRIBE invalide" -#: tcop/postgres.c:4604 +#: tcop/postgres.c:4608 #, c-format msgid "fastpath function calls not supported in a replication connection" msgstr "appels à la fonction fastpath non supportés dans une connexion de réplication" -#: tcop/postgres.c:4608 +#: tcop/postgres.c:4612 #, c-format msgid "extended query protocol not supported in a replication connection" msgstr "protocole étendu de requêtes non supporté dans une connexion de réplication" -#: tcop/postgres.c:4785 +#: tcop/postgres.c:4789 #, c-format msgid "disconnection: session time: %d:%02d:%02d.%03d user=%s database=%s host=%s%s%s" msgstr "" @@ -21408,27 +21433,27 @@ msgid "text search parser does not support headline creation" msgstr "l'analyseur de recherche plein texte ne supporte pas headline" -#: tsearch/wparser_def.c:2585 +#: tsearch/wparser_def.c:2600 #, c-format msgid "unrecognized headline parameter: \"%s\"" msgstr "paramètre headline non reconnu : « %s »" -#: tsearch/wparser_def.c:2604 +#: tsearch/wparser_def.c:2619 #, c-format msgid "MinWords should be less than MaxWords" msgstr "MinWords doit avoir une valeur plus petite que celle de MaxWords" -#: tsearch/wparser_def.c:2608 +#: tsearch/wparser_def.c:2623 #, c-format msgid "MinWords should be positive" msgstr "MinWords doit être positif" -#: tsearch/wparser_def.c:2612 +#: tsearch/wparser_def.c:2627 #, c-format msgid "ShortWord should be >= 0" msgstr "ShortWord devrait être positif ou nul" -#: tsearch/wparser_def.c:2616 +#: tsearch/wparser_def.c:2631 #, c-format msgid "MaxFragments should be >= 0" msgstr "MaxFragments devrait être positif ou nul" @@ -22971,42 +22996,42 @@ msgid "jsonpath item method .%s() can only be applied to a string" msgstr "la méthode de l'objet jsonpath .%s() ne peut être appliquée qu'à une chaîne" -#: utils/adt/jsonpath_exec.c:1894 +#: utils/adt/jsonpath_exec.c:1903 #, c-format msgid "datetime format is not recognized: \"%s\"" msgstr "le format datetime n'est pas reconnu : « %s »" -#: utils/adt/jsonpath_exec.c:1896 +#: utils/adt/jsonpath_exec.c:1905 #, c-format msgid "Use a datetime template argument to specify the input data format." msgstr "Utilisez un argument modèle de datetime pour indiquer le format de données en entrée." -#: utils/adt/jsonpath_exec.c:1964 +#: utils/adt/jsonpath_exec.c:1973 #, c-format msgid "jsonpath item method .%s() can only be applied to an object" msgstr "la méthode .%s() de l'entité jsonpath ne peut être appliquée qu'à un objet" -#: utils/adt/jsonpath_exec.c:2147 +#: utils/adt/jsonpath_exec.c:2156 #, c-format msgid "could not find jsonpath variable \"%s\"" msgstr "n'a pas pu trouver la variable jsonpath « %s »" -#: utils/adt/jsonpath_exec.c:2411 +#: utils/adt/jsonpath_exec.c:2420 #, c-format msgid "jsonpath array subscript is not a single numeric value" msgstr "l'indice du tableau jsonpath n'est pas une valeur numérique unique" -#: utils/adt/jsonpath_exec.c:2423 +#: utils/adt/jsonpath_exec.c:2432 #, c-format msgid "jsonpath array subscript is out of integer range" msgstr "indice du tableau jsonpath hors des limites d'un entier" -#: utils/adt/jsonpath_exec.c:2600 +#: utils/adt/jsonpath_exec.c:2609 #, c-format msgid "cannot convert value from %s to %s without time zone usage" msgstr "ne peut pas convertir la valeur de %s à %s sans utilisation des fuseaux horaires" -#: utils/adt/jsonpath_exec.c:2602 +#: utils/adt/jsonpath_exec.c:2611 #, c-format msgid "Use *_tz() function for time zone support." msgstr "Utilisez la fonction *_tz() pour le support des fuseaux horaires." @@ -24411,22 +24436,22 @@ msgid "operator class \"%s\" of access method %s is missing support function %d for type %s" msgstr "la classe d'opérateur « %s » de la méthode d'accès %s nécessite la fonction de support manquante %d pour le type %s" -#: utils/cache/plancache.c:718 +#: utils/cache/plancache.c:720 #, c-format msgid "cached plan must not change result type" msgstr "le plan en cache ne doit pas modifier le type en résultat" -#: utils/cache/relcache.c:6200 +#: utils/cache/relcache.c:6201 #, c-format msgid "could not create relation-cache initialization file \"%s\": %m" msgstr "n'a pas pu créer le fichier d'initialisation relation-cache « %s » : %m" -#: utils/cache/relcache.c:6202 +#: utils/cache/relcache.c:6203 #, c-format msgid "Continuing anyway, but there's something wrong." msgstr "Continue malgré tout, mais quelque chose s'est mal passé." -#: utils/cache/relcache.c:6524 +#: utils/cache/relcache.c:6525 #, c-format msgid "could not remove cache file \"%s\": %m" msgstr "n'a pas pu supprimer le fichier cache « %s » : %m" @@ -25041,17 +25066,22 @@ msgid "database %u does not exist" msgstr "la base de données « %u » n'existe pas" -#: utils/init/postinit.c:983 +#: utils/init/postinit.c:984 #, c-format msgid "It seems to have just been dropped or renamed." msgstr "Cet objet semble avoir été tout juste supprimé ou renommé." -#: utils/init/postinit.c:1001 +#: utils/init/postinit.c:991 +#, c-format +msgid "cannot connect to invalid database \"%s\"" +msgstr "ne peut pas se connecter à la base de données invalide « %s »" + +#: utils/init/postinit.c:1011 #, c-format msgid "The database subdirectory \"%s\" is missing." msgstr "Le sous-répertoire de la base de données « %s » est manquant." -#: utils/init/postinit.c:1006 +#: utils/init/postinit.c:1016 #, c-format msgid "could not access directory \"%s\": %m" msgstr "n'a pas pu accéder au répertoire « %s » : %m" @@ -27481,7 +27511,7 @@ msgid "Failed while creating memory context \"%s\"." msgstr "Échec lors de la création du contexte mémoire « %s »." -#: utils/mmgr/dsa.c:519 utils/mmgr/dsa.c:1332 +#: utils/mmgr/dsa.c:520 utils/mmgr/dsa.c:1337 #, c-format msgid "could not attach to dynamic shared area" msgstr "n'a pas pu attacher le segment de mémoire partagée dynamique" @@ -29078,10 +29108,6 @@ #~ "n'a pas pu utiliser la méthode d'authentification « crypt » car le mot de\n" #~ "passe est chiffré avec MD5" -#, c-format -#~ msgid "cannot use invalid index \"%s\" as replica identity" -#~ msgstr "ne peut pas utiliser l'index invalide « %s » comme identité de réplicat" - #~ msgid "cannot use subquery in parameter default value" #~ msgstr "ne peut pas utiliser une sous-requête dans une valeur par défaut d'un paramètre" diff -Nru postgresql-13-13.11/src/backend/po/ja.po postgresql-13-13.12/src/backend/po/ja.po --- postgresql-13-13.11/src/backend/po/ja.po 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/po/ja.po 2023-08-07 20:11:34.000000000 +0000 @@ -7,8 +7,8 @@ msgstr "" "Project-Id-Version: postgres (PostgreSQL 13)\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2023-04-03 09:36+0900\n" -"PO-Revision-Date: 2023-04-03 16:24+0900\n" +"POT-Creation-Date: 2023-07-18 14:23+0900\n" +"PO-Revision-Date: 2023-07-18 14:47+0900\n" "Last-Translator: Kyotaro Horiguchi \n" "Language-Team: jpug-doc \n" "Language: ja\n" @@ -24,13 +24,13 @@ msgid "not recorded" msgstr "記録されていません" -#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 commands/copy.c:3499 commands/extension.c:3444 utils/adt/genfile.c:125 +#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 commands/copy.c:3499 commands/extension.c:3441 utils/adt/genfile.c:125 #, c-format msgid "could not open file \"%s\" for reading: %m" msgstr "ファイル\"%s\"を読み取り用にオープンできませんでした: %m" -#: ../common/controldata_utils.c:86 ../common/controldata_utils.c:89 access/transam/timeline.c:143 access/transam/timeline.c:362 access/transam/twophase.c:1334 access/transam/xlog.c:3528 access/transam/xlog.c:4772 access/transam/xlog.c:11414 access/transam/xlog.c:11427 access/transam/xlog.c:11882 access/transam/xlog.c:11962 access/transam/xlog.c:12001 access/transam/xlog.c:12044 access/transam/xlogfuncs.c:662 access/transam/xlogfuncs.c:681 -#: commands/extension.c:3454 libpq/hba.c:499 replication/logical/origin.c:717 replication/logical/origin.c:753 replication/logical/reorderbuffer.c:3661 replication/logical/snapbuild.c:1862 replication/logical/snapbuild.c:1904 replication/logical/snapbuild.c:1932 replication/logical/snapbuild.c:1959 replication/slot.c:1716 replication/slot.c:1757 replication/walsender.c:548 storage/file/buffile.c:441 storage/file/copydir.c:195 utils/adt/genfile.c:200 +#: ../common/controldata_utils.c:86 ../common/controldata_utils.c:89 access/transam/timeline.c:143 access/transam/timeline.c:362 access/transam/twophase.c:1334 access/transam/xlog.c:3528 access/transam/xlog.c:4772 access/transam/xlog.c:11418 access/transam/xlog.c:11431 access/transam/xlog.c:11886 access/transam/xlog.c:11966 access/transam/xlog.c:12005 access/transam/xlog.c:12048 access/transam/xlogfuncs.c:662 access/transam/xlogfuncs.c:681 +#: commands/extension.c:3451 libpq/hba.c:499 replication/logical/origin.c:717 replication/logical/origin.c:753 replication/logical/reorderbuffer.c:3661 replication/logical/snapbuild.c:1862 replication/logical/snapbuild.c:1904 replication/logical/snapbuild.c:1932 replication/logical/snapbuild.c:1959 replication/slot.c:1716 replication/slot.c:1757 replication/walsender.c:548 storage/file/buffile.c:441 storage/file/copydir.c:195 utils/adt/genfile.c:200 #: utils/adt/misc.c:792 utils/cache/relmapper.c:744 #, c-format msgid "could not read file \"%s\": %m" @@ -68,18 +68,18 @@ #: ../common/controldata_utils.c:197 ../common/controldata_utils.c:203 ../common/file_utils.c:224 ../common/file_utils.c:283 ../common/file_utils.c:357 access/heap/rewriteheap.c:1264 access/transam/timeline.c:111 access/transam/timeline.c:251 access/transam/timeline.c:348 access/transam/twophase.c:1290 access/transam/xlog.c:3299 access/transam/xlog.c:3439 access/transam/xlog.c:3483 access/transam/xlog.c:3681 access/transam/xlog.c:3766 access/transam/xlog.c:3869 #: access/transam/xlog.c:4762 access/transam/xlogutils.c:807 postmaster/syslogger.c:1488 replication/basebackup.c:621 replication/basebackup.c:1599 replication/logical/origin.c:707 replication/logical/reorderbuffer.c:2512 replication/logical/reorderbuffer.c:2876 replication/logical/reorderbuffer.c:3641 replication/logical/snapbuild.c:1726 replication/logical/snapbuild.c:1833 replication/slot.c:1688 replication/walsender.c:521 replication/walsender.c:2552 -#: storage/file/copydir.c:161 storage/file/fd.c:679 storage/file/fd.c:3432 storage/file/fd.c:3519 storage/smgr/md.c:514 utils/cache/relmapper.c:724 utils/cache/relmapper.c:842 utils/error/elog.c:1858 utils/init/miscinit.c:1321 utils/init/miscinit.c:1455 utils/init/miscinit.c:1532 utils/misc/guc.c:8292 utils/misc/guc.c:8324 +#: storage/file/copydir.c:161 storage/file/fd.c:679 storage/file/fd.c:3432 storage/file/fd.c:3519 storage/smgr/md.c:517 utils/cache/relmapper.c:724 utils/cache/relmapper.c:842 utils/error/elog.c:1858 utils/init/miscinit.c:1321 utils/init/miscinit.c:1455 utils/init/miscinit.c:1532 utils/misc/guc.c:8292 utils/misc/guc.c:8324 #, c-format msgid "could not open file \"%s\": %m" msgstr "ファイル\"%s\"をオープンできませんでした: %m" -#: ../common/controldata_utils.c:221 ../common/controldata_utils.c:224 access/transam/twophase.c:1730 access/transam/twophase.c:1739 access/transam/xlog.c:11171 access/transam/xlog.c:11209 access/transam/xlog.c:11622 access/transam/xlogfuncs.c:741 postmaster/syslogger.c:1499 postmaster/syslogger.c:1512 utils/cache/relmapper.c:876 +#: ../common/controldata_utils.c:221 ../common/controldata_utils.c:224 access/transam/twophase.c:1730 access/transam/twophase.c:1739 access/transam/xlog.c:11175 access/transam/xlog.c:11213 access/transam/xlog.c:11626 access/transam/xlogfuncs.c:741 postmaster/syslogger.c:1499 postmaster/syslogger.c:1512 utils/cache/relmapper.c:876 #, c-format msgid "could not write file \"%s\": %m" msgstr "ファイル\"%s\"を書き出せませんでした: %m" -#: ../common/controldata_utils.c:239 ../common/controldata_utils.c:245 ../common/file_utils.c:295 ../common/file_utils.c:365 access/heap/rewriteheap.c:958 access/heap/rewriteheap.c:1172 access/heap/rewriteheap.c:1275 access/transam/timeline.c:432 access/transam/timeline.c:510 access/transam/twophase.c:1751 access/transam/xlog.c:3390 access/transam/xlog.c:3562 access/transam/xlog.c:4735 access/transam/xlog.c:10659 access/transam/xlog.c:10686 -#: replication/logical/snapbuild.c:1764 replication/slot.c:1593 replication/slot.c:1698 storage/file/fd.c:696 storage/file/fd.c:3540 storage/smgr/md.c:960 storage/smgr/md.c:1001 storage/sync/sync.c:433 utils/cache/relmapper.c:891 utils/misc/guc.c:8075 +#: ../common/controldata_utils.c:239 ../common/controldata_utils.c:245 ../common/file_utils.c:295 ../common/file_utils.c:365 access/heap/rewriteheap.c:958 access/heap/rewriteheap.c:1172 access/heap/rewriteheap.c:1275 access/transam/timeline.c:432 access/transam/timeline.c:510 access/transam/twophase.c:1751 access/transam/xlog.c:3390 access/transam/xlog.c:3562 access/transam/xlog.c:4735 access/transam/xlog.c:10663 access/transam/xlog.c:10690 +#: replication/logical/snapbuild.c:1764 replication/slot.c:1593 replication/slot.c:1698 storage/file/fd.c:696 storage/file/fd.c:3540 storage/smgr/md.c:963 storage/smgr/md.c:1004 storage/sync/sync.c:433 utils/cache/relmapper.c:891 utils/misc/guc.c:8075 #, c-format msgid "could not fsync file \"%s\": %m" msgstr "ファイル\"%s\"をfsyncできませんでした: %m" @@ -109,7 +109,7 @@ msgid "could not change directory to \"%s\": %m" msgstr "ディレクトリ\"%s\"に移動できませんでした: %m" -#: ../common/exec.c:300 access/transam/xlog.c:11043 replication/basebackup.c:1424 utils/adt/misc.c:366 +#: ../common/exec.c:300 access/transam/xlog.c:11047 replication/basebackup.c:1424 utils/adt/misc.c:366 #, c-format msgid "could not read symbolic link \"%s\": %m" msgstr "シンボリックリンク\"%s\"を読めませんでした: %m" @@ -120,9 +120,9 @@ msgstr "pcloseが失敗しました: %m" #: ../common/exec.c:577 ../common/exec.c:622 ../common/exec.c:714 ../common/psprintf.c:143 ../common/stringinfo.c:305 ../port/path.c:630 ../port/path.c:668 ../port/path.c:685 access/transam/twophase.c:1404 access/transam/xlog.c:6545 lib/dshash.c:245 libpq/auth.c:1478 libpq/auth.c:1546 libpq/auth.c:2076 libpq/be-secure-gssapi.c:520 postmaster/bgworker.c:349 postmaster/bgworker.c:963 postmaster/postmaster.c:2550 postmaster/postmaster.c:4187 -#: postmaster/postmaster.c:5638 postmaster/postmaster.c:5998 replication/libpqwalreceiver/libpqwalreceiver.c:286 replication/logical/logical.c:176 replication/walsender.c:595 storage/buffer/localbuf.c:442 storage/file/fd.c:854 storage/file/fd.c:1324 storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1079 storage/ipc/procarray.c:1580 storage/ipc/procarray.c:1587 storage/ipc/procarray.c:2024 storage/ipc/procarray.c:2702 +#: postmaster/postmaster.c:5638 postmaster/postmaster.c:5998 replication/libpqwalreceiver/libpqwalreceiver.c:286 replication/logical/logical.c:176 replication/walsender.c:595 storage/buffer/localbuf.c:442 storage/file/fd.c:854 storage/file/fd.c:1324 storage/file/fd.c:1485 storage/file/fd.c:2290 storage/ipc/procarray.c:1080 storage/ipc/procarray.c:1581 storage/ipc/procarray.c:1588 storage/ipc/procarray.c:2025 storage/ipc/procarray.c:2703 #: utils/adt/cryptohashes.c:45 utils/adt/cryptohashes.c:65 utils/adt/formatting.c:1700 utils/adt/formatting.c:1824 utils/adt/formatting.c:1949 utils/adt/pg_locale.c:484 utils/adt/pg_locale.c:648 utils/adt/regexp.c:223 utils/fmgr/dfmgr.c:229 utils/hash/dynahash.c:450 utils/hash/dynahash.c:559 utils/hash/dynahash.c:1071 utils/mb/mbutils.c:401 utils/mb/mbutils.c:428 utils/mb/mbutils.c:757 utils/mb/mbutils.c:783 utils/misc/guc.c:4858 utils/misc/guc.c:4874 -#: utils/misc/guc.c:4887 utils/misc/guc.c:8053 utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:701 utils/mmgr/dsa.c:723 utils/mmgr/dsa.c:804 utils/mmgr/generation.c:233 utils/mmgr/mcxt.c:821 utils/mmgr/mcxt.c:857 utils/mmgr/mcxt.c:895 utils/mmgr/mcxt.c:933 utils/mmgr/mcxt.c:969 utils/mmgr/mcxt.c:1000 utils/mmgr/mcxt.c:1036 utils/mmgr/mcxt.c:1088 utils/mmgr/mcxt.c:1123 utils/mmgr/mcxt.c:1158 utils/mmgr/slab.c:237 +#: utils/misc/guc.c:4887 utils/misc/guc.c:8053 utils/misc/tzparser.c:476 utils/mmgr/aset.c:475 utils/mmgr/dsa.c:702 utils/mmgr/dsa.c:724 utils/mmgr/dsa.c:805 utils/mmgr/generation.c:233 utils/mmgr/mcxt.c:821 utils/mmgr/mcxt.c:857 utils/mmgr/mcxt.c:895 utils/mmgr/mcxt.c:933 utils/mmgr/mcxt.c:969 utils/mmgr/mcxt.c:1000 utils/mmgr/mcxt.c:1036 utils/mmgr/mcxt.c:1088 utils/mmgr/mcxt.c:1123 utils/mmgr/mcxt.c:1158 utils/mmgr/slab.c:237 #, c-format msgid "out of memory" msgstr "メモリ不足です" @@ -137,7 +137,7 @@ msgid "cannot duplicate null pointer (internal error)\n" msgstr "nullポインタは複製できません(内部エラー)\n" -#: ../common/file_utils.c:79 ../common/file_utils.c:181 access/transam/twophase.c:1302 access/transam/xlog.c:8100 access/transam/xlog.c:11030 access/transam/xlog.c:11147 access/transam/xlog.c:11185 access/transam/xlog.c:11402 access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3433 commands/tablespace.c:806 commands/tablespace.c:897 guc-file.l:1064 replication/basebackup.c:444 +#: ../common/file_utils.c:79 ../common/file_utils.c:181 access/transam/twophase.c:1302 access/transam/xlog.c:8104 access/transam/xlog.c:11034 access/transam/xlog.c:11151 access/transam/xlog.c:11189 access/transam/xlog.c:11406 access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3430 commands/tablespace.c:806 commands/tablespace.c:897 guc-file.l:1064 replication/basebackup.c:444 #: replication/basebackup.c:627 replication/basebackup.c:700 replication/logical/snapbuild.c:1640 storage/file/copydir.c:68 storage/file/copydir.c:107 storage/file/fd.c:1836 storage/file/fd.c:3116 storage/file/fd.c:3298 storage/file/fd.c:3384 utils/adt/dbsize.c:70 utils/adt/dbsize.c:222 utils/adt/dbsize.c:302 utils/adt/genfile.c:416 utils/adt/genfile.c:642 utils/adt/misc.c:351 #, c-format msgid "could not stat file \"%s\": %m" @@ -463,32 +463,32 @@ msgid "could not check access token membership: error code %lu\n" msgstr "アクセストークンのメンバーシップを確認できませんでした: エラーコード %lu\n" -#: access/brin/brin.c:210 +#: access/brin/brin.c:211 #, c-format msgid "request for BRIN range summarization for index \"%s\" page %u was not recorded" msgstr "インデックス\"%s\" ページ%uのBRIN範囲要約のリクエストは登録されていません" -#: access/brin/brin.c:876 access/brin/brin.c:980 access/gin/ginfast.c:1038 access/transam/xlog.c:10795 access/transam/xlog.c:11353 access/transam/xlogfuncs.c:274 access/transam/xlogfuncs.c:301 access/transam/xlogfuncs.c:340 access/transam/xlogfuncs.c:361 access/transam/xlogfuncs.c:382 access/transam/xlogfuncs.c:452 access/transam/xlogfuncs.c:509 +#: access/brin/brin.c:962 access/brin/brin.c:1066 access/gin/ginfast.c:1043 access/transam/xlog.c:10799 access/transam/xlog.c:11357 access/transam/xlogfuncs.c:274 access/transam/xlogfuncs.c:301 access/transam/xlogfuncs.c:340 access/transam/xlogfuncs.c:361 access/transam/xlogfuncs.c:382 access/transam/xlogfuncs.c:452 access/transam/xlogfuncs.c:509 #, c-format msgid "recovery is in progress" msgstr "リカバリは現在進行中です" -#: access/brin/brin.c:877 access/brin/brin.c:981 +#: access/brin/brin.c:963 access/brin/brin.c:1067 #, c-format msgid "BRIN control functions cannot be executed during recovery." msgstr "BRIN制御関数はリカバリ中は実行できません。" -#: access/brin/brin.c:885 access/brin/brin.c:989 +#: access/brin/brin.c:971 access/brin/brin.c:1075 #, c-format msgid "block number out of range: %s" msgstr "ブロック番号が範囲外です: %s" -#: access/brin/brin.c:929 access/brin/brin.c:1015 +#: access/brin/brin.c:1015 access/brin/brin.c:1101 #, c-format msgid "\"%s\" is not a BRIN index" msgstr "\"%s\"はBRINインデックスではありません" -#: access/brin/brin.c:945 access/brin/brin.c:1031 +#: access/brin/brin.c:1031 access/brin/brin.c:1117 #, c-format msgid "could not open parent table of index %s" msgstr "インデックス%sの親テーブルをオープンできませんでした" @@ -686,22 +686,22 @@ msgid "Reduce maintenance_work_mem." msgstr "maintenance_work_mem を小さくしてください。" -#: access/gin/ginfast.c:1039 +#: access/gin/ginfast.c:1044 #, c-format msgid "GIN pending list cannot be cleaned up during recovery." msgstr "GIN保留リストはリカバリ中には処理できません。" -#: access/gin/ginfast.c:1046 +#: access/gin/ginfast.c:1051 #, c-format msgid "\"%s\" is not a GIN index" msgstr "\"%s\"はGINインデックスではありません" -#: access/gin/ginfast.c:1057 +#: access/gin/ginfast.c:1062 #, c-format msgid "cannot access temporary indexes of other sessions" msgstr "他のセッションの一時インデックスにはアクセスできません" -#: access/gin/ginget.c:270 access/nbtree/nbtinsert.c:745 +#: access/gin/ginget.c:272 access/nbtree/nbtinsert.c:745 #, c-format msgid "failed to re-find tuple within index \"%s\"" msgstr "インデックス\"%s\"内で行の再検索に失敗しました" @@ -781,7 +781,7 @@ msgid "could not determine which collation to use for string hashing" msgstr "文字列のハッシュ値計算で使用する照合順序を特定できませんでした" -#: access/hash/hashfunc.c:279 access/hash/hashfunc.c:336 catalog/heap.c:709 catalog/heap.c:715 commands/createas.c:206 commands/createas.c:501 commands/indexcmds.c:1918 commands/tablecmds.c:16444 commands/view.c:86 parser/parse_utilcmd.c:4252 regex/regc_pg_locale.c:263 utils/adt/formatting.c:1667 utils/adt/formatting.c:1791 utils/adt/formatting.c:1916 utils/adt/like.c:194 utils/adt/like_support.c:1004 utils/adt/varchar.c:733 utils/adt/varchar.c:994 +#: access/hash/hashfunc.c:279 access/hash/hashfunc.c:336 catalog/heap.c:709 catalog/heap.c:715 commands/createas.c:206 commands/createas.c:501 commands/indexcmds.c:1935 commands/tablecmds.c:16444 commands/view.c:86 parser/parse_utilcmd.c:4252 regex/regc_pg_locale.c:263 utils/adt/formatting.c:1667 utils/adt/formatting.c:1791 utils/adt/formatting.c:1916 utils/adt/like.c:194 utils/adt/like_support.c:1004 utils/adt/varchar.c:733 utils/adt/varchar.c:994 #: utils/adt/varchar.c:1055 utils/adt/varlena.c:1486 #, c-format msgid "Use the COLLATE clause to set the collation explicitly." @@ -877,7 +877,7 @@ msgid "could not write to file \"%s\", wrote %d of %d: %m" msgstr "ファイル\"%1$s\"に書き込めませんでした、%3$dバイト中%2$dバイト書き込みました: %m" -#: access/heap/rewriteheap.c:1012 access/heap/rewriteheap.c:1131 access/transam/timeline.c:329 access/transam/timeline.c:485 access/transam/xlog.c:3322 access/transam/xlog.c:3497 access/transam/xlog.c:4714 access/transam/xlog.c:11162 access/transam/xlog.c:11200 access/transam/xlog.c:11605 access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4650 replication/logical/origin.c:575 replication/slot.c:1540 storage/file/copydir.c:167 storage/smgr/md.c:218 +#: access/heap/rewriteheap.c:1012 access/heap/rewriteheap.c:1131 access/transam/timeline.c:329 access/transam/timeline.c:485 access/transam/xlog.c:3322 access/transam/xlog.c:3497 access/transam/xlog.c:4714 access/transam/xlog.c:11166 access/transam/xlog.c:11204 access/transam/xlog.c:11609 access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4650 replication/logical/origin.c:575 replication/slot.c:1540 storage/file/copydir.c:167 storage/smgr/md.c:218 #: utils/time/snapmgr.c:1358 #, c-format msgid "could not create file \"%s\": %m" @@ -895,7 +895,7 @@ msgstr "ファイル\"%s\"を書き出せませんでした: %m" #: access/heap/rewriteheap.c:1249 access/transam/twophase.c:1690 access/transam/xlogarchive.c:118 access/transam/xlogarchive.c:421 postmaster/postmaster.c:1092 postmaster/syslogger.c:1465 replication/logical/origin.c:563 replication/logical/reorderbuffer.c:3132 replication/logical/snapbuild.c:1682 replication/logical/snapbuild.c:2127 replication/slot.c:1672 storage/file/fd.c:754 storage/file/fd.c:3136 storage/file/fd.c:3198 storage/file/reinit.c:255 -#: storage/ipc/dsm.c:302 storage/smgr/md.c:355 storage/smgr/md.c:405 storage/sync/sync.c:229 utils/time/snapmgr.c:1703 +#: storage/ipc/dsm.c:302 storage/smgr/md.c:358 storage/smgr/md.c:408 storage/sync/sync.c:229 utils/time/snapmgr.c:1703 #, c-format msgid "could not remove file \"%s\": %m" msgstr "ファイル\"%s\"を削除できませんでした: %m" @@ -1001,7 +1001,7 @@ msgstr[0] "%uページが完全に空です。\n" msgstr[1] "%uページが完全に空です。\n" -#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3639 commands/indexcmds.c:3657 +#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3656 commands/indexcmds.c:3674 #, c-format msgid "%s." msgstr "%s。" @@ -1111,7 +1111,7 @@ msgid "index access method \"%s\" does not have a handler" msgstr "インデックスアクセスメソッド\"%s\"はハンドラを持っていません" -#: access/index/indexam.c:142 catalog/objectaddress.c:1260 commands/indexcmds.c:2647 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16142 commands/tablecmds.c:17642 +#: access/index/indexam.c:142 catalog/objectaddress.c:1260 commands/indexcmds.c:2664 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16142 commands/tablecmds.c:17646 #, c-format msgid "\"%s\" is not an index" msgstr "\"%s\"はインデックスではありません" @@ -1136,7 +1136,7 @@ msgid "This may be because of a non-immutable index expression." msgstr "これは不変でないインデックス式が原因である可能性があります" -#: access/nbtree/nbtpage.c:150 access/nbtree/nbtpage.c:536 parser/parse_utilcmd.c:2291 +#: access/nbtree/nbtpage.c:150 access/nbtree/nbtpage.c:536 parser/parse_utilcmd.c:2289 #, c-format msgid "index \"%s\" is not a btree" msgstr "インデックス\"%s\"はbtreeではありません" @@ -1530,12 +1530,12 @@ msgid "transaction identifier \"%s\" is already in use" msgstr "トランザクション識別子\"%s\"はすでに存在します" -#: access/transam/twophase.c:417 access/transam/twophase.c:2450 +#: access/transam/twophase.c:417 access/transam/twophase.c:2483 #, c-format msgid "maximum number of prepared transactions reached" msgstr "準備済みのトランザクションの最大数に達しました" -#: access/transam/twophase.c:418 access/transam/twophase.c:2451 +#: access/transam/twophase.c:418 access/transam/twophase.c:2484 #, c-format msgid "Increase max_prepared_transactions (currently %d)." msgstr "max_prepared_transactionsを増加してください（現状%d）。" @@ -1669,6 +1669,21 @@ msgid "corrupted two-phase state in memory for transaction %u" msgstr "メモリ上にあるトランザクション%uの2相状態が破損しています" +#: access/transam/twophase.c:2465 +#, c-format +msgid "could not recover two-phase state file for transaction %u" +msgstr "トランザクション%uの2相状態ファイルを復元できませんでした" + +#: access/transam/twophase.c:2467 +#, c-format +msgid "Two-phase state file has been found in WAL record %X/%X, but this transaction has already been restored from disk." +msgstr "2相状態ファイルがWALレコード%X/%Xで見つかりましたが、このトランザクションはすでにディスクから復元済みです。" + +#: access/transam/twophase.c:2476 jit/jit.c:205 utils/fmgr/dfmgr.c:209 utils/fmgr/dfmgr.c:417 utils/fmgr/dfmgr.c:465 +#, c-format +msgid "could not access file \"%s\": %m" +msgstr "ファイル\"%s\"にアクセスできませんでした: %m" + #: access/transam/varsup.c:127 #, c-format msgid "database is not accepting commands to avoid wraparound data loss in database \"%s\"" @@ -1863,7 +1878,7 @@ msgid "creating missing WAL directory \"%s\"" msgstr "なかったWALディレクトリ\"%s\"を作成しています" -#: access/transam/xlog.c:4305 commands/dbcommands.c:2208 +#: access/transam/xlog.c:4305 commands/dbcommands.c:2278 #, c-format msgid "could not create missing directory \"%s\": %m" msgstr "なかったディレクトリ\"%s\"の作成に失敗しました: %m" @@ -2261,7 +2276,7 @@ msgid "ignoring file \"%s\" because no file \"%s\" exists" msgstr "ファイル\"%2$s\"が存在しないためファイル\"%1$s\"を無視します" -#: access/transam/xlog.c:6671 access/transam/xlog.c:12123 +#: access/transam/xlog.c:6671 access/transam/xlog.c:12127 #, c-format msgid "File \"%s\" was renamed to \"%s\"." msgstr "ファイル\"%s\"は\"%s\"にリネームされました。" @@ -2386,348 +2401,348 @@ msgid "selected new timeline ID: %u" msgstr "新しいタイムラインIDを選択: %u" -#: access/transam/xlog.c:8108 +#: access/transam/xlog.c:8112 #, c-format msgid "unexpected directory entry \"%s\" found in %s" msgstr "%2$s で想定外のディレクトリエントリ\"%1$s\"が見つかりました" -#: access/transam/xlog.c:8110 +#: access/transam/xlog.c:8114 #, c-format msgid "All directory entries in pg_tblspc/ should be symbolic links." msgstr "Pg_tblspc/ のすべてのディレクトリエントリは、シンボリックリンクである必要があります。" -#: access/transam/xlog.c:8111 +#: access/transam/xlog.c:8115 #, c-format msgid "Remove those directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete." msgstr "これらのディレクトリを削除するか、またはallow_in_place_tablespacesを一時的にONに設定することでリカバリを完了させることができます。" -#: access/transam/xlog.c:8195 +#: access/transam/xlog.c:8199 #, c-format msgid "consistent recovery state reached at %X/%X" msgstr "%X/%X でリカバリの一貫性が確保されました" -#: access/transam/xlog.c:8405 +#: access/transam/xlog.c:8409 #, c-format msgid "invalid primary checkpoint link in control file" msgstr "制御ファイル内の最初のチェックポイントへのリンクが不正です" -#: access/transam/xlog.c:8409 +#: access/transam/xlog.c:8413 #, c-format msgid "invalid checkpoint link in backup_label file" msgstr "backup_labelファイル内のチェックポイントへのリンクが不正です" -#: access/transam/xlog.c:8427 +#: access/transam/xlog.c:8431 #, c-format msgid "invalid primary checkpoint record" msgstr "最初のチェックポイントレコードが不正です" -#: access/transam/xlog.c:8431 +#: access/transam/xlog.c:8435 #, c-format msgid "invalid checkpoint record" msgstr "チェックポイントレコードが不正です" -#: access/transam/xlog.c:8442 +#: access/transam/xlog.c:8446 #, c-format msgid "invalid resource manager ID in primary checkpoint record" msgstr "プライマリチェックポイントレコード内のリソースマネージャIDが不正です" -#: access/transam/xlog.c:8446 +#: access/transam/xlog.c:8450 #, c-format msgid "invalid resource manager ID in checkpoint record" msgstr "チェックポイントレコード内のリソースマネージャIDがで不正です" -#: access/transam/xlog.c:8459 +#: access/transam/xlog.c:8463 #, c-format msgid "invalid xl_info in primary checkpoint record" msgstr "最初のチェックポイントレコード内のxl_infoが不正です" -#: access/transam/xlog.c:8463 +#: access/transam/xlog.c:8467 #, c-format msgid "invalid xl_info in checkpoint record" msgstr "チェックポイントレコード内のxl_infoが不正です" -#: access/transam/xlog.c:8474 +#: access/transam/xlog.c:8478 #, c-format msgid "invalid length of primary checkpoint record" msgstr "最初のチェックポイントレコード長が不正です" -#: access/transam/xlog.c:8478 +#: access/transam/xlog.c:8482 #, c-format msgid "invalid length of checkpoint record" msgstr "チェックポイントレコード長が不正です" -#: access/transam/xlog.c:8658 +#: access/transam/xlog.c:8662 #, c-format msgid "shutting down" msgstr "シャットダウンしています" -#: access/transam/xlog.c:8965 +#: access/transam/xlog.c:8969 #, c-format msgid "checkpoint skipped because system is idle" msgstr "システムがアイドル状態なためチェックポイントがスキップされました" -#: access/transam/xlog.c:9175 +#: access/transam/xlog.c:9179 #, c-format msgid "concurrent write-ahead log activity while database system is shutting down" msgstr "データベースのシャットダウンに並行して、先行書き込みログが発生しました" -#: access/transam/xlog.c:9487 +#: access/transam/xlog.c:9491 #, c-format msgid "skipping restartpoint, recovery has already ended" msgstr "再開ポイントをスキップします、リカバリはすでに終わっています" -#: access/transam/xlog.c:9510 +#: access/transam/xlog.c:9514 #, c-format msgid "skipping restartpoint, already performed at %X/%X" msgstr "%X/%X ですでに実行済みの再開ポイントをスキップします" -#: access/transam/xlog.c:9700 +#: access/transam/xlog.c:9704 #, c-format msgid "recovery restart point at %X/%X" msgstr "リカバリ再開ポイントは%X/%Xです" -#: access/transam/xlog.c:9702 +#: access/transam/xlog.c:9706 #, c-format msgid "Last completed transaction was at log time %s." msgstr "最後に完了したトランザクションはログ時刻 %s のものです" -#: access/transam/xlog.c:9950 +#: access/transam/xlog.c:9954 #, c-format msgid "restore point \"%s\" created at %X/%X" msgstr "復帰ポイント\"%s\"が%X/%Xに作成されました" -#: access/transam/xlog.c:10095 +#: access/transam/xlog.c:10099 #, c-format msgid "unexpected previous timeline ID %u (current timeline ID %u) in checkpoint record" msgstr "チェックポイントレコードにおいて想定外の前回のタイムラインID %u(現在のタイムラインIDは%u)がありました" -#: access/transam/xlog.c:10104 +#: access/transam/xlog.c:10108 #, c-format msgid "unexpected timeline ID %u (after %u) in checkpoint record" msgstr "チェックポイントレコードにおいて想定外のタイムラインID %u (%uの後)がありました" -#: access/transam/xlog.c:10120 +#: access/transam/xlog.c:10124 #, c-format msgid "unexpected timeline ID %u in checkpoint record, before reaching minimum recovery point %X/%X on timeline %u" msgstr "タイムライン%4$uの最小リカバリポイント%2$X/%3$Xに達する前のチェックポイントレコード内の想定外のタイムラインID%1$u。" -#: access/transam/xlog.c:10196 +#: access/transam/xlog.c:10200 #, c-format msgid "online backup was canceled, recovery cannot continue" msgstr "オンラインバックアップはキャンセルされ、リカバリを継続できません" -#: access/transam/xlog.c:10252 access/transam/xlog.c:10308 access/transam/xlog.c:10338 +#: access/transam/xlog.c:10256 access/transam/xlog.c:10312 access/transam/xlog.c:10342 #, c-format msgid "unexpected timeline ID %u (should be %u) in checkpoint record" msgstr "チェックポイントレコードにおいて想定外のタイムラインID %u(%uのはず)がありました" -#: access/transam/xlog.c:10498 +#: access/transam/xlog.c:10502 #, c-format msgid "successfully skipped missing contrecord at %X/%X, overwritten at %s" msgstr "%X/%Xで%sに上書きされて失われた継続行を正常にスキップしました" -#: access/transam/xlog.c:10691 +#: access/transam/xlog.c:10695 #, c-format msgid "could not fsync write-through file \"%s\": %m" msgstr "ライトスルーファイル\"%s\"をfsyncできませんでした: %m" -#: access/transam/xlog.c:10697 +#: access/transam/xlog.c:10701 #, c-format msgid "could not fdatasync file \"%s\": %m" msgstr "ファイル\"%s\"をfdatasyncできませんでした: %m" -#: access/transam/xlog.c:10796 access/transam/xlog.c:11354 access/transam/xlogfuncs.c:275 access/transam/xlogfuncs.c:302 access/transam/xlogfuncs.c:341 access/transam/xlogfuncs.c:362 access/transam/xlogfuncs.c:383 +#: access/transam/xlog.c:10800 access/transam/xlog.c:11358 access/transam/xlogfuncs.c:275 access/transam/xlogfuncs.c:302 access/transam/xlogfuncs.c:341 access/transam/xlogfuncs.c:362 access/transam/xlogfuncs.c:383 #, c-format msgid "WAL control functions cannot be executed during recovery." msgstr "リカバリ中はWAL制御関数は実行できません。" -#: access/transam/xlog.c:10805 access/transam/xlog.c:11363 +#: access/transam/xlog.c:10809 access/transam/xlog.c:11367 #, c-format msgid "WAL level not sufficient for making an online backup" msgstr "オンラインバックアップを行うにはWALレベルが不十分です" -#: access/transam/xlog.c:10806 access/transam/xlog.c:11364 access/transam/xlogfuncs.c:308 +#: access/transam/xlog.c:10810 access/transam/xlog.c:11368 access/transam/xlogfuncs.c:308 #, c-format msgid "wal_level must be set to \"replica\" or \"logical\" at server start." msgstr "サーバの開始時にwal_levelを\"replica\"または \"logical\"にセットする必要があります。" -#: access/transam/xlog.c:10811 +#: access/transam/xlog.c:10815 #, c-format msgid "backup label too long (max %d bytes)" msgstr "バックアップラベルが長すぎます (最大%dバイト)" -#: access/transam/xlog.c:10848 access/transam/xlog.c:11153 access/transam/xlog.c:11191 +#: access/transam/xlog.c:10852 access/transam/xlog.c:11157 access/transam/xlog.c:11195 #, c-format msgid "a backup is already in progress" msgstr "すでにバックアップが進行中です" -#: access/transam/xlog.c:10849 +#: access/transam/xlog.c:10853 #, c-format msgid "Run pg_stop_backup() and try again." msgstr "pg_stop_backup()を実行後に再試行してください" -#: access/transam/xlog.c:10945 +#: access/transam/xlog.c:10949 #, c-format msgid "WAL generated with full_page_writes=off was replayed since last restartpoint" msgstr "full_page_writes=off で生成されたWALは最終リスタートポイントから再生されます" -#: access/transam/xlog.c:10947 access/transam/xlog.c:11559 +#: access/transam/xlog.c:10951 access/transam/xlog.c:11563 #, c-format msgid "This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master, and then try an online backup again." msgstr "つまりこのスタンバイで取得されたバックアップは破損しており、使用すべきではありません。マスターでfull_page_writesを有効にしCHECKPOINTを実行したのち、再度オンラインバックアップを試行してください。" -#: access/transam/xlog.c:11050 replication/basebackup.c:1429 utils/adt/misc.c:371 +#: access/transam/xlog.c:11054 replication/basebackup.c:1429 utils/adt/misc.c:371 #, c-format msgid "symbolic link \"%s\" target is too long" msgstr "シンボリックリンク\"%s\"の参照先が長すぎます" -#: access/transam/xlog.c:11103 commands/tablespace.c:385 commands/tablespace.c:561 replication/basebackup.c:1444 utils/adt/misc.c:379 +#: access/transam/xlog.c:11107 commands/tablespace.c:385 commands/tablespace.c:561 replication/basebackup.c:1444 utils/adt/misc.c:379 #, c-format msgid "tablespaces are not supported on this platform" msgstr "このプラットフォームではテーブル空間はサポートしていません" -#: access/transam/xlog.c:11154 access/transam/xlog.c:11192 +#: access/transam/xlog.c:11158 access/transam/xlog.c:11196 #, c-format msgid "If you're sure there is no backup in progress, remove file \"%s\" and try again." msgstr "バックアップが進行中でないことが確かであれば、ファイル\"%s\"を削除し再実行してください。" -#: access/transam/xlog.c:11379 +#: access/transam/xlog.c:11383 #, c-format msgid "exclusive backup not in progress" msgstr "排他バックアップは進行中ではありません" -#: access/transam/xlog.c:11406 +#: access/transam/xlog.c:11410 #, c-format msgid "a backup is not in progress" msgstr "バックアップが進行中ではありません" -#: access/transam/xlog.c:11492 access/transam/xlog.c:11505 access/transam/xlog.c:11896 access/transam/xlog.c:11902 access/transam/xlog.c:11950 access/transam/xlog.c:12023 access/transam/xlogfuncs.c:692 +#: access/transam/xlog.c:11496 access/transam/xlog.c:11509 access/transam/xlog.c:11900 access/transam/xlog.c:11906 access/transam/xlog.c:11954 access/transam/xlog.c:12027 access/transam/xlogfuncs.c:692 #, c-format msgid "invalid data in file \"%s\"" msgstr "ファイル\"%s\"内の不正なデータ" -#: access/transam/xlog.c:11509 replication/basebackup.c:1277 +#: access/transam/xlog.c:11513 replication/basebackup.c:1277 #, c-format msgid "the standby was promoted during online backup" msgstr "オンラインバックアップ中にスタンバイが昇格しました" -#: access/transam/xlog.c:11510 replication/basebackup.c:1278 +#: access/transam/xlog.c:11514 replication/basebackup.c:1278 #, c-format msgid "This means that the backup being taken is corrupt and should not be used. Try taking another online backup." msgstr "つまり取得中のバックアップは破損しているため使用してはいけません。再度オンラインバックアップを取得してください。" -#: access/transam/xlog.c:11557 +#: access/transam/xlog.c:11561 #, c-format msgid "WAL generated with full_page_writes=off was replayed during online backup" msgstr "full_page_writes=offで生成されたWALはオンラインバックアップ中に再生されます" -#: access/transam/xlog.c:11677 +#: access/transam/xlog.c:11681 #, c-format msgid "base backup done, waiting for required WAL segments to be archived" msgstr "ベースバックアップ完了、必要な WAL セグメントがアーカイブされるのを待っています" -#: access/transam/xlog.c:11689 +#: access/transam/xlog.c:11693 #, c-format msgid "still waiting for all required WAL segments to be archived (%d seconds elapsed)" msgstr "まだ必要なすべての WAL セグメントがアーカイブされるのを待っています（%d 秒経過）" -#: access/transam/xlog.c:11691 +#: access/transam/xlog.c:11695 #, c-format msgid "Check that your archive_command is executing properly. You can safely cancel this backup, but the database backup will not be usable without all the WAL segments." msgstr "archive_commandが適切に実行されていることを確認してください。バックアップ処理は安全に取り消すことができますが、全てのWALセグメントがそろわなければこのバックアップは利用できません。" -#: access/transam/xlog.c:11698 +#: access/transam/xlog.c:11702 #, c-format msgid "all required WAL segments have been archived" msgstr "必要なすべての WAL セグメントがアーカイブされました" -#: access/transam/xlog.c:11702 +#: access/transam/xlog.c:11706 #, c-format msgid "WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backup" msgstr "WAL アーカイブが有効になっていません。バックアップを完了させるには、すべての必要なWALセグメントが他の方法でコピーされたことを確認してください。" -#: access/transam/xlog.c:11757 +#: access/transam/xlog.c:11761 #, c-format msgid "aborting backup due to backend exiting before pg_stop_backup was called" msgstr "バックエンドが pg_stop_backup の呼び出し前に終了したため、バックアップは異常終了しました" -#: access/transam/xlog.c:11933 +#: access/transam/xlog.c:11937 #, c-format msgid "backup time %s in file \"%s\"" msgstr "ファイル\"%2$s\"内のバックアップ時刻は %1$s" -#: access/transam/xlog.c:11938 +#: access/transam/xlog.c:11942 #, c-format msgid "backup label %s in file \"%s\"" msgstr "ファイル\"%2$s\"内のバックアップラベルは %1$s" -#: access/transam/xlog.c:11951 +#: access/transam/xlog.c:11955 #, c-format msgid "Timeline ID parsed is %u, but expected %u." msgstr "読み取られたタイムラインIDは%uでしたが、%uであるはずです。" -#: access/transam/xlog.c:11955 +#: access/transam/xlog.c:11959 #, c-format msgid "backup timeline %u in file \"%s\"" msgstr "ファイル\"%2$s\"内のバックアップタイムラインは %1$u" #. translator: %s is a WAL record description -#: access/transam/xlog.c:12063 +#: access/transam/xlog.c:12067 #, c-format msgid "WAL redo at %X/%X for %s" msgstr "%X/%Xにある%sのWAL再生" -#: access/transam/xlog.c:12112 +#: access/transam/xlog.c:12116 #, c-format msgid "online backup mode was not canceled" msgstr "オンラインバックアップモードはキャンセルされていません" -#: access/transam/xlog.c:12113 +#: access/transam/xlog.c:12117 #, c-format msgid "File \"%s\" could not be renamed to \"%s\": %m." msgstr "ファイル\"%s\"の名前を\"%s\"に変更できませんでした: %m。" -#: access/transam/xlog.c:12122 access/transam/xlog.c:12134 access/transam/xlog.c:12144 +#: access/transam/xlog.c:12126 access/transam/xlog.c:12138 access/transam/xlog.c:12148 #, c-format msgid "online backup mode canceled" msgstr "オンラインバックアップモードがキャンセルされました" -#: access/transam/xlog.c:12135 +#: access/transam/xlog.c:12139 #, c-format msgid "Files \"%s\" and \"%s\" were renamed to \"%s\" and \"%s\", respectively." msgstr "ファイル\"%s\"、\"%s\"の名前はそれぞれ\"%s\"、\"%s\"へと変更されました。" -#: access/transam/xlog.c:12145 +#: access/transam/xlog.c:12149 #, c-format msgid "File \"%s\" was renamed to \"%s\", but file \"%s\" could not be renamed to \"%s\": %m." msgstr "ファイル\"%s\"の名前は\"%s\"に変更できましたが、\"%s\"の名前は\"%s\"に変更できませんでした: %m" -#: access/transam/xlog.c:12278 access/transam/xlogutils.c:971 +#: access/transam/xlog.c:12282 access/transam/xlogutils.c:971 #, c-format msgid "could not read from log segment %s, offset %u: %m" msgstr "ログセグメント%s、オフセット%uを読み取れませんでした: %m" -#: access/transam/xlog.c:12284 access/transam/xlogutils.c:978 +#: access/transam/xlog.c:12288 access/transam/xlogutils.c:978 #, c-format msgid "could not read from log segment %s, offset %u: read %d of %zu" msgstr "ログセグメント%1$s、オフセット%2$uを読み取れませんでした: %4$zu 中 %3$d の読み取り" -#: access/transam/xlog.c:12827 +#: access/transam/xlog.c:12831 #, c-format msgid "WAL receiver process shutdown requested" msgstr "WAL receiverプロセスのシャットダウンが要求されました" -#: access/transam/xlog.c:12933 +#: access/transam/xlog.c:12937 #, c-format msgid "received promote request" msgstr "昇格要求を受信しました" -#: access/transam/xlog.c:12946 +#: access/transam/xlog.c:12950 #, c-format msgid "promote trigger file found: %s" msgstr "昇格トリガファイルがあります: %s" -#: access/transam/xlog.c:12955 +#: access/transam/xlog.c:12959 #, c-format msgid "could not stat promote trigger file \"%s\": %m" msgstr "昇格トリガファイル\"%s\"のstatに失敗しました: %m" @@ -3138,10 +3153,10 @@ msgstr "ラージオブジェクト%uは存在しません" #: catalog/aclchk.c:910 catalog/aclchk.c:919 commands/collationcmds.c:118 commands/copy.c:1137 commands/copy.c:1157 commands/copy.c:1166 commands/copy.c:1175 commands/copy.c:1184 commands/copy.c:1193 commands/copy.c:1202 commands/copy.c:1211 commands/copy.c:1229 commands/copy.c:1245 commands/copy.c:1265 commands/copy.c:1282 commands/dbcommands.c:158 commands/dbcommands.c:167 commands/dbcommands.c:176 commands/dbcommands.c:185 commands/dbcommands.c:194 -#: commands/dbcommands.c:203 commands/dbcommands.c:212 commands/dbcommands.c:221 commands/dbcommands.c:230 commands/dbcommands.c:239 commands/dbcommands.c:261 commands/dbcommands.c:1503 commands/dbcommands.c:1512 commands/dbcommands.c:1521 commands/dbcommands.c:1530 commands/extension.c:1735 commands/extension.c:1745 commands/extension.c:1755 commands/extension.c:3055 commands/foreigncmds.c:539 commands/foreigncmds.c:548 commands/functioncmds.c:572 +#: commands/dbcommands.c:203 commands/dbcommands.c:212 commands/dbcommands.c:221 commands/dbcommands.c:230 commands/dbcommands.c:239 commands/dbcommands.c:261 commands/dbcommands.c:1529 commands/dbcommands.c:1538 commands/dbcommands.c:1547 commands/dbcommands.c:1556 commands/extension.c:1735 commands/extension.c:1745 commands/extension.c:1755 commands/extension.c:3052 commands/foreigncmds.c:539 commands/foreigncmds.c:548 commands/functioncmds.c:572 #: commands/functioncmds.c:738 commands/functioncmds.c:747 commands/functioncmds.c:756 commands/functioncmds.c:765 commands/functioncmds.c:2017 commands/functioncmds.c:2025 commands/publicationcmds.c:87 commands/publicationcmds.c:130 commands/sequence.c:1275 commands/sequence.c:1285 commands/sequence.c:1295 commands/sequence.c:1305 commands/sequence.c:1315 commands/sequence.c:1325 commands/sequence.c:1335 commands/sequence.c:1345 commands/sequence.c:1355 #: commands/subscriptioncmds.c:105 commands/subscriptioncmds.c:115 commands/subscriptioncmds.c:125 commands/subscriptioncmds.c:135 commands/subscriptioncmds.c:151 commands/subscriptioncmds.c:162 commands/subscriptioncmds.c:176 commands/tablecmds.c:7287 commands/typecmds.c:322 commands/typecmds.c:1357 commands/typecmds.c:1366 commands/typecmds.c:1374 commands/typecmds.c:1382 commands/typecmds.c:1390 commands/user.c:133 commands/user.c:147 commands/user.c:156 -#: commands/user.c:165 commands/user.c:174 commands/user.c:183 commands/user.c:192 commands/user.c:201 commands/user.c:210 commands/user.c:219 commands/user.c:228 commands/user.c:237 commands/user.c:246 commands/user.c:582 commands/user.c:590 commands/user.c:598 commands/user.c:606 commands/user.c:614 commands/user.c:622 commands/user.c:630 commands/user.c:638 commands/user.c:647 commands/user.c:655 commands/user.c:663 parser/parse_utilcmd.c:416 +#: commands/user.c:165 commands/user.c:174 commands/user.c:183 commands/user.c:192 commands/user.c:201 commands/user.c:210 commands/user.c:219 commands/user.c:228 commands/user.c:237 commands/user.c:246 commands/user.c:582 commands/user.c:590 commands/user.c:598 commands/user.c:606 commands/user.c:614 commands/user.c:622 commands/user.c:630 commands/user.c:638 commands/user.c:647 commands/user.c:655 commands/user.c:663 parser/parse_utilcmd.c:414 #: replication/pgoutput/pgoutput.c:142 replication/pgoutput/pgoutput.c:163 replication/walsender.c:891 replication/walsender.c:902 replication/walsender.c:912 #, c-format msgid "conflicting or redundant options" @@ -3158,7 +3173,7 @@ msgstr "GRANT/REVOKE ON SCHEMAS を使っている時には IN SCHEMA 句は指定できません" #: catalog/aclchk.c:1561 catalog/catalog.c:506 catalog/objectaddress.c:1427 commands/analyze.c:389 commands/copy.c:5091 commands/sequence.c:1710 commands/tablecmds.c:6750 commands/tablecmds.c:6906 commands/tablecmds.c:6956 commands/tablecmds.c:7030 commands/tablecmds.c:7100 commands/tablecmds.c:7212 commands/tablecmds.c:7306 commands/tablecmds.c:7365 commands/tablecmds.c:7454 commands/tablecmds.c:7483 commands/tablecmds.c:7638 commands/tablecmds.c:7720 -#: commands/tablecmds.c:7813 commands/tablecmds.c:7968 commands/tablecmds.c:11330 commands/tablecmds.c:11511 commands/tablecmds.c:11671 commands/tablecmds.c:12755 commands/trigger.c:884 parser/analyze.c:2331 parser/parse_relation.c:713 parser/parse_target.c:1035 parser/parse_type.c:144 parser/parse_utilcmd.c:3337 parser/parse_utilcmd.c:3373 parser/parse_utilcmd.c:3415 utils/adt/acl.c:2869 utils/adt/ruleutils.c:2543 +#: commands/tablecmds.c:7813 commands/tablecmds.c:7968 commands/tablecmds.c:11330 commands/tablecmds.c:11511 commands/tablecmds.c:11671 commands/tablecmds.c:12755 commands/trigger.c:884 parser/analyze.c:2331 parser/parse_relation.c:713 parser/parse_target.c:1035 parser/parse_type.c:144 parser/parse_utilcmd.c:3335 parser/parse_utilcmd.c:3371 parser/parse_utilcmd.c:3413 utils/adt/acl.c:2869 utils/adt/ruleutils.c:2543 #, c-format msgid "column \"%s\" of relation \"%s\" does not exist" msgstr "リレーション\"%2$s\"の列\"%1$s\"は存在しません" @@ -3648,7 +3663,7 @@ msgid "publication with OID %u does not exist" msgstr "OID %uのパブリケーションは存在しません" -#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1116 +#: catalog/aclchk.c:5300 commands/subscriptioncmds.c:1117 #, c-format msgid "subscription with OID %u does not exist" msgstr "OID %uのサブスクリプションは存在しません" @@ -3668,7 +3683,7 @@ msgid "pg_nextoid() can only be used on system catalogs" msgstr "pg_nextoid() はシステムカタログでのみ使用できます" -#: catalog/catalog.c:498 parser/parse_utilcmd.c:2238 +#: catalog/catalog.c:498 parser/parse_utilcmd.c:2236 #, c-format msgid "index \"%s\" does not belong to table \"%s\"" msgstr "インデックス\"%s\"はテーブル\"%s\"には属していません" @@ -3733,7 +3748,7 @@ msgid "cannot drop %s because other objects depend on it" msgstr "他のオブジェクトが依存しているため%sを削除できません" -#: catalog/dependency.c:1203 catalog/dependency.c:1210 catalog/dependency.c:1222 commands/tablecmds.c:1259 commands/tablecmds.c:13374 commands/tablespace.c:464 commands/user.c:1095 commands/view.c:509 libpq/auth.c:334 replication/syncrep.c:1032 storage/lmgr/deadlock.c:1154 storage/lmgr/proc.c:1354 utils/misc/guc.c:6783 utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11004 utils/misc/guc.c:11038 utils/misc/guc.c:11072 utils/misc/guc.c:11115 +#: catalog/dependency.c:1203 catalog/dependency.c:1210 catalog/dependency.c:1222 commands/tablecmds.c:1259 commands/tablecmds.c:13374 commands/tablespace.c:464 commands/user.c:1095 commands/view.c:509 libpq/auth.c:334 replication/syncrep.c:1032 storage/lmgr/deadlock.c:1153 storage/lmgr/proc.c:1356 utils/misc/guc.c:6783 utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11004 utils/misc/guc.c:11038 utils/misc/guc.c:11072 utils/misc/guc.c:11115 #: utils/misc/guc.c:11157 #, c-format msgid "%s" @@ -3814,7 +3829,7 @@ msgid "no collation was derived for column \"%s\" with collatable type %s" msgstr "照合可能な型 %2$s を持つ列\"%1$s\"のための照合順序を決定できませんでした" -#: catalog/heap.c:1162 catalog/index.c:866 commands/tablecmds.c:3573 +#: catalog/heap.c:1162 catalog/index.c:867 commands/tablecmds.c:3573 #, c-format msgid "relation \"%s\" already exists" msgstr "リレーション\"%s\"はすでに存在します" @@ -3844,7 +3859,7 @@ msgid "check constraint \"%s\" already exists" msgstr "検査制約\"%s\"はすでに存在します" -#: catalog/heap.c:2855 catalog/index.c:880 catalog/pg_constraint.c:668 commands/tablecmds.c:8318 +#: catalog/heap.c:2855 catalog/index.c:881 catalog/pg_constraint.c:668 commands/tablecmds.c:8318 #, c-format msgid "constraint \"%s\" for relation \"%s\" already exists" msgstr "すでに制約\"%s\"はリレーション\"%s\"に存在します" @@ -3894,12 +3909,12 @@ msgid "generation expression is not immutable" msgstr "生成式は不変ではありません" -#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1236 +#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1238 #, c-format msgid "column \"%s\" is of type %s but default expression is of type %s" msgstr "列\"%s\"の型は%sですが、デフォルト式の型は%sです" -#: catalog/heap.c:3088 commands/prepare.c:371 parser/parse_node.c:412 parser/parse_target.c:588 parser/parse_target.c:868 parser/parse_target.c:878 rewrite/rewriteHandler.c:1241 +#: catalog/heap.c:3088 commands/prepare.c:371 parser/parse_node.c:412 parser/parse_target.c:588 parser/parse_target.c:868 parser/parse_target.c:878 rewrite/rewriteHandler.c:1243 #, c-format msgid "You will need to rewrite or cast the expression." msgstr "式を書き換えるかキャストする必要があります。" @@ -3934,99 +3949,99 @@ msgid "Truncate table \"%s\" at the same time, or use TRUNCATE ... CASCADE." msgstr "同時にテーブル\"%s\"がtruncateされました。TRUNCATE ... CASCADEを使用してください。" -#: catalog/index.c:220 parser/parse_utilcmd.c:2144 +#: catalog/index.c:221 parser/parse_utilcmd.c:2142 #, c-format msgid "multiple primary keys for table \"%s\" are not allowed" msgstr "テーブル\"%s\"に複数のプライマリキーを持たせることはできません" -#: catalog/index.c:238 +#: catalog/index.c:239 #, c-format msgid "primary keys cannot be expressions" msgstr "プライマリキーを式にすることはできません" -#: catalog/index.c:255 +#: catalog/index.c:256 #, c-format msgid "primary key column \"%s\" is not marked NOT NULL" msgstr "主キー列\"%s\"がNOT NULL指定されていません" -#: catalog/index.c:765 catalog/index.c:1930 +#: catalog/index.c:766 catalog/index.c:1931 #, c-format msgid "user-defined indexes on system catalog tables are not supported" msgstr "ユーザによるシステムカタログテーブルに対するインデックスの定義はサポートされていません" -#: catalog/index.c:805 +#: catalog/index.c:806 #, c-format msgid "nondeterministic collations are not supported for operator class \"%s\"" msgstr "非決定的照合順序は演算子クラス \"%s\" ではサポートされません" -#: catalog/index.c:820 +#: catalog/index.c:821 #, c-format msgid "concurrent index creation on system catalog tables is not supported" msgstr "システムカタログテーブルの並行的インデックス作成はサポートされていません" -#: catalog/index.c:829 catalog/index.c:1282 +#: catalog/index.c:830 catalog/index.c:1283 #, c-format msgid "concurrent index creation for exclusion constraints is not supported" msgstr "排他制約のためのインデックスの並列的作成はサポートされていません" -#: catalog/index.c:838 +#: catalog/index.c:839 #, c-format msgid "shared indexes cannot be created after initdb" msgstr "initdbの後に共有インデックスを作成できません" -#: catalog/index.c:858 commands/createas.c:264 commands/sequence.c:162 parser/parse_utilcmd.c:221 +#: catalog/index.c:859 commands/createas.c:264 commands/sequence.c:162 parser/parse_utilcmd.c:219 #, c-format msgid "relation \"%s\" already exists, skipping" msgstr "リレーション\"%s\"はすでに存在します、スキップします" -#: catalog/index.c:908 +#: catalog/index.c:909 #, c-format msgid "pg_class index OID value not set when in binary upgrade mode" msgstr "バイナリアップグレードモード中にpg_classのインデックスOIDが設定されていません" -#: catalog/index.c:2226 +#: catalog/index.c:2227 #, c-format msgid "DROP INDEX CONCURRENTLY must be first action in transaction" msgstr "DROP INDEX CONCURRENTLYはトランザクション内で最初の操作でなければなりません" -#: catalog/index.c:2957 +#: catalog/index.c:2958 #, c-format msgid "building index \"%s\" on table \"%s\" serially" msgstr "テーブル\"%2$s\"のインデックス\"%1$s\"を非並列で構築しています" -#: catalog/index.c:2962 +#: catalog/index.c:2963 #, c-format msgid "building index \"%s\" on table \"%s\" with request for %d parallel worker" msgid_plural "building index \"%s\" on table \"%s\" with request for %d parallel workers" msgstr[0] "テーブル\"%2$s\"のインデックス\"%1$s\"を%3$d個のパラレルワーカを要求して構築しています" msgstr[1] "テーブル\"%2$s\"のインデックス\"%1$s\"を%3$d個のパラレルワーカを要求して構築しています" -#: catalog/index.c:3595 +#: catalog/index.c:3597 #, c-format msgid "cannot reindex temporary tables of other sessions" msgstr "他のセッションの一時テーブルはインデクス再構築できません" -#: catalog/index.c:3606 commands/indexcmds.c:3134 +#: catalog/index.c:3608 commands/indexcmds.c:3151 #, c-format msgid "cannot reindex invalid index on TOAST table" msgstr "TOASTテーブルの無効なインデックスの再作成はできません" -#: catalog/index.c:3728 +#: catalog/index.c:3730 #, c-format msgid "index \"%s\" was reindexed" msgstr "インデックス\"%s\"のインデックス再構築が完了しました" -#: catalog/index.c:3810 commands/indexcmds.c:3155 +#: catalog/index.c:3812 commands/indexcmds.c:3172 #, c-format msgid "REINDEX of partitioned tables is not yet implemented, skipping \"%s\"" msgstr "パーティションテーブルの REINDEX は実装されていません、\"%s\"はスキップします" -#: catalog/index.c:3865 +#: catalog/index.c:3867 #, c-format msgid "cannot reindex invalid index \"%s.%s\" on TOAST table, skipping" msgstr "TOASTテーブルの無効なインデックス \"%s.%s\"の再作成はできません、スキップします " -#: catalog/namespace.c:258 catalog/namespace.c:462 catalog/namespace.c:554 commands/trigger.c:5122 +#: catalog/namespace.c:258 catalog/namespace.c:462 catalog/namespace.c:554 commands/trigger.c:5153 #, c-format msgid "cross-database references are not implemented: \"%s.%s.%s\"" msgstr "データベース間の参照は実装されていません: \"%s.%s.%s\"" @@ -4121,7 +4136,7 @@ msgid "cannot move objects into or out of TOAST schema" msgstr "TOASTスキーマへ、またはTOASTスキーマからオブジェクトを移動できません" -#: catalog/namespace.c:3053 commands/schemacmds.c:267 commands/schemacmds.c:347 commands/tablecmds.c:1204 +#: catalog/namespace.c:3053 commands/schemacmds.c:285 commands/schemacmds.c:365 commands/tablecmds.c:1204 #, c-format msgid "schema \"%s\" does not exist" msgstr "スキーマ\"%s\"は存在しません" @@ -4131,32 +4146,32 @@ msgid "improper relation name (too many dotted names): %s" msgstr "リレーション名が不適切です(ドット区切りの名前が多すぎます): %s" -#: catalog/namespace.c:3647 +#: catalog/namespace.c:3651 #, c-format msgid "collation \"%s\" for encoding \"%s\" does not exist" msgstr "エンコーディング\"%2$s\"の照合順序\"%1$s\"は存在しません" -#: catalog/namespace.c:3702 +#: catalog/namespace.c:3706 #, c-format msgid "conversion \"%s\" does not exist" msgstr "変換\"%sは存在しません" -#: catalog/namespace.c:3966 +#: catalog/namespace.c:3970 #, c-format msgid "permission denied to create temporary tables in database \"%s\"" msgstr "データベース\"%s\"に一時テーブルを作成する権限がありません" -#: catalog/namespace.c:3982 +#: catalog/namespace.c:3986 #, c-format msgid "cannot create temporary tables during recovery" msgstr "リカバリ中は一時テーブルを作成できません" -#: catalog/namespace.c:3988 +#: catalog/namespace.c:3992 #, c-format msgid "cannot create temporary tables during a parallel operation" msgstr "並行処理中は一時テーブルを作成できません" -#: catalog/namespace.c:4289 commands/tablespace.c:1216 commands/variable.c:64 utils/misc/guc.c:11189 utils/misc/guc.c:11267 +#: catalog/namespace.c:4293 commands/tablespace.c:1216 commands/variable.c:64 utils/misc/guc.c:11189 utils/misc/guc.c:11267 #, c-format msgid "List syntax is invalid." msgstr "リスト文法が無効です" @@ -4789,12 +4804,12 @@ msgid "default conversion for %s to %s already exists" msgstr "%sから%sへのデフォルトの変換はすでに存在します" -#: catalog/pg_depend.c:176 commands/extension.c:3332 +#: catalog/pg_depend.c:176 commands/extension.c:3329 #, c-format msgid "%s is already a member of extension \"%s\"" msgstr "%sはすでに機能拡張\"%s\"のメンバです" -#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3372 +#: catalog/pg_depend.c:183 catalog/pg_depend.c:234 commands/extension.c:3369 #, c-format msgid "%s is not a member of extension \"%s\"" msgstr "%s は機能拡張\"%s\"のメンバではありません" @@ -4849,7 +4864,7 @@ msgid "ALTER TYPE ADD BEFORE/AFTER is incompatible with binary upgrade" msgstr "ALTER TYPE ADD BEFORE/AFTER はバイナリアップグレードでは互換性がありません" -#: catalog/pg_namespace.c:64 commands/schemacmds.c:276 +#: catalog/pg_namespace.c:64 commands/schemacmds.c:294 #, c-format msgid "schema \"%s\" already exists" msgstr "スキーマ\"%s\"はすでに存在します" @@ -5108,7 +5123,7 @@ msgid "cannot reassign ownership of objects owned by %s because they are required by the database system" msgstr "データベースシステムが必要としているため%sが所有するオブジェクトの所有者を再割り当てできません" -#: catalog/pg_subscription.c:171 commands/subscriptioncmds.c:648 commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1084 +#: catalog/pg_subscription.c:171 commands/subscriptioncmds.c:648 commands/subscriptioncmds.c:862 commands/subscriptioncmds.c:1085 #, c-format msgid "subscription \"%s\" does not exist" msgstr "サブスクリプション\"%s\"は存在しません" @@ -5592,12 +5607,12 @@ msgid "no usable system locales were found" msgstr "使用できるシステムロケールが見つかりません" -#: commands/comment.c:61 commands/dbcommands.c:842 commands/dbcommands.c:1038 commands/dbcommands.c:1151 commands/dbcommands.c:1341 commands/dbcommands.c:1589 commands/dbcommands.c:1703 commands/dbcommands.c:2143 utils/init/postinit.c:877 utils/init/postinit.c:982 utils/init/postinit.c:999 +#: commands/comment.c:61 commands/dbcommands.c:853 commands/dbcommands.c:1064 commands/dbcommands.c:1177 commands/dbcommands.c:1367 commands/dbcommands.c:1615 commands/dbcommands.c:1737 commands/dbcommands.c:2177 utils/init/postinit.c:877 utils/init/postinit.c:983 utils/init/postinit.c:1009 #, c-format msgid "database \"%s\" does not exist" msgstr "データベース\"%s\"は存在しません" -#: commands/comment.c:101 commands/seclabel.c:117 parser/parse_utilcmd.c:996 +#: commands/comment.c:101 commands/seclabel.c:117 parser/parse_utilcmd.c:994 #, c-format msgid "\"%s\" is not a table, view, materialized view, composite type, or foreign table" msgstr "\"%s\"はテーブル、ビュー、実体化ビュー、複合型、外部テーブルのいずれでもありません" @@ -5722,7 +5737,7 @@ msgid "argument to option \"%s\" must be a valid encoding name" msgstr "オプション\"%s\"の引数は有効なエンコーディング名でなければなりません" -#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1537 +#: commands/copy.c:1295 commands/dbcommands.c:254 commands/dbcommands.c:1563 #, c-format msgid "option \"%s\" not recognized" msgstr "タイムゾーン\"%s\"を認識できません" @@ -6142,7 +6157,7 @@ msgid "Generated columns cannot be used in COPY." msgstr "生成カラムはCOPYでは使えません。" -#: commands/copy.c:5096 commands/indexcmds.c:1789 commands/statscmds.c:228 commands/tablecmds.c:2205 commands/tablecmds.c:2824 commands/tablecmds.c:3211 parser/parse_relation.c:3557 parser/parse_relation.c:3577 utils/adt/tsvector_op.c:2683 +#: commands/copy.c:5096 commands/indexcmds.c:1806 commands/statscmds.c:228 commands/tablecmds.c:2205 commands/tablecmds.c:2824 commands/tablecmds.c:3211 parser/parse_relation.c:3557 parser/parse_relation.c:3577 utils/adt/tsvector_op.c:2683 #, c-format msgid "column \"%s\" does not exist" msgstr "列\"%s\"は存在しません" @@ -6189,7 +6204,7 @@ msgid "%s is not a valid encoding name" msgstr "%sは有効な符号化方式名ではありません" -#: commands/dbcommands.c:315 commands/dbcommands.c:1570 commands/user.c:275 commands/user.c:691 +#: commands/dbcommands.c:315 commands/dbcommands.c:1596 commands/user.c:275 commands/user.c:691 #, c-format msgid "invalid connection limit: %d" msgstr "不正な接続数制限: %d" @@ -6204,210 +6219,225 @@ msgid "template database \"%s\" does not exist" msgstr "テンプレートデータベース\"%s\"は存在しません" -#: commands/dbcommands.c:369 +#: commands/dbcommands.c:367 +#, c-format +msgid "cannot use invalid database \"%s\" as template" +msgstr "無効なデータベース\"%s\"はテンプレートとして使用できません" + +#: commands/dbcommands.c:368 commands/dbcommands.c:1625 utils/init/postinit.c:992 +#, c-format +msgid "Use DROP DATABASE to drop invalid databases." +msgstr "DROP DATABASEを使用して無効なデータベースを削除してください。" + +#: commands/dbcommands.c:379 #, c-format msgid "permission denied to copy database \"%s\"" msgstr "データベース\"%s\"をコピーする権限がありません" -#: commands/dbcommands.c:385 +#: commands/dbcommands.c:395 #, c-format msgid "invalid server encoding %d" msgstr "サーバの符号化方式%dは不正です" -#: commands/dbcommands.c:391 commands/dbcommands.c:396 +#: commands/dbcommands.c:401 commands/dbcommands.c:406 #, c-format msgid "invalid locale name: \"%s\"" msgstr "ロケール名\"%s\"は不正です" -#: commands/dbcommands.c:416 +#: commands/dbcommands.c:426 #, c-format msgid "new encoding (%s) is incompatible with the encoding of the template database (%s)" msgstr "新しい符号化方式(%s)はテンプレートデータベースの符号化方式(%s)と互換性がありません" -#: commands/dbcommands.c:419 +#: commands/dbcommands.c:429 #, c-format msgid "Use the same encoding as in the template database, or use template0 as template." msgstr "テンプレートデータベースの符号化方式と同じものを使うか、もしくは template0 をテンプレートとして使用してください" -#: commands/dbcommands.c:424 +#: commands/dbcommands.c:434 #, c-format msgid "new collation (%s) is incompatible with the collation of the template database (%s)" msgstr "新しい照合順序(%s)はテンプレートデータベースの照合順序(%s)と互換性がありません" -#: commands/dbcommands.c:426 +#: commands/dbcommands.c:436 #, c-format msgid "Use the same collation as in the template database, or use template0 as template." msgstr "テンプレートデータベースの照合順序と同じものを使うか、もしくは template0 をテンプレートとして使用してください" -#: commands/dbcommands.c:431 +#: commands/dbcommands.c:441 #, c-format msgid "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)" msgstr "新しいLC_CTYPE(%s)はテンプレートデータベース(%s)のLC_CTYPEと互換性がありません" -#: commands/dbcommands.c:433 +#: commands/dbcommands.c:443 #, c-format msgid "Use the same LC_CTYPE as in the template database, or use template0 as template." msgstr "テンプレートデータベースのLC_CTYPEと同じものを使うか、もしくはtemplate0をテンプレートとして使用してください" -#: commands/dbcommands.c:455 commands/dbcommands.c:1197 +#: commands/dbcommands.c:465 commands/dbcommands.c:1223 #, c-format msgid "pg_global cannot be used as default tablespace" msgstr "デフォルトのテーブル空間としてpg_globalを使用できません" -#: commands/dbcommands.c:481 +#: commands/dbcommands.c:491 #, c-format msgid "cannot assign new default tablespace \"%s\"" msgstr "新しいデフォルトのテーブル空間\"%s\"を割り当てられません" -#: commands/dbcommands.c:483 +#: commands/dbcommands.c:493 #, c-format msgid "There is a conflict because database \"%s\" already has some tables in this tablespace." msgstr "データベース\"%s\"のいくつかテーブルはすでにこのテーブル空間にあるため、競合しています。" -#: commands/dbcommands.c:513 commands/dbcommands.c:1067 +#: commands/dbcommands.c:523 commands/dbcommands.c:1093 #, c-format msgid "database \"%s\" already exists" msgstr "データベース\"%s\"はすでに存在します" -#: commands/dbcommands.c:527 +#: commands/dbcommands.c:537 #, c-format msgid "source database \"%s\" is being accessed by other users" msgstr "元となるデータベース\"%s\"は他のユーザによってアクセスされています" -#: commands/dbcommands.c:770 commands/dbcommands.c:785 +#: commands/dbcommands.c:780 commands/dbcommands.c:795 #, c-format msgid "encoding \"%s\" does not match locale \"%s\"" msgstr "符号化方式\"%s\"がロケール\"%s\"に合いません" -#: commands/dbcommands.c:773 +#: commands/dbcommands.c:783 #, c-format msgid "The chosen LC_CTYPE setting requires encoding \"%s\"." msgstr "選択されたLC_CTYPEを設定するには、符号化方式\"%s\"である必要があります。" -#: commands/dbcommands.c:788 +#: commands/dbcommands.c:798 #, c-format msgid "The chosen LC_COLLATE setting requires encoding \"%s\"." msgstr "選択されたLC_COLLATEを設定するには、符号化方式\"%s\"である必要があります。" -#: commands/dbcommands.c:849 +#: commands/dbcommands.c:860 #, c-format msgid "database \"%s\" does not exist, skipping" msgstr "データベース\"%s\"は存在しません、スキップします" -#: commands/dbcommands.c:873 +#: commands/dbcommands.c:884 #, c-format msgid "cannot drop a template database" msgstr "テンプレートデータベースを削除できません" -#: commands/dbcommands.c:879 +#: commands/dbcommands.c:890 #, c-format msgid "cannot drop the currently open database" msgstr "現在オープンしているデータベースを削除できません" -#: commands/dbcommands.c:892 +#: commands/dbcommands.c:903 #, c-format msgid "database \"%s\" is used by an active logical replication slot" msgstr "データベース\"%s\"は有効な論理レプリケーションスロットで使用中です" -#: commands/dbcommands.c:894 +#: commands/dbcommands.c:905 #, c-format msgid "There is %d active slot." msgid_plural "There are %d active slots." msgstr[0] "%d 個のアクティブなスロットがあります。" msgstr[1] "%d 個のアクティブなスロットがあります。" -#: commands/dbcommands.c:908 +#: commands/dbcommands.c:919 #, c-format msgid "database \"%s\" is being used by logical replication subscription" msgstr "データベース\"%s\"は論理レプリケーションのサブスクリプションで使用中です" -#: commands/dbcommands.c:910 +#: commands/dbcommands.c:921 #, c-format msgid "There is %d subscription." msgid_plural "There are %d subscriptions." msgstr[0] "%d個のサブスクリプションがあります" msgstr[1] "%d個のサブスクリプションがあります" -#: commands/dbcommands.c:931 commands/dbcommands.c:1089 commands/dbcommands.c:1219 +#: commands/dbcommands.c:942 commands/dbcommands.c:1115 commands/dbcommands.c:1245 #, c-format msgid "database \"%s\" is being accessed by other users" msgstr "データベース\"%s\"は他のユーザからアクセスされています" -#: commands/dbcommands.c:1049 +#: commands/dbcommands.c:1075 #, c-format msgid "permission denied to rename database" msgstr "データベースの名前を変更する権限がありません" -#: commands/dbcommands.c:1078 +#: commands/dbcommands.c:1104 #, c-format msgid "current database cannot be renamed" msgstr "現在のデータベースの名前を変更できません" -#: commands/dbcommands.c:1175 +#: commands/dbcommands.c:1201 #, c-format msgid "cannot change the tablespace of the currently open database" msgstr "現在オープン中のデータベースのテーブルスペースは変更できません" -#: commands/dbcommands.c:1278 +#: commands/dbcommands.c:1304 #, c-format msgid "some relations of database \"%s\" are already in tablespace \"%s\"" msgstr "データベース\"%s\"のリレーションの中に、テーブルスペース\"%s\"にすでに存在するものがあります" -#: commands/dbcommands.c:1280 +#: commands/dbcommands.c:1306 #, c-format msgid "You must move them back to the database's default tablespace before using this command." msgstr "このコマンドを使う前に、データベースのデフォルトのテーブルスペースに戻す必要があります。" -#: commands/dbcommands.c:1405 commands/dbcommands.c:1981 commands/dbcommands.c:2244 commands/dbcommands.c:2330 +#: commands/dbcommands.c:1431 commands/dbcommands.c:2015 commands/dbcommands.c:2314 commands/dbcommands.c:2400 #, c-format msgid "some useless files may be left behind in old database directory \"%s\"" msgstr "元のデータベースのディレクトリ\"%s\"に不要なファイルが残っているかもしれません" -#: commands/dbcommands.c:1461 +#: commands/dbcommands.c:1487 #, c-format msgid "unrecognized DROP DATABASE option \"%s\"" msgstr "DROP DATABASEのオプション\"%s\"が認識できません" -#: commands/dbcommands.c:1551 +#: commands/dbcommands.c:1577 #, c-format msgid "option \"%s\" cannot be specified with other options" msgstr "オプション\"%s\"は他のオプションと一緒に指定はできません" -#: commands/dbcommands.c:1607 +#: commands/dbcommands.c:1624 +#, c-format +msgid "cannot alter invalid database \"%s\"" +msgstr "無効なデータベース\"%s\"は変更できません" + +#: commands/dbcommands.c:1641 #, c-format msgid "cannot disallow connections for current database" msgstr "現在のデータベースへの接続は禁止できません" -#: commands/dbcommands.c:1743 +#: commands/dbcommands.c:1777 #, c-format msgid "permission denied to change owner of database" msgstr "データベースの所有者を変更する権限がありません" -#: commands/dbcommands.c:2087 +#: commands/dbcommands.c:2121 #, c-format msgid "There are %d other session(s) and %d prepared transaction(s) using the database." msgstr "他にこのデータベースを使っている %d 個のセッションと %d 個の準備済みトランザクションがあります。" -#: commands/dbcommands.c:2090 +#: commands/dbcommands.c:2124 #, c-format msgid "There is %d other session using the database." msgid_plural "There are %d other sessions using the database." msgstr[0] "他にこのデータベースを使っている %d 個のセッションがあります。" msgstr[1] "他にこのデータベースを使っている %d 個のセッションがあります。" -#: commands/dbcommands.c:2095 storage/ipc/procarray.c:3128 +#: commands/dbcommands.c:2129 storage/ipc/procarray.c:3129 #, c-format msgid "There is %d prepared transaction using the database." msgid_plural "There are %d prepared transactions using the database." msgstr[0] "このデータベースを使用する準備されたトランザクションが%d存在します。" msgstr[1] "このデータベースを使用する準備されたトランザクションが%d存在します。" -#: commands/dbcommands.c:2201 +#: commands/dbcommands.c:2271 #, c-format msgid "missing directory \"%s\"" msgstr "ディレクトリ\"%s\"がありません" -#: commands/dbcommands.c:2260 commands/tablespace.c:188 commands/tablespace.c:634 +#: commands/dbcommands.c:2330 commands/tablespace.c:188 commands/tablespace.c:634 #, c-format msgid "could not stat directory \"%s\": %m" msgstr "ディレクトリ\"%s\"のstatができませんでした: %m" @@ -6688,7 +6718,7 @@ msgid "EXPLAIN option TIMING requires ANALYZE" msgstr "EXPLAINオプションのTIMINGにはANALYZE指定が必要です" -#: commands/extension.c:173 commands/extension.c:3013 +#: commands/extension.c:173 commands/extension.c:3010 #, c-format msgid "extension \"%s\" does not exist" msgstr "機能拡張\"%s\"は存在しません" @@ -6818,7 +6848,7 @@ msgid "extension \"%s\" has no update path from version \"%s\" to version \"%s\"" msgstr "機能拡張\"%s\"について、バージョン\"%s\"からバージョン\"%s\"へのアップデートパスがありません" -#: commands/extension.c:1408 commands/extension.c:3074 +#: commands/extension.c:1408 commands/extension.c:3071 #, c-format msgid "version to install must be specified" msgstr "インストールするバージョンを指定してください" @@ -6893,32 +6923,32 @@ msgid "cannot move extension \"%s\" into schema \"%s\" because the extension contains the schema" msgstr "機能拡張がそのスキーマを含んでいるため、機能拡張\"%s\"をスキーマ\"%s\"に移動できません" -#: commands/extension.c:2869 commands/extension.c:2932 +#: commands/extension.c:2869 commands/extension.c:2929 #, c-format msgid "extension \"%s\" does not support SET SCHEMA" msgstr "機能拡張\"%s\"は SET SCHEMA をサポートしていません" -#: commands/extension.c:2934 +#: commands/extension.c:2931 #, c-format msgid "%s is not in the extension's schema \"%s\"" msgstr "機能拡張のスキーマ\"%2$s\"に%1$sが見つかりません" -#: commands/extension.c:2993 +#: commands/extension.c:2990 #, c-format msgid "nested ALTER EXTENSION is not supported" msgstr "入れ子になった ALTER EXTENSION はサポートされていません" -#: commands/extension.c:3085 +#: commands/extension.c:3082 #, c-format msgid "version \"%s\" of extension \"%s\" is already installed" msgstr "機能拡張 \"%2$s\"のバージョン\"%1$s\"はすでにインストールされています" -#: commands/extension.c:3344 +#: commands/extension.c:3341 #, c-format msgid "cannot add schema \"%s\" to extension \"%s\" because the schema contains the extension" msgstr "スキーマ\"%s\"を拡張\"%s\"に追加できません。そのスキーマにその拡張が含まれているためです" -#: commands/extension.c:3438 +#: commands/extension.c:3435 #, c-format msgid "file \"%s\" is too large" msgstr "ファイル\"%s\"は大きすぎます" @@ -7475,162 +7505,162 @@ msgid "Table \"%s\" contains partitions that are foreign tables." msgstr "テーブル\"%s\"は外部テーブルを子テーブルとして含んでいます" -#: commands/indexcmds.c:1706 +#: commands/indexcmds.c:1723 #, c-format msgid "functions in index predicate must be marked IMMUTABLE" msgstr "インデックスの述部の関数はIMMUTABLEマークが必要です" -#: commands/indexcmds.c:1784 parser/parse_utilcmd.c:2487 parser/parse_utilcmd.c:2622 +#: commands/indexcmds.c:1801 parser/parse_utilcmd.c:2485 parser/parse_utilcmd.c:2620 #, c-format msgid "column \"%s\" named in key does not exist" msgstr "キーとして指名された列\"%s\"は存在しません" -#: commands/indexcmds.c:1808 parser/parse_utilcmd.c:1823 +#: commands/indexcmds.c:1825 parser/parse_utilcmd.c:1821 #, c-format msgid "expressions are not supported in included columns" msgstr "包含列では式はサポートされません" -#: commands/indexcmds.c:1849 +#: commands/indexcmds.c:1866 #, c-format msgid "functions in index expression must be marked IMMUTABLE" msgstr "式インデックスの関数はIMMUTABLEマークが必要です" -#: commands/indexcmds.c:1864 +#: commands/indexcmds.c:1881 #, c-format msgid "including column does not support a collation" msgstr "包含列は照合順序をサポートしません" -#: commands/indexcmds.c:1868 +#: commands/indexcmds.c:1885 #, c-format msgid "including column does not support an operator class" msgstr "包含列は演算子クラスをサポートしません" -#: commands/indexcmds.c:1872 +#: commands/indexcmds.c:1889 #, c-format msgid "including column does not support ASC/DESC options" msgstr "包含列は ASC/DESC オプションをサポートしません" -#: commands/indexcmds.c:1876 +#: commands/indexcmds.c:1893 #, c-format msgid "including column does not support NULLS FIRST/LAST options" msgstr "包含列は NULLS FIRST/LAST オプションをサポートしません" -#: commands/indexcmds.c:1917 +#: commands/indexcmds.c:1934 #, c-format msgid "could not determine which collation to use for index expression" msgstr "インデックス式で使用する照合順序を特定できませんでした" -#: commands/indexcmds.c:1925 commands/tablecmds.c:16451 commands/typecmds.c:771 parser/parse_expr.c:2863 parser/parse_type.c:566 parser/parse_utilcmd.c:3698 parser/parse_utilcmd.c:4259 utils/adt/misc.c:532 +#: commands/indexcmds.c:1942 commands/tablecmds.c:16451 commands/typecmds.c:771 parser/parse_expr.c:2863 parser/parse_type.c:566 parser/parse_utilcmd.c:3696 parser/parse_utilcmd.c:4259 utils/adt/misc.c:532 #, c-format msgid "collations are not supported by type %s" msgstr "%s 型では照合順序はサポートされません" -#: commands/indexcmds.c:1990 +#: commands/indexcmds.c:2007 #, c-format msgid "operator %s is not commutative" msgstr "演算子 %s は可換ではありません" -#: commands/indexcmds.c:1992 +#: commands/indexcmds.c:2009 #, c-format msgid "Only commutative operators can be used in exclusion constraints." msgstr "排除制約で使えるのは可換演算子だけです" -#: commands/indexcmds.c:2018 +#: commands/indexcmds.c:2035 #, c-format msgid "operator %s is not a member of operator family \"%s\"" msgstr "演算子%sは演算子族\"%s\"のメンバーではありません" -#: commands/indexcmds.c:2021 +#: commands/indexcmds.c:2038 #, c-format msgid "The exclusion operator must be related to the index operator class for the constraint." msgstr "この排除に使用する演算子はこの制約に使用するインデックス演算子に関連付けられている必要があります。" -#: commands/indexcmds.c:2056 +#: commands/indexcmds.c:2073 #, c-format msgid "access method \"%s\" does not support ASC/DESC options" msgstr "アクセスメソッド\"%s\"はASC/DESCオプションをサポートしません" -#: commands/indexcmds.c:2061 +#: commands/indexcmds.c:2078 #, c-format msgid "access method \"%s\" does not support NULLS FIRST/LAST options" msgstr "アクセスメソッド\"%s\"はNULLS FIRST/LASTオプションをサポートしません" -#: commands/indexcmds.c:2107 commands/tablecmds.c:16476 commands/tablecmds.c:16482 commands/typecmds.c:1947 +#: commands/indexcmds.c:2124 commands/tablecmds.c:16476 commands/tablecmds.c:16482 commands/typecmds.c:1947 #, c-format msgid "data type %s has no default operator class for access method \"%s\"" msgstr "アクセスメソッド\"%2$s\"にはデータ型%1$s用のデフォルトの演算子クラスがありません" -#: commands/indexcmds.c:2109 +#: commands/indexcmds.c:2126 #, c-format msgid "You must specify an operator class for the index or define a default operator class for the data type." msgstr "このインデックスの演算子クラスを指定するか、あるいはこのデータ型のデフォルト演算子クラスを定義しなければなりません。" -#: commands/indexcmds.c:2138 commands/indexcmds.c:2146 commands/opclasscmds.c:208 +#: commands/indexcmds.c:2155 commands/indexcmds.c:2163 commands/opclasscmds.c:208 #, c-format msgid "operator class \"%s\" does not exist for access method \"%s\"" msgstr "アクセスメソッド\"%2$s\"用の演算子クラス\"%1$s\"は存在しません" -#: commands/indexcmds.c:2160 commands/typecmds.c:1935 +#: commands/indexcmds.c:2177 commands/typecmds.c:1935 #, c-format msgid "operator class \"%s\" does not accept data type %s" msgstr "演算子クラス\"%s\"はデータ型%sを受け付けません" -#: commands/indexcmds.c:2250 +#: commands/indexcmds.c:2267 #, c-format msgid "there are multiple default operator classes for data type %s" msgstr "データ型%sには複数のデフォルトの演算子クラスがあります" -#: commands/indexcmds.c:2699 +#: commands/indexcmds.c:2716 #, c-format msgid "table \"%s\" has no indexes that can be reindexed concurrently" msgstr "テーブル\"%s\"には並行インデックス再作成が可能なインデックスがありません" -#: commands/indexcmds.c:2710 +#: commands/indexcmds.c:2727 #, c-format msgid "table \"%s\" has no indexes to reindex" msgstr "テーブル\"%s\"には再構築すべきインデックスはありません" -#: commands/indexcmds.c:2749 commands/indexcmds.c:3030 commands/indexcmds.c:3123 +#: commands/indexcmds.c:2766 commands/indexcmds.c:3047 commands/indexcmds.c:3140 #, c-format msgid "cannot reindex system catalogs concurrently" msgstr "システムカタログではインデックスの並行再構築はできません" -#: commands/indexcmds.c:2772 +#: commands/indexcmds.c:2789 #, c-format msgid "can only reindex the currently open database" msgstr "現在オープンしているデータベースのみをインデックス再構築することができます" -#: commands/indexcmds.c:2863 +#: commands/indexcmds.c:2880 #, c-format msgid "cannot reindex system catalogs concurrently, skipping all" msgstr "システムカタログではインデックスの並行再構築はできません、全てスキップします" -#: commands/indexcmds.c:2915 commands/indexcmds.c:3655 +#: commands/indexcmds.c:2932 commands/indexcmds.c:3672 #, c-format msgid "table \"%s.%s\" was reindexed" msgstr "テーブル\"%s.%s\"のインデックス再構築が完了しました" -#: commands/indexcmds.c:3045 commands/indexcmds.c:3091 +#: commands/indexcmds.c:3062 commands/indexcmds.c:3108 #, c-format msgid "cannot reindex invalid index \"%s.%s\" concurrently, skipping" msgstr "無効なインデックス \"%s.%s\"の並行再構築はできません、スキップします " -#: commands/indexcmds.c:3051 +#: commands/indexcmds.c:3068 #, c-format msgid "cannot reindex exclusion constraint index \"%s.%s\" concurrently, skipping" msgstr "排他制約インデックス\"%s.%s\"を並行再構築することはできません、スキップします " -#: commands/indexcmds.c:3162 +#: commands/indexcmds.c:3179 #, c-format msgid "cannot reindex this type of relation concurrently" msgstr "このタイプのリレーションでインデックス並列再構築はできません" -#: commands/indexcmds.c:3637 commands/indexcmds.c:3648 +#: commands/indexcmds.c:3654 commands/indexcmds.c:3665 #, c-format msgid "index \"%s.%s\" was reindexed" msgstr " インデックス\"%s.%s\"の再構築が完了しました " -#: commands/indexcmds.c:3680 +#: commands/indexcmds.c:3697 #, c-format msgid "REINDEX is not yet implemented for partitioned indexes" msgstr "パーティションインデックスに対する REINDEX は実装されていません" @@ -8090,17 +8120,17 @@ msgid "The owner of a FOR ALL TABLES publication must be a superuser." msgstr "FOR ALL TABLES設定のパブリケーションの所有者はスーパユーザである必要があります" -#: commands/schemacmds.c:105 commands/schemacmds.c:292 +#: commands/schemacmds.c:108 commands/schemacmds.c:310 #, c-format msgid "unacceptable schema name \"%s\"" msgstr "スキーマ名\"%s\"は受け付けられません" -#: commands/schemacmds.c:106 commands/schemacmds.c:293 +#: commands/schemacmds.c:109 commands/schemacmds.c:311 #, c-format msgid "The prefix \"pg_\" is reserved for system schemas." msgstr "接頭辞\"pg_\"はシステムスキーマ用に予約されています" -#: commands/schemacmds.c:130 +#: commands/schemacmds.c:133 #, c-format msgid "schema \"%s\" already exists, skipping" msgstr "スキーマ\"%s\"はすでに存在します、スキップします" @@ -8404,7 +8434,7 @@ msgid "could not connect to publisher when attempting to drop the replication slot \"%s\"" msgstr "レプリケーションスロット\"%s\"を削除するための発行者サーバへの接続に失敗しました" -#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1008 replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 +#: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1009 replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 #, c-format msgid "The error was: %s" msgstr "発生したエラー: %s" @@ -8412,30 +8442,30 @@ #. translator: %s is an SQL ALTER command #: commands/subscriptioncmds.c:995 #, c-format -msgid "Use %s to disassociate the subscription from the slot." -msgstr "サブスクリプションのスロットへの関連付けを解除するには %s を実行してください。" +msgid "Use %s to disable the subscription, and then use %s to disassociate it from the slot." +msgstr "%s でサブスクリプションを無効化してから、%s でスロットとの関連付けを解除してください。" -#: commands/subscriptioncmds.c:1006 +#: commands/subscriptioncmds.c:1007 #, c-format msgid "could not drop the replication slot \"%s\" on publisher" msgstr "発行サーバ上のレプリケーションスロット\"%s\"の削除に失敗しました" -#: commands/subscriptioncmds.c:1011 +#: commands/subscriptioncmds.c:1012 #, c-format msgid "dropped replication slot \"%s\" on publisher" msgstr "発行サーバ上のレプリケーションスロット\"%s\"を削除しました" -#: commands/subscriptioncmds.c:1048 +#: commands/subscriptioncmds.c:1049 #, c-format msgid "permission denied to change owner of subscription \"%s\"" msgstr "サブスクリプション\"%s\"の所有者を変更する権限がありません" -#: commands/subscriptioncmds.c:1050 +#: commands/subscriptioncmds.c:1051 #, c-format msgid "The owner of a subscription must be a superuser." msgstr "サブスクリプションの所有者はスーパユーザでなければなりません。" -#: commands/subscriptioncmds.c:1165 +#: commands/subscriptioncmds.c:1166 #, c-format msgid "could not receive list of replicated tables from the publisher: %s" msgstr "発行テーブルの一覧を発行サーバから受け取れませんでした: %s" @@ -8496,7 +8526,7 @@ msgid "Use DROP MATERIALIZED VIEW to remove a materialized view." msgstr "実体化ビューを削除するにはDROP MATERIALIZED VIEWを使用してください。" -#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17685 parser/parse_utilcmd.c:2219 +#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17689 parser/parse_utilcmd.c:2217 #, c-format msgid "index \"%s\" does not exist" msgstr "インデックス\"%s\"は存在しません" @@ -8618,7 +8648,7 @@ msgid "cannot inherit from partition \"%s\"" msgstr "パーティション子テーブル\"%s\"からの継承はできません" -#: commands/tablecmds.c:2301 parser/parse_utilcmd.c:2449 parser/parse_utilcmd.c:2591 +#: commands/tablecmds.c:2301 parser/parse_utilcmd.c:2447 parser/parse_utilcmd.c:2589 #, c-format msgid "inherited relation \"%s\" is not a table or foreign table" msgstr "継承しようとしたリレーション\"%s\"はテーブルまたは外部テーブルではありません" @@ -8673,17 +8703,17 @@ msgid "inherited column \"%s\" has a generation conflict" msgstr "継承された列 \"%s\"の生成が競合しています" -#: commands/tablecmds.c:2519 commands/tablecmds.c:2574 commands/tablecmds.c:11545 parser/parse_utilcmd.c:1299 parser/parse_utilcmd.c:1342 parser/parse_utilcmd.c:1750 parser/parse_utilcmd.c:1859 +#: commands/tablecmds.c:2519 commands/tablecmds.c:2574 commands/tablecmds.c:11545 parser/parse_utilcmd.c:1297 parser/parse_utilcmd.c:1340 parser/parse_utilcmd.c:1748 parser/parse_utilcmd.c:1857 #, c-format msgid "cannot convert whole-row table reference" msgstr "行全体テーブル参照を変換できません" -#: commands/tablecmds.c:2520 parser/parse_utilcmd.c:1300 +#: commands/tablecmds.c:2520 parser/parse_utilcmd.c:1298 #, c-format msgid "Generation expression for column \"%s\" contains a whole-row reference to table \"%s\"." msgstr "制約\"%s\"はテーブル\"%s\"への行全体参照を含みます。" -#: commands/tablecmds.c:2575 parser/parse_utilcmd.c:1343 +#: commands/tablecmds.c:2575 parser/parse_utilcmd.c:1341 #, c-format msgid "Constraint \"%s\" contains a whole-row reference to table \"%s\"." msgstr "制約\"%s\"はテーブル\"%s\"への行全体参照を含みます。" @@ -9230,7 +9260,7 @@ msgid "Key columns \"%s\" and \"%s\" are of incompatible types: %s and %s." msgstr "キーとなる列\"%s\"と\"%s\"との間で型に互換性がありません:%sと%s" -#: commands/tablecmds.c:9190 commands/tablecmds.c:9603 parser/parse_utilcmd.c:803 parser/parse_utilcmd.c:932 +#: commands/tablecmds.c:9190 commands/tablecmds.c:9603 parser/parse_utilcmd.c:801 parser/parse_utilcmd.c:930 #, c-format msgid "foreign key constraints are not supported on foreign tables" msgstr "外部テーブルでは外部キー制約はサポートされていません" @@ -9716,7 +9746,7 @@ msgid "cannot use generated column in partition key" msgstr "パーティションキーで生成カラムは使用できません" -#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 rewrite/rewriteHandler.c:873 rewrite/rewriteHandler.c:890 +#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 #, c-format msgid "Column \"%s\" is a generated column." msgstr "列\"%s\"は生成カラムです。" @@ -9831,32 +9861,32 @@ msgid "Table \"%s\" contains unique indexes." msgstr "テーブル\"%s\"はユニークインデックスを持っています。" -#: commands/tablecmds.c:17719 commands/tablecmds.c:17739 commands/tablecmds.c:17759 commands/tablecmds.c:17778 commands/tablecmds.c:17820 +#: commands/tablecmds.c:17723 commands/tablecmds.c:17743 commands/tablecmds.c:17763 commands/tablecmds.c:17782 commands/tablecmds.c:17824 #, c-format msgid "cannot attach index \"%s\" as a partition of index \"%s\"" msgstr "インデックス\"%s\"をインデックス\"%s\"の子インデックスとしてアタッチすることはできません" -#: commands/tablecmds.c:17722 +#: commands/tablecmds.c:17726 #, c-format msgid "Index \"%s\" is already attached to another index." msgstr "インデックス\"%s\"はすでに別のインデックスにアタッチされています。" -#: commands/tablecmds.c:17742 +#: commands/tablecmds.c:17746 #, c-format msgid "Index \"%s\" is not an index on any partition of table \"%s\"." msgstr "インデックス\"%s\"はテーブル\"%s\"のどの子テーブルのインデックスでもありません。" -#: commands/tablecmds.c:17762 +#: commands/tablecmds.c:17766 #, c-format msgid "The index definitions do not match." msgstr "インデックス定義が合致しません。" -#: commands/tablecmds.c:17781 +#: commands/tablecmds.c:17785 #, c-format msgid "The index \"%s\" belongs to a constraint in table \"%s\" but no constraint exists for index \"%s\"." msgstr "インデックス\"%s\"はテーブル\"%s\"の制約に属していますが、インデックス\"%s\"には制約がありません。" -#: commands/tablecmds.c:17823 +#: commands/tablecmds.c:17827 #, c-format msgid "Another index is already attached for partition \"%s\"." msgstr "子テーブル\"%s\"にはすでに他のインデックスがアタッチされています。" @@ -10216,17 +10246,17 @@ msgid "could not serialize access due to concurrent delete" msgstr "削除が同時に行われたためアクセスの直列化ができませんでした" -#: commands/trigger.c:4124 +#: commands/trigger.c:4155 #, c-format msgid "cannot fire deferred trigger within security-restricted operation" msgstr "セキュリティー制限操作中は、遅延トリガーは発火させられません" -#: commands/trigger.c:5173 +#: commands/trigger.c:5204 #, c-format msgid "constraint \"%s\" is not deferrable" msgstr "制約\"%s\"は遅延可能ではありません" -#: commands/trigger.c:5196 +#: commands/trigger.c:5227 #, c-format msgid "constraint \"%s\" does not exist" msgstr "制約\"%s\"は存在しません" @@ -10934,17 +10964,17 @@ msgid "Close open transactions with multixacts soon to avoid wraparound problems." msgstr "周回問題を回避するために、マルチトランザクションを使用している実行中のトランザクションをすぐにクローズしてください。" -#: commands/vacuum.c:1640 +#: commands/vacuum.c:1654 #, c-format msgid "some databases have not been vacuumed in over 2 billion transactions" msgstr "データベースの一部は20億トランザクション以上の間にVACUUMを実行されていませんでした" -#: commands/vacuum.c:1641 +#: commands/vacuum.c:1655 #, c-format msgid "You might have already suffered transaction-wraparound data loss." msgstr "トランザクションの周回によるデータ損失が発生している可能性があります" -#: commands/vacuum.c:1801 +#: commands/vacuum.c:1819 #, c-format msgid "skipping \"%s\" --- cannot vacuum non-tables or special system tables" msgstr "\"%s\"をスキップしています --- テーブルではないものや、特別なシステムテーブルに対してはVACUUMを実行できません" @@ -11134,12 +11164,12 @@ msgid "cursor \"%s\" is not a simply updatable scan of table \"%s\"" msgstr "カーソル\"%s\"はテーブル\"%s\"を単純な更新可能スキャンではありません" -#: executor/execCurrent.c:280 executor/execExprInterp.c:2434 +#: executor/execCurrent.c:280 executor/execExprInterp.c:2435 #, c-format msgid "type of parameter %d (%s) does not match that when preparing the plan (%s)" msgstr "パラメータの型%d(%s)が実行計画(%s)を準備する時点と一致しません" -#: executor/execCurrent.c:292 executor/execExprInterp.c:2446 +#: executor/execCurrent.c:292 executor/execExprInterp.c:2447 #, c-format msgid "no value found for parameter %d" msgstr "パラメータ%dの値がありません" @@ -11166,7 +11196,7 @@ msgstr[0] "関数に%dを超える引数を渡せません" msgstr[1] "関数に%dを超える引数を渡せません" -#: executor/execExpr.c:2690 executor/execExpr.c:2696 executor/execExprInterp.c:2759 utils/adt/arrayfuncs.c:262 utils/adt/arrayfuncs.c:562 utils/adt/arrayfuncs.c:1304 utils/adt/arrayfuncs.c:3346 utils/adt/arrayfuncs.c:5308 utils/adt/arrayfuncs.c:5825 +#: executor/execExpr.c:2690 executor/execExpr.c:2696 executor/execExprInterp.c:2760 utils/adt/arrayfuncs.c:262 utils/adt/arrayfuncs.c:562 utils/adt/arrayfuncs.c:1304 utils/adt/arrayfuncs.c:3346 utils/adt/arrayfuncs.c:5308 utils/adt/arrayfuncs.c:5825 #, c-format msgid "number of array dimensions (%d) exceeds the maximum allowed (%d)" msgstr "配列の次数(%d)が上限(%d)を超えています" @@ -11181,79 +11211,79 @@ msgid "attribute %d of type %s has wrong type" msgstr "型%2$sの属性%1$dの型が間違っています" -#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3040 executor/execExprInterp.c:3086 +#: executor/execExprInterp.c:1907 executor/execExprInterp.c:3041 executor/execExprInterp.c:3087 #, c-format msgid "Table has type %s, but query expects %s." msgstr "テーブルの型は%sですが、問い合わせでは%sを想定しています。" -#: executor/execExprInterp.c:1986 utils/adt/expandedrecord.c:99 utils/adt/expandedrecord.c:231 utils/cache/typcache.c:1632 utils/cache/typcache.c:1788 utils/cache/typcache.c:1936 utils/fmgr/funcapi.c:456 +#: executor/execExprInterp.c:1987 utils/adt/expandedrecord.c:99 utils/adt/expandedrecord.c:231 utils/cache/typcache.c:1632 utils/cache/typcache.c:1788 utils/cache/typcache.c:1936 utils/fmgr/funcapi.c:456 #, c-format msgid "type %s is not composite" msgstr "型%sは複合型ではありません" -#: executor/execExprInterp.c:2524 +#: executor/execExprInterp.c:2525 #, c-format msgid "WHERE CURRENT OF is not supported for this table type" msgstr "このタイプのテーブルではWHERE CURRENT OFをサポートしません" -#: executor/execExprInterp.c:2737 +#: executor/execExprInterp.c:2738 #, c-format msgid "cannot merge incompatible arrays" msgstr "互換性がない配列をマージできません" -#: executor/execExprInterp.c:2738 +#: executor/execExprInterp.c:2739 #, c-format msgid "Array with element type %s cannot be included in ARRAY construct with element type %s." msgstr "要素型%sの配列を要素型%sのARRAY式に含められません" -#: executor/execExprInterp.c:2779 executor/execExprInterp.c:2814 +#: executor/execExprInterp.c:2780 executor/execExprInterp.c:2815 #, c-format msgid "multidimensional arrays must have array expressions with matching dimensions" msgstr "多次元配列の配列式の次数があっていなければなりません" -#: executor/execExprInterp.c:2791 utils/adt/array_expanded.c:274 utils/adt/arrayfuncs.c:935 utils/adt/arrayfuncs.c:1522 utils/adt/arrayfuncs.c:3234 utils/adt/arrayfuncs.c:3376 utils/adt/arrayfuncs.c:5917 utils/adt/arrayfuncs.c:6258 utils/adt/arrayutils.c:94 utils/adt/arrayutils.c:103 utils/adt/arrayutils.c:110 +#: executor/execExprInterp.c:2792 utils/adt/array_expanded.c:274 utils/adt/arrayfuncs.c:935 utils/adt/arrayfuncs.c:1522 utils/adt/arrayfuncs.c:3234 utils/adt/arrayfuncs.c:3376 utils/adt/arrayfuncs.c:5917 utils/adt/arrayfuncs.c:6258 utils/adt/arrayutils.c:94 utils/adt/arrayutils.c:103 utils/adt/arrayutils.c:110 #, c-format msgid "array size exceeds the maximum allowed (%d)" msgstr "配列の次数が上限(%d)を超えています" -#: executor/execExprInterp.c:3039 executor/execExprInterp.c:3085 +#: executor/execExprInterp.c:3040 executor/execExprInterp.c:3086 #, c-format msgid "attribute %d has wrong type" msgstr "属性%dの型が間違っています" -#: executor/execExprInterp.c:3199 +#: executor/execExprInterp.c:3204 #, c-format msgid "array subscript in assignment must not be null" msgstr "代入における配列の添え字はnullにはできません" -#: executor/execExprInterp.c:3626 utils/adt/domains.c:149 +#: executor/execExprInterp.c:3631 utils/adt/domains.c:149 #, c-format msgid "domain %s does not allow null values" msgstr "ドメイン%sはnull値を許しません" -#: executor/execExprInterp.c:3641 utils/adt/domains.c:184 +#: executor/execExprInterp.c:3646 utils/adt/domains.c:184 #, c-format msgid "value for domain %s violates check constraint \"%s\"" msgstr "ドメイン%sの値が検査制約\"%s\"に違反しています" -#: executor/execExprInterp.c:4011 executor/execExprInterp.c:4028 executor/execExprInterp.c:4127 executor/nodeModifyTable.c:110 executor/nodeModifyTable.c:121 executor/nodeModifyTable.c:138 executor/nodeModifyTable.c:146 +#: executor/execExprInterp.c:4016 executor/execExprInterp.c:4033 executor/execExprInterp.c:4132 executor/nodeModifyTable.c:110 executor/nodeModifyTable.c:121 executor/nodeModifyTable.c:138 executor/nodeModifyTable.c:146 #, c-format msgid "table row type and query-specified row type do not match" msgstr "テーブルの行型と問い合わせで指定した行型が一致しません" -#: executor/execExprInterp.c:4012 +#: executor/execExprInterp.c:4017 #, c-format msgid "Table row contains %d attribute, but query expects %d." msgid_plural "Table row contains %d attributes, but query expects %d." msgstr[0] "テーブル行には%d属性ありますが、問い合わせでは%dを想定しています。" msgstr[1] "テーブル行には%d属性ありますが、問い合わせでは%dを想定しています。" -#: executor/execExprInterp.c:4029 executor/nodeModifyTable.c:122 +#: executor/execExprInterp.c:4034 executor/nodeModifyTable.c:122 #, c-format msgid "Table has type %s at ordinal position %d, but query expects %s." msgstr "テーブルでは %2$d 番目の型は %1$s ですが、問い合わせでは %3$s を想定しています。" -#: executor/execExprInterp.c:4128 executor/execSRF.c:967 +#: executor/execExprInterp.c:4133 executor/execSRF.c:967 #, c-format msgid "Physical storage mismatch on dropped attribute at ordinal position %d." msgstr "序数位置%dの削除された属性における物理格納形式が一致しません。" @@ -11303,32 +11333,32 @@ msgid "cannot change TOAST relation \"%s\"" msgstr "TOASTリレーション\"%s\"を変更できません" -#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3025 rewrite/rewriteHandler.c:3851 +#: executor/execMain.c:1101 rewrite/rewriteHandler.c:3027 rewrite/rewriteHandler.c:3853 #, c-format msgid "cannot insert into view \"%s\"" msgstr "ビュー\"%s\"へは挿入(INSERT)できません" -#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3028 rewrite/rewriteHandler.c:3854 +#: executor/execMain.c:1103 rewrite/rewriteHandler.c:3030 rewrite/rewriteHandler.c:3856 #, c-format msgid "To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule." msgstr "ビューへの挿入を可能にするために、INSTEAD OF INSERTトリガまたは無条件のON INSERT DO INSTEADルールを作成してください。" -#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3033 rewrite/rewriteHandler.c:3859 +#: executor/execMain.c:1109 rewrite/rewriteHandler.c:3035 rewrite/rewriteHandler.c:3861 #, c-format msgid "cannot update view \"%s\"" msgstr "ビュー\"%s\"は更新できません" -#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3036 rewrite/rewriteHandler.c:3862 +#: executor/execMain.c:1111 rewrite/rewriteHandler.c:3038 rewrite/rewriteHandler.c:3864 #, c-format msgid "To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule." msgstr "ビューへの更新を可能にするために、INSTEAD OF UPDATEトリガまたは無条件のON UPDATE DO INSTEADルールを作成してください。" -#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3041 rewrite/rewriteHandler.c:3867 +#: executor/execMain.c:1117 rewrite/rewriteHandler.c:3043 rewrite/rewriteHandler.c:3869 #, c-format msgid "cannot delete from view \"%s\"" msgstr "ビュー\"%s\"からは削除できません" -#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3044 rewrite/rewriteHandler.c:3870 +#: executor/execMain.c:1119 rewrite/rewriteHandler.c:3046 rewrite/rewriteHandler.c:3872 #, c-format msgid "To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule." msgstr "ビューからの削除を可能にするために、INSTEAD OF DELETEトリガまたは無条件のON DELETE DO INSTEADルールを作成してください。" @@ -11473,7 +11503,7 @@ msgid "concurrent delete, retrying" msgstr "並行する削除がありました、リトライします" -#: executor/execReplication.c:276 parser/parse_oper.c:228 utils/adt/array_userfuncs.c:720 utils/adt/array_userfuncs.c:859 utils/adt/arrayfuncs.c:3626 utils/adt/arrayfuncs.c:4146 utils/adt/arrayfuncs.c:6138 utils/adt/rowtypes.c:1182 +#: executor/execReplication.c:276 parser/parse_oper.c:228 utils/adt/array_userfuncs.c:724 utils/adt/array_userfuncs.c:867 utils/adt/arrayfuncs.c:3626 utils/adt/arrayfuncs.c:4146 utils/adt/arrayfuncs.c:6138 utils/adt/rowtypes.c:1182 #, c-format msgid "could not identify an equality operator for type %s" msgstr "型%sの等価性演算子を識別できませんでした" @@ -11992,7 +12022,7 @@ msgid "duplicate trigger events specified" msgstr "重複したトリガーイベントが指定されました" -#: gram.y:5595 parser/parse_utilcmd.c:3619 parser/parse_utilcmd.c:3645 +#: gram.y:5595 parser/parse_utilcmd.c:3617 parser/parse_utilcmd.c:3643 #, c-format msgid "constraint declared INITIALLY DEFERRED must be DEFERRABLE" msgstr "INITIALLY DEFERREDと宣言された制約はDEFERRABLEでなければなりません" @@ -12324,12 +12354,7 @@ msgid "could not open configuration directory \"%s\": %m" msgstr "設定ディレクトリ\"%s\"をオープンできませんでした: %m" -#: jit/jit.c:205 utils/fmgr/dfmgr.c:209 utils/fmgr/dfmgr.c:417 utils/fmgr/dfmgr.c:465 -#, c-format -msgid "could not access file \"%s\": %m" -msgstr "ファイル\"%s\"にアクセスできませんでした: %m" - -#: jit/llvm/llvmjit.c:730 +#: jit/llvm/llvmjit.c:732 #, c-format msgid "time to inline: %.3fs, opt: %.3fs, emit: %.3fs" msgstr "所要時間: インライン化: %.3fs、最適化: %.3fs、出力: %.3fs" @@ -12366,7 +12391,7 @@ msgid "unsupported Unicode escape sequence" msgstr "サポートされないUnicodeエスケープシーケンス" -#: lib/dshash.c:246 utils/mmgr/dsa.c:702 utils/mmgr/dsa.c:724 utils/mmgr/dsa.c:805 +#: lib/dshash.c:246 utils/mmgr/dsa.c:703 utils/mmgr/dsa.c:725 utils/mmgr/dsa.c:806 #, c-format msgid "Failed on DSA request of size %zu." msgstr "サイズ%zuの動的共有エリアの要求に失敗しました。" @@ -13889,7 +13914,7 @@ msgid "could not receive data from client: %m" msgstr "クライアントからデータを受信できませんでした: %m" -#: libpq/pqcomm.c:1215 tcop/postgres.c:4186 +#: libpq/pqcomm.c:1215 tcop/postgres.c:4187 #, c-format msgid "terminating connection because protocol synchronization was lost" msgstr "プロトコルの同期が失われたためコネクションを終了します" @@ -16245,247 +16270,247 @@ msgid "invalid type name \"%s\"" msgstr "不正な型名\"%s\"" -#: parser/parse_utilcmd.c:276 +#: parser/parse_utilcmd.c:274 #, c-format msgid "cannot create partitioned table as inheritance child" msgstr "パーティションテーブルを継承の子テーブルとして作成はできません" -#: parser/parse_utilcmd.c:457 +#: parser/parse_utilcmd.c:455 #, c-format msgid "%s will create implicit sequence \"%s\" for serial column \"%s.%s\"" msgstr "%1$sはシリアル列\"%3$s.%4$s\"用に暗黙的なシーケンス\"%2$s\"を作成します。" -#: parser/parse_utilcmd.c:588 +#: parser/parse_utilcmd.c:586 #, c-format msgid "array of serial is not implemented" msgstr "連番(SERIAL)の配列は実装されていません" -#: parser/parse_utilcmd.c:666 parser/parse_utilcmd.c:678 parser/parse_utilcmd.c:737 +#: parser/parse_utilcmd.c:664 parser/parse_utilcmd.c:676 parser/parse_utilcmd.c:735 #, c-format msgid "conflicting NULL/NOT NULL declarations for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"でNULL宣言とNOT NULL宣言が競合しています" -#: parser/parse_utilcmd.c:690 +#: parser/parse_utilcmd.c:688 #, c-format msgid "multiple default values specified for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"で複数のデフォルト値の指定があります" -#: parser/parse_utilcmd.c:707 +#: parser/parse_utilcmd.c:705 #, c-format msgid "identity columns are not supported on typed tables" msgstr "型付けされたテーブルでは識別列はサポートされていません" -#: parser/parse_utilcmd.c:711 +#: parser/parse_utilcmd.c:709 #, c-format msgid "identity columns are not supported on partitions" msgstr "パーティションでは識別列はサポートされていません" -#: parser/parse_utilcmd.c:720 +#: parser/parse_utilcmd.c:718 #, c-format msgid "multiple identity specifications for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"に複数の識別指定があります" -#: parser/parse_utilcmd.c:750 +#: parser/parse_utilcmd.c:748 #, c-format msgid "generated columns are not supported on typed tables" msgstr "型付けされたテーブルでは生成カラムはサポートされていません" -#: parser/parse_utilcmd.c:754 +#: parser/parse_utilcmd.c:752 #, c-format msgid "generated columns are not supported on partitions" msgstr "パーティションでは生成カラムはサポートされていません" -#: parser/parse_utilcmd.c:759 +#: parser/parse_utilcmd.c:757 #, c-format msgid "multiple generation clauses specified for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"に複数のGENERATED句の指定があります" -#: parser/parse_utilcmd.c:777 parser/parse_utilcmd.c:892 +#: parser/parse_utilcmd.c:775 parser/parse_utilcmd.c:890 #, c-format msgid "primary key constraints are not supported on foreign tables" msgstr "外部テーブルでは主キー制約はサポートされていません" -#: parser/parse_utilcmd.c:786 parser/parse_utilcmd.c:902 +#: parser/parse_utilcmd.c:784 parser/parse_utilcmd.c:900 #, c-format msgid "unique constraints are not supported on foreign tables" msgstr "外部テーブルではユニーク制約はサポートされていません" -#: parser/parse_utilcmd.c:831 +#: parser/parse_utilcmd.c:829 #, c-format msgid "both default and identity specified for column \"%s\" of table \"%s\"" msgstr "デフォルト値と識別指定の両方がテーブル\"%2$s\"の列\"%1$s\"に指定されています" -#: parser/parse_utilcmd.c:839 +#: parser/parse_utilcmd.c:837 #, c-format msgid "both default and generation expression specified for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"にデフォルト値と生成式の両方が指定されています" -#: parser/parse_utilcmd.c:847 +#: parser/parse_utilcmd.c:845 #, c-format msgid "both identity and generation expression specified for column \"%s\" of table \"%s\"" msgstr "テーブル\"%2$s\"の列\"%1$s\"に識別指定と生成式の両方が指定されています" -#: parser/parse_utilcmd.c:912 +#: parser/parse_utilcmd.c:910 #, c-format msgid "exclusion constraints are not supported on foreign tables" msgstr "外部テーブルでは除外制約はサポートされていません" -#: parser/parse_utilcmd.c:918 +#: parser/parse_utilcmd.c:916 #, c-format msgid "exclusion constraints are not supported on partitioned tables" msgstr "パーティションテーブルでは除外制約はサポートされていません" -#: parser/parse_utilcmd.c:983 +#: parser/parse_utilcmd.c:981 #, c-format msgid "LIKE is not supported for creating foreign tables" msgstr "外部テーブルの作成においてLIKEはサポートされていません" -#: parser/parse_utilcmd.c:1751 parser/parse_utilcmd.c:1860 +#: parser/parse_utilcmd.c:1749 parser/parse_utilcmd.c:1858 #, c-format msgid "Index \"%s\" contains a whole-row table reference." msgstr "インデックス\"%s\"には行全体テーブル参照が含まれます" -#: parser/parse_utilcmd.c:2210 +#: parser/parse_utilcmd.c:2208 #, c-format msgid "cannot use an existing index in CREATE TABLE" msgstr "CREATE TABLE では既存のインデックスを使えません" -#: parser/parse_utilcmd.c:2230 +#: parser/parse_utilcmd.c:2228 #, c-format msgid "index \"%s\" is already associated with a constraint" msgstr "インデックス\"%s\"はすでに1つの制約に割り当てられています" -#: parser/parse_utilcmd.c:2245 +#: parser/parse_utilcmd.c:2243 #, c-format msgid "index \"%s\" is not valid" msgstr "インデックス\"%s\"は有効ではありません" -#: parser/parse_utilcmd.c:2251 +#: parser/parse_utilcmd.c:2249 #, c-format msgid "\"%s\" is not a unique index" msgstr "\"%s\"はユニークインデックスではありません" -#: parser/parse_utilcmd.c:2252 parser/parse_utilcmd.c:2259 parser/parse_utilcmd.c:2266 parser/parse_utilcmd.c:2343 +#: parser/parse_utilcmd.c:2250 parser/parse_utilcmd.c:2257 parser/parse_utilcmd.c:2264 parser/parse_utilcmd.c:2341 #, c-format msgid "Cannot create a primary key or unique constraint using such an index." msgstr "このようなインデックスを使ってプライマリキーや一意性制約を作成することはできません" -#: parser/parse_utilcmd.c:2258 +#: parser/parse_utilcmd.c:2256 #, c-format msgid "index \"%s\" contains expressions" msgstr "インデックス\"%s\"は式を含んでいます" -#: parser/parse_utilcmd.c:2265 +#: parser/parse_utilcmd.c:2263 #, c-format msgid "\"%s\" is a partial index" msgstr "\"%s\"は部分インデックスです" -#: parser/parse_utilcmd.c:2277 +#: parser/parse_utilcmd.c:2275 #, c-format msgid "\"%s\" is a deferrable index" msgstr "\"%s\"は遅延可能インデックスです" -#: parser/parse_utilcmd.c:2278 +#: parser/parse_utilcmd.c:2276 #, c-format msgid "Cannot create a non-deferrable constraint using a deferrable index." msgstr "遅延可能インデックスを使った遅延不可制約は作れません。" -#: parser/parse_utilcmd.c:2342 +#: parser/parse_utilcmd.c:2340 #, c-format msgid "index \"%s\" column number %d does not have default sorting behavior" msgstr "インデックス\"%s\"の列番号%dにはデフォルトのソート動作がありません" -#: parser/parse_utilcmd.c:2499 +#: parser/parse_utilcmd.c:2497 #, c-format msgid "column \"%s\" appears twice in primary key constraint" msgstr "列\"%s\"がプライマリキー制約内に2回出現します" -#: parser/parse_utilcmd.c:2505 +#: parser/parse_utilcmd.c:2503 #, c-format msgid "column \"%s\" appears twice in unique constraint" msgstr "列\"%s\"が一意性制約内に2回出現します" -#: parser/parse_utilcmd.c:2858 +#: parser/parse_utilcmd.c:2856 #, c-format msgid "index expressions and predicates can refer only to the table being indexed" msgstr "インデックス式と述語はインデックス付けされるテーブルのみを参照できます" -#: parser/parse_utilcmd.c:2904 +#: parser/parse_utilcmd.c:2902 #, c-format msgid "rules on materialized views are not supported" msgstr "実体化ビューに対するルールはサポートされません" -#: parser/parse_utilcmd.c:2967 +#: parser/parse_utilcmd.c:2965 #, c-format msgid "rule WHERE condition cannot contain references to other relations" msgstr "ルールのWHERE条件に他のリレーションへの参照を持たせられません" -#: parser/parse_utilcmd.c:3041 +#: parser/parse_utilcmd.c:3039 #, c-format msgid "rules with WHERE conditions can only have SELECT, INSERT, UPDATE, or DELETE actions" msgstr "ルールのWHERE条件はSELECT、INSERT、UPDATE、DELETE動作のみを持つことができます" -#: parser/parse_utilcmd.c:3059 parser/parse_utilcmd.c:3160 rewrite/rewriteHandler.c:525 rewrite/rewriteManip.c:1021 +#: parser/parse_utilcmd.c:3057 parser/parse_utilcmd.c:3158 rewrite/rewriteHandler.c:527 rewrite/rewriteManip.c:1021 #, c-format msgid "conditional UNION/INTERSECT/EXCEPT statements are not implemented" msgstr "条件付きのUNION/INTERSECT/EXCEPT文は実装されていません" -#: parser/parse_utilcmd.c:3077 +#: parser/parse_utilcmd.c:3075 #, c-format msgid "ON SELECT rule cannot use OLD" msgstr "ON SELECTルールではOLDを使用できません" -#: parser/parse_utilcmd.c:3081 +#: parser/parse_utilcmd.c:3079 #, c-format msgid "ON SELECT rule cannot use NEW" msgstr "ON SELECTルールではNEWを使用できません" -#: parser/parse_utilcmd.c:3090 +#: parser/parse_utilcmd.c:3088 #, c-format msgid "ON INSERT rule cannot use OLD" msgstr "ON INSERTルールではOLDを使用できません" -#: parser/parse_utilcmd.c:3096 +#: parser/parse_utilcmd.c:3094 #, c-format msgid "ON DELETE rule cannot use NEW" msgstr "ON DELETEルールではNEWを使用できません" -#: parser/parse_utilcmd.c:3124 +#: parser/parse_utilcmd.c:3122 #, c-format msgid "cannot refer to OLD within WITH query" msgstr "WITH 問い合わせ内では OLD は参照できません" -#: parser/parse_utilcmd.c:3131 +#: parser/parse_utilcmd.c:3129 #, c-format msgid "cannot refer to NEW within WITH query" msgstr "WITH 問い合わせ内では NEW は参照できません" -#: parser/parse_utilcmd.c:3591 +#: parser/parse_utilcmd.c:3589 #, c-format msgid "misplaced DEFERRABLE clause" msgstr "DEFERRABLE句の場所が間違っています" -#: parser/parse_utilcmd.c:3596 parser/parse_utilcmd.c:3611 +#: parser/parse_utilcmd.c:3594 parser/parse_utilcmd.c:3609 #, c-format msgid "multiple DEFERRABLE/NOT DEFERRABLE clauses not allowed" msgstr "複数のDEFERRABLE/NOT DEFERRABLE句を使用できません" -#: parser/parse_utilcmd.c:3606 +#: parser/parse_utilcmd.c:3604 #, c-format msgid "misplaced NOT DEFERRABLE clause" msgstr "NOT DEFERRABLE句の場所が間違っています" -#: parser/parse_utilcmd.c:3627 +#: parser/parse_utilcmd.c:3625 #, c-format msgid "misplaced INITIALLY DEFERRED clause" msgstr "INITIALLY DEFERRED句の場所が間違っています<" -#: parser/parse_utilcmd.c:3632 parser/parse_utilcmd.c:3658 +#: parser/parse_utilcmd.c:3630 parser/parse_utilcmd.c:3656 #, c-format msgid "multiple INITIALLY IMMEDIATE/DEFERRED clauses not allowed" msgstr "複数のINITIALLY IMMEDIATE/DEFERRED句を使用できません" -#: parser/parse_utilcmd.c:3653 +#: parser/parse_utilcmd.c:3651 #, c-format msgid "misplaced INITIALLY IMMEDIATE clause" msgstr "INITIALLY IMMEDIATE句の場所が間違っています<" @@ -16901,32 +16926,32 @@ msgid "autovacuum: processing database \"%s\"" msgstr "自動VACUUM: データベース\"%s\"の処理中です" -#: postmaster/autovacuum.c:2259 +#: postmaster/autovacuum.c:2271 #, c-format msgid "autovacuum: dropping orphan temp table \"%s.%s.%s\"" msgstr "自動VACUUM: 孤立した一時テーブル\"%s.%s.%s\"を削除します" -#: postmaster/autovacuum.c:2488 +#: postmaster/autovacuum.c:2500 #, c-format msgid "automatic vacuum of table \"%s.%s.%s\"" msgstr "テーブル\"%s.%s.%s\"に対する自動VACUUM" -#: postmaster/autovacuum.c:2491 +#: postmaster/autovacuum.c:2503 #, c-format msgid "automatic analyze of table \"%s.%s.%s\"" msgstr "テーブル\"%s.%s.%s\"に対する自動ANALYZE" -#: postmaster/autovacuum.c:2684 +#: postmaster/autovacuum.c:2696 #, c-format msgid "processing work entry for relation \"%s.%s.%s\"" msgstr "リレーション\"%s.%s.%s\"の作業エントリを処理しています" -#: postmaster/autovacuum.c:3288 +#: postmaster/autovacuum.c:3300 #, c-format msgid "autovacuum not started because of misconfiguration" msgstr "誤設定のため自動VACUUMが起動できません" -#: postmaster/autovacuum.c:3289 +#: postmaster/autovacuum.c:3301 #, c-format msgid "Enable the \"track_counts\" option." msgstr "\"track_counts\"オプションを有効にしてください。" @@ -18824,7 +18849,7 @@ msgid "could not write to log segment %s at offset %u, length %lu: %m" msgstr "ログファイルセグメント%sのオフセット%uに長さ%luで書き出せませんでした: %m" -#: replication/walsender.c:528 storage/smgr/md.c:1330 +#: replication/walsender.c:528 storage/smgr/md.c:1333 #, c-format msgid "could not seek to end of file \"%s\": %m" msgstr "ファイル\"%s\"の終端へシークできませんでした: %m" @@ -19164,196 +19189,196 @@ msgid "renaming an ON SELECT rule is not allowed" msgstr "ON SELECTルールの名前を変更することはできません" -#: rewrite/rewriteHandler.c:569 +#: rewrite/rewriteHandler.c:571 #, c-format msgid "WITH query name \"%s\" appears in both a rule action and the query being rewritten" msgstr "WITH の問い合わせ名\"%s\"が、ルールのアクションと書き換えられようとしている問い合わせの両方に現れています" -#: rewrite/rewriteHandler.c:596 +#: rewrite/rewriteHandler.c:598 #, c-format msgid "INSERT...SELECT rule actions are not supported for queries having data-modifying statements in WITH" msgstr "INSERT...SELECTルールのアクションはWITHにデータ更新文を持つ問い合わせに対してはサポートされません" -#: rewrite/rewriteHandler.c:649 +#: rewrite/rewriteHandler.c:651 #, c-format msgid "cannot have RETURNING lists in multiple rules" msgstr "複数ルールではRETURNINGリストを持つことはできません" -#: rewrite/rewriteHandler.c:860 rewrite/rewriteHandler.c:872 +#: rewrite/rewriteHandler.c:862 rewrite/rewriteHandler.c:874 #, c-format msgid "cannot insert into column \"%s\"" msgstr "列\"%s\"への挿入はできません" -#: rewrite/rewriteHandler.c:861 rewrite/rewriteHandler.c:883 +#: rewrite/rewriteHandler.c:863 rewrite/rewriteHandler.c:885 #, c-format msgid "Column \"%s\" is an identity column defined as GENERATED ALWAYS." msgstr "列\"%s\"は GENERATED ALWAYS として定義されています。" -#: rewrite/rewriteHandler.c:863 +#: rewrite/rewriteHandler.c:865 #, c-format msgid "Use OVERRIDING SYSTEM VALUE to override." msgstr "OVERRIDING SYSTEM VALUE を指定することで挿入を強制できます。" -#: rewrite/rewriteHandler.c:882 rewrite/rewriteHandler.c:889 +#: rewrite/rewriteHandler.c:884 rewrite/rewriteHandler.c:891 #, c-format msgid "column \"%s\" can only be updated to DEFAULT" msgstr "列\"%s\"はDEFAULTにのみ更新可能です" -#: rewrite/rewriteHandler.c:1058 rewrite/rewriteHandler.c:1076 +#: rewrite/rewriteHandler.c:1060 rewrite/rewriteHandler.c:1078 #, c-format msgid "multiple assignments to same column \"%s\"" msgstr "同じ列\"%s\"に複数の代入があります" -#: rewrite/rewriteHandler.c:2068 rewrite/rewriteHandler.c:3925 +#: rewrite/rewriteHandler.c:2070 rewrite/rewriteHandler.c:3927 #, c-format msgid "infinite recursion detected in rules for relation \"%s\"" msgstr "リレーション\"%s\"のルールで無限再帰を検出しました" -#: rewrite/rewriteHandler.c:2153 +#: rewrite/rewriteHandler.c:2155 #, c-format msgid "infinite recursion detected in policy for relation \"%s\"" msgstr "リレーション\"%s\"のポリシで無限再帰を検出しました" -#: rewrite/rewriteHandler.c:2473 +#: rewrite/rewriteHandler.c:2475 msgid "Junk view columns are not updatable." msgstr "ジャンクビュー列は更新不可です。" -#: rewrite/rewriteHandler.c:2478 +#: rewrite/rewriteHandler.c:2480 msgid "View columns that are not columns of their base relation are not updatable." msgstr "基底リレーションの列ではないビュー列は更新不可です。" -#: rewrite/rewriteHandler.c:2481 +#: rewrite/rewriteHandler.c:2483 msgid "View columns that refer to system columns are not updatable." msgstr "システム列を参照するビュー列は更新不可です。" -#: rewrite/rewriteHandler.c:2484 +#: rewrite/rewriteHandler.c:2486 msgid "View columns that return whole-row references are not updatable." msgstr "行全体参照を返すビュー列は更新不可です。" -#: rewrite/rewriteHandler.c:2545 +#: rewrite/rewriteHandler.c:2547 msgid "Views containing DISTINCT are not automatically updatable." msgstr "DISTINCTを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2548 +#: rewrite/rewriteHandler.c:2550 msgid "Views containing GROUP BY are not automatically updatable." msgstr "GROUP BYを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2551 +#: rewrite/rewriteHandler.c:2553 msgid "Views containing HAVING are not automatically updatable." msgstr "HAVINGを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2554 +#: rewrite/rewriteHandler.c:2556 msgid "Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable." msgstr "UNION、INTERSECT、EXCEPTを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2557 +#: rewrite/rewriteHandler.c:2559 msgid "Views containing WITH are not automatically updatable." msgstr "WITHを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2560 +#: rewrite/rewriteHandler.c:2562 msgid "Views containing LIMIT or OFFSET are not automatically updatable." msgstr "LIMIT、OFFSETを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2572 +#: rewrite/rewriteHandler.c:2574 msgid "Views that return aggregate functions are not automatically updatable." msgstr "集約関数を返すビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2575 +#: rewrite/rewriteHandler.c:2577 msgid "Views that return window functions are not automatically updatable." msgstr "ウィンドウ関数を返すビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2578 +#: rewrite/rewriteHandler.c:2580 msgid "Views that return set-returning functions are not automatically updatable." msgstr "集合返却関数を返すビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2585 rewrite/rewriteHandler.c:2589 rewrite/rewriteHandler.c:2597 +#: rewrite/rewriteHandler.c:2587 rewrite/rewriteHandler.c:2591 rewrite/rewriteHandler.c:2599 msgid "Views that do not select from a single table or view are not automatically updatable." msgstr "単一のテーブルまたはビューからselectしていないビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2600 +#: rewrite/rewriteHandler.c:2602 msgid "Views containing TABLESAMPLE are not automatically updatable." msgstr "TABLESAMPLEを含むビューは自動更新できません。" -#: rewrite/rewriteHandler.c:2624 +#: rewrite/rewriteHandler.c:2626 msgid "Views that have no updatable columns are not automatically updatable." msgstr "更新可能な列を持たないビューは自動更新できません。" -#: rewrite/rewriteHandler.c:3101 +#: rewrite/rewriteHandler.c:3103 #, c-format msgid "cannot insert into column \"%s\" of view \"%s\"" msgstr "ビュー\"%2$s\"の列\"%1$s\"への挿入はできません" -#: rewrite/rewriteHandler.c:3109 +#: rewrite/rewriteHandler.c:3111 #, c-format msgid "cannot update column \"%s\" of view \"%s\"" msgstr "ビュー\"%2$s\"の列\"%1$s\"は更新できません" -#: rewrite/rewriteHandler.c:3594 +#: rewrite/rewriteHandler.c:3596 #, c-format msgid "DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH" msgstr "DO INSTEAD NOTIFYルールはWITH内のデータ更新文に対してはサポートされません" -#: rewrite/rewriteHandler.c:3605 +#: rewrite/rewriteHandler.c:3607 #, c-format msgid "DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH" msgstr "WITH にデータを変更するステートメントがある場合は DO INSTEAD NOTHING ルールはサポートされません" -#: rewrite/rewriteHandler.c:3619 +#: rewrite/rewriteHandler.c:3621 #, c-format msgid "conditional DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "WITH にデータを変更するステートメントがある場合は、条件付き DO INSTEAD ルールはサポートされません" -#: rewrite/rewriteHandler.c:3623 +#: rewrite/rewriteHandler.c:3625 #, c-format msgid "DO ALSO rules are not supported for data-modifying statements in WITH" msgstr "WITH にデータを変更するステートメントがある場合は DO ALSO ルールはサポートされません" -#: rewrite/rewriteHandler.c:3628 +#: rewrite/rewriteHandler.c:3630 #, c-format msgid "multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH" msgstr "WITH にデータを変更するステートメントがある場合はマルチステートメントの DO INSTEAD ルールはサポートされません" -#: rewrite/rewriteHandler.c:3853 rewrite/rewriteHandler.c:3861 rewrite/rewriteHandler.c:3869 +#: rewrite/rewriteHandler.c:3855 rewrite/rewriteHandler.c:3863 rewrite/rewriteHandler.c:3871 #, c-format msgid "Views with conditional DO INSTEAD rules are not automatically updatable." msgstr "条件付きDO INSTEADルールを持つビューは自動更新できません。" -#: rewrite/rewriteHandler.c:3974 +#: rewrite/rewriteHandler.c:3976 #, c-format msgid "cannot perform INSERT RETURNING on relation \"%s\"" msgstr "リレーション\"%s\"へのINSERT RETURNINGを行うことはできません" -#: rewrite/rewriteHandler.c:3976 +#: rewrite/rewriteHandler.c:3978 #, c-format msgid "You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause." msgstr "RETURNING句を持つ無条件のON INSERT DO INSTEADルールが必要です。" -#: rewrite/rewriteHandler.c:3981 +#: rewrite/rewriteHandler.c:3983 #, c-format msgid "cannot perform UPDATE RETURNING on relation \"%s\"" msgstr "リレーション\"%s\"へのUPDATE RETURNINGを行うことはできません" -#: rewrite/rewriteHandler.c:3983 +#: rewrite/rewriteHandler.c:3985 #, c-format msgid "You need an unconditional ON UPDATE DO INSTEAD rule with a RETURNING clause." msgstr "RETURNING句を持つ無条件のON UPDATE DO INSTEADルールが必要です。" -#: rewrite/rewriteHandler.c:3988 +#: rewrite/rewriteHandler.c:3990 #, c-format msgid "cannot perform DELETE RETURNING on relation \"%s\"" msgstr "リレーション\"%s\"へのDELETE RETURNINGを行うことはできません" -#: rewrite/rewriteHandler.c:3990 +#: rewrite/rewriteHandler.c:3992 #, c-format msgid "You need an unconditional ON DELETE DO INSTEAD rule with a RETURNING clause." msgstr "RETURNING句を持つ無条件のON DELETE DO INSTEADルールが必要です。" -#: rewrite/rewriteHandler.c:4008 +#: rewrite/rewriteHandler.c:4010 #, c-format msgid "INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules" msgstr "ON CONFLICT句を伴うINSERTは、INSERTまたはUPDATEルールを持つテーブルでは使えません" -#: rewrite/rewriteHandler.c:4065 +#: rewrite/rewriteHandler.c:4067 #, c-format msgid "WITH cannot be used in a query that is rewritten by rules into multiple queries" msgstr "複数問い合わせに対するルールにより書き換えられた問い合わせでは WITH を使用できません" @@ -19748,17 +19773,17 @@ msgid "%s failed: %m" msgstr "%s が失敗しました: %m" -#: storage/ipc/procarray.c:3126 +#: storage/ipc/procarray.c:3127 #, c-format msgid "database \"%s\" is being used by prepared transactions" msgstr "データベース\"%s\"は準備済みトランザクションで使用中です" -#: storage/ipc/procarray.c:3158 storage/ipc/signalfuncs.c:142 +#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:142 #, c-format msgid "must be a superuser to terminate superuser process" msgstr "スーパユーザのプロセスを終了させるにはスーパユーザである必要があります" -#: storage/ipc/procarray.c:3165 storage/ipc/signalfuncs.c:147 +#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:147 #, c-format msgid "must be a member of the role whose process is being terminated or member of pg_signal_backend" msgstr "終了しようとしているプロセスのロールまたはpg_signal_backendのメンバである必要があります。" @@ -19773,7 +19798,7 @@ msgid "invalid message size %zu in shared memory queue" msgstr "共有メモリキュー内の不正なメッセージ長%zu" -#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:982 storage/lmgr/lock.c:1020 storage/lmgr/lock.c:2845 storage/lmgr/lock.c:4252 storage/lmgr/lock.c:4317 storage/lmgr/lock.c:4667 storage/lmgr/predicate.c:2489 storage/lmgr/predicate.c:2504 storage/lmgr/predicate.c:3994 storage/lmgr/predicate.c:5109 utils/hash/dynahash.c:1067 +#: storage/ipc/shm_toc.c:118 storage/ipc/shm_toc.c:200 storage/lmgr/lock.c:963 storage/lmgr/lock.c:1001 storage/lmgr/lock.c:2821 storage/lmgr/lock.c:4228 storage/lmgr/lock.c:4293 storage/lmgr/lock.c:4643 storage/lmgr/predicate.c:2489 storage/lmgr/predicate.c:2504 storage/lmgr/predicate.c:3994 storage/lmgr/predicate.c:5109 utils/hash/dynahash.c:1067 #, c-format msgid "out of shared memory" msgstr "共有メモリが足りません" @@ -19808,7 +19833,7 @@ msgid "PID %d is not a PostgreSQL server process" msgstr "PID %dはPostgreSQLサーバプロセスではありません" -#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1370 +#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1372 #, c-format msgid "could not send signal to process %d: %m" msgstr "プロセス%dにシグナルを送信できませんでした: %m" @@ -19869,22 +19894,22 @@ msgid "invalid large object write request size: %d" msgstr "ラージオブジェクトの書き出し要求サイズが不正です: %d" -#: storage/lmgr/deadlock.c:1124 +#: storage/lmgr/deadlock.c:1123 #, c-format msgid "Process %d waits for %s on %s; blocked by process %d." msgstr "プロセス %d は %s を %s で待機していましたが、プロセス %d でブロックされました" -#: storage/lmgr/deadlock.c:1143 +#: storage/lmgr/deadlock.c:1142 #, c-format msgid "Process %d: %s" msgstr "プロセス %d: %s" -#: storage/lmgr/deadlock.c:1152 +#: storage/lmgr/deadlock.c:1151 #, c-format msgid "deadlock detected" msgstr "デッドロックを検出しました" -#: storage/lmgr/deadlock.c:1155 +#: storage/lmgr/deadlock.c:1154 #, c-format msgid "See server log for query details." msgstr "問い合わせの詳細はサーバログを参照してください" @@ -19989,22 +20014,22 @@ msgid "unrecognized locktag type %d" msgstr "ロックタグタイプ%dは不明です" -#: storage/lmgr/lock.c:803 +#: storage/lmgr/lock.c:791 #, c-format msgid "cannot acquire lock mode %s on database objects while recovery is in progress" msgstr "リカバリの実行中はデータベースオブジェクトでロックモード %s を獲得できません" -#: storage/lmgr/lock.c:805 +#: storage/lmgr/lock.c:793 #, c-format msgid "Only RowExclusiveLock or less can be acquired on database objects during recovery." msgstr "リカバリの実行中は、データベースオブジェクトで RowExclusiveLock もしくはそれ以下だけが獲得できます" -#: storage/lmgr/lock.c:983 storage/lmgr/lock.c:1021 storage/lmgr/lock.c:2846 storage/lmgr/lock.c:4253 storage/lmgr/lock.c:4318 storage/lmgr/lock.c:4668 +#: storage/lmgr/lock.c:964 storage/lmgr/lock.c:1002 storage/lmgr/lock.c:2822 storage/lmgr/lock.c:4229 storage/lmgr/lock.c:4294 storage/lmgr/lock.c:4644 #, c-format msgid "You might need to increase max_locks_per_transaction." msgstr "max_locks_per_transactionを増やす必要があるかもしれません" -#: storage/lmgr/lock.c:3301 storage/lmgr/lock.c:3369 storage/lmgr/lock.c:3485 +#: storage/lmgr/lock.c:3277 storage/lmgr/lock.c:3345 storage/lmgr/lock.c:3461 #, c-format msgid "cannot PREPARE while holding both session-level and transaction-level locks on the same object" msgstr "同一オブジェクト上にセッションレベルとトランザクションレベルのロックの両方を保持している時にPREPAREすることはできません" @@ -20074,37 +20099,37 @@ msgid "number of requested standby connections exceeds max_wal_senders (currently %d)" msgstr "要求されたスタンバイ接続が max_wal_senders を超えています（現在は %d）" -#: storage/lmgr/proc.c:1341 +#: storage/lmgr/proc.c:1343 #, c-format msgid "Process %d waits for %s on %s." msgstr "プロセス%dは%sを%sで待機しています。" -#: storage/lmgr/proc.c:1352 +#: storage/lmgr/proc.c:1354 #, c-format msgid "sending cancel to blocking autovacuum PID %d" msgstr "ブロックしている自動VACUUMプロセスのPID %dへキャンセルを送付しています" -#: storage/lmgr/proc.c:1472 +#: storage/lmgr/proc.c:1474 #, c-format msgid "process %d avoided deadlock for %s on %s by rearranging queue order after %ld.%03d ms" msgstr "プロセス%1$dは、%4$ld.%5$03d ms後にキューの順番を再調整することで、%3$s上の%2$sに対するデッドロックを防ぎました。" -#: storage/lmgr/proc.c:1487 +#: storage/lmgr/proc.c:1489 #, c-format msgid "process %d detected deadlock while waiting for %s on %s after %ld.%03d ms" msgstr "プロセス%1$dは、%3$s上の%2$sに対し%4$ld.%5$03d ms待機するデッドロックを検知しました" -#: storage/lmgr/proc.c:1496 +#: storage/lmgr/proc.c:1498 #, c-format msgid "process %d still waiting for %s on %s after %ld.%03d ms" msgstr "プロセス%dは%sを%sで待機しています。%ld.%03dミリ秒後" -#: storage/lmgr/proc.c:1503 +#: storage/lmgr/proc.c:1505 #, c-format msgid "process %d acquired %s on %s after %ld.%03d ms" msgstr "プロセス%1$dは%4$ld.%5$03d ms後に%3$s上の%2$sを獲得しました" -#: storage/lmgr/proc.c:1519 +#: storage/lmgr/proc.c:1521 #, c-format msgid "process %d failed to acquire %s on %s after %ld.%03d ms" msgstr "プロセス%1$dは%4$ld.%5$03d ms後に%3$s上で%2$sを獲得することに失敗しました" @@ -20134,72 +20159,72 @@ msgid "corrupted line pointer: offset = %u, size = %u" msgstr "ラインポインタが破損しています: オフセット = %u サイズ = %u" -#: storage/smgr/md.c:317 storage/smgr/md.c:875 +#: storage/smgr/md.c:320 storage/smgr/md.c:878 #, c-format msgid "could not truncate file \"%s\": %m" msgstr "ファイル\"%s\"の切り詰め処理ができませんでした: %m" -#: storage/smgr/md.c:446 +#: storage/smgr/md.c:449 #, c-format msgid "cannot extend file \"%s\" beyond %u blocks" msgstr "ファイル\"%s\"を%uブロック以上に拡張できません" -#: storage/smgr/md.c:461 +#: storage/smgr/md.c:464 #, c-format msgid "could not extend file \"%s\": %m" msgstr "ファイル\"%s\"を拡張できませんでした: %m" -#: storage/smgr/md.c:463 storage/smgr/md.c:470 storage/smgr/md.c:758 +#: storage/smgr/md.c:466 storage/smgr/md.c:473 storage/smgr/md.c:761 #, c-format msgid "Check free disk space." msgstr "ディスクの空き容量をチェックしてください。" -#: storage/smgr/md.c:467 +#: storage/smgr/md.c:470 #, c-format msgid "could not extend file \"%s\": wrote only %d of %d bytes at block %u" msgstr "ファイル\"%1$s\"を拡張できませんでした: %4$uブロックで%3$dバイト中%2$dバイト分のみを書き出しました。" -#: storage/smgr/md.c:679 +#: storage/smgr/md.c:682 #, c-format msgid "could not read block %u in file \"%s\": %m" msgstr "ファイル\"%2$s\"で%1$uブロックを読み取れませんでした: %3$m" -#: storage/smgr/md.c:695 +#: storage/smgr/md.c:698 #, c-format msgid "could not read block %u in file \"%s\": read only %d of %d bytes" msgstr "ファイル\"%2$s\"のブロック%1$uを読み取れませんでした: %4$dバイト中%3$dバイト分のみ読み取りました" -#: storage/smgr/md.c:749 +#: storage/smgr/md.c:752 #, c-format msgid "could not write block %u in file \"%s\": %m" msgstr "ファイル\"%2$s\"で%1$uブロックが書き出せませんでした: %3$m" -#: storage/smgr/md.c:754 +#: storage/smgr/md.c:757 #, c-format msgid "could not write block %u in file \"%s\": wrote only %d of %d bytes" msgstr "ファイル\"%2$s\"のブロック%1$uを書き込めませんでした: %4$dバイト中%3$dバイト分のみ書き込みました" -#: storage/smgr/md.c:846 +#: storage/smgr/md.c:849 #, c-format msgid "could not truncate file \"%s\" to %u blocks: it's only %u blocks now" msgstr "ファイル\"%s\"を%uブロックに切り詰められませんでした: 現在は%uブロックのみとなりました" -#: storage/smgr/md.c:901 +#: storage/smgr/md.c:904 #, c-format msgid "could not truncate file \"%s\" to %u blocks: %m" msgstr "ファイル\"%s\"を%uブロックに切り詰められませんでした: %m" -#: storage/smgr/md.c:996 +#: storage/smgr/md.c:999 #, c-format msgid "could not forward fsync request because request queue is full" msgstr "リクエストキューが満杯につき fsync リクエストのフォワードができませんでした" -#: storage/smgr/md.c:1295 +#: storage/smgr/md.c:1298 #, c-format msgid "could not open file \"%s\" (target block %u): previous segment is only %u blocks" msgstr "ファイル\"%s\"(対象ブロック%u)をオープンできませんでした: 直前のセグメントは%uブロックだけでした" -#: storage/smgr/md.c:1309 +#: storage/smgr/md.c:1312 #, c-format msgid "could not open file \"%s\" (target block %u): %m" msgstr "ファイル \"%s\"（対象ブロック %u）をオープンできませんでした: %m" @@ -20254,7 +20279,7 @@ msgid "unexpected EOF on client connection" msgstr "クライアント接続に想定外のEOFがありました" -#: tcop/postgres.c:440 tcop/postgres.c:452 tcop/postgres.c:463 tcop/postgres.c:475 tcop/postgres.c:4583 +#: tcop/postgres.c:440 tcop/postgres.c:452 tcop/postgres.c:463 tcop/postgres.c:475 tcop/postgres.c:4587 #, c-format msgid "invalid frontend message type %d" msgstr "フロントエンドメッセージタイプ%dが不正です" @@ -20505,27 +20530,27 @@ msgid "%s: no database nor user name specified" msgstr "%s: データベース名もユーザ名も指定されていません" -#: tcop/postgres.c:4491 +#: tcop/postgres.c:4495 #, c-format msgid "invalid CLOSE message subtype %d" msgstr "不正なCLOSEメッセージのサブタイプ%d" -#: tcop/postgres.c:4526 +#: tcop/postgres.c:4530 #, c-format msgid "invalid DESCRIBE message subtype %d" msgstr "不正なDESCRIBEメッセージのサブタイプ%d" -#: tcop/postgres.c:4604 +#: tcop/postgres.c:4608 #, c-format msgid "fastpath function calls not supported in a replication connection" msgstr "レプリケーション接続では高速関数呼び出しはサポートされていません" -#: tcop/postgres.c:4608 +#: tcop/postgres.c:4612 #, c-format msgid "extended query protocol not supported in a replication connection" msgstr "レプリケーション接続では拡張問い合わせプロトコルはサポートされていません" -#: tcop/postgres.c:4785 +#: tcop/postgres.c:4789 #, c-format msgid "disconnection: session time: %d:%02d:%02d.%03d user=%s database=%s host=%s%s%s" msgstr "接続を切断: セッション時間: %d:%02d:%02d.%03d ユーザ=%s データベース=%s ホスト=%s%s%s" @@ -20800,27 +20825,27 @@ msgid "text search parser does not support headline creation" msgstr "テキスト検索パーサは見出し作成をサポートしません" -#: tsearch/wparser_def.c:2581 +#: tsearch/wparser_def.c:2600 #, c-format msgid "unrecognized headline parameter: \"%s\"" msgstr "認識できない見出しパラメータ: \"%s\"" -#: tsearch/wparser_def.c:2600 +#: tsearch/wparser_def.c:2619 #, c-format msgid "MinWords should be less than MaxWords" msgstr "MinWordsはMaxWordsより小さくなければなりません" -#: tsearch/wparser_def.c:2604 +#: tsearch/wparser_def.c:2623 #, c-format msgid "MinWords should be positive" msgstr "MinWordsは正でなければなりません" -#: tsearch/wparser_def.c:2608 +#: tsearch/wparser_def.c:2627 #, c-format msgid "ShortWord should be >= 0" msgstr "ShortWordは>= 0でなければなりません" -#: tsearch/wparser_def.c:2612 +#: tsearch/wparser_def.c:2631 #, c-format msgid "MaxFragments should be >= 0" msgstr "MaxFragments は 0 以上でなければなりません" @@ -20981,12 +21006,12 @@ msgid "Arrays with differing dimensions are not compatible for concatenation." msgstr "異なる次数の配列の連結には互換性がありません。" -#: utils/adt/array_userfuncs.c:663 utils/adt/array_userfuncs.c:815 +#: utils/adt/array_userfuncs.c:662 utils/adt/array_userfuncs.c:816 #, c-format msgid "searching for elements in multidimensional arrays is not supported" msgstr "多次元配列内の要素の検索はサポートされません" -#: utils/adt/array_userfuncs.c:687 +#: utils/adt/array_userfuncs.c:691 #, c-format msgid "initial position must not be null" msgstr "初期位置nullであってはなりません" @@ -22363,42 +22388,42 @@ msgid "jsonpath item method .%s() can only be applied to a string" msgstr "jsonpath 項目メソッド .%s() は文字列にのみ適用可能です" -#: utils/adt/jsonpath_exec.c:1894 +#: utils/adt/jsonpath_exec.c:1903 #, c-format msgid "datetime format is not recognized: \"%s\"" msgstr "datetime書式を認識できません: \"%s\"" -#: utils/adt/jsonpath_exec.c:1896 +#: utils/adt/jsonpath_exec.c:1905 #, c-format msgid "Use a datetime template argument to specify the input data format." msgstr "datetimeテンプレート引数を使って入力データフォーマットを指定してください。" -#: utils/adt/jsonpath_exec.c:1964 +#: utils/adt/jsonpath_exec.c:1973 #, c-format msgid "jsonpath item method .%s() can only be applied to an object" msgstr "jsonpath項目メソッド .%s() はオブジェクトに対してのみ適用可能です" -#: utils/adt/jsonpath_exec.c:2147 +#: utils/adt/jsonpath_exec.c:2156 #, c-format msgid "could not find jsonpath variable \"%s\"" msgstr "jsonpath変数\"%s\"が見つかりませんでした" -#: utils/adt/jsonpath_exec.c:2411 +#: utils/adt/jsonpath_exec.c:2420 #, c-format msgid "jsonpath array subscript is not a single numeric value" msgstr "jsonpath配列添え字が単一の数値ではありません" -#: utils/adt/jsonpath_exec.c:2423 +#: utils/adt/jsonpath_exec.c:2432 #, c-format msgid "jsonpath array subscript is out of integer range" msgstr "jsonpath配列の添え字が整数の範囲外です" -#: utils/adt/jsonpath_exec.c:2600 +#: utils/adt/jsonpath_exec.c:2609 #, c-format msgid "cannot convert value from %s to %s without time zone usage" msgstr "時間帯を使用せずに%sから%sへの値の変換はできません" -#: utils/adt/jsonpath_exec.c:2602 +#: utils/adt/jsonpath_exec.c:2611 #, c-format msgid "Use *_tz() function for time zone support." msgstr "Use *_tz() function for time zone suppo*_tz() 関数を使用することで時間帯がサポートされます。" @@ -23773,22 +23798,22 @@ msgid "operator class \"%s\" of access method %s is missing support function %d for type %s" msgstr "アクセスメソッド %2$s の演算子クラス\"%1$s\"は%4$s型に対応するサポート関数%3$dを含んでいません" -#: utils/cache/plancache.c:718 +#: utils/cache/plancache.c:720 #, c-format msgid "cached plan must not change result type" msgstr "キャッシュした実行計画は結果型を変更してはなりません" -#: utils/cache/relcache.c:6200 +#: utils/cache/relcache.c:6201 #, c-format msgid "could not create relation-cache initialization file \"%s\": %m" msgstr "リレーションキャッシュ初期化ファイル\"%sを作成できません: %m" -#: utils/cache/relcache.c:6202 +#: utils/cache/relcache.c:6203 #, c-format msgid "Continuing anyway, but there's something wrong." msgstr "とりあえず続行しますが、何かがおかしいです。" -#: utils/cache/relcache.c:6524 +#: utils/cache/relcache.c:6525 #, c-format msgid "could not remove cache file \"%s\": %m" msgstr "キャッシュファイル\"%s\"を削除できませんでした: %m" @@ -24367,17 +24392,22 @@ msgid "database %u does not exist" msgstr "データベース %u は存在しません" -#: utils/init/postinit.c:983 +#: utils/init/postinit.c:984 #, c-format msgid "It seems to have just been dropped or renamed." msgstr "削除またはリネームされたばかりのようです。" -#: utils/init/postinit.c:1001 +#: utils/init/postinit.c:991 +#, c-format +msgid "cannot connect to invalid database \"%s\"" +msgstr "無効なデータベース\"%s\"への接続はできません" + +#: utils/init/postinit.c:1011 #, c-format msgid "The database subdirectory \"%s\" is missing." msgstr "データベースのサブディレクトリ\"%s\"がありません。" -#: utils/init/postinit.c:1006 +#: utils/init/postinit.c:1016 #, c-format msgid "could not access directory \"%s\": %m" msgstr "ディレクトリ\"%s\"にアクセスできませんでした: %m" @@ -26633,7 +26663,7 @@ msgid "Failed while creating memory context \"%s\"." msgstr "メモリコンテキスト\"%s\"の作成時に失敗しました" -#: utils/mmgr/dsa.c:519 utils/mmgr/dsa.c:1332 +#: utils/mmgr/dsa.c:520 utils/mmgr/dsa.c:1337 #, c-format msgid "could not attach to dynamic shared area" msgstr "動的共有エリアをアタッチできませんでした" diff -Nru postgresql-13-13.11/src/backend/po/zh_CN.po postgresql-13-13.12/src/backend/po/zh_CN.po --- postgresql-13-13.11/src/backend/po/zh_CN.po 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/po/zh_CN.po 2023-08-07 20:11:34.000000000 +0000 @@ -25312,7 +25312,7 @@ #: utils/misc/guc.c:2708 msgid "Zero prints all queries, subject to log_statement_sample_rate. -1 turns this feature off." -msgstr "如果值设置为0，那么打印出所有查询,以og_statement_sample_rate为准. 如果设置为-1，那么将把这个功能特性关闭." +msgstr "如果值设置为0，那么打印出所有查询,以log_statement_sample_rate为准. 如果设置为-1，那么将把这个功能特性关闭." #: utils/misc/guc.c:2719 msgid "Sets the minimum execution time above which autovacuum actions will be logged." diff -Nru postgresql-13-13.11/src/backend/postmaster/autovacuum.c postgresql-13-13.12/src/backend/postmaster/autovacuum.c --- postgresql-13-13.11/src/backend/postmaster/autovacuum.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/postmaster/autovacuum.c 2023-08-07 20:11:34.000000000 +0000 @@ -1891,6 +1891,18 @@ MemoryContext oldcxt; /* + * If database has partially been dropped, we can't, nor need to, + * vacuum it. + */ + if (database_is_invalid_form(pgdatabase)) + { + elog(DEBUG2, + "autovacuum: skipping invalid database \"%s\"", + NameStr(pgdatabase->datname)); + continue; + } + + /* * Allocate our results in the caller's context, not the * transaction's. We do this inside the loop, and restore the original * context at the end, so that leaky things like heap_getnext() are diff -Nru postgresql-13-13.11/src/backend/rewrite/rewriteHandler.c postgresql-13-13.12/src/backend/rewrite/rewriteHandler.c --- postgresql-13-13.11/src/backend/rewrite/rewriteHandler.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/rewrite/rewriteHandler.c 2023-08-07 20:11:34.000000000 +0000 @@ -472,6 +472,8 @@ /* other RTE types don't contain bare expressions */ break; } + sub_action->hasSubLinks |= + checkExprHasSubLink((Node *) rte->securityQuals); if (sub_action->hasSubLinks) break; /* no need to keep scanning rtable */ } @@ -3269,7 +3271,7 @@ view_targetlist, REPLACEVARS_REPORT_ERROR, 0, - &parsetree->hasSubLinks); + NULL); /* * Update all other RTI references in the query that point to the view @@ -3289,7 +3291,7 @@ * columns to be affected. * * Note that this destroys the resno ordering of the targetlist, but that - * will be fixed when we recurse through rewriteQuery, which will invoke + * will be fixed when we recurse through RewriteQuery, which will invoke * rewriteTargetListIU again on the updated targetlist. */ if (parsetree->commandType != CMD_DELETE) diff -Nru postgresql-13-13.11/src/backend/storage/ipc/procarray.c postgresql-13-13.12/src/backend/storage/ipc/procarray.c --- postgresql-13-13.11/src/backend/storage/ipc/procarray.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/ipc/procarray.c 2023-08-07 20:11:34.000000000 +0000 @@ -644,6 +644,7 @@ /* redundant, but just in case */ pgxact->vacuumFlags &= ~PROC_VACUUM_STATE_MASK; proc->delayChkpt = false; + proc->delayChkptEnd = false; /* Clear the subtransaction-XID cache too */ pgxact->nxids = 0; diff -Nru postgresql-13-13.11/src/backend/storage/lmgr/README postgresql-13-13.12/src/backend/storage/lmgr/README --- postgresql-13-13.11/src/backend/storage/lmgr/README 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/lmgr/README 2023-08-07 20:11:34.000000000 +0000 @@ -597,10 +597,10 @@ complicated. We choose to regard locks held by processes in the same parallel group as -non-conflicting with the exception of relation extension and page locks. This -means that two processes in a parallel group can hold a self-exclusive lock on -the same relation at the same time, or one process can acquire an AccessShareLock -while the other already holds AccessExclusiveLock. This might seem dangerous and +non-conflicting with the exception of relation extension lock. This means that +two processes in a parallel group can hold a self-exclusive lock on the same +relation at the same time, or one process can acquire an AccessShareLock while +the other already holds AccessExclusiveLock. This might seem dangerous and could be in some cases (more on that below), but if we didn't do this then parallel query would be extremely prone to self-deadlock. For example, a parallel query against a relation on which the leader already had @@ -638,23 +638,15 @@ parallelism from a point in the code at which it had some backend-private state that made table access from another process unsafe, for example after calling SetReindexProcessing and before calling ResetReindexProcessing, -catastrophe could ensue, because the worker won't have that state. - -To allow parallel inserts and parallel copy, we have ensured that relation -extension and page locks don't participate in group locking which means such -locks can conflict among the same group members. This is required as it is no -safer for two related processes to extend the same relation or perform clean up -in gin indexes at a time than for unrelated processes to do the same. We don't -acquire a heavyweight lock on any other object after relation extension lock -which means such a lock can never participate in the deadlock cycle. After -acquiring page locks, we can acquire relation extension lock but reverse never -happens, so those will also not participate in deadlock. To allow for other -parallel writes like parallel update or parallel delete, we'll either need to -(1) further enhance the deadlock detector to handle those tuple locks in a -different way than other types; or (2) have parallel workers use some other -mutual exclusion method for such cases. Currently, the parallel mode is -strictly read-only, but now we have the infrastructure to allow parallel -inserts and parallel copy. +catastrophe could ensue, because the worker won't have that state. Similarly, +problems could occur with certain kinds of non-relation locks, such as +GIN page locks. It's no safer for two related processes to perform GIN clean +up at the same time than for unrelated processes to do the same. +However, since parallel mode is strictly read-only at present, neither this +nor most of the similar cases can arise at present. To allow parallel writes, +we'll either need to (1) further enhance the deadlock detector to handle those +types of locks in a different way than other types; or (2) have parallel +workers use some other mutual exclusion method for such cases. Group locking adds three new members to each PGPROC: lockGroupLeader, lockGroupMembers, and lockGroupLink. A PGPROC's lockGroupLeader is NULL for diff -Nru postgresql-13-13.11/src/backend/storage/lmgr/deadlock.c postgresql-13-13.12/src/backend/storage/lmgr/deadlock.c --- postgresql-13-13.11/src/backend/storage/lmgr/deadlock.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/lmgr/deadlock.c 2023-08-07 20:11:34.000000000 +0000 @@ -556,12 +556,11 @@ lm; /* - * The relation extension or page lock can never participate in actual - * deadlock cycle. See Asserts in LockAcquireExtended. So, there is no - * advantage in checking wait edges from them. + * The relation extension lock can never participate in actual deadlock + * cycle. See Assert in LockAcquireExtended. So, there is no advantage + * in checking wait edges from it. */ - if (LOCK_LOCKTAG(*lock) == LOCKTAG_RELATION_EXTEND || - (LOCK_LOCKTAG(*lock) == LOCKTAG_PAGE)) + if (LOCK_LOCKTAG(*lock) == LOCKTAG_RELATION_EXTEND) return false; lockMethodTable = GetLocksMethodTable(lock); diff -Nru postgresql-13-13.11/src/backend/storage/lmgr/lock.c postgresql-13-13.12/src/backend/storage/lmgr/lock.c --- postgresql-13-13.11/src/backend/storage/lmgr/lock.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/lmgr/lock.c 2023-08-07 20:11:34.000000000 +0000 @@ -185,18 +185,6 @@ */ static bool IsRelationExtensionLockHeld PG_USED_FOR_ASSERTS_ONLY = false; -/* - * Flag to indicate if the page lock is held by this backend. We don't - * acquire any other heavyweight lock while holding the page lock except for - * relation extension. However, these locks are never taken in reverse order - * which implies that page locks will also never participate in the deadlock - * cycle. - * - * Similar to relation extension, page locks are also held for a short - * duration, so imposing such a restriction won't hurt. - */ -static bool IsPageLockHeld PG_USED_FOR_ASSERTS_ONLY = false; - /* Macros for manipulating proc->fpLockBits */ #define FAST_PATH_BITS_PER_SLOT 3 #define FAST_PATH_LOCKNUMBER_OFFSET 1 @@ -887,13 +875,6 @@ Assert(!IsRelationExtensionLockHeld); /* - * We don't acquire any other heavyweight lock while holding the page lock - * except for relation extension. - */ - Assert(!IsPageLockHeld || - (locktag->locktag_type == LOCKTAG_RELATION_EXTEND)); - - /* * Prepare to emit a WAL record if acquisition of this lock needs to be * replayed in a standby server. * @@ -1341,10 +1322,10 @@ } /* - * Check and set/reset the flag that we hold the relation extension/page lock. + * Check and set/reset the flag that we hold the relation extension lock. * * It is callers responsibility that this function is called after - * acquiring/releasing the relation extension/page lock. + * acquiring/releasing the relation extension lock. * * Pass acquired as true if lock is acquired, false otherwise. */ @@ -1354,9 +1335,6 @@ #ifdef USE_ASSERT_CHECKING if (LOCALLOCK_LOCKTAG(*locallock) == LOCKTAG_RELATION_EXTEND) IsRelationExtensionLockHeld = acquired; - else if (LOCALLOCK_LOCKTAG(*locallock) == LOCKTAG_PAGE) - IsPageLockHeld = acquired; - #endif } @@ -1482,11 +1460,9 @@ } /* - * The relation extension or page lock conflict even between the group - * members. + * The relation extension lock conflict even between the group members. */ - if (LOCK_LOCKTAG(*lock) == LOCKTAG_RELATION_EXTEND || - (LOCK_LOCKTAG(*lock) == LOCKTAG_PAGE)) + if (LOCK_LOCKTAG(*lock) == LOCKTAG_RELATION_EXTEND) { PROCLOCK_PRINT("LockCheckConflicts: conflicting (group)", proclock); diff -Nru postgresql-13-13.11/src/backend/storage/lmgr/proc.c postgresql-13-13.12/src/backend/storage/lmgr/proc.c --- postgresql-13-13.11/src/backend/storage/lmgr/proc.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/lmgr/proc.c 2023-08-07 20:11:34.000000000 +0000 @@ -396,7 +396,8 @@ MyProc->roleId = InvalidOid; MyProc->tempNamespaceId = InvalidOid; MyProc->isBackgroundWorker = IsBackgroundWorker; - MyProc->delayChkpt = 0; + MyProc->delayChkpt = false; + MyProc->delayChkptEnd = false; MyPgXact->vacuumFlags = 0; /* NB -- autovac launcher intentionally does not set IS_AUTOVACUUM */ if (IsAutoVacuumWorkerProcess()) @@ -578,7 +579,8 @@ MyProc->roleId = InvalidOid; MyProc->tempNamespaceId = InvalidOid; MyProc->isBackgroundWorker = IsBackgroundWorker; - MyProc->delayChkpt = 0; + MyProc->delayChkpt = false; + MyProc->delayChkptEnd = false; MyPgXact->vacuumFlags = 0; MyProc->lwWaiting = false; MyProc->lwWaitMode = 0; @@ -1078,12 +1080,12 @@ /* * If group locking is in use, locks held by members of my locking group * need to be included in myHeldLocks. This is not required for relation - * extension or page locks which conflict among group members. However, - * including them in myHeldLocks will give group members the priority to - * get those locks as compared to other backends which are also trying to - * acquire those locks. OTOH, we can avoid giving priority to group - * members for that kind of locks, but there doesn't appear to be a clear - * advantage of the same. + * extension lock which conflict among group members. However, including + * them in myHeldLocks will give group members the priority to get those + * locks as compared to other backends which are also trying to acquire + * those locks. OTOH, we can avoid giving priority to group members for + * that kind of locks, but there doesn't appear to be a clear advantage of + * the same. */ if (leader != NULL) { diff -Nru postgresql-13-13.11/src/backend/storage/smgr/md.c postgresql-13-13.12/src/backend/storage/smgr/md.c --- postgresql-13-13.11/src/backend/storage/smgr/md.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/storage/smgr/md.c 2023-08-07 20:11:34.000000000 +0000 @@ -225,6 +225,9 @@ mdfd = &reln->md_seg_fds[forkNum][0]; mdfd->mdfd_vfd = fd; mdfd->mdfd_segno = 0; + + if (!SmgrIsTemp(reln)) + register_dirty_segment(reln, forkNum, mdfd); } /* diff -Nru postgresql-13-13.11/src/backend/tcop/postgres.c postgresql-13-13.12/src/backend/tcop/postgres.c --- postgresql-13-13.11/src/backend/tcop/postgres.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/tcop/postgres.c 2023-08-07 20:11:34.000000000 +0000 @@ -3823,11 +3823,11 @@ const char *dbname, const char *username) { - int firstchar; - StringInfoData input_message; sigjmp_buf local_sigjmp_buf; + + /* these must be volatile to ensure state is preserved across longjmp: */ volatile bool send_ready_for_query = true; - bool disable_idle_in_transaction_timeout = false; + volatile bool disable_idle_in_transaction_timeout = false; /* Initialize startup process environment if necessary. */ if (!IsUnderPostmaster) @@ -4111,8 +4111,9 @@ * query cancels from being misreported as timeouts in case we're * forgetting a timeout cancel. */ - disable_all_timeouts(false); - QueryCancelPending = false; /* second to avoid race condition */ + disable_all_timeouts(false); /* do first to avoid race condition */ + QueryCancelPending = false; + disable_idle_in_transaction_timeout = false; /* Not reading from the client anymore. */ DoingCommandRead = false; @@ -4201,6 +4202,9 @@ for (;;) { + int firstchar; + StringInfoData input_message; + /* * At top of loop, reset extended-query-message flag, so that any * errors encountered in "idle" state don't provoke skip. diff -Nru postgresql-13-13.11/src/backend/tsearch/wparser_def.c postgresql-13-13.12/src/backend/tsearch/wparser_def.c --- postgresql-13-13.11/src/backend/tsearch/wparser_def.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/tsearch/wparser_def.c 2023-08-07 20:11:34.000000000 +0000 @@ -18,6 +18,7 @@ #include "catalog/pg_collation.h" #include "commands/defrem.h" +#include "miscadmin.h" #include "tsearch/ts_locale.h" #include "tsearch/ts_public.h" #include "tsearch/ts_type.h" @@ -639,6 +640,12 @@ tmpprs->wanthost = true; + /* + * Check stack depth before recursing. (Since TParserGet() doesn't + * normally recurse, we put the cost of checking here not there.) + */ + check_stack_depth(); + if (TParserGet(tmpprs) && tmpprs->type == HOST) { prs->state->posbyte += tmpprs->lenbytetoken; @@ -662,6 +669,12 @@ tmpprs->state = newTParserPosition(tmpprs->state); tmpprs->state->state = TPS_InURLPathFirst; + /* + * Check stack depth before recursing. (Since TParserGet() doesn't + * normally recurse, we put the cost of checking here not there.) + */ + check_stack_depth(); + if (TParserGet(tmpprs) && tmpprs->type == URLPATH) { prs->state->posbyte += tmpprs->lenbytetoken; @@ -1705,6 +1718,8 @@ { const TParserStateActionItem *item = NULL; + CHECK_FOR_INTERRUPTS(); + Assert(prs->state); if (prs->state->posbyte >= prs->lenstr) diff -Nru postgresql-13-13.11/src/backend/utils/adt/jsonpath.c postgresql-13-13.12/src/backend/utils/adt/jsonpath.c --- postgresql-13-13.11/src/backend/utils/adt/jsonpath.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/adt/jsonpath.c 2023-08-07 20:11:34.000000000 +0000 @@ -978,7 +978,8 @@ v->type == jpiDouble || v->type == jpiDatetime || v->type == jpiKeyValue || - v->type == jpiStartsWith); + v->type == jpiStartsWith || + v->type == jpiLikeRegex); if (a) jspInitByBuffer(a, v->base, v->nextPos); diff -Nru postgresql-13-13.11/src/backend/utils/adt/jsonpath_exec.c postgresql-13-13.12/src/backend/utils/adt/jsonpath_exec.c --- postgresql-13-13.11/src/backend/utils/adt/jsonpath_exec.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/adt/jsonpath_exec.c 2023-08-07 20:11:34.000000000 +0000 @@ -1842,20 +1842,29 @@ * According to SQL/JSON standard enumerate ISO formats for: date, * timetz, time, timestamptz, timestamp. * - * We also support ISO 8601 for timestamps, because to_json[b]() - * functions use this format. + * We also support ISO 8601 format (with "T") for timestamps, because + * to_json[b]() functions use this format. */ static const char *fmt_str[] = { - "yyyy-mm-dd", + "yyyy-mm-dd", /* date */ + "HH24:MI:SS.USTZH:TZM", /* timetz */ + "HH24:MI:SS.USTZH", "HH24:MI:SSTZH:TZM", "HH24:MI:SSTZH", + "HH24:MI:SS.US", /* time without tz */ "HH24:MI:SS", + "yyyy-mm-dd HH24:MI:SS.USTZH:TZM", /* timestamptz */ + "yyyy-mm-dd HH24:MI:SS.USTZH", "yyyy-mm-dd HH24:MI:SSTZH:TZM", "yyyy-mm-dd HH24:MI:SSTZH", - "yyyy-mm-dd HH24:MI:SS", + "yyyy-mm-dd\"T\"HH24:MI:SS.USTZH:TZM", + "yyyy-mm-dd\"T\"HH24:MI:SS.USTZH", "yyyy-mm-dd\"T\"HH24:MI:SSTZH:TZM", "yyyy-mm-dd\"T\"HH24:MI:SSTZH", + "yyyy-mm-dd HH24:MI:SS.US", /* timestamp without tz */ + "yyyy-mm-dd HH24:MI:SS", + "yyyy-mm-dd\"T\"HH24:MI:SS.US", "yyyy-mm-dd\"T\"HH24:MI:SS" }; diff -Nru postgresql-13-13.11/src/backend/utils/cache/plancache.c postgresql-13-13.12/src/backend/utils/cache/plancache.c --- postgresql-13-13.11/src/backend/utils/cache/plancache.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/cache/plancache.c 2023-08-07 20:11:34.000000000 +0000 @@ -78,9 +78,11 @@ /* * We must skip "overhead" operations that involve database access when the * cached plan's subject statement is a transaction control command. + * For the convenience of postgres.c, treat empty statements as control + * commands too. */ #define IsTransactionStmtPlan(plansource) \ - ((plansource)->raw_parse_tree && \ + ((plansource)->raw_parse_tree == NULL || \ IsA((plansource)->raw_parse_tree->stmt, TransactionStmt)) /* @@ -1434,7 +1436,9 @@ * that here we *do* check plansource->is_valid, so as to force plan * rebuild if that's become false. */ - if (!plansource->is_valid || plan != plansource->gplan || !plan->is_valid) + if (!plansource->is_valid || + plan == NULL || plan != plansource->gplan || + !plan->is_valid) return false; Assert(plan->magic == CACHEDPLAN_MAGIC); diff -Nru postgresql-13-13.11/src/backend/utils/cache/relcache.c postgresql-13-13.12/src/backend/utils/cache/relcache.c --- postgresql-13-13.11/src/backend/utils/cache/relcache.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/cache/relcache.c 2023-08-07 20:11:34.000000000 +0000 @@ -2318,6 +2318,7 @@ relation->rd_index->indcheckxmin = index->indcheckxmin; relation->rd_index->indisready = index->indisready; relation->rd_index->indislive = index->indislive; + relation->rd_index->indisreplident = index->indisreplident; /* Copy xmin too, as that is needed to make sense of indcheckxmin */ HeapTupleHeaderSetXmin(relation->rd_indextuple->t_data, diff -Nru postgresql-13-13.11/src/backend/utils/init/postinit.c postgresql-13-13.12/src/backend/utils/init/postinit.c --- postgresql-13-13.11/src/backend/utils/init/postinit.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/init/postinit.c 2023-08-07 20:11:34.000000000 +0000 @@ -972,6 +972,7 @@ if (!bootstrap) { HeapTuple tuple; + Form_pg_database datform; tuple = GetDatabaseTuple(dbname); if (!HeapTupleIsValid(tuple) || @@ -981,6 +982,15 @@ (errcode(ERRCODE_UNDEFINED_DATABASE), errmsg("database \"%s\" does not exist", dbname), errdetail("It seems to have just been dropped or renamed."))); + + datform = (Form_pg_database) GETSTRUCT(tuple); + if (database_is_invalid_form(datform)) + { + ereport(FATAL, + errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), + errmsg("cannot connect to invalid database \"%s\"", dbname), + errhint("Use DROP DATABASE to drop invalid databases.")); + } } /* diff -Nru postgresql-13-13.11/src/backend/utils/mmgr/dsa.c postgresql-13-13.12/src/backend/utils/mmgr/dsa.c --- postgresql-13-13.11/src/backend/utils/mmgr/dsa.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/backend/utils/mmgr/dsa.c 2023-08-07 20:11:34.000000000 +0000 @@ -406,6 +406,7 @@ dsa_handle handle); static void check_for_freed_segments(dsa_area *area); static void check_for_freed_segments_locked(dsa_area *area); +static void rebin_segment(dsa_area *area, dsa_segment_map *segment_map); /* * Create a new shared area in a new DSM segment. Further DSM segments will @@ -857,7 +858,11 @@ FreePageManagerPut(segment_map->fpm, DSA_EXTRACT_OFFSET(span->start) / FPM_PAGE_SIZE, span->npages); + + /* Move segment to appropriate bin if necessary. */ + rebin_segment(area, segment_map); LWLockRelease(DSA_AREA_LOCK(area)); + /* Unlink span. */ LWLockAcquire(DSA_SCLASS_LOCK(area, DSA_SCLASS_SPAN_LARGE), LW_EXCLUSIVE); @@ -1849,6 +1854,11 @@ segment_map->mapped_address = NULL; } } + + /* Move segment to appropriate bin if necessary. */ + if (segment_map->header != NULL) + rebin_segment(area, segment_map); + LWLockRelease(DSA_AREA_LOCK(area)); /* @@ -2012,28 +2022,7 @@ /* Re-bin it if it's no longer in the appropriate bin. */ if (contiguous_pages < threshold) { - size_t new_bin; - - new_bin = contiguous_pages_to_segment_bin(contiguous_pages); - - /* Remove it from its current bin. */ - unlink_segment(area, segment_map); - - /* Push it onto the front of its new bin. */ - segment_map->header->prev = DSA_SEGMENT_INDEX_NONE; - segment_map->header->next = - area->control->segment_bins[new_bin]; - segment_map->header->bin = new_bin; - area->control->segment_bins[new_bin] = segment_index; - if (segment_map->header->next != DSA_SEGMENT_INDEX_NONE) - { - dsa_segment_map *next; - - next = get_segment_by_index(area, - segment_map->header->next); - Assert(next->header->bin == new_bin); - next->header->prev = segment_index; - } + rebin_segment(area, segment_map); /* * But fall through to see if it's enough to satisfy this @@ -2288,3 +2277,35 @@ area->freed_segment_counter = freed_segment_counter; } } + +/* + * Re-bin segment if it's no longer in the appropriate bin. + */ +static void +rebin_segment(dsa_area *area, dsa_segment_map *segment_map) +{ + size_t new_bin; + dsa_segment_index segment_index; + + new_bin = contiguous_pages_to_segment_bin(fpm_largest(segment_map->fpm)); + if (segment_map->header->bin == new_bin) + return; + + /* Remove it from its current bin. */ + unlink_segment(area, segment_map); + + /* Push it onto the front of its new bin. */ + segment_index = get_segment_index(area, segment_map); + segment_map->header->prev = DSA_SEGMENT_INDEX_NONE; + segment_map->header->next = area->control->segment_bins[new_bin]; + segment_map->header->bin = new_bin; + area->control->segment_bins[new_bin] = segment_index; + if (segment_map->header->next != DSA_SEGMENT_INDEX_NONE) + { + dsa_segment_map *next; + + next = get_segment_by_index(area, segment_map->header->next); + Assert(next->header->bin == new_bin); + next->header->prev = segment_index; + } +} diff -Nru postgresql-13-13.11/src/bin/pg_basebackup/t/010_pg_basebackup.pl postgresql-13-13.12/src/bin/pg_basebackup/t/010_pg_basebackup.pl --- postgresql-13-13.11/src/bin/pg_basebackup/t/010_pg_basebackup.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/pg_basebackup/t/010_pg_basebackup.pl 2023-08-07 20:11:34.000000000 +0000 @@ -199,17 +199,23 @@ [ 'pg_basebackup', '-D', "$tempdir/backup_foo", '-Fp', "-Tfoo" ], '-T with invalid format fails'); -# Tar format doesn't support filenames longer than 100 bytes. my $superlongname = "superlongname_" . ("x" x 100); -my $superlongpath = "$pgdata/$superlongname"; +# Tar format doesn't support filenames longer than 100 bytes. +SKIP: +{ + my $superlongpath = "$pgdata/$superlongname"; + + skip "File path too long", 1 + if $windows_os && length($superlongpath) > 255; -open my $file, '>', "$superlongpath" - or die "unable to create file $superlongpath"; -close $file; -$node->command_fails( - [ 'pg_basebackup', '-D', "$tempdir/tarbackup_l1", '-Ft' ], - 'pg_basebackup tar with long name fails'); -unlink "$pgdata/$superlongname"; + open my $file, '>', "$superlongpath" + or die "unable to create file $superlongpath"; + close $file; + $node->command_fails( + [ 'pg_basebackup', '-D', "$tempdir/tarbackup_l1", '-Ft' ], + 'pg_basebackup tar with long name fails'); + unlink "$superlongpath"; +} # The following tests test symlinks. Windows doesn't have symlinks, so # skip on Windows. diff -Nru postgresql-13-13.11/src/bin/pg_dump/pg_dumpall.c postgresql-13-13.12/src/bin/pg_dump/pg_dumpall.c --- postgresql-13-13.11/src/bin/pg_dump/pg_dumpall.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/pg_dump/pg_dumpall.c 2023-08-07 20:11:34.000000000 +0000 @@ -1320,7 +1320,7 @@ res = executeQuery(conn, "SELECT datname " "FROM pg_database d " - "WHERE datallowconn " + "WHERE datallowconn AND datconnlimit != -2 " "ORDER BY datname"); if (PQntuples(res) > 0) @@ -1473,7 +1473,7 @@ res = executeQuery(conn, "SELECT datname " "FROM pg_database d " - "WHERE datallowconn " + "WHERE datallowconn AND datconnlimit != -2 " "ORDER BY (datname <> 'template1'), datname"); if (PQntuples(res) > 0) diff -Nru postgresql-13-13.11/src/bin/pg_dump/t/002_pg_dump.pl postgresql-13-13.12/src/bin/pg_dump/t/002_pg_dump.pl --- postgresql-13-13.11/src/bin/pg_dump/t/002_pg_dump.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/pg_dump/t/002_pg_dump.pl 2023-08-07 20:11:34.000000000 +0000 @@ -1430,6 +1430,17 @@ }, }, + 'CREATE DATABASE regression_invalid...' => { + create_order => 1, + create_sql => q( + CREATE DATABASE regression_invalid; + UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'), + regexp => qr/^CREATE DATABASE regression_invalid/m, + not_like => { + pg_dumpall_dbprivs => 1, + }, + }, + 'CREATE ACCESS METHOD gist2' => { create_order => 52, create_sql => @@ -3521,7 +3532,7 @@ # Start with number of command_fails_like()*2 tests below (each # command_fails_like is actually 2 tests) -my $num_tests = 12; +my $num_tests = 14; foreach my $run (sort keys %pgdump_runs) { @@ -3650,6 +3661,14 @@ 'connecting to a non-existent database'); ######################################### +# Test connecting to an invalid database + +command_fails_like( + [ 'pg_dump', '-p', "$port", '-d', 'regression_invalid' ], + qr/pg_dump: error: connection to database .* failed: FATAL: cannot connect to invalid database "regression_invalid"/, + 'connecting to an invalid database'); + +######################################### # Test connecting with an unprivileged user command_fails_like( diff -Nru postgresql-13-13.11/src/bin/scripts/clusterdb.c postgresql-13-13.12/src/bin/scripts/clusterdb.c --- postgresql-13-13.11/src/bin/scripts/clusterdb.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/clusterdb.c 2023-08-07 20:11:34.000000000 +0000 @@ -237,7 +237,9 @@ int i; conn = connectMaintenanceDatabase(cparams, progname, echo); - result = executeQuery(conn, "SELECT datname FROM pg_database WHERE datallowconn ORDER BY 1;", echo); + result = executeQuery(conn, + "SELECT datname FROM pg_database WHERE datallowconn AND datconnlimit <> -2 ORDER BY 1;", + echo); PQfinish(conn); for (i = 0; i < PQntuples(result); i++) diff -Nru postgresql-13-13.11/src/bin/scripts/reindexdb.c postgresql-13-13.12/src/bin/scripts/reindexdb.c --- postgresql-13-13.11/src/bin/scripts/reindexdb.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/reindexdb.c 2023-08-07 20:11:34.000000000 +0000 @@ -720,7 +720,9 @@ int i; conn = connectMaintenanceDatabase(cparams, progname, echo); - result = executeQuery(conn, "SELECT datname FROM pg_database WHERE datallowconn ORDER BY 1;", echo); + result = executeQuery(conn, + "SELECT datname FROM pg_database WHERE datallowconn AND datconnlimit <> -2 ORDER BY 1;", + echo); PQfinish(conn); for (i = 0; i < PQntuples(result); i++) diff -Nru postgresql-13-13.11/src/bin/scripts/t/011_clusterdb_all.pl postgresql-13-13.12/src/bin/scripts/t/011_clusterdb_all.pl --- postgresql-13-13.11/src/bin/scripts/t/011_clusterdb_all.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/t/011_clusterdb_all.pl 2023-08-07 20:11:34.000000000 +0000 @@ -3,7 +3,7 @@ use PostgresNode; use TestLib; -use Test::More tests => 2; +use Test::More tests => 4; my $node = get_new_node('main'); $node->init; @@ -17,3 +17,16 @@ [ 'clusterdb', '-a' ], qr/statement: CLUSTER.*statement: CLUSTER/s, 'cluster all databases'); + +$node->safe_psql( + 'postgres', q( + CREATE DATABASE regression_invalid; + UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'; +)); +$node->command_ok([ 'clusterdb', '-a' ], + 'invalid database not targeted by clusterdb -a'); + +# Doesn't quite belong here, but don't want to waste time by creating an +# invalid database in 010_clusterdb.pl as well. +$node->command_fails([ 'clusterdb', '-d', 'regression_invalid'], + 'clusterdb cannot target invalid database'); diff -Nru postgresql-13-13.11/src/bin/scripts/t/050_dropdb.pl postgresql-13-13.12/src/bin/scripts/t/050_dropdb.pl --- postgresql-13-13.11/src/bin/scripts/t/050_dropdb.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/t/050_dropdb.pl 2023-08-07 20:11:34.000000000 +0000 @@ -3,7 +3,7 @@ use PostgresNode; use TestLib; -use Test::More tests => 13; +use Test::More tests => 14; program_help_ok('dropdb'); program_version_ok('dropdb'); @@ -27,3 +27,12 @@ $node->command_fails([ 'dropdb', 'nonexistent' ], 'fails with nonexistent database'); + +# check that invalid database can be dropped with dropdb +$node->safe_psql( + 'postgres', q( + CREATE DATABASE regression_invalid; + UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'; +)); +$node->command_ok([ 'dropdb', 'regression_invalid' ], + 'invalid database can be dropped'); diff -Nru postgresql-13-13.11/src/bin/scripts/t/091_reindexdb_all.pl postgresql-13-13.12/src/bin/scripts/t/091_reindexdb_all.pl --- postgresql-13-13.11/src/bin/scripts/t/091_reindexdb_all.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/t/091_reindexdb_all.pl 2023-08-07 20:11:34.000000000 +0000 @@ -2,7 +2,7 @@ use warnings; use PostgresNode; -use Test::More tests => 2; +use Test::More tests => 4; my $node = get_new_node('main'); $node->init; @@ -14,3 +14,16 @@ [ 'reindexdb', '-a' ], qr/statement: REINDEX.*statement: REINDEX/s, 'reindex all databases'); + +$node->safe_psql( + 'postgres', q( + CREATE DATABASE regression_invalid; + UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'; +)); +$node->command_ok([ 'reindexdb', '-a' ], + 'invalid database not targeted by reindexdb -a'); + +# Doesn't quite belong here, but don't want to waste time by creating an +# invalid database in 090_reindexdb.pl as well. +$node->command_fails([ 'reindexdb', '-d', 'regression_invalid'], + 'reindexdb cannot target invalid database'); diff -Nru postgresql-13-13.11/src/bin/scripts/t/101_vacuumdb_all.pl postgresql-13-13.12/src/bin/scripts/t/101_vacuumdb_all.pl --- postgresql-13-13.11/src/bin/scripts/t/101_vacuumdb_all.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/t/101_vacuumdb_all.pl 2023-08-07 20:11:34.000000000 +0000 @@ -2,7 +2,7 @@ use warnings; use PostgresNode; -use Test::More tests => 2; +use Test::More tests => 4; my $node = get_new_node('main'); $node->init; @@ -12,3 +12,16 @@ [ 'vacuumdb', '-a' ], qr/statement: VACUUM.*statement: VACUUM/s, 'vacuum all databases'); + +$node->safe_psql( + 'postgres', q( + CREATE DATABASE regression_invalid; + UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'; +)); +$node->command_ok([ 'vacuumdb', '-a' ], + 'invalid database not targeted by vacuumdb -a'); + +# Doesn't quite belong here, but don't want to waste time by creating an +# invalid database in 010_vacuumdb.pl as well. +$node->command_fails([ 'vacuumdb', '-d', 'regression_invalid'], + 'vacuumdb cannot target invalid database'); diff -Nru postgresql-13-13.11/src/bin/scripts/vacuumdb.c postgresql-13-13.12/src/bin/scripts/vacuumdb.c --- postgresql-13-13.11/src/bin/scripts/vacuumdb.c 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/bin/scripts/vacuumdb.c 2023-08-07 20:11:34.000000000 +0000 @@ -718,7 +718,7 @@ conn = connectMaintenanceDatabase(cparams, progname, echo); result = executeQuery(conn, - "SELECT datname FROM pg_database WHERE datallowconn ORDER BY 1;", + "SELECT datname FROM pg_database WHERE datallowconn AND datconnlimit <> -2 ORDER BY 1;", echo); PQfinish(conn); diff -Nru postgresql-13-13.11/src/include/access/brin_tuple.h postgresql-13-13.12/src/include/access/brin_tuple.h --- postgresql-13-13.11/src/include/access/brin_tuple.h 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/access/brin_tuple.h 2023-08-07 20:11:34.000000000 +0000 @@ -36,6 +36,7 @@ typedef struct BrinMemTuple { bool bt_placeholder; /* this is a placeholder tuple */ + bool bt_empty_range; /* range represents no tuples */ BlockNumber bt_blkno; /* heap blkno that the tuple is for */ MemoryContext bt_context; /* memcxt holding the bt_columns values */ /* output arrays for brin_deform_tuple: */ @@ -61,7 +62,7 @@ * * 7th (high) bit: has nulls * 6th bit: is placeholder tuple - * 5th bit: unused + * 5th bit: range is empty * 4-0 bit: offset of data * --------------- */ @@ -74,13 +75,14 @@ * bt_info manipulation macros */ #define BRIN_OFFSET_MASK 0x1F -/* bit 0x20 is not used at present */ +#define BRIN_EMPTY_RANGE_MASK 0x20 #define BRIN_PLACEHOLDER_MASK 0x40 #define BRIN_NULLS_MASK 0x80 #define BrinTupleDataOffset(tup) ((Size) (((BrinTuple *) (tup))->bt_info & BRIN_OFFSET_MASK)) #define BrinTupleHasNulls(tup) (((((BrinTuple *) (tup))->bt_info & BRIN_NULLS_MASK)) != 0) #define BrinTupleIsPlaceholder(tup) (((((BrinTuple *) (tup))->bt_info & BRIN_PLACEHOLDER_MASK)) != 0) +#define BrinTupleIsEmptyRange(tup) (((((BrinTuple *) (tup))->bt_info & BRIN_EMPTY_RANGE_MASK)) != 0) extern BrinTuple *brin_form_tuple(BrinDesc *brdesc, BlockNumber blkno, diff -Nru postgresql-13-13.11/src/include/catalog/pg_database.h postgresql-13-13.12/src/include/catalog/pg_database.h --- postgresql-13-13.11/src/include/catalog/pg_database.h 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/catalog/pg_database.h 2023-08-07 20:11:34.000000000 +0000 @@ -52,7 +52,10 @@ /* new connections allowed? */ bool datallowconn; - /* max connections allowed (-1=no limit) */ + /* + * Max connections allowed. Negative values have special meaning, see + * DATCONNLIMIT_* defines below. + */ int32 datconnlimit; /* highest OID to consider a system OID */ @@ -80,4 +83,19 @@ */ typedef FormData_pg_database *Form_pg_database; +/* + * Special values for pg_database.datconnlimit. Normal values are >= 0. + */ +#define DATCONNLIMIT_UNLIMITED -1 /* no limit */ + +/* + * A database is set to invalid partway through being dropped. Using + * datconnlimit=-2 for this purpose isn't particularly clean, but is + * backpatchable. + */ +#define DATCONNLIMIT_INVALID_DB -2 + +extern bool database_is_invalid_form(Form_pg_database datform); +extern bool database_is_invalid_oid(Oid dboid); + #endif /* PG_DATABASE_H */ diff -Nru postgresql-13-13.11/src/include/lib/simplehash.h postgresql-13-13.12/src/include/lib/simplehash.h --- postgresql-13-13.11/src/include/lib/simplehash.h 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/lib/simplehash.h 2023-08-07 20:11:34.000000000 +0000 @@ -840,7 +840,6 @@ SH_SCOPE void SH_START_ITERATE(SH_TYPE * tb, SH_ITERATOR * iter) { - int i; uint64 startelem = PG_UINT64_MAX; /* @@ -848,7 +847,7 @@ * supported, we want to start/end at an element that cannot be affected * by elements being shifted. */ - for (i = 0; i < tb->size; i++) + for (uint32 i = 0; i < tb->size; i++) { SH_ELEMENT_TYPE *entry = &tb->data[i]; @@ -859,6 +858,7 @@ } } + /* we should have found an empty element */ Assert(startelem < SH_MAX_SIZE); /* diff -Nru postgresql-13-13.11/src/include/nodes/pathnodes.h postgresql-13-13.12/src/include/nodes/pathnodes.h --- postgresql-13-13.11/src/include/nodes/pathnodes.h 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/nodes/pathnodes.h 2023-08-07 20:11:34.000000000 +0000 @@ -1353,15 +1353,18 @@ } ForeignPath; /* - * CustomPath represents a table scan done by some out-of-core extension. + * CustomPath represents a table scan or a table join done by some out-of-core + * extension. * * We provide a set of hooks here - which the provider must take care to set * up correctly - to allow extensions to supply their own methods of scanning - * a relation. For example, a provider might provide GPU acceleration, a - * cache-based scan, or some other kind of logic we haven't dreamed up yet. + * a relation or joing relations. For example, a provider might provide GPU + * acceleration, a cache-based scan, or some other kind of logic we haven't + * dreamed up yet. * - * CustomPaths can be injected into the planning process for a relation by - * set_rel_pathlist_hook functions. + * CustomPaths can be injected into the planning process for a base or join + * relation by set_rel_pathlist_hook or set_join_pathlist_hook functions, + * respectively. * * Core code must avoid assuming that the CustomPath is only as large as * the structure declared here; providers are allowed to make it the first diff -Nru postgresql-13-13.11/src/include/optimizer/restrictinfo.h postgresql-13-13.12/src/include/optimizer/restrictinfo.h --- postgresql-13-13.11/src/include/optimizer/restrictinfo.h 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/optimizer/restrictinfo.h 2023-08-07 20:11:34.000000000 +0000 @@ -49,6 +49,8 @@ Relids joinrelids, List **joinquals, List **otherquals); +extern bool has_pseudoconstant_clauses(PlannerInfo *root, + List *restrictinfo_list); extern bool join_clause_is_movable_to(RestrictInfo *rinfo, RelOptInfo *baserel); extern bool join_clause_is_movable_into(RestrictInfo *rinfo, Relids currentrelids, diff -Nru postgresql-13-13.11/src/include/pg_config.h.in postgresql-13-13.12/src/include/pg_config.h.in --- postgresql-13-13.11/src/include/pg_config.h.in 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/include/pg_config.h.in 2023-08-07 20:11:34.000000000 +0000 @@ -758,6 +758,10 @@ /* Define bytes to use libc memset(). */ #undef MEMSET_LOOP_LIMIT +/* Define to the OpenSSL API version in use. This avoids deprecation warnings + from newer OpenSSL versions. */ +#undef OPENSSL_API_COMPAT + /* Define to the address where bug reports for this package should be sent. */ #undef PACKAGE_BUGREPORT diff -Nru postgresql-13-13.11/src/test/isolation/expected/eval-plan-qual.out postgresql-13-13.12/src/test/isolation/expected/eval-plan-qual.out --- postgresql-13-13.11/src/test/isolation/expected/eval-plan-qual.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/isolation/expected/eval-plan-qual.out 2023-08-07 20:11:34.000000000 +0000 @@ -842,6 +842,90 @@ step writep3b: <... completed> step c2: COMMIT; +starting permutation: writep4a writep4b c1 c2 readp +step writep4a: UPDATE p SET c = 4 WHERE c = 0; +step writep4b: UPDATE p SET b = -4 WHERE c = 0; +step c1: COMMIT; +step writep4b: <... completed> +step c2: COMMIT; +step readp: SELECT tableoid::regclass, ctid, * FROM p; +tableoid|ctid |a|b|c +--------+------+-+-+- +c1 |(0,2) |0|0|1 +c1 |(0,3) |0|0|2 +c1 |(0,5) |0|1|1 +c1 |(0,6) |0|1|2 +c1 |(0,8) |0|2|1 +c1 |(0,9) |0|2|2 +c1 |(0,11)|0|0|4 +c1 |(0,12)|0|1|4 +c1 |(0,13)|0|2|4 +c1 |(0,14)|0|3|4 +c2 |(0,2) |1|0|1 +c2 |(0,3) |1|0|2 +c2 |(0,5) |1|1|1 +c2 |(0,6) |1|1|2 +c2 |(0,8) |1|2|1 +c2 |(0,9) |1|2|2 +c2 |(0,11)|1|0|4 +c2 |(0,12)|1|1|4 +c2 |(0,13)|1|2|4 +c2 |(0,14)|1|3|4 +c3 |(0,2) |2|0|1 +c3 |(0,3) |2|0|2 +c3 |(0,5) |2|1|1 +c3 |(0,6) |2|1|2 +c3 |(0,8) |2|2|1 +c3 |(0,9) |2|2|2 +c3 |(0,11)|2|0|4 +c3 |(0,12)|2|1|4 +c3 |(0,13)|2|2|4 +c3 |(0,14)|2|3|4 +(30 rows) + + +starting permutation: writep4a deletep4 c1 c2 readp +step writep4a: UPDATE p SET c = 4 WHERE c = 0; +step deletep4: DELETE FROM p WHERE c = 0; +step c1: COMMIT; +step deletep4: <... completed> +step c2: COMMIT; +step readp: SELECT tableoid::regclass, ctid, * FROM p; +tableoid|ctid |a|b|c +--------+------+-+-+- +c1 |(0,2) |0|0|1 +c1 |(0,3) |0|0|2 +c1 |(0,5) |0|1|1 +c1 |(0,6) |0|1|2 +c1 |(0,8) |0|2|1 +c1 |(0,9) |0|2|2 +c1 |(0,11)|0|0|4 +c1 |(0,12)|0|1|4 +c1 |(0,13)|0|2|4 +c1 |(0,14)|0|3|4 +c2 |(0,2) |1|0|1 +c2 |(0,3) |1|0|2 +c2 |(0,5) |1|1|1 +c2 |(0,6) |1|1|2 +c2 |(0,8) |1|2|1 +c2 |(0,9) |1|2|2 +c2 |(0,11)|1|0|4 +c2 |(0,12)|1|1|4 +c2 |(0,13)|1|2|4 +c2 |(0,14)|1|3|4 +c3 |(0,2) |2|0|1 +c3 |(0,3) |2|0|2 +c3 |(0,5) |2|1|1 +c3 |(0,6) |2|1|2 +c3 |(0,8) |2|2|1 +c3 |(0,9) |2|2|2 +c3 |(0,11)|2|0|4 +c3 |(0,12)|2|1|4 +c3 |(0,13)|2|2|4 +c3 |(0,14)|2|3|4 +(30 rows) + + starting permutation: wx2 partiallock c2 c1 read step wx2: UPDATE accounts SET balance = balance + 450 WHERE accountid = 'checking' RETURNING balance; balance @@ -1104,22 +1188,41 @@ (1 row) +starting permutation: simplepartupdate conditionalpartupdate c1 c2 read_part +step simplepartupdate: + update parttbl set b = b + 10; + +step conditionalpartupdate: + update parttbl set c = -c where b < 10; + +step c1: COMMIT; +step conditionalpartupdate: <... completed> +step c2: COMMIT; +step read_part: SELECT * FROM parttbl ORDER BY a, c; +a| b|c| d +-+--+-+-- +1|11|1|12 +2|12|2|14 +(2 rows) + + starting permutation: simplepartupdate complexpartupdate c1 c2 read_part step simplepartupdate: update parttbl set b = b + 10; step complexpartupdate: with u as (update parttbl set b = b + 1 returning parttbl.*) - update parttbl set b = u.b + 100 from u; + update parttbl p set b = u.b + 100 from u where p.a = u.a; step c1: COMMIT; step complexpartupdate: <... completed> step c2: COMMIT; -step read_part: SELECT * FROM parttbl ORDER BY a; +step read_part: SELECT * FROM parttbl ORDER BY a, c; a| b|c| d -+--+-+-- 1|12|1|13 -(1 row) +2|13|2|15 +(2 rows) starting permutation: simplepartupdate_route1to2 complexpartupdate_route_err1 c1 c2 read_part @@ -1139,11 +1242,12 @@ step complexpartupdate_route_err1: <... completed> ERROR: tuple to be locked was already moved to another partition due to concurrent update step c2: COMMIT; -step read_part: SELECT * FROM parttbl ORDER BY a; +step read_part: SELECT * FROM parttbl ORDER BY a, c; a|b|c|d -+-+-+- 2|1|1|3 -(1 row) +2|2|2|4 +(2 rows) starting permutation: simplepartupdate_noroute complexpartupdate_route c1 c2 read_part @@ -1167,11 +1271,12 @@ (1 row) step c2: COMMIT; -step read_part: SELECT * FROM parttbl ORDER BY a; +step read_part: SELECT * FROM parttbl ORDER BY a, c; a|b|c|d -+-+-+- 2|2|1|4 -(1 row) +2|2|2|4 +(2 rows) starting permutation: simplepartupdate_noroute complexpartupdate_doesnt_route c1 c2 read_part @@ -1195,9 +1300,10 @@ (1 row) step c2: COMMIT; -step read_part: SELECT * FROM parttbl ORDER BY a; +step read_part: SELECT * FROM parttbl ORDER BY a, c; a|b|c|d -+-+-+- 1|2|1|3 -(1 row) +2|2|2|4 +(2 rows) diff -Nru postgresql-13-13.11/src/test/isolation/specs/eval-plan-qual.spec postgresql-13-13.12/src/test/isolation/specs/eval-plan-qual.spec --- postgresql-13-13.11/src/test/isolation/specs/eval-plan-qual.spec 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/isolation/specs/eval-plan-qual.spec 2023-08-07 20:11:34.000000000 +0000 @@ -38,7 +38,7 @@ d int GENERATED ALWAYS AS (a + b) STORED) PARTITION BY LIST (a); CREATE TABLE parttbl1 PARTITION OF parttbl FOR VALUES IN (1); CREATE TABLE parttbl2 PARTITION OF parttbl FOR VALUES IN (2); - INSERT INTO parttbl VALUES (1, 1, 1); + INSERT INTO parttbl VALUES (1, 1, 1), (2, 2, 2); CREATE TABLE another_parttbl (a int, b int, c int) PARTITION BY LIST (a); CREATE TABLE another_parttbl1 PARTITION OF another_parttbl FOR VALUES IN (1); @@ -100,11 +100,15 @@ # when the first updated tuple was in a non-first child table. # writep2/returningp1 tests a memory allocation issue # writep3a/writep3b tests updates touching more than one table +# writep4a/writep4b tests a case where matches in another table confused EPQ +# writep4a/deletep4 tests the same case in the DELETE path +step readp { SELECT tableoid::regclass, ctid, * FROM p; } step readp1 { SELECT tableoid::regclass, ctid, * FROM p WHERE b IN (0, 1) AND c = 0 FOR UPDATE; } step writep1 { UPDATE p SET b = -1 WHERE a = 1 AND b = 1 AND c = 0; } step writep2 { UPDATE p SET b = -b WHERE a = 1 AND c = 0; } step writep3a { UPDATE p SET b = -b WHERE c = 0; } +step writep4a { UPDATE p SET c = 4 WHERE c = 0; } step c1 { COMMIT; } step r1 { ROLLBACK; } @@ -208,6 +212,8 @@ SELECT * FROM u; } step writep3b { UPDATE p SET b = -b WHERE c = 0; } +step writep4b { UPDATE p SET b = -4 WHERE c = 0; } +step deletep4 { DELETE FROM p WHERE c = 0; } step readforss { SELECT ta.id AS ta_id, ta.value AS ta_value, (SELECT ROW(tb.id, tb.value) @@ -224,9 +230,14 @@ } step wrtwcte { UPDATE table_a SET value = 'tableAValue2' WHERE id = 1; } step wrjt { UPDATE jointest SET data = 42 WHERE id = 7; } + +step conditionalpartupdate { + update parttbl set c = -c where b < 10; +} + step complexpartupdate { with u as (update parttbl set b = b + 1 returning parttbl.*) - update parttbl set b = u.b + 100 from u; + update parttbl p set b = u.b + 100 from u where p.a = u.a; } step complexpartupdate_route_err1 { @@ -275,7 +286,7 @@ step read { SELECT * FROM accounts ORDER BY accountid; } step read_ext { SELECT * FROM accounts_ext ORDER BY accountid; } step read_a { SELECT * FROM table_a ORDER BY id; } -step read_part { SELECT * FROM parttbl ORDER BY a; } +step read_part { SELECT * FROM parttbl ORDER BY a, c; } # this test exercises EvalPlanQual with a CTE, cf bug #14328 step readwcte { @@ -345,6 +356,8 @@ permutation readp1 writep1 readp2 c1 c2 permutation writep2 returningp1 c1 c2 permutation writep3a writep3b c1 c2 +permutation writep4a writep4b c1 c2 readp +permutation writep4a deletep4 c1 c2 readp permutation wx2 partiallock c2 c1 read permutation wx2 lockwithvalues c2 c1 read permutation wx2_ext partiallock_ext c2 c1 read_ext @@ -356,6 +369,7 @@ permutation wrjt selectresultforupdate c2 c1 permutation wrtwcte multireadwcte c1 c2 +permutation simplepartupdate conditionalpartupdate c1 c2 read_part permutation simplepartupdate complexpartupdate c1 c2 read_part permutation simplepartupdate_route1to2 complexpartupdate_route_err1 c1 c2 read_part permutation simplepartupdate_noroute complexpartupdate_route c1 c2 read_part diff -Nru postgresql-13-13.11/src/test/kerberos/t/001_auth.pl postgresql-13-13.12/src/test/kerberos/t/001_auth.pl --- postgresql-13-13.11/src/test/kerberos/t/001_auth.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/kerberos/t/001_auth.pl 2023-08-07 20:11:34.000000000 +0000 @@ -28,8 +28,15 @@ my ($krb5_bin_dir, $krb5_sbin_dir); -if ($^O eq 'darwin') +if ($^O eq 'darwin' && -d "/opt/homebrew" ) { + # typical paths for Homebrew on ARM + $krb5_bin_dir = '/opt/homebrew/opt/krb5/bin'; + $krb5_sbin_dir = '/opt/homebrew/opt/krb5/sbin'; +} +elsif ($^O eq 'darwin') +{ + # typical paths for Homebrew on Intel $krb5_bin_dir = '/usr/local/opt/krb5/bin'; $krb5_sbin_dir = '/usr/local/opt/krb5/sbin'; } diff -Nru postgresql-13-13.11/src/test/ldap/t/001_auth.pl postgresql-13-13.12/src/test/ldap/t/001_auth.pl --- postgresql-13-13.11/src/test/ldap/t/001_auth.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/ldap/t/001_auth.pl 2023-08-07 20:11:34.000000000 +0000 @@ -17,9 +17,15 @@ $ldap_bin_dir = undef; # usually in PATH -if ($^O eq 'darwin' && -d '/usr/local/opt/openldap') +if ($^O eq 'darwin' && -d '/opt/homebrew/opt/openldap') { - # typical paths for Homebrew + # typical paths for Homebrew on ARM + $slapd = '/opt/homebrew/opt/openldap/libexec/slapd'; + $ldap_schema_dir = '/opt/homebrew/etc/openldap/schema'; +} +elsif ($^O eq 'darwin' && -d '/usr/local/opt/openldap') +{ + # typical paths for Homebrew on Intel $slapd = '/usr/local/opt/openldap/libexec/slapd'; $ldap_schema_dir = '/usr/local/etc/openldap/schema'; } diff -Nru postgresql-13-13.11/src/test/modules/brin/expected/summarization-and-inprogress-insertion.out postgresql-13-13.12/src/test/modules/brin/expected/summarization-and-inprogress-insertion.out --- postgresql-13-13.11/src/test/modules/brin/expected/summarization-and-inprogress-insertion.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/brin/expected/summarization-and-inprogress-insertion.out 2023-08-07 20:11:34.000000000 +0000 @@ -4,7 +4,7 @@ step s2check: SELECT * FROM brin_page_items(get_raw_page('brinidx', 2), 'brinidx'::regclass); itemoffset|blknum|attnum|allnulls|hasnulls|placeholder|value ----------+------+------+--------+--------+-----------+-------- - 1| 0| 1|f |f |f |{1 .. 1} + 1| 0| 1|f |t |f |{1 .. 1} (1 row) step s1b: BEGIN ISOLATION LEVEL REPEATABLE READ; @@ -26,7 +26,7 @@ step s2check: SELECT * FROM brin_page_items(get_raw_page('brinidx', 2), 'brinidx'::regclass); itemoffset|blknum|attnum|allnulls|hasnulls|placeholder|value ----------+------+------+--------+--------+-----------+----------- - 1| 0| 1|f |f |f |{1 .. 1} + 1| 0| 1|f |t |f |{1 .. 1} 2| 1| 1|f |f |f |{1 .. 1000} (2 rows) @@ -35,7 +35,7 @@ step s2check: SELECT * FROM brin_page_items(get_raw_page('brinidx', 2), 'brinidx'::regclass); itemoffset|blknum|attnum|allnulls|hasnulls|placeholder|value ----------+------+------+--------+--------+-----------+-------- - 1| 0| 1|f |f |f |{1 .. 1} + 1| 0| 1|f |t |f |{1 .. 1} (1 row) step s1b: BEGIN ISOLATION LEVEL REPEATABLE READ; @@ -45,7 +45,7 @@ step s2check: SELECT * FROM brin_page_items(get_raw_page('brinidx', 2), 'brinidx'::regclass); itemoffset|blknum|attnum|allnulls|hasnulls|placeholder|value ----------+------+------+--------+--------+-----------+----------- - 1| 0| 1|f |f |f |{1 .. 1} + 1| 0| 1|f |t |f |{1 .. 1} 2| 1| 1|f |f |f |{1 .. 1000} (2 rows) diff -Nru postgresql-13-13.11/src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec postgresql-13-13.12/src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec --- postgresql-13-13.11/src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/brin/specs/summarization-and-inprogress-insertion.spec 2023-08-07 20:11:34.000000000 +0000 @@ -9,6 +9,7 @@ ) WITH (fillfactor=10); CREATE INDEX brinidx ON brin_iso USING brin (value) WITH (pages_per_range=1); -- this fills the first page + INSERT INTO brin_iso VALUES (NULL); DO $$ DECLARE curtid tid; BEGIN diff -Nru postgresql-13-13.11/src/test/modules/test_extensions/Makefile postgresql-13-13.12/src/test/modules/test_extensions/Makefile --- postgresql-13-13.11/src/test/modules/test_extensions/Makefile 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/test_extensions/Makefile 2023-08-07 20:11:34.000000000 +0000 @@ -6,6 +6,7 @@ EXTENSION = test_ext1 test_ext2 test_ext3 test_ext4 test_ext5 test_ext6 \ test_ext7 test_ext8 test_ext_cine test_ext_cor \ test_ext_cyclic1 test_ext_cyclic2 \ + test_ext_extschema \ test_ext_evttrig DATA = test_ext1--1.0.sql test_ext2--1.0.sql test_ext3--1.0.sql \ test_ext4--1.0.sql test_ext5--1.0.sql test_ext6--1.0.sql \ @@ -13,6 +14,7 @@ test_ext_cine--1.0.sql test_ext_cine--1.0--1.1.sql \ test_ext_cor--1.0.sql \ test_ext_cyclic1--1.0.sql test_ext_cyclic2--1.0.sql \ + test_ext_extschema--1.0.sql \ test_ext_evttrig--1.0.sql test_ext_evttrig--1.0--2.0.sql REGRESS = test_extensions test_extdepend diff -Nru postgresql-13-13.11/src/test/modules/test_extensions/expected/test_extensions.out postgresql-13-13.12/src/test/modules/test_extensions/expected/test_extensions.out --- postgresql-13-13.11/src/test/modules/test_extensions/expected/test_extensions.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/test_extensions/expected/test_extensions.out 2023-08-07 20:11:34.000000000 +0000 @@ -1,3 +1,4 @@ +CREATE SCHEMA has$dollar; -- test some errors CREATE EXTENSION test_ext1; ERROR: required extension "test_ext2" is not installed @@ -6,35 +7,35 @@ ERROR: schema "test_ext1" does not exist CREATE EXTENSION test_ext1 SCHEMA test_ext; ERROR: schema "test_ext" does not exist -CREATE SCHEMA test_ext; -CREATE EXTENSION test_ext1 SCHEMA test_ext; +CREATE EXTENSION test_ext1 SCHEMA has$dollar; ERROR: extension "test_ext1" must be installed in schema "test_ext1" -- finally success -CREATE EXTENSION test_ext1 SCHEMA test_ext CASCADE; +CREATE EXTENSION test_ext1 SCHEMA has$dollar CASCADE; NOTICE: installing required extension "test_ext2" NOTICE: installing required extension "test_ext3" NOTICE: installing required extension "test_ext5" NOTICE: installing required extension "test_ext4" SELECT extname, nspname, extversion, extrelocatable FROM pg_extension e, pg_namespace n WHERE extname LIKE 'test_ext%' AND e.extnamespace = n.oid ORDER BY 1; - extname | nspname | extversion | extrelocatable ------------+-----------+------------+---------------- - test_ext1 | test_ext1 | 1.0 | f - test_ext2 | test_ext | 1.0 | t - test_ext3 | test_ext | 1.0 | t - test_ext4 | test_ext | 1.0 | t - test_ext5 | test_ext | 1.0 | t + extname | nspname | extversion | extrelocatable +-----------+------------+------------+---------------- + test_ext1 | test_ext1 | 1.0 | f + test_ext2 | has$dollar | 1.0 | t + test_ext3 | has$dollar | 1.0 | t + test_ext4 | has$dollar | 1.0 | t + test_ext5 | has$dollar | 1.0 | t (5 rows) CREATE EXTENSION test_ext_cyclic1 CASCADE; NOTICE: installing required extension "test_ext_cyclic2" ERROR: cyclic dependency detected between extensions "test_ext_cyclic1" and "test_ext_cyclic2" -DROP SCHEMA test_ext CASCADE; +DROP SCHEMA has$dollar CASCADE; NOTICE: drop cascades to 5 other objects DETAIL: drop cascades to extension test_ext3 drop cascades to extension test_ext5 drop cascades to extension test_ext2 drop cascades to extension test_ext4 drop cascades to extension test_ext1 +CREATE SCHEMA has$dollar; CREATE EXTENSION test_ext6; DROP EXTENSION test_ext6; CREATE EXTENSION test_ext6; @@ -312,3 +313,10 @@ table ext_cine_tab3 (9 rows) +-- +-- Test @extschema@ syntax. +-- +CREATE SCHEMA "has space"; +CREATE EXTENSION test_ext_extschema SCHEMA has$dollar; +ERROR: invalid character in extension "test_ext_extschema" schema: must not contain any of ""$'\" +CREATE EXTENSION test_ext_extschema SCHEMA "has space"; diff -Nru postgresql-13-13.11/src/test/modules/test_extensions/sql/test_extensions.sql postgresql-13-13.12/src/test/modules/test_extensions/sql/test_extensions.sql --- postgresql-13-13.11/src/test/modules/test_extensions/sql/test_extensions.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/test_extensions/sql/test_extensions.sql 2023-08-07 20:11:34.000000000 +0000 @@ -1,18 +1,20 @@ +CREATE SCHEMA has$dollar; + -- test some errors CREATE EXTENSION test_ext1; CREATE EXTENSION test_ext1 SCHEMA test_ext1; CREATE EXTENSION test_ext1 SCHEMA test_ext; -CREATE SCHEMA test_ext; -CREATE EXTENSION test_ext1 SCHEMA test_ext; +CREATE EXTENSION test_ext1 SCHEMA has$dollar; -- finally success -CREATE EXTENSION test_ext1 SCHEMA test_ext CASCADE; +CREATE EXTENSION test_ext1 SCHEMA has$dollar CASCADE; SELECT extname, nspname, extversion, extrelocatable FROM pg_extension e, pg_namespace n WHERE extname LIKE 'test_ext%' AND e.extnamespace = n.oid ORDER BY 1; CREATE EXTENSION test_ext_cyclic1 CASCADE; -DROP SCHEMA test_ext CASCADE; +DROP SCHEMA has$dollar CASCADE; +CREATE SCHEMA has$dollar; CREATE EXTENSION test_ext6; DROP EXTENSION test_ext6; @@ -209,3 +211,10 @@ ALTER EXTENSION test_ext_cine UPDATE TO '1.1'; \dx+ test_ext_cine + +-- +-- Test @extschema@ syntax. +-- +CREATE SCHEMA "has space"; +CREATE EXTENSION test_ext_extschema SCHEMA has$dollar; +CREATE EXTENSION test_ext_extschema SCHEMA "has space"; diff -Nru postgresql-13-13.11/src/test/modules/test_extensions/test_ext_extschema--1.0.sql postgresql-13-13.12/src/test/modules/test_extensions/test_ext_extschema--1.0.sql --- postgresql-13-13.11/src/test/modules/test_extensions/test_ext_extschema--1.0.sql 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/test_extensions/test_ext_extschema--1.0.sql 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,5 @@ +/* src/test/modules/test_extensions/test_ext_extschema--1.0.sql */ +-- complain if script is sourced in psql, rather than via CREATE EXTENSION +\echo Use "CREATE EXTENSION test_ext_extschema" to load this file. \quit + +SELECT 1 AS @extschema@; diff -Nru postgresql-13-13.11/src/test/modules/test_extensions/test_ext_extschema.control postgresql-13-13.12/src/test/modules/test_extensions/test_ext_extschema.control --- postgresql-13-13.11/src/test/modules/test_extensions/test_ext_extschema.control 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/src/test/modules/test_extensions/test_ext_extschema.control 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,3 @@ +comment = 'test @extschema@' +default_version = '1.0' +relocatable = false diff -Nru postgresql-13-13.11/src/test/perl/PostgresNode.pm postgresql-13-13.12/src/test/perl/PostgresNode.pm --- postgresql-13-13.11/src/test/perl/PostgresNode.pm 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/perl/PostgresNode.pm 2023-08-07 20:11:34.000000000 +0000 @@ -2081,6 +2081,21 @@ =pod +=item $node->log_contains(pattern, offset) + +Find pattern in logfile of node after offset byte. + +=cut + +sub log_contains +{ + my ($self, $pattern, $offset) = @_; + + return TestLib::slurp_file($self->logfile, $offset) =~ m/$pattern/; +} + +=pod + =item $node->run_log(...) Runs a shell command like TestLib::run_log, but with connection parameters set diff -Nru postgresql-13-13.11/src/test/perl/TestLib.pm postgresql-13-13.12/src/test/perl/TestLib.pm --- postgresql-13-13.11/src/test/perl/TestLib.pm 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/perl/TestLib.pm 2023-08-07 20:11:34.000000000 +0000 @@ -252,7 +252,7 @@ Securely create a temporary directory inside C<$tmp_check>, like C, and return its name. The directory will be removed automatically at the -end of the tests. +end of the tests, unless the environment variable PG_TEST_NOCLEAN is provided. If C is given, the new directory is templated as C<${prefix}_XXXX>. Otherwise the template is C. @@ -266,7 +266,7 @@ return File::Temp::tempdir( $prefix . '_XXXX', DIR => $tmp_check, - CLEANUP => 1); + CLEANUP => not defined $ENV{'PG_TEST_NOCLEAN'}); } =pod @@ -281,7 +281,8 @@ sub tempdir_short { - return File::Temp::tempdir(CLEANUP => 1); + return File::Temp::tempdir( + CLEANUP => not defined $ENV{'PG_TEST_NOCLEAN'}); } =pod diff -Nru postgresql-13-13.11/src/test/recovery/t/019_replslot_limit.pl postgresql-13-13.12/src/test/recovery/t/019_replslot_limit.pl --- postgresql-13-13.11/src/test/recovery/t/019_replslot_limit.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/recovery/t/019_replslot_limit.pl 2023-08-07 20:11:34.000000000 +0000 @@ -165,8 +165,7 @@ $node_standby->stop; -ok( !find_in_log( - $node_standby, +ok( !$node_standby->log_contains( "requested WAL segment [0-9A-F]+ has already been removed"), 'check that required WAL segments are still available'); @@ -188,8 +187,7 @@ my $invalidated = 0; for (my $i = 0; $i < 10000; $i++) { - if (find_in_log( - $node_master, + if ($node_master->log_contains( "invalidating slot \"rep1\" because its restart_lsn [0-9A-F/]+ exceeds max_slot_wal_keep_size", $logstart)) { @@ -212,7 +210,7 @@ my $checkpoint_ended = 0; for (my $i = 0; $i < 10000; $i++) { - if (find_in_log($node_master, "checkpoint complete: ", $logstart)) + if ($node_master->log_contains("checkpoint complete: ", $logstart)) { $checkpoint_ended = 1; last; @@ -242,8 +240,7 @@ my $failed = 0; for (my $i = 0; $i < 10000; $i++) { - if (find_in_log( - $node_standby, + if ($node_standby->log_contains( "requested WAL segment [0-9A-F]+ has already been removed", $logstart)) { @@ -318,17 +315,3 @@ return (stat $node->logfile)[7]; } - -# find $pat in logfile of $node after $off-th byte -sub find_in_log -{ - my ($node, $pat, $off) = @_; - - $off = 0 unless defined $off; - my $log = TestLib::slurp_file($node->logfile); - return 0 if (length($log) <= $off); - - $log = substr($log, $off); - - return $log =~ m/$pat/; -} diff -Nru postgresql-13-13.11/src/test/recovery/t/033_replay_tsp_drops.pl postgresql-13-13.12/src/test/recovery/t/033_replay_tsp_drops.pl --- postgresql-13-13.11/src/test/recovery/t/033_replay_tsp_drops.pl 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/recovery/t/033_replay_tsp_drops.pl 2023-08-07 20:11:34.000000000 +0000 @@ -132,21 +132,11 @@ { last if ( - find_in_log( - $node_standby, qr!WARNING: ( [A-Z0-9]+:)? creating missing directory: pg_tblspc/!, + $node_standby->log_contains( + qr!WARNING: ( [A-Z0-9]+:)? creating missing directory: pg_tblspc/!, $logstart)); usleep(100_000); } ok($max_attempts > 0, "invalid directory creation is detected"); done_testing(); - -# find $pat in logfile of $node after $off-th byte -sub find_in_log -{ - my ($node, $pat, $off) = @_; - - my $log = PostgreSQL::Test::Utils::slurp_file($node->logfile, $off); - - return $log =~ m/$pat/; -} diff -Nru postgresql-13-13.11/src/test/recovery/t/037_invalid_database.pl postgresql-13-13.12/src/test/recovery/t/037_invalid_database.pl --- postgresql-13-13.11/src/test/recovery/t/037_invalid_database.pl 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.12/src/test/recovery/t/037_invalid_database.pl 2023-08-07 20:11:34.000000000 +0000 @@ -0,0 +1,157 @@ +# Copyright (c) 2023, PostgreSQL Global Development Group +# +# Test we handle interrupted DROP DATABASE correctly. + +use strict; +use warnings; +use PostgreSQL::Test::Cluster; +use PostgreSQL::Test::Utils; +use Test::More; + +my $node = PostgreSQL::Test::Cluster->new('node'); +$node->init; +$node->append_conf( + "postgresql.conf", qq( +autovacuum = off +max_prepared_transactions=5 +log_min_duration_statement=0 +log_connections=on +log_disconnections=on +)); + +$node->start; + + +# First verify that we can't connect to or ALTER an invalid database. Just +# mark the database as invalid ourselves, that's more reliable than hitting the +# required race conditions (see testing further down)... + +$node->safe_psql( + "postgres", qq( +CREATE DATABASE regression_invalid; +UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid'; +)); + +my $psql_stdout = ''; +my $psql_stderr = ''; + +is($node->psql('regression_invalid', '', stderr => \$psql_stderr), + 2, "can't connect to invalid database - error code"); +like( + $psql_stderr, + qr/FATAL:\s+cannot connect to invalid database "regression_invalid"/, + "can't connect to invalid database - error message"); + +is($node->psql('postgres', 'ALTER DATABASE regression_invalid CONNECTION LIMIT 10'), + 2, "can't ALTER invalid database"); + +# check invalid database can't be used as a template +is( $node->psql('postgres', 'CREATE DATABASE copy_invalid TEMPLATE regression_invalid'), + 3, + "can't use invalid database as template"); + + +# Verify that VACUUM ignores an invalid database when computing how much of +# the clog is needed (vac_truncate_clog()). For that we modify the pg_database +# row of the invalid database to have an outdated datfrozenxid. +$psql_stderr = ''; +$node->psql( + 'postgres', + qq( +UPDATE pg_database SET datfrozenxid = '123456' WHERE datname = 'regression_invalid'; +DROP TABLE IF EXISTS foo_tbl; CREATE TABLE foo_tbl(); +VACUUM FREEZE;), + stderr => \$psql_stderr); +unlike( + $psql_stderr, + qr/some databases have not been vacuumed in over 2 billion transactions/, + "invalid databases are ignored by vac_truncate_clog"); + + +# But we need to be able to drop an invalid database. +is( $node->psql( + 'postgres', 'DROP DATABASE regression_invalid', + stdout => \$psql_stdout, + stderr => \$psql_stderr), + 0, + "can DROP invalid database"); + +# Ensure database is gone +is($node->psql('postgres', 'DROP DATABASE regression_invalid'), + 3, "can't drop already dropped database"); + + +# Test that interruption of DROP DATABASE is handled properly. To ensure the +# interruption happens at the appropriate moment, we lock pg_tablespace. DROP +# DATABASE scans pg_tablespace once it has reached the "irreversible" part of +# dropping the database, making it a suitable point to wait. +my $bgpsql_in = ''; +my $bgpsql_out = ''; +my $bgpsql_err = ''; +my $bgpsql_timer = IPC::Run::timer($PostgreSQL::Test::Utils::timeout_default); +my $bgpsql = $node->background_psql('postgres', \$bgpsql_in, \$bgpsql_out, + $bgpsql_timer, on_error_stop => 0); +$bgpsql_out = ''; +$bgpsql_in .= "SELECT pg_backend_pid();\n"; + +pump_until($bgpsql, $bgpsql_timer, \$bgpsql_out, qr/\d/); + +my $pid = $bgpsql_out; +$bgpsql_out = ''; + +# create the database, prevent drop database via lock held by a 2PC transaction +$bgpsql_in .= qq( + CREATE DATABASE regression_invalid_interrupt; + BEGIN; + LOCK pg_tablespace; + PREPARE TRANSACTION 'lock_tblspc'; + \\echo done +); + +ok(pump_until($bgpsql, $bgpsql_timer, \$bgpsql_out, qr/done/), + "blocked DROP DATABASE completion"); +$bgpsql_out = ''; + +# Try to drop. This will wait due to the still held lock. +$bgpsql_in .= qq( + DROP DATABASE regression_invalid_interrupt; + \\echo DROP DATABASE completed +); +$bgpsql->pump_nb; + +# Ensure we're waiting for the lock +$node->poll_query_until('postgres', + qq(SELECT EXISTS(SELECT * FROM pg_locks WHERE NOT granted AND relation = 'pg_tablespace'::regclass AND mode = 'AccessShareLock');) +); + +# and finally interrupt the DROP DATABASE +ok($node->safe_psql('postgres', "SELECT pg_cancel_backend($pid)"), + "canceling DROP DATABASE"); + +# wait for cancellation to be processed +ok( pump_until( + $bgpsql, $bgpsql_timer, \$bgpsql_out, qr/DROP DATABASE completed/), + "cancel processed"); +$bgpsql_out = ''; + +# verify that connection to the database aren't allowed +is($node->psql('regression_invalid_interrupt', ''), + 2, "can't connect to invalid_interrupt database"); + +# To properly drop the database, we need to release the lock previously preventing +# doing so. +$bgpsql_in .= qq( + ROLLBACK PREPARED 'lock_tblspc'; + \\echo ROLLBACK PREPARED +); +ok(pump_until($bgpsql, $bgpsql_timer, \$bgpsql_out, qr/ROLLBACK PREPARED/), + "unblock DROP DATABASE"); +$bgpsql_out = ''; + +is($node->psql('postgres', "DROP DATABASE regression_invalid_interrupt"), + 0, "DROP DATABASE invalid_interrupt"); + +$bgpsql_in .= "\\q\n"; +$bgpsql->finish(); + +done_testing(); diff -Nru postgresql-13-13.11/src/test/regress/expected/indexing.out postgresql-13-13.12/src/test/regress/expected/indexing.out --- postgresql-13-13.11/src/test/regress/expected/indexing.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/indexing.out 2023-08-07 20:11:34.000000000 +0000 @@ -1420,3 +1420,131 @@ "parted_index_col_drop11_b_idx" btree (b) drop table parted_index_col_drop; +-- Check that invalid indexes are not selected when attaching a partition. +create table parted_inval_tab (a int) partition by range (a); +create index parted_inval_idx on parted_inval_tab (a); +create table parted_inval_tab_1 (a int) partition by range (a); +create table parted_inval_tab_1_1 partition of parted_inval_tab_1 + for values from (0) to (10); +create table parted_inval_tab_1_2 partition of parted_inval_tab_1 + for values from (10) to (20); +-- this creates an invalid index. +create index parted_inval_ixd_1 on only parted_inval_tab_1 (a); +-- this creates new indexes for all the partitions of parted_inval_tab_1, +-- discarding the invalid index created previously as what is chosen. +alter table parted_inval_tab attach partition parted_inval_tab_1 + for values from (1) to (100); +select indexrelid::regclass, indisvalid, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_inval%' + order by indexrelid::regclass::text collate "C"; + indexrelid | indisvalid | indrelid | inhparent +----------------------------+------------+----------------------+-------------------------- + parted_inval_idx | t | parted_inval_tab | + parted_inval_ixd_1 | f | parted_inval_tab_1 | + parted_inval_tab_1_1_a_idx | t | parted_inval_tab_1_1 | parted_inval_tab_1_a_idx + parted_inval_tab_1_2_a_idx | t | parted_inval_tab_1_2 | parted_inval_tab_1_a_idx + parted_inval_tab_1_a_idx | t | parted_inval_tab_1 | parted_inval_idx +(5 rows) + +drop table parted_inval_tab; +-- Check setup of indisvalid across a complex partition tree on index +-- creation. If one index in a partition index is invalid, so should its +-- partitioned index. +create table parted_isvalid_tab (a int, b int) partition by range (a); +create table parted_isvalid_tab_1 partition of parted_isvalid_tab + for values from (1) to (10) partition by range (a); +create table parted_isvalid_tab_2 partition of parted_isvalid_tab + for values from (10) to (20) partition by range (a); +create table parted_isvalid_tab_11 partition of parted_isvalid_tab_1 + for values from (1) to (5); +create table parted_isvalid_tab_12 partition of parted_isvalid_tab_1 + for values from (5) to (10); +-- create an invalid index on one of the partitions. +insert into parted_isvalid_tab_11 values (1, 0); +create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b)); +ERROR: division by zero +-- The previous invalid index is selected, invalidating all the indexes up to +-- the top-most parent. +create index parted_isvalid_idx on parted_isvalid_tab ((a/b)); +select indexrelid::regclass, indisvalid, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_isvalid%' + order by indexrelid::regclass::text collate "C"; + indexrelid | indisvalid | indrelid | inhparent +--------------------------------+------------+-----------------------+------------------------------- + parted_isvalid_idx | f | parted_isvalid_tab | + parted_isvalid_idx_11 | f | parted_isvalid_tab_11 | parted_isvalid_tab_1_expr_idx + parted_isvalid_tab_12_expr_idx | t | parted_isvalid_tab_12 | parted_isvalid_tab_1_expr_idx + parted_isvalid_tab_1_expr_idx | f | parted_isvalid_tab_1 | parted_isvalid_idx + parted_isvalid_tab_2_expr_idx | t | parted_isvalid_tab_2 | parted_isvalid_idx +(5 rows) + +drop table parted_isvalid_tab; +-- Check state of replica indexes when attaching a partition. +begin; +create table parted_replica_tab (id int not null) partition by range (id); +create table parted_replica_tab_1 partition of parted_replica_tab + for values from (1) to (10) partition by range (id); +create table parted_replica_tab_11 partition of parted_replica_tab_1 + for values from (1) to (5); +create unique index parted_replica_idx + on only parted_replica_tab using btree (id); +create unique index parted_replica_idx_1 + on only parted_replica_tab_1 using btree (id); +-- This triggers an update of pg_index.indisreplident for parted_replica_idx. +alter table only parted_replica_tab_1 replica identity + using index parted_replica_idx_1; +create unique index parted_replica_idx_11 on parted_replica_tab_11 USING btree (id); +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; + indexrelid | indisvalid | indisreplident | indrelid | inhparent +-----------------------+------------+----------------+-----------------------+----------- + parted_replica_idx | f | f | parted_replica_tab | + parted_replica_idx_1 | f | t | parted_replica_tab_1 | + parted_replica_idx_11 | t | f | parted_replica_tab_11 | +(3 rows) + +-- parted_replica_idx is not valid yet here, because parted_replica_idx_1 +-- is not valid. +alter index parted_replica_idx ATTACH PARTITION parted_replica_idx_1; +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; + indexrelid | indisvalid | indisreplident | indrelid | inhparent +-----------------------+------------+----------------+-----------------------+-------------------- + parted_replica_idx | f | f | parted_replica_tab | + parted_replica_idx_1 | f | t | parted_replica_tab_1 | parted_replica_idx + parted_replica_idx_11 | t | f | parted_replica_tab_11 | +(3 rows) + +-- parted_replica_idx becomes valid here. +alter index parted_replica_idx_1 ATTACH PARTITION parted_replica_idx_11; +alter table only parted_replica_tab_1 replica identity + using index parted_replica_idx_1; +commit; +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; + indexrelid | indisvalid | indisreplident | indrelid | inhparent +-----------------------+------------+----------------+-----------------------+---------------------- + parted_replica_idx | t | f | parted_replica_tab | + parted_replica_idx_1 | t | t | parted_replica_tab_1 | parted_replica_idx + parted_replica_idx_11 | t | f | parted_replica_tab_11 | parted_replica_idx_1 +(3 rows) + +drop table parted_replica_tab; diff -Nru postgresql-13-13.11/src/test/regress/expected/join.out postgresql-13-13.12/src/test/regress/expected/join.out --- postgresql-13-13.11/src/test/regress/expected/join.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/join.out 2023-08-07 20:11:34.000000000 +0000 @@ -6346,6 +6346,23 @@ Output: j2.id1, j2.id2 (8 rows) +create unique index j1_id2_idx on j1(id2) where id2 is not null; +-- ensure we don't use a partial unique index as unique proofs +explain (verbose, costs off) +select * from j1 +inner join j2 on j1.id2 = j2.id2; + QUERY PLAN +------------------------------------------ + Nested Loop + Output: j1.id1, j1.id2, j2.id1, j2.id2 + Join Filter: (j1.id2 = j2.id2) + -> Seq Scan on public.j2 + Output: j2.id1, j2.id2 + -> Seq Scan on public.j1 + Output: j1.id1, j1.id2 +(7 rows) + +drop index j1_id2_idx; -- validate logic in merge joins which skips mark and restore. -- it should only do this if all quals which were used to detect the unique -- are present as join quals, and not plain quals. diff -Nru postgresql-13-13.11/src/test/regress/expected/join_hash.out postgresql-13-13.12/src/test/regress/expected/join_hash.out --- postgresql-13-13.11/src/test/regress/expected/join_hash.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/join_hash.out 2023-08-07 20:11:34.000000000 +0000 @@ -1013,3 +1013,39 @@ (1 row) ROLLBACK; +-- Verify that we behave sanely when the inner hash keys contain parameters +-- (that is, outer or lateral references). This situation has to defeat +-- re-use of the inner hash table across rescans. +begin; +set local enable_hashjoin = on; +explain (costs off) +select i8.q2, ss.* from +int8_tbl i8, +lateral (select t1.fivethous, i4.f1 from tenk1 t1 join int4_tbl i4 + on t1.fivethous = i4.f1+i8.q2 order by 1,2) ss; + QUERY PLAN +----------------------------------------------------------- + Nested Loop + -> Seq Scan on int8_tbl i8 + -> Sort + Sort Key: t1.fivethous, i4.f1 + -> Hash Join + Hash Cond: (t1.fivethous = (i4.f1 + i8.q2)) + -> Seq Scan on tenk1 t1 + -> Hash + -> Seq Scan on int4_tbl i4 +(9 rows) + +select i8.q2, ss.* from +int8_tbl i8, +lateral (select t1.fivethous, i4.f1 from tenk1 t1 join int4_tbl i4 + on t1.fivethous = i4.f1+i8.q2 order by 1,2) ss; + q2 | fivethous | f1 +-----+-----------+---- + 456 | 456 | 0 + 456 | 456 | 0 + 123 | 123 | 0 + 123 | 123 | 0 +(4 rows) + +rollback; diff -Nru postgresql-13-13.11/src/test/regress/expected/jsonb_jsonpath.out postgresql-13-13.12/src/test/regress/expected/jsonb_jsonpath.out --- postgresql-13-13.11/src/test/regress/expected/jsonb_jsonpath.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/jsonb_jsonpath.out 2023-08-07 20:11:34.000000000 +0000 @@ -1920,6 +1920,21 @@ select jsonb_path_query('"2017-03-10t12:34:56+3:10"', '$.datetime()'); ERROR: datetime format is not recognized: "2017-03-10t12:34:56+3:10" HINT: Use a datetime template argument to specify the input data format. +select jsonb_path_query('"2017-03-10 12:34:56.789+3:10"', '$.datetime()'); + jsonb_path_query +--------------------------------- + "2017-03-10T12:34:56.789+03:10" +(1 row) + +select jsonb_path_query('"2017-03-10T12:34:56.789+3:10"', '$.datetime()'); + jsonb_path_query +--------------------------------- + "2017-03-10T12:34:56.789+03:10" +(1 row) + +select jsonb_path_query('"2017-03-10t12:34:56.789+3:10"', '$.datetime()'); +ERROR: datetime format is not recognized: "2017-03-10t12:34:56.789+3:10" +HINT: Use a datetime template argument to specify the input data format. select jsonb_path_query('"12:34:56"', '$.datetime().type()'); jsonb_path_query -------------------------- diff -Nru postgresql-13-13.11/src/test/regress/expected/psql.out postgresql-13-13.12/src/test/regress/expected/psql.out --- postgresql-13-13.11/src/test/regress/expected/psql.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/psql.out 2023-08-07 20:11:34.000000000 +0000 @@ -237,6 +237,17 @@ 3 | Hello | 4 | t (1 row) +-- test for server bug #17983 with empty statement in aborted transaction +set search_path = default; +begin; +bogus; +ERROR: syntax error at or near "bogus" +LINE 1: bogus; + ^ +; +\gdesc +The command has no result, or the result has no columns. +rollback; -- \gexec create temporary table gexec_test(a int, b text, c date, d float); select format('create index on gexec_test(%I)', attname) diff -Nru postgresql-13-13.11/src/test/regress/expected/rowtypes.out postgresql-13-13.12/src/test/regress/expected/rowtypes.out --- postgresql-13-13.11/src/test/regress/expected/rowtypes.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/rowtypes.out 2023-08-07 20:11:34.000000000 +0000 @@ -139,6 +139,15 @@ Jim | abcdefghijklabcdefgh | 1200000 (2 rows) +-- try an update on a toasted composite value, too +update people set fn.first = 'Jack'; +select (fn).first, substr((fn).last, 1, 20), length((fn).last) from people; + first | substr | length +-------+----------------------+--------- + Jack | Blow | 4 + Jack | abcdefghijklabcdefgh | 1200000 +(2 rows) + -- Test row comparison semantics. Prior to PG 8.2 we did this in a totally -- non-spec-compliant way. select ROW(1,2) < ROW(1,3) as true; diff -Nru postgresql-13-13.11/src/test/regress/expected/transactions.out postgresql-13-13.12/src/test/regress/expected/transactions.out --- postgresql-13-13.11/src/test/regress/expected/transactions.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/transactions.out 2023-08-07 20:11:34.000000000 +0000 @@ -571,10 +571,10 @@ -- performed in the aborted subtransaction begin; savepoint x; -create table abc (a int); -insert into abc values (5); -insert into abc values (10); -declare foo cursor for select * from abc; +create table trans_abc (a int); +insert into trans_abc values (5); +insert into trans_abc values (10); +declare foo cursor for select * from trans_abc; fetch from foo; a --- @@ -587,11 +587,11 @@ ERROR: cursor "foo" does not exist commit; begin; -create table abc (a int); -insert into abc values (5); -insert into abc values (10); -insert into abc values (15); -declare foo cursor for select * from abc; +create table trans_abc (a int); +insert into trans_abc values (5); +insert into trans_abc values (10); +insert into trans_abc values (15); +declare foo cursor for select * from trans_abc; fetch from foo; a --- @@ -660,7 +660,7 @@ DROP FUNCTION create_temp_tab(); DROP FUNCTION invert(x float8); -- Tests for AND CHAIN -CREATE TABLE abc (a int); +CREATE TABLE trans_abc (a int); -- set nondefault value so we have something to override below SET default_transaction_read_only = on; START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE; @@ -682,8 +682,8 @@ on (1 row) -INSERT INTO abc VALUES (1); -INSERT INTO abc VALUES (2); +INSERT INTO trans_abc VALUES (1); +INSERT INTO trans_abc VALUES (2); COMMIT AND CHAIN; -- TBLOCK_END SHOW transaction_isolation; transaction_isolation @@ -703,11 +703,11 @@ on (1 row) -INSERT INTO abc VALUES ('error'); +INSERT INTO trans_abc VALUES ('error'); ERROR: invalid input syntax for type integer: "error" -LINE 1: INSERT INTO abc VALUES ('error'); - ^ -INSERT INTO abc VALUES (3); -- check it's really aborted +LINE 1: INSERT INTO trans_abc VALUES ('error'); + ^ +INSERT INTO trans_abc VALUES (3); -- check it's really aborted ERROR: current transaction is aborted, commands ignored until end of transaction block COMMIT AND CHAIN; -- TBLOCK_ABORT_END SHOW transaction_isolation; @@ -728,7 +728,7 @@ on (1 row) -INSERT INTO abc VALUES (4); +INSERT INTO trans_abc VALUES (4); COMMIT; START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE; SHOW transaction_isolation; @@ -750,10 +750,10 @@ (1 row) SAVEPOINT x; -INSERT INTO abc VALUES ('error'); +INSERT INTO trans_abc VALUES ('error'); ERROR: invalid input syntax for type integer: "error" -LINE 1: INSERT INTO abc VALUES ('error'); - ^ +LINE 1: INSERT INTO trans_abc VALUES ('error'); + ^ COMMIT AND CHAIN; -- TBLOCK_ABORT_PENDING SHOW transaction_isolation; transaction_isolation @@ -773,7 +773,7 @@ on (1 row) -INSERT INTO abc VALUES (5); +INSERT INTO trans_abc VALUES (5); COMMIT; START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE; SHOW transaction_isolation; @@ -835,7 +835,7 @@ off (1 row) -INSERT INTO abc VALUES (6); +INSERT INTO trans_abc VALUES (6); ROLLBACK AND CHAIN; -- TBLOCK_ABORT_PENDING SHOW transaction_isolation; transaction_isolation @@ -855,10 +855,10 @@ off (1 row) -INSERT INTO abc VALUES ('error'); +INSERT INTO trans_abc VALUES ('error'); ERROR: invalid input syntax for type integer: "error" -LINE 1: INSERT INTO abc VALUES ('error'); - ^ +LINE 1: INSERT INTO trans_abc VALUES ('error'); + ^ ROLLBACK AND CHAIN; -- TBLOCK_ABORT_END SHOW transaction_isolation; transaction_isolation @@ -884,7 +884,7 @@ ERROR: COMMIT AND CHAIN can only be used in transaction blocks ROLLBACK AND CHAIN; -- error ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks -SELECT * FROM abc ORDER BY 1; +SELECT * FROM trans_abc ORDER BY 1; a --- 1 @@ -894,7 +894,7 @@ (4 rows) RESET default_transaction_read_only; -DROP TABLE abc; +DROP TABLE trans_abc; -- Test assorted behaviors around the implicit transaction block created -- when multiple SQL commands are sent in a single Query message. These -- tests rely on the fact that psql will not break SQL commands apart at a @@ -996,21 +996,21 @@ off (1 row) -CREATE TABLE abc (a int); +CREATE TABLE trans_abc (a int); -- COMMIT/ROLLBACK + COMMIT/ROLLBACK AND CHAIN -INSERT INTO abc VALUES (7)\; COMMIT\; INSERT INTO abc VALUES (8)\; COMMIT AND CHAIN; -- 7 commit, 8 error +INSERT INTO trans_abc VALUES (7)\; COMMIT\; INSERT INTO trans_abc VALUES (8)\; COMMIT AND CHAIN; -- 7 commit, 8 error WARNING: there is no transaction in progress ERROR: COMMIT AND CHAIN can only be used in transaction blocks -INSERT INTO abc VALUES (9)\; ROLLBACK\; INSERT INTO abc VALUES (10)\; ROLLBACK AND CHAIN; -- 9 rollback, 10 error +INSERT INTO trans_abc VALUES (9)\; ROLLBACK\; INSERT INTO trans_abc VALUES (10)\; ROLLBACK AND CHAIN; -- 9 rollback, 10 error WARNING: there is no transaction in progress ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks -- COMMIT/ROLLBACK AND CHAIN + COMMIT/ROLLBACK -INSERT INTO abc VALUES (11)\; COMMIT AND CHAIN\; INSERT INTO abc VALUES (12)\; COMMIT; -- 11 error, 12 not reached +INSERT INTO trans_abc VALUES (11)\; COMMIT AND CHAIN\; INSERT INTO trans_abc VALUES (12)\; COMMIT; -- 11 error, 12 not reached ERROR: COMMIT AND CHAIN can only be used in transaction blocks -INSERT INTO abc VALUES (13)\; ROLLBACK AND CHAIN\; INSERT INTO abc VALUES (14)\; ROLLBACK; -- 13 error, 14 not reached +INSERT INTO trans_abc VALUES (13)\; ROLLBACK AND CHAIN\; INSERT INTO trans_abc VALUES (14)\; ROLLBACK; -- 13 error, 14 not reached ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks -- START TRANSACTION + COMMIT/ROLLBACK AND CHAIN -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (15)\; COMMIT AND CHAIN; -- 15 ok +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (15)\; COMMIT AND CHAIN; -- 15 ok SHOW transaction_isolation; -- transaction is active at this point transaction_isolation ----------------------- @@ -1018,7 +1018,7 @@ (1 row) COMMIT; -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (16)\; ROLLBACK AND CHAIN; -- 16 ok +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (16)\; ROLLBACK AND CHAIN; -- 16 ok SHOW transaction_isolation; -- transaction is active at this point transaction_isolation ----------------------- @@ -1027,7 +1027,7 @@ ROLLBACK; -- START TRANSACTION + COMMIT/ROLLBACK + COMMIT/ROLLBACK AND CHAIN -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (17)\; COMMIT\; INSERT INTO abc VALUES (18)\; COMMIT AND CHAIN; -- 17 commit, 18 error +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (17)\; COMMIT\; INSERT INTO trans_abc VALUES (18)\; COMMIT AND CHAIN; -- 17 commit, 18 error ERROR: COMMIT AND CHAIN can only be used in transaction blocks SHOW transaction_isolation; -- out of transaction block transaction_isolation @@ -1035,7 +1035,7 @@ read committed (1 row) -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (19)\; ROLLBACK\; INSERT INTO abc VALUES (20)\; ROLLBACK AND CHAIN; -- 19 rollback, 20 error +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (19)\; ROLLBACK\; INSERT INTO trans_abc VALUES (20)\; ROLLBACK AND CHAIN; -- 19 rollback, 20 error ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks SHOW transaction_isolation; -- out of transaction block transaction_isolation @@ -1043,7 +1043,7 @@ read committed (1 row) -SELECT * FROM abc ORDER BY 1; +SELECT * FROM trans_abc ORDER BY 1; a ---- 7 @@ -1051,7 +1051,7 @@ 17 (3 rows) -DROP TABLE abc; +DROP TABLE trans_abc; -- Test for successful cleanup of an aborted transaction at session exit. -- THIS MUST BE THE LAST TEST IN THIS FILE. begin; diff -Nru postgresql-13-13.11/src/test/regress/expected/updatable_views.out postgresql-13-13.12/src/test/regress/expected/updatable_views.out --- postgresql-13-13.11/src/test/regress/expected/updatable_views.out 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/expected/updatable_views.out 2023-08-07 20:11:34.000000000 +0000 @@ -2616,6 +2616,38 @@ DROP TABLE t2; DROP TABLE t1; -- +-- Test sub-select in nested security barrier views, per bug #17972 +-- +CREATE TABLE t1 (a int); +CREATE VIEW v1 WITH (security_barrier = true) AS + SELECT * FROM t1; +CREATE RULE v1_upd_rule AS ON UPDATE TO v1 DO INSTEAD + UPDATE t1 SET a = NEW.a WHERE a = OLD.a; +CREATE VIEW v2 WITH (security_barrier = true) AS + SELECT * FROM v1 WHERE EXISTS (SELECT 1); +EXPLAIN (COSTS OFF) UPDATE v2 SET a = 1; + QUERY PLAN +--------------------------------------------------- + Update on t1 + InitPlan 1 (returns $0) + -> Result + -> Merge Join + Merge Cond: (t1.a = v1.a) + -> Sort + Sort Key: t1.a + -> Seq Scan on t1 + -> Sort + Sort Key: v1.a + -> Subquery Scan on v1 + -> Result + One-Time Filter: $0 + -> Seq Scan on t1 t1_1 +(14 rows) + +DROP VIEW v2; +DROP VIEW v1; +DROP TABLE t1; +-- -- Test CREATE OR REPLACE VIEW turning a non-updatable view into an -- auto-updatable view and adding check options in a single step -- diff -Nru postgresql-13-13.11/src/test/regress/sql/indexing.sql postgresql-13-13.12/src/test/regress/sql/indexing.sql --- postgresql-13-13.11/src/test/regress/sql/indexing.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/indexing.sql 2023-08-07 20:11:34.000000000 +0000 @@ -760,3 +760,94 @@ \d parted_index_col_drop2 \d parted_index_col_drop11 drop table parted_index_col_drop; + +-- Check that invalid indexes are not selected when attaching a partition. +create table parted_inval_tab (a int) partition by range (a); +create index parted_inval_idx on parted_inval_tab (a); +create table parted_inval_tab_1 (a int) partition by range (a); +create table parted_inval_tab_1_1 partition of parted_inval_tab_1 + for values from (0) to (10); +create table parted_inval_tab_1_2 partition of parted_inval_tab_1 + for values from (10) to (20); +-- this creates an invalid index. +create index parted_inval_ixd_1 on only parted_inval_tab_1 (a); +-- this creates new indexes for all the partitions of parted_inval_tab_1, +-- discarding the invalid index created previously as what is chosen. +alter table parted_inval_tab attach partition parted_inval_tab_1 + for values from (1) to (100); +select indexrelid::regclass, indisvalid, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_inval%' + order by indexrelid::regclass::text collate "C"; +drop table parted_inval_tab; + +-- Check setup of indisvalid across a complex partition tree on index +-- creation. If one index in a partition index is invalid, so should its +-- partitioned index. +create table parted_isvalid_tab (a int, b int) partition by range (a); +create table parted_isvalid_tab_1 partition of parted_isvalid_tab + for values from (1) to (10) partition by range (a); +create table parted_isvalid_tab_2 partition of parted_isvalid_tab + for values from (10) to (20) partition by range (a); +create table parted_isvalid_tab_11 partition of parted_isvalid_tab_1 + for values from (1) to (5); +create table parted_isvalid_tab_12 partition of parted_isvalid_tab_1 + for values from (5) to (10); +-- create an invalid index on one of the partitions. +insert into parted_isvalid_tab_11 values (1, 0); +create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b)); +-- The previous invalid index is selected, invalidating all the indexes up to +-- the top-most parent. +create index parted_isvalid_idx on parted_isvalid_tab ((a/b)); +select indexrelid::regclass, indisvalid, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_isvalid%' + order by indexrelid::regclass::text collate "C"; +drop table parted_isvalid_tab; + +-- Check state of replica indexes when attaching a partition. +begin; +create table parted_replica_tab (id int not null) partition by range (id); +create table parted_replica_tab_1 partition of parted_replica_tab + for values from (1) to (10) partition by range (id); +create table parted_replica_tab_11 partition of parted_replica_tab_1 + for values from (1) to (5); +create unique index parted_replica_idx + on only parted_replica_tab using btree (id); +create unique index parted_replica_idx_1 + on only parted_replica_tab_1 using btree (id); +-- This triggers an update of pg_index.indisreplident for parted_replica_idx. +alter table only parted_replica_tab_1 replica identity + using index parted_replica_idx_1; +create unique index parted_replica_idx_11 on parted_replica_tab_11 USING btree (id); +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; +-- parted_replica_idx is not valid yet here, because parted_replica_idx_1 +-- is not valid. +alter index parted_replica_idx ATTACH PARTITION parted_replica_idx_1; +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; +-- parted_replica_idx becomes valid here. +alter index parted_replica_idx_1 ATTACH PARTITION parted_replica_idx_11; +alter table only parted_replica_tab_1 replica identity + using index parted_replica_idx_1; +commit; +select indexrelid::regclass, indisvalid, indisreplident, + indrelid::regclass, inhparent::regclass + from pg_index idx left join + pg_inherits inh on (idx.indexrelid = inh.inhrelid) + where indexrelid::regclass::text like 'parted_replica%' + order by indexrelid::regclass::text collate "C"; +drop table parted_replica_tab; diff -Nru postgresql-13-13.11/src/test/regress/sql/join.sql postgresql-13-13.12/src/test/regress/sql/join.sql --- postgresql-13-13.11/src/test/regress/sql/join.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/join.sql 2023-08-07 20:11:34.000000000 +0000 @@ -2204,6 +2204,15 @@ select * from j1 left join j2 on j1.id1 = j2.id1 where j1.id2 = 1; +create unique index j1_id2_idx on j1(id2) where id2 is not null; + +-- ensure we don't use a partial unique index as unique proofs +explain (verbose, costs off) +select * from j1 +inner join j2 on j1.id2 = j2.id2; + +drop index j1_id2_idx; + -- validate logic in merge joins which skips mark and restore. -- it should only do this if all quals which were used to detect the unique -- are present as join quals, and not plain quals. diff -Nru postgresql-13-13.11/src/test/regress/sql/join_hash.sql postgresql-13-13.12/src/test/regress/sql/join_hash.sql --- postgresql-13-13.11/src/test/regress/sql/join_hash.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/join_hash.sql 2023-08-07 20:11:34.000000000 +0000 @@ -538,3 +538,22 @@ AND hjtest_1.a <> hjtest_2.b; ROLLBACK; + +-- Verify that we behave sanely when the inner hash keys contain parameters +-- (that is, outer or lateral references). This situation has to defeat +-- re-use of the inner hash table across rescans. +begin; +set local enable_hashjoin = on; + +explain (costs off) +select i8.q2, ss.* from +int8_tbl i8, +lateral (select t1.fivethous, i4.f1 from tenk1 t1 join int4_tbl i4 + on t1.fivethous = i4.f1+i8.q2 order by 1,2) ss; + +select i8.q2, ss.* from +int8_tbl i8, +lateral (select t1.fivethous, i4.f1 from tenk1 t1 join int4_tbl i4 + on t1.fivethous = i4.f1+i8.q2 order by 1,2) ss; + +rollback; diff -Nru postgresql-13-13.11/src/test/regress/sql/jsonb_jsonpath.sql postgresql-13-13.12/src/test/regress/sql/jsonb_jsonpath.sql --- postgresql-13-13.11/src/test/regress/sql/jsonb_jsonpath.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/jsonb_jsonpath.sql 2023-08-07 20:11:34.000000000 +0000 @@ -414,6 +414,9 @@ select jsonb_path_query('"2017-03-10 12:34:56+3:10"', '$.datetime()'); select jsonb_path_query('"2017-03-10T12:34:56+3:10"', '$.datetime()'); select jsonb_path_query('"2017-03-10t12:34:56+3:10"', '$.datetime()'); +select jsonb_path_query('"2017-03-10 12:34:56.789+3:10"', '$.datetime()'); +select jsonb_path_query('"2017-03-10T12:34:56.789+3:10"', '$.datetime()'); +select jsonb_path_query('"2017-03-10t12:34:56.789+3:10"', '$.datetime()'); select jsonb_path_query('"12:34:56"', '$.datetime().type()'); select jsonb_path_query('"12:34:56"', '$.datetime()'); select jsonb_path_query('"12:34:56+3"', '$.datetime().type()'); diff -Nru postgresql-13-13.11/src/test/regress/sql/psql.sql postgresql-13-13.12/src/test/regress/sql/psql.sql --- postgresql-13-13.11/src/test/regress/sql/psql.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/psql.sql 2023-08-07 20:11:34.000000000 +0000 @@ -119,6 +119,14 @@ -- all on one line SELECT 3 AS x, 'Hello', 4 AS y, true AS "dirty\name" \gdesc \g +-- test for server bug #17983 with empty statement in aborted transaction +set search_path = default; +begin; +bogus; +; +\gdesc +rollback; + -- \gexec create temporary table gexec_test(a int, b text, c date, d float); diff -Nru postgresql-13-13.11/src/test/regress/sql/rowtypes.sql postgresql-13-13.12/src/test/regress/sql/rowtypes.sql --- postgresql-13-13.11/src/test/regress/sql/rowtypes.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/rowtypes.sql 2023-08-07 20:11:34.000000000 +0000 @@ -76,6 +76,11 @@ select (fn).first, substr((fn).last, 1, 20), length((fn).last) from people; +-- try an update on a toasted composite value, too +update people set fn.first = 'Jack'; + +select (fn).first, substr((fn).last, 1, 20), length((fn).last) from people; + -- Test row comparison semantics. Prior to PG 8.2 we did this in a totally -- non-spec-compliant way. diff -Nru postgresql-13-13.11/src/test/regress/sql/transactions.sql postgresql-13-13.12/src/test/regress/sql/transactions.sql --- postgresql-13-13.11/src/test/regress/sql/transactions.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/transactions.sql 2023-08-07 20:11:34.000000000 +0000 @@ -358,10 +358,10 @@ begin; savepoint x; -create table abc (a int); -insert into abc values (5); -insert into abc values (10); -declare foo cursor for select * from abc; +create table trans_abc (a int); +insert into trans_abc values (5); +insert into trans_abc values (10); +declare foo cursor for select * from trans_abc; fetch from foo; rollback to x; @@ -371,11 +371,11 @@ begin; -create table abc (a int); -insert into abc values (5); -insert into abc values (10); -insert into abc values (15); -declare foo cursor for select * from abc; +create table trans_abc (a int); +insert into trans_abc values (5); +insert into trans_abc values (10); +insert into trans_abc values (15); +declare foo cursor for select * from trans_abc; fetch from foo; @@ -421,7 +421,7 @@ -- Tests for AND CHAIN -CREATE TABLE abc (a int); +CREATE TABLE trans_abc (a int); -- set nondefault value so we have something to override below SET default_transaction_read_only = on; @@ -430,19 +430,19 @@ SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES (1); -INSERT INTO abc VALUES (2); +INSERT INTO trans_abc VALUES (1); +INSERT INTO trans_abc VALUES (2); COMMIT AND CHAIN; -- TBLOCK_END SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES ('error'); -INSERT INTO abc VALUES (3); -- check it's really aborted +INSERT INTO trans_abc VALUES ('error'); +INSERT INTO trans_abc VALUES (3); -- check it's really aborted COMMIT AND CHAIN; -- TBLOCK_ABORT_END SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES (4); +INSERT INTO trans_abc VALUES (4); COMMIT; START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE; @@ -450,12 +450,12 @@ SHOW transaction_read_only; SHOW transaction_deferrable; SAVEPOINT x; -INSERT INTO abc VALUES ('error'); +INSERT INTO trans_abc VALUES ('error'); COMMIT AND CHAIN; -- TBLOCK_ABORT_PENDING SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES (5); +INSERT INTO trans_abc VALUES (5); COMMIT; START TRANSACTION ISOLATION LEVEL REPEATABLE READ, READ WRITE, DEFERRABLE; @@ -474,12 +474,12 @@ SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES (6); +INSERT INTO trans_abc VALUES (6); ROLLBACK AND CHAIN; -- TBLOCK_ABORT_PENDING SHOW transaction_isolation; SHOW transaction_read_only; SHOW transaction_deferrable; -INSERT INTO abc VALUES ('error'); +INSERT INTO trans_abc VALUES ('error'); ROLLBACK AND CHAIN; -- TBLOCK_ABORT_END SHOW transaction_isolation; SHOW transaction_read_only; @@ -490,11 +490,11 @@ COMMIT AND CHAIN; -- error ROLLBACK AND CHAIN; -- error -SELECT * FROM abc ORDER BY 1; +SELECT * FROM trans_abc ORDER BY 1; RESET default_transaction_read_only; -DROP TABLE abc; +DROP TABLE trans_abc; -- Test assorted behaviors around the implicit transaction block created @@ -559,35 +559,35 @@ SET TRANSACTION READ ONLY\; ROLLBACK AND CHAIN; -- error SHOW transaction_read_only; -CREATE TABLE abc (a int); +CREATE TABLE trans_abc (a int); -- COMMIT/ROLLBACK + COMMIT/ROLLBACK AND CHAIN -INSERT INTO abc VALUES (7)\; COMMIT\; INSERT INTO abc VALUES (8)\; COMMIT AND CHAIN; -- 7 commit, 8 error -INSERT INTO abc VALUES (9)\; ROLLBACK\; INSERT INTO abc VALUES (10)\; ROLLBACK AND CHAIN; -- 9 rollback, 10 error +INSERT INTO trans_abc VALUES (7)\; COMMIT\; INSERT INTO trans_abc VALUES (8)\; COMMIT AND CHAIN; -- 7 commit, 8 error +INSERT INTO trans_abc VALUES (9)\; ROLLBACK\; INSERT INTO trans_abc VALUES (10)\; ROLLBACK AND CHAIN; -- 9 rollback, 10 error -- COMMIT/ROLLBACK AND CHAIN + COMMIT/ROLLBACK -INSERT INTO abc VALUES (11)\; COMMIT AND CHAIN\; INSERT INTO abc VALUES (12)\; COMMIT; -- 11 error, 12 not reached -INSERT INTO abc VALUES (13)\; ROLLBACK AND CHAIN\; INSERT INTO abc VALUES (14)\; ROLLBACK; -- 13 error, 14 not reached +INSERT INTO trans_abc VALUES (11)\; COMMIT AND CHAIN\; INSERT INTO trans_abc VALUES (12)\; COMMIT; -- 11 error, 12 not reached +INSERT INTO trans_abc VALUES (13)\; ROLLBACK AND CHAIN\; INSERT INTO trans_abc VALUES (14)\; ROLLBACK; -- 13 error, 14 not reached -- START TRANSACTION + COMMIT/ROLLBACK AND CHAIN -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (15)\; COMMIT AND CHAIN; -- 15 ok +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (15)\; COMMIT AND CHAIN; -- 15 ok SHOW transaction_isolation; -- transaction is active at this point COMMIT; -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (16)\; ROLLBACK AND CHAIN; -- 16 ok +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (16)\; ROLLBACK AND CHAIN; -- 16 ok SHOW transaction_isolation; -- transaction is active at this point ROLLBACK; -- START TRANSACTION + COMMIT/ROLLBACK + COMMIT/ROLLBACK AND CHAIN -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (17)\; COMMIT\; INSERT INTO abc VALUES (18)\; COMMIT AND CHAIN; -- 17 commit, 18 error +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (17)\; COMMIT\; INSERT INTO trans_abc VALUES (18)\; COMMIT AND CHAIN; -- 17 commit, 18 error SHOW transaction_isolation; -- out of transaction block -START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO abc VALUES (19)\; ROLLBACK\; INSERT INTO abc VALUES (20)\; ROLLBACK AND CHAIN; -- 19 rollback, 20 error +START TRANSACTION ISOLATION LEVEL REPEATABLE READ\; INSERT INTO trans_abc VALUES (19)\; ROLLBACK\; INSERT INTO trans_abc VALUES (20)\; ROLLBACK AND CHAIN; -- 19 rollback, 20 error SHOW transaction_isolation; -- out of transaction block -SELECT * FROM abc ORDER BY 1; +SELECT * FROM trans_abc ORDER BY 1; -DROP TABLE abc; +DROP TABLE trans_abc; -- Test for successful cleanup of an aborted transaction at session exit. diff -Nru postgresql-13-13.11/src/test/regress/sql/updatable_views.sql postgresql-13-13.12/src/test/regress/sql/updatable_views.sql --- postgresql-13-13.11/src/test/regress/sql/updatable_views.sql 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/test/regress/sql/updatable_views.sql 2023-08-07 20:11:34.000000000 +0000 @@ -1244,6 +1244,23 @@ DROP TABLE t1; -- +-- Test sub-select in nested security barrier views, per bug #17972 +-- +CREATE TABLE t1 (a int); +CREATE VIEW v1 WITH (security_barrier = true) AS + SELECT * FROM t1; +CREATE RULE v1_upd_rule AS ON UPDATE TO v1 DO INSTEAD + UPDATE t1 SET a = NEW.a WHERE a = OLD.a; +CREATE VIEW v2 WITH (security_barrier = true) AS + SELECT * FROM v1 WHERE EXISTS (SELECT 1); + +EXPLAIN (COSTS OFF) UPDATE v2 SET a = 1; + +DROP VIEW v2; +DROP VIEW v1; +DROP TABLE t1; + +-- -- Test CREATE OR REPLACE VIEW turning a non-updatable view into an -- auto-updatable view and adding check options in a single step -- diff -Nru postgresql-13-13.11/src/tools/msvc/Solution.pm postgresql-13-13.12/src/tools/msvc/Solution.pm --- postgresql-13-13.11/src/tools/msvc/Solution.pm 2023-05-08 21:17:31.000000000 +0000 +++ postgresql-13-13.12/src/tools/msvc/Solution.pm 2023-08-07 20:11:34.000000000 +0000 @@ -152,6 +152,8 @@ my $package_bugreport; my $package_url; my ($majorver, $minorver); + my $ac_define_openssl_api_compat_found = 0; + my $openssl_api_compat; # Parse configure.in to get version numbers open(my $c, '<', "configure.in") @@ -176,10 +178,15 @@ $majorver = sprintf("%d", $1); $minorver = sprintf("%d", $2 ? $2 : 0); } + elsif (/\bAC_DEFINE\(OPENSSL_API_COMPAT, \[([0-9xL]+)\]/) + { + $ac_define_openssl_api_compat_found = 1; + $openssl_api_compat = $1; + } } close($c); confess "Unable to parse configure.in for all variables!" - unless $ac_init_found; + unless $ac_init_found && $ac_define_openssl_api_compat_found; if (IsNewer("src/include/pg_config_os.h", "src/include/port/win32.h")) { @@ -436,6 +443,7 @@ LOCALE_T_IN_XLOCALE => undef, MAXIMUM_ALIGNOF => 8, MEMSET_LOOP_LIMIT => 1024, + OPENSSL_API_COMPAT => $openssl_api_compat, PACKAGE_BUGREPORT => qq{"$package_bugreport"}, PACKAGE_NAME => qq{"$package_name"}, PACKAGE_STRING => qq{"$package_name $package_version"},